From: "Scott McCaskill" <scott@3dfx.com>
To: <pthreads-win32@sourceware.cygnus.com>
Subject: Re: #define catch?
Date: Wed, 02 Aug 2000 09:50:00 -0000 [thread overview]
Message-ID: <030101bffca1$b107dd00$84011e0a@3dfx.com> (raw)
In-Reply-To: <430F887D415DD1118C2700805F31ECF1037F129B@sota0005.cognos.com>
----- Original Message -----
From: "Bossom, John" <John.Bossom@Cognos.COM>
To: "'Ross Johnson'" <rpj@ise.canberra.edu.au>; "Scott McCaskill"
<scott@3dfx.com>
Cc: <pthreads-win32@sourceware.cygnus.com>
Sent: Wednesday, August 02, 2000 10:42 AM
Subject: RE: #define catch?
> "catch" is actually a keyword in C++...
>
This is true.. but I don't see what you're getting at. The fundamental
problem I encountered is that this (legal) code:
catch ( app_exception ) { }
catch ( some_other_app_exception ) { }
..will be expanded to the following when using the macro in pthread.h:
catch ( Pthread_exception_cancel ) { throw; }
catch ( Pthread_exception_exit ) { throw; }
catch ( app_exception ) { }
catch ( Pthread_exception_cancel ) { throw; }
catch ( Pthread_exception_exit ) { throw; }
catch ( some_other_app_exception ) { }
..and VC++ will not compile that because of the existence of multiple
handlers for Pthread_exception_cancel and Pthread_exception_exit.
next prev parent reply other threads:[~2000-08-02 9:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-02 8:42 Bossom, John
2000-08-02 9:50 ` Scott McCaskill [this message]
2000-08-03 9:11 ` Followup -- " Scott McCaskill
2000-08-03 20:14 ` Ross Johnson
-- strict thread matches above, loose matches on Subject: below --
2000-08-01 10:27 Scott McCaskill
2000-08-01 23:27 ` Ross Johnson
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='030101bffca1$b107dd00$84011e0a@3dfx.com' \
--to=scott@3dfx.com \
--cc=pthreads-win32@sourceware.cygnus.com \
/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).