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


  • Subject: RE: Open Source discussion on error handling was: RPGIII/RPG400 ERRORMONITORING
  • From: Buck Calabro <buck.calabro@xxxxxxxxxxxxxxxxx>
  • Date: Wed, 9 Feb 2000 13:39:38 -0500

Martin wrote:

>One thing to add is the general *PSSR principle of 
>using a flag to prevent it calling itself recursively.  

Yes indeed!  The code I posted does that as a "side effect" (which is not a
Good Thing - thanks for pointing it out!)  When you are in *PSSR and do an
ENDSR, control passes to the section of the compiler named in factor 2
(*DETC being perhaps the most useful place to return!)  This particular code
loads the ERRACN variable when the program initialises.  When *PSSR gets
called the first time, it does an ENDSRERRACN.  This clears the contents of
ERRACN.  If *PSSR gets tripped again, ERRACN is blank, causing the default
error handler to be invoked.

MUCH better is Martin's method of setting a "I'm already handling an error"
flag.  It explicitly lets the programmer see what the intent is, rather than
relying on an obscure side-effect.

Buck
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-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 thread ...


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.