Re: #include_next and removing of duplicate include dirs

[Phil Edwards <pedwards at disaster dot jaj dot com>]

On Tue, Sep 04, 2001 at 04:13:23PM +0200, Gabriel Dos Reis wrote:
> Zack Weinberg <zack@codesourcery.com> writes:
> | > This is a requirement of the C++ standard, see Annex D, "C" compatibility 
> | > headers. 
> | 
> | Wouldn't it be simpler and easier in the long run to cooperate with
> | the C library?
> 
> Yes, that was mentionned sometime ago (probably just before we released
> gcc-3.0) but there is no concretization yet -- at least if memory
> serves me well.

I think you're correct (again, if my own memory serves me well).  For glibc,
we just need to convince the glibc maintainers to allow C++ constructs in
their headers, and (again, IIRC) they historically have been unwilling to
do anything but C.  But given that they are chock full of GNU extensions,
adding "#ifdef __cplusplus" shouldn't hurt.  I don't the conversation ever
went any further.

For Solaris and similar systems, I don't remember what the most recent
problem was when their C++-aware headers get activated by our compatability
attempts.  Multiple definitions of size_t and other stddef types, I think.


Phil

-- 
Would I had phrases that are not known, utterances that are strange, in
new language that has not been used, free from repetition, not an utterance
which has grown stale, which men of old have spoken.
                                     - anonymous Egyptian scribe, c.1700 BC