Hi Stephan, >>> Re the check in the dor: The osl_destroyThread documentation says "If >>> Thread is NULL, the function won't do anything." Why not rely on this? >> Because sometimes a thread object might be created, but never actually used? > > I guess we are talking past each other here. My point was that > osl_destroyThread is guaranteed by its documentation to noop for NULL > (so should most probably not contain some OSL_ASSERT(!NULL)), so there > is no need to wrap the call osl_destroyThread(m_hThread) in > if(m_hThread!=NULL).
Okay, I misunderstood you. And yes, I would agree here - I think osl_destroyThread shouldn't assert (in fact in the Windows version, it doesn't). Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Base http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
