|
In <199804250440.AAA000.96@unicorn.flybynight.com.au>, on 04/24/98 at 11:32 PM, "Simon Coulter" <shc@flybynight.com.au> said: LEAVESR is explicit and unambiguos. It is different than a GOTO because there is no doubt as to what is happening. There are places that I'd normally feel that a GOTO could be used, including leaving a subroutine but with LEAVESR being available then that is one less excuse to justify a GOTO. The IF tests are nice, no question about it, but putting an END seventy five or more lines away from it's IF is no big winner either, in my mind. >As for Toronto even considering a LEAVESR operation code regardless of >the small effort required to satisfy the request ... words fail me! >This 'op-code' can adequately be replaced by a GOTO and a label on the >ENDSR statement if you must use it. It is not even necessary, it can >ALWAYS be replaced by an appropriate IF test. >Whether you disagree is of >no interest to me whatsoever. None of the arguments in favour of these >operation codes has been persuavive, merely misguided. -- ----------------------------------------------------------- boothm@ibm.net ----------------------------------------------------------- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.