public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/46043] attribute to mark virtual methods that can't be further overriden so they can be devirtualized
Date: Sat, 16 Oct 2010 14:01:00 -0000	[thread overview]
Message-ID: <20101016140100.Q3VL3tDcoMjusrS7hyaz04KybZi2sqZ-KP2ijP0XwX4@z> (raw)
In-Reply-To: <bug-46043-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46043

--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> 2010-10-16 14:01:25 UTC ---
(In reply to comment #0)
> One idea I could come with would be omitting the "virtual" keyword causing the
> method to lose its "virtual" status. But that would break a lot of existing
> code.

This is not acceptable.

The idea is useful in general though.  You should read
http://www.open-std.org/JTC1/SC22/WG21/docs/papers/2009/n2928.htm for related
features in C++0x


  reply	other threads:[~2010-10-16 14:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-16 12:04 [Bug c++/46043] New: " zsojka at seznam dot cz
2010-10-16 14:01 ` redi at gcc dot gnu.org [this message]
2010-10-16 15:46 ` [Bug c++/46043] " redi at gcc dot gnu.org
2010-10-16 15:50 ` zsojka at seznam dot cz
2010-10-27 22:12 ` pinskia at gcc dot gnu.org
2010-10-28  8:50 ` redi at gcc dot gnu.org
2011-07-07 22:02 ` jason at gcc dot gnu.org
2011-07-17 11:46 ` paolo.carlini at oracle dot com
2011-07-17 13:12 ` jason at gcc dot gnu.org

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=20101016140100.Q3VL3tDcoMjusrS7hyaz04KybZi2sqZ-KP2ijP0XwX4@z \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).