From: Rony G. F. <Ron...@wu...> - 2014-07-29 17:12:32
|
Currently, I am looking deeper into the RAISE keyword instruction. The reason being, that conditions trapped in a parallel thread (let us say #2) should be re-raised in the (blocked) thread (let us say #1) that spun off the execution on a separate thread. It has been possible to secure the condition object in the parallel thread #2 and upon return (guarded wait) it is necessary to (re-)raise that very same condition in thread #1 in the context of that method that caused the execution in a parallel thread. The easiest way to do that would be to enhance the RAISE keyword instruction to accept a condition object which carries all information that should be used to re-raise the condition like: "RAISE CONDITION condObj", where condObj is a condition object directory (perhaps from ooRexx). [Something with the semantics of "raise propagate".] Short of that possibility I started out to analyze the condition object for all conditions that can be trapped in ooRexx 4.2.0. Unfortunately the current RAISE keyword instruction does not allow for RAISing all trappable the conditions, notabene the conditions: "halt", "lostdigits", "nomethod", "nostring", "notready", "novalue". Is there any workaround to still become able to (re-)RAISE all possible conditions in 4.2.0? If none, should I enter a RFE? ---rony |