All the probability theory in the world doesn't make me feel better about not winning the car. (Which, of course I had actually correctly selected with my first guess). Wouldn't you also be upset if you lost because you failed to switch when you had the opportunity? Either choice can result in a loss--wouldn't you rather make the choice that is more likely to result in a win?
I used to be a die-hard C/C++ programmer, and I figured I'd never be quite as comfortable in another language. These days, though, I don't feel productive unless I'm using OCaml. You won't realize how broken and clumsy most mainstream languages are until you learn OCaml or one of its ML relatives. It takes some time, but it's worth it.
And yes, you can actually write real programs with it!
There's nothing ambiguous or implied in the way that sentence is structured. It pretty clearly states him as being a co-founder of Yahoo. The Slashdot story is both unambiguous and wrong in this respect. I was referring to the original article to which the Slashdot story links, which says:
Mike McCue hasn't talked to Yahoo Inc. co-founder Jerry Yang since Microsoft Corp. ambushed the Internet pioneer with an unsolicited takeover bid a month ago. I don't think the author of this article meant to imply that McCue co-founded Yahoo with Yang, but I can see how the Slashdot editors read it that way. For the record, once again, McCue is not a co-founder of Yahoo.
Mike McCue is not a co-founder of Yahoo. Prior to starting Tellme in 1999, he founded a company called Paper Software, which was subsequently bought by Netscape, but he was never directly involved with Yahoo.
The article is admittedly ambiguous about this point--it introduces Jerry Yang as a co-founder of Yahoo, and in the process, it inadvertently implies that he co-founded it with McCue.
Will we now have computers that do base 4 arithemetic rather than base 2? A base-4 digit is the same as two base-2 digits, information-wise, so it doesn't really matter how the information is stored. If you want to store a byte in some piece of hardware, you can store it as 4 base-4 values or 8 base-2 values, and it'll all look the same to the CPU.
The term "canon" is used in literature to describe a generally-accepted set of "great" literary works, and it makes perfect sense to extend this concept to games.
Hey everybody, look! A member of our own online community, who is definitely not receiving any form of compensation from a game company, has just declared their undying loyalty toward an upcoming title! Golly, let's all go check it out!
The 360 may be a middle ground in terms of price, but not in terms of features. If you're looking for an innovative console, the Wii is the only game in town (so to speak).
1. The fact that an array, a pointer (of any level), and an address are fundamentally the same. I.e. not seeing that there's no conversion needed from "type[]" to "type *"
Interestingly enough, this statement is not perfectly accurate. They're really different types with different meanings, but C has a bunch of shortcuts that make them appear to be the same thing in certain (common) situations.
Let's take an example. Say we have the following declarations:
int a[5]; int *p;
Here are two examples of C's syntactic sugar:
p = a;// really means p = &a[0]; p[1] = 0;// really means *(p + 1) = 0;
These shortcuts make arrays and pointers seem interchangeable when they are actually slightly different beasts.
To see how they're different, consider the expressions a[1] and p[1]. It might look like these expressions do the exact same thing, but they don't. The first statement reads an integer from the array a, which is allocated on the current function's stack frame (assuming a was declared as a local). The second statement reads a pointer from the current function's stack frame, and it reads an integer from the block of memory to which that pointer points.
Note that the first expression involves one memory read, and the second expression involves two. The only difference here is the types of a and p--in other words, the array type and the pointer type are not "fundamentally the same".
By the same token, you're not allowed to assign a pointer to an array (i.e., a = p;). The array has already been allocated in memory somewhere, so there's no way to modify its location by assigning a pointer to it.
The one place where the array type and pointer type actually are identical is in function parameters. The function types void foo(int *p) and void foo(int a[]) are identical.
Unless you believe that people should only have sex for the purposes of reproduction, then there are lots of reasons to use birth control, and an extra option like this, for guys, is a good thing. I'm sure we've all heard stories of the girl trapping the guy by getting pregnant by forgetting to take her pill. Well, maybe now those guys will have another option.
I think it's rather unfortunate that that's the first example that comes to mind regarding the benefits of this pill. How about the simple fact that men are now equally able to take responsibility for birth control in a sexual relationship? Also, this pill provides a nice alternative to the nasty side-effects associated with existing female birth control pills.
I didn't read TFA, but "3 hours a night in Molten Core" is not the only end-game in World of Warcraft. PVP Battlegrounds, Blackwing Lair, Zul'Gurub, Ahn-Qiraj, soon, Naxxrammis and the upcoming Burning Crusade expansion pack -- the list goes on. I would assume the aricle is short-sighted throughout.
Er, I think the emphasis was on "3 hours a night", not on "Molten Core". Most of the end-game content in WoW requires a pretty serious time committment, well beyond that which is required to reach level 60 in the first place.
Slashdot Mirror
Video game pushes your buttons.
Give Objective Caml a try.
I used to be a die-hard C/C++ programmer, and I figured I'd never be quite as comfortable in another language. These days, though, I don't feel productive unless I'm using OCaml. You won't realize how broken and clumsy most mainstream languages are until you learn OCaml or one of its ML relatives. It takes some time, but it's worth it.
And yes, you can actually write real programs with it!
Mike McCue is not a co-founder of Yahoo. Prior to starting Tellme in 1999, he founded a company called Paper Software, which was subsequently bought by Netscape, but he was never directly involved with Yahoo.
The article is admittedly ambiguous about this point--it introduces Jerry Yang as a co-founder of Yahoo, and in the process, it inadvertently implies that he co-founded it with McCue.
The term "canon" is used in literature to describe a generally-accepted set of "great" literary works, and it makes perfect sense to extend this concept to games.
http://en.wikipedia.org/wiki/Western_canon
Perhaps next time you'll educate yourself (or at least read your own link) before denigrating others!
Hey everybody, look! A member of our own online community, who is definitely not receiving any form of compensation from a game company, has just declared their undying loyalty toward an upcoming title! Golly, let's all go check it out!
The 360 may be a middle ground in terms of price, but not in terms of features. If you're looking for an innovative console, the Wii is the only game in town (so to speak).
Interestingly enough, this statement is not perfectly accurate. They're really different types with different meanings, but C has a bunch of shortcuts that make them appear to be the same thing in certain (common) situations.
Let's take an example. Say we have the following declarations:
Here are two examples of C's syntactic sugar:
These shortcuts make arrays and pointers seem interchangeable when they are actually slightly different beasts.
To see how they're different, consider the expressions a[1] and p[1]. It might look like these expressions do the exact same thing, but they don't. The first statement reads an integer from the array a, which is allocated on the current function's stack frame (assuming a was declared as a local). The second statement reads a pointer from the current function's stack frame, and it reads an integer from the block of memory to which that pointer points.
Note that the first expression involves one memory read, and the second expression involves two. The only difference here is the types of a and p--in other words, the array type and the pointer type are not "fundamentally the same".
By the same token, you're not allowed to assign a pointer to an array (i.e., a = p;). The array has already been allocated in memory somewhere, so there's no way to modify its location by assigning a pointer to it.
The one place where the array type and pointer type actually are identical is in function parameters. The function types void foo(int *p) and void foo(int a[]) are identical.
I cried when Floyd died for me.
Er, I think the emphasis was on "3 hours a night", not on "Molten Core". Most of the end-game content in WoW requires a pretty serious time committment, well beyond that which is required to reach level 60 in the first place.