$include_dir="/home/hyper-archives/boost/include"; include("$include_dir/msg-header.inc") ?>
Subject: Re: [boost] Boost.Algorithms organization question
From: Vicente Botet (vicente.botet_at_[hidden])
Date: 2011-12-05 11:59:30
Marshall Clow-2 wrote
> 
> So, while I'm waiting for my review result, I've been implementing the new
> algorithms that were to the standard library for C++11
> (at least the ones that don't require the new language features)
> 
> 
> (and, of course, Boost.Range versions wherever appropriate)
> 
IMO, the Boost.Range versions shouldn't go into  the c++11 file.
> I have not done:
> 	shuffle				-- requires rvalue references
> 	random_shuffle		-- requires rvalue references
> 
Could a Boost.Move emulation help here?
> 	move				-- already in Boost.Move; maybe just a forwarding header file?
> 	move_backward		-- already in Boost.Move; maybe just a forwarding header
> file?
> 
> 
> Anyway - my question is:
> 	Should these all go into a "c++11" subdirectory? If so, should I create a
> "c++11.hpp" header file that includes all of them, so that users can just
> 	#include <boost/algorithm/C++11.hpp> 
> and get all the C++11 algorithms?
> 
> Alternately, should they just live in boost/algorithm ?
> 
I would create a std_2011.hpp file.
In addition if this is not too much work I will find very useful to have a
kind of C++11 standard that uses std instead of boost as it was done for
TR1;
boost/std_2011/algorithm
We could do this way for all the standard files for which Boost provides a
c++11 compliant implementation or a c++03 emulation.
Best,
Vicente
-- View this message in context: http://boost.2283326.n4.nabble.com/Boost-Algorithms-organization-question-tp4161063p4161317.html Sent from the Boost - Dev mailing list archive at Nabble.com.