------- 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 <ostream> 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
