Re: [boost] [modularization] Improving/splitting up detail

Subject: Re: [boost] [modularization] Improving/splitting up detail
From: Marshall Clow (mclow.lists_at_[hidden])
Date: 2013-11-03 10:40:22

On Nov 1, 2013, at 2:15 PM, Jeremiah Willcock <jewillco_at_[hidden]> wrote:

> On Fri, 1 Nov 2013, John Maddock wrote:
> 
>> Lets say we wanted boost/detail to depend on nothing but config, here's what it would take:
>> 
>> boost/detail/algorithm.hpp
>> 
>>  Used by graph lib only, suggest it's moved there.
> 
> I'm fine with that, but all uses of them can probably be removed anyway
> (there are only two functions in that file with four overloads).
> 
>> boost/detail/is_sorted.hpp
>> 
>>  Used by graph and range, move to "common"
> 
> Doesn't this belong in Algorithm?  It might be there already by some
> other name.

Yes.
#include <boost/algorithm/cxx11/is_sorted.hpp>

And has two advantages:
1) Range-based overloads.
2) Uses the standard library versions in c++11 (and beyond)

-- Marshall

Marshall Clow     Idio Software   <mailto:mclow.lists_at_[hidden]>

A.D. 1517: Martin Luther nails his 95 Theses to the church door and is promptly moderated down to (-1, Flamebait).
        -- Yu Suzuki