× 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. RPG400-L
  3. September 2015

Re: Coding in Column 1

Iterations make sense to me. Working with code that has 20 years of changes, all dutifully commented and annotated, swells program source to spaghetti monsters.



On 9/18/2015 2:31 PM, Vernon Hamberg wrote:
Kurt

This was a question of mine when I first looked at 9.5 - we use this
approach, and it's been around for decades.

Fortunately, there's no need to change the old stuff - this new format
is for new code only.

So if we use the 1+ way of coding, we'll need new ways (maybe old in
other languages) to indicate change, if we do it in the code. Other
languages take advantage of diffs between iterations, so no need for
marking in code itself.

To mark changes in CL has required some kind of START and END comments
with a change ID, perhaps.

A comment could be placed to the right for this kind of thing.

Other ideas? I know I don't have the market covered here.

Cheers
Vern


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.