Uli,
On 28.02.2011 14:55, u.zinngr...@inter.nl.net wrote:
When I run a Rexx script through BSF4ooRexx, it seems that streams that
are opened in a script are not closed when the Rexx interpreter is
finished executing the script.
This code demonstrates the problem:
import org.apache.bsf.*;
Hi
Currently, we don't have a uniform way to get the current thread id from a
rexx script.
Under Windows : SysQueryProcess(TID)
if (stricmp(option, TID) == 0)
{
return context-WholeNumber(GetCurrentThreadId());
}
Under Unix : Sysgettid()
pthread_t tid = pthread_self();
On Sat, Mar 5, 2011 at 11:45 AM, Jean-Louis Faucher
jfaucher...@gmail.com wrote:
Currently, we don't have a uniform way to get the current thread id from a
rexx script.
Jean-Louis, I'm not actively apposed to this, but I'm not keen on it either.
I would rather see any future work take the
2011/3/5 Rick McGuire object.r...@gmail.com
I guess I'd need to know a reason. If the purpose is to somehow map
this back to the Rexx thread, then I'm not comfortable with exposing a
system-specific concept such as a thread id to any ooRexx construct.
The issue of Rexx thread identifiers
Ok, I'm definitely -1 on adding this then. First of all, you're only
adding this for Unix systems, but working on adding a facility that is
generally useful. This is exactly the sort of usage I'm against.
A better approach would be to define an ooRexx thread object that
provides different
Generally, it would be good to open an RFE for the specific item you
wish to implement. It would be fine to include the function of having
a threadlocal as part of that RFE and close both once they are
implemented.
For something of this scope, I think you need to write the
documentation (or at
