Re: Documenting code changes

On 9/27/2013 10:54 AM, Cyndi Bradberry wrote:

Hi, In the past, we have documented at the top of the program the
date, ticket # and a description of a change. Now we are being told
to put the ticket number in the first 5 positions, copy the line we
are changing, commenting out the original line and editing the new.
In CLP, /* */ to enclose the ticket number on the line being
changed.

I don't like that technique ... the code gets WAY too cluttered with a result of being hard to read.

Personally, I perfer to have a change control system that does detailed source code archiving ... that way we can compare the various versions and what issue resulted in the change.

david
(who works for PTC, makers of the Implementerchange control system, in addition to running midrange.com)