Re: [boost] [1.33.0] Code is frozen

From: Ralf W. Grosse-Kunstleve (rwgk_at_[hidden])
Date: 2005-07-27 12:06:49

--- Douglas Gregor <doug.gregor_at_[hidden]> wrote:

> The source code for Boost 1.33.0 is now frozen. Please do not check in 
> any changes to the Boost source code without my explicit permission. 
> You may still update parts of Boost that do not affect the regression 
> tests in any way, until we have our final freeze of the entire tree at 
> 11PM EST on Wednesday.

Hi Dough,

Coincidentally HP released a field-test (beta) version of the new Tru64 cxx
compiler two days ago. The new compiler is based on EDG 304. Diagnostics from
this front-end made it clear to us that a GCC-specific workaround in one of the
Boost.Python tests should be universal. See the tiny patch below. Clearly this
patch is not super critical since it is only for a test file, but assuming a
time span of 6-12 months before the next Boost release, the problem may upset a
fair number of people testing with new compilers. To eliminate this
possibility, could we still check in the patch?

Thanks!
        Ralf

Index: data_members.cpp
===================================================================
RCS file: /cvsroot/boost/boost/libs/python/test/data_members.cpp,v
retrieving revision 1.21
diff -r1.21 data_members.cpp
67,71c67
<   const Color3 Color3::black
< #if BOOST_WORKAROUND(__GNUC__, BOOST_TESTED_AT(3))
<   = {}
< #endif 
<       ;
--- 
>   const Color3 Color3::black = {} ;

                
____________________________________________________
Start your day with Yahoo! - make it your home page 
http://www.yahoo.com/r/hs