Comment Re:Doesn't it seemed like a flawed study? (Score 1) 418
How does the carrier know whether someone's driving or not?
(speechless)
How does the carrier know whether someone's driving or not?
(speechless)
Well, I never thought I'd see someone argue that flying a military jet is easier than driving a car.
Yeah that's a thing
That's the whole point. In both cases you're a poor judge of your own ability. "I did it and felt OK and didn't die" doesn't mean it wasn't dangerous.
But you'll put your life in the hands of somebody who's had basically no formal training in driving?
You are allowed 5 free articles (or views) of The Onion website. After that they greet you with a paywall.
Is that real? I saw it and figured it was another Onion joke.
No country has the balls to tell USA to fuck off, at the moment. Except Iran and North Korea but they know US wouldn't bother to swat them.
Until you get so small as to bump into the realm of Quantum Mechanics, and then you literally can't say for certain - ever - if a specific thing is at one location or another.
You can, but you wouldn't know where it was going
You forgot Yasser Arafat...
This is why you don't use threads for important stuff...
Does this photo have another angle on the Mars lizard ?
Huh? Google Maps still exists
"unsigned int x = -3;" generates no compile errors or warnings.
This supports the point of the poster you were referring to. The code is correct, predictable, and generates no warnings.
If you don't believe me, listen to the creator of C++
C and C++ are different languages. The implicit conversion rules and the promotion rules are different in C++ to C. In C, unsigned types always promote to unsigned types. But in C++, unsigned types may promote to signed ones, if the value fits in the signed range.
In general, it's a good idea to used signed ints whenever possible.
Says who?
In C, signed ints have a whole lot of problems associated with representation and overflow. But unsigned ints have well-defined behaviour in every circumstance. They wrap around in case of overflow or an out-of-range assignment. You can safely test, set and reset individual bits.
With signed ints, you can raise a signal (triggering a signal handler, or aborting the program if there is no handler) if there is overflow or underflow. Using '^', '|' or '&' on signed values can trap due to creating an invalid representation (e.g. negative zero, or parity error).
Test: what is wrong with this code snippet (assuming the appropriate furniture)? Hint: it doesn't always print 0x82.
char ch = 130;
printf("0x%x\n", (unsigned int)ch);
As a former Alaskan I can tell you that glacialization has come back the last 3 years and summer temperatures are rapidly falling year after year. So climate != weather but 13 years of data is starting to make a case for a cooler climate regardless of increased CO2.
"global warming" doesn't meant that every point on the globe will warm up by the same amount. It could be that Alaska gets colder, but Brazil gets hotter by a larger amount, for example.
PURGE COMPLETE.
