Otherwise, the "next guy" comes along, looks at the code, and thinks, "That's weird... Well, I can fix this." And proceeds to hack away at code that was written a specific way for a specific reason.
It has happened to me, the latest case was something so screwy that you should stop a search after the second first in order to accomplish processing some format created by the same i****. YES, it is not a misprint "after the second first". Of Course there was no comment as to that pecularity and, because it was a unique exception I did not run into it until after thousands of systems shipped. Fortunately we can avoid the "unique exception" by other means, so no reprogramming of thousands of units will be required.

Erik

Isn't it odd that those that make $#!+ like that are the same that do not commet it?