Re: [jamboost] Re: propagation of usage-requirements

From: Toon Knapen (toon.knapen_at_[hidden])
Date: 2004-12-17 03:59:01

Vladimir Prus wrote:
> 
> Sure, before my change it was possible to use:
> 
> lib B : b.cpp : <use>A : : <use>A ;
> 
> to propagate usage requirements of "B" to its dependents. So, library C need 
> not be changed, no matter how dependencies of 'B' are changed.
> 
> The issue is if this extra <use>A is not confusing enough in itself.

Sorry but I'm not sure how to interpret this last sentence. Do you find 
the extra '<use>A' confusing or not ?

I find this certainly confusing. Because if lib C uses lib B and if 
usage-requirements need to be explicitly propagated, I'm sure that one 
day someone will ask that lib C is able to specify that he wants to 
propagate the usage-requirements of lib A but not of lib B etc. IMO this 
become unnecessarily complex.