From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: Ville Voutilainen <ville.voutilainen@gmail.com>
Cc: gcc-patches@gcc.gnu.org, jason@redhat.com
Subject: Re: [PATCH] C++0x, teach the parser to parse virt-specifier-seq for member functions
Date: Mon, 25 Apr 2011 16:16:00 -0000 [thread overview]
Message-ID: <BANLkTi=f+-mKmgGPQg0rmqvqhM-zzDQUQw@mail.gmail.com> (raw)
In-Reply-To: <87ei4qbnkk.wl%ville@ville-laptop>
On Mon, Apr 25, 2011 at 6:03 AM, Ville Voutilainen
<ville.voutilainen@gmail.com> wrote:
>
> This is just for the parser, the semantic analysis of virt-specifiers
> will be done later. Also, these changes don't yet support a final
> specifier on class.
>
> diff --git a/gcc/cp/cp-tree.h b/gcc/cp/cp-tree.h
> index e538825..08d939f 100644
> --- a/gcc/cp/cp-tree.h
> +++ b/gcc/cp/cp-tree.h
> @@ -4420,6 +4420,11 @@ extern GTY(()) operator_name_info_t assignment_operator_name_info
>
> typedef int cp_cv_quals;
>
> +/* A type-qualifier, or bitmask therefore, using the VIRT_SPEC
> + constants. */
> +
> +typedef int cp_virt_specifiers;
could we use enums instead?
-- Gaby
next prev parent reply other threads:[~2011-04-25 15:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-25 14:11 Ville Voutilainen
2011-04-25 16:16 ` Gabriel Dos Reis [this message]
2011-04-25 16:39 ` Ville Voutilainen
2011-04-25 17:58 ` Jason Merrill
2011-04-25 18:12 ` Ville Voutilainen
2011-04-25 18:21 ` Jason Merrill
2011-04-26 9:11 ` Gabriel Dos Reis
[not found] ` <BANLkTi=kA3D+k0AASLEaoBtV=qMHsFX1ig@mail.gmail.com>
[not found] ` <BANLkTimHtLTx374Phz_HASbOVY0B4BLsWw@mail.gmail.com>
[not found] ` <BANLkTim8SQkNOtudxj90DhjYJ+HNCALQFQ@mail.gmail.com>
2011-04-27 23:07 ` Gabriel Dos Reis
2011-04-27 23:24 ` Ville Voutilainen
2011-04-27 23:29 ` Gabriel Dos Reis
2011-04-28 14:25 ` Ville Voutilainen
2011-04-28 14:26 ` Gabriel Dos Reis
2011-04-26 8:59 ` Gabriel Dos Reis
2011-04-25 17:11 ` 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='BANLkTi=f+-mKmgGPQg0rmqvqhM-zzDQUQw@mail.gmail.com' \
--to=gdr@integrable-solutions.net \
--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).