[v3] annex D 8 and 9 for C++0x

[Jonathan Wakely]

On 27/10/2007, Joe Buck <Joe.Buck@synopsys.com> wrote:
>
> Also, I had another question: do we expect the TR1 features, or some of
> them, to be absorbed into the regular standard, so that some future
> standards version will tell people to write <unordered_set> and not
> <tr1/unordered_set>, and drop the tr1 namespace as well?

Yes, absolutely, 100%. They're in the working paper already, and if
you use -std=c++0x you can include them that way today.

> And will we
> then get another round of deprecation?  The reason I ask is that a lot
> of long-lived code tries to support being compiled by many compilers,
> and I would like to argue in advance that making people keep changing
> the code is a bad idea.

I hope Benjamin or Paolo will correct me if I'm wrong, but I think the
TR1 features will continue to be available in C++98 mode, so will not
be deprecated.

There are some open questions about whether the interfaces should
track the C++0x paper. e.g. when I add allocator and aliasing support
to shared_ptr, should those featuers only be available in C++0x's
std::shared_ptr and not in std::tr1::shared_ptr ?

Jon