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: Phil Edwards <phil at jaj dot com>
- Cc: Paolo Carlini <pcarlini at unitus dot it>, libstdc++ at gcc dot gnu dot org, Phil Edwards <pedwards at disaster dot jaj dot com>, Nathan Myers <ncm at cantrip dot org>
- Date: 20 May 2002 19:49:12 +0200
- Subject: Re: [RFC] libstdc++/6720 and libstdc++/6671
- Organization: CodeSourcery, LLC
- References: <3CE8ED6C.2060309@unitus.it> <20020520134218.A30387@disaster.basement.lan>
Phil Edwards <phil@jaj.com> writes:
| 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.
I don't think the naming <ext/xxx> is the problem. We should cure the
problem, not the symptoms :-)
I describe the problem in an earlier message. I just sent a message
on gcc-gnats outlining (briefly) how we should map standard headers
into files.
-- Gaby