RE: General purpose "level break" logic for RPG.

Amen.

We as developers need to remember that coding ease is NOT the sole
objective.  There is a thing called maintainability we must keep in mind
when writing code.

I don't have any problems reading code that uses "DO" and "IF" statements
for level and control breaks, but a program that uses the logic cycle,
especially the more obscure "features" such as record address files and
matching records, sends me scurrying for books and manuals.


When I see one of these programs, I take pity on those that may come after
me and rewrite it.  In my opinion, logic that can be seen is better than
that which cannot.

Donald R. Fisher, III
Project Leader
Heilig-Meyers Furniture Company
(804) 784-7500 ext. 2124
Don.Fisher@HeiligMeyers.com


-----Original Message-----
<clip> the cycle is
invisible logic...and requires more effort to remember when it does
what...vs logic
that you can see in the code.

I've worked with many monolithic RPG II report programs...after they have
been
around awhile...patched, modified, cloned, changed from just reports to
progams
that report and output and update...etc...they are total hell to maintain.

Don't get me started....  ;>

+---
| 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
+---