Re: [boost] [Git] Modularization of Boost.Any, Boost.Array, and Boost.StaticAssert

Subject: Re: [boost] [Git] Modularization of Boost.Any, Boost.Array, and Boost.StaticAssert
From: Beman Dawes (bdawes_at_[hidden])
Date: 2012-12-26 11:12:57

On Wed, Dec 26, 2012 at 10:47 AM, Dave Abrahams <dave_at_[hidden]> wrote:
>
> on Tue Dec 25 2012, Daniel Pfeifer <daniel-AT-pfeifer-mail.de> wrote:
>
>> 2012/12/26 Klaim - Joël Lamotte <mjklaim_at_[hidden]>
>>
>>> Hi,
>>>
>>>
>>> On Wed, Dec 26, 2012 at 12:33 AM, Daniel Pfeifer <daniel_at_[hidden]
>>> >wrote:
>>>
>>> > I propose to put all three of them into the Boost.Utility repository.
>>> > Comments?
>>> >
>>>
>>> It would mean that getting a specific version of one of these libraries
>>> will potentially change the version of the other libraries.
>>> As they don't seem directly related, it might not be a good idea.
>>> DVCS repositories are cheap (on space) so is there specific reasons that
>>> would make this better?
>>>
>>
>> Consistency. Boost.Utility already hosts some similarly small and unrelated
>> libaries: CallTraits, Noncopyable, Operators, EnableIf, ...
>
> Well, there's also the possibility that these libraries should each have
> their own repository.  That would be another way of achieving consistency.

There is also the question of ownership. These libraries have
different maintainers. Lumping them all into utility dilutes
responsibility.

I'd rather leave any, static_assert, and array as separate libraries.

--Beman