RE: RPG Cycle (was Reinventing Code)

["Fisher, Don" <DRF@xxxxxxxxxxxxxxxx>]

I have to disagree with your first point.  The argument against the cycle
does not revolve around people not using it in the past, but against its
ease of maintenance, or lack thereof.  

I will concede that the LX indicators are not as bad as the more esoteric
features, but they are still more difficult to read and understand that "DO"
and "IF".

As for the externally described files hiding things...perhaps.  However,
they still allow the most easily maintainable code to be written.  Anyone up
for analyzing a system written entirely with internally described files?
How about modifying the format of a report that uses "O" specs? <shudder>  

The point is simply that we, as developers and managers, must create the
most maintainable and flexible code possible with the tools we have.  In my
opinion, the logic cycle simply does not provide the level of
maintainability that is required with such a transient work force.  

There is a reason why top-down structured programming techiniques are so
popular and why their associated operation codes (BEGSR, IF, DOW, DOU, CASXX
etc.) were added to the RPG language.

They work and are easily understood.

Just one man's opinion.

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


<clip>
Using this argument, we shouldn't use EVAL's, externally defined print
files, or even externally defined db files either.  Many have not used
them in the past.  And they do hide things from you.

<clip>
Have you looked at your home grown level break logic?  If it is
working, then it probably IS the cycle.  Doesn't matter if it in RPG,
COBOL, or C++.

And regarding the "hidden logic" argument, what about the logic that is
hidden from you when you use a Join file?  Or OPNQRYF, or many other
features?

Regards,
Bob Crothers
+---
| 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
+---