differences between getThread () on unices and win32

[Pavel Tsekov]

Hello, there! :)

getThread () on Win32 seem to not follow the trend and looks a
little bit outdated. It uses the old implementation - its the same
as in 1.6.x perhaps even before that. Would a patch be required to
add this functionality or not ? I would vote for simply copying the
unix implementation without the fix for Solaris... Is this acceptable
? If a a patch is required I'd supply one...

For the curious I've found this difference because of SEGV caused
by getException () which calls getThread () to retrieve the _throw
thread artifact on a thread other than the main one. Now I am curios
is it acceptable to remove the _throw member from thread and make it
a thread data ? This involves patching get/setException... Please, let
me know - I am willing to provide the patches - just want to know
if there are any pros / cons on this topic. I think a common situation
where this will be a better solution is applications which do not use
CommonC++ for their threading purposes.

Thanks :)