Goo'day,
At 09:55 28/09/05 -0600, you wrote:
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.
We take the approach to keep the stamp and story at the top, but remove the
tags after a while.....
-----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/
--
No virus found in this incoming message.
Checked by AVG Anti-Virus.
Version: 7.0.344 / Virus Database: 267.11.8/113 - Release Date: 27/09/05
--
No virus found in this incoming message.
Checked by AVG Anti-Virus.
Version: 7.0.344 / Virus Database: 267.11.8/113 - Release Date: 27/09/05
Regards,
Bruce Nichol
Talon Computer Services
ALBURY NSW 2640
Australia
http://www.taloncs.com.au
Tel: +61 (0)411149636
Fax: +61 (0)260232119
If it ain't broke, fix it till it is!
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.344 / Virus Database: 267.11.8/113 - Release Date: 27/09/05
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
