From: Ian Lance Taylor <iant@google.com>
To: "John S. Fine" <johnsfine@verizon.net>
Cc: gcc-help@gcc.gnu.org
Subject: Re: error: 'cit' was not declared in this scope
Date: Wed, 06 Jan 2010 15:35:00 -0000 [thread overview]
Message-ID: <mcrzl4r1c26.fsf@dhcp-172-17-9-151.mtv.corp.google.com> (raw)
In-Reply-To: <4B3BE264.2070703@verizon.net> (John S. Fine's message of "Wed\, 30 Dec 2009 18\:29\:40 -0500")
"John S. Fine" <johnsfine@verizon.net> writes:
> Having written many parsers myself (though not for anything
> approaching the difficulty of parsing C++) I know how hard it is to
> get a parser to generate decent error messages. But in this case the
> error message is particularly lame:
I would encourage you to file a bug report with a test case. See
http://gcc.gnu.org/bugs/ .
Ian
next prev parent reply other threads:[~2010-01-06 15:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-29 19:49 Gerry Sweeney
2009-12-29 20:45 ` John S. Fine
2009-12-30 3:49 ` Gerry Sweeney
2009-12-30 13:51 ` Andrew Haley
2009-12-30 23:59 ` John S. Fine
2010-01-06 15:35 ` Ian Lance Taylor [this message]
[not found] <E2A1DD3AE3471D42B24E218A48E0D89D0187585B@exch2.internal.hornbill.com>
2009-12-29 17:30 ` Gerry Sweeney
2009-12-29 18:11 ` Ian Lance Taylor
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=mcrzl4r1c26.fsf@dhcp-172-17-9-151.mtv.corp.google.com \
--to=iant@google.com \
--cc=gcc-help@gcc.gnu.org \
--cc=johnsfine@verizon.net \
/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).