Going back in time, the problem with 'goto' evolved with the lack of
discipline and structure in written program code.
The quick and easy escape from complex code often made modification and
debugging difficult and time consuming.
Reading through complex code resembled untangling spaghetti (spaghetti
code).
With the evolution of structured code, the 'goto' was effectively outlawed,
even though the operation still existed.
Norm Dennis
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Dave
Sent: Monday, 10 September 2012 7:19 PM
To: RPG programming on the IBM i / System i
Subject: GOTO in free form!
Found this in an rpg program :
A programme reads a primary file then does :
/free
if ..; //error detected
doErrorstuff;
/END-FREE
C GOTO FIN
/FREE
endif;
/end-free
The same is repeated wherever an error may occur.
What's wrong with this, apart from being ugly code? I was told that a GOTO
indicates poor analysis.
What's different with using a DO loop with ITER or LEAVE, a SUBR with
LEAVESR?
--
This is the RPG programming on the IBM i / System i (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.
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2012.0.2197 / Virus Database: 2437/5258 - Release Date: 09/09/12
midrange.com
