On Mon, 9 May 2005, Ralf Corsepius wrote:
> FWIW: IMO, NO_IMPLICIT_EXTERN_C actually is an OS/libc feature ("Your
> system headers are c++ aware"), therefore it is hardly possible or
> useful to ever use "#define NO_IMPLICIT_EXTERN_C" on "generic" targets
> (*-elf, *-coff etc.).
You could apply that argument the other way round - adding implicit extern
"C" is a workaround of an OS misfeature and you can hardly say that
generic targets are for systems with that misfeature.
I'd argue that on a generic target the user takes responsibility for
ensuring the headers and libc are suitable for GCC, and if the user is
using C++ then this responsibility includes making sure the headers are
C++-aware.
--
Joseph S. Myers http://www.srcf.ucam.org/~jsm28/gcc/
[EMAIL PROTECTED] (personal mail)
[EMAIL PROTECTED] (CodeSourcery mail)
[EMAIL PROTECTED] (Bugzilla assignments and CCs)
