Re: [boost] Removing old config macro and increasing compiler requirements.

Subject: Re: [boost] Removing old config macro and increasing compiler requirements.
From: Dave Abrahams (dave_at_[hidden])
Date: 2013-08-05 10:19:38

on Sun Aug 04 2013, Stephen Kelly <steveire-AT-gmail.com> wrote:

> On 08/03/2013 11:08 PM, Dave Abrahams wrote:
>> on Wed Jul 31 2013, Stephen Kelly <steveire-AT-gmail.com> wrote:
>>> That could be an option. Timing is difficult though. I still believe, as
>>> I wrote before
>>>
>>>  http://thread.gmane.org/gmane.comp.programming.tools.ryppl.devel/201/focus=208
>>>
>>> that modularization should be done before repo-splitting into many (35
>>> in the case of attempting to use boost::any) interdependent repos.
>> Why do you believe that?  It seems to me much, much easier to untangle
>> undesired dependencies after the repositories are split.
>
> A personal bias I suppose :). I don't know why you think it's much much
> easier to do post-split, but I guess the reason doesn't matter too much
> and it's manageable either way.

Well, I guess it's only *much* easier post-ryppl, which is further down
the road.  At that point, all dependencies will be explicitly declared
and each library author will have independent control.

-- 
Dave Abrahams