Re: [Boost-bugs] [Boost C++ Libraries] #3869: Unconditional call to memset in value_initialized()

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #3869: Unconditional call to memset in value_initialized()
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2010-01-29 17:14:58

#3869: Unconditional call to memset in value_initialized()
--------------------------+-------------------------------------------------
 Reporter:  agurtovoy     |       Owner:  niels_dekker
     Type:  Bugs          |      Status:  new         
Milestone:  Boost 1.42.0  |   Component:  utility     
  Version:  Boost 1.41.0  |    Severity:  Problem     
 Keywords:                |  
--------------------------+-------------------------------------------------

Comment(by niels_dekker):

 Thanks, John.  I read that there's a BOOST_NO_''SOMETHING'' naming
 convention. So now I'm considering to name the macro
 ''BOOST_NO_PROPER_VALUE_INITIALIZATION_FOR_ALL_TYPES''. (Instead of
 ''BOOST_VALUE_INITIALIZATION_NEEDS_MEMSET''.) So that the unit test should
 show that compilers that have this macro defined do indeed do an improper
 value-initialization, for at least one type.

 I'll have a closer look later...

-- 
Ticket URL: <https://svn.boost.org/trac/boost/ticket/3869#comment:3>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.