Re: [boost] Boost policy for putting headers in boost/ Was: #3541 Support <boost/ptr_map.hpp>

Subject: Re: [boost] Boost policy for putting headers in boost/ Was: #3541 Support <boost/ptr_map.hpp>
From: Stewart, Robert (Robert.Stewart_at_[hidden])
Date: 2009-10-28 13:18:15

Joel de Guzman wrote:
> > on Mon Oct 26 2009, Joel de Guzman
> <joel-AT-boost-consulting.com> wrote:
> >
> >> FWIW, we've solved that by having a flat include
> >> directory. It's the
> >> include/ dir you see up there. The directory contains all
> >> forwarding
> >> headers. For instance, see http://tinyurl.com/yj86r8v. You have:
> >>
> >>     #include <boost/fusion/include/deref.hpp>
> >>
> >> in addition to the modular:
> >>
> >>     #include <boost/fusion/iterator/deref.hpp>
[snip]
> I also advocate consistency. That is why I chose that structure.
> It's not different at all, if you think in terms of modularity.
> Boost is a set of libraries; each library is composed of smaller
> sub-libraries or components, and so on. The (outermost) main boost
> goes like this:
>
>      boost/
>          libx/
>          liby/
>          libx.hpp
>          liby.hpp
>
> Some libraries, especially the bigger ones really ought to
> be broken down into sub-libraries or modules. Following the
> main header convention, it goes the same for sub-libraries,
> e.g.:
>
>      boost/
>          libx/
>              modx/
>              mody/
>              modx.hpp
>              mody.hpp
>          liby/
>          libx.hpp
>          liby.hpp

That is reasonable and defensible, but argues against your include directory.

_____
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.