On 11.02.2012 14:36, Rick McGuire wrote: > On Sat, Feb 11, 2012 at 8:33 AM, Rony G. Flatscher > <[email protected]> wrote: >> Am 10.02.2012 um 23:34 schrieb Rick McGuire <[email protected]>: >> >>> I'm really not sure what you're asking here. The rxffsub flag is an >>> input to the exit that merely tells you how the routine was invoked >>> (function or CALL instruction). The rxfferr and rxffnfnd flags are >>> used to raise either the invalid call to routine or function not found >>> errors and only have meaning if the exit return value is HANDLED >>> (i.e., the exit chooses to handle these, and the result is a request >>> to raise an error). >> In the case of such an error, shouldn't the handler return >> RXEXIT_RAISE_ERROR instead of RXEXIT_HANDLED? > It depends on the nature of the error. An error in the processing of > the exit itself should use RXEXIT_RAISE_ERROR, which gives an error > message that the exit failed (failure in System Service, if memory > serves). The error flags are for situations where the exit itself > functioned correctly, but it is desired to indicate an error in the > executing of the invoked function itself, with the appropriate error > raised. Thank you very much, everything is now "crystal-clear" !
---rony ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
