Re: [boost] [1.36.0] Libraries with unmerged changed - more accurate results.

From: David Abrahams (dave_at_[hidden])
Date: 2008-07-09 22:30:21

on Wed Jul 09 2008, Beman Dawes <bdawes-AT-acm.org> wrote:

> Below is a more accurate list of headers and libraries whose header
> files appear to differ between the trunk and branches/release.
>
> The most likely causes are:
>
> * Changes that should be merged into branches/release for 1.36.0. If
> that is the case, developers need to merge these changes right away!
>
> * Work in process that should *not* be merged into branches/release
> for 1.36.0. Please let me know that that is the case so I can stop
> worrying:-)
>
> * Although it seems to be working much better, there still may be
> issues with the script used to generate the report. Please let me know
> so the script can be improved.

What does it mean if my library appears in the list but none of its
headers show up?

> Headers:
>
> any.hpp
> concept_check.hpp
> enable_shared_from_this.hpp
> intrusive_ptr.hpp
> lexical_cast.hpp
> make_shared.hpp
> memory_order.hpp
> operators.hpp
> pointer_cast.hpp
> pointer_to_other.hpp
> rational.hpp
> scoped_array.hpp
> scoped_ptr.hpp
> shared_ptr.hpp
> smart_cast.hpp
> static_assert.hpp
> static_warning.hpp
> swap.hpp

The above is a new feature of the utility lib, not for release in 1.36

> tokenizer.hpp
> weak_ptr.hpp
>
> Libraries:
>
> iterator
> parameter
> python
> utility

What, specifically, are we concerned about with these libs?

-- 
Dave Abrahams
BoostPro Computing
http://www.boostpro.com