Lloyd L Chambers wrote:
> Bill,
>
> Yes, but why bother? I can just as easy add temporary printlns. The
> name alone is a good reminder to strip them out before committing.
> Adding log messages means they'd tend to be left in the code, cluttering
> everything long after their usefulness passes.
>
> Logging is *not* a debugging solution IMO. IMO, logging is for
> informing customers of server state, not debugging one's logical errors
> in code.
I don't care what you do to debug the code before committing, as long
as you're ripping it out before committing.
I was only talking about the "debugging" code that would be left in the
code when it's shipped, and that might be useful when helping debug a
customer problem.