Re: Eval Exception Error Trapping

[boldt@xxxxxxxxxx]

Jon wrote:
>Hans - I like the try/catch type approach in some ways but it is overkill in
>many ways. Why not simply permit the coding of the "E" extender on numeric
>operations? That way I can trap at the statement level if I wish.

On the other hand, the E extender, as currently designed, already
has serious limitations.  For example, coding E on a WRITE will
trap file exceptions, but not program exceptions.  But on other
opcodes, it does trap program exceptions.

Perhaps it is overkill, but when writing new apps, it's the only
exception handling method you need to know about.  Today, you need
to know about INFSR's, *PSSR's, error indicators, extender E, etc.
MONITOR is one easy-to-understand technique that can replace all
others.

Cheers!  Hans

Hans Boldt, ILE RPG Development, IBM Toronto Lab, boldt@ca.ibm.com


* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the RPG/400 Discussion Mailing List!  To submit a new         *
* message, send your mail to "RPG400-L@midrange.com".  To unsubscribe   *
* from this list send email to MAJORDOMO@midrange.com and specify       *
* 'unsubscribe RPG400-L' in the body of your message.  Questions should *
* be directed to the list owner / operator: david@midrange.com          *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *