public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mueller at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/26142]  New: global debug namespace clashes everywhere
Date: Tue, 07 Feb 2006 00:16:00 -0000	[thread overview]
Message-ID: <bug-26142-12049@http.gcc.gnu.org/bugzilla/> (raw)

the 

namespace debug = std::__gnu_debug;

from debug/debug.h (which is pulled in by almost every STL header) causes
quite some clashes and is a huge PITA, as debug is often a user application
namespace or
function. 

why can't this be inside the std:: namespace or at least not be pulled in
by default? (without explicitely including this header, or even using some
define?)

this seems a violation of namespace cleanness to me. is this really defined
in ISO C++?


-- 
           Summary: global debug namespace clashes everywhere
           Product: gcc
           Version: 4.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: mueller at gcc dot gnu dot org


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


             reply	other threads:[~2006-02-07  0:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-07  0:16 mueller at gcc dot gnu dot org [this message]
2006-02-07  0:46 ` [Bug libstdc++/26142] " pinskia at gcc dot gnu dot org
2006-02-07  5:43 ` bkoz at gcc dot gnu dot org
2006-02-07 14:20 ` pinskia at gcc dot gnu dot org
2006-02-07 14:49 ` pinskia at gcc dot gnu dot org
2006-02-08 20:59 ` bkoz at gcc dot gnu dot org
2006-02-08 21:42 ` bkoz at gcc dot gnu dot org
2006-02-09  4:31 ` bkoz at gcc dot gnu dot org
2006-02-09  5:07 ` bkoz at gcc dot gnu dot org
2006-02-22 17:17 ` bkoz at gcc dot gnu dot org
2006-02-22 18:53 ` mueller at gcc dot gnu dot org
2006-03-16  1:42 ` bkoz 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-26142-12049@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).