Re: Eval Exception Error Trapping

[boldt@xxxxxxxxxx]

John Hall wrote:
>The monitor statements also need to have the capability of being nested.
>
>CF      Monitor
>Cf         Read SCREEN1
>CF         Monitor
>CF             Amount = price/per * qty
>CF         on-error
>CF            Monitor
>CF               Amount = price * qty
>CF            on-error
>CF               Amount = 0
>CF            endmo
>CF         endMon
>CF         Update PurchOrd
>CF      on-error
>CF         write SCreenErr
>CF      endmon
>
>note: the above code is intended as as example only and does not
>necessarily represent any logical way of doing anything useful.

Oh, it was a very useful example.  It prompted me to try out
something similar, and it resulted in an infinite loop!  The
bug has been reported to the developer.  Oh well, we still
have a lot of work to do.

Yes, working properly, nesting should be allowed.

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          *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *