From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15821 invoked by alias); 29 Apr 2010 23:36:05 -0000 Received: (qmail 15792 invoked by uid 48); 29 Apr 2010 23:35:55 -0000 Date: Thu, 29 Apr 2010 23:36:00 -0000 Message-ID: <20100429233555.15791.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/msg03214.txt.bz2 ------- Comment #3 from igodard at pacbell dot net 2010-04-29 23:35 ------- Reopened, because comment#2 mistakes the problem. I don't want to get anything included into namespace std. However, I also do not want tyo get C header names imported into my application's global space merely because I included a C++ header. The correct solution to this is for the C++ library to not transitively include any C headers. If the C++ facility requires access to a C library function then the access can be hidden behind an adapter function in the C++ library. It is commonly assumed that applications will mix-and-match both C and C++ in one program, but some of us are trying to write only in C++ and don't want to be polluted. -- igodard at pacbell dot net changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |UNCONFIRMED Resolution|WONTFIX | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36231