The following scenario (a Rexx object running in the role of a server):
* a Rexx program gets started, serving as a server, dispatching
messages from clients
o creates a message loop on a separate thread, dispatching
messages from client
* either "calls SysSleep(someTime)" or does "parse pull x" to keep
the Rexx program alive
Now, whenever a syntax error occurs while a Rexx message gets dispatched
on the message loop thread (maybe even on another thread), it is not
noticed by the main thread, it seems.
In the message loop thread the Rexx condition causes it to be stopped
and the message-loop thread goes away.
However the main Rexx thread (either in "SysSleep()" or "parse pull x")
keeps on running, it seems.
As reported in a previous message, "RexxSetHalt(processId,0)" returns
"1" and does not work for ending all Rexx threads from the message loop
thread, which knows that the state of the Rexx server application has
become unstable, because of the syntax error that occurred on one of its
dispatches.
---
How is one able to end the threads of a Rexx interpreter instance?
---rony
------------------------------------------------------------------------------
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
The must-attend event for mobile developers. Connect with experts.
Get tools for creating Super Apps. See the latest technologies.
Sessions, hands-on labs, demos & much more. Register early & save!
http://p.sf.net/sfu/rim-blackberry-1
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
