• Subject: Commenting Code Was ->(Re: IBM pushing Java)
  • From: "Jeffrey Silberberg" <jsilberberg@xxxxxxxxxxxxxx>
  • Date: Wed, 31 Mar 1999 10:10:49 -0500


Okay,

        Just a quick jump in here.  When I have to remove large blocks of
code, rather than comment them, I rename the subroutine, to oldnnn, add and
exsr within my *INLR IFNE *INLR condition, and the rewrite the subroutine
with all the new code.  Of course I tend to write in subroutines with very
minimal mainlines so this makes this method of coding easy.  Old routines
stay active for 1 iteration of the code, then the whole routine gets
commented intact, so the next programmer can easily see what it did verses
what it does, and can even back out the changes by updating the exsr
statements.

        An yes I also code C and C++ so I am very use to putting as much
logic as possible into functions/subroutines, and keeping a though/function
to a single screen full of code.

        JMS...


-----Original Message-----
From: Larry Bolhuis <lbolhui@ibm.net>
To: MIDRANGE-L@midrange.com <MIDRANGE-L@midrange.com>
Date: Wednesday, March 31, 1999 9:03 AM
Subject: Re: IBM pushing Java


>> Our company's standards -insist- that the old code be commented out and
>> left in place, noted with the Assigned Task Number so everyone knows when
>> the code was changed.
>>
>> It makes some programs almost impossible to read.
>
>  I have a customer who is a blind programmer.  He has a laptop that reads
the
>screens to him.    Have someone read you a 20 line RPG subroutine where 15
of
>them are commented out (be sure to have them read the entire line even with
'*'
>in column 7) and see if YOU can say what the subroutine does!  If for no
one
>else but him,  I no longer leave code commented out in my programs.
>
>  - Larry
>
>--
>Larry Bolhuis         |
>Arbor Solutions, Inc  | Two rules to success in life:
>(616) 451-2500        | 1. Never tell people everything you know.
>lbolhui@ibm.net       |
>+---
>| This is the Midrange System Mailing List!
>| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
>| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
>| To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
>| Questions should be directed to the list owner/operator:
david@midrange.com
>+---

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].