[boost] Re: Preparing 1.30.1 Release

From: David Abrahams (dave_at_[hidden])
Date: 2003-08-01 12:18:20

"Joel de Guzman" <djowel_at_[hidden]> writes:

> David Abrahams <dave_at_[hidden]> wrote:
>> I have put a diff of the changes between Version_1_30_0 and RC_1_30_0
>> at http://www.boost-consulting.com/diffs-1-30-1.txt.  These will be
>> the changes that go into the Boost 1.30.1 release.  Will the
>> authors/maintainers of the following libraries please post a brief
>> summary of the fixes that were applied?
>>
>>         smart_ptr
>>         lexical_cast
>>         function
>>         lambda
>>         MPL
>>         type_traits
>>
>>         workaround (that's me)
>>         Python (me again)
>>         error_handling.html (again, me)
>
> Hi Dave,
>
> I'd like to add Spirit 1.6.1 (a bug fix release) to Boost 1.30.1.
> There are no new features in 1.6.1, just bug fixes. Here are
> the list of bug fixes.
>
>   a.. Fixed. Using MSVC++6 (SP5), calling the assign action with a string value on parsers
> using the file_iterator will not work.
>   b.. Fixed: using assign semantic action in a grammar with a multi_pass iterator adaptor
> applied to an std::istream_iterator resulted in a failure to compile under msvc 7.0.
>   c.. Fixed: There is a bug in the "range_run<CharT>::set (range<CharT> const& r)" function in
> the "boost\spirit\utility\impl\chset\range_run.ipp".
>   d.. Fixed: handling of trailing whitespace bug (ast_parse/pt_parse related)
>   e.. Fixed: comment_p and end of data bug
>   f.. Fixed: Most trailing space bug:
>   g.. Fixed:
>   chset<>::operator~(range<>) bug
>   operator&(chset<>, range<>) bug
>   operator&(range<>, chset<>) bug
>   h.. Fixed: impl::detach_clear bug
>   i.. Fixed: mismatch closure return type bug
>   j.. Fixed: access_node_d[] and access_match_d[] iterator bugs
>   k.. Fixed a bug regarding threadsafety of Phoenix/Spirit closures.
>   l.. Added missing include files to miniboost
>
> I am about to commit Spirit 1.6.1 to the RC_1_30_0 but wanted to
> ask anyway.

Thanks for asking.  Normally, I'd say absolutely not.  We announced
we were starting this release a while back and said that there would
be only minimal changes required to fix bugs which could reasonably
be applied in a week.  That week is long past.

However, since, like Boost.Python, Spirit doesn't appear in the
regression tests (we've got to fix that) and no libraries depend on it
(right?), you can't hurt the regression results by upgrading Spirit to
1.6.1.  You may proceed if you can do it in an hour or less.

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com