This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: C++0x support for libstdc++-v3?


On Tue, 2006-11-21 at 19:09 +0100, Benjamin Kosnik wrote:
> > I suggest that we shuffle the headers so that the C++0x headers that
> > involve TR1 components (like <tuple> and <functional>) include the TR1
> > bits, then make them available in namespace "std", while the TR1 headers
> > make them available in namespace std::tr1. Most likely, we'll need to
> > move all of the TR1 bits into a new namespace (std::__tr1), then have
> > strong using pull them into the appropriate namespace.
> 
> Your idea of using namespace association to do this is intriguing to
> me: you make it sound easy.

I think it's relatively easy. The main trick is to realize that include
<tr1/tuple> and <tuple> gives you the same facilities in two namespaces
(std and std::tr1).

>  I'll bite: I volunteer for this part.

Thanks!

> Pity we canot fudge and just keep std::tr1. I think we could do it with
> the header additions and a one-file (c++config.h) change with that
> constraint.

Yeah, it would be easier. But, we shouldn't have a std::tr1 namespace if
the user didn't include any TR1 headers, so we're stuck doing it the
more tedious way.

  Cheers,
  Doug


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]