public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pcarlini at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/24537] Non-uglified names inside namespace __gnu_cxx
Date: Wed, 26 Oct 2005 12:37:00 -0000	[thread overview]
Message-ID: <20051026123714.31983.qmail@sourceware.org> (raw)
In-Reply-To: <bug-24537-133@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from pcarlini at suse dot de  2005-10-26 12:37 -------
(In reply to comment #1)
> Seems like to me, this is what namespaces are for anyways?  and non-uglified
> names are correct, maybe it needs to be a different namespace like
> __gnu_cxx::__implemenation instead which seems like the more correct thing to
> do than uglify names.  I think this is what Boost does too.

Indeed, the idea is using namespaces. But seems much more clean to me using
separate namespaces, not nested ones, for our problem: __gnu_cxx for new
extensions and __gnu_legacy for legacy extensions. The implementation proper
bits are instead already inside __gnu_internal.


-- 


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


  parent reply	other threads:[~2005-10-26 12:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-26 10:28 [Bug libstdc++/24537] New: " pcarlini at suse dot de
2005-10-26 12:34 ` [Bug libstdc++/24537] " pinskia at gcc dot gnu dot org
2005-10-26 12:37 ` pcarlini at suse dot de [this message]
2005-10-27  6:04 ` bkoz at gcc dot gnu dot org
2005-10-27  9:07 ` pcarlini at suse dot de
2005-10-27 21:55 ` pinskia at gcc dot gnu dot org
2006-11-21 10:48 ` bkoz at gcc dot gnu dot org
     [not found] <bug-24537-4@http.gcc.gnu.org/bugzilla/>
2022-11-04 19:20 ` redi 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=20051026123714.31983.qmail@sourceware.org \
    --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).