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: Frank Mori Hess (frank.hess_at_[hidden])
Date: 2009-10-23 10:43:06

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Friday 23 October 2009, Olaf van der Spek wrote:
> On Fri, Oct 23, 2009 at 3:39 PM, Stewart, Robert <Robert.Stewart_at_[hidden]> 
wrote:
> > Olaf van der Spek wrote:
> >> On Fri, Oct 23, 2009 at 3:18 PM, Frank Mori Hess
> >>
> >> <frank.hess_at_[hidden]> wrote:

> >> > One suggestion I liked that came up earlier was using
> >> > all.hpp, for example boost/ptr_container/all.hpp.
> >>
> >> All seems a bit redundant, the standard is just <lib>.hpp AFAIK.
> >
> > Redundancy occurs with boost/ptr_container/ptr_container.hpp, not
> > boost/ptr_container/all.hpp. Â Using all.hpp means that all libraries use
> > the same header name and the library name isn't repeated. Â "all.hpp" is
> > as short as you can get and still mean "give me everything."
>
> Doesn't boost/ptr_container.hpp mean the same?

As another example, boost/thread.hpp (catch-all) is easily confused with 
boost/thread/thread.hpp (boost::thread class), whereas boost/thread/all.hpp 
is not.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkrhwPoACgkQ5vihyNWuA4XWsgCcDwBtb7S9CyMJckOay+w8Ft4r
b/cAoM1nVkNtCtu+mea2cFS4eR+r5rPE
=u2qF
-----END PGP SIGNATURE-----