I'm redundant in my prior post. Sorry. I would also suggest archiving BP UPDATE_092905 in separate file, BP.ARCHIVE for example. This way, a FIND (SEARCH) won't grab false positives when looking for a program.
I wrote an article for Spectrum on this very topic. Mark Johnson ----- Original Message ----- From: "Allen E. Elwood" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Wednesday, September 28, 2005 12:28 PM Subject: RE: [U2] Good Programming Practice Question......... > I'll second that motion. If you *really* want source control, get serious > about it and save all previous versions with dates as part of the id. Then > you can just do source compares if you need to go back a rev. > > When you get a 2300 line program, and 1700 of the lines have comments with > project numbers and permission about who said to do it, the overhead to keep > the revision history ***HARD CODED*** becomes 60% or more of the project. > Let the computer do the work for you. Instead of hard coding revisions, > keep a revision file! > > By saving the program before modifying it, it becomes 0.01% overhead, and > a.fish.in.sea is the name of the game. Since I end up going back a > revision, about once out of every 1500 programs I change, I don't think it's > a great idea to obfuscate the code with "Joe said this was ok 02-02-88" when > "Joe" worked for the company 15 years ago and nobody even remembers who he > was. > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Jeff Schasny > Sent: Wednesday, September 28, 2005 08:56 > To: [email protected] > 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/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
