This is the mail archive of the gcc@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]

Re: #include_next and removing of duplicate include dirs

To: Zack Weinberg <zack at codesourcery dot com>
Subject: Re: #include_next and removing of duplicate include dirs
From: Gabriel Dos Reis <gdr at codesourcery dot com>
Date: 04 Sep 2001 16:13:23 +0200
Cc: Benjamin Kosnik <bkoz at redhat dot com>, Jakub Jelinek <jakub at redhat dot com>, Neil Booth <neil at daikokuya dot demon dot co dot uk>, gcc at gcc dot gnu dot org
Organization: CodeSourcery, LLC
References: <20010903121625.A19816@panix.com> <Pine.SOL.3.91.1010903155629.4272A-100000@taarna.cygnus.com> <20010903162454.H16450@codesourcery.com>

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.

-- Gaby
CodeSourcery, LLC                       http://www.codesourcery.com

Follow-Ups:
- Re: #include_next and removing of duplicate include dirs
  - From: Phil Edwards

References:
- Re: #include_next and removing of duplicate include dirs
  - From: Zack Weinberg
- Re: #include_next and removing of duplicate include dirs
  - From: Benjamin Kosnik
- Re: #include_next and removing of duplicate include dirs
  - From: Zack Weinberg

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