Subject: Re: [boost] Boost.Test updates in trunk: need for (mini) review?
From: Evgeny Panasyuk (evgeny.panasyuk_at_[hidden])
Date: 2012-10-20 15:47:55
20.10.2012 23:31, Gennadiy Rozenal wrote:
>> 2. Is it OK to introduce dependencies on other boost libraries in order
>> to replace C++11 features? For instance replace (std::list + std::move)
> std::list older compilers should be able to handle.
yes, of course :)
Question was related to move-semantic of std::list itself (like
boost::container::list also has move-constructor (like std::list in
C++11) which works in all C++ ISOs, with help of Boost.Move.
> std::move, std::forward
> could probably be removed altogether. They use only to achieve proper move
> semantic of dataset construction
Yes, instead of using Boost's substitutions for C++11, it is possible to
refactor code for removing need in these new features.
But obviously that would take more time than just replacing std:: with
boost::, that why I am asking.
>> with (boost::container::list + boost::move), (std::shared_ptr +
>> std::make_shared) with (boost::shared_ptr + boost::make_shared)?
> boost shared_ptr is fine I guess.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk