$include_dir="/home/hyper-archives/boost/include"; include("$include_dir/msg-header.inc") ?>
From: David Abrahams (dave_at_[hidden])
Date: 2007-12-04 09:55:10
on Mon Dec 03 2007, Joel de Guzman <joel-AT-boost-consulting.com> wrote:
> Anthony Williams wrote:
>> Joel de Guzman <joel_at_[hidden]> writes:
>> 
>>> * Non-core libraries may place a single consolidated convenience 
>>>   header in boost/, forwarding to files of the form 
>>>   boost/<libraryname>/<header>.hpp.  Regardless, their documented
>>>   public components are not in boost/ or namespace boost::
>> 
>> What about boost.thread? Though the "general use" header is boost/thread.hpp,
>> and the other headers are in boost/thread/xyz.hpp, the public interface is and
>> always has been in namespace boost::, and changing this now would be a
>> breaking change.
>
> Seems that if thread is a non-core library then it indeed breaks the
> "standard practice". 
I think our practices of namespace subdivision were only getting
established when Boost.Thread was introduced.
-- Dave Abrahams Boost Consulting http://www.boost-consulting.com