>but, but, but,  I always get rid of old code.  Well, almost always; if I
>am not really sure of the >ramifications, I leave the old code there,
>commented out just in case...  If you've seen it in code then it >must be
>more than just me that does that?


Our company's standards -insist- that the old code be commented out and
left in place, noted with the Assigned Task Number so everyone knows when
the code was changed.

It makes some programs almost impossible to read.

This is in spite of the fact that our Change Management System tracks 5
previous versions.  Of course, this doesn't help when a program is 'fixed'
5 times the same week and flushes out all previous versions.

--Paul E Musselman
PaulMmn@ix.netcom.com


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.