From: Mark Mitchell <mark@codesourcery.com>
To: Richard Henderson <rth@redhat.com>
Cc: Jason Merrill <jason@redhat.com>,
Alexandre Oliva <aoliva@redhat.com>, Mike Stump <mrs@apple.com>,
gcc@gcc.gnu.org
Subject: Re: __attribute__((cleanup(function)) versus try/finally
Date: Tue, 13 May 2003 21:41:00 -0000 [thread overview]
Message-ID: <1052862018.4181.418.camel@doubledemon.codesourcery.com> (raw)
In-Reply-To: <20030513211938.GC8273@redhat.com>
On Tue, 2003-05-13 at 14:19, Richard Henderson wrote:
> On Tue, May 13, 2003 at 02:06:50PM -0700, Mark Mitchell wrote:
> > In any case, there are some semantics to be defined; if a cleanup throws
> > an exception, what happens?
>
> At present, the old exception doesn't get destroyed, and
> the new exception propagates. I'm not really sure *what*
> should be said except that it's undefined behaviour.
That's perhaps acceptable; "undefined behavior" is at least an
affirmative non-specification.
Calling "abort" would seem to be the C-ish equivalent of the C++
std::terminate.
--
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com
next prev parent reply other threads:[~2003-05-13 21:41 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.BSF.4.55.0305061457450.57349@acrux.dbai.tuwien.ac.at>
[not found] ` <1052245742.2583.315.camel@doubledemon.codesourcery.com>
[not found] ` <wvlissnc2e3.fsf@prospero.boston.redhat.com>
[not found] ` <1052249890.31850.338.camel@doubledemon.codesourcery.com>
2003-05-06 21:04 ` Jason Merrill
2003-05-06 21:24 ` Mark Mitchell
2003-05-07 21:21 ` Jason Merrill
2003-05-07 22:18 ` Mark Mitchell
2003-05-07 23:01 ` Jason Merrill
2003-05-08 12:05 ` Gabriel Dos Reis
2003-05-09 5:46 ` Kai Henningsen
2003-05-06 21:52 ` Anthony Green
2003-05-08 17:44 ` Mike Stump
2003-05-08 17:45 ` Jason Merrill
2003-05-08 18:40 ` Mark Mitchell
2003-05-08 19:06 ` Alexandre Oliva
2003-05-08 19:47 ` Mark Mitchell
2003-05-08 20:19 ` Alexandre Oliva
2003-05-08 21:18 ` Jason Merrill
2003-05-13 21:10 ` Mark Mitchell
2003-05-13 21:25 ` Richard Henderson
2003-05-13 21:41 ` Mark Mitchell [this message]
2003-05-13 22:16 ` Richard Henderson
2003-05-13 21:31 ` Gabriel Dos Reis
2003-05-15 17:00 ` Jason Merrill
2003-05-15 17:23 ` Mark Mitchell
2003-05-09 19:41 ` Kai Henningsen
2003-05-08 19:37 ` Jason Merrill
2003-05-07 0:14 ` Richard Henderson
2003-05-07 2:32 ` Mark Mitchell
2003-05-13 21:33 Richard Kenner
2003-05-13 22:11 ` Richard Henderson
-- strict thread matches above, loose matches on Subject: below --
2003-05-09 9:54 Ranjit Mathew
2003-05-09 10:16 ` Andrew Haley
2003-05-09 12:08 ` Fergus Henderson
2003-05-09 12:49 ` Jamie Lokier
2003-05-09 9:23 Ranjit Mathew
2003-05-09 9:31 ` Andrew Haley
2003-05-08 7:49 Ranjit Mathew
2003-05-08 21:21 ` Richard Henderson
2003-05-07 10:18 Ranjit Mathew
2003-05-07 13:54 ` Jason Merrill
2003-05-07 18:23 ` Richard Henderson
2003-05-08 18:02 ` Mike Stump
2003-05-06 19:56 Jason Merrill
2003-05-08 11:59 ` Gabriel Dos Reis
2003-05-08 15:02 ` Jason Merrill
2003-05-08 18:30 ` Mike Stump
2003-05-08 20:49 ` Richard Henderson
2003-05-08 22:29 ` Mike Stump
2003-05-13 0:07 ` Geoff Keating
2003-05-13 21:27 ` Richard Henderson
2003-05-14 1:14 ` Geoff Keating
2003-05-14 7:41 ` Richard Henderson
2003-05-14 21:11 ` Geoff Keating
2003-05-14 22:20 ` Richard Henderson
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=1052862018.4181.418.camel@doubledemon.codesourcery.com \
--to=mark@codesourcery.com \
--cc=aoliva@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=mrs@apple.com \
--cc=rth@redhat.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).