This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug libstdc++/1773] __cplusplus defined to 1, should be 199711L


PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=1773



------- Additional Comments From gdr at integrable-solutions dot net  2003-08-03 19:16 -------
Subject: Re:  __cplusplus defined to 1, should be 199711L

"neroden at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> writes:

| Do we know what platforms are causing problems and why?
| 
| Also, are there more details on *why* this breaks things?  

I think most of the answers to your questions are contained in the
archive.  It was reported recently that a fix could be applied for
solaris-2.9 only. 

| Does it trigger incorrect behavior in system headers?  If so, can we make a
| system-specific change, or perhaps better, a fixincludes fix?

I don't think this is a case where we would like to use fixincludes
hacks.  Basically, some host (== target for the compiler) C libraries
are made ISO C++ aware (solaris-2.[89] C headers are such an example)
so that they are clean with respect to C++ rules.  We, in V3 land,
assume that most host C headers are not C++ aware and build our headers
on that assumption.  Many attempts were made in the past to correct
those assumtpions.  I believe Stephen Webb had worked in this area on
the topic of "stagged headers".

-- Gaby


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]