× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



GUY_HENZA@xxxxxxxxxxxxxx wrote:
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.

Hmm. Sounds like you were taught by a fanatical disciple of Wirth.

There is nothing inherently bad about ITER or LEAVE, provided they are
used in situations (e.g., brute-force table look-up) in which premature
exit of a loop is the norm, and completion of the loop is the exception.

--
James H. H. Lampert
Touchtone Corporation

Exactly. I also use them when there are more than one reasons to
leave a loop, and more than one reason to start at the top again.

Why have twelve nests of if/else/ends inside your do loops when you
can test/dosomething/iter, test/dosomething/iter?

Why have twelve conditions boogering up a perfectly simple do loop
when you can test/dosomething/leave?

I also like the leave/iter for exfmt processing routines:

dow 1 = 1
exfmt screen

select
when *inkc
return

when *inkl
leave

when *inkd
exsr prompt
iter

other
exsr edit

if errors
iter
end

exsr update
leave
endsl

enddo

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.