From: Ed Smith-Rowland <3dw4rd@verizon.net>
To: Jason Merrill <jason@redhat.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [C++-11] User defined literals
Date: Wed, 12 Oct 2011 06:51:00 -0000 [thread overview]
Message-ID: <4E95201F.4020004@verizon.net> (raw)
In-Reply-To: <4E947562.5090505@redhat.com>
On 10/11/2011 12:57 PM, Jason Merrill wrote:
> On 10/11/2011 12:55 PM, Jason Merrill wrote:
>> On 10/09/2011 07:19 PM, Ed Smith-Rowland wrote:
>>> Does cp_parser_identifier (parser) *not* consume the identifier token?
>>
>> I'm pretty sure it does.
It does.
>>
>> Does it work to only complain if !cp_parser_parsing_tentatively?
>
> I suppose not, if you got no complaints with cp_parser_error.
>
> Jason
>
>
cp_parser_operator(function_id) is simply run twice in
cp_parser_unqualified_id.
Once inside cp_parser_template_id called at parser.c:4515.
Once directly inside cp_parser_unqualified_id at parser.c:4525.
cp_parser_template_id never succeeds with literal operator templates. I
find that curious. But I haven't looked real hard and the things do get
parsed somehow.
next prev parent reply other threads:[~2011-10-12 5:06 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
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 [this message]
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=4E95201F.4020004@verizon.net \
--to=3dw4rd@verizon.net \
--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).