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 [thread overview]
Message-ID: <396D60A0.A89B833@ise.canberra.edu.au> (raw)
In-Reply-To: <396CAA0B.BA376CDF@ife.ee.ethz.ch>
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
next prev parent reply other threads:[~2000-07-12 23:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-12 7:34 cancelling Bossom, John
2000-07-12 8:44 ` cancelling Lorin Hochstein
2000-07-12 10:25 ` cancelling Thomas Sailer
2000-07-12 23:24 ` Ross Johnson [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-07-10 9:35 cancelling Bossom, John
2000-07-12 4:21 ` cancelling Thomas Sailer
2000-07-10 8:55 cancelling Thomas Sailer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=396D60A0.A89B833@ise.canberra.edu.au \
--to=rpj@ise.canberra.edu.au \
--cc=John.Bossom@Cognos.COM \
--cc=pthreads-win32@sourceware.cygnus.com \
--cc=sailer@ife.ee.ethz.ch \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).