There is no such Rexx thread id concept in the interpreter, and given how threads function inside the interpreter, I don't see that it would make much sense to add this.
Rick On Sun, Sep 27, 2009 at 7:41 AM, Rony G. Flatscher <rony.flatsc...@wu-wien.ac.at> wrote: > > Rick McGuire wrote: > > On Sun, Sep 27, 2009 at 6:18 AM, Rony G. Flatscher > <rony.flatsc...@wu-wien.ac.at> wrote: > > > Just a question: if issuing AttachThread() multiple times for the same > thread, would the same thread context pointer be returned or a new one > constructed each time? > > > It creates a new thread context each time. > > > Thanks. > > Is the Rexx instance maintaining any thread-related data as long as a > Rexx thread exists at all? > > > Not sure what you're asking here. > > > Is there a means to query some sort of an id which would be unique for each > Rexx thread at runtime? Such that the same id would be returned by different > Rexx thread contexts returned by AttachThread(), if it was the same Rexx > thread one attaches to? > > Then, if a new Rexx thread gets created (and by chance using the same > operating system thread) that would have a different unique id that one can > query at runtime? If each Rexx thread had a unique id, that does not get > reused, then maybe it even becomes possible to learn whether a particular > Rexx thread exists or or not (e.g. has died in the meantime.) > > If such a means (to uniquely identify each Rexx thread) was available, it > would become possible to create and maintain Rexx thread dependent > application data and as long as a Rexx thread keeps on running that thread > related app data could be maintained/used for thread management (e.g. in the > BSF4Rexx case the bridge between Rexx threads and Java threads, allowing one > to maintain established point-to-point relationships). > > ---rony > > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register now! > http://p.sf.net/sfu/devconf > _______________________________________________ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
