public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "glenn at zewt dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/43126] New: "at this point in file" warnings are upside down Date: Sat, 20 Feb 2010 05:22:00 -0000 [thread overview] Message-ID: <bug-43126-18813@http.gcc.gnu.org/bugzilla/> (raw) [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 1218 bytes --] These warnings have driven me insane for years: blah.cc:1: error: too many arguments to function void a(int) blah.cc:7: error: at this point in file I always end up jumping to line 1 in the file. I glance at the message and line number in the first line, and I'm jumping to that line number before my brain has really processed which error message it is. This is inherently something I can't learn to work around without deliberately slowing down my workflow (a mental pipeline stall?). The line number next to the error should be the one causing the error; any additional, related lines should come *after*. This is much better: blah.cc:7: error: too many arguments to function void a(int) blah.cc:1: error: declared here This also makes it consistent with the C version of this error. -- Summary: "at this point in file" warnings are upside down Product: gcc Version: 4.4.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: glenn at zewt dot org GCC host triplet: i486-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43126
next reply other threads:[~2010-02-20 5:22 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-02-20 5:22 glenn at zewt dot org [this message] 2010-02-20 6:25 ` [Bug c++/43126] " pinskia at gcc dot gnu dot org 2010-02-20 6:27 ` pinskia at gcc dot gnu dot org 2010-02-20 6:51 ` glenn at zewt dot org 2010-02-20 9:00 ` Andrew Pinski 2010-02-20 9:01 ` pinskia at gmail dot com 2010-02-20 15:31 ` manu at gcc dot gnu dot org 2010-02-20 15:56 ` manu at gcc dot gnu dot org 2010-02-22 22:31 ` manu at gcc dot gnu dot org 2010-02-22 22:32 ` manu at gcc dot gnu dot org 2010-06-02 6:54 ` pzhao at gcc dot gnu dot org
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-43126-18813@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: linkBe 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).