Re: [Oorexx-devel] RXOFNC/RXEXF vs. RXFNC when setting flags and returning

[Rony G. F. <Ron...@wu...>]

On 21.02.2012 20:48, Rony G. Flatscher wrote:
> The "classic Rexx" exit RXFNC will raise a Rexx condition, if the handler either sets the "rxfferr"
> ("invaliid call to routine") or the rxffnfnd ("function not found") flag and returns with
> RXEXIT_HANDLED.
>
> Doing the same in the "ooRexx-supported"  RXOFNC/RXEXF handlers does not raise the Rexx condition
> upon return, rather one has to return RXEXIT_RAISE_ERROR for that.
>
> Should the behaviour be the same among the three or is it intentional that the "ooRexx" exits behave
> here differently than the "classic Rexx" exit?
O.K. with further research, I think it is a bug with RXOFNC/RXEXF, because if returning
RXEXIT_RAISE_ERROR the handler's flags are not really respected and the Rexx condition that gets
raised is: "Failure in system service: RXEXF" etc.

So I will file this as a bug with the bug tracker.

---rony