From: Nick <nospam@codesniffer.com>
To: gcc@gcc.gnu.org
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Kudos!
Date: Wed, 24 Apr 2013 16:02:00 -0000 [thread overview]
Message-ID: <1366819363.14975.13.camel@nimble.325Bayport> (raw)
If this e-mail is not appropriate for either DL, then apologies in
advance.
I've used GCC for many years on and off and have always liked it. But
today I couldn't help but smile while using it. Here's what I saw:
main.cpp: In function 'int main(int, char**)':
main.cpp:130:29: error: 'Baz' was not declared in this scope
main.cpp:130:29: note: suggested alternative:
In file included from main.cpp:4:0:
Baz.h:208:8: note: 'Foo::Bar::Baz'
make[1]: *** [obj/main.o] Error 1
I'm using GCC 4.7.2, so I realize this feature has been present for a
while now. But something like this is really nice to see. It's the
little bit of help that saves me 20 seconds of doing the tedious
cross-referencing manually. I've also noticed improvements in build
failure messages where they are more useful in helping me figure out the
problem.
So this e-mail is Kudos to the project's developers & contributors for a
rockin' product! Keep up the good work!
Nick
reply other threads:[~2013-04-24 16:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1366819363.14975.13.camel@nimble.325Bayport \
--to=nospam@codesniffer.com \
--cc=gcc-help@gcc.gnu.org \
--cc=gcc@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).