Subject: Re: [boost] std::auto_ptr in public interfaces
From: Daniela Engert (dani_at_[hidden])
Date: 2017-05-23 14:36:06
Am 23.05.2017 um 01:56 schrieb Gavin Lambert via Boost:
> If anything else that currently uses std::auto_ptr in its public
> interface does likewise, then everybody should be happy:
> - those using C++98/03 compilers can continue using std::auto_ptr.
> - those using C++11/14 compilers get both and their old code will
> compile while allowing them to convert to std::unique_ptr at their
> leisure. (The compiler should be giving them deprecation warnings, so
> they know to do this.)
> - those using C++17 compilers don't get the std::auto_ptr version,
> which would no longer compile.
There it is, my take on Boost.Ptr_container:
This passes the testsuite just like vanilla develop when compiled with
* msvc 9.0 which has no std::unique_ptr
* msvc 14.x in a mode without std::auto_ptr
* msvc 12.0 which has both std::auto_ptr and std::unique_ptr
The std::auto_ptr-based library interface can be deliberately disabled,
and similarly the std::auto_ptr-based tests.
I'm all ears for suggestions, pointing out errors, whatever ...
-- PGP/GPG: 2CCB 3ECB 0954 5CD3 B0DB 6AA0 BA03 56A1 2C4638C5
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk