forked from boostorg/utility
Merge.
[SVN r42905]
This commit is contained in:
1 parent
fc960ec5ef
commit
928091779d
3 files changed
+245
-45
No files matched your search
@@ -1,31 +1,20 @@
|
||||
// (C) Copyright 2002-2007, Fernando Luis Cacciola Carballal.
|
||||
// (C) Copyright 2002-2008, Fernando Luis Cacciola Carballal.
|
||||
//
|
||||
// Distributed under the Boost Software License, Version 1.0. (See
|
||||
// accompanying file LICENSE_1_0.txt or copy at
|
||||
// http://www.boost.org/LICENSE_1_0.txt)
|
||||
//
|
||||
// 21 Ago 2002 (Created) Fernando Cacciola
|
||||
// 24 Dec 2007 (Refactored and worked around various compiler bugs) Fernando Cacciola, Niels Dekker
|
||||
// 19 Jan 2008 (Worked around compiler bugs, added initialized_value) Fernando Cacciola, Niels Dekker
|
||||
//
|
||||
#ifndef BOOST_UTILITY_VALUE_INIT_21AGO2002_HPP
|
||||
#define BOOST_UTILITY_VALUE_INIT_21AGO2002_HPP
|
||||
|
||||
// Note: The implementation of boost::value_initialized had to deal with the
|
||||
// fact that various compilers haven't fully implemented value-initialization:
|
||||
// Microsoft Feedback ID 100744 - Value-initialization in new-expression
|
||||
// Reported by Pavel Kuznetsov (MetaCommunications Engineering), 2005-07-28
|
||||
// https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=100744
|
||||
// GCC Bug 30111 - Value-initialization of POD base class doesn't initialize members
|
||||
// Reported by Jonathan Wakely, 2006-12-07
|
||||
// http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30111
|
||||
// GCC Bug 33916 - Default constructor fails to initialize array members
|
||||
// Reported by Michael Elizabeth Chastain, 2007-10-26
|
||||
// http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33916
|
||||
// Borland Report 51854 - Value-initialization: POD struct should be zero-initialized
|
||||
// Reported by Niels Dekker (LKEB, Leiden University Medical Center), 2007-11-09
|
||||
// http://qc.codegear.com/wc/qcmain.aspx?d=51854
|
||||
// The constructor of boost::value_initialized<T> works around these issues, by
|
||||
// clearing the bytes of T, before constructing the T object it contains.
|
||||
// fact that various compilers haven't fully implemented value-initialization.
|
||||
// The constructor of boost::value_initialized<T> works around these compiler
|
||||
// issues, by clearing the bytes of T, before constructing the T object it
|
||||
// contains. More details on these issues are at libs/utility/value_init.htm
|
||||
|
||||
#include <boost/aligned_storage.hpp>
|
||||
#include <boost/detail/workaround.hpp>
|
||||
@@ -60,7 +49,7 @@ class value_initialized
|
||||
#if _MSC_VER >= 1310
|
||||
// When using MSVC 7.1 or higher, the following placement new expression may trigger warning C4345:
|
||||
// "behavior change: an object of POD type constructed with an initializer of the form ()
|
||||
// will be default-initialized". There is no need to worry about this, though.
|
||||
// will be default-initialized". It is safe to ignore this warning when using value_initialized.
|
||||
#pragma warning(disable: 4345)
|
||||
#endif
|
||||
#endif
|
||||
@@ -77,9 +66,8 @@ class value_initialized
|
||||
|
||||
value_initialized & operator=(value_initialized const & arg)
|
||||
{
|
||||
T & this_data = this->data();
|
||||
T const & arg_data = arg.data();
|
||||
this_data = arg_data;
|
||||
this->data() = arg_data;
|
||||
return *this;
|
||||
}
|
||||
|
||||
@@ -110,6 +98,18 @@ T& get ( value_initialized<T>& x )
|
||||
return x.data() ;
|
||||
}
|
||||
|
||||
|
||||
class initialized_value
|
||||
{
|
||||
public :
|
||||
|
||||
template <class T> operator T() const
|
||||
{
|
||||
return get( value_initialized<T>() );
|
||||
}
|
||||
};
|
||||
|
||||
|
||||
} // namespace boost
|
||||
|
||||
|
||||
|
||||
Reference in new issue
Block a user