Re: Eval Exception Error Trapping

[John P Carr <jpcarr@xxxxxxxxxxxx>]

>Hans:
>You are right that the *PSSR sucks. (you said it bro).  But it is very
useful and
>can be enhanced.  What it badly needs is a *CONTINUE in the ENDSR besides
the
>*GETIN *DETAIL etc.   This way I can deal with the error and continue with
the
>next statement without missing a beat.  The CF solution is great but aren't
we
>trying so much like basic and c that we are erasing our unique RPG ways?
(let the
>war of the languages begin ...  1 2 3  go 8-) )

Since the targets(*Cancl, *Detl, *Getin, etc) are places in the cycle
flowchart the the control branches to,   
I would rather see    *NEXT  instead of *CONTINUE.      Meaning GOTO (like
the *GETIN and the rest do)
the NEXT statement after the error happened.   That would allow us the most
control(inconjuction with Jon's 
suggestion of an E extender on the Opcode) of where the logic flow goes.


John Carr


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