On Tue, 31 May 2005 22:35:31 -0000, Robert Bonomi wrote:
Only to
find that *now* that the crime is happening "somewhere else". This was
a 'bug' with *legs* -- it MOVED!

Sounds like a timing problem (race condition)?

In desperation, played with the order in which the modules were linked,
found a sequence where (presumably *still* happening) memory corruption
did not affect the answers coming out, and released it that way. Put a
*LOUD* note in the source, documenting the existence of the problem; that
if the existing code was linked in _this_ order, the problem was 'harmless',
and that _any_ modification of any component was "highly risky".

I love finding those.

This was documentation that *literally* started off:
"Warning, Will Robinson. WARNING!!"
and ended with "All hope abandon, ye who press 'enter' here."

My personal favorite is writing error messages like "There is no way
that you should ever see this error message." But, you don't want an
unhandled exception, even if it's "impossible".