Re: [boost] To split, or not to split, or something else? RE: type_traits rewrite, modularization, dependencies, etc.

Subject: Re: [boost] To split, or not to split, or something else? RE: type_traits rewrite, modularization, dependencies, etc.
From: Peter Dimov (lists_at_[hidden])
Date: 2015-02-04 10:44:20

Rene Rivera wrote:
> I guess I'm more of a stickler about structure then :-) I look at the 
> (small) special cases in build scripts and I cringe. I also think that if 
> it's a problem now, it will continue to be a problem in the future for new 
> libraries. So it's better to have an agreed upon structure (and 
> documentation) that we can point new authors to. This is al optional 
> anyway. It's just that I would prefer to have *one* option instead of *N* 
> options for each library (even if N is small).

I prefer zero options. :-)

I especially disprefer nested options, that is, libs/X and libs/X/Y. But 
ideally, it should all be libs/X, no options at all.