in reply to Commented out production code?

I'm in the process of finishing up a project that generates a PDF on the fly. There are various diagnostic bits for PDFs that I'd like to keep -- if I have to dig through the PDFLib docs again it'll take me hours as compared to minutes to do 'that thing' again.

I also leave a few useful debug messages in suitable places (I always use __LINE__ to mark where they are), commented out, but ready if I have to go digging again.

I may also leave old versions of statements lying around in case (this never happens, heh heh) the user changes their mind and wants to go back to the old way of doing things.

Now if you're talking about code that's been rewritten, go ahead and delete it swhen it's not longer relevant.

But if there's stuff that is/was relevant, comment it out and leave it.

So, my vote is, 'keep that stuff!'

"Excellent. Release the hounds." -- Monty Burns.
T. Alex Beamish, TAB Software -- Toronto, Ontario