From: Jason Merrill <jason@redhat.com>
To: Paolo Carlini <paolo.carlini@oracle.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [C++ Patch] PR 29003
Date: Thu, 09 Jun 2011 14:19:00 -0000 [thread overview]
Message-ID: <4DF0D368.4020206@redhat.com> (raw)
In-Reply-To: <4DF09B6B.4060709@oracle.com>
On 06/09/2011 06:07 AM, Paolo Carlini wrote:
> I tested on x86_64-linux the below patchlet for a long standing
> accepts-invalid. Is it ok for mainline? Or do we want a different error
> message? A somehow tighter check?
The error message needs to say something about typedef being the
problem. Maybe follow the pattern of the previous error, and say
error ("declaration of %qD as %<typedef%>", dname);
Jason
next prev parent reply other threads:[~2011-06-09 14:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-09 11:44 Paolo Carlini
2011-06-09 14:19 ` Jason Merrill [this message]
2011-06-09 14:37 ` Paolo Carlini
2011-06-09 14:50 ` 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=4DF0D368.4020206@redhat.com \
--to=jason@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=paolo.carlini@oracle.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).