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-23 11:56:24

Eric Niebler wrote:
>
> I don't like the idea of a boost/<lib>/all.hpp header. Does
> that really
> drag in everything? Debug utilities? Boost.Python integration?
> Boost.Serialization support? Typeof registrations? Support
> for Zlib and
> Bzip compression that will require downloading, configuring,
> building,
> and linking to additional external libraries? I find all.hpp headers
> generally useless.

If you don't want everything, you wouldn't include the all.hpp header.  Such headers are a convenience, particularly for those just learning to use a library (when the constant compilation failure because yet another include directive is needed can turn off a new user).

This is no different from what is already happening, except the name of the header would be standardized and its location relative to the library directory would be standardized.  It doesn't preclude you from including only the headers you want.

What we're trying to address is whether the "include all" header should be boost/<libname>.hpp, boost/<libname>/<libname>.hpp, or boost/<libname>/all.hpp.  There are examples of the first two already -- and perhaps even slight variations of those.

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