boost-react-native-bundle

<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=US-ASCII"> <title>Using and building the library</title> <link rel="stylesheet" href="../../../doc/src/boostbook.css" type="text/css"> <meta name="generator" content="DocBook XSL Stylesheets V1.78.1"> <link rel="home" href="../index.html" title="The Boost C++ Libraries BoostBook Documentation Subset"> <link rel="up" href="../thread.html" title="Chapter 30. Thread 4.4.0"> <link rel="prev" href="../thread.html" title="Chapter 30. Thread 4.4.0"> <link rel="next" href="changes.html" title="History"> </head> <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"> <table cellpadding="2" width="100%"><tr> <td valign="top"><img alt="Boost C++ Libraries" width="277" height="86" src="../../../boost.png"></td> <td align="center"><a href="../../../index.html">Home</a></td> <td align="center"><a href="../../../libs/libraries.htm">Libraries</a></td> <td align="center"><a href="http://www.boost.org/users/people.html">People</a></td> <td align="center"><a href="http://www.boost.org/users/faq.html">FAQ</a></td> <td align="center"><a href="../../../more/index.htm">More</a></td> </tr></table> <hr> <div class="spirit-nav"> <a accesskey="p" href="../thread.html"><img src="../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../thread.html"><img src="../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="changes.html"><img src="../../../doc/src/images/next.png" alt="Next"></a> </div> <div class="section"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="thread.build"></a><a class="link" href="build.html" title="Using and building the library">Using and building the library</a> </h2></div></div></div> <div class="toc"><dl class="toc"> <dt><a href="build.html#thread.build.configuration">Configuration</a></dt> <dt><a href="build.html#thread.build.limitations">Limitations</a></dt> </dl></div> Boost.Thread is configured following the conventions used to build <a href="http://www.boost.org/doc/libs/1_48_0/libs/config/doc/html/boost_config/boost_macro_reference.html#boost_config.boost_macro_reference.macros_for_libraries_with_separate_source_code" target="_top">libraries with separate source code</a>. Boost.Thread will import/export the code only if the user has specifically asked for it, by defining either BOOST_ALL_DYN_LINK if they want all boost libraries to be dynamically linked, or BOOST_THREAD_DYN_LINK if they want just this one to be dynamically liked. The definition of these macros determines whether BOOST_THREAD_USE_DLL is defined. If BOOST_THREAD_USE_DLL is not defined, the library will define BOOST_THREAD_USE_DLL or BOOST_THREAD_USE_LIB depending on whether the platform. On non windows platforms BOOST_THREAD_USE_LIB is defined if is not defined. In windows platforms, BOOST_THREAD_USE_LIB is defined if BOOST_THREAD_USE_DLL and the compiler supports auto-tss cleanup with Boost.Threads (for the time been Msvc and Intel) The source code compiled when building the library defines a macros BOOST_THREAD_SOURCE that is used to import or export it. The user must not define this macro in any case. Boost.Thread depends on some non header-only libraries. <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"> Boost.System: This dependency is mandatory and you will need to link with the library. </li> <li class="listitem"> Boost.Chrono: This dependency is optional (see below how to configure) and you will need to link with the library if you use some of the time related interfaces. </li> <li class="listitem"> Boost.DateTime: This dependency is mandatory, but even if Boost.DateTime is a non header-only library Boost.Thread uses only parts that are header-only, so in principle you should not need to link with the library. </li> </ul></div> It seems that there are some IDE (as e.g. Visual Studio) that deduce the libraries that a program needs to link to inspecting the sources. Such IDE could force to link to Boost.DateTime and/or Boost.Chrono. As the single mandatory dependency is to Boost.System, the following <pre class="programlisting">bjam toolset=msvc-11.0 --build-type=complete --with-thread </pre> will install only boost_thread and boost_system. Users of such IDE should force the Boost.Chrono and Boost.DateTime build using <pre class="programlisting">bjam toolset=msvc-11.0 --build-type=complete --with-thread --with-chrono --with-date_time </pre> The following section describes all the macros used to configure Boost.Thread. <div class="section"> <div class="titlepage"><div><div><h3 class="title"> <a name="thread.build.configuration"></a><a class="link" href="build.html#thread.build.configuration" title="Configuration">Configuration</a> </h3></div></div></div> <div class="toc"><dl class="toc"> <dt><a href="build.html#thread.build.configuration.chrono">Boost.Chrono</a></dt> <dt><a href="build.html#thread.build.configuration.move">Boost.Move</a></dt> <dt><a href="build.html#thread.build.configuration.date_time">Boost.DateTime</a></dt> <dt><a href="build.html#thread.build.configuration.move0">Boost.Atomic</a></dt> <dt><a href="build.html#thread.build.configuration.thread_eq"><code class="computeroutput">boost::thread::operator==</code> deprecated</a></dt> <dt><a href="build.html#thread.build.configuration.condition">boost::condition deprecated</a></dt> <dt><a href="build.html#thread.build.configuration.nested_lock">Mutex nested lock types deprecated</a></dt> <dt><a href="build.html#thread.build.configuration.id">thread::id</a></dt> <dt><a href="build.html#thread.build.configuration.shared_gen">Shared Locking Generic</a></dt> <dt><a href="build.html#thread.build.configuration.shared_upwards">Shared Locking Upwards Conversion</a></dt> <dt><a href="build.html#thread.build.configuration.explicit_cnv">Explicit Lock Conversion</a></dt> <dt><a href="build.html#thread.build.configuration.future">unique_future versus future</a></dt> <dt><a href="build.html#thread.build.configuration.lazy">promise lazy initialization</a></dt> <dt><a href="build.html#thread.build.configuration.alloc">promise Allocator constructor</a></dt> <dt><a href="build.html#thread.build.configuration.terminate">Call to terminate if joinable</a></dt> <dt><a href="build.html#thread.build.configuration.once_flag">once_flag</a></dt> <dt><a href="build.html#thread.build.configuration.deprecated">Signature parameter for packaged_task</a></dt> <dt><a href="build.html#thread.build.configuration.thread_const">-var thread constructor with variadic rvalue parameters</a></dt> <dt><a href="build.html#thread.build.configuration.get_invalid">future<>::get() invalidates the future</a></dt> <dt><a href="build.html#thread.build.configuration.intr">Interruptions</a></dt> <dt><a href="build.html#thread.build.configuration.version">Version</a></dt> </dl></div> <div class="table"> <a name="thread.build.configuration.default_values_for_configurable_features"></a>Table 30.1. Default Values for Configurable Features <div class="table-contents"><table class="table" summary="Default Values for Configurable Features"> <colgroup> <col> <col> <col> <col> <col> </colgroup> <thead><tr> <th> Feature </th> <th> Anti-Feature </th> <th> V2 </th> <th> V3 </th> <th> V4 </th> </tr></thead> <tbody> <tr> <td> USES_CHRONO </td> <td> DONT_USE_CHRONO </td> <td> YES/NO </td> <td> YES/NO </td> <td> YES/NO </td> </tr> <tr> <td> PROVIDES_INTERRUPTIONS </td> <td> DONT_PROVIDE_INTERRUPTIONS </td> <td> YES </td> <td> YES </td> <td> YES </td> </tr> <tr> <td> THROW_IF_PRECONDITION_NOT_SATISFIED </td> <td> - </td> <td> NO </td> <td> NO </td> <td> NO </td> </tr> <tr> <td> PROVIDES_PROMISE_LAZY </td> <td> DONT_PROVIDE_PROMISE_LAZY </td> <td> YES </td> <td> NO </td> <td> NO </td> </tr> <tr> <td> PROVIDES_BASIC_THREAD_ID </td> <td> DONT_PROVIDE_BASIC_THREAD_ID </td> <td> NO </td> <td> YES </td> <td> YES </td> </tr> <tr> <td> PROVIDES_GENERIC_SHARED_MUTEX_ON_WIN </td> <td> DONT_PROVIDE_GENERIC_SHARED_MUTEX_ON_WIN </td> <td> NO </td> <td> YES </td> <td> YES </td> </tr> <tr> <td> PROVIDES_SHARED_MUTEX_UPWARDS_CONVERSION </td> <td> DONT_PROVIDE_SHARED_MUTEX_UPWARDS_CONVERSION </td> <td> NO </td> <td> YES </td> <td> YES </td> </tr> <tr> <td> PROVIDES_EXPLICIT_LOCK_CONVERSION </td> <td> DONT_PROVIDE_EXPLICIT_LOCK_CONVERSION </td> <td> NO </td> <td> YES </td> <td> YES </td> </tr> <tr> <td> PROVIDES_FUTURE </td> <td> DONT_PROVIDE_FUTURE </td> <td> NO </td> <td> YES </td> <td> YES </td> </tr> <tr> <td> PROVIDES_FUTURE_CTOR_ALLOCATORS </td> <td> DONT_PROVIDE_FUTURE_CTOR_ALLOCATORS </td> <td> NO </td> <td> YES </td> <td> YES </td> </tr> <tr> <td> PROVIDES_THREAD_DESTRUCTOR_CALLS_TERMINATE_IF_JOINABLE </td> <td> DONT_PROVIDE_THREAD_DESTRUCTOR_CALLS_TERMINATE_IF_JOINABLE </td> <td> NO </td> <td> YES </td> <td> YES </td> </tr> <tr> <td> PROVIDES_THREAD_MOVE_ASSIGN_CALLS_TERMINATE_IF_JOINABLE </td> <td> DONT_PROVIDE_THREAD_MOVE_ASSIGN_CALLS_TERMINATE_IF_JOINABLE </td> <td> NO </td> <td> YES </td> <td> YES </td> </tr> <tr> <td> PROVIDES_ONCE_CXX11 </td> <td> DONT_PROVIDE_ONCE_CXX11 </td> <td> NO </td> <td> YES </td> <td> YES </td> </tr> <tr> <td> USES_MOVE </td> <td> DONT_USE_MOVE </td> <td> NO </td> <td> YES </td> <td> YES </td> </tr> <tr> <td> USES_DATETIME </td> <td> DONT_USE_DATETIME </td> <td> YES/NO </td> <td> YES/NO </td> <td> YES/NO </td> </tr> <tr> <td> PROVIDES_THREAD_EQ </td> <td> DONT_PROVIDE_THREAD_EQ </td> <td> YES </td> <td> YES </td> <td> NO </td> </tr> <tr> <td> PROVIDES_CONDITION </td> <td> DONT_PROVIDE_CONDITION </td> <td> YES </td> <td> YES </td> <td> NO </td> </tr> <tr> <td> PROVIDES_NESTED_LOCKS </td> <td> DONT_PROVIDE_NESTED_LOCKS </td> <td> YES </td> <td> YES </td> <td> NO </td> </tr> <tr> <td> PROVIDES_SIGNATURE_PACKAGED_TASK </td> <td> DONT_PROVIDE_SIGNATURE_PACKAGED_TASK </td> <td> NO </td> <td> NO </td> <td> YES </td> </tr> <tr> <td> PROVIDES_FUTURE_INVALID_AFTER_GET </td> <td> DONT_PROVIDE_FUTURE_INVALID_AFTER_GET </td> <td> NO </td> <td> NO </td> <td> YES </td> </tr> <tr> <td> PROVIDES_VARIADIC_THREAD </td> <td> DONT_PROVIDE_VARIADIC_THREAD </td> <td> NO </td> <td> NO </td> <td> C++11 </td> </tr> </tbody> </table></div> </div> <div class="section"> <div class="titlepage"><div><div><h4 class="title"> <a name="thread.build.configuration.chrono"></a><a class="link" href="build.html#thread.build.configuration.chrono" title="Boost.Chrono">Boost.Chrono</a> </h4></div></div></div> Boost.Thread uses by default Boost.Chrono for the time related functions and define <code class="computeroutput">BOOST_THREAD_USES_CHRONO</code> if <code class="computeroutput">BOOST_THREAD_DONT_USE_CHRONO</code> is not defined. The user should define <code class="computeroutput">BOOST_THREAD_DONT_USE_CHRONO</code> for compilers that don't work well with Boost.Chrono. <div class="warning"><table border="0" summary="Warning"> <tr> <td rowspan="2" align="center" valign="top" width="25"><img alt="[Warning]" src="../../../doc/src/images/warning.png"></td> <th align="left">Warning</th> </tr> <tr><td align="left" valign="top"> When defined BOOST_THREAD_PLATFORM_WIN32 BOOST_THREAD_USES_CHRONO is defined independently of user settings. </td></tr> </table></div> </div> <div class="section"> <div class="titlepage"><div><div><h4 class="title"> <a name="thread.build.configuration.move"></a><a class="link" href="build.html#thread.build.configuration.move" title="Boost.Move">Boost.Move</a> </h4></div></div></div> Boost.Thread uses by default an internal move semantic implementation. Since version 3.0.0 you can use the move emulation emulation provided by Boost.Move. When <code class="computeroutput">BOOST_THREAD_VERSION==2</code> define <code class="computeroutput">BOOST_THREAD_USES_MOVE </code> if you want to use Boost.Move interface. When <code class="computeroutput">BOOST_THREAD_VERSION>=3</code> define <code class="computeroutput">BOOST_THREAD_DONT_USE_MOVE </code> if you don't want to use Boost.Move interface. </div> <div class="section"> <div class="titlepage"><div><div><h4 class="title"> <a name="thread.build.configuration.date_time"></a><a class="link" href="build.html#thread.build.configuration.date_time" title="Boost.DateTime">Boost.DateTime</a> </h4></div></div></div> The Boost.DateTime time related functions introduced in Boost 1.35.0, using the <a class="link" href="../date_time.html" title="Chapter 9. Boost.Date_Time">Boost.Date_Time</a> library are deprecated. These include (but are not limited to): <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"> <a class="link" href="thread_management.html#thread.thread_management.this_thread.sleep" title="Non-member function sleep() DEPRECATED"><code class="computeroutput">boost::this_thread::sleep()</code></a> </li> <li class="listitem"> <a class="link" href="thread_management.html#thread.thread_management.thread.timed_join" title="Member function timed_join() DEPRECATED"><code class="computeroutput">timed_join()</code></a> </li> <li class="listitem"> <a class="link" href="synchronization.html#thread.synchronization.condvar_ref.condition_variable.timed_wait" title="bool timed_wait(boost::unique_lock<boost::mutex>& lock,boost::system_time const& abs_time)"><code class="computeroutput">timed_wait()</code></a> </li> <li class="listitem"> <a class="link" href="synchronization.html#thread.synchronization.mutex_concepts.timed_lockable.timed_lock" title="m.timed_lock(abs_time)"><code class="computeroutput">timed_lock()</code></a> </li> </ul></div> When <code class="computeroutput">BOOST_THREAD_VERSION<=3</code> && defined BOOST_THREAD_PLATFORM_PTHREAD define <code class="computeroutput">BOOST_THREAD_DONT_USE_DATETIME</code> if you don't want to use Boost.DateTime related interfaces. When <code class="computeroutput">BOOST_THREAD_VERSION>3</code> && defined BOOST_THREAD_PLATFORM_PTHREAD define <code class="computeroutput">BOOST_THREAD_USES_DATETIME</code> if you want to use Boost.DateTime related interfaces. <div class="warning"><table border="0" summary="Warning"> <tr> <td rowspan="2" align="center" valign="top" width="25"><img alt="[Warning]" src="../../../doc/src/images/warning.png"></td> <th align="left">Warning</th> </tr> <tr><td align="left" valign="top"> When defined BOOST_THREAD_PLATFORM_WIN32 BOOST_THREAD_USES_DATETIME is defined independently of user settings. </td></tr> </table></div> </div> <div class="section"> <div class="titlepage"><div><div><h4 class="title"> <a name="thread.build.configuration.move0"></a><a class="link" href="build.html#thread.build.configuration.move0" title="Boost.Atomic">Boost.Atomic</a> </h4></div></div></div> Boost.Thread uses by default an Boost.Atomic in POSIX platforms to implement call_once.. Define <code class="computeroutput">BOOST_THREAD_USES_ATOMIC </code> if you want to use Boost.Atomic. Define <code class="computeroutput">BOOST_THREAD_DONT_USE_ATOMIC </code> if you don't want to use Boost.Atomic or if it is not supported in your platform. </div> <div class="section"> <div class="titlepage"><div><div><h4 class="title"> <a name="thread.build.configuration.thread_eq"></a><a class="link" href="build.html#thread.build.configuration.thread_eq" title="boost::thread::operator== deprecated"><code class="computeroutput">boost::thread::operator==</code> deprecated</a> </h4></div></div></div> The following operators are deprecated: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"> <code class="computeroutput">boost::thread::operator==</code> </li> <li class="listitem"> <code class="computeroutput">boost::thread::operator!=</code> </li> </ul></div> When <code class="computeroutput">BOOST_THREAD_PROVIDES_THREAD_EQ</code> is defined Boost.Thread provides these deprecated feature. Use instead <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"> <code class="computeroutput">boost::thread::id::operator==</code> </li> <li class="listitem"> <code class="computeroutput">boost::thread::id::operator!=</code> </li> </ul></div> <div class="warning"><table border="0" summary="Warning"> <tr> <td rowspan="2" align="center" valign="top" width="25"><img alt="[Warning]" src="../../../doc/src/images/warning.png"></td> <th align="left">Warning</th> </tr> <tr><td align="left" valign="top"> This is a breaking change respect to version 1.x. </td></tr> </table></div> When <code class="computeroutput">BOOST_THREAD_VERSION>=4</code> define <code class="computeroutput">BOOST_THREAD_PROVIDES_THREAD_EQ </code> if you want this feature. When <code class="computeroutput">BOOST_THREAD_VERSION<4</code> define <code class="computeroutput">BOOST_THREAD_DONT_PROVIDE_THREAD_EQ </code> if you don't want this feature. </div> <div class="section"> <div class="titlepage"><div><div><h4 class="title"> <a name="thread.build.configuration.condition"></a><a class="link" href="build.html#thread.build.configuration.condition" title="boost::condition deprecated">boost::condition deprecated</a> </h4></div></div></div> <code class="computeroutput">boost::condition</code> is deprecated. When <code class="computeroutput">BOOST_THREAD_PROVIDES_CONDITION</code> is defined Boost.Thread provides this deprecated feature. Use instead <code class="computeroutput">boost::condition_variable_any</code>. <div class="warning"><table border="0" summary="Warning"> <tr> <td rowspan="2" align="center" valign="top" width="25"><img alt="[Warning]" src="../../../doc/src/images/warning.png"></td> <th align="left">Warning</th> </tr> <tr><td align="left" valign="top"> This is a breaking change respect to version 1.x. </td></tr> </table></div> When <code class="computeroutput">BOOST_THREAD_VERSION>3</code> define <code class="computeroutput">BOOST_THREAD_PROVIDES_CONDITION</code> if you want this feature. When <code class="computeroutput">BOOST_THREAD_VERSION<=3</code> define <code class="computeroutput">BOOST_THREAD_DONT_PROVIDE_CONDITION</code> if you don't want this feature. </div> <div class="section"> <div class="titlepage"><div><div><h4 class="title"> <a name="thread.build.configuration.nested_lock"></a><a class="link" href="build.html#thread.build.configuration.nested_lock" title="Mutex nested lock types deprecated">Mutex nested lock types deprecated</a> </h4></div></div></div> The following nested typedefs are deprecated: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"> <code class="computeroutput">boost::mutex::scoped_lock</code>, </li> <li class="listitem"> <code class="computeroutput">boost::mutex::scoped_try_lock</code>, </li> <li class="listitem"> <code class="computeroutput">boost::timed_mutex::scoped_lock</code> </li> <li class="listitem"> <code class="computeroutput">boost::timed_mutex::scoped_try_lock</code> </li> <li class="listitem"> <code class="computeroutput">boost::timed_mutex::timed_scoped_timed_lock</code> </li> <li class="listitem"> <code class="computeroutput">boost::recursive_mutex::scoped_lock</code>, </li> <li class="listitem"> <code class="computeroutput">boost::recursive_mutex::scoped_try_lock</code>, </li> <li class="listitem"> <code class="computeroutput">boost::recursive_timed_mutex::scoped_lock</code> </li> <li class="listitem"> <code class="computeroutput">boost::recursive_timed_mutex::scoped_try_lock</code> </li> <li class="listitem"> <code class="computeroutput">boost::recursive_timed_mutex::timed_scoped_timed_lock</code> </li> </ul></div> When <code class="computeroutput">BOOST_THREAD_PROVIDES_NESTED_LOCKS</code> is defined Boost.Thread provides these deprecated feature. Use instead * <code class="computeroutput">boost::unique_lock<boost::mutex></code>, * <code class="computeroutput">boost::unique_lock<boost::mutex></code> with the <code class="computeroutput">try_to_lock_t</code> constructor, * <code class="computeroutput">boost::unique_lock<boost::timed_mutex></code> * <code class="computeroutput">boost::unique_lock<boost::timed_mutex></code> with the <code class="computeroutput">try_to_lock_t</code> constructor * <code class="computeroutput">boost::unique_lock<boost::timed_mutex></code> * <code class="computeroutput">boost::unique_lock<boost::recursive_mutex></code>, * <code class="computeroutput">boost::unique_lock<boost::recursive_mutex></code> with the <code class="computeroutput">try_to_lock_t</code> constructor, * <code class="computeroutput">boost::unique_lock<boost::recursive_timed_mutex></code> * <code class="computeroutput">boost::unique_lock<boost::recursive_timed_mutex></code> with the <code class="computeroutput">try_to_lock_t</code> constructor * <code class="computeroutput">boost::unique_lock<boost::recursive_timed_mutex></code> <div class="warning"><table border="0" summary="Warning"> <tr> <td rowspan="2" align="center" valign="top" width="25"><img alt="[Warning]" src="../../../doc/src/images/warning.png"></td> <th align="left">Warning</th> </tr> <tr><td align="left" valign="top"> This is a breaking change respect to version 1.x. </td></tr> </table></div> When <code class="computeroutput">BOOST_THREAD_VERSION>=4</code> define <code class="computeroutput">BOOST_THREAD_PROVIDES_NESTED_LOCKS</code> if you want these features. When <code class="computeroutput">BOOST_THREAD_VERSION<4</code> define <code class="computeroutput">BOOST_THREAD_DONT_PROVIDE_NESTED_LOCKS</code> if you don't want thes features. </div> <div class="section"> <div class="titlepage"><div><div><h4 class="title"> <a name="thread.build.configuration.id"></a><a class="link" href="build.html#thread.build.configuration.id" title="thread::id">thread::id</a> </h4></div></div></div> Boost.Thread uses by default a thread::id on Posix based on the pthread type (BOOST_THREAD_PROVIDES_BASIC_THREAD_ID). For backward compatibility and also for compilers that don't work well with this modification the user can define <code class="computeroutput">BOOST_THREAD_DONT_PROVIDE_BASIC_THREAD_ID</code>. Define <code class="computeroutput">BOOST_THREAD_DONT_PROVIDE_BASIC_THREAD_ID </code> if you don't want these features. </div> <div class="section"> <div class="titlepage"><div><div><h4 class="title"> <a name="thread.build.configuration.shared_gen"></a><a class="link" href="build.html#thread.build.configuration.shared_gen" title="Shared Locking Generic">Shared Locking Generic</a> </h4></div></div></div> The shared mutex implementation on Windows platform provides currently less functionality than the generic one that is used for PTheads based platforms. In order to have access to these functions, the user needs to define <code class="computeroutput">BOOST_THREAD_PROVIDES_GENERIC_SHARED_MUTEX_ON_WIN</code> to use the generic implementation, that while could be less efficient, provides all the functions. When <code class="computeroutput">BOOST_THREAD_VERSION==2</code> define <code class="computeroutput">BOOST_THREAD_PROVIDES_GENERIC_SHARED_MUTEX_ON_WIN </code> if you want these features. When <code class="computeroutput">BOOST_THREAD_VERSION>=3</code> define <code class="computeroutput">BOOST_THREAD_DONT_PROVIDE_GENERIC_SHARED_MUTEX_ON_WIN </code> if you don't want these features. </div> <div class="section"> <div class="titlepage"><div><div><h4 class="title"> <a name="thread.build.configuration.shared_upwards"></a><a class="link" href="build.html#thread.build.configuration.shared_upwards" title="Shared Locking Upwards Conversion">Shared Locking Upwards Conversion</a> </h4></div></div></div> Boost.Threads includes in version 3 the Shared Locking Upwards Conversion as defined in <a href="http://home.roadrunner.com/~hinnant/bloomington/shared_mutex.html" target="_top">Shared Locking</a>. These conversions need to be used carefully to avoid deadlock or livelock. The user need to define explicitly <code class="computeroutput">BOOST_THREAD_PROVIDES_SHARED_MUTEX_UPWARDS_CONVERSION</code> to get these upwards conversions. When <code class="computeroutput">BOOST_THREAD_VERSION==2</code> define <code class="computeroutput">BOOST_THREAD_PROVIDES_SHARED_MUTEX_UPWARDS_CONVERSION </code> if you want these features. When <code class="computeroutput">BOOST_THREAD_VERSION>=3</code> define <code class="computeroutput">BOOST_THREAD_DONT_PROVIDE_SHARED_MUTEX_UPWARDS_CONVERSION </code> if you don't want these features. </div> <div class="section"> <div class="titlepage"><div><div><h4 class="title"> <a name="thread.build.configuration.explicit_cnv"></a><a class="link" href="build.html#thread.build.configuration.explicit_cnv" title="Explicit Lock Conversion">Explicit Lock Conversion</a> </h4></div></div></div> In <a href="http://home.roadrunner.com/~hinnant/bloomington/shared_mutex.html" target="_top">Shared Locking</a> the lock conversions are explicit. As this explicit conversion breaks the lock interfaces, it is provided only if the <code class="computeroutput">BOOST_THREAD_PROVIDES_EXPLICIT_LOCK_CONVERSION</code> is defined. When <code class="computeroutput">BOOST_THREAD_VERSION==2</code> define <code class="computeroutput">BOOST_THREAD_PROVIDES_EXPLICIT_LOCK_CONVERSION </code> if you want these features. When <code class="computeroutput">BOOST_THREAD_VERSION==3</code> define <code class="computeroutput">BOOST_THREAD_DONT_PROVIDE_EXPLICIT_LOCK_CONVERSION </code> if you don't want these features. </div> <div class="section"> <div class="titlepage"><div><div><h4 class="title"> <a name="thread.build.configuration.future"></a><a class="link" href="build.html#thread.build.configuration.future" title="unique_future versus future">unique_future versus future</a> </h4></div></div></div> C++11 uses <code class="computeroutput">std::future</code>. Versions of Boost.Thread previous to version 3.0.0 uses <code class="computeroutput">boost:unique_future</code>. Since version 3.0.0 <code class="computeroutput">boost::future</code> replaces <code class="computeroutput">boost::unique_future</code> when <code class="computeroutput">BOOST_THREAD_PROVIDES_FUTURE</code> is defined. The documentation doesn't contains anymore however <code class="computeroutput">boost::unique_future</code>. When <code class="computeroutput">BOOST_THREAD_VERSION==2</code> define <code class="computeroutput">BOOST_THREAD_PROVIDES_FUTURE</code> if you want to use boost::future. When <code class="computeroutput">BOOST_THREAD_VERSION>=3</code> define <code class="computeroutput">BOOST_THREAD_DONT_PROVIDE_FUTURE</code> if you want to use boost::unique_future. </div> <div class="section"> <div class="titlepage"><div><div><h4 class="title"> <a name="thread.build.configuration.lazy"></a><a class="link" href="build.html#thread.build.configuration.lazy" title="promise lazy initialization">promise lazy initialization</a> </h4></div></div></div> C++11 promise initialize the associated state at construction time. Versions of Boost.Thread previous to version 3.0.0 initialize it lazily at any point in time in which this associated state is needed. Since version 3.0.0 this difference in behavior can be configured. When <code class="computeroutput">BOOST_THREAD_PROVIDES_PROMISE_LAZY</code> is defined the backward compatible behavior is provided. When <code class="computeroutput">BOOST_THREAD_VERSION==2</code> define <code class="computeroutput">BOOST_THREAD_DONT_PROVIDE_PROMISE_LAZY </code> if you want to use boost::future. When <code class="computeroutput">BOOST_THREAD_VERSION>=3</code> define <code class="computeroutput">BOOST_THREAD_PROVIDES_PROMISE_LAZY </code> if you want to use boost::unique_future. </div> <div class="section"> <div class="titlepage"><div><div><h4 class="title"> <a name="thread