From: Paolo Carlini <pcarlini@gmail.com>
To: Ville Voutilainen <ville.voutilainen@gmail.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Jason Merrill <jason@redhat.com>
Subject: Re: [PATCH] C++0x, implement final on classes
Date: Sat, 14 May 2011 14:35:00 -0000 [thread overview]
Message-ID: <DB615F73-1A5E-4DA5-9E46-F9D97D776398@oracle.com> (raw)
In-Reply-To: <87r582w6w7.wl%ville@ville-laptop>
... I'm wondering if wouldn't be more appropriate for the new testcase to be in /cpp0x, with a name like final.C
Paolo
next prev parent reply other threads:[~2011-05-14 7:01 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 [this message]
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
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=DB615F73-1A5E-4DA5-9E46-F9D97D776398@oracle.com \
--to=pcarlini@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=ville.voutilainen@gmail.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).