Politics, Embedded Linux, Theology, and Other Eclectica
The atexit() Rule of Software Development
I hereby propose "The atexit() Rule":
If you are seriously considering fixing a bug by patching atexit() to perform an action that is completely unrelated to process exit, then is it probably time to rewrite your code.
Wait, no...never mind. I'm ever-more sure I don't actually want to know. In fact, I'm pretty sure I actively _don't_ want to know, because every additional person on whom that information is inflicted would thereby make the universe a worse place.
My condolences go out to you, for being in a position where you have apparently been compelled to join the ranks of those cursed by such knowledge. But they go out to you through the bulletproof plexiglass of your quarantine cell.
1 comment:
Why the fu...
Wait, no...never mind. I'm ever-more sure I don't actually want to know. In fact, I'm pretty sure I actively _don't_ want to know, because every additional person on whom that information is inflicted would thereby make the universe a worse place.
My condolences go out to you, for being in a position where you have apparently been compelled to join the ranks of those cursed by such knowledge. But they go out to you through the bulletproof plexiglass of your quarantine cell.
:)
Post a Comment