Re: [boost] To modularize, or not to modularize. What is the plan?

Subject: Re: [boost] To modularize, or not to modularize. What is the plan?
From: Robert Ramey (ramey_at_[hidden])
Date: 2019-05-08 14:43:17

On 5/7/19 9:27 PM, Gavin Lambert via Boost wrote:
> On 8/05/2019 14:33, Rene Rivera wrote:

> In a modular Boost world, perhaps a user might say "I want to use 
> Boost.Thread", and add one include path and one library path.
> 
> Except that this won't work without the "preprocessing".  I don't think 
> that this user would want to add the 62 other libraries (I counted) that 
> are apparently required (according to boostdep/depinst) in order to use 
> Boost.Thread.
> 
> (Granted, it's probably being overly pessimistic -- I don't see why 
> Boost.Thread should depend on Boost.Regex, for example -- but that's 
> where we are right now.)

Right - that IS where we are.  Our assertion (library by library) of 
dependency leads to the conclusion that 62 other libraries are necessary 
when in fact they are not.

This assertion leads to demonstrably incorrect conclusions.  Thus it 
must be false.  This logic is incontestable.

Robert Ramey

> 
> _______________________________________________
> Unsubscribe & other changes: 
> http://lists.boost.org/mailman/listinfo.cgi/boost
>