From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ross Johnson <rpj@ise.canberra.edu.au>
To: Thomas Sailer <sailer@ife.ee.ethz.ch>
Cc: "Bossom, John" <John.Bossom@Cognos.COM>, pthreads-win32@sourceware.cygnus.com
Subject: Re: cancelling
Date: Wed, 12 Jul 2000 23:24:00 -0000
Message-id: <396D60A0.A89B833@ise.canberra.edu.au>
References: <430F887D415DD1118C2700805F31ECF1037F1263@sota0005.cognos.com> <396CAA0B.BA376CDF@ife.ee.ethz.ch>
X-SW-Source: 2000/msg00036.html

Thomas Sailer wrote:
> 
> The code currently seems to support three mechanisms:
> 
> if _MSC_VER is defined, it seems to be using SEH.
> 
> otherwise, if __cplusplus is defined, it seems to
> be using C++ EH.
> 
> otherwise, it just starts the thread without any
> exception handling.
> 
> Now the question is how the precompiled
> DLL on the net was compiled.

The precompiled DLL was built using MSVC and is using SEH.
The C++ EH is in there to support building the library
with the GNU compilers. The third option (ie. build with C
and no EH) perhaps shouldn't be there, although, provided
people are aware of the limitations could be useful to
someone.

Side note: the EH within the DLL should be self-contained
such that an application which uses the library can be
built as standard C without EH and not run into trouble.
At least that is what I've been assuming. I could be wrong.

Ross