On Fri, Nov 08, 2002 at 10:56:24AM -0500, David Edelsohn wrote:
I am inclined to enable NO_IMPLICIT_EXTERN_C for the entire
directory,
in rs6000.h. What few targets this is inappropriate for -- I'm
willing to bet that's either none, or only AIX 3.1 -- can #undef it
again.
Comments?
I could see placing this in sysv4.h, but not rs6000.h. I do not
believe that GCC's fixincludes completely addresses the C++ issues in
the
AIX header files. IBM Visual Age C++ distributes its own system
header
files.
Defining or not defining NO_IMPLICIT_EXTERN_C addresses only one C++
issue with system headers. It should be defined by all targets where
the system headers already wrap declarations in extern "C" { ... }
when appropriate, and not defined otherwise. Is it really the case
that no AIX release provides extern "C" markers?
Darwin headers seem to provide extern "C", at least in the examples I