× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. September 2013

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)




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.