This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: TR library extensions
- From: Gabriel Dos Reis <gdr at integrable-solutions dot net>
- To: Pétur Runólfsson <peturr02 at ru dot is>
- Cc: <libstdc++ at gcc dot gnu dot org>
- Date: 06 Oct 2003 12:02:26 +0200
- Subject: Re: TR library extensions
- Organization: Integrable Solutions
- References: <07D05A69A3D0C14FAEA60C3ACE8E5564028F55DD@mail.ru.is>
Pétur Runólfsson <peturr02@ru.is> writes:
| > What do people think about directory structure and naming conventions
| > and such?
|
| I vote for include/tr1.
|
| A -std= option is needed that adds include/tr1 to the include path,
| because the new tr1 headers should not be visible if -std=c++98 is
| given.
Why?
the TR1 resides in a separate namespace (excep for a very few).
| A preprocessor macro is needed for the same reason (as some
| proposals make changes to existing components). Maybe -std=tr1 and
| __TR1__ ?
__LIBCXX_TR1__?
We should be aware that we're not the only project. We should make it
clear which symbols are ours (or C++'s), preferably in the spelling.
| The implementation will probably take a while to settle down. Should
| the additions be put in a separate library so that non-compatible
| changes can be made without breaking programs that only use C++98?
I don't understand this.
-- Gaby