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



Back in the day, when we found a serious error in a program such as a
missing config record, we would set on *INH1 and return. We didn't care
about exiting gracefully. We just wanted it to DIE immediately. Typically
these errors were so rare, that it wasn't worth the time to build the logic
for a graceful exit. When we got the H1, we would look at the code to see
why.



Now that we are using procedures instead of subroutines, the "return" just
exits the current procedure and returns to the calling procedure. It does
not exist the program. Consequently, the calling procedure doesn't know
that there was an error and it keeps running.



I know *INH1 is old school but it served the purpose. One of my work
arounds for this was to force a div by 0 as in var = var / (var - var) but
I have gotten some grief for that lately. What is the acceptable
replacement for this logic when using procedures? Again, we don't care
about a graceful exit. We only care that the program stops when it needs
to.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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

This mailing list archive is Copyright 1997-2023 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.