This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: std::ext STL (was: Re: design doc on alternative pointer support)
- From: "Phil Bouchard" <philippe at fornux dot com>
- To: libstdc++ at gcc dot gnu dot org
- Date: Fri, 1 Aug 2008 03:05:27 -0700
- Subject: Re: std::ext STL (was: Re: design doc on alternative pointer support)
- References: <g6ge3q$4hv$1@ger.gmane.org> <12045826.1217359611034.JavaMail.oracle@acsmt301.oracle.com> <g6s37t$8as$1@ger.gmane.org> <15568220.1217500906101.JavaMail.oracle@acsmt305.oracle.com>
"Paolo Carlini" <paolo.carlini@oracle.com> wrote in message
news:15568220.1217500906101.JavaMail.oracle@acsmt305.oracle.com...
[...]
> - Code living in a new namespace, an approach completely analogous to the
> debug-mode and parallel-mode facilities. Of course binary compatibility
> with normal containers cannot be achieved, but the user, at variance with
> the previous solution, is allowed to not change the sources, has simply to
> recompile all the translation units using the containers (the so called
> "Per-use recompilation" in the documentation of debug-mode)
In regards to licensing it is queued and on its way. As far as namespaces
are concerned then although it would be possible having different
specializations here and there with binary compatibility for raw pointers,
the maintenance of it will be a greater issue. I don't see anything wrong
by using a new namespace and may save trouble for both maintainers and
debugging issues for users.
Thanks,
-Phil