Re: [boost] namespace boost?

Subject: Re: [boost] namespace boost?
From: Stewart, Robert (Robert.Stewart_at_[hidden])
Date: 2011-01-18 12:50:40

Dave Abrahams wrote:
> 2011/1/18 Stewart, Robert <Robert.Stewart_at_[hidden]>:
>
> >> But for libraries with one 'main concept' file must exists
> >> such file.
> >> For example, in my Configurator:
> >>
> >> #include <boost/configurator/configurator.hpp>
> >
> > That should not preclude configurator/all.hpp, even if
> > all.hpp merely includes configurator.hpp.  You can change
> > boost/configurator/all.hpp should the need ever arise while
> > boost/configurator.hpp won't need to change.  That makes
> > selective, local changes easier because they would be
> > isolated to the configurator subdirectory.
>
> This is true, but I don't want to encourage a proliferation of
> files with the same name (in different directories).  That
> will just make development harder.  I can't help but think
> that those against boost/library_name.hpp are focusing so hard
> on purity that they're ignoring convenience.  It should be
> _trivial_ for people to get started with a boost library, and
> #include <boost/library_name/library_name.hpp> makes a bad
> first impression, IMO.

For the person just starting with a Boost library, boost/library_name.hpp is the way to go (I wasn't suggesting not having that file).  If that includes boost/library_name/all.hpp, then once boost/library_name.hpp exists, it will never change so library_name's developer need never worry about it again.

I wasn't commenting on the wisdom of boost/configurator/configurator.hpp, though I agree that the redundancy is unfortunate.  However, if there's no other include file in boost/configurator, what name should it have?

_____
Rob Stewart                           robert.stewart_at_[hidden]
Software Engineer, Core Software      using std::disclaimer;
Susquehanna International Group, LLP  http://www.sig.com

IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments. Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited. Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument. Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses.