id	summary	reporter	owner	description	type	status	milestone	component	version	severity	resolution	keywords	cc
1459	value_initialized leaves data uninitialized, when using Borland	niels_dekker	niels_dekker	"The data of an instance of boost::value_initialized<T> may not be initialized properly, when using Borland C++. This is caused by a Borland specific compiler issue:
[http://qc.codegear.com/wc/qcmain.aspx?d=51854 Value-initialization: POD struct should be zero-initialized]

For example:
{{{
#include <boost/utility/value_init.hpp>

struct Data { int i; };

  ...

  boost::value_initialized<Data> d;
  BOOST_CHECK( get(d).i == 0 ); // Typically fails on Borland!
}}}

Fernando Cacciola and I have already discussed this issue.  I hope to have a workaround within a few weeks... Note that the workaround described by Ticket #1217 does not yet work for Borland, because of some other Borland specific issues related to the use of ""typename"", placement-new, and explicit destructor calls."	Bugs	closed	Boost 1.35.0	None	Boost 1.34.1	Problem	fixed