Re[2]: differences between getThread () on unices and win32

[David Sugar]

We are in the process of getting GNU Common C++ 2 ready for release and I
recall some work had been done on this issue.  This has not been
transferred into CVS in Savannah yet as it started as an entirely
experimental effort, but is in sourceforge public cvs, under
cvs.cplusplus.sourceforge.net:/cvsroot/CommonC++ I believe.

On Wed, 20 Feb 2002, Pavel Tsekov wrote:

> Hello David,
>
> Just to let you know that the version I refer to is 1.9.5.
>
> Btw is there an public accessible CVS server for CommonC++ ? Or
> a web based one ?
>
> Wednesday, February 20, 2002, 1:38:10 PM, you wrote:
>
> DS> Freddy, do you think this issue is still in the 2 tree?  I recall this
> DS> was changed around a bit...
>
> DS> Pavel Tsekov wrote:
>
> >>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 :)
>
>