This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: [RFC] libstdc++/6720 and libstdc++/6671
On Wed, May 22, 2002 at 09:33:29PM +0200, Gabriel Dos Reis wrote:
> | 2. Creating header files with the same names as system headers, and
> | injecting them into the search path ahead of the system headers, is
> | common practice
>
> I do not disregard that practice; that is why I said we provide
> an option to tell the compiler not give the standard meaning standard
> headers have.
Thinking about it, my entire position on this issue can be summed up
thus: That option already exists, and its name is -I <path>.
Furthermore, any change in this area will break an uncertain but large
number of user programs. The benefits of the change, meanwhile, are
minimal. I therefore do not believe any change should be made.
> If the user intentionally chooses to inject home-grown headers in
> place of standard ones, then that shouldn't be something the compiler
> should discover accidently; it should be something that it knows about
> because of appropriate options on invokation line.
Let me reiterate that the compiler does not "discover it accidently".
The compiler knows that the user wants their home-grown headers to be
used, because the user gave it an -I switch pointing to a directory
containing those headers. Anything else is second-guessing the user,
which I object to.
zw