Re: Never use GOTO (was Is this the Free-Format that we asked for?)

Actually, I don't use LEAVE and INTR that much.  In fact, when
I do use one of those I have to check the manual to see what
the command is since I use it so little.  Before I use one of
them, however, I think if it's going to help the code or to
hinder it.

But, when I see one in a program I know *exactly* where it's
going.  And why.

If someone said they were not going to allow LEAVE and INTR
in free format that would be fine with me, although those are
constructs I would prefer to remain.

Regards,

Jim Langston

Buck Calabro wrote:
> 
> Jim Langston wrote:
> 
> >I think the whole point is, 95% of the time that
> >GOTO is used it is used incorrectly!  With
> >such a failure to success rate it is much
> >better just to not use the statement at all.
> >
> >That is why I said I don't use GOTO.  Ever.
> >Period.  Not that GOTO is a bad statement,
> >but since it can be abused so easily it is
> >much simpler just not to use it.
> 
> Jim,
> I bet you use LEAVE or ITER though.
> They are also branching instructions that leave a construct before all it's
> statements are executed.  It's the early exit that's the Bad Thing, not the
> spelling of the instruction.
> 
> Buck Calabro
> Aptis; Albany, NY
> "Nothing is so firmly believed as
>  that which we least know" -- Michel Montaigne
> Visit the Midrange archives at http://www.midrange.com
+---
| 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
+---