>>Hello Thomas.
>>
>>>> When I am asked to find and correct a problem I do so my commenting out the offending code, dating my action and define why I did it. Often my comments are longer than the code I create. If need be you can return to the commented area should that be necessary. <<
>>
>>Now that would drive me crazy. It is one of my pet peeves. Not comments < g >. I often have more comments than code in my methods. But I hate to see commented out code. IMHO, if the code doesn't work, it should be deleted.
>
>I do it when I fix somebody else's code, for several reasons: I want a reminder on the previous version, in case I didn't properly understand the intention; I want the author to see what I have done and take action if I was wrong, and I want some history at hand to keep the evolution of the snippet visible. Once it's stable enough, or when it goes into a major revision, I clean it up.

Dragan;

Amen! A programmer after my own heart!

Tom