public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "igodard at pacbell dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/36231] ostream includes unistd.h outside namespace std, polluting
Date: Thu, 29 Apr 2010 23:36:00 -0000 [thread overview]
Message-ID: <20100429233555.15791.qmail@sourceware.org> (raw)
In-Reply-To: <bug-36231-6594@http.gcc.gnu.org/bugzilla/>
------- 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
next prev parent reply other threads:[~2010-04-29 23:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-13 19:46 [Bug libstdc++/36231] New: " igodard at pacbell dot net
2008-05-13 20:04 ` [Bug libstdc++/36231] " pinskia at gcc dot gnu dot org
2010-04-29 23:16 ` redi at gcc dot gnu dot org
2010-04-29 23:36 ` igodard at pacbell dot net [this message]
2010-04-30 1:02 ` redi at gcc dot gnu dot org
2010-04-30 1:04 ` paolo dot carlini at oracle dot com
2010-04-30 5:28 ` igodard at pacbell dot net
2010-04-30 9:32 ` paolo dot carlini at oracle dot com
2010-04-30 9:51 ` redi at gcc dot gnu dot org
2010-04-30 14:24 ` igodard at pacbell dot net
2010-04-30 14:42 ` joseph at codesourcery dot com
2010-04-30 15:58 ` redi at gcc dot gnu dot org
[not found] <bug-36231-4@http.gcc.gnu.org/bugzilla/>
2011-04-20 15:18 ` redi at gcc dot gnu.org
2011-04-20 18:42 ` paolo.carlini at oracle dot com
2011-04-20 18:44 ` paolo.carlini at oracle dot com
2011-04-20 20:37 ` paolo.carlini at oracle dot com
2011-04-20 21:07 ` igodard at pacbell dot net
2011-04-20 23:10 ` rwild at gcc dot gnu.org
2011-04-21 0:03 ` paolo.carlini at oracle dot com
2011-04-21 0:23 ` igodard at pacbell dot net
2011-07-15 12:10 ` paolo.carlini at oracle dot com
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=20100429233555.15791.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).