RE: RPGIV: RPGIII to get a facelift?

I've a professor once told all the students that if he see a goto statement in 
the program, he/she will automatically get a "D" on the assignment.

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Tony Carolla
Sent: Sunday, December 26, 2004 1:00 PM
To: RPG programming on the AS400 / iSeries
Subject: Re: RPGIV: RPGIII to get a facelift?


On Tue, 26 Oct 2004 02:14:42 -0500, Reeve <rfritchman@xxxxxxxxx> wrote:
> ... but the lack of a free-form
> GOTO/TAG is a burr under my coding saddle.  

You know, I have wrestled with that very fact, and started to come to
the conclusion that some people just take this 'structured' approach
too far.  But soon after, I started to see the whole picture.  Alot of
times, when I was so tempted to use a TAG/GOTO pair, I realized that
instead of 'parachuting' into a section of code, I should have created
subprocedures out of the two chunks of code that I was jumping
between, and handled their functions as modules of code, then there
would be no need for the jumps.

The only times I really think a TAG/GOTO is when you present a screen
to a user, and you want to re-display if they made an error (user? 
error?  nahh...), to show them their error, turn on an indicator and
... uh... GOTO?

In these cases, I usually code a DOU loop that the user falls out of
if they happen to get the screen parameters correct.

-- 
"Enter any 11-digit prime number to continue..."
-- 
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.