Re: Eval Exception Error Trapping

[Dave Mahadevan <mahadevan@xxxxxxxx>]

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

boldt@ca.ibm.com wrote:

> Joe wrote:
>
> As someone already mentioned, you can use the *PSSR.  But that
> solution, frankly, (hmmm, what's the right word?) sucks.  You
> need to code TAGs and GOTOs, and if you want to handle exceptions
> in several places, things start to look ugly fast.  Unfortunately,
> at the moment, that's the best solution available.

--
Thank You.

Regards

Dave Mahadevan.. mailto:mahadevan@fuse.net


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