I had no intention to overcomplicate the issue, that's why I posted a hint
on what to think about if he implements the code (whether he chooses to
handle that situation or not was left up to him). You went into detail and I
thought it would be useful to the readers to point out that your suggestion
was unusable and was not fixing an issue you claimed it was fixing. Had you
posted an algorithm that was valid and working (or not posted any at all) it
would have ended then. I just think it was valuable to point out that the
solution posted was not doing what you were claiming. It has nothing to do
with you or with this particular issue, I think it's good to point out that
code/algorithm/solution posted is not valid/correct/working. If I posted a
bogus code I would appreciate someone noticing and letting us know.
Jerry
Steve C. Orr said:
There are many possible solutions to the rare "bug" you mentioned, which
would likely have mild consequences anyway.
I'd list them all out for you but nobody asked me to so I won't bother.
The guy posted a simple question, and I posted a simple answer. He was
satisfied with the answer and, as far as we know, lived happily ever after.
I don't know why you've bothered to overcomplicate the situation.
If you're as smart as you like to imply then this newsgroup would benefit
from you posting solutions instead of criticisms.