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-26 10:14:52

Joel de Guzman wrote:
> David Abrahams wrote:
> > on Fri Oct 23 2009, "troy d. straszheim"
> <troy-AT-resophonic.com> wrote:
> >>
> >> % ls boost/fusion
> >> adapted/       container.hpp   iterator.hpp  support/
>   view.hpp
> >> adapted.hpp    functional/     mpl/             support.hpp
> >> algorithm/     functional.hpp  mpl.hpp          tuple/
> >> algorithm.hpp  include/        sequence/     tuple.hpp
> >> container/     iterator/       sequence.hpp  view/
> >>
> > Fusion is very clean, but I have a problem remembering where
> > to find various files.  For that reason, I prefer the MPL's
> > organization, where component xxx can always be used after
> > #include <boost/mpl/xxx.hpp>.  There is lower-level
> > modularization, but for the most part the public interfaces
> > are in boost/mpl and subdirectories are reserved for
> > implementation details.
>
> 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>

That's just confusing.  Why would you want multiple copies of the same header or multiple ways to include the same functionality?  Besides, wouldn't the equivalent to what Dave noted be the following?

   #include <boost/fusion/deref.hpp>

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