|
Aaron, I suppose if that you are subprocedure, and subroutine, phobic and insist on one 1,000 page listing of inline code, then a leave, or iter, out of a loop that begins on page 10 and ends on page 1000 is probably just as ugly as a goto. Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com "Bartell, Aaron L. (TC)" <ALBartell@xxxxxxxxxxxxxx> Sent by: rpg400-l-bounces@xxxxxxxxxxxx 02/16/2004 03:12 PM Please respond to RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx> To "'RPG programming on the AS400 / iSeries'" <rpg400-l@xxxxxxxxxxxx> cc Fax to Subject RE: NOTO (or "no GOTO in FreeForm RPG") <jt> It is absolutely false to believe a GOTO is bad, but an ITER or LEAVE is good, in all cases by definition. At the same time, it is absolutely true that these are a matter of style, And a CONSISTENT style in ANY shop is better than inconsistent styles, but not all styles are equal. (Not saying my style is all that good, either, but nonetheless these facts are gonna be plainly self-evident to some folks.) </jt> Correct me if I am wrong, but isn't the scope of GOTO much larger than ITER and LEAVE? When you execute an ITER or LEAVE you won't be placed any further in the code than the loop you are in. If you use a GOTO you could potentially be placed anywhere in the code that can have a TAG attached. That is, IMO, what makes GOTO's bad and separates it from ITER and LEAVE. Aaron Bartell _______________________________________________ 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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.