Re: Good places to use "The Cycle" in today's RPG was->Re: FW: Niftiest thing(s) you have done in RPG ILE or /FREE

I was taught structured programming in 1980 and I have never written a new
program with a GOTO, ITER or LEAVE. I consider them to be poor program
design.

Regards,

Guy
Inactive hide details for "James Perkins" <jrperkinsjr@xxxxxxxxx>"James
Perkins" <jrperkinsjr@xxxxxxxxx>

"James Perkins" To "RPG programming on the
<jrperkinsjr@xxxxxxxxx> IBM i / System i"
Sent by: <rpg400-l@xxxxxxxxxxxx>
rpg400-l-bounces@xxxxxxxxxxxx cc
Subject Re: Good places to use
01/08/2009 03:26 PM "The Cycle" in today's
RPG was->Re: FW: Niftiest
+---------------------------+ thing(s) you have done in
| Please respond to | RPG ILE or /FREE
| RPG programming on the |
| IBM i / System i |
| <rpg400-l@xxxxxxxxxxxx> |
+---------------------------+

While I agree that GOTOs are not required in cycle programs, I have
probably
only seen a handful of cycle programs that did not use them. There is
usually always some record you don't want.

Usually when I find cycle programs that do not have GOTOs, it's because
they
are some kind of work file.

Personally I find the ITER or LEAVESR can always replace a GOTO, if and
only
if it's not a cycle program ;-)

James R. Perkins

On Thu, Jan 8, 2009 at 11:50, Booth Martin <booth@xxxxxxxxxxxx> wrote:

> GOTOs have nothing to with the cycle.
>
> Also, GOTOs are pretty handy if there are no exsr, begsr, and endsr
opcodes
--

-------------------------------------------------------------------------------
The information contained in and transmitted with this e-mail may be
privileged, proprietary, confidential and protected from disclosure. No
privilege is hereby intended to be waived. This e-mail is intended only
for the person to whom it is addressed. If you are not the intended
recipient/addressee, any use of the e-mail and/or its contents, including,
but not limited to, dissemination, distribution or copying is strictly
prohibited and may be unlawful, and you must not take any action in
reliance on it. If you receive this e-mail in error, please immediately
notify the sender and delete the original message and any copies of it
from your computer system. We deny any liability for damages resulting
from the use of this e-mail by the unintended recipient, including the
recipient in error.