51 karma · joined July 29, 2012
P.S. Recursive bonus: closed with a comment ("you should just google it") and now actually the top result in search output (happens quite frequently) :)
No sympathy for clunky DRM-"enhanced" hw, of course :)
(was touching)
http://www.kuro5hin.org/story/2004/2/15/71552/7795
I'd say, the user experience has improved since then overall (meaning the code quality, too, in one of the most practical senses).
Anyways, never ever try out your luck with mushrooms, if you were not well-taught to deal with them by someone experienced, in person (internet advice / taking and sending m-room photos do not count, period).
Couple seasons of mushroom-hunting alongside someone, willing to teach you, is a minimum before you ever decide to put any mushroom you picked up yourself into your (or someone else's) mouth.
Btw, even experienced people sometimes do not pick up mushrooms, they have suspicions about (there are some not quite deadly ones here, masquerading as edible in my place, for example).
But yes, authoring a book titled "Well-defined C (and C++)" one day would be awesome.
Thanks for the link.
I have yet to see a thorough (source-to-compiler-intent-to-assembly) comparative description of undefined, unspecified and implementation-defined behaviors, though (not just a somewhat insightful blog, or techno gospel, which the C and C++ standards are).
Good luck!
If anyone wants a wager on whether Reddit is accessible through most ISPs in a month, ping me :D
* Closures capturing their environment and keeping local variables alive longer than intended.
How can that happen to a stack variable (and RAII is about those), given C++11/14's closures ("lambdas") do not prolongate the lifetime of the objects captured by reference? Or did you mean capture by value? (would be really confusing with RAII-ing classes :) )