|
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?
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
