public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: lerdsuwa@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, jody@ifi.unizh.ch,
	nobody@gcc.gnu.org
Subject: Re: c++/6006: problem with pure virtual functions and destructord
Date: Tue, 14 May 2002 08:46:00 -0000	[thread overview]
Message-ID: <20020514154623.21750.qmail@sources.redhat.com> (raw)

Synopsis: problem with pure virtual functions and destructord

State-Changed-From-To: open->closed
State-Changed-By: lerdsuwa
State-Changed-When: Tue May 14 08:46:22 2002
State-Changed-Why:
    Not a bug.  The virtual function is treated as non-virtual
    inside destructors.  So ~A() can only call A::f() which is
    pure virtual.  Here is the relevant part of the standard
    [section 12.7 para 3]
    ... When a virtual function is called directly or indirectly
    from a constructor (including from the mem-initializer for a
    data member) or from a destructor, and the object to which
    the call applies is the object under construction or destruction,
    the function called is the one defined in the constructor or
    destructor's own class or in one of its base, but not a function
    overriding it in a class derived from the constructor or
    destructor's class, or overriding it in one of the other
    base classes of the most derived object (1.8).

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6006


             reply	other threads:[~2002-05-14 15:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-14  8:46 lerdsuwa [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-05-15  3:16 Nathan Sidwell
2002-05-15  1:46 jody
2002-03-19 10:06 jody

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=20020514154623.21750.qmail@sources.redhat.com \
    --to=lerdsuwa@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=jody@ifi.unizh.ch \
    --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).