From: "Assinovsky, Lev" <LAssinovsky@algorithm.aelita.com>
To: "Assinovsky, Lev" <LAssinovsky@algorithm.aelita.com>,
"Eljay Love-Jensen" <eljay@adobe.com>, <gcc-help@gcc.gnu.org>
Subject: RE: Great g++ bug! Local destructor isn't called!
Date: Thu, 11 Mar 2004 21:37:00 -0000 [thread overview]
Message-ID: <3F6F4712B759A34ABD453A8B39C10D6201F2CB64@bagman.edm.com> (raw)
Sorry for mistyping in my previous message.
Right text is:
The bug is NOT shown up if
an exception spec of exception raiser exactly matches
an exception spec of the virtual function.
----
Lev Assinovsky
Aelita Software Corporation
O&S InTrust Framework Division, Team Leader
ICQ# 165072909
> -----Original Message-----
> From: Assinovsky, Lev
> Sent: Thursday, March 11, 2004 1:43 PM
> To: Eljay Love-Jensen; gcc-help@gcc.gnu.org
> Subject: RE: Great g++ bug! Local destructor isn't called!
>
>
> If to compile with -fno-enforce-eh-specs my testcase works.
> Actually that's very natural. The bug is shown up if
> an exception spec of exception raiser exactly matches
> an exception spec of the virtual function.
>
> ----
> Lev Assinovsky
> Aelita Software Corporation
> O&S InTrust Framework Division, Team Leader
> ICQ# 165072909
>
>
> > -----Original Message-----
> > From: Eljay Love-Jensen [mailto:eljay@adobe.com]
> > Sent: Wednesday, March 10, 2004 5:46 PM
> > To: Assinovsky, Lev; gcc-help@gcc.gnu.org
> > Subject: Re: Great g++ bug! Local destructor isn't called!
> >
> >
> > Hi Lev,
> >
> > I notice that if the throw(int) specification is taken off
> the Raiser
> > constructor, then the ~Object() is called with -O3.
> >
> > (I'm using GCC 3.3.1 on CygWin / Windows XP.)
> >
> > Very odd. Good catch. Have you filed a bug?
> >
> > 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.)
> >
> > If C++ did exception specifications like how Java does them,
> > then that'd be
> > a different story.
> >
> > --Eljay
> >
> >
>
next reply other threads:[~2004-03-11 11:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-11 21:37 Assinovsky, Lev [this message]
-- strict thread matches above, loose matches on Subject: below --
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 16:02 Moore, Mathew L
2004-03-10 16:49 ` Momchil Velikov
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=3F6F4712B759A34ABD453A8B39C10D6201F2CB64@bagman.edm.com \
--to=lassinovsky@algorithm.aelita.com \
--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).