From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8957 invoked by alias); 30 Apr 2010 05:28:26 -0000 Received: (qmail 8889 invoked by uid 48); 30 Apr 2010 05:28:12 -0000 Date: Fri, 30 Apr 2010 05:28:00 -0000 Message-ID: <20100430052812.8888.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug libstdc++/36231] ostream includes unistd.h outside namespace std, polluting In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "igodard at pacbell dot net" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2010-04/txt/msg03227.txt.bz2 ------- Comment #6 from igodard at pacbell dot net 2010-04-30 05:28 ------- I guess I'm still not being clear. I'm not using *any* of those names; I'm not using C; I'm not using POSIX. I'm only using ostream, which is a plain old C++ library, but when I include I'm getting C library functions like open() - not C++ open, C open() - added to my global space, where they conflict with application identifiers. Including a C++ include file should not cause any identifiers from the C or POSIX to be gratuitously added to the the user's global space. This is a bug. Please check with your colleagues if you still do not understand the problem. Andrew says 4.3 has fixed this; if so it can be closed FIXED, if verified. But closing it WONTFIX is wrong. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36231