Boost logo

Boost :

From: David Abrahams (dave_at_[hidden])
Date: 2005-01-14 12:00:00

Jason Hise wrote:
> Deane Yang wrote:
>> Martin Slater wrote:
>>> Just going to jump out from lurk mode for a second here, hope you
>>> don't mind me butting in;) I really don't get what the problem with
>>> dependencies on boost is. The whole point of boost as I see it is a
>>> big repository of well developed and proven portable code, subverting
>>> this just brings all the associated maintenence problems of having
>>> effectively duplicated code.
>> I'm another lurker who agrees with this.
> Alright, I will agree that I should use boost if my library naturally
> requires it. The difficulty I am having is that only one special policy
> in my library requires it, not the singleton framework itself. I just
> want to split apart these dependencies. You know, the whole "only pay
> for what you use" thing. It seems like the most natural way to do this
> would be to just put this policy and any others that required boost in a
> separate header, like "boost_singleton_extensions.h"

Header separation shouldn't be done based on implementation details.
Put every component of your library in a separate header and then
there's no question which should be included to use a particular
feature, and you don't have to move things around if your boost
dependencies change.

Dave Abrahams
Boost Consulting

Boost list run by bdawes at, gregod at, cpdaniel at, john at