From: Momchil Velikov <velco@fadata.bg>
To: "Moore, Mathew L" <MooreML@BATTELLE.ORG>
Cc: Eljay Love-Jensen <eljay@adobe.com>, gcc-help@gcc.gnu.org
Subject: Re: Great g++ bug! Local destructor isn't called!
Date: Wed, 10 Mar 2004 16:49:00 -0000 [thread overview]
Message-ID: <877jxslm92.fsf@freon.briz.fadata.bg> (raw)
In-Reply-To: <D0DB062F3B1EE24E8A171F220FF12BDEFE4970@ws-bco-mse4.milky-way.battelle.org>
>>>>> "Moore" == Moore, Mathew L <MooreML@BATTELLE.ORG> writes:
Moore> <snip>
>> BTW, in general, I've found that it's usually best NOT to put
>> in throw
>> specifications for functions / methods. Ever. (This
>> restriction does not
>> apply to putting in the "throw() -- I throw nothing, ever"
>> specification. But even that should be used with great caution.)
>>
Moore> Just out of curiosity, what is the reasoning for this? Is this for g++
Moore> specifically, or C++ in general?
It must intercept thrown exceptiions and call ``unexpected()'' if
they do not match the specification. Pure overhead.
Including ``throw()''.
~velco
next prev parent reply other threads:[~2004-03-10 16:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-10 16:02 Moore, Mathew L
2004-03-10 16:49 ` Momchil Velikov [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-11 21:37 Assinovsky, Lev
2004-03-11 18:20 Assinovsky, Lev
2004-03-10 19:49 Martin York
2004-03-10 18:34 Eljay Love-Jensen
2004-03-10 15:59 Assinovsky, Lev
2004-03-10 15:38 Assinovsky, Lev
2004-03-10 14:52 Assinovsky, Lev
2004-03-10 15:23 ` Eljay Love-Jensen
2004-03-10 15:57 ` Tony Wetmore
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=877jxslm92.fsf@freon.briz.fadata.bg \
--to=velco@fadata.bg \
--cc=MooreML@BATTELLE.ORG \
--cc=eljay@adobe.com \
--cc=gcc-help@gcc.gnu.org \
/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).