This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: [RFC] libstdc++/6720 and libstdc++/6671
- From: Gabriel Dos Reis <gdr at codesourcery dot com>
- To: Alexandre Oliva <aoliva at redhat dot com>
- Cc: Zack Weinberg <zack at codesourcery dot com>, Paolo Carlini <pcarlini at unitus dot it>, Jonathan Wakely <cow at compsoc dot man dot ac dot uk>, libstdc++ at gcc dot gnu dot org, mark at codesourcery dot com
- Date: 23 May 2002 07:46:04 +0200
- Subject: Re: [RFC] libstdc++/6720 and libstdc++/6671
- Organization: CodeSourcery, LLC
- References: <3CEBD5BA.10409@unitus.it> <20020522174155.GC3536@codesourcery.com> <oroff7scyf.fsf@free.redhat.lsd.ic.unicamp.br>
Alexandre Oliva <aoliva@redhat.com> writes:
[...]
| My suggestion is that, whenever a *system* header file includes
| another header file using angle brackets, we search only the system
| header files (or perhaps search them first).
That is a position I can I agree (pending we resolve inclusion from
main programs) with and pretty close to Mark's proposal.
[...]
| This doesn't solve the problem of including standard headers from the
| main program. One could still replace them by having a file with the
| same name in one of the `-I'ed directories. It seems to me that the
| only way to overcome this problem is to have the preprocessor know a
| list of standard headers, that, when included with angle brackets, it
| would search in -I directories, but warn instead of including them.
| Such standard headers could still be replaced by a user by means of
| -isystem, and the user would get a warning in case the intent was to
| have a system header file replaced using -I.
I can live with that compromise.
-- Gaby