From: Jason Merrill <jason@redhat.com>
To: Ed Smith-Rowland <3dw4rd@verizon.net>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [C++-11] User defined literals
Date: Sun, 09 Oct 2011 01:18:00 -0000 [thread overview]
Message-ID: <4E90D97F.9060506@redhat.com> (raw)
In-Reply-To: <4E909588.3000801@verizon.net>
On 10/08/2011 07:25 PM, Ed Smith-Rowland wrote:
> Also, In spite of the documentation cp_parser_template_parameter_list
> returns a TREE_VEC not a TREE_LIST. This happens inside
> end_template_parm_list called inside the former. So parameter_list is a
> TREE_VEC, parm_list is a TREE_LIST, parm is a PARM_DECL, etc.
Ah, I was thinking of template arguments rather than parameters. You're
right, except that INNERMOST_TEMPLATE_PARMS should be just TREE_VALUE;
you are already starting from the innermost parm list if you use what
end_template_parm_list returns.
Though it occurs to me that push_template_decl_real might be a better
place for this check.
> I'm still looking for a fix for duplicate errors/warnings coming from
> cp_parser_operator. I tried cp_parser_error and lost the errors. I'll
> look for different code paths for the two invocations and see if I can
> either move something up or see if something is set differently between
> the two that would be useful for a flag.
One approach would be changing the token stream after the first error to
something that won't produce another error, e.g. changing token->u.value
to be an empty string after you complain about it being non-empty.
Jason
next prev parent reply other threads:[~2011-10-08 23:15 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-13 15:36 Ed Smith-Rowland
2011-09-13 16:43 ` Jason Merrill
2011-09-14 8:00 ` Jason Merrill
2011-09-19 8:33 ` Ed Smith-Rowland
2011-09-19 22:43 ` Jason Merrill
2011-09-20 7:23 ` Ed Smith-Rowland
2011-09-20 21:48 ` Jason Merrill
2011-10-05 15:57 ` Ed Smith-Rowland
2011-10-05 21:24 ` Jason Merrill
2011-10-08 21:38 ` Ed Smith-Rowland
2011-10-09 1:18 ` Jason Merrill [this message]
2011-10-09 23:46 ` Ed Smith-Rowland
2011-10-11 19:20 ` Jason Merrill
2011-10-11 17:39 ` Jason Merrill
2011-10-12 6:51 ` Ed Smith-Rowland
2011-10-12 18:49 ` Jason Merrill
2011-10-12 21:12 3dw4rd
2011-10-15 23:13 ` Jason Merrill
2011-10-16 7:59 ` Jason Merrill
2011-10-21 14:56 ` Ed Smith-Rowland
2011-10-21 21:20 ` Tom Tromey
2011-10-21 23:38 ` Jason Merrill
2011-10-23 22:29 ` Ed Smith-Rowland
2011-10-24 15:41 ` Ed Smith-Rowland
2011-10-25 23:38 ` Jason Merrill
2011-10-26 9:16 ` Ed Smith-Rowland
2011-10-26 20:13 ` Jason Merrill
2011-10-27 19:15 ` Ed Smith-Rowland
2011-10-27 19:55 ` Ed Smith-Rowland
2011-10-27 20:37 ` Jason Merrill
2011-10-30 19:10 ` Ed Smith-Rowland
2011-10-31 17:52 ` Jason Merrill
2011-10-25 7:07 ` Ed Smith-Rowland
2011-10-21 17:04 3dw4rd
2011-10-26 20:33 3dw4rd
2011-10-26 20:46 ` Jason Merrill
2011-10-31 17:58 3dw4rd
2011-10-31 20:20 ` 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=4E90D97F.9060506@redhat.com \
--to=jason@redhat.com \
--cc=3dw4rd@verizon.net \
--cc=gcc-patches@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).