Hi,
no idea, hro said, this is the right thing to do.
Kind regards, pl
Stephan Bergmann wrote:
Philipp, all,
Hm, is this a (misguided, IMO) attempt at making the code more robust?
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?
Re the other checks: Is it useful to have those functions silently noop
for a non-created thread? I would guess that any code that relies on
those newly introduced checks is already in error, and should rather be
exposed and fixed rather than hidden. (Also, getIdentifier for
m_hTread==NULL confusingly returns the id of the current thread, at
least in the osl/unx branch.)
Just my 2cents/sorry for bothering,
-Stephan
--
If you give someone a program, you will frustrate them for a day;
if you teach them how to program, you will frustrate them for a lifetime.
-- Author unknown
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
