From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8948 invoked by alias); 1 May 2006 23:40:00 -0000 Received: (qmail 8897 invoked by alias); 1 May 2006 23:39:58 -0000 Date: Mon, 01 May 2006 23:40:00 -0000 Message-ID: <20060501233958.8896.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug libstdc++/27340] valarray uses __cos which may conflict with libm functions In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "gdr at integrable-solutions dot net" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2006-05/txt/msg00072.txt.bz2 List-Id: ------- Comment #7 from gdr at integrable-solutions dot net 2006-05-01 23:39 ------- Subject: Re: valarray uses __cos which may conflict with libm functions "marc dot glisse at normalesup dot org" writes: | (In reply to comment #4) | > Should all those private classes and functions be declared in some | > specific namespace std::glibcxx_private to have a single point of failure? | | Oups, I just noticed that was one of the roles of __gnu_cxx (although I don't | understand why this namespace is not a subnamespace of std:: as tr1 (or at | least contains a using namespace std;), Why shall it? Before people suggest more tricky playing with libstdc++ name spaces, I would recommand people understand that namespaces are not silver bullet against machivelic playing with names. | which would at the same time fix things | like getenv not being prefixed by std:: in ext/mt_allocator.h). That is a separate problem that does not require namespace nesting. Nesting namespaces does not come for free. You really need to understand its consequences (name lookp, overload resolution, etc.) before proposing it. -- Gaby -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27340