At Fri, 26 Mar 2010 20:30:25 +0200, Peter Dimov wrote:
Steven Watanabe:
AMDG
David Abrahams wrote:
Every dependency should be an informed and conscious decision on the part of a library developer.
Humph. It's not as though #includes mysteriously appear in your code when you're looking the other way.
They do, as part of bug fixes made by others and as indirect dependencies. This goes unnoticed because the test infrastructure always has the whole of Boost available. One needs to actively fight dependencies, or they do creep in.
They also appear indirectly. If A depends on B and B acquires a new dependency, A now has a new dependency too. -- Dave Abrahams Meet me at BoostCon: http://www.boostcon.com BoostPro Computing http://www.boostpro.com