public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ville Voutilainen <ville.voutilainen@gmail.com>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: Jason Merrill <jason@redhat.com>
Subject: Re: [PATCH] C++0x, implement final on classes
Date: Sun, 15 May 2011 10:25:00 -0000	[thread overview]
Message-ID: <BANLkTim4hWFrBHtUVN+z=ChDLOp-VYfvXQ@mail.gmail.com> (raw)
In-Reply-To: <4DCEC6B0.2000905@redhat.com>

On 14 May 2011 21:15, Jason Merrill <jason@redhat.com> wrote:
> On 05/14/2011 12:42 PM, Ville Voutilainen wrote:
>> Duly noted, I'll keep that in mind for subsequent ones. Is the patch
>> otherwise ok?
> Yes, and I've applied it.

Cool, thanks! I'm not quite sure whether there are ambiguities in the case
of elaborate-specifiers, but I suppose those can be fixed later. Should these
facilities be somehow flagged 0x-only? I haven't done that at all..

Somebody should probably update the C++0x status page, and refer to N3206
rather than to N2928 for explicit virtual overrides, and mark it done?

  reply	other threads:[~2011-05-14 18:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-13 20:03 Ville Voutilainen
2011-05-13 20:19 ` Jason Merrill
2011-05-13 20:24   ` Ville Voutilainen
2011-05-13 20:48     ` Jason Merrill
2011-05-14  9:50       ` Ville Voutilainen
2011-05-14 14:35         ` Paolo Carlini
2011-05-14 18:15           ` Ville Voutilainen
2011-05-14 22:50             ` Jason Merrill
2011-05-14 22:52               ` Ville Voutilainen
2011-05-15  9:35                 ` Jason Merrill
2011-05-15 10:25                   ` Ville Voutilainen [this message]
2011-05-15 14:08                     ` Jason Merrill
2011-05-15 15:43                       ` Jason Merrill

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='BANLkTim4hWFrBHtUVN+z=ChDLOp-VYfvXQ@mail.gmail.com' \
    --to=ville.voutilainen@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jason@redhat.com \
    /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).