On 29.07.2014 19:35, Rick McGuire wrote:
> No, it does NOT miss this.  The "condition" part of the syntax diagram covers 
> those situations, as
> the the statement "The RAISE instruction can raise all conditions that can be 
> trapped".  The
> syntax diagrams spells out SYNTAX, ERROR, and FAILURE as special as those 
> conditions also require
> an argument.
Hmm, I see.

---rony


> On Tue, Jul 29, 2014 at 1:25 PM, Rony G. Flatscher <rony.flatsc...@wu.ac.at
> <mailto:rony.flatsc...@wu.ac.at>> wrote:
>
>
>     On 29.07.2014 19:23, Rick McGuire wrote:
>>
>>
>>
>>     On Tue, Jul 29, 2014 at 1:11 PM, Rony G. Flatscher 
>> <rony.flatsc...@wu.ac.at
>>     <mailto:rony.flatsc...@wu.ac.at>> wrote:
>>
>>         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".
>>
>>
>>     RAISE is fully capable of raising all of those conditions. 
>     Ah, just tried it with notready and halt and they worked, super!
>
>     The documentation in rexxref.pdf misses these, I will file a 
> documentation bug.
>
>     Thanks, Rick!
>
>     ---rony
>

------------------------------------------------------------------------------
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls. 
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Reply via email to