While doing the housework in my notes, I retrieved this post from Rick :
http://sourceforge.net/mailarchive/forum.php?thread_name=33bd05330711150446l30ee70b2m43978a99e5426068%40mail.gmail.com&forum_name=oorexx-devel
Not needed for the current work on oodialog documentation, but could be
useful in
2011/8/6 Rony G. Flatscher
> **
>
> 0 is not a good value for threadid (I saw this value in one of your next
> mails).
>
>
> Did use hat particular value, because of the documentation of "10.10.1.1.1.
> Parameters" in rexxpg.pdf:
>
> ah, yes, I didn't read this part of the doc...
It seems that Re
On 06.08.2011 12:23, Jean-Louis Faucher wrote:
> Could it be what you need ?
>
> context->Halt
> Raise a HALT condition on all threads associated with the interpreter
> instance
*YES*, thank you very much, Jean-Louis !
(Haven't seen the forest for the trees anymore...)
---rony
On 06.08.2011 12:22, Jean-Louis Faucher wrote:
> I see two reasons to return RXARI_NOT_FOUND from RexxSetHalt :
> either the interpreter is not started (not your case)
> or the threadid parameter is not registered with a RexxActivity
> (the procid parameter is not used)
>
> 0 is not a good value f
Could it be what you need ?
context->Halt
Raise a HALT condition on all threads associated with the interpreter
instance
Jean-Louis
2011/8/3 Rony G. Flatscher
> **
> The aforementioned Rexx server use case can be changed to be ended: if one
> ends the main thread (by not issuing a SysSleep() o
I see two reasons to return RXARI_NOT_FOUND from RexxSetHalt :
either the interpreter is not started (not your case)
or the threadid parameter is not registered with a RexxActivity
(the procid parameter is not used)
0 is not a good value for threadid (I saw this value in one of your next
mails).
