From: Paolo Carlini <paolo.carlini@oracle.com>
To: Jason Merrill <jason@redhat.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [C++ Patch] PR 67318 ("[6 regression] Parsing error when using abbreviated integral type names in template parameter pack declaration")
Date: Wed, 09 Sep 2015 19:35:00 -0000 [thread overview]
Message-ID: <55F08345.2010408@oracle.com> (raw)
In-Reply-To: <55F07DA4.4030808@redhat.com>
Hi,
On 09/09/2015 08:42 PM, Jason Merrill wrote:
> We should fix the logic in cp_parser_parameter_declaration to handle
> this, not work around it here.
Ok, that's what I meant for "more aggressive" ;) I didn't try do that
immediately when I noticed that the function is called from a few other
places, but I'll do that now. If I can't sort it out as quickly as I
want I'll tell you, the issue seems rather annoying...
Thanks!
Paolo.
next prev parent reply other threads:[~2015-09-09 19:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-09 16:58 Paolo Carlini
2015-09-09 18:51 ` Jason Merrill
2015-09-09 19:35 ` Paolo Carlini [this message]
2015-09-09 21:14 ` Paolo Carlini
2015-09-10 13:36 ` 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=55F08345.2010408@oracle.com \
--to=paolo.carlini@oracle.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).