This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: #include <complex>
- To: Dimitri PAPADOPOULOS-ORFANOS <papadopo at shfj dot cea dot fr>
- Subject: Re: #include <complex>
- From: Richard Hadsell <hadsell at blueskystudios dot com>
- Date: Thu, 05 Feb 1998 14:17:51 -0500
- CC: egcs-bugs at cygnus dot com
- Organization: Blue Sky | VIFX
- References: <199802051630.RAA07230@broceliande.shfj.cea.fr>
Dimitri PAPADOPOULOS-ORFANOS wrote:
>
> I agree, directories should be silently ignored.
>
> Still, I think that when processing
> #include <...>
> directories in $CPLUS_INCLUDE_PATH should be scanned before
> the directories specified on the command line.
>
> On the other hand, when processing
> #include "..."
> it's ok for directories specified on the command line to be
> scanned first.
I hope not. The conventional interpretation of #include "..." was to
look in the current directory first, and then look in the include path.
I certainly don't want to change my millions of #include <...>
statements just to insist that it use my include path. And if I want to
override a standard header with an equivalent one from some alternative
library, I always want to do it. When would one ever want the default
standard headers to supersede an alternative one found in the -I include
path?
--
Dick Hadsell 914-381-8400 Fax: 914-381-9790
Reply-to: hadsell@blueskystudios.com
Blue Sky | VIFX http://www.blueskystudios.com
1 South Road, Harrison, NY 10528