public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: aoliva@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, markus@ibp.de,
	nobody@gcc.gnu.org
Subject: Re: c++/3356: Multiple inheritance from a class that has a throw() destructor doesn't compile
Date: Fri, 22 Jun 2001 23:50:00 -0000	[thread overview]
Message-ID: <20010623065009.15039.qmail@sourceware.cygnus.com> (raw)

Synopsis: Multiple inheritance from a class that has a throw() destructor doesn't compile

State-Changed-From-To: open->closed
State-Changed-By: aoliva
State-Changed-When: Fri Jun 22 23:50:09 2001
State-Changed-Why:
    So where's the bug?  An overrider of a virtual member function must have a throw() specification at least as strict as that of the overridden member function.  Consider how odd it would appear for a caller of the method thorugh a reference to the base class if the overrider could throw an exception that the overriden member function had promised not to throw.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=3356&database=gcc


                 reply	other threads:[~2001-06-22 23:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20010623065009.15039.qmail@sourceware.cygnus.com \
    --to=aoliva@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=markus@ibp.de \
    --cc=nobody@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).