3 ms·
OT, but for the uninitiated who you enjoyed the above and didn't know him, the James Mickens USENIX column is absolutely hilarious and insightful. Other exampl
by riffraff 12y ago
OT, but for the uninitiated who you enjoyed the above and didn't know him, the James Mickens USENIX column is absolutely hilarious and insightful.
Other examples can be found towards the bottom of his MSR page[0] (search for "humor").
[0] http://research.microsoft.com/en-us/people/mickens/ http://research.microsoft.com/en-us/people/mickens/
- dghf 12y agohttp://research.microsoft.com/en-us/people/mickens/thenightwatch.pdf http://research.microsoft.com/en-us/people/mickens/thenightw... in particular is a thing of beauty. Indeed, the common discovery mode for an impossibly large buffer error is that your program seems to be working fine, and then it tries to display a string that should say “Hello world,” but instead it prints “#a[5]:3!” or another syntactically correct Perl script, and you’re like WHAT THE HOW THE, and then you realize that your prodigal memory accesses have been stomping around the heap like the Incredible Hulk when asked to write an essay entitled “Smashing Considered Harmful.”
- tormeh 12y ago"Smashing considered harmful" - The Hulk About C++: "When it’s 3 A.M., and you’ve been debugging for 12 hours, and you encounter a virtual static friend protected volatile templated function pointer, you want to go into hibernation and awake as a werewolf and then find the people who wrote the C++ standard and bring ruin to the things that they love."
- dghf 12y agoAlso about C++: "One time I tried to create a list<map<int>>, and my syntax errors caused the dead to walk among the living."