I'll agree with that. When I came on board at one site I found many programs that were commented in this manner with all lines commented out for changes. I remember one program in particular with over 1000 lines of code. After removing the commented out code and all of the references to ancient changes I came up with a program under 100 lines.
----- Original Message ----- From: "Jeff Schasny" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Wednesday, September 28, 2005 10:55 AM Subject: RE: [U2] Good Programming Practice Question......... I've got to disagree with this one. This is the job of your source code control system. I've seen applications which were commented in this manner over a number of years and they are almost unreadable due to the sheer volume of mod tags. -----Original Message----- [mailto:[EMAIL PROTECTED] Behalf Of Marilyn Hilb Sent: Wednesday, September 28, 2005 8:48 AM To: [email protected] Subject: RE: [U2] Good Programming Practice Question......... Two items I have thought of. 1. In addition to putting a modification tag at the top of the code with who/date/what, we also will assign a job number to the mod in addition to a No for the mod. Such as mod 01. Then throughout the code where the changes are made we put a tag such as *<<01>> start and *<<01>> end or, just a single tag at the end of the line if only one or two lines being changed. This makes the changes very easy to search for and spot should there be problems in the new code. [snip] ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
