public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "3dw4rd at verizon dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/58057] gcc lexer cannot parse extern "\x43" void blah() with option -std=c++0x;
Date: Sat, 03 Aug 2013 03:30:00 -0000 [thread overview]
Message-ID: <bug-58057-4-Y93UFQh4vy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58057-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58057
--- Comment #12 from Ed Smith-Rowland <3dw4rd at verizon dot net> ---
On 08/02/2013 01:47 PM, paolo.carlini at oracle dot com wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58057
>
> --- Comment #11 from Paolo Carlini <paolo.carlini at oracle dot com> ---
> Ed, your analysis matches my intuition, but the error message is still very
> poor: to the user something like "... before STRING_USERDEF..." makes no sense
> at all. Can we improve it?
>
I agree that a better message is desirable.
I am starting to track this down and fix it.
(Any ideas?)
Ed
next prev parent reply other threads:[~2013-08-03 3:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-02 8:36 [Bug c++/58057] New: gcc lexer cannot parse extern "\x43" void blah(); schnoerr at mailzone dot com
2013-08-02 8:48 ` [Bug c++/58057] " mpolacek at gcc dot gnu.org
2013-08-02 8:50 ` paolo.carlini at oracle dot com
2013-08-02 11:30 ` [Bug c++/58057] gcc lexer cannot parse extern "\x43" void blah() with option -std=c++0x; mpolacek at gcc dot gnu.org
2013-08-02 11:31 ` paolo.carlini at oracle dot com
2013-08-02 12:32 ` schnoerr at mailzone dot com
2013-08-02 13:47 ` paolo.carlini at oracle dot com
2013-08-02 15:41 ` 3dw4rd at verizon dot net
2013-08-02 17:31 ` 3dw4rd at verizon dot net
2013-08-02 17:47 ` paolo.carlini at oracle dot com
2013-08-03 3:30 ` 3dw4rd at verizon dot net [this message]
2013-08-03 17:51 ` paolo.carlini at oracle dot com
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=bug-58057-4-Y93UFQh4vy@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).