RE: Finding Indicators Used (was: RE: MOVEA -> EVAL)

But can you always trust the Documentation has been maintained?  :)
Got burned once under this assumptions which is why I started checking the
compile listings.  Only takes a few extra minutes and I can scan the compile
listing from the source that I am editing.
Guess it all comes back to style of coding (or CYA).



Joe Giusto II
Programmer/Analyst
Ritz Camera
Beltsville, MD
301-419-3209 x347
410-813-2812 x347

 -----Original Message-----
From:   owner-rpg400-l@midrange.com [mailto:owner-rpg400-l@midrange.com]  On
Behalf Of Jim Langston
Sent:   Monday, June 18, 2001 5:02 PM
To:     RPG400-L@midrange.com
Subject:        Re: Finding Indicators Used (was: RE: MOVEA -> EVAL)

Er, you really expect me to do this?  You expect a programmer to have
to compile your program and look at the generated code to be able to
maintain it?

What ever happened to self documenting code?  Structured Programming?
Proper documentation?

If it takes me 1 or even 5 extra lines of code to achieve all three of
these, I'm for the extra code.

"Real programmers don't eat quiche" is interesting reading, and a good
chuckle, but I have never abhered to it!

Regards,

Jim Langston

Me transmitte sursum, Caledoni!




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