-isystem and C++ headers

[Zack Weinberg]

Daniel Jacobowitz <drow@false.org> writes:

>> On the original topic, I'd be open to changing -isystem (but,
>> contrariwise, I could be convinced that it isn't safe), and I am
>> definitely in favor of expanding the number of systems that define
>> NO_IMPLICIT_EXTERN_C.  I'm not going to abolish a feature that Darwin
>> needs, but I do want to get rid of it eventually.
>
> Perhaps we should flip the default?  I don't think newlib requires it,
> presumably neither does rtems; I don't know about other embedded
> targets like vxworks.  But some hosted systems (at least some Solaris
> versions, yes?) do.  I'd like to see the *-elf targets dump it.

I'd be happy to see the default flipped; I didn't suggest it because
it would involve auditing every target, whereas adding the existing
define to more targets doesn't.

vxworks I know doesn't need it; I should check the revised ports we
have in house (to be contributed RSN) to see if they are defining
N_I_E_C.

zw