×
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.
And as far as that EXSR GETOUTNOW argument... that just hides the
RETURN from the maintainer more effectively. It is lazy, ugly, and
asking for trouble down the road (when the author is at some other job,
creating new problems for new followers).
It occurs to me that an EXSR from which there will, by design, be no return
is nothing more than a glorified GOTO. I would love to hear the explanation
of how that is better than RETURN, but to the point: All programmers should
be justified in their belief that the statement after EXSR will always be
executed (if the EXSR is executed, of course).
I say this from experience. AS/SET generates a subroutine (EXPGM, I think?)
from which there shall be no return. I cannot say how many times the
approach has burned me as we modernized the generated code. Not because of
the EXSR (one learns the nuance and triggers on the SR name), but because
use of that SR was also buried within other SRs. You have to understand
every line of code before you can touch one line. Proceduralization SHOULD
free you from that obligation.
Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
If you lined up all the cars in the world end to end, someone would be
stupid enough to try to pass them, five or six at a time, on a hill, in the
fog.
midrange.com
