From f16220569162b667d4f257d11ce3c1fd30456e5a Mon Sep 17 00:00:00 2001 From: Niels Dekker Date: Sun, 25 Apr 2010 09:48:49 +0000 Subject: [PATCH] Postponed BOOST_NO_COMPLETE_VALUE_INITIALIZATION definition, in order to check value-initialization of heap objects, which I just added to boost_no_complete_value_initialization::test() [61552] [SVN r61554] --- include/boost/config/compiler/vacpp.hpp | 8 -------- 1 file changed, 8 deletions(-) diff --git a/include/boost/config/compiler/vacpp.hpp b/include/boost/config/compiler/vacpp.hpp index 36c8288f..01956d3a 100644 --- a/include/boost/config/compiler/vacpp.hpp +++ b/include/boost/config/compiler/vacpp.hpp @@ -30,14 +30,6 @@ # define BOOST_NO_INITIALIZER_LISTS #endif -#if (__IBMCPP__ <= 1010) -// XL C++ V10.1.0.0 may not always value-initialize a temporary object T(), -// when T is a non-POD aggregate class type. Michael Wong (IBM Canada Ltd) -// has confirmed this issue and gave it high priority. -// -- Niels Dekker (LKEB), 2010. -# define BOOST_NO_COMPLETE_VALUE_INITIALIZATION -#endif - // // On AIX thread support seems to be indicated by _THREAD_SAFE: //