public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/46836] reporting locations for names in std namespace could be improved
Date: Tue, 29 May 2012 12:47:00 -0000	[thread overview]
Message-ID: <bug-46836-4-01ovkrOwRI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46836-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46836

--- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-05-29 12:14:18 UTC ---
(In reply to comment #2)
> #pragma GCC canonical_header [header-name] [identifier]

I don't think we even need to do it per-identifier.

If each standard header started with:

#pragma GCC canonical_header push [header-name]

and ended with:

#pragma GCC canonical_header pop

then we'd always know which header we're "in" when an error occurs, even for
nested headers (e.g. <fstream> includes <ios>) and helper files that are
included from many places (e.g. bits/stl_tree.h gets included by both <map> and
<set>)


  parent reply	other threads:[~2012-05-29 12:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-07 14:58 [Bug c++/46836] New: " froydnj at gcc dot gnu.org
2010-12-07 15:31 ` [Bug c++/46836] " redi at gcc dot gnu.org
2010-12-07 15:49 ` froydnj at codesourcery dot com
2010-12-07 16:49 ` redi at gcc dot gnu.org
2012-05-29 12:06 ` paolo.carlini at oracle dot com
2012-05-29 12:14 ` redi at gcc dot gnu.org
2012-05-29 12:47 ` redi at gcc dot gnu.org [this message]
2012-05-29 13:51 ` manu at gcc dot gnu.org
2012-05-30  7:49 ` dodji at seketeli 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-46836-4-01ovkrOwRI@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).