Re: [osg-users] Error in OpenThreads::ReentrantLock ???

2007-07-27 Thread Robert Osfield
On 7/27/07, Thibault Genessay <[EMAIL PROTECTED]> wrote: > Robert, do you see any objection if the implementation of the thread ID > mechanism is delegated to the underlying threading system, through the > adequate functions ? > > I could submit the pthreads and Win32 implementations, but I don't k

Re: [osg-users] Error in OpenThreads::ReentrantLock ???

2007-07-27 Thread Thibault Genessay
Hi guys, On 7/27/07, Schmidt, Richard, SDGE1 <[EMAIL PROTECTED]> wrote: > > Introduce a > > static int Thread::getCurrentThreadId() which is implemented on Win32 > with > >inline static DWORD getCurrentThreadId () { > return GetCurrentThreadId(); > } > > On other systems, i don't kno

Re: [osg-users] Error in OpenThreads::ReentrantLock ???

2007-07-26 Thread Schmidt, Richard, SDGE1
Introduce a static int Thread::getCurrentThreadId() which is implemented on Win32 with inline static DWORD getCurrentThreadId () { return GetCurrentThreadId(); } On other systems, i don't know the implementation, however there should be one. Richard Hi Richard, Well if you c

Re: [osg-users] Error in OpenThreads::ReentrantLock ???

2007-07-26 Thread Robert Osfield
Hi Richard, Well if you can think of better solution for the ReentrantMutex feel free to suggest one ;-) Robert. On 7/26/07, Schmidt, Richard, SDGE1 <[EMAIL PROTECTED]> wrote: > > > > > Hi, > > I am not quite sure about the internals of OpenThreads, but ReentrantMutex > uses a function of „Curre

[osg-users] Error in OpenThreads::ReentrantLock ???

2007-07-26 Thread Schmidt, Richard, SDGE1
Hi, I am not quite sure about the internals of OpenThreads, but ReentrantMutex uses a function of "CurrentThread" which returns the current OpenThread. However, if the current thread isn't an OpenThread, it seems to return NULL. So if you are using the ReentrantMutex with multiple other Non-Op