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: Phil Edwards <phil at jaj dot com>
- To: Paolo Carlini <pcarlini at unitus dot it>
- Cc: libstdc++ at gcc dot gnu dot org, Nathan Myers <ncm at cantrip dot org>
- Date: Mon, 20 May 2002 17:42:17 -0400
- Subject: Re: [RFC] libstdc++/6720 and libstdc++/6671
- References: <3CE8ED6C.2060309@unitus.it>
On Mon, May 20, 2002 at 02:34:52PM +0200, Paolo Carlini wrote:
> In a nutshell, it looks like the idea of giving the ext/ extension
> headers the same name of the corresponding standard headers (e.g.,
> <algorithm> => <ext/algorithm>) was not so good afer all :-(
Ah well, we live and we learn. The only problems I'd noted so far were
with doxygen; it doesn't seem to do "maximal munch" when parsing header
file names.
> Probably, some confusion stems from entry 5.4 of the FAQ, which hints at
> the possibility of using -I: now this is not an option, since, when a
> standard header tries to include another standard header which has a
> corresponding extension in ext/, it ends up including the latter,
> instead of the former!!
Yes, this advice (which predates the header rename scheme) is now outdated.
I'll remove that bit of text.
Phil
--
If ye love wealth greater than liberty, the tranquility of servitude greater
than the animating contest for freedom, go home and leave us in peace. We seek
not your counsel, nor your arms. Crouch down and lick the hand that feeds you;
and may posterity forget that ye were our countrymen. - Samuel Adams