Slashdot Mirror

why blame Microsoft? Have they been knowing for astroturfing here before?

Just a little...

http://lists.essential.org/1998/am-info/msg01529.html
http://www.theregister.co.uk/2009/01/27/microsoft_ie8_chain_letter/
http://www.1pstart.com/mercury-news-writer-accuses-microsoft-of-bribery/
http://www.dslreports.com/shownews/87901
http://news.cnet.com/8301-1035_3-57345892-94/microsoft-nokia-linked-to-comments-on-negative-lumia-review/
http://en.wikipedia.org/wiki/Astroturfing
http://linkprimer.com/internet-marketing/microsoft-encourages-reputation-management
http://www.velocityreviews.com/forums/t568832-microsoft-well-take-the-astroturf-supreme-please.html
http://www.nytimes.com/2009/07/30/business/smallbusiness/30reputation.html?_r=1
http://www.clickz.com/clickz/news/1698666/microsoft-tests-social-media-monitoring-product
http://www.informationweek.com/news/220200062
etc
etc
etc
etc

While not as powerful as my suggestion, I think that every time I've wanted this feature, the C++ const pointer would have sufficed.
To do it properly, not only does the object pointed to have to be unmodifiable, so too do any objects contained within that one, which C(++) does not do. (I.e. any pointer obtained via a 'const' pointer is also 'const'.)

I've just found a couple of discussions on this -
http://www.velocityreviews.com/forums/t150742-how-do-java-programmers-cope-with-java-missing-c-const.html
http://www.javamex.com/java_equivalents/const_java.shtml

Have you tried pressing the menu button

You mean the "put the letter Ø in the corner of the screen" button?

or 'next'?

Also puts the letter Ø in the corner of the screen.

I've never ever seen trailers you can't skip.

I don't remember the title I encountered (it was a rental), but I remember it was published by Universal. Here are some examples of where fast forward works but next chapter doesn't.

Here's an interview where he says it:

http://www.velocityreviews.com/forums/t576610-alan-cox-on-software-patents.html

"""Alan Cox: The same has happened with IP version 6. You notice that everyone
is saying IP version 6 is this, is that, and there's all this research
software up there. No one at Cisco is releasing big IPv6 routers.
Not because there's no market demand, but because they want 20
years to have elapsed from the publication of the standard before
the product comes out -- because they know that there will be
hundreds of people who've had guesses at where the standard
would go and filed patents around it. And it's easier to let things
lapse for 20 years than fight the system."""

(More info would be good - any other prominent techs saying this?)

You sadly don't know what you are talking about and you don't even try to disprove anything that I've said. For example, you replied to my comment regarding how Google is a disgrace at filtering spam with an idiotic statement that:

I don't see any difference between DejaNews and Googlegroups. It's still the same interface that I've been using since the 90s.

Either you failed to read what I've written or you tried to pull a red herring to divert the attention from Google's appallingly bad track record at tackling both spam and spammers to this absurd comment regarding user interfaces. My point was about Google's terrible anti-spam and anti-spammer track record, not UI design. So, where exactly did you get the idea this was about UI?

Then your next statement is this silly thing:

Google search results DO link to Usenet groups.

Once again you've failed to understand what has been said. No one said that Google stopped presenting usenet results. What has been said was that Google groups search is so bad that it even places on their top hits (i.e., what Google considers the best match) hits from websites that do nothing more than mirror usenet to try to pass off discussions from newsgroups as their own forums. As a quick and dirty demonstration, I've browsed comp.lang.c and then searched Google groups for "How to use maloc with strcut", a discussion which has been started quite recently and whose subject is somewhat unique. So, after searching for the subject through Google groups, you will notice that the first two hits are from websites mirroring comp.lang.c. Granted, in this test (which was quick and dirty) a link to Google's site on comp.lang.c appears in 3rd place but this, unfortunately, isn't the norm. It is, quite unfortunately, an isolated incident. For example, if you search for "malloc array" on google groups then all your hits will be from sites that either mirror usenet or provide rudimentary forums, with the first usenet hits appearing on the 3rd page and being from groups such as mailing.freebsd.stable and comp.unix.questions, the last one being a hit from 1991. In fact, the first hit that pops up from Google's usenet archive that comes from a C-related newsgroup comes in the form of this post from comp.lang.c.moderated that appears at the bottom of the 5th search results page and is from 2003.

So, care to explain where exactly do you not see a burying of usenet's search results and an erosion of the usenet's archive?

You may play the role of one of Google's tireless PR drones by either slapping red herrings around in the attempt to conceal Google's problems such as the abysmal spam problem and it's usenet results' burying in it's Google groups search. You may even try to go into personal attacks such as claiming that Google's problems amount to nothing more than user dumbness. Yet, that doesn't stop people from looking stuff for themselves and, as a consequence, realize that your accusations are either baseless or patently false.

Dell's are very funny about ram, make sure that you use ram specifically for Dell either Crucial or Kingston.

Are you running an all Dell shop and only swapping RAM between them? I swear, people will take a crapshot at Apple without looking at what they are currently running. It was a lot cheaper for me buying ram for my B&W G3 back in the day than a Dell Dimension.

"0x" designates a number being represented, or displayed, as a hex value. It is not being displayed as a BCD value. This has nothing to do with how it is being treated internally by the machine.

This is just plain wrong. If you want to go find some sources to back up this claim, feel free to try, but until then please stop repeating it.

BCD values are normally given as hex values (i.e. the value actually stored in memory). The number 12, in BCD, is 0x12, 00010010, or 18. It would be stupid to write it in decimal, because it would only confuse people. However, the value being stored would never be written as “12”, unless it was implicit that you were writing it in hex (e.g. in certain variants of assembly language all constants are written in hex by default).

The 0x notation is commonly used when writing hex values, including when writing BCD hex values. As I have said elsewhere, if you are storing a BCD number in a C program for an embedded project, you’ll use hex 0x notation. There is no other sensible way to store the value.

I actually took embedded design courses in college and we did BCD operations on embedded microcontrollers, by the way. I think I know what I’m talking about. But don’t just take my word for it... /t21476-re-binary-to-bcd-assistance.html#post132747 involves exactly this scenario: working with binary and BCD numbers (more specifically, converting from one to the other). Binary and BCD are encoding formats, not to be confused with the representation (hex) or the internal storage (binary). As you can clearly see, BCD values are given in hex 0x notation:

carry = (bcd[j] & 0x10) == 0x10;

...

printf(" %x\n", bin);

Note that the correct printf format for a BCD number is %x. BCD numbers are written in hex. Do this:

#include <stdio.h>

int main() {
    unsigned long num;

    num = ???;
    printf("%x", num);

    return 0;
}

What are you going to put in the place of the “???” to get it to print “12”? You will use “0x12”, of course. Anything else would be silly.

Oh, you're so right. From now on, I'll just totally go to sleep whenever I see the little lock, and I'll ignore stuff like this or this

Some of those are a hack around the VC 6 "for loop doesn't scope as per ANSI" bug. This forum post explains when its used.