× 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.



Booth Martin wrote:

... Besides that, why have a never ending loop? I thought goto, leave, iter,
CAS**, and CAB** were all opcodes that had been disgraced and sent into
exile?

Ah, it must be friday! ;-)


First, disregarding such pedantries that there's really no such thing as a never ending loop, lots of applications are driven by a loop without any explicitly coded form of termination, and end when the operators decide to cancel them. For example, many IP servers are driven by a loop that waits on incoming requests and spins off threads to service the requests.

Second, while most recommend avoiding GOTO, CASxx, and CABxx for new code, there's absolutely nothing wrong with LEAVE and ITER. Even if you subscribe to the tenets of "structured programming", when using LEAVE or ITER, your loop still has a single entry and a single exit. By explicitly exiting a construct early, you can often avoid additional levels of nesting.

Cheers! Hans



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.