This is what will really fill that void between PDAs and UMPCs. Two pounds, 200 bucks, built-in wireless, comes with Linux installed, but can run Windows too.
FTA: Think of the last time you were at a national park. It's a very good possibility that the only information you had about the park fit on a tri-fold paper that you picked up at the visitor's station. In the information age, how is this acceptable?
It's more than just acceptable. It's exactly what I want when I go to a national park: to get away from the hyper-connected world of technology. The only information I want I will get from the park ranger, who hopefully can't tell his DVD-ROM from his Firewire, but can answer my questions about lizards and rocks.
"Earmarks are good for the country and good for the people you represent. That is the role of a congressman. If you can't get money for your district, you shouldn't be in Congress."
This is a quote FTA from Republican representative, Don Young.
Ted Striker: My orders came through. My squadron ships out tomorrow. We're bombing the storage depots at Daiquiri at 1800 hours. We're coming in from the north, below their radar.
Elaine Dickinson: When will you be back?
Ted Striker: I can't tell you that. It's classified.
As a student I really thought I would get the opportunity to write games, but after seeing the development process at a software publisher specializing in gaming, I realized that the programmers spend more time dealing with things like physics and optimization and leave a lot up to graphics artists.
That was not my experience in 10 years of professional game programming. Every project I worked on required a significant amount of graphics programming. In some cases, there were one or two guys who did the graphics programming full time. In others, almost everyone contributed some graphics code. And even if you end up doing mostly audio, AI, or physics, the math you'll learn in a 3D graphics class is very useful.
I'm not sure if you're being sarcastic.:) No, I don't want fallthrough. Depending on the situation, fallthrough is trivially rewritten by making the downstream case blocks into functions, or using non-exclusive ifs. An example of the former:
switch (foo ) { case 1:
doA();
// FALL THROUGH case 2:
x = ( y << 2 ) + 1;
doB(x);
break;
case 3:
e = m * c * c;
break; }
is rewritten:
int transmogrify( int y ) {
int x;
x = ( y << 2 ) + 1;
doB(x);
return x; }
switch (foo ) { case 1:
doA();
x = transmogrify(y);
break;
The (if.. else if.. else if..) idiom is a "generalized switch". When I first encountered it, I recall being confused a bit, so your point is a fair one. I think the expectation is that the elses should somehow create a nested structure. Yet the code does not reflect a nesting in its layout. If C had some sort of generalized switch syntax like
genswitch {
case (cond1)
{
firstthing();
}
case (cond2)
{
some = other + stuff;
}.. etc.. } ... would you agree that it's better than goto? If so, then it's really a minor question of syntax. A novice programmer might be confused by the (if..else if..else if) syntax, but there are lots of much harder problems in programming than picking up this idiom.
As for the multiple returns versus multiple "else if's", I still prefer multiple "else if's". Being familiar with the idiom, I think it's just as clear. (And with any decent compiler, it will compile to the same binary, so you wouldn't get the minor speed gains from reducing the number of jumps.) The benefit of multiple "else if's" is again, maintainability. Many people, myself included, consider having a single return statement within a function to be a best practice. It's not a rule I live by, but I rarely find that multiple points of return are necessary for flow clarity nor speed (though, in those cases, I will use them). This enforces the idea that structure defines flow, a core concept in structured programming. It makes for easier static code analysis, which helps both compiler code optimization and with programmers tracking down logic/flow-related bugs. Of course, this practice is a lot easier to follow in a language that has exception handling, so you don't have to jump through hoops to signal error conditions.
O.K. Now add multiple failure conditions which all require different levels of cleanup handling. That's pretty much most functions in a kernel. Which is why you use goto more: it's actually clearer and reduces code duplication, making it safer.
If you need to break out of the block, fine: add a goto. I'm not claiming that gotos are useless. They're just not called for in this case.
Honestly, if C had exception handling, there would be almost no need for gotos in a kernel.
shorter perhaps. I don't see why it would be less bug prone.
Come on now. Maintaining blocks + labels + gotos is clearly more error prone than just maintaining blocks.
And I do think the structure is less easy to parse, and less accurately reflects the logic and structure of the algorithm. I know flow charts are deeply unfashionable, but sometimes they capture exactly what you mean.
The multiple "else if" block is an extremely common idiom that an experienced programmer recognizes immediately. It exactly reflects the logic and structure of an "arbitrary switch". Seriously, you've never seen this before?
EA would have to be complete idiots to not make Madden 2008, 2009, etc. It's a huge cash cow - they make several hundred million in revenue from that single title each year. If you don't like it, don't buy it.
That said, EA is a big company with a corporate culture that doesn't exactly promote creativity. Riccitello is trying to do what he can to push in the right direction. The CEO can't just clap his hands and make creativity happen. He recognizes the issue and is calling for the company, and the industry as a whole, to take more risks and make more creative games.
If you try to apply the results of the study to a specific situation, standard error certainly does come into play. For instance, if the error in an IQ test is 5 points, and my older brother gets 3 more points than I do on that test, you can't claim that the study predicted that particular spread.
Trick question for you. How much is Final Fantasy X?
You want to know why it's a trick question? Because you can't buy Final Fantasy X. You can buy a Playstation 2 version of it, but you cannot buy Final Fantasy X to play on your XBox. Go ahead and look around on the web for a place that you can get Final Fantasy X for non-Sony hardware. I'll wait here for you.
Slashdot Mirror
This is what will really fill that void between PDAs and UMPCs. Two pounds, 200 bucks, built-in wireless, comes with Linux installed, but can run Windows too.
FTA: Think of the last time you were at a national park. It's a very good possibility that the only information you had about the park fit on a tri-fold paper that you picked up at the visitor's station. In the information age, how is this acceptable?
It's more than just acceptable. It's exactly what I want when I go to a national park: to get away from the hyper-connected world of technology. The only information I want I will get from the park ranger, who hopefully can't tell his DVD-ROM from his Firewire, but can answer my questions about lizards and rocks.
"Earmarks are good for the country and good for the people you represent. That is the role of a congressman. If you can't get money for your district, you shouldn't be in Congress."
This is a quote FTA from Republican representative, Don Young.
This is the "party of smaller government?"
Sony would have to be complete idiots to give up this momentum, this just seems like a strategy to unload the 60GB hardware.
A product that has "momentum" doesn't have to get "unloaded".
Wow, does he really have nothing better to do with his time?
You should check out his blog. He surely can't have time to do anything else.
Ted Striker: My orders came through. My squadron ships out tomorrow. We're bombing the storage depots at Daiquiri at 1800 hours. We're coming in from the north, below their radar.
Elaine Dickinson: When will you be back?
Ted Striker: I can't tell you that. It's classified.
As a student I really thought I would get the opportunity to write games, but after seeing the development process at a software publisher specializing in gaming, I realized that the programmers spend more time dealing with things like physics and optimization and leave a lot up to graphics artists.
That was not my experience in 10 years of professional game programming. Every project I worked on required a significant amount of graphics programming. In some cases, there were one or two guys who did the graphics programming full time. In others, almost everyone contributed some graphics code. And even if you end up doing mostly audio, AI, or physics, the math you'll learn in a 3D graphics class is very useful.
I'm not sure if you're being sarcastic.
The (if.. else if.. else if..) idiom is a "generalized switch". When I first encountered it, I recall being confused a bit, so your point is a fair one. I think the expectation is that the elses should somehow create a nested structure. Yet the code does not reflect a nesting in its layout. If C had some sort of generalized switch syntax like
.. etc ..
... would you agree that it's better than goto? If so, then it's really a minor question of syntax. A novice programmer might be confused by the (if..else if..else if) syntax, but there are lots of much harder problems in programming than picking up this idiom.
genswitch
{
case (cond1)
{
firstthing();
}
case (cond2)
{
some = other + stuff;
}
}
As for the multiple returns versus multiple "else if's", I still prefer multiple "else if's". Being familiar with the idiom, I think it's just as clear. (And with any decent compiler, it will compile to the same binary, so you wouldn't get the minor speed gains from reducing the number of jumps.) The benefit of multiple "else if's" is again, maintainability. Many people, myself included, consider having a single return statement within a function to be a best practice. It's not a rule I live by, but I rarely find that multiple points of return are necessary for flow clarity nor speed (though, in those cases, I will use them). This enforces the idea that structure defines flow, a core concept in structured programming. It makes for easier static code analysis, which helps both compiler code optimization and with programmers tracking down logic/flow-related bugs. Of course, this practice is a lot easier to follow in a language that has exception handling, so you don't have to jump through hoops to signal error conditions.
O.K. Now add multiple failure conditions which all require different levels of cleanup handling. That's pretty much most functions in a kernel. Which is why you use goto more: it's actually clearer and reduces code duplication, making it safer.
If you need to break out of the block, fine: add a goto. I'm not claiming that gotos are useless. They're just not called for in this case.
Honestly, if C had exception handling, there would be almost no need for gotos in a kernel.
shorter perhaps. I don't see why it would be less bug prone.
Come on now. Maintaining blocks + labels + gotos is clearly more error prone than just maintaining blocks.
And I do think the structure is less easy to parse, and less accurately reflects the logic and structure of the algorithm. I know flow charts are deeply unfashionable, but sometimes they capture exactly what you mean.
The multiple "else if" block is an extremely common idiom that an experienced programmer recognizes immediately. It exactly reflects the logic and structure of an "arbitrary switch". Seriously, you've never seen this before?
EA would have to be complete idiots to not make Madden 2008, 2009, etc. It's a huge cash cow - they make several hundred million in revenue from that single title each year. If you don't like it, don't buy it.
That said, EA is a big company with a corporate culture that doesn't exactly promote creativity. Riccitello is trying to do what he can to push in the right direction. The CEO can't just clap his hands and make creativity happen. He recognizes the issue and is calling for the company, and the industry as a whole, to take more risks and make more creative games.
Your cases are mutually exclusive. The following is indeed clearer, shorter, and less bug prone:
/* and so-on */
if(criterion1||criterion3){
do_something();
} else if(criterion2){
do_something_else;
} else if(criterion4){
do something_else again();
}
Bogus hotmail accounts!?!?! I don't believe it!!!
Maybe because if the IDE reformats all your code you wind up with the entire file as a diff when you check it in to your source code control system?
This is why a code formatter should be part of the source control checkin process.
HMOs deny valid claims of their customers every single day. So much for risk mitigation.
but it's still just a comic
Dude, it's Captain America! Captain America's dead, dude!
Yeah, I don't get it either.
.gnola evom esaelP
> Microsoft is a convicted monopolist
Ask AT&T how much the DOJ cares about anti-monopoly cases these days.
>> If you try to apply the results of the study to a specific situation
> Nobody's doing that - and nobody who understands statistics is even thinking about it. NEXT!
So, like I said, it's non-predictive. NEXT!
If you try to apply the results of the study to a specific situation, standard error certainly does come into play. For instance, if the error in an IQ test is 5 points, and my older brother gets 3 more points than I do on that test, you can't claim that the study predicted that particular spread.
Trick question for you. How much is Final Fantasy X?
You want to know why it's a trick question? Because you can't buy Final Fantasy X. You can buy a Playstation 2 version of it, but you cannot buy Final Fantasy X to play on your XBox. Go ahead and look around on the web for a place that you can get Final Fantasy X for non-Sony hardware. I'll wait here for you.
the author is trying to romanticize gold farmers
Yeah, 80 hour weeks in small offices for 35 cents an hour. Romantic.
I'll feel sorry for these Chinese people, but in the end I'll still gank them in game whenever and wherever I find them.
How valiant of you.
he still couldn't understand this udderly basic principle
Moo.
Anyway, you can go out and buy a god-damned high end video-card, and it will fit in the PCI-E slot of a newer Apple system.
Similarly, game discs for the XBox 360 fit perfectly well inside your car's CD player.