public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marc dot glisse at normalesup dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/6257] C-library symbols enter global namespace
Date: Wed, 19 Apr 2006 11:09:00 -0000	[thread overview]
Message-ID: <20060419110943.11689.qmail@sourceware.org> (raw)
In-Reply-To: <bug-6257-4079@http.gcc.gnu.org/bugzilla/>



------- Comment #19 from marc dot glisse at normalesup dot org  2006-04-19 11:09 -------
(In reply to comment #18)
> Probably this PR should be suspended, while waiting for the resolution of DR
> 456:
> 
>   http://www.open-std.org/jtc1/sc22/wg21/docs/lwg-active.html#456

Whether the situation remains the same or the g++ implementation becomes legal
does not change the fact that it would be nice (and not at all out of reach) to
use the features of glibc and solaris (any others?) that allow a cleaner global
namespace when including a <cxxx> header, it would just lower the priority of
this from bug to wishitem. And for platforms where it is not possible, then the
current implementation will have to remain, whatever the committee decides.

But if you want to suspend it, it is your call...


-- 


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


  parent reply	other threads:[~2006-04-19 11:09 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-6257-4079@http.gcc.gnu.org/bugzilla/>
2005-10-03  3:42 ` neroden at gcc dot gnu dot org
2006-02-07 12:41 ` pinskia at gcc dot gnu dot org
2006-04-18 15:10 ` marc dot glisse at normalesup dot org
2006-04-18 17:49 ` pcarlini at suse dot de
2006-04-19 11:09 ` marc dot glisse at normalesup dot org [this message]
2006-04-19 11:20 ` pcarlini at suse dot de
2006-04-19 11:38 ` marc dot glisse at normalesup dot org
2006-04-30 23:05   ` Gabriel Dos Reis
2006-04-19 11:44 ` pcarlini at suse dot de
2006-04-22  2:09 ` pinskia at gcc dot gnu dot org
2006-04-30 23:05 ` gdr at integrable-solutions dot net
2006-04-30 23:06 ` [Bug libstdc++/6257] [DR 456] " pinskia at gcc dot gnu dot org
2007-06-16 22:07 ` pcarlini at suse dot de
2007-06-16 22:19 ` pcarlini at suse dot de
2008-12-15 18:47 ` paolo dot carlini at oracle dot com
2010-02-05 13:16 ` paolo dot carlini at oracle dot com
     [not found] <20020411092600.6257.marc-oliver.gewaltig@hre-ftr.f.rd.honda.co.jp>
2003-06-01 21:46 ` [Bug libstdc++/6257] " pinskia@physics.uc.edu
2003-06-01 23:10 ` pinskia@physics.uc.edu
2003-06-01 23:13 ` pinskia@physics.uc.edu
2003-07-06 19:42 ` pinskia at physics dot uc dot edu
2003-10-15 22:49 ` pinskia at gcc dot gnu dot org
2003-11-16 20:58 ` paolo at gcc dot gnu dot org
2004-07-22  8:48 ` pinskia at gcc dot gnu dot org
2005-01-05 20:25 ` pinskia 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=20060419110943.11689.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).