public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/55252] Caret diagnostic doesn't show useful location when macro clashes with name in system header
Date: Tue, 15 Jul 2014 16:32:00 -0000	[thread overview]
Message-ID: <bug-55252-4-60RtTQQYeV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55252-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55252

--- Comment #16 from Tom Tromey <tromey at gcc dot gnu.org> ---
I've tripped across this enough that I've actually filed dups twice now.

I think it would be best to change the ordering here.
That is, the initial error ought to generally be the
location of the outermost expansion.  Then, the remaining
notes ought to delineate the macro expansions.

While it is true that this will yield a sub-optimal result in some
cases, I think that it will have better results in the preponderance
of cases.  That is, there's no way to be perfect here but gcc could be more
useful.


  parent reply	other threads:[~2014-07-15 16:32 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-09 18:07 [Bug c++/55252] New: " redi at gcc dot gnu.org
2012-11-09 18:08 ` [Bug c++/55252] " redi at gcc dot gnu.org
2012-11-09 21:02 ` manu at gcc dot gnu.org
2012-11-10 22:58 ` manu at gcc dot gnu.org
2012-11-10 23:10 ` manu at gcc dot gnu.org
2012-11-10 23:20 ` redi at gcc dot gnu.org
2012-11-19 16:17 ` dodji at seketeli dot org
2012-11-19 16:34 ` dodji at seketeli dot org
2012-11-19 16:50 ` manu at gcc dot gnu.org
2012-11-19 17:06 ` dodji at seketeli dot org
2012-11-19 17:18 ` dodji at seketeli dot org
2013-11-01 15:30 ` manu at gcc dot gnu.org
2013-11-01 21:33 ` manu at gcc dot gnu.org
2014-05-13 15:53 ` tromey at gcc dot gnu.org
2014-07-15 16:29 ` tromey at gcc dot gnu.org
2014-07-15 16:32 ` tromey at gcc dot gnu.org [this message]
2015-02-01 20:29 ` manu at gcc dot gnu.org
2015-02-03 10:35 ` dodji at gcc dot gnu.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-55252-4-60RtTQQYeV@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).