While testing redirecting command exit handlers one test program causes intentionally a failure condition to be raised in the RexxExitContext which gets trapped with a "signal on any name someLabel" in the invoking context upon return from the handler.

From then on whenever a new "signal on any name someNextLabel" is stated before invoking the command handler again (without causing any new condition in it) will cause upon return the transfer to "someNextLabel" and supplies as the condition object with condition('o') the condition information of the previous condition.

Is it possible that the condition that got raised in the RexxExitContext is not cleared before the next invocation of the command handler such that upon return it gets triggered again if a new "signal on any" is in effect?

---rony



_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Reply via email to