On calling clear() on a vector<std::string> my code takes a left turn and reenters at some random point. Seriously, how can one be a programmer and NOT believe in ghosts??
On calling clear() on a vector<std::string> my code takes a left turn and reenters at some random point. Seriously, how can one be a programmer and NOT believe in ghosts??
All the way off. It just... leaves. The next lines don't get executed anymore, instead the code continues somewhere else. Now, I had such things with memory violations that didn't directly result in access violations, but that really shouldn't happen on calling vector::clear.
Yes, that happens when you step through a code, that was optimized by the compiler. This can change the execution order, that is why the debug build is done without ANY optimizations.
If all else fails, imagine an alien sitting on a flying saucer near you, and explain the code to him, line by line (i'm serious!).
Try taking a good night's sleep to recharge your obviousness detectors, then look at the code the next day.
If all else fails, imagine an alien sitting on a flying saucer near you, and explain the code to him, line by line (i'm serious!).
...There is a reason they crash test cars with dummies instead of real people...My wife might look a bit funny... but wait, I could try explaining the code to her instead... :hmm:
http://rt.com/news/meteor-shower-perseid-sky-341/
Could you actually see the meteor themselves by your own eyes, or you need a camera to see them?
http://rt.com/news/meteor-shower-perseid-sky-341/
Could you actually see the meteor themselves by your own eyes, or you need a camera to see them?
Fun fact: The apparent magnitude of meteors is significantly lower when it's cloudy.
I knew the UK got a lot of rain, but...wow.
![]()
Stonehenge in Washington? What is this madness?!
Fun fact: When Stonehenge was built native Americans just populated the Arctic and learned how to make tools out of bone...
The rain got so severe it flooded the UK and Stonehenge floated towards Washington.