[RFC] libstdc++/6720 and libstdc++/6671
Mark Mitchell
mark@codesourcery.com
Wed May 22 13:25:00 GMT 2002
--On Wednesday, May 22, 2002 09:48:57 PM +0200 Gabriel Dos Reis
<gdr@codesourcery.com> wrote:
> Mark Mitchell <mark@codesourcery.com> writes:
>
> [...]
>
>| If we had a directory that contained *only* the standard headers, i.e,.
>| <cmath>, <cstdio>, <iostream>, etc., then could we just put it at
>| the front of the #include path? In other words, *prepend*
>| -I /path/to/dir to the front of the users command line?
>
> I think that will work for standard headers. How can we make that
> work with extension headers?
Well, for them, we don't have a standards issue; it's at most a QOI
issue.
So, maybe we don't need to worry about it?
(I'm not even sure the extension headers should be named "memory" and
so forth; maybe they should be "memory.h". They're not the magic headers
defined by the standard; they're just headers we provide as part of our
implementation.)
>| That would make sure that those header files won. I guess it would
>| be better if this affected:
>|
>| # include <cmath>
>|
>| but not:
>|
>| # include "cmath"
>
> You're right.
>
>| I'm not sure if cpplib can keep track of separate lists for the two
>| different syntaxes, but I suppose it could be taught to do so.
>
> Yes. But, I'll wait Zack to confirm.
>
> -- Gaby
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com
More information about the Libstdc++
mailing list