Re: Left hand indicators (was Re: DOW vs DOU)

[John Carr <74711.77@xxxxxxxxxxxxxx>]

Message text written by "Kahn, David"
>
John,

Why not simply code *IN50 in the comment area, or if you prefer not to use 
that area code a comment line such as

     C*     Next line uses *IN50, *IN51, *IN67

Dave Kahn - Tengizchevroil, Kazakstan<

David:
As a matter of fact,  I do use the comment area on the right of each C-spec for
that type of thing also in addition to describing what the code is doing.   For
example, I use *in90-*in99 as error indicators (maybe even 80-99) for screen
DSPATR(RI,PC) etc.  and I turn them all off in the mainline via MOVEA  *OFF
*IN,90 (using correct syntax)  and since that will not be found using scan,  I
code comments on right to catch it(Reset *IN90-*IN99) .  However this is the
shop standard and EVERYONE does it the same way.  In that type of
environment(with Real Standards & Conventions)  you can get down to
understanding WHAT the code is doing VERY quickly by not having to focus on HOW
its doing it.  Indicators , subroutine names, etc. etc. are the same in EVERY
program.  This is ONLY way that 2 guys could write a whole shop floor package in
9 months by being able to clone with impunity and not get hurt.  ( BTW thats one
of the things my software package offers)

As a comment on Structured Code,  I believe that structured code IS the
Simplest, Clearest, and most importantly  MOST MAINTAINABLE by the next guy/gal.


Remember what seems like the hard way is usually in the long run the simplest.
Code thats thrown together while worrying about speed,  seems the quickest to
write,  but after 2-10 modifications and enhancements it runs like a dog and
people draw straws to maintain it. 

Those are my opinions,  But I probably wrong

John P. Carr  CDP
EdgeTech
74711.77@compuserve.com    804-739-7689

BTW   Askerisks in position 7 (commented out code) is the other thing we cut the
hands off a programmer for.  If it doesn't run,  It's not in there.  Get a
better archiving/version control mechanism.

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the Midrange System Mailing List!  To submit a new message,   *
* send your mail to "MIDRANGE-L@midrange.com".  To unsubscribe from     *
* this list send email to MAJORDOMO@midrange.com and specify            *
* 'unsubscribe MIDRANGE-L' in the body of your message.  Questions      *
* should be directed to the list owner / operator: david@midrange.com   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *