on Fri Jun 22 2012, Daniel James <dnljms-AT-gmail.com> wrote:
On 22 June 2012 18:30, Robert Ramey <ramey@rrsd.com> wrote:
Stewart, Robert wrote:
The more dependencies you introduce, the more fragile your code becomes, but there's a great deal of benefit to reuse, too. The only issue in this case is that one can reasonably expect a top-level header to avoid dependencies on libraries.
Personally I wouldn't say it's the only issue. But I'm glad we can agree that it's its a BIG issue.
There are a lot of headers violating your rule.
Most notably, there are plenty of aggregate headers that do this.
What problems has it caused?
Good question. We do have two problematic dependency loops in Boost, but it's not caused by this sort of header structure: http://f.cl.ly/items/343N460u3b3039091C0g/deps.pdf -- Dave Abrahams BoostPro Computing http://www.boostpro.com