Subject: Re: [boost] std::auto_ptr in public interfaces
From: Daniel James (dnljms_at_[hidden])
Date: 2017-05-22 08:46:48
On 22 May 2017 at 06:56, Daniela Engert via Boost <boost_at_[hidden]> wrote:
> Am 21.05.2017 um 19:41 schrieb Daniel James via Boost:
>> On 20 May 2017 at 17:29, Daniela Engert via Boost <boost_at_[hidden]> wrote:
>> I don't think it's realistic to expect everyone to update their entire
>> code base at once. Especially if they're using code from multiple
>> sources. It should be as easy as possible to start using new versions,
>> any friction can result in people getting stuck on old versions which
>> makes life harder for everyone. If two dependencies both use the same
>> boost library, then it's unlikely they'll both update simultaneously,
>> so making it an either/or choice can cause real problems.
> I totally agree with you Daniel, but I'm not sure if we are on the same
> page here. Andrey's proposal is to have the existing interface based on
> std::auto-ptr side-by-side with a new one based on a future
> boost::unique_ptr, deprecating the std::auto_ptr interface. My proposal
> differs only in going to std::unique_ptr rather than boost::unique_ptr.
Sorry, I misunderstood what you meant by two solutions sitting side-by-side.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk