Boost-Commit mailing page: [Boost-commit] svn:boost r81443 - in website/public_html/live/doc/fixes: boost_1_51_0 boost_1_51_0/libs boost_1_51_0/libs/config boost_1_51_0/libs/config/doc boost_1_51_0/libs/config/doc/html boost_1_51_0/libs/config/doc/html/boost_config boost_1_52_0 boost_1_52_0/libs boost_1_52_0/libs/config boost_1_52_0/libs/config/doc boost_1_52_0/libs/config/doc/html boost_1_52_0/libs/config/doc/html/boost

Date view	Thread view	Subject view	Author view

Subject: [Boost-commit] svn:boost r81443 - in website/public_html/live/doc/fixes: boost_1_51_0 boost_1_51_0/libs boost_1_51_0/libs/config boost_1_51_0/libs/config/doc boost_1_51_0/libs/config/doc/html boost_1_51_0/libs/config/doc/html/boost_config boost_1_52_0 boost_1_52_0/libs boost_1_52_0/libs/config boost_1_52_0/libs/config/doc boost_1_52_0/libs/config/doc/html boost_1_52_0/libs/config/doc/html/boost_config
From: dnljms_at_[hidden]
Date: 2012-11-20 15:40:11

Next message: marshall_at_[hidden]: "[Boost-commit] svn:boost r81444 - in trunk/boost: chrono signals2 signals2/detail"
Previous message: marshall_at_[hidden]: "[Boost-commit] svn:boost r81442 - in trunk/boost: detail random random/detail"

Author: danieljames
Date: 2012-11-20 15:40:09 EST (Tue, 20 Nov 2012)
New Revision: 81443
URL: http://svn.boost.org/trac/boost/changeset/81443

Log:
Website: Update config docs for 1.51 and 1.52. Refs #7676.

Added:
   website/public_html/live/doc/fixes/boost_1_51_0/
   website/public_html/live/doc/fixes/boost_1_51_0/libs/
   website/public_html/live/doc/fixes/boost_1_51_0/libs/config/
   website/public_html/live/doc/fixes/boost_1_51_0/libs/config/doc/
   website/public_html/live/doc/fixes/boost_1_51_0/libs/config/doc/html/
   website/public_html/live/doc/fixes/boost_1_51_0/libs/config/doc/html/boost_config/
   website/public_html/live/doc/fixes/boost_1_51_0/libs/config/doc/html/boost_config/acknowledgements.html (contents, props changed)
   website/public_html/live/doc/fixes/boost_1_51_0/libs/config/doc/html/boost_config/boost_macro_reference.html (contents, props changed)
   website/public_html/live/doc/fixes/boost_1_51_0/libs/config/doc/html/boost_config/guidelines_for_boost_authors.html (contents, props changed)
   website/public_html/live/doc/fixes/boost_1_51_0/libs/config/doc/html/boost_config/rationale.html (contents, props changed)
   website/public_html/live/doc/fixes/boost_1_51_0/libs/config/doc/html/index.html (contents, props changed)
   website/public_html/live/doc/fixes/boost_1_52_0/
   website/public_html/live/doc/fixes/boost_1_52_0/libs/
   website/public_html/live/doc/fixes/boost_1_52_0/libs/config/
   website/public_html/live/doc/fixes/boost_1_52_0/libs/config/doc/
   website/public_html/live/doc/fixes/boost_1_52_0/libs/config/doc/html/
   website/public_html/live/doc/fixes/boost_1_52_0/libs/config/doc/html/boost_config/
   website/public_html/live/doc/fixes/boost_1_52_0/libs/config/doc/html/boost_config/acknowledgements.html (contents, props changed)
   website/public_html/live/doc/fixes/boost_1_52_0/libs/config/doc/html/boost_config/boost_macro_reference.html (contents, props changed)
   website/public_html/live/doc/fixes/boost_1_52_0/libs/config/doc/html/boost_config/guidelines_for_boost_authors.html (contents, props changed)
   website/public_html/live/doc/fixes/boost_1_52_0/libs/config/doc/html/boost_config/rationale.html (contents, props changed)
   website/public_html/live/doc/fixes/boost_1_52_0/libs/config/doc/html/index.html (contents, props changed)

Added: website/public_html/live/doc/fixes/boost_1_51_0/libs/config/doc/html/boost_config/acknowledgements.html
==============================================================================
--- (empty file)
+++ website/public_html/live/doc/fixes/boost_1_51_0/libs/config/doc/html/boost_config/acknowledgements.html 2012-11-20 15:40:09 EST (Tue, 20 Nov 2012)
@@ -0,0 +1,62 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
+<title>Acknowledgements</title>
+<link rel="stylesheet" href="../../../../../doc/src/boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="../index.html" title="Boost.Config">
+<link rel="up" href="../index.html" title="Boost.Config">
+<link rel="prev" href="rationale.html" title="Rationale">
+</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">Home</td>
+<td align="center">Libraries</td>
+<td align="center">People</td>
+<td align="center">FAQ</td>
+<td align="center">More</td>
+</tr></table>
+<hr>
+<div class="spirit-nav">
+<a accesskey="p" href="rationale.html"><img src="../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.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>
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="boost_config.acknowledgements"></a><a class="link" href="acknowledgements.html" title="Acknowledgements">Acknowledgements</a>
+</h2></div></div></div>
+
+ Beman Dawes provided the original <code class="computeroutput">config.hpp</code> and
+ part of this document.
+ 
+
+ Vesa Karvonen provided a description of the principles (see <a class="link" href="rationale.html" title="Rationale">rationale</a>)
+ and put together an early version of the current configuration setup.
+ 
+
+ John Maddock put together the configuration current code, the test programs,
+ the configuration script and the reference section of this document.
+ 
+
+ Matias Capeletto converted the docs to quickbook format.
+ 
+
+ Numerous boost members, past and present, have contributed fixes to boost's
+ configuration.
+ 
+</div>
+<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
+<td align="left"></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Beman Dawes, Vesa Karvonen, John
+ Maddock
+ 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)
+ 
+</div></td>
+</tr></table>
+<hr>
+<div class="spirit-nav">
+<a accesskey="p" href="rationale.html"><img src="../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.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>
+</div>
+</body>
+</html>

Added: website/public_html/live/doc/fixes/boost_1_51_0/libs/config/doc/html/boost_config/boost_macro_reference.html
==============================================================================
--- (empty file)
+++ website/public_html/live/doc/fixes/boost_1_51_0/libs/config/doc/html/boost_config/boost_macro_reference.html 2012-11-20 15:40:09 EST (Tue, 20 Nov 2012)
@@ -0,0 +1,5050 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
+<title>Boost Macro Reference</title>
+<link rel="stylesheet" href="../../../../../doc/src/boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="../index.html" title="Boost.Config">
+<link rel="up" href="../index.html" title="Boost.Config">
+<link rel="prev" href="../index.html" title="Boost.Config">
+<link rel="next" href="guidelines_for_boost_authors.html" title="Guidelines for Boost Authors">
+</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">Home</td>
+<td align="center">Libraries</td>
+<td align="center">People</td>
+<td align="center">FAQ</td>
+<td align="center">More</td>
+</tr></table>
+<hr>
+<div class="spirit-nav">
+<a accesskey="p" href="../index.html"><img src="../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.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="guidelines_for_boost_authors.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="boost_config.boost_macro_reference"></a><a class="link" href="boost_macro_reference.html" title="Boost Macro Reference">Boost Macro Reference</a>
+</h2></div></div></div>
+<div class="toc"><dl>
+<dt><a href="boost_macro_reference.html#boost_config.boost_macro_reference.macros_that_describe_c__03_defects">Macros
+ that describe C++03 defects</a></dt>
+<dt><a href="boost_macro_reference.html#boost_config.boost_macro_reference.macros_that_describe_optional_features">Macros
+ that describe optional features</a></dt>
+<dt><a href="boost_macro_reference.html#boost_config.boost_macro_reference.macros_that_describe_possible_c___future_features">Macros
+ that describe possible C++ future features</a></dt>
+<dt><a href="boost_macro_reference.html#boost_config.boost_macro_reference.macros_that_describe_c__11_features_not_supported">Macros
+ that describe C++11 features not supported</a></dt>
+<dt><a href="boost_macro_reference.html#boost_config.boost_macro_reference.macros_that_allow_use_of_c__11_features_with_c__03_compilers">Macros
+ that allow use of C++11 features with C++03 compilers</a></dt>
+<dt><a href="boost_macro_reference.html#boost_config.boost_macro_reference.boost_helper_macros">Boost
+ Helper Macros</a></dt>
+<dt><a href="boost_macro_reference.html#boost_config.boost_macro_reference.boost_informational_macros">Boost
+ Informational Macros</a></dt>
+<dt><a href="boost_macro_reference.html#boost_config.boost_macro_reference.boost_deprecated_macros">Boost
+ Deprecated Macros</a></dt>
+<dt><a href="boost_macro_reference.html#boost_config.boost_macro_reference.macros_for_libraries_with_separate_source_code">Macros
+ for libraries with separate source code</a></dt>
+</dl></div>
+<div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="boost_config.boost_macro_reference.macros_that_describe_c__03_defects"></a><a name="config_defects"></a><a class="link" href="boost_macro_reference.html#boost_config.boost_macro_reference.macros_that_describe_c__03_defects" title="Macros that describe C++03 defects">Macros
+ that describe C++03 defects</a>
+</h3></div></div></div>
+
+ The following macros all describe features that are required by the C++03
+ standard, if one of the following macros is defined, then it represents a
+ defect in the compiler's conformance with the 2003 standard.
+ 
+<div class="informaltable"><table class="table">
+<colgroup>
+<col>
+<col>
+<col>
+</colgroup>
+<thead><tr>
+<th>
+ 
+ Macro
+ 
+ </th>
+<th>
+ 
+ Section
+ 
+ </th>
+<th>
+ 
+ Description
+ 
+ </th>
+</tr></thead>
+<tbody>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_BCB_PARTIAL_SPECIALIZATION_BUG</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ The compiler exibits certain partial specialisation bug - probably
+ Borland C++ Builder specific.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_FUNCTION_SCOPE_USING_DECLARATION_BREAKS_ADL</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ Argument dependent lookup fails if there is a using declaration
+ for the symbol being looked up in the current scope. For example,
+ using <code class="computeroutput">boost::get_pointer</code>; prevents ADL from
+ finding overloads of <code class="computeroutput">get_pointer</code>
+ in namespaces nested inside boost (but not elsewhere). Probably
+ Borland specific.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_ADL_BARRIER</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ The compiler locates and searches namespaces that it should *not*
+ in fact search when performing argument dependent lookup.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_ARGUMENT_DEPENDENT_LOOKUP</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ Compiler does not implement argument-dependent lookup (also named
+ Koenig lookup); see std::3.4.2 [basic.koenig.lookup]
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_AUTO_PTR</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ If the compiler / library supplies non-standard or broken <code class="computeroutput">std::auto_ptr</code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_COMPLETE_VALUE_INITIALIZATION</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ Compiler has not completely implemented value-initialization. See
+ also <a href="../../../../utility/value_init.htm#compiler_issues" target="_top">The
+ Utility/Value Init docs</a>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CTYPE_FUNCTIONS</code>
+ 
+ </td>
+<td>
+ 
+ Platform
+ 
+ </td>
+<td>
+ 
+ The Platform does not provide functions for the character-classifying
+ operations <code class="computeroutput"><ctype.h></code> and <code class="computeroutput"><cctype></code>,
+ only macros.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CV_SPECIALIZATIONS</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ If template specialisations for cv-qualified types conflict with
+ a specialisation for a cv-unqualififed type.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CV_VOID_SPECIALIZATIONS</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ If template specialisations for cv-void types conflict with a specialisation
+ for void.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CWCHAR</code>
+ 
+ </td>
+<td>
+ 
+ Platform
+ 
+ </td>
+<td>
+ 
+ The Platform does not provide <code class="computeroutput"><wchar.h></code>
+ and <code class="computeroutput"><cwchar></code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CWCTYPE</code>
+ 
+ </td>
+<td>
+ 
+ Platform
+ 
+ </td>
+<td>
+ 
+ The Platform does not provide <code class="computeroutput"><wctype.h></code>
+ and <code class="computeroutput"><cwctype></code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_FENV_H</code>
+ 
+ </td>
+<td>
+ 
+ Platform, Standard library
+ 
+ </td>
+<td>
+ 
+ The C standard library doesn't provide <code class="computeroutput"><fenv.h></code>.
+ <boost/detail/fenv.hpp>
+ should be included instead of <code class="computeroutput"><fenv.h></code>
+ for maximum portability on platforms which do provide <code class="computeroutput"><fenv.h></code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_DEPENDENT_NESTED_DERIVATIONS</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ The compiler fails to compile a nested class that has a dependent
+ base class:
+
+<pre xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="table-programlisting">template<typename T>
+struct foo : {
+ template<typename U>
+ struct bar : public U {};
+</pre>
+
+ };
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_DEPENDENT_TYPES_IN_TEMPLATE_VALUE_PARAMETERS</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ Template value parameters cannot have a dependent type, for example:
+
+<pre xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="table-programlisting">template<class T, typename T::type value>
+class X { ... };
+</pre>
+
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_EXCEPTION_STD_NAMESPACE</code>
+ 
+ </td>
+<td>
+ 
+ Standard Library
+ 
+ </td>
+<td>
+ 
+ The standard library does not put some or all of the contents of
+ <code class="computeroutput"><exception></code> in namespace std.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_EXCEPTIONS</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ The compiler does not support exception handling (this setting
+ is typically required by many C++ compilers for embedded platforms).
+ Note that there is no requirement for boost libraries to honor
+ this configuration setting - indeed doing so may be impossible
+ in some cases. Those libraries that do honor this will typically
+ abort if a critical error occurs - you have been warned!
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_EXPLICIT_FUNCTION_TEMPLATE_ARGUMENTS</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ Can only use deduced template arguments when calling function template
+ instantiations.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_FUNCTION_TEMPLATE_ORDERING</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ The compiler does not perform function template ordering or its
+ function template ordering is incorrect.
+
+<pre xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="table-programlisting">// #1
+template<class T> void f(T);
+
+// #2
+template<class T,class U> void f(T(*)(U));
+
+void bar(int);
+
+f(&bar); // should choose #2.
+</pre>
+
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_INCLASS_MEMBER_INITIALIZATION</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ Compiler violates std::9.4.2/4.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_INTRINSIC_WCHAR_T</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ The C++ implementation does not provide <code class="computeroutput">wchar_t</code>,
+ or it is really a synonym for another integral type. Use this symbol
+ to decide whether it is appropriate to explicitly specialize a
+ template on <code class="computeroutput">wchar_t</code>
+ if there is already a specialization for other integer types.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_IOSFWD</code>
+ 
+ </td>
+<td>
+ 
+ std lib
+ 
+ </td>
+<td>
+ 
+ The standard library lacks <code class="computeroutput"><iosfwd></code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_IOSTREAM</code>
+ 
+ </td>
+<td>
+ 
+ std lib
+ 
+ </td>
+<td>
+ 
+ The standard library lacks <code class="computeroutput"><iostream></code>,
+ <code class="computeroutput"><istream></code> or <code class="computeroutput"><ostream></code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_IS_ABSTRACT</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ The C++ compiler does not support SFINAE with abstract types, this
+ is covered by <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/cwg_defects.html#337" target="_top">Core
+ Language DR337</a>, but is not part of the current standard.
+ Fortunately most compilers that support SFINAE also support this
+ DR.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_LIMITS</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The C++ implementation does not provide the <code class="computeroutput"><limits></code>
+ header. Never check for this symbol in library code; always include
+ <code class="computeroutput"><boost/limits.hpp></code>, which guarantees to provide
+ <code class="computeroutput">std::numeric_limits</code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_NUMERIC_LIMITS</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ C++11 additions to <code class="computeroutput">std::numeric_limits</code>
+ are not available for use. <code class="computeroutput">static
+ function numeric_limits<T>::lowest()</code> the lowest finite value representable
+ by the numeric type. <code class="computeroutput">static
+ int const
+ max_digits10</code> the number
+ of decimal digits that are required to make sure that two distinct
+ values of the type have distinct decimal representations. <code class="computeroutput">template<>
+ class numeric_limits<char16_t>;</code>, see also <code class="computeroutput">BOOST_NO_CXX11_CHAR16_T</code>,
+ <code class="computeroutput">template<>
+ class numeric_limits<char32_t>;</code> see also <code class="computeroutput">BOOST_NO_CXX11_CHAR32_T</code>.
+ Replaces BOOST_NO_NUMERIC_LIMITS_LOWEST.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_LIMITS_COMPILE_TIME_CONSTANTS</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ Constants such as <code class="computeroutput">numeric_limits<T>::is_signed</code>
+ are not available for use at compile-time.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_LONG_LONG_NUMERIC_LIMITS</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ There is no specialization for <code class="computeroutput">numeric_limits<long
+ long></code>
+ and <code class="computeroutput">numeric_limits<unsigned
+ long long></code>. <code class="computeroutput"><boost/limits.hpp></code>
+ will then add these specializations as a standard library "fix"
+ only if the compiler supports the <code class="computeroutput">long
+ long</code> datatype.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_MEMBER_FUNCTION_SPECIALIZATIONS</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ The compiler does not support the specialization of individual
+ member functions of template classes.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_MEMBER_TEMPLATE_KEYWORD</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ If the compiler supports member templates, but not the template
+ keyword when accessing member template classes.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_MEMBER_TEMPLATE_FRIENDS</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ Member template friend syntax (<code class="computeroutput">template<class
+ P>
+ friend class
+ frd;</code>)
+ described in the C++ Standard, 14.5.3, not supported.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_MEMBER_TEMPLATES</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ Member template functions not fully supported.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_MS_INT64_NUMERIC_LIMITS</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ There is no specialization for <code class="computeroutput">numeric_limits<__int64></code> and <code class="computeroutput">numeric_limits<unsigned
+ __int64></code>.
+ <code class="computeroutput"><boost/limits.hpp></code> will then add these specializations
+ as a standard library "fix", only if the compiler supports
+ the <code class="computeroutput">__int64</code> datatype.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_NESTED_FRIENDSHIP</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ Compiler doesn't allow a nested class to access private members
+ of its containing class. Probably Borland/CodeGear specific.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_OPERATORS_IN_NAMESPACE</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ Compiler requires inherited operator friend functions to be defined
+ at namespace scope, then using'ed to boost. Probably GCC specific.
+ See <boost/operators.hpp> for example.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_PARTIAL_SPECIALIZATION_IMPLICIT_DEFAULT_ARGS</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ The compiler does not correctly handle partial specializations
+ which depend upon default arguments in the primary template.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_POINTER_TO_MEMBER_CONST</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ The compiler does not correctly handle pointers to const member
+ functions, preventing use of these in overloaded function templates.
+ See <boost/functional.hpp> for example.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_POINTER_TO_MEMBER_TEMPLATE_PARAMETERS</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ Pointers to members don't work when used as template parameters.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_PRIVATE_IN_AGGREGATE</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ The compiler misreads 8.5.1, treating classes as non-aggregate
+ if they contain private or protected member functions.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_RTTI</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ The compiler may (or may not) have the typeid operator, but RTTI
+ on the dynamic type of an object is not supported.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_SFINAE</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ The compiler does not support the "Substitution Failure Is
+ Not An Error" meta-programming idiom.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_SFINAE_EXPR</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ The compiler does not support usage of SFINAE with arbitrary expressions.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_STD_ALLOCATOR</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The C++ standard library does not provide a standards conforming
+ <code class="computeroutput">std::allocator</code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_STD_DISTANCE</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The platform does not have a conforming version of <code class="computeroutput">std::distance</code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_STD_ITERATOR</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The C++ implementation fails to provide the <code class="computeroutput">std::iterator</code>
+ class.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_STD_ITERATOR_TRAITS</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The compiler does not provide a standard compliant implementation
+ of <code class="computeroutput">std::iterator_traits</code>. Note that the
+ compiler may still have a non-standard implementation.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_STD_LOCALE</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The standard library lacks <code class="computeroutput">std::locale</code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_STD_MESSAGES</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The standard library lacks a conforming <code class="computeroutput">std::messages</code>
+ facet.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_STD_MIN_MAX</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The C++ standard library does not provide the <code class="computeroutput">min()</code> and <code class="computeroutput">max()</code> template functions that should
+ be in <code class="computeroutput"><algorithm></code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_STD_OUTPUT_ITERATOR_ASSIGN</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ Defined if the standard library's output iterators are not assignable.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_STD_TYPEINFO</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The <typeinfo> header declares <code class="computeroutput">type_info</code>
+ in the global namespace instead of namespace std.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_STD_USE_FACET</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The standard library lacks a conforming <code class="computeroutput">std::use_facet</code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_STD_WSTREAMBUF</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The standard library's implementation of <code class="computeroutput">std::basic_streambuf<wchar_t></code> is either missing, incomplete,
+ or buggy.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_STD_WSTRING</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The standard library lacks <code class="computeroutput">std::wstring</code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_STDC_NAMESPACE</code>
+ 
+ </td>
+<td>
+ 
+ Compiler, Platform
+ 
+ </td>
+<td>
+ 
+ The contents of C++ standard headers for C library functions (the
+ <code class="computeroutput"><c...></code> headers) have not been placed
+ in namespace std. This test is difficult - some libraries "fake"
+ the std C functions by adding using declarations to import them
+ into namespace std, unfortunately they don't necessarily catch
+ all of them...
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_STRINGSTREAM</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The C++ implementation does not provide the <code class="computeroutput"><sstream></code>
+ header.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_SWPRINTF</code>
+ 
+ </td>
+<td>
+ 
+ Platform
+ 
+ </td>
+<td>
+ 
+ The platform does not have a conforming version of <code class="computeroutput">swprintf</code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_TEMPLATE_PARTIAL_SPECIALIZATION</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ Class template partial specialization (14.5.4 [temp.class.spec])
+ not supported.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_TEMPLATED_IOSTREAMS</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The standard library does not provide templated iostream classes.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_TEMPLATED_ITERATOR_CONSTRUCTORS</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The standard library does not provide templated iterator constructors
+ for its containers.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_TEMPLATE_TEMPLATES</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ The compiler does not support template template parameters.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_TYPEID</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ The compiler does not support the typeid operator at all.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_TYPENAME_WITH_CTOR</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ The typename keyword cannot be used when creating a temporary of
+ a Dependent type.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_UNREACHABLE_RETURN_DETECTION</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ If a return is unreachable, then no return statement should be
+ required, however some compilers insist on it, while other issue
+ a bunch of warnings if it is in fact present.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_USING_DECLARATION_OVERLOADS_FROM_TYPENAME_BASE</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ The compiler will not accept a using declaration that brings a
+ function from a typename used as a base class into a derived class
+ if functions of the same name are present in the derived class.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_USING_TEMPLATE</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ The compiler will not accept a using declaration that imports a
+ template class or function from another namespace. Originally a
+ Borland specific problem with imports to/from the global namespace,
+ extended to MSVC6 which has a specific issue with importing template
+ classes (but not functions).
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_VOID_RETURNS</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ The compiler does not allow a void function to return the result
+ of calling another void function.
+
+<pre xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="table-programlisting">void f() {}
+void g() { return f(); }
+</pre>
+
+ 
+ </td>
+</tr>
+</tbody>
+</table></div>
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="boost_config.boost_macro_reference.macros_that_describe_optional_features"></a><a name="config_features"></a><a class="link" href="boost_macro_reference.html#boost_config.boost_macro_reference.macros_that_describe_optional_features" title="Macros that describe optional features">Macros
+ that describe optional features</a>
+</h3></div></div></div>
+
+ The following macros describe features that are not required by the C++ standard.
+ The macro is only defined if the feature is present.
+ 
+<div class="informaltable"><table class="table">
+<colgroup>
+<col>
+<col>
+<col>
+</colgroup>
+<thead><tr>
+<th>
+ 
+ Macro
+ 
+ </th>
+<th>
+ 
+ Section
+ 
+ </th>
+<th>
+ 
+ Description
+ 
+ </th>
+</tr></thead>
+<tbody>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_BETHREADS</code>
+ 
+ </td>
+<td>
+ 
+ Platform
+ 
+ </td>
+<td>
+ 
+ The platform supports BeOS style threads.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_CLOCK_GETTIME</code>
+ 
+ </td>
+<td>
+ 
+ Platform
+ 
+ </td>
+<td>
+ 
+ The platform has the POSIX API <code class="computeroutput">clock_gettime</code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_DIRENT_H</code>
+ 
+ </td>
+<td>
+ 
+ Platform
+ 
+ </td>
+<td>
+ 
+ The platform has the POSIX header <code class="computeroutput"><dirent.h></code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_EXPM1</code>
+ 
+ </td>
+<td>
+ 
+ Platform
+ 
+ </td>
+<td>
+ 
+ The platform has the functions <code class="computeroutput">expm1</code>,
+ <code class="computeroutput">expm1f</code> and <code class="computeroutput">expm1l</code> in <code class="computeroutput"><math.h></code>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_FTIME</code>
+ 
+ </td>
+<td>
+ 
+ Platform
+ 
+ </td>
+<td>
+ 
+ The platform has the Win32 API type FTIME.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_GETSYSTEMTIMEASFILETIME</code>
+ 
+ </td>
+<td>
+ 
+ Platform
+ 
+ </td>
+<td>
+ 
+ The platform has the Win32 API GetSystemTimeAsFileTime.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_GETTIMEOFDAY</code>
+ 
+ </td>
+<td>
+ 
+ Platform
+ 
+ </td>
+<td>
+ 
+ The platform has the POSIX API <code class="computeroutput">gettimeofday</code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_HASH</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The C++ implementation provides the (SGI) hash_set and hash_map
+ classes. When defined, <code class="computeroutput">BOOST_HASH_SET_HEADER</code>
+ and <code class="computeroutput">BOOST_HASH_LIST_HEADER</code>
+ will contain the names of the header needed to access hash_set
+ and hash_map; <code class="computeroutput">BOOST_STD_EXTENSION_NAMESPACE</code>
+ will provide the namespace in which the two class templates reside.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_LOG1P</code>
+ 
+ </td>
+<td>
+ 
+ Platform
+ 
+ </td>
+<td>
+ 
+ The platform has the functions <code class="computeroutput">log1p</code>,
+ <code class="computeroutput">log1pf</code> and <code class="computeroutput">log1pl</code> in <code class="computeroutput"><math.h></code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_MACRO_USE_FACET</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The standard library lacks a conforming <code class="computeroutput">std::use_facet</code>,
+ but has a macro <code class="computeroutput">_USE(loc, Type)</code> that does the job. This is primarily
+ for the Dinkumware std lib.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_MS_INT64</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ The compiler supports the <code class="computeroutput">__int64</code>
+ data type.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_NANOSLEEP</code>
+ 
+ </td>
+<td>
+ 
+ Platform
+ 
+ </td>
+<td>
+ 
+ The platform has the POSIX API nanosleep.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_NL_TYPES_H</code>
+ 
+ </td>
+<td>
+ 
+ Platform
+ 
+ </td>
+<td>
+ 
+ The platform has an <code class="computeroutput"><nl_types.h></code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_NRVO</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ Indicated that the compiler supports the named return value optimization
+ (NRVO). Used to select the most efficient implementation for some
+ function. See <boost/operators.hpp> for example.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_PARTIAL_STD_ALLOCATOR</code>
+ 
+ </td>
+<td>
+ 
+ Standard Library
+ 
+ </td>
+<td>
+ 
+ The standard library has a partially conforming <code class="computeroutput">std::allocator</code>
+ class, but without any of the member templates.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_PTHREAD_DELAY_NP</code>
+ 
+ </td>
+<td>
+ 
+ Platform
+ 
+ </td>
+<td>
+ 
+ The platform has the POSIX API <code class="computeroutput">pthread_delay_np</code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_PTHREAD_MUTEXATTR_SETTYPE</code>
+ 
+ </td>
+<td>
+ 
+ Platform
+ 
+ </td>
+<td>
+ 
+ The platform has the POSIX API <code class="computeroutput">pthread_mutexattr_settype</code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_PTHREAD_YIELD</code>
+ 
+ </td>
+<td>
+ 
+ Platform
+ 
+ </td>
+<td>
+ 
+ The platform has the POSIX API <code class="computeroutput">pthread_yield</code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_PTHREADS</code>
+ 
+ </td>
+<td>
+ 
+ Platform
+ 
+ </td>
+<td>
+ 
+ The platform support POSIX style threads.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_SCHED_YIELD</code>
+ 
+ </td>
+<td>
+ 
+ Platform
+ 
+ </td>
+<td>
+ 
+ The platform has the POSIX API <code class="computeroutput">sched_yield</code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_SGI_TYPE_TRAITS</code>
+ 
+ </td>
+<td>
+ 
+ Compiler, Standard library
+ 
+ </td>
+<td>
+ 
+ The compiler has native support for SGI style type traits.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_STDINT_H</code>
+ 
+ </td>
+<td>
+ 
+ Platform
+ 
+ </td>
+<td>
+ 
+ The platform has a <code class="computeroutput"><stdint.h></code>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_SLIST</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The C++ implementation provides the (SGI) slist class. When defined,
+ <code class="computeroutput">BOOST_SLIST_HEADER</code>
+ will contain the name of the header needed to access <code class="computeroutput">slist</code> and <code class="computeroutput">BOOST_STD_EXTENSION_NAMESPACE</code>
+ will provide the namespace in which <code class="computeroutput">slist</code>
+ resides.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_STLP_USE_FACET</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The standard library lacks a conforming <code class="computeroutput">std::use_facet</code>,
+ but has a workaround class-version that does the job. This is primarily
+ for the STLport std lib.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_TR1_ARRAY</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The library has a TR1 conforming version of <code class="computeroutput"><array></code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_TR1_COMPLEX_OVERLOADS</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The library has a version of <code class="computeroutput"><complex></code>
+ that supports passing scalars to the complex number algorithms.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_TR1_COMPLEX_INVERSE_TRIG</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The library has a version of <code class="computeroutput"><complex></code>
+ that includes the new inverse trig functions from TR1.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_TR1_REFERENCE_WRAPPER</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The library has TR1 conforming reference wrappers in <code class="computeroutput"><functional></code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_TR1_RESULT_OF</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The library has a TR1 conforming result_of template in <code class="computeroutput"><functional></code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_TR1_MEM_FN</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The library has a TR1 conforming mem_fn function template in <code class="computeroutput"><functional></code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_TR1_BIND</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The library has a TR1 conforming bind function template in <code class="computeroutput"><functional></code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_TR1_FUNCTION</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The library has a TR1 conforming function class template in <code class="computeroutput"><functional></code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_TR1_HASH</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The library has a TR1 conforming hash function template in <code class="computeroutput"><functional></code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_TR1_SHARED_PTR</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The library has a TR1 conforming <code class="computeroutput">shared_ptr</code>
+ class template in <code class="computeroutput"><memory></code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_TR1_RANDOM</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The library has a TR1 conforming version of <code class="computeroutput"><random></code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_TR1_REGEX</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The library has a TR1 conforming version of <code class="computeroutput"><regex></code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_TR1_TUPLE</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The library has a TR1 conforming version of <code class="computeroutput"><tuple></code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_TR1_TYPE_TRAITS</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The library has a TR1 conforming version of <code class="computeroutput"><type_traits></code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_TR1_UTILITY</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The library has the TR1 additions to <code class="computeroutput"><utility></code>
+ (tuple interface to <code class="computeroutput">std::pair</code>).
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_TR1_UNORDERED_MAP</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The library has a TR1 conforming version of <code class="computeroutput"><unordered_map></code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_TR1_UNORDERED_SET</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The library has a TR1 conforming version of <code class="computeroutput"><unordered_set></code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_TR1</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ Implies all the other <code class="computeroutput">BOOST_HAS_TR1_*</code> macros should be set.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_THREADS</code>
+ 
+ </td>
+<td>
+ 
+ Platform, Compiler
+ 
+ </td>
+<td>
+ 
+ Defined if the compiler, in its current translation mode, supports
+ multiple threads of execution.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_TWO_ARG_USE_FACET</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The standard library lacks a conforming std::use_facet, but has
+ a two argument version that does the job. This is primarily for
+ the Rogue Wave std lib.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_UNISTD_H</code>
+ 
+ </td>
+<td>
+ 
+ Platform
+ 
+ </td>
+<td>
+ 
+ The Platform provides <code class="computeroutput"><unistd.h></code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_WINTHREADS</code>
+ 
+ </td>
+<td>
+ 
+ Platform
+ 
+ </td>
+<td>
+ 
+ The platform supports MS Windows style threads.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_MSVC_STD_ITERATOR</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ Microsoft's broken version of <code class="computeroutput">std::iterator</code>
+ is being used. This implies that <code class="computeroutput">std::iterator</code>
+ takes no more than two template parameters.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_MSVC6_MEMBER_TEMPLATES</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ Microsoft Visual C++ 6.0 has enough member template idiosyncrasies
+ (being polite) that <code class="computeroutput">BOOST_NO_MEMBER_TEMPLATES</code>
+ is defined for this compiler. <code class="computeroutput">BOOST_MSVC6_MEMBER_TEMPLATES</code>
+ is defined to allow compiler specific workarounds. This macro gets
+ defined automatically if <code class="computeroutput">BOOST_NO_MEMBER_TEMPLATES</code>
+ is not defined - in other words this is treated as a strict subset
+ of the features required by the standard.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_STDINT_H</code>
+ 
+ </td>
+<td>
+ 
+ Platform
+ 
+ </td>
+<td>
+ 
+ There are no 1998 C++ Standard headers <code class="computeroutput"><stdint.h></code>
+ or <code class="computeroutput"><cstdint></code>, although the 1999 C Standard
+ does include <code class="computeroutput"><stdint.h></code>.
+ If <code class="computeroutput"><stdint.h></code> is present, <code class="computeroutput"><boost/stdint.h></code>
+ can make good use of it, so a flag is supplied (signalling presence;
+ thus the default is not present, conforming to the current C++
+ standard).
+ 
+ </td>
+</tr>
+</tbody>
+</table></div>
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="boost_config.boost_macro_reference.macros_that_describe_possible_c___future_features"></a><a class="link" href="boost_macro_reference.html#boost_config.boost_macro_reference.macros_that_describe_possible_c___future_features" title="Macros that describe possible C++ future features">Macros
+ that describe possible C++ future features</a>
+</h3></div></div></div>
+
+ The following macros describe features that may be included in some future
+ ISO C++ standard, but have not yet been approved for inclusion in the language.
+ 
+<div class="informaltable"><table class="table">
+<colgroup>
+<col>
+<col>
+</colgroup>
+<thead><tr>
+<th>
+ 
+ Macro
+ 
+ </th>
+<th>
+ 
+ Description
+ 
+ </th>
+</tr></thead>
+<tbody><tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_CONCEPTS</code>
+ 
+ </td>
+<td>
+ 
+ The compiler supports concepts.
+ 
+ </td>
+</tr></tbody>
+</table></div>
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="boost_config.boost_macro_reference.macros_that_describe_c__11_features_not_supported"></a><a class="link" href="boost_macro_reference.html#boost_config.boost_macro_reference.macros_that_describe_c__11_features_not_supported" title="Macros that describe C++11 features not supported">Macros
+ that describe C++11 features not supported</a>
+</h3></div></div></div>
+
+ The following macros describe features in the 2011 ISO C++ standard, formerly
+ known as C++0x, that are not yet supported by a particular compiler or library.
+ 
+<div class="informaltable"><table class="table">
+<colgroup>
+<col>
+<col>
+</colgroup>
+<thead><tr>
+<th>
+ 
+ Macro
+ 
+ </th>
+<th>
+ 
+ Description
+ 
+ </th>
+</tr></thead>
+<tbody>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_ALLOCATOR</code>
+ 
+ </td>
+<td>
+ 
+ The standard library does not provide a C++11 version of <code class="computeroutput">std::allocator</code> in <memory>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_ATOMIC_SP</code>
+ 
+ </td>
+<td>
+ 
+ The standard library <memory> does not support atomic smart
+ pointer operations.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_ARRAY</code>
+ 
+ </td>
+<td>
+ 
+ The standard library does not provide header <array>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_CHRONO</code>
+ 
+ </td>
+<td>
+ 
+ The standard library does not provide header <chrono>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_CODECVT</code>
+ 
+ </td>
+<td>
+ 
+ The standard library does not provide header <codecvt>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_CONDITION_VARIABLE</code>
+ 
+ </td>
+<td>
+ 
+ The standard library does not provide header <condition_variable>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_FORWARD_LIST</code>
+ 
+ </td>
+<td>
+ 
+ The standard library does not provide header <forward_list>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_FUNCTIONAL</code>
+ 
+ </td>
+<td>
+ 
+ The standard library does not provide a C++11 compatible version
+ of <functional>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_FUTURE</code>
+ 
+ </td>
+<td>
+ 
+ The standard library does not provide header <future>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_INITIALIZER_LIST</code>
+ 
+ </td>
+<td>
+ 
+ The standard library does not provide header <initializer_list>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_MUTEX</code>
+ 
+ </td>
+<td>
+ 
+ The standard library does not provide header <mutex>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_RANDOM</code>
+ 
+ </td>
+<td>
+ 
+ The standard library does not provide header <random>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_RATIO</code>
+ 
+ </td>
+<td>
+ 
+ The standard library does not provide header <ratio>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_REGEX</code>
+ 
+ </td>
+<td>
+ 
+ The standard library does not provide header <regex>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_SYSTEM_ERROR</code>
+ 
+ </td>
+<td>
+ 
+ The standard library does not provide header <system_error>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_THREAD</code>
+ 
+ </td>
+<td>
+ 
+ The standard library does not provide header <thread>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_TUPLE</code>
+ 
+ </td>
+<td>
+ 
+ The standard library does not provide header <tuple>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_TYPEINDEX</code>
+ 
+ </td>
+<td>
+ 
+ The standard library does not provide header <typeindex>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_TYPE_TRAITS</code>
+ 
+ </td>
+<td>
+ 
+ The standard library does not provide header <type_traits>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_UNORDERED_MAP</code>
+ 
+ </td>
+<td>
+ 
+ The standard library does not provide header <unordered_map>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_UNORDERED_SET</code>
+ 
+ </td>
+<td>
+ 
+ The standard library does not provide header <unordered_set>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_SMART_PTR</code>
+ 
+ </td>
+<td>
+ 
+ The standard library header <memory> has no shared_ptr and
+ unique_ptr.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_AUTO_DECLARATIONS</code>
+ 
+ </td>
+<td>
+ 
+ The compiler does not support type deduction for variables declared
+ with the <code class="computeroutput">auto</code> keyword
+ (<code class="computeroutput">auto var
+ = ...;</code>).
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_AUTO_MULTIDECLARATIONS</code>
+ 
+ </td>
+<td>
+ 
+ The compiler does not support type deduction for multiple variables
+ declared with the <code class="computeroutput">auto</code>
+ keyword (<code class="computeroutput">auto var
+ = ...,
+ *ptr
+ = ...;</code>).
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_CHAR16_T</code>
+ 
+ </td>
+<td>
+ 
+ The compiler does not support type <code class="computeroutput">char16_t</code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_CHAR32_T</code>
+ 
+ </td>
+<td>
+ 
+ The compiler does not support type <code class="computeroutput">char32_t</code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_TEMPLATE_ALIASES</code>
+ 
+ </td>
+<td>
+ 
+ The compiler does not support template aliases.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_CONSTEXPR</code>
+ 
+ </td>
+<td>
+ 
+ The compiler does not support <code class="computeroutput">constexpr</code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_DECLTYPE</code>
+ 
+ </td>
+<td>
+ 
+ The compiler does not support <code class="computeroutput">decltype</code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_DECLTYPE_N3276</code>
+ 
+ </td>
+<td>
+ 
+ The compiler does not support the extension to <code class="computeroutput">decltype</code>
+ described in N3276,
+ accepted in Madrid, March 2011.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_DEFAULTED_FUNCTIONS</code>
+ 
+ </td>
+<td>
+ 
+ The compiler does not support defaulted (<code class="computeroutput">=
+ default</code>) functions.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_DELETED_FUNCTIONS</code>
+ 
+ </td>
+<td>
+ 
+ The compiler does not support deleted (<code class="computeroutput">=
+ delete</code>) functions.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_EXPLICIT_CONVERSION_OPERATORS</code>
+ 
+ </td>
+<td>
+ 
+ The compiler does not support explicit conversion operators (<code class="computeroutput">explicit operator
+ T()</code>).
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_EXTERN_TEMPLATE</code>
+ 
+ </td>
+<td>
+ 
+ The compiler does not support explicit instantiation forward declarations
+ for templates (<code class="computeroutput">extern template ...</code>).
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_FUNCTION_TEMPLATE_DEFAULT_ARGS</code>
+ 
+ </td>
+<td>
+ 
+ The compiler does not support default template arguments for function
+ templates.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_LAMBDAS</code>
+ 
+ </td>
+<td>
+ 
+ The compiler does not support Lambdas.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_LOCAL_CLASS_TEMPLATE_PARAMETERS</code>
+ 
+ </td>
+<td>
+ 
+ The compiler does not allow to pass local classes as template parameters
+ (this macro intentionally does not control passing of unnamed types
+ as template parameters, see also N2657).
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_LONG_LONG</code>
+ 
+ </td>
+<td>
+ 
+ The compiler does not support <code class="computeroutput">long
+ long</code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_NOEXCEPT</code>
+ 
+ </td>
+<td>
+ 
+ The compiler does not support <code class="computeroutput">noexcept</code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_NULLPTR</code>
+ 
+ </td>
+<td>
+ 
+ The compiler does not support <code class="computeroutput">nullptr</code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_RANGE_BASED_FOR</code>
+ 
+ </td>
+<td>
+ 
+ The compiler does not support range-based for statements.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_RAW_LITERALS</code>
+ 
+ </td>
+<td>
+ 
+ The compiler does not support raw string literals.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_RVALUE_REFERENCES</code>
+ 
+ </td>
+<td>
+ 
+ The compiler does not support r-value references.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_SCOPED_ENUMS</code>
+ 
+ </td>
+<td>
+ 
+ The compiler does not support scoped enumerations (<code class="computeroutput">enum class</code>).
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_STATIC_ASSERT</code>
+ 
+ </td>
+<td>
+ 
+ The compiler does not support <code class="computeroutput">static_assert</code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_STD_UNORDERD</code>
+ 
+ </td>
+<td>
+ 
+ The standard library does not support <unordered_map> and
+ <unordered_set>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_UNICODE_LITERALS</code>
+ 
+ </td>
+<td>
+ 
+ The compiler does not support Unicode (<code class="computeroutput">u8</code>,
+ <code class="computeroutput">u</code>, <code class="computeroutput">U</code>) literals.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_UNIFIED_INITIALIZATION_SYNTAX</code>
+ 
+ </td>
+<td>
+ 
+ The compiler does not support the <a href="http://en.wikipedia.org/wiki/C%2B%2B0x#Uniform_initialization" target="_top">C++11
+ Unified Initialization Syntax</a>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_VARIADIC_TEMPLATES</code>
+ 
+ </td>
+<td>
+ 
+ The compiler does not support variadic templates.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_VARIADIC_MACROS</code>
+ 
+ </td>
+<td>
+ 
+ The compiler does not support variadic macros.
+ 
+ </td>
+</tr>
+</tbody>
+</table></div>
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="boost_config.boost_macro_reference.macros_that_allow_use_of_c__11_features_with_c__03_compilers"></a><a name="config_11_for_03"></a><a class="link" href="boost_macro_reference.html#boost_config.boost_macro_reference.macros_that_allow_use_of_c__11_features_with_c__03_compilers" title="Macros that allow use of C++11 features with C++03 compilers">Macros
+ that allow use of C++11 features with C++03 compilers</a>
+</h3></div></div></div>
+
+ The following macros allow use of C++11 features even with compilers that
+ do not yet provide compliant C++11 support.
+ 
+<div class="informaltable"><table class="table">
+<colgroup>
+<col>
+<col>
+</colgroup>
+<thead><tr>
+<th>
+ 
+ Macro
+ 
+ </th>
+<th>
+ 
+ Description
+ 
+ </th>
+</tr></thead>
+<tbody>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_CONSTEXPR</code>
+ 
+ </td>
+<td>
+ 
+ Some compilers don't support the use of <code class="computeroutput">constexpr</code>.
+ This macro expands to nothing on those compilers, and <code class="computeroutput">constexpr</code> elsewhere. For example,
+ when defining a constexpr function or constructor replace:
+
+<pre xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="table-programlisting">constexpr tuple();
+</pre>
+
+ with:
+
+<pre xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="table-programlisting">BOOST_CONSTEXPR tuple();
+</pre>
+
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_CONSTEXPR_OR_CONST</code>
+ 
+ </td>
+<td>
+ 
+ Some compilers don't support the use of <code class="computeroutput">constexpr</code>.
+ This macro expands to <code class="computeroutput">const</code>
+ on those compilers, and <code class="computeroutput">constexpr</code>
+ elsewhere. For example, when defining const expr variables replace:
+
+<pre xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="table-programlisting">static constexpr UIntType xor_mask = a;
+</pre>
+
+ with:
+
+<pre xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="table-programlisting">static BOOST_CONSTEXPR_OR_CONST UIntType xor_mask = a;
+</pre>
+
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_STATIC_CONSTEXPR</code>
+ 
+ </td>
+<td>
+ 
+ This is a shortcut for <code class="computeroutput">static
+ BOOST_CONSTEXPR_OR_CONST</code>.
+ For example, when defining const expr variables replace:
+
+<pre xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="table-programlisting">static constexpr UIntType xor_mask = a;
+</pre>
+
+ with:
+
+<pre xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="table-programlisting">BOOST_STATIC_CONSTEXPR UIntType xor_mask = a;
+</pre>
+
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+
+<pre xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="table-programlisting">BOOST_NOEXCEPT
+BOOST_NOEXCEPT_IF(Predicate)
+BOOST_NOEXCEPT_EXPR(Expression)
+</pre>
+
+ 
+ </td>
+<td>
+ 
+ If <code class="computeroutput">BOOST_NO_NOEXCEPT</code>
+ is defined (i.e. C++03 compliant compilers) these macros are defined
+ as:
+ 
+ <div class="blockquote"><blockquote class="blockquote">
+
+
+<pre xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="table-programlisting">#define BOOST_NOEXCEPT
+#define BOOST_NOEXCEPT_IF(Predicate)
+#define BOOST_NOEXCEPT_EXPR(Expression) false
+</pre>
+
+ 
+</blockquote></div>
+ 
+ If <code class="computeroutput">BOOST_NO_NOEXCEPT</code>
+ is not defined (i.e. C++11 compliant compilers) they are defined
+ as:
+ 
+ <div class="blockquote"><blockquote class="blockquote">
+
+
+<pre xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="table-programlisting">#define BOOST_NOEXCEPT noexcept
+#define BOOST_NOEXCEPT_IF(Predicate) noexcept((Predicate))
+#define BOOST_NOEXCEPT_EXPR(Expression) noexcept((Expression))
+</pre>
+
+ 
+</blockquote></div>
+ </td>
+</tr>
+</tbody>
+</table></div>
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="boost_config.boost_macro_reference.boost_helper_macros"></a><a name="config_helpers"></a><a class="link" href="boost_macro_reference.html#boost_config.boost_macro_reference.boost_helper_macros" title="Boost Helper Macros">Boost
+ Helper Macros</a>
+</h3></div></div></div>
+
+ The following macros are either simple helpers, or macros that provide workarounds
+ for compiler/standard library defects.
+ 
+<div class="informaltable"><table class="table">
+<colgroup>
+<col>
+<col>
+</colgroup>
+<thead><tr>
+<th>
+ 
+ Macro
+ 
+ </th>
+<th>
+ 
+ Description
+ 
+ </th>
+</tr></thead>
+<tbody>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_WORKAROUND</code>
+ 
+ </td>
+<td>
+ 
+ This macro is used where a compiler specific workaround is required
+ that is not otherwise described by one of the other Boost.Config
+ macros. To use the macro you must first
+
+<pre xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="table-programlisting">#include <boost/detail/workaround.hpp>
+</pre>
+
+ usage is then:
+
+<pre xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="table-programlisting">#if BOOST_WORKAROUND(MACRONAME, CONDITION)
+ // workaround code goes here...
+#else
+ // Standard conforming code goes here...
+#endif
+</pre>
+
+ where <code class="computeroutput">MACRONAME</code>
+ is a macro that usually describes the version number to be tested
+ against, and <code class="computeroutput">CONDITION</code>
+ is a comparison operator followed by a value. For example <code class="computeroutput">BOOST_WORKAROUND(BOOST_INTEL,
+ <= 1010)</code> would evaluate to <code class="computeroutput">1</code> for Intel C++ 10.1 and earlier.
+ 
+ 
+ The macro can also be used with <code class="computeroutput">BOOST_TESTED_AT</code>
+ if all current compiler versions exhibit the issue, but the issue
+ is expected to be fixed at some later point.
+ 
+ 
+ For example <code class="computeroutput">BOOST_WORKAROUND(__BORLANDC__, BOOST_TESTED_AT(0x590))</code> would normally evaluate to <code class="computeroutput">1</code> for all values of <code class="computeroutput">__BORLANDC__</code> unless
+ the macro <code class="computeroutput">BOOST_DETECT_OUTDATED_WORKAROUNDS</code>
+ is defined, in which case evaluates to <code class="computeroutput">(__BORLANDC__ <=
+ 0x590)</code>.
+ 
+ 
+ Note: the ultimate source of documentation
+ for this macro is in boost/detail/workaround.hpp.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_PREVENT_MACRO_SUBSTITUTION</code>
+ 
+ </td>
+<td>
+ 
+ Sometimes you have a function name with the same name as a C macro,
+ for example "min" and "max" member functions,
+ in which case one can prevent the function being expanded as a
+ macro using:
+
+<pre xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="table-programlisting">someclass.min BOOST_PREVENT_MACRO_SUBSTITUTION(arg1, arg2);
+</pre>
+
+ The following also works in most, but not all, contexts:
+
+<pre xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="table-programlisting">(someclass.max)(arg1, arg2);
+</pre>
+
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_DEDUCED_TYPENAME</code>
+ 
+ </td>
+<td>
+ 
+ Some compilers don't support the use of typename for dependent
+ types in deduced contexts. This macro expands to nothing on those
+ compilers, and typename elsewhere. For example, replace: <code class="computeroutput">template <class T> void
+ f(T,
+ typename T::type);</code> with: <code class="computeroutput">template
+ <class
+ T>
+ void f(T, BOOST_DEDUCED_TYPENAME
+ T::type);</code>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HASH_MAP_HEADER</code>
+ 
+ </td>
+<td>
+ 
+ The header to include to get the SGI <code class="computeroutput">hash_map</code>
+ class. This macro is only available if <code class="computeroutput">BOOST_HAS_HASH</code>
+ is defined.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HASH_SET_HEADER</code>
+ 
+ </td>
+<td>
+ 
+ The header to include to get the SGI <code class="computeroutput">hash_set</code>
+ class. This macro is only available if <code class="computeroutput">BOOST_HAS_HASH</code>
+ is defined.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_SLIST_HEADER</code>
+ 
+ </td>
+<td>
+ 
+ The header to include to get the SGI <code class="computeroutput">slist</code>
+ class. This macro is only available if <code class="computeroutput">BOOST_HAS_SLIST</code>
+ is defined.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_STD_EXTENSION_NAMESPACE</code>
+ 
+ </td>
+<td>
+ 
+ The namespace used for std library extensions (hashtable classes
+ etc).
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_STATIC_CONSTANT(Type, assignment)</code>
+ 
+ </td>
+<td>
+ 
+ On compilers which don't allow in-class initialization of static
+ integral constant members, we must use enums as a workaround if
+ we want the constants to be available at compile-time. This macro
+ gives us a convenient way to declare such constants. For example
+ instead of:
+
+<pre xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="table-programlisting">struct foo{
+ static const int value = 2;
+};
+</pre>
+
+ use:
+
+<pre xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="table-programlisting">struct foo{
+ BOOST_STATIC_CONSTANT(int, value = 2);
+};
+</pre>
+
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_UNREACHABLE_RETURN(result)</code>
+ 
+ </td>
+<td>
+ 
+ Normally evaluates to nothing, but evaluates to return x; if the
+ compiler requires a return, even when it can never be reached.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_EXPLICIT_TEMPLATE_TYPE(t)</code> <code class="computeroutput">BOOST_EXPLICIT_TEMPLATE_NON_TYPE(t,v)</code> <code class="computeroutput">BOOST_APPEND_EXPLICIT_TEMPLATE_TYPE(t)</code> <code class="computeroutput">BOOST_APPEND_EXPLICIT_TEMPLATE_NON_TYPE(t,v)</code>
+ 
+ </td>
+<td>
+ 
+ Some compilers silently "fold" different function template
+ instantiations if some of the template parameters don't appear
+ in the function parameter list. For instance:
+
+<pre xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="table-programlisting">#include <iostream>
+#include <ostream>
+#include <typeinfo>
+
+template <int n>
+void f() { std::cout << n << ' '; }
+
+template <typename T>
+void g() { std::cout << typeid(T).name() << ' '; }
+
+int main() {
+ f<1>();
+ f<2>();
+
+ g<int>();
+ g<double>();
+}
+</pre>
+
+ incorrectly outputs <code class="literal">2 2 double double</code> on VC++
+ 6. These macros, to be used in the function parameter list, fix
+ the problem without effects on the calling syntax. For instance,
+ in the case above write:
+
+<pre xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="table-programlisting">template <int n>
+void f(BOOST_EXPLICIT_TEMPLATE_NON_TYPE(int, n)) { ... }
+
+template <typename T>
+void g(BOOST_EXPLICIT_TEMPLATE_TYPE(T)) { ... }
+</pre>
+
+ Beware that they can declare (for affected compilers) a dummy defaulted
+ parameter, so they
+ 
+ 
+ a) should be always invoked at the end of the parameter list
+ 
+ 
+ b) can't be used if your function
+ template is multiply declared.
+ 
+ 
+ Furthermore, in order to add any needed comma separator, an <code class="computeroutput">APPEND_*</code>
+ version must be used when the macro invocation appears after a
+ normal parameter declaration or after the invocation of another
+ macro of this same group.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_USE_FACET(Type, loc)</code>
+ 
+ </td>
+<td>
+ 
+ When the standard library does not have a conforming <code class="computeroutput">std::use_facet</code> there are various workarounds
+ available, but they differ from library to library. This macro
+ provides a consistent way to access a locale's facets. For example,
+ replace: <code class="computeroutput">std::use_facet<Type>(loc);</code>
+ with: <code class="computeroutput">BOOST_USE_FACET(Type, loc);</code> Note do not add a <code class="computeroutput">std::</code>
+ prefix to the front of <code class="computeroutput">BOOST_USE_FACET</code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_FACET(Type, loc)</code>
+ 
+ </td>
+<td>
+ 
+ When the standard library does not have a comforming <code class="computeroutput">std::has_facet</code> there are various workarounds
+ available, but they differ from library to library. This macro
+ provides a consistent way to check a locale's facets. For example,
+ replace: <code class="computeroutput">std::has_facet<Type>(loc);</code>
+ with: <code class="computeroutput">BOOST_HAS_FACET(Type, loc);</code> Note do not add a <code class="computeroutput">std::</code>
+ prefix to the front of <code class="computeroutput">BOOST_HAS_FACET</code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NESTED_TEMPLATE</code>
+ 
+ </td>
+<td>
+ 
+ Member templates are supported by some compilers even though they
+ can't use the <code class="computeroutput">A::template
+ member<U></code>
+ syntax, as a workaround replace: <code class="computeroutput">typedef
+ typename A::template
+ rebind<U>
+ binder;</code>
+ with: <code class="computeroutput">typedef typename
+ A::BOOST_NESTED_TEMPLATE rebind<U> binder;</code>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_STRINGIZE(X)</code>
+ 
+ </td>
+<td>
+ 
+ Converts the parameter <code class="computeroutput">X</code>
+ to a string after macro replacement on <code class="computeroutput">X</code>
+ has been performed.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_JOIN(X,Y)</code>
+ 
+ </td>
+<td>
+ 
+ This piece of macro magic joins the two arguments together, even
+ when one of the arguments is itself a macro (see 16.3.1 in C++
+ standard). This is normally used to create a mangled name in combination
+ with a predefined macro such a __LINE__.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_FORCEINLINE</code>
+ 
+ </td>
+<td>
+ 
+ This macro can be used in place of the <code class="computeroutput">inline</code>
+ keyword to instruct the compiler that a function should always
+ be inlined. Overuse of this macro can lead to significant bloat,
+ while good use can increase performance in certain cases, such
+ as computation-intensive code built through generative programming
+ techniques.
+ 
+ 
+ Usage example:
+
+<pre xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="table-programlisting">template<class T>
+BOOST_FORCEINLINE T& f(T& t)
+{
+ return t;
+}
+</pre>
+
+ 
+ 
+ Note that use of this macro can lead to cryptic error messages
+ with some compilers. Consider defining it to <code class="computeroutput">inline</code>
+ before including the Boost.Config header in order to be able to
+ debug errors more easily.
+ 
+ </td>
+</tr>
+</tbody>
+</table></div>
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="boost_config.boost_macro_reference.boost_informational_macros"></a><a name="config_info_macros"></a><a class="link" href="boost_macro_reference.html#boost_config.boost_macro_reference.boost_informational_macros" title="Boost Informational Macros">Boost
+ Informational Macros</a>
+</h3></div></div></div>
+
+ The following macros describe boost features; these are, generally speaking
+ the only boost macros that should be tested in user code.
+ 
+<div class="informaltable"><table class="table">
+<colgroup>
+<col>
+<col>
+<col>
+</colgroup>
+<thead><tr>
+<th>
+ 
+ Macro
+ 
+ </th>
+<th>
+ 
+ Header
+ 
+ </th>
+<th>
+ 
+ Description
+ 
+ </th>
+</tr></thead>
+<tbody>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_VERSION</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput"><boost/version.hpp></code>
+ 
+ </td>
+<td>
+ 
+ Describes the boost version number in XYYYZZ format such that:
+ <code class="computeroutput">(BOOST_VERSION
+ % 100)</code> is the sub-minor version, <code class="computeroutput">((BOOST_VERSION
+ / 100) % 1000)</code>
+ is the minor version, and <code class="computeroutput">(BOOST_VERSION /
+ 100000)</code>
+ is the major version.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_INT64_T</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput"><boost/cstdint.hpp></code> <code class="computeroutput"><boost/stdint.h></code>
+ 
+ </td>
+<td>
+ 
+ Defined if there are no 64-bit integral types: <code class="computeroutput">int64_t</code>,
+ <code class="computeroutput">uint64_t</code> etc.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_INTEGRAL_INT64_T</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput"><boost/cstdint.hpp></code> <code class="computeroutput"><boost/stdint.h></code>
+ 
+ </td>
+<td>
+ 
+ Defined if <code class="computeroutput">int64_t</code>
+ as defined by <code class="computeroutput"><boost/cstdint.hpp></code>
+ is not usable in integral constant expressions.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_MSVC</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput"><boost/config.hpp></code>
+ 
+ </td>
+<td>
+ 
+ Defined if the compiler is really Microsoft Visual C++, as opposed
+ to one of the many other compilers that also define <code class="computeroutput">_MSC_VER</code>. Has the same value
+ as _MSC_VER.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_MSVC_FULL_VER</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput"><boost/config.hpp></code>
+ 
+ </td>
+<td>
+ 
+ Defined to a normalised 9 digit version of _MSC_FULL_VER (which
+ sometimes only has 8 digits), the macro has the form VVMMPPPPP
+ where VV is the major version number, MM is the minor version number,
+ and PPPPP is the compiler build number.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_INTEL</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput"><boost/config.hpp></code>
+ 
+ </td>
+<td>
+ 
+ Defined if the compiler is an Intel compiler, takes the same value
+ as the compiler version macro.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_CLANG</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput"><boost/config.hpp></code>
+ 
+ </td>
+<td>
+ 
+ Defined to 1 if the compiler is the Clang compiler.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_WINDOWS</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput"><boost/config.hpp></code>
+ 
+ </td>
+<td>
+ 
+ Defined if the Windows platform API is available.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_DINKUMWARE_STDLIB</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput"><boost/config.hpp></code>
+ 
+ </td>
+<td>
+ 
+ Defined if the dinkumware standard library is in use, takes the
+ same value as the Dinkumware library version macro <code class="computeroutput">_CPPLIB_VER</code> if defined, otherwise
+ 1.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_WREGEX</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput"><boost/regex.hpp></code>
+ 
+ </td>
+<td>
+ 
+ Defined if the regex library does not support wide character regular
+ expressions.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_COMPILER</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput"><boost/config.hpp></code>
+ 
+ </td>
+<td>
+ 
+ Defined as a string describing the name and version number of the
+ compiler in use. Mainly for debugging the configuration.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_STDLIB</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput"><boost/config.hpp></code>
+ 
+ </td>
+<td>
+ 
+ Defined as a string describing the name and version number of the
+ standard library in use. Mainly for debugging the configuration.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_PLATFORM</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput"><boost/config.hpp></code>
+ 
+ </td>
+<td>
+ 
+ Defined as a string describing the name of the platform. Mainly
+ for debugging the configuration.
+ 
+ </td>
+</tr>
+</tbody>
+</table></div>
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="boost_config.boost_macro_reference.boost_deprecated_macros"></a><a name="deprecated_macros"></a><a class="link" href="boost_macro_reference.html#boost_config.boost_macro_reference.boost_deprecated_macros" title="Boost Deprecated Macros">Boost
+ Deprecated Macros</a>
+</h3></div></div></div>
+
+ The following have been deprecated; please use the replacements instead.
+ They will be removed in a future version of boost.
+ 
+<div class="informaltable"><table class="table">
+<colgroup>
+<col>
+<col>
+<col>
+<col>
+</colgroup>
+<thead><tr>
+<th>
+ 
+ Deprecated Macro
+ 
+ </th>
+<th>
+ 
+ Replacement
+ 
+ </th>
+<th>
+ 
+ When deprecated
+ 
+ </th>
+<th>
+ 
+ When removed
+ 
+ </th>
+</tr></thead>
+<tbody>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_0X_HDR_ARRAY</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_ARRAY</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.50
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_0X_HDR_CHRONO</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_CHRONO</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.50
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_0X_HDR_CODECVT</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_CODECVT</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.50
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_0X_HDR_CONDITION_VARIABLE</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_CONDITION_VARIABLE</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.50
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_0X_HDR_FORWARD_LIST</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_FORWARD_LIST</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.50
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_0X_HDR_FUTURE</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_FUTURE</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.50
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_0X_HDR_INITIALIZER_LIST</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_INITIALIZER_LIST</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.50
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_INITIALIZER_LISTS</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_INITIALIZER_LIST</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.50
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_0X_HDR_MUTEX</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_MUTEX</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.50
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_0X_HDR_RANDOM</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_RANDOM</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.50
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_0X_HDR_RATIO</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_RATIO</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.50
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_0X_HDR_REGEX</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_REGEX</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.50
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_0X_HDR_SYSTEM_ERROR</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_SYSTEM_ERROR</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.50
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_0X_HDR_THREAD</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_THREAD</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.50
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_0X_HDR_TUPLE</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_TUPLE</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.50
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_0X_HDR_TYPE_TRAITS</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_TYPE_TRAITS</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.50
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_0X_HDR_TYPEINDEX</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_TYPEINDEX</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.50
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_0X_HDR_UNORDERED_SET</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_UNORDERED_SET</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.50
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_0X_HDR_UNORDERED_MAP</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_UNORDERED_MAP</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.50
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_STD_UNORDERED</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_UNORDERED_SET</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.50
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ </td>
+<td>
+ </td>
+<td>
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_AUTO_DECLARATIONS</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_AUTO_DECLARATIONS</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.51
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_AUTO_MULTIDECLARATIONS</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_AUTO_MULTIDECLARATIONS</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.51
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CHAR16_T</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_CHAR16_T</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.51
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CHAR32_T</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_CHAR32_T</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.51
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_TEMPLATE_ALIASES</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_TEMPLATE_ALIASES</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.51
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CONSTEXPR</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_CONSTEXPR</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.51
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_DECLTYPE</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_DECLTYPE</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.51
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_DECLTYPE_N3276</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_DECLTYPE_N3276</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.51
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_DEFAULTED_FUNCTIONS</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_DEFAULTED_FUNCTIONS</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.51
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_DELETED_FUNCTIONS</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_DELETED_FUNCTIONS</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.51
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_EXPLICIT_CONVERSION_OPERATORS</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_EXPLICIT_CONVERSION_OPERATORS</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.51
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_EXTERN_TEMPLATE</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_EXTERN_TEMPLATE</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.51
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_FUNCTION_TEMPLATE_DEFAULT_ARGS</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_FUNCTION_TEMPLATE_DEFAULT_ARGS</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.51
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_LAMBDAS</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_LAMBDAS</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.51
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_LOCAL_CLASS_TEMPLATE_PARAMETERS</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_LOCAL_CLASS_TEMPLATE_PARAMETERS</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.51
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_NOEXCEPT</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_NOEXCEPT</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.51
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_NULLPTR</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_NULLPTR</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.51
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_RAW_LITERALS</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_RAW_LITERALS</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.51
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_RVALUE_REFERENCES</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_RVALUE_REFERENCES</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.51
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_SCOPED_ENUMS</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_SCOPED_ENUMS</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.51
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_STATIC_ASSERT</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_STATIC_ASSERT</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.51
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_STD_UNORDERD</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_STD_UNORDERD</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.51
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_UNICODE_LITERALS</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_UNICODE_LITERALS</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.51
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_UNIFIED_INITIALIZATION_SYNTAX</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_UNIFIED_INITIALIZATION_SYNTAX</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.51
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_VARIADIC_TEMPLATES</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_VARIADIC_TEMPLATES</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.51
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_VARIADIC_MACROS</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_VARIADIC_MACROS</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.51
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_NUMERIC_LIMITS_LOWEST</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_NUMERIC_LIMITS</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.51
+ 
+ </td>
+<td>
+ </td>
+</tr>
+</tbody>
+</table></div>
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="boost_config.boost_macro_reference.macros_for_libraries_with_separate_source_code"></a><a class="link" href="boost_macro_reference.html#boost_config.boost_macro_reference.macros_for_libraries_with_separate_source_code" title="Macros for libraries with separate source code">Macros
+ for libraries with separate source code</a>
+</h3></div></div></div>
+<div class="toc"><dl>
+<dt><a href="boost_macro_reference.html#boost_config.boost_macro_reference.macros_for_libraries_with_separate_source_code.macros_controlling_shared_library_symbol_visibility">Macros
+ controlling shared library symbol visibility</a></dt>
+<dt><a href="boost_macro_reference.html#boost_config.boost_macro_reference.macros_for_libraries_with_separate_source_code.abi_fixing">ABI
+ Fixing</a></dt>
+<dt><a href="boost_macro_reference.html#boost_config.boost_macro_reference.macros_for_libraries_with_separate_source_code.automatic_library_selection">Automatic
+ library selection</a></dt>
+</dl></div>
+
+ The following macros and helper headers are of use to authors whose libraries
+ include separate source code, and are intended to address several issues:
+ 
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem">
+ Controlling shared library symbol visibility
+ </li>
+<li class="listitem">
+ Fixing the ABI of the compiled library
+ </li>
+<li class="listitem">
+ Selecting which compiled library to link against based upon the compilers
+ settings
+ </li>
+</ul></div>
+
+ See <a href="http://svn.boost.org/trac/boost/wiki/Guidelines/Separate" target="_top">Guidelines
+ for Authors of Boost Libraries Containing Separate Source</a>
+ 
+<div class="section">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="boost_config.boost_macro_reference.macros_for_libraries_with_separate_source_code.macros_controlling_shared_library_symbol_visibility"></a><a class="link" href="boost_macro_reference.html#boost_config.boost_macro_reference.macros_for_libraries_with_separate_source_code.macros_controlling_shared_library_symbol_visibility" title="Macros controlling shared library symbol visibility">Macros
+ controlling shared library symbol visibility</a>
+</h4></div></div></div>
+
+ Some compilers support C++ extensions that control which symbols will be
+ exported from shared libraries such as dynamic shared objects (DSO's) on
+ Unix-like systems or dynamic-link libraries (DLL's) on Windows.
+ 
+
+ The Microsoft VC++ compiler has long supplied <code class="computeroutput">__declspec(dllexport)</code> and <code class="computeroutput">__declspec(dllimport)</code> extensions for this purpose, as do virtually
+ all other compilers targeting the Windows platform.
+ 
+
+ Modern versions of the GNU GCC compiler provide the <code class="computeroutput">__attribute__((visibility("default")))</code> extension to indicate that a symbol
+ should be exported. All other symbols may be hidden by using the <code class="computeroutput">-fvisibility-hidden</code>
+ or <code class="computeroutput">-fvisibility-ms-compat</code> compiler switches.
+ 
+
+ Boost supplies several macros to make it easier to manage symbol visibility
+ in a way that is portable between compilers and operating systems.
+ 
+<div class="informaltable"><table class="table">
+<colgroup>
+<col>
+<col>
+</colgroup>
+<thead><tr>
+<th>
+ 
+ Macro
+ 
+ </th>
+<th>
+ 
+ Description
+ 
+ </th>
+</tr></thead>
+<tbody>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_SYMBOL_EXPORT</code>
+ 
+ </td>
+<td>
+ 
+ Defines the syntax of a C++ language extension that indicates
+ a symbol is to be exported from a shared library. If the compiler
+ has no such extension, the macro is defined with no replacement
+ text.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_SYMBOL_IMPORT</code>
+ 
+ </td>
+<td>
+ 
+ Defines the syntax of a C++ language extension that indicates
+ a symbol is to be imported from a shared library. If the compiler
+ has no such extension, the macro is defined with no replacement
+ text.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_SYMBOL_VISIBLE</code>
+ 
+ </td>
+<td>
+ 
+ Defines the syntax of a C++ language extension that indicates
+ a symbol is to be globally visible. If the compiler has no such
+ extension, the macro is defined with no replacement text. Needed
+ for classes that are not otherwise exported, but are used by
+ RTTI. Examples include class for objects that will be thrown
+ as exceptions or used in dynamic_casts, across shared library
+ boundaries. For example, a header-only exception class might
+ look like this:
+
+<pre xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="table-programlisting">class BOOST_SYMBOL_VISIBLE my_exception : public std::runtime_error { ... };
+</pre>
+
+ Without BOOST_SYMBOL_VISIBLE, it would be impossible to catch
+ my_exception thrown from a shared library compiled by GCC with
+ the -fvisibility=hidden option.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_DECLSPEC</code>
+ 
+ </td>
+<td>
+ 
+ The compiler has C++ extensions <code class="computeroutput">__declspec(dllexport)</code> and <code class="computeroutput">__declspec(dllimport)</code> to control export/import of
+ symbols from shared libraries. Deprecated. This macro
+ is no longer necessary since BOOST_SYMBOL_EXPORT and BOOST_SYMBOL_IMPORT
+ are now supplied. It is provided to support legacy code.
+ 
+ </td>
+</tr>
+</tbody>
+</table></div>
+
+ Typical usage:
+ 
+
+ boost/foo/config.hpp
+ 
+<pre class="programlisting">...
+#if defined(BOOST_ALL_DYN_LINK) || defined(BOOST_FOO_DYN_LINK)
+# if defined(BOOST_FOO_SOURCE)
+# define BOOST_FOO_DECL BOOST_SYMBOL_EXPORT
+# else
+# define BOOST_FOO_DECL BOOST_SYMBOL_IMPORT
+# endif
+#else
+# define BOOST_FOO_DECL
+#endif
+...
+</pre>
+
+ boost/foo/foo.hpp
+ 
+<pre class="programlisting">#include <boost/foo/config.hpp>
+...
+class BOOST_FOO_DECL bar { ... };
+...
+void BOOST_FOO_DECL f();
+...
+</pre>
+
+ boost/libs/foo/src/foo.cpp
+ 
+<pre class="programlisting">#define BOOST_FOO_SOURCE
+#include <boost/foo/foo.hpp>
+...
+void BOOST_FOO_DECL f()
+{
+ ...
+}
+...
+</pre>
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="boost_config.boost_macro_reference.macros_for_libraries_with_separate_source_code.abi_fixing"></a><a class="link" href="boost_macro_reference.html#boost_config.boost_macro_reference.macros_for_libraries_with_separate_source_code.abi_fixing" title="ABI Fixing">ABI
+ Fixing</a>
+</h4></div></div></div>
+
+ When linking against a pre-compiled library it vital that the ABI used
+ by the compiler when building the library matches exactly
+ the ABI used by the code using the library. In this case ABI means things
+ like the struct packing arrangement used, the name mangling scheme used,
+ or the size of some types (enum types for example). This is separate from
+ things like threading support, or runtime library variations, which have
+ to be dealt with by build variants. To put this in perspective there is
+ one compiler (Borland's) that has so many compiler options that make subtle
+ changes to the ABI, that at least in theory there 3200 combinations, and
+ that's without considering runtime library variations. Fortunately these
+ variations can be managed by <code class="computeroutput">#pragma</code>'s
+ that tell the compiler what ABI to use for the types declared in your library.
+ In order to avoid sprinkling <code class="computeroutput">#pragma</code>'s
+ all over the boost headers, there are some prefix and suffix headers that
+ do the job. Typical usage is:
+ 
+
+ my_library.hpp
+ 
+<pre class="programlisting">#ifndef MY_INCLUDE_GUARD
+#define MY_INCLUDE_GUARD
+
+// all includes go here:
+<code class="literal">#include <boost/config.hpp></code>
+#include <whatever>
+
+<code class="literal">#include <boost/config/abi_prefix.hpp></code> // must be the last #include
+
+namespace boost {
+
+// your code goes here
+
+}
+
+<code class="literal">#include <boost/config/abi_suffix.hpp></code> // pops abi_prefix.hpp pragmas
+
+#endif // include guard
+</pre>
+
+ my_library.cpp
+ 
+<pre class="programlisting">...
+// nothing special need be done in the implementation file
+...
+</pre>
+
+ The user can disable this mechanism by defining <code class="computeroutput">BOOST_DISABLE_ABI_HEADERS</code>,
+ or they can define <code class="computeroutput">BOOST_ABI_PREFIX</code>
+ and/or <code class="computeroutput">BOOST_ABI_SUFFIX</code>
+ to point to their own prefix/suffix headers if they so wish.
+ 
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="boost_config.boost_macro_reference.macros_for_libraries_with_separate_source_code.automatic_library_selection"></a><a class="link" href="boost_macro_reference.html#boost_config.boost_macro_reference.macros_for_libraries_with_separate_source_code.automatic_library_selection" title="Automatic library selection">Automatic
+ library selection</a>
+</h4></div></div></div>
+
+ It is essential that users link to a build of a library which was built
+ against the same runtime library that their application will be built against
+ -if this does not happen then the library will not be binary compatible
+ with their own code- and there is a high likelihood that their application
+ will experience runtime crashes. These kinds of problems can be extremely
+ time consuming and difficult to debug, and often lead to frustrated users
+ and authors alike (simply selecting the right library to link against is
+ not as easy as it seems when their are 6-8 of them to chose from, and some
+ users seem to be blissfully unaware that there even are different runtimes
+ available to them).
+ 
+
+ To solve this issue, some compilers allow source code to contain <code class="computeroutput">#pragma</code>'s that instruct the linker
+ which library to link against, all the user need do is include the headers
+ they need, place the compiled libraries in their library search path, and
+ the compiler and linker do the rest. Boost.config supports this via the
+ header <code class="computeroutput"><boost/config/auto_link.hpp></code>, before including this header one or
+ more of the following macros need to be defined:
+ 
+<div class="variablelist">
+
+<dl>
+<dt><code class="computeroutput">BOOST_LIB_NAME</code></dt>
+<dd>
+ Required: An identifier containing the basename of the library, for
+ example 'boost_regex'.
+ </dd>
+<dt><code class="computeroutput">BOOST_DYN_LINK</code></dt>
+<dd>
+ Optional: when set link to dll rather than static library.
+ </dd>
+<dt><code class="computeroutput">BOOST_LIB_DIAGNOSTIC</code></dt>
+<dd>
+ Optional: when set the header will print out the name of the library
+ selected (useful for debugging).
+ </dd>
+</dl>
+</div>
+
+ If the compiler supports this mechanism, then it will be told to link against
+ the appropriately named library, the actual algorithm used to mangle the
+ name of the library is documented inside <code class="computeroutput"><boost/config/auto_link.hpp></code>
+ and has to match that used to create the libraries via bjam 's install
+ rules.
+ 
+
+ my_library.hpp
+ 
+<pre class="programlisting">...
+//
+// Don't include auto-linking code if the user has disabled it by
+// defining BOOST_ALL_NO_LIB, or BOOST_MY_LIBRARY_NO_LIB, or if this 
+// is one of our own source files (signified by BOOST_MY_LIBRARY_SOURCE):
+//
+#if !defined(BOOST_ALL_NO_LIB) && !defined(BOOST_MY_LIBRARY_NO_LIB) && !defined(BOOST_MY_LIBRARY_SOURCE)
+# define BOOST_LIB_NAME boost_my_library
+# ifdef BOOST_MY_LIBRARY_DYN_LINK
+# define BOOST_DYN_LINK
+# endif
+# include <boost/config/auto_link.hpp>
+#endif
+...
+</pre>
+
+ my_library.cpp
+ 
+<pre class="programlisting">// define BOOST_MY_LIBRARY_SOURCE so that the header knows that the
+// library is being built (possibly exporting rather than importing code)
+//
+#define BOOST_MY_LIBRARY_SOURCE
+
+#include <boost/my_library/my_library.hpp>
+...
+</pre>
+</div>
+</div>
+</div>
+<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
+<td align="left"></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Beman Dawes, Vesa Karvonen, John
+ Maddock
+ 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)
+ 
+</div></td>
+</tr></table>
+<hr>
+<div class="spirit-nav">
+<a accesskey="p" href="../index.html"><img src="../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.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="guidelines_for_boost_authors.html"><img src="../../../../../doc/src/images/next.png" alt="Next"></a>
+</div>
+</body>
+</html>

Added: website/public_html/live/doc/fixes/boost_1_51_0/libs/config/doc/html/boost_config/guidelines_for_boost_authors.html
==============================================================================
--- (empty file)
+++ website/public_html/live/doc/fixes/boost_1_51_0/libs/config/doc/html/boost_config/guidelines_for_boost_authors.html 2012-11-20 15:40:09 EST (Tue, 20 Nov 2012)
@@ -0,0 +1,377 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
+<title>Guidelines for Boost Authors</title>
+<link rel="stylesheet" href="../../../../../doc/src/boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="../index.html" title="Boost.Config">
+<link rel="up" href="../index.html" title="Boost.Config">
+<link rel="prev" href="boost_macro_reference.html" title="Boost Macro Reference">
+<link rel="next" href="rationale.html" title="Rationale">
+</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">Home</td>
+<td align="center">Libraries</td>
+<td align="center">People</td>
+<td align="center">FAQ</td>
+<td align="center">More</td>
+</tr></table>
+<hr>
+<div class="spirit-nav">
+<a accesskey="p" href="boost_macro_reference.html"><img src="../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.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="rationale.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="boost_config.guidelines_for_boost_authors"></a><a class="link" href="guidelines_for_boost_authors.html" title="Guidelines for Boost Authors">Guidelines for
+ Boost Authors</a>
+</h2></div></div></div>
+<div class="toc"><dl>
+<dt><a href="guidelines_for_boost_authors.html#boost_config.guidelines_for_boost_authors.warnings">Disabling
+ Compiler Warnings</a></dt>
+<dt><a href="guidelines_for_boost_authors.html#boost_config.guidelines_for_boost_authors.adding_new_defect_macros">Adding
+ New Defect Macros</a></dt>
+<dt><a href="guidelines_for_boost_authors.html#boost_config.guidelines_for_boost_authors.adding_new_feature_test_macros">Adding
+ New Feature Test Macros</a></dt>
+<dt><a href="guidelines_for_boost_authors.html#boost_config.guidelines_for_boost_authors.modifying_the_boost_configuration_headers">Modifying
+ the Boost Configuration Headers</a></dt>
+</dl></div>
+
+ The <boost/config.hpp>
+ header is used to pass configuration information to other boost files, allowing
+ them to cope with platform dependencies such as arithmetic byte ordering, compiler
+ pragmas, or compiler shortcomings. Without such configuration information,
+ many current compilers would not work with the Boost libraries.
+ 
+
+ Centralizing configuration information in this header reduces the number of
+ files that must be modified when porting libraries to new platforms, or when
+ compilers are updated. Ideally, no other files would have to be modified when
+ porting to a new platform.
+ 
+
+ Configuration headers are controversial because some view them as condoning
+ broken compilers and encouraging non-standard subsets. Adding settings for
+ additional platforms and maintaining existing settings can also be a problem.
+ In other words, configuration headers are a necessary evil rather than a desirable
+ feature. The boost config.hpp policy is designed to minimize the problems and
+ maximize the benefits of a configuration header.
+ 
+
+ Note that:
+ 
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem">
+ Boost library implementers are not required to "<code class="computeroutput">#include
+ <boost/config.hpp></code>", and are not required in any
+ way to support compilers that do not comply with the C++ Standard (ISO/IEC
+ 14882).
+ </li>
+<li class="listitem">
+ If a library implementer wishes to support some non-conforming compiler,
+ or to support some platform specific feature, "<code class="computeroutput">#include
+ <boost/config.hpp></code>" is the preferred way to obtain
+ configuration information not available from the standard headers such
+ as <code class="computeroutput"><climits></code>, etc.
+ </li>
+<li class="listitem">
+ If configuration information can be deduced from standard headers such
+ as <code class="computeroutput"><climits></code>, use those standard headers rather
+ than <code class="computeroutput"><boost/config.hpp></code>.
+ </li>
+<li class="listitem">
+ Boost files that use macros defined in <code class="computeroutput"><boost/config.hpp></code>
+ should have sensible, standard conforming, default behavior if the macro
+ is not defined. This means that the starting point for porting <code class="computeroutput"><boost/config.hpp></code> to a new platform is simply to define
+ nothing at all specific to that platform. In the rare case where there
+ is no sensible default behavior, an #error message should describe the
+ problem.
+ </li>
+<li class="listitem">
+ If a Boost library implementer wants something added to <code class="computeroutput">config.hpp</code>,
+ post a request on the Boost mailing list. There is no guarantee such a
+ request will be honored; the intent is to limit the complexity of config.hpp.
+ </li>
+<li class="listitem">
+ The intent is to support only compilers which appear on their way to becoming
+ C++ Standard compliant, and only recent releases of those compilers at
+ that.
+ </li>
+<li class="listitem">
+ The intent is not to disable mainstream features now well-supported by
+ the majority of compilers, such as namespaces, exceptions, RTTI, or templates.
+ </li>
+</ul></div>
+<div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="boost_config.guidelines_for_boost_authors.warnings"></a><a class="link" href="guidelines_for_boost_authors.html#boost_config.guidelines_for_boost_authors.warnings" title="Disabling Compiler Warnings">Disabling
+ Compiler Warnings</a>
+</h3></div></div></div>
+
+ The header <code class="computeroutput"><boost/config/warning_disable.hpp></code>
+ can be used to disable certain compiler warnings that are hard or impossible
+ to otherwise remove.
+ 
+
+ Note that:
+ 
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem">
+ This header should never be included
+ by another Boost header, it should only ever be
+ used by a library source file or a test case.
+ </li>
+<li class="listitem">
+ The header should be included before
+ you include any other header.
+ </li>
+<li class="listitem">
+ This header only disables warnings that are hard or impossible to otherwise
+ deal with, and which are typically emitted by one compiler only, or in
+ one compilers own standard library headers.
+ </li>
+</ul></div>
+
+ Currently it disables the following warnings:
+ 
+<div class="informaltable"><table class="table">
+<colgroup>
+<col>
+<col>
+</colgroup>
+<thead><tr>
+<th>
+ 
+ Compiler
+ 
+ </th>
+<th>
+ 
+ Warning
+ 
+ </th>
+</tr></thead>
+<tbody>
+<tr>
+<td>
+ 
+ Visual C++ 8 and later
+ 
+ </td>
+<td>
+ 
+ C4996:
+ Error 'function': was declared deprecated
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ Intel C++
+ 
+ </td>
+<td>
+ 
+ Warning 1786: relates to the use of "deprecated" standard
+ library functions rather like C4996 in Visual C++.
+ 
+ </td>
+</tr>
+</tbody>
+</table></div>
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="boost_config.guidelines_for_boost_authors.adding_new_defect_macros"></a><a class="link" href="guidelines_for_boost_authors.html#boost_config.guidelines_for_boost_authors.adding_new_defect_macros" title="Adding New Defect Macros">Adding
+ New Defect Macros</a>
+</h3></div></div></div>
+
+ When you need to add a new defect macro - either to fix a problem with an
+ existing library, or when adding a new library - distil the issue down to
+ a simple test case; often, at this point other (possibly better) workarounds
+ may become apparent. Secondly always post the test case code to the boost
+ mailing list and invite comments; remember that C++ is complex and that sometimes
+ what may appear a defect, may in fact turn out to be a problem with the authors
+ understanding of the standard.
+ 
+
+ When you name the macro, follow the <code class="computeroutput">BOOST_NO_</code>SOMETHING
+ naming convention, so that it's obvious that this is a macro reporting a
+ defect.
+ 
+
+ Finally, add the test program to the regression tests. You will need to place
+ the test case in a <code class="computeroutput">.ipp</code>
+ file with the following comments near the top:
+ 
+<pre class="programlisting">// MACRO: BOOST_NO_FOO
+// TITLE: foo
+// DESCRIPTION: If the compiler fails to support foo
+</pre>
+
+ These comments are processed by the autoconf script, so make sure the format
+ follows the one given. The file should be named "<code class="computeroutput">boost_no_foo.ipp</code>",
+ where foo is the defect description - try and keep the file name under the
+ Mac 30 character filename limit though. You will also need to provide a function
+ prototype "<code class="computeroutput">int test()</code>" that is declared in a namespace with
+ the same name as the macro, but in all lower case, and which returns zero
+ on success:
+ 
+<pre class="programlisting">namespace boost_no_foo {
+int test()
+{
+ // test code goes here:
+ //
+ return 0;
+}
+
+}
+</pre>
+
+ Once the test code is in place in libs/config/test, updating the configuration
+ test system proceeds as:
+ 
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem">
+ cd into <code class="computeroutput">libs/config/tools</code> and run <code class="computeroutput">bjam</code>.
+ This generates the <code class="computeroutput">.cpp</code>
+ file test cases from the <code class="computeroutput">.ipp</code> file, updates the libs/config/test/all/Jamfile.v2,
+ <code class="computeroutput">config_test.cpp</code> and <code class="computeroutput">config_info.cpp</code>. 
+ 
+ </li>
+<li class="listitem">
+ cd into <code class="computeroutput">libs/config/test/all</code> and run <code class="computeroutput">bjam
+ </code>MACRONAME<code class="computeroutput"> compiler-list</code>,
+ where MACRONAME is the name of the new macro, and
+ <code class="computeroutput">compiler-list</code> is a space separated
+ list of compilers to test with. The xxx_pass_test and the
+ xxx_fail_test should both report <code class="computeroutput">**passed**</code>. If MACRONAME
+ is not defined when it should be defined, xxx_pass_test will not report
+ <code class="computeroutput">**passed**</code>. If MACRONAME
+ is defined when it should not be defined, xxx_fail_test will not report
+ <code class="computeroutput">**passed**</code>. 
+ </li>
+<li class="listitem">
+ cd into <code class="computeroutput">libs/config/test</code> and run <code class="computeroutput">bjam
+ config_info config_test
+ </code><code class="computeroutput">compiler-list</code>.
+ <code class="computeroutput">config_info</code> should build
+ and run cleanly for all the compilers in <code class="computeroutput">compiler-list</code>
+ while <code class="computeroutput">config_test</code> should
+ fail for those that have the defect, and pass for those that do not.
+ </li>
+</ul></div>
+
+ Then you should:
+ 
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem">
+ Define the defect macro in those config headers that require it.
+ </li>
+<li class="listitem">
+ Document the macro in this documentation (please do not forget this step!!)
+ </li>
+<li class="listitem">
+ Commit everything.
+ </li>
+<li class="listitem">
+ Keep an eye on the regression tests for new failures in Boost.Config
+ caused by the addition.
+ </li>
+<li class="listitem">
+ Start using the macro.
+ </li>
+</ul></div>
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="boost_config.guidelines_for_boost_authors.adding_new_feature_test_macros"></a><a class="link" href="guidelines_for_boost_authors.html#boost_config.guidelines_for_boost_authors.adding_new_feature_test_macros" title="Adding New Feature Test Macros">Adding
+ New Feature Test Macros</a>
+</h3></div></div></div>
+
+ When you need to add a macro that describes a feature that the standard does
+ not require, follow the convention for adding a new defect macro (above),
+ but call the macro <code class="computeroutput">BOOST_HAS_FOO</code>,
+ and name the test file "<code class="computeroutput">boost_has_foo.ipp</code>".
+ Try not to add feature test macros unnecessarily, if there is a platform
+ specific macro that can already be used (for example <code class="computeroutput">_WIN32</code>,
+ <code class="computeroutput">__BEOS__</code>, or <code class="computeroutput">__linux</code>) to identify the feature then use
+ that. Try to keep the macro to a feature group, or header name, rather than
+ one specific API (for example <code class="computeroutput">BOOST_HAS_NL_TYPES_H</code>
+ rather than <code class="computeroutput">BOOST_HAS_CATOPEN</code>).
+ If the macro describes a POSIX feature group, then add boilerplate code to
+ <boost/config/suffix.hpp>
+ to auto-detect the feature where possible (if you are wondering why we can't
+ use POSIX feature test macro directly, remember that many of these features
+ can be added by third party libraries, and are not therefore identified inside
+ <code class="computeroutput"><unistd.h></code>).
+ 
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="boost_config.guidelines_for_boost_authors.modifying_the_boost_configuration_headers"></a><a class="link" href="guidelines_for_boost_authors.html#boost_config.guidelines_for_boost_authors.modifying_the_boost_configuration_headers" title="Modifying the Boost Configuration Headers">Modifying
+ the Boost Configuration Headers</a>
+</h3></div></div></div>
+
+ The aim of boost's configuration setup is that the configuration headers
+ should be relatively stable - a boost user should not have to recompile their
+ code just because the configuration for some compiler that they're not interested
+ in has changed. Separating the configuration into separate compiler/standard
+ library/platform sections provides for part of this stability, but boost
+ authors require some amount of restraint as well, in particular:
+ 
+
+ <boost/config.hpp>
+ should never change, don't alter this file.
+ 
+
+ <boost/config/user.hpp>
+ is included by default, don't add extra code to this file unless you have
+ to. If you do, please remember to update libs/config/tools/configure.in
+ as well.
+ 
+
+ <boost/config/suffix.hpp>
+ is always included so be careful about modifying this file as it breaks dependencies
+ for everyone. This file should include only "boilerplate" configuration
+ code, and generally should change only when new macros are added.
+ 
+
+ <boost/config/select_compiler_config.hpp>,
+ <boost/config/select_platform_config.hpp>
+ and <boost/config/select_stdlib_config.hpp>
+ are included by default and should change only if support for a new compiler/standard
+ library/platform is added.
+ 
+
+ The compiler/platform/standard library selection code is set up so that unknown
+ platforms are ignored and assumed to be fully standards compliant - this
+ gives unknown platforms a "sporting chance" of working "as
+ is" even without running the configure script.
+ 
+
+ When adding or modifying the individual mini-configs, assume that future,
+ as yet unreleased versions of compilers, have all the defects of the current
+ version. Although this is perhaps unnecessarily pessimistic, it cuts down
+ on the maintenance of these files, and experience suggests that pessimism
+ is better placed than optimism here!
+ 
+</div>
+</div>
+<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
+<td align="left"></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Beman Dawes, Vesa Karvonen, John
+ Maddock
+ 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)
+ 
+</div></td>
+</tr></table>
+<hr>
+<div class="spirit-nav">
+<a accesskey="p" href="boost_macro_reference.html"><img src="../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.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="rationale.html"><img src="../../../../../doc/src/images/next.png" alt="Next"></a>
+</div>
+</body>
+</html>

Added: website/public_html/live/doc/fixes/boost_1_51_0/libs/config/doc/html/boost_config/rationale.html
==============================================================================
--- (empty file)
+++ website/public_html/live/doc/fixes/boost_1_51_0/libs/config/doc/html/boost_config/rationale.html 2012-11-20 15:40:09 EST (Tue, 20 Nov 2012)
@@ -0,0 +1,124 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
+<title>Rationale</title>
+<link rel="stylesheet" href="../../../../../doc/src/boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="../index.html" title="Boost.Config">
+<link rel="up" href="../index.html" title="Boost.Config">
+<link rel="prev" href="guidelines_for_boost_authors.html" title="Guidelines for Boost Authors">
+<link rel="next" href="acknowledgements.html" title="Acknowledgements">
+</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">Home</td>
+<td align="center">Libraries</td>
+<td align="center">People</td>
+<td align="center">FAQ</td>
+<td align="center">More</td>
+</tr></table>
+<hr>
+<div class="spirit-nav">
+<a accesskey="p" href="guidelines_for_boost_authors.html"><img src="../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.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="acknowledgements.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="boost_config.rationale"></a><a class="link" href="rationale.html" title="Rationale">Rationale</a>
+</h2></div></div></div>
+<div class="toc"><dl>
+<dt>The problem</dt>
+<dt>The solution</dt>
+</dl></div>
+
+ The problem with many traditional "textbook" implementations of configuration
+ headers (where all the configuration options are in a single "monolithic"
+ header) is that they violate certain fundamental software engineering principles
+ which would have the effect of making boost more fragile, more difficult to
+ maintain and more difficult to use safely. You can find a description of the
+ principles from the <a href="http://www.objectmentor.com/resources/articles/Principles_and_Patterns.pdf" target="_top">following
+ article</a>.
+ 
+<div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="boost_config.rationale.the_problem"></a><a class="link" href="rationale.html#boost_config.rationale.the_problem" title="The problem">The problem</a>
+</h3></div></div></div>
+
+ Consider a situation in which you are concurrently developing on multiple
+ platforms. Then consider adding a new platform or changing the platform definitions
+ of an existing platform. What happens? Everything, and this does literally
+ mean everything, recompiles. Isn't it quite absurd that adding a new platform,
+ which has absolutely nothing to do with previously existing platforms, means
+ that all code on all existing platforms needs to be recompiled?
+ 
+
+ Effectively, there is an imposed physical dependency between platforms that
+ have nothing to do with each other. Essentially, the traditional solution
+ employed by configuration headers does not conform to the Open-Closed Principle:
+ 
+<div class="blockquote"><blockquote class="blockquote">
+ "A module should be open for extension but closed
+ for modification."
+ </blockquote></div>
+
+ Extending a traditional configuration header implies modifying existing code.
+ 
+
+ Furthermore, consider the complexity and fragility of the platform detection
+ code. What if a simple change breaks the detection on some minor platform?
+ What if someone accidentally or on purpose (as a workaround for some other
+ problem) defines some platform dependent macros that are used by the detection
+ code? A traditional configuration header is one of the most volatile headers
+ of the entire library, and more stable elements of Boost would depend on
+ it. This violates the Stable Dependencies Principle:
+ 
+<div class="blockquote"><blockquote class="blockquote">
+ "Depend in the direction of stability."
+ </blockquote></div>
+
+ After even a minor change to a traditional configuration header on one minor
+ platform, almost everything on every platform should be tested if we follow
+ sound software engineering practice.
+ 
+
+ Another important issue is that it is not always possible to submit changes
+ to <code class="computeroutput"><boost/config.hpp></code>.
+ Some boost users are currently working on platforms using tools and libraries
+ that are under strict Non-Disclosure Agreements. In this situation it is
+ impossible to submit changes to a traditional monolithic configuration header,
+ instead some method by which the user can insert their own configuration
+ code must be provided.
+ 
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="boost_config.rationale.the_solution"></a><a class="link" href="rationale.html#boost_config.rationale.the_solution" title="The solution">The solution</a>
+</h3></div></div></div>
+
+ The approach taken by boost's configuration headers is to separate configuration
+ into three orthogonal parts: the compiler, the standard library and the platform.
+ Each compiler/standard library/platform gets its own mini-configuration header,
+ so that changes to one compiler's configuration (for example) does not affect
+ other compilers. In addition there are measures that can be taken both to
+ omit the compiler/standard library/platform detection code (so that adding
+ support to a new platform does not break dependencies), or to freeze the
+ configuration completely; providing almost complete protection against dependency
+ changes.
+ 
+</div>
+</div>
+<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
+<td align="left"></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Beman Dawes, Vesa Karvonen, John
+ Maddock
+ 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)
+ 
+</div></td>
+</tr></table>
+<hr>
+<div class="spirit-nav">
+<a accesskey="p" href="guidelines_for_boost_authors.html"><img src="../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.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="acknowledgements.html"><img src="../../../../../doc/src/images/next.png" alt="Next"></a>
+</div>
+</body>
+</html>

Added: website/public_html/live/doc/fixes/boost_1_51_0/libs/config/doc/html/index.html
==============================================================================
--- (empty file)
+++ website/public_html/live/doc/fixes/boost_1_51_0/libs/config/doc/html/index.html 2012-11-20 15:40:09 EST (Tue, 20 Nov 2012)
@@ -0,0 +1,960 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
+<title>Boost.Config</title>
+<link rel="stylesheet" href="../../../../doc/src/boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="Boost.Config">
+<link rel="next" href="boost_config/boost_macro_reference.html" title="Boost Macro Reference">
+</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">Home</td>
+<td align="center">Libraries</td>
+<td align="center">People</td>
+<td align="center">FAQ</td>
+<td align="center">More</td>
+</tr></table>
+<hr>
+<div class="spirit-nav"><a accesskey="n" href="boost_config/boost_macro_reference.html"><img src="../../../../doc/src/images/next.png" alt="Next"></a></div>
+<div class="article">
+<div class="titlepage">
+<div>
+<div><h2 class="title">
+<a name="config"></a>Boost.Config</h2></div>
+<div><div class="authorgroup"><div class="author"><h3 class="author">
+Vesa Karvonen, John Maddock Beman Dawes
+</h3></div></div></div>
+<div>Copyright © 2001-2007 Beman Dawes, Vesa Karvonen, John
+ Maddock</div>
+<div><div class="legalnotice">
+<a name="config.legal"></a>
+ 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)
+ 
+</div></div>
+</div>
+<hr>
+</div>
+<div class="toc">
+Table of Contents
+<dl>
+<dt><a href="index.html#boost_config.configuring_boost_for_your_platform">Configuring
+ Boost for Your Platform</a></dt>
+<dd><dl>
+<dt><a href="index.html#boost_config.configuring_boost_for_your_platform.using_the_default_boost_configuration">Using
+ the default boost configuration</a></dt>
+<dt><a href="index.html#boost_config.configuring_boost_for_your_platform.the__boost_config_hpp__header">The
+ <boost/config.hpp> header</a></dt>
+<dt><a href="index.html#boost_config.configuring_boost_for_your_platform.using_the_configure_script">Using
+ the configure script</a></dt>
+<dt><a href="index.html#boost_config.configuring_boost_for_your_platform.user_settable_options">User
+ settable options</a></dt>
+<dt><a href="index.html#boost_config.configuring_boost_for_your_platform.advanced_configuration_usage">Advanced
+ configuration usage</a></dt>
+<dt><a href="index.html#boost_config.configuring_boost_for_your_platform.testing_the_boost_configuration">Testing
+ the boost configuration</a></dt>
+</dl></dd>
+<dt>Boost Macro Reference</dt>
+<dd><dl>
+<dt><a href="boost_config/boost_macro_reference.html#boost_config.boost_macro_reference.macros_that_describe_c__03_defects">Macros
+ that describe C++03 defects</a></dt>
+<dt><a href="boost_config/boost_macro_reference.html#boost_config.boost_macro_reference.macros_that_describe_optional_features">Macros
+ that describe optional features</a></dt>
+<dt><a href="boost_config/boost_macro_reference.html#boost_config.boost_macro_reference.macros_that_describe_possible_c___future_features">Macros
+ that describe possible C++ future features</a></dt>
+<dt><a href="boost_config/boost_macro_reference.html#boost_config.boost_macro_reference.macros_that_describe_c__11_features_not_supported">Macros
+ that describe C++11 features not supported</a></dt>
+<dt><a href="boost_config/boost_macro_reference.html#boost_config.boost_macro_reference.macros_that_allow_use_of_c__11_features_with_c__03_compilers">Macros
+ that allow use of C++11 features with C++03 compilers</a></dt>
+<dt><a href="boost_config/boost_macro_reference.html#boost_config.boost_macro_reference.boost_helper_macros">Boost
+ Helper Macros</a></dt>
+<dt><a href="boost_config/boost_macro_reference.html#boost_config.boost_macro_reference.boost_informational_macros">Boost
+ Informational Macros</a></dt>
+<dt><a href="boost_config/boost_macro_reference.html#boost_config.boost_macro_reference.boost_deprecated_macros">Boost
+ Deprecated Macros</a></dt>
+<dt><a href="boost_config/boost_macro_reference.html#boost_config.boost_macro_reference.macros_for_libraries_with_separate_source_code">Macros
+ for libraries with separate source code</a></dt>
+</dl></dd>
+<dt><a href="boost_config/guidelines_for_boost_authors.html">Guidelines for
+ Boost Authors</a></dt>
+<dd><dl>
+<dt><a href="boost_config/guidelines_for_boost_authors.html#boost_config.guidelines_for_boost_authors.warnings">Disabling
+ Compiler Warnings</a></dt>
+<dt><a href="boost_config/guidelines_for_boost_authors.html#boost_config.guidelines_for_boost_authors.adding_new_defect_macros">Adding
+ New Defect Macros</a></dt>
+<dt><a href="boost_config/guidelines_for_boost_authors.html#boost_config.guidelines_for_boost_authors.adding_new_feature_test_macros">Adding
+ New Feature Test Macros</a></dt>
+<dt><a href="boost_config/guidelines_for_boost_authors.html#boost_config.guidelines_for_boost_authors.modifying_the_boost_configuration_headers">Modifying
+ the Boost Configuration Headers</a></dt>
+</dl></dd>
+<dt>Rationale</dt>
+<dd><dl>
+<dt>The problem</dt>
+<dt>The solution</dt>
+</dl></dd>
+<dt>Acknowledgements</dt>
+</dl>
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="boost_config.configuring_boost_for_your_platform"></a><a class="link" href="index.html#boost_config.configuring_boost_for_your_platform" title="Configuring Boost for Your Platform">Configuring
+ Boost for Your Platform</a>
+</h2></div></div></div>
+<div class="toc"><dl>
+<dt><a href="index.html#boost_config.configuring_boost_for_your_platform.using_the_default_boost_configuration">Using
+ the default boost configuration</a></dt>
+<dt><a href="index.html#boost_config.configuring_boost_for_your_platform.the__boost_config_hpp__header">The
+ <boost/config.hpp> header</a></dt>
+<dt><a href="index.html#boost_config.configuring_boost_for_your_platform.using_the_configure_script">Using
+ the configure script</a></dt>
+<dt><a href="index.html#boost_config.configuring_boost_for_your_platform.user_settable_options">User
+ settable options</a></dt>
+<dt><a href="index.html#boost_config.configuring_boost_for_your_platform.advanced_configuration_usage">Advanced
+ configuration usage</a></dt>
+<dt><a href="index.html#boost_config.configuring_boost_for_your_platform.testing_the_boost_configuration">Testing
+ the boost configuration</a></dt>
+</dl></div>
+<div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="boost_config.configuring_boost_for_your_platform.using_the_default_boost_configuration"></a><a class="link" href="index.html#boost_config.configuring_boost_for_your_platform.using_the_default_boost_configuration" title="Using the default boost configuration">Using
+ the default boost configuration</a>
+</h3></div></div></div>
+
+ Boost comes already configured for most common compilers and platforms; you
+ should be able to use boost "as is". Since the compiler is configured
+ separately from the standard library, the default configuration should work
+ even if you replace the compiler's standard library with a third-party standard
+ library (like STLport).
+ 
+
+ Using boost "as is" without trying to reconfigure is the recommended
+ method for using boost. You can, however, run the configure script if you
+ want to, and there are regression tests provided that allow you to test the
+ current boost configuration with your particular compiler setup.
+ 
+
+ Boost library users can request support for additional compilers or platforms
+ by visiting our Trac
+ and submitting a support request.
+ 
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="boost_config.configuring_boost_for_your_platform.the__boost_config_hpp__header"></a><a class="link" href="index.html#boost_config.configuring_boost_for_your_platform.the__boost_config_hpp__header" title="The <boost/config.hpp> header">The
+ <boost/config.hpp> header</a>
+</h3></div></div></div>
+
+ Boost library implementations access configuration macros via
+ 
+<pre class="programlisting">#include <boost/config.hpp>
+</pre>
+
+ While Boost library users are not required to include that file directly,
+ or use those configuration macros, such use is acceptable. The configuration
+ macros are documented as to their purpose, usage, and limitations which makes
+ them usable by both Boost library and user code.
+ 
+
+ Boost <a class="link" href="boost_config/boost_macro_reference.html#config_info_macros">informational</a> or <a class="link" href="boost_config/boost_macro_reference.html#config_helpers">helper</a>
+ macros are designed for use by Boost users as well as for our own internal
+ use. Note however, that the <a class="link" href="boost_config/boost_macro_reference.html#config_features">feature test</a>
+ and <a class="link" href="boost_config/boost_macro_reference.html#config_defects">defect test</a> macros were designed
+ for internal use by Boost libraries, not user code, so they can change at
+ any time (though no gratuitous changes are made to them). Boost library problems
+ resulting from changes to the configuration macros are caught by the Boost
+ regression tests, so the Boost libraries are updated to account for those
+ changes. By contrast, Boost library user code can be adversely affected by
+ changes to the macros without warning. The best way to keep abreast of changes
+ to the macros used in user code is to monitor the discussions on the Boost
+ developers list.
+ 
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="boost_config.configuring_boost_for_your_platform.using_the_configure_script"></a><a name="config_config_script"></a><a class="link" href="index.html#boost_config.configuring_boost_for_your_platform.using_the_configure_script" title="Using the configure script">Using
+ the configure script</a>
+</h3></div></div></div>
+<div class="important"><table border="0" summary="Important">
+<tr>
+<td rowspan="2" align="center" valign="top" width="25"><img alt="[Important]" src="../../../../doc/src/images/important.png"></td>
+<th align="left">Important</th>
+</tr>
+<tr><td align="left" valign="top">
+ This configure script only sets up the Boost headers for use with a particular
+ compiler. It has no effect on Boost.Build, or how the libraries are built.
+ </td></tr>
+</table></div>
+
+ If you know that boost is incorrectly configured for your particular setup,
+ and you are on a UNIX like platform, then you may want to try and improve
+ things by running the boost configure script. From a shell command prompt
+ you will need to cd into <boost-root><code class="computeroutput">/libs/config/</code>
+ and type:
+ 
+<div class="blockquote"><blockquote class="blockquote">
+ <code class="computeroutput">sh ./configure</code>
+ </blockquote></div>
+
+ you will see a list of the items being checked as the script works its way
+ through the regression tests. Note that the configure script only really
+ auto-detects your compiler if it's called g++, c++ or CC. If you are using
+ some other compiler you will need to set one or more of the following environment
+ variables:
+ 
+<div class="informaltable"><table class="table">
+<colgroup>
+<col>
+<col>
+</colgroup>
+<thead><tr>
+<th>
+ 
+ Variable
+ 
+ </th>
+<th>
+ 
+ Description
+ 
+ </th>
+</tr></thead>
+<tbody>
+<tr>
+<td>
+ 
+ CXX
+ 
+ </td>
+<td>
+ 
+ The name of the compiler, for example <code class="computeroutput">c++</code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ CXXFLAGS
+ 
+ </td>
+<td>
+ 
+ The compiler flags to use, for example <code class="computeroutput">-O2</code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ LDFLAGS
+ 
+ </td>
+<td>
+ 
+ The linker flags to use, for example <code class="computeroutput">-L/mypath</code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ LIBS
+ 
+ </td>
+<td>
+ 
+ Any libraries to link in, for example <code class="computeroutput">-lpthread</code>.
+ 
+ </td>
+</tr>
+</tbody>
+</table></div>
+
+ For example to run the configure script with HP aCC, you might use something
+ like:
+ 
+<pre class="programlisting">export CXX="aCC"
+export CXXFLAGS="-Aa -DAportable -D__HPACC_THREAD_SAFE_RB_TREE \
+ -DRWSTD_MULTI_THREAD -DRW_MULTI_THREAD -D_REENTRANT -D_THREAD_SAFE"
+export LDFLAGS="-DAportable"
+export LIBS="-lpthread"
+sh ./configure
+</pre>
+
+ However you run the configure script, when it finishes you will find a new
+ header -<code class="computeroutput">user.hpp</code>- located in the <boost-root><code class="computeroutput">/libs/config/</code>
+ directory. Note that configure does not install this
+ header into your boost include path by default. This header contains
+ all the options generated by the configure script, plus a header-section
+ that contains the user settable options from the default version of <boost/config/user.hpp>
+ (located under <boost-root><code class="computeroutput">/boost/config/</code>).
+ There are two ways you can use this header:
+ 
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem">
+ Option 1: copy the header into <boost-root><code class="computeroutput">/boost/config/</code> so that it replaces the default user.hpp
+ provided by boost. This option allows only one configure-generated setup;
+ boost developers should avoid this option, as it incurs the danger of
+ accidentally committing a configure-modified <boost/config/user.hpp>
+ to the svn repository (something you will not be thanked for!).
+ </li>
+<li class="listitem">
+ Option 2: give the header a more memorable
+ name, and place it somewhere convenient; then, define the macro <code class="computeroutput">BOOST_USER_CONFIG</code> to point to it. For
+ example create a new sub-directory <boost-root><code class="computeroutput">/boost/config/</code> <code class="computeroutput">user/</code>, and copy the header there; for example
+ as <code class="computeroutput">multithread-gcc-config.hpp</code>. Then, when compiling add the command
+ line option: <code class="computeroutput">-DBOOST_USER_CONFIG="<boost/config/user/multithread-gcc-config.hpp>"</code>,
+ and boost will use the new configuration header. This option allows you
+ to generate more than one configuration header, and to keep them separate
+ from the boost source - so that updates to the source do not interfere
+ with your configuration.
+ </li>
+</ul></div>
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="boost_config.configuring_boost_for_your_platform.user_settable_options"></a><a name="config_user_settable"></a><a class="link" href="index.html#boost_config.configuring_boost_for_your_platform.user_settable_options" title="User settable options">User
+ settable options</a>
+</h3></div></div></div>
+
+ There are some configuration-options that represent user choices, rather
+ than compiler defects or platform specific options. These are listed in
+ <code class="computeroutput"><boost/config/user.hpp></code>
+ and at the start of a configure-generated <code class="computeroutput">user.hpp</code> header.
+ You can define these on the command line, or by editing <code class="computeroutput"><boost/config/user.hpp></code>, they are listed in the following table:
+ 
+<div class="informaltable"><table class="table">
+<colgroup>
+<col>
+<col>
+</colgroup>
+<thead><tr>
+<th>
+ 
+ Macro
+ 
+ </th>
+<th>
+ 
+ Description
+ 
+ </th>
+</tr></thead>
+<tbody>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_USER_CONFIG</code>
+ 
+ </td>
+<td>
+ 
+ When defined, it should point to the name of the user configuration
+ file to include prior to any boost configuration files. When not
+ defined, defaults to <boost/config/user.hpp>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_COMPILER_CONFIG</code>
+ 
+ </td>
+<td>
+ 
+ When defined, it should point to the name of the compiler configuration
+ file to use. Defining this cuts out the compiler selection logic,
+ and eliminates the dependency on the header containing that logic.
+ For example if you are using gcc, then you could define BOOST_COMPILER_CONFIG
+ to <boost/config/compiler/gcc.hpp>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_STDLIB_CONFIG</code>
+ 
+ </td>
+<td>
+ 
+ When defined, it should point to the name of the standard library
+ configuration file to use. Defining this cuts out the standard
+ library selection logic, and eliminates the dependency on the header
+ containing that logic. For example if you are using STLport, then
+ you could define <code class="computeroutput">BOOST_STDLIB_CONFIG</code>
+ to <boost/config/stdlib/stlport.hpp>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_PLATFORM_CONFIG</code>
+ 
+ </td>
+<td>
+ 
+ When defined, it should point to the name of the platform configuration
+ file to use. Defining this cuts out the platform selection logic,
+ and eliminates the dependency on the header containing that logic.
+ For example if you are compiling on linux, then you could define
+ <code class="computeroutput">BOOST_PLATFORM_CONFIG</code>
+ to <boost/config/platform/linux.hpp>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_COMPILER_CONFIG</code>
+ 
+ </td>
+<td>
+ 
+ When defined, no compiler configuration file is selected or included,
+ define when the compiler is fully conformant with the standard,
+ or where the user header (see <code class="computeroutput">BOOST_USER_CONFIG</code>),
+ has had any options necessary added to it, for example by an autoconf
+ generated configure script.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_STDLIB_CONFIG</code>
+ 
+ </td>
+<td>
+ 
+ When defined, no standard library configuration file is selected
+ or included, define when the standard library is fully conformant
+ with the standard, or where the user header (see <code class="computeroutput">BOOST_USER_CONFIG</code>), has had any
+ options necessary added to it, for example by an autoconf generated
+ configure script.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_PLATFORM_CONFIG</code>
+ 
+ </td>
+<td>
+ 
+ When defined, no platform configuration file is selected or included,
+ define when the platform is fully conformant with the standard
+ (and has no useful extra features), or where the user header (see
+ <code class="computeroutput">BOOST_USER_CONFIG</code>),
+ has had any options necessary added to it, for example by an autoconf
+ generated configure script.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CONFIG</code>
+ 
+ </td>
+<td>
+ 
+ Equivalent to defining all of <code class="computeroutput">BOOST_NO_COMPILER_CONFIG</code>,
+ <code class="computeroutput">BOOST_NO_STDLIB_CONFIG</code>
+ and <code class="computeroutput">BOOST_NO_PLATFORM_CONFIG</code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_STRICT_CONFIG</code>
+ 
+ </td>
+<td>
+ 
+ The normal behavior for compiler versions that are newer than the
+ last known version, is to assume that they have all the same defects
+ as the last known version. By setting this define, then compiler
+ versions that are newer than the last known version are assumed
+ to be fully conforming with the standard. This is probably most
+ useful for boost developers or testers, and for those who want
+ to use boost to test beta compiler versions.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_ASSERT_CONFIG</code>
+ 
+ </td>
+<td>
+ 
+ When this flag is set, if the config finds anything unknown, then
+ it will stop with a #error rather than continue. Boost regression
+ testers should set this define, as should anyone who wants to quickly
+ check whether boost is supported on their platform.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_DISABLE_THREADS</code>
+ 
+ </td>
+<td>
+ 
+ When defined, disables threading support, even if the compiler
+ in its current translation mode supports multiple threads.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_DISABLE_WIN32</code>
+ 
+ </td>
+<td>
+ 
+ When defined, disables the use of Win32 specific API's, even when
+ these are available. Also has the effect of setting <code class="computeroutput">BOOST_DISABLE_THREADS</code> unless
+ <code class="computeroutput">BOOST_HAS_PTHREADS</code>
+ is set. This option may be set automatically by the config system
+ when it detects that the compiler is in "strict mode".
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_DISABLE_ABI_HEADERS</code>
+ 
+ </td>
+<td>
+ 
+ Stops boost headers from including any prefix/suffix headers that
+ normally control things like struct packing and alignment.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_ABI_PREFIX</code>
+ 
+ </td>
+<td>
+ 
+ A prefix header to include in place of whatever boost.config would
+ normally select, any replacement should set up struct packing and
+ alignment options as required.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_ABI_SUFFIX</code>
+ 
+ </td>
+<td>
+ 
+ A suffix header to include in place of whatever boost.config would
+ normally select, any replacement should undo the effects of the
+ prefix header.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_ALL_DYN_LINK</code>
+ 
+ </td>
+<td>
+ 
+ Forces all libraries that have separate source, to be linked as
+ dll's rather than static libraries on Microsoft Windows (this macro
+ is used to turn on <code class="computeroutput">__declspec(dllimport)</code> modifiers, so that the compiler
+ knows which symbols to look for in a dll rather than in a static
+ library). Note that there may be some libraries that can only be
+ statically linked (Boost.Test for example) and others which may
+ only be dynamically linked (Boost.Thread for example), in these
+ cases this macro has no effect.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_</code>WHATEVER<code class="computeroutput">_DYN_LINK</code>
+ 
+ </td>
+<td>
+ 
+ Forces library "whatever" to be linked as a dll rather
+ than a static library on Microsoft Windows: replace the WHATEVER
+ part of the macro name with the name of the library that you want
+ to dynamically link to, for example use <code class="computeroutput">BOOST_DATE_TIME_DYN_LINK</code>
+ or <code class="computeroutput">BOOST_REGEX_DYN_LINK</code>
+ etc (this macro is used to turn on <code class="computeroutput">__declspec(dllimport)</code> modifiers, so that the compiler
+ knows which symbols to look for in a dll rather than in a static
+ library). Note that there may be some libraries that can only be
+ statically linked (Boost.Test for example) and others which may
+ only be dynamically linked (Boost.Thread for example), in these
+ cases this macro is unsupported.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_ALL_NO_LIB</code>
+ 
+ </td>
+<td>
+ 
+ Tells the config system not to automatically select which libraries
+ to link against. Normally if a compiler supports #pragma lib, then
+ the correct library build variant will be automatically selected
+ and linked against, simply by the act of including one of that
+ library's headers. This macro turns that feature off.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_</code>WHATEVER<code class="computeroutput">_NO_LIB</code>
+ 
+ </td>
+<td>
+ 
+ Tells the config system not to automatically select which library
+ to link against for library "whatever", replace WHATEVER
+ in the macro name with the name of the library; for example <code class="computeroutput">BOOST_DATE_TIME_NO_LIB</code> or <code class="computeroutput">BOOST_REGEX_NO_LIB</code>. Normally
+ if a compiler supports <code class="computeroutput">#pragma
+ lib</code>, then the correct
+ library build variant will be automatically selected and linked
+ against, simply by the act of including one of that library's headers.
+ This macro turns that feature off.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_LIB_DIAGNOSTIC</code>
+ 
+ </td>
+<td>
+ 
+ Causes the auto-linking code to output diagnostic messages indicating
+ the name of the library that is selected for linking.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_LIB_TOOLSET</code>
+ 
+ </td>
+<td>
+ 
+ Overrides the name of the toolset part of the name of library being
+ linked to; note if defined this must be defined to a quoted string
+ literal, for example "abc".
+ 
+ </td>
+</tr>
+</tbody>
+</table></div>
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="boost_config.configuring_boost_for_your_platform.advanced_configuration_usage"></a><a class="link" href="index.html#boost_config.configuring_boost_for_your_platform.advanced_configuration_usage" title="Advanced configuration usage">Advanced
+ configuration usage</a>
+</h3></div></div></div>
+<div class="toc"><dl>
+<dt><a href="index.html#boost_config.configuring_boost_for_your_platform.advanced_configuration_usage.example_1__creating_our_own_frozen_configuration">Example
+ 1: creating our own frozen configuration</a></dt>
+<dt><a href="index.html#boost_config.configuring_boost_for_your_platform.advanced_configuration_usage.example_2__skipping_files_that_you_don_t_need">Example
+ 2: skipping files that you don't need</a></dt>
+<dt><a href="index.html#boost_config.configuring_boost_for_your_platform.advanced_configuration_usage.example_3__using_configure_script_to_freeze_the_boost_configuration">Example
+ 3: using configure script to freeze the boost configuration</a></dt>
+</dl></div>
+
+ By setting various macros on the compiler command line or by editing <boost/config/user.hpp>,
+ the boost configuration setup can be optimised in a variety of ways.
+ 
+
+ Boost's configuration is structured so that the user-configuration is included
+ first (defaulting to <boost/config/user.hpp>
+ if <code class="computeroutput">BOOST_USER_CONFIG</code> is not
+ defined). This sets up any user-defined policies, and gives the user-configuration
+ a chance to influence what happens next.
+ 
+
+ Next the compiler, standard library, and platform configuration files are
+ included. These are included via macros (<code class="computeroutput">BOOST_COMPILER_CONFIG</code>
+ etc, <a class="link" href="index.html#config_user_settable">see user settable macros</a>),
+ and if the corresponding macro is undefined then a separate header that detects
+ which compiler/standard library/platform is in use is included in order to
+ set these. The config can be told to ignore these headers altogether if the
+ corresponding <code class="computeroutput">BOOST_NO_XXX</code>
+ macro is set (for example <code class="computeroutput">BOOST_NO_COMPILER_CONFIG</code>
+ to disable including any compiler configuration file - <a class="link" href="index.html#config_user_settable">see
+ user settable macros</a>).
+ 
+
+ Finally the boost configuration header, includes <boost/config/suffix.hpp>;
+ this header contains any boiler plate configuration code - for example where
+ one boost macro being set implies that another must be set also.
+ 
+
+ The following usage examples represent just a few of the possibilities:
+ 
+<div class="section">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="boost_config.configuring_boost_for_your_platform.advanced_configuration_usage.example_1__creating_our_own_frozen_configuration"></a><a class="link" href="index.html#boost_config.configuring_boost_for_your_platform.advanced_configuration_usage.example_1__creating_our_own_frozen_configuration" title="Example 1: creating our own frozen configuration">Example
+ 1: creating our own frozen configuration</a>
+</h4></div></div></div>
+
+ Lets suppose that we're building boost with Visual C++ 6, and STLport 4.0.
+ Lets suppose also that we don't intend to update our compiler or standard
+ library any time soon. In order to avoid breaking dependencies when we
+ update boost, we may want to "freeze" our configuration headers,
+ so that we only have to rebuild our project if the boost code itself has
+ changed, and not because the boost config has been updated for more recent
+ versions of Visual C++ or STLport. We'll start by realising that the configuration
+ files in use are: <boost/config/compiler/visualc.hpp> for the compiler, <boost/config/stdlib/stlport.hpp> for the
standard library, and
+ <boost/config/platform/win32.hpp> for the platform. Next we'll
+ create our own private configuration directory: <code class="computeroutput">boost/config/mysetup/</code>, and copy the configuration files into
+ there. Finally, open up <boost/config/user.hpp>
+ and edit the following defines:
+ 
+<pre class="programlisting">#define BOOST_COMPILER_CONFIG "boost/config/mysetup/visualc.hpp"
+#define BOOST_STDLIB_CONFIG "boost/config/mysetup/stlport.hpp"
+#define BOOST_USER_CONFIG "boost/config/mysetup/win32.hpp"
+</pre>
+
+ Now when you use boost, its configuration header will go straight to our
+ "frozen" versions, and ignore the default versions, you will
+ now be insulated from any configuration changes when you update boost.
+ This technique is also useful if you want to modify some of the boost configuration
+ files; for example if you are working with a beta compiler release not
+ yet supported by boost.
+ 
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="boost_config.configuring_boost_for_your_platform.advanced_configuration_usage.example_2__skipping_files_that_you_don_t_need"></a><a class="link" href="index.html#boost_config.configuring_boost_for_your_platform.advanced_configuration_usage.example_2__skipping_files_that_you_don_t_need" title="Example 2: skipping files that you don't need">Example
+ 2: skipping files that you don't need</a>
+</h4></div></div></div>
+
+ Lets suppose that you're using boost with a compiler that is fully conformant
+ with the standard; you're not interested in the fact that older versions
+ of your compiler may have had bugs, because you know that your current
+ version does not need any configuration macros setting. In a case like
+ this, you can define <code class="computeroutput">BOOST_NO_COMPILER_CONFIG</code>
+ either on the command line, or in <boost/config/user.hpp>,
+ and miss out the compiler configuration header altogether (actually you
+ miss out two headers, one which works out what the compiler is, and one
+ that configures boost for it). This has two consequences: the first is
+ that less code has to be compiled, and the second that you have removed
+ a dependency on two boost headers.
+ 
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="boost_config.configuring_boost_for_your_platform.advanced_configuration_usage.example_3__using_configure_script_to_freeze_the_boost_configuration"></a><a class="link" href="index.html#boost_config.configuring_boost_for_your_platform.advanced_configuration_usage.example_3__using_configure_script_to_freeze_the_boost_configuration" title="Example 3: using configure script to freeze the boost configuration">Example
+ 3: using configure script to freeze the boost configuration</a>
+</h4></div></div></div>
+
+ If you are working on a unix-like platform then you can use the configure
+ script to generate a "frozen" configuration based on your current
+ compiler setup - <a class="link" href="index.html#config_config_script">see using the configure
+ script for more details</a>.
+ 
+</div>
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="boost_config.configuring_boost_for_your_platform.testing_the_boost_configuration"></a><a class="link" href="index.html#boost_config.configuring_boost_for_your_platform.testing_the_boost_configuration" title="Testing the boost configuration">Testing
+ the boost configuration</a>
+</h3></div></div></div>
+
+ The boost configuration library provides a full set of regression test programs
+ under the <boost-root><code class="computeroutput">/boost/config/</code>
+ <code class="computeroutput">test/</code>
+ sub-directory:
+ 
+<div class="informaltable"><table class="table">
+<colgroup>
+<col>
+<col>
+</colgroup>
+<thead><tr>
+<th>
+ 
+ File
+ 
+ </th>
+<th>
+ 
+ Description
+ 
+ </th>
+</tr></thead>
+<tbody>
+<tr>
+<td>
+ 
+ <code class="computeroutput">config_info.cpp</code>
+ 
+ </td>
+<td>
+ 
+ Prints out a detailed description of your compiler/standard library/platform
+ setup, plus your current boost configuration. The information provided
+ by this program useful in setting up the boost configuration files.
+ If you report that boost is incorrectly configured for your compiler/library/platform
+ then please include the output from this program when reporting
+ the changes required.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">config_test.cpp</code>
+ 
+ </td>
+<td>
+ 
+ A monolithic test program that includes most of the individual
+ test cases. This provides a quick check to see if boost is correctly
+ configured for your compiler/library/platform.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">limits_test.cpp</code>
+ 
+ </td>
+<td>
+ 
+ Tests your standard library's <code class="computeroutput">std::numeric_limits</code>
+ implementation (or its boost provided replacement if <code class="computeroutput">BOOST_NO_LIMITS</code> is defined).
+ This test file fails with most versions of numeric_limits, mainly
+ due to the way that some compilers treat NAN's and infinity.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">no_*pass.cpp</code>
+ 
+ </td>
+<td>
+ 
+ Individual compiler defect test files. Each of these should compile,
+ if one does not then the corresponding <code class="computeroutput">BOOST_NO_XXX</code>
+ macro needs to be defined - see each test file for specific details.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">no_*fail.cpp</code>
+ 
+ </td>
+<td>
+ 
+ Individual compiler defect test files. Each of these should not
+ compile, if one does then the corresponding <code class="computeroutput">BOOST_NO_XXX</code>
+ macro is defined when it need not be - see each test file for specific
+ details.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">has_*pass.cpp</code>
+ 
+ </td>
+<td>
+ 
+ Individual feature test files. If one of these does not compile
+ then the corresponding <code class="computeroutput">BOOST_HAS_XXX</code>
+ macro is defined when it should not be - see each test file for
+ specific details.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">has_*fail.cpp</code>
+ 
+ </td>
+<td>
+ 
+ Individual feature test files. If one of these does compile then
+ the corresponding <code class="computeroutput">BOOST_HAS_XXX</code>
+ macro can be safely defined - see each test file for specific details.
+ 
+ </td>
+</tr>
+</tbody>
+</table></div>
+
+ Although you can run the configuration regression tests as individual test
+ files, there are rather a lot of them, so there are a couple of shortcuts
+ to help you out:
+ 
+
+ If you have built the <a href="../../../../tools/regression/doc/index.html" target="_top">boost
+ regression test driver</a>, then you can use this to produce a nice html
+ formatted report of the results using the supplied test file.
+ 
+
+ Alternatively you can run the configure script like this:
+ 
+<div class="blockquote"><blockquote class="blockquote">
+ <code class="computeroutput">./configure
+ --enable-test</code>
+ </blockquote></div>
+
+ in which case the script will test the current configuration rather than
+ creating a new one from scratch.
+ 
+
+ If you are reporting the results of these tests for a new platform/library/compiler
+ then please include a log of the full compiler output, the output from <code class="computeroutput">config_info.cpp</code>, and the pass/fail test results.
+ 
+</div>
+</div>
+</div>
+<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
+<td align="left">Last revised: November 20, 2012 at 20:32:39 GMT</td>
+<td align="right"><div class="copyright-footer"></div></td>
+</tr></table>
+<hr>
+<div class="spirit-nav"><a accesskey="n" href="boost_config/boost_macro_reference.html"><img src="../../../../doc/src/images/next.png" alt="Next"></a></div>
+</body>
+</html>

Added: website/public_html/live/doc/fixes/boost_1_52_0/libs/config/doc/html/boost_config/acknowledgements.html
==============================================================================
--- (empty file)
+++ website/public_html/live/doc/fixes/boost_1_52_0/libs/config/doc/html/boost_config/acknowledgements.html 2012-11-20 15:40:09 EST (Tue, 20 Nov 2012)
@@ -0,0 +1,62 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
+<title>Acknowledgements</title>
+<link rel="stylesheet" href="../../../../../doc/src/boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="../index.html" title="Boost.Config">
+<link rel="up" href="../index.html" title="Boost.Config">
+<link rel="prev" href="rationale.html" title="Rationale">
+</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">Home</td>
+<td align="center">Libraries</td>
+<td align="center">People</td>
+<td align="center">FAQ</td>
+<td align="center">More</td>
+</tr></table>
+<hr>
+<div class="spirit-nav">
+<a accesskey="p" href="rationale.html"><img src="../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.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>
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="boost_config.acknowledgements"></a><a class="link" href="acknowledgements.html" title="Acknowledgements">Acknowledgements</a>
+</h2></div></div></div>
+
+ Beman Dawes provided the original <code class="computeroutput">config.hpp</code> and
+ part of this document.
+ 
+
+ Vesa Karvonen provided a description of the principles (see <a class="link" href="rationale.html" title="Rationale">rationale</a>)
+ and put together an early version of the current configuration setup.
+ 
+
+ John Maddock put together the configuration current code, the test programs,
+ the configuration script and the reference section of this document.
+ 
+
+ Matias Capeletto converted the docs to quickbook format.
+ 
+
+ Numerous boost members, past and present, have contributed fixes to boost's
+ configuration.
+ 
+</div>
+<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
+<td align="left"></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Beman Dawes, Vesa Karvonen, John
+ Maddock
+ 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)
+ 
+</div></td>
+</tr></table>
+<hr>
+<div class="spirit-nav">
+<a accesskey="p" href="rationale.html"><img src="../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.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>
+</div>
+</body>
+</html>

Added: website/public_html/live/doc/fixes/boost_1_52_0/libs/config/doc/html/boost_config/boost_macro_reference.html
==============================================================================
--- (empty file)
+++ website/public_html/live/doc/fixes/boost_1_52_0/libs/config/doc/html/boost_config/boost_macro_reference.html 2012-11-20 15:40:09 EST (Tue, 20 Nov 2012)
@@ -0,0 +1,5050 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
+<title>Boost Macro Reference</title>
+<link rel="stylesheet" href="../../../../../doc/src/boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="../index.html" title="Boost.Config">
+<link rel="up" href="../index.html" title="Boost.Config">
+<link rel="prev" href="../index.html" title="Boost.Config">
+<link rel="next" href="guidelines_for_boost_authors.html" title="Guidelines for Boost Authors">
+</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">Home</td>
+<td align="center">Libraries</td>
+<td align="center">People</td>
+<td align="center">FAQ</td>
+<td align="center">More</td>
+</tr></table>
+<hr>
+<div class="spirit-nav">
+<a accesskey="p" href="../index.html"><img src="../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.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="guidelines_for_boost_authors.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="boost_config.boost_macro_reference"></a><a class="link" href="boost_macro_reference.html" title="Boost Macro Reference">Boost Macro Reference</a>
+</h2></div></div></div>
+<div class="toc"><dl>
+<dt><a href="boost_macro_reference.html#boost_config.boost_macro_reference.macros_that_describe_c__03_defects">Macros
+ that describe C++03 defects</a></dt>
+<dt><a href="boost_macro_reference.html#boost_config.boost_macro_reference.macros_that_describe_optional_features">Macros
+ that describe optional features</a></dt>
+<dt><a href="boost_macro_reference.html#boost_config.boost_macro_reference.macros_that_describe_possible_c___future_features">Macros
+ that describe possible C++ future features</a></dt>
+<dt><a href="boost_macro_reference.html#boost_config.boost_macro_reference.macros_that_describe_c__11_features_not_supported">Macros
+ that describe C++11 features not supported</a></dt>
+<dt><a href="boost_macro_reference.html#boost_config.boost_macro_reference.macros_that_allow_use_of_c__11_features_with_c__03_compilers">Macros
+ that allow use of C++11 features with C++03 compilers</a></dt>
+<dt><a href="boost_macro_reference.html#boost_config.boost_macro_reference.boost_helper_macros">Boost
+ Helper Macros</a></dt>
+<dt><a href="boost_macro_reference.html#boost_config.boost_macro_reference.boost_informational_macros">Boost
+ Informational Macros</a></dt>
+<dt><a href="boost_macro_reference.html#boost_config.boost_macro_reference.boost_deprecated_macros">Boost
+ Deprecated Macros</a></dt>
+<dt><a href="boost_macro_reference.html#boost_config.boost_macro_reference.macros_for_libraries_with_separate_source_code">Macros
+ for libraries with separate source code</a></dt>
+</dl></div>
+<div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="boost_config.boost_macro_reference.macros_that_describe_c__03_defects"></a><a name="config_defects"></a><a class="link" href="boost_macro_reference.html#boost_config.boost_macro_reference.macros_that_describe_c__03_defects" title="Macros that describe C++03 defects">Macros
+ that describe C++03 defects</a>
+</h3></div></div></div>
+
+ The following macros all describe features that are required by the C++03
+ standard, if one of the following macros is defined, then it represents a
+ defect in the compiler's conformance with the 2003 standard.
+ 
+<div class="informaltable"><table class="table">
+<colgroup>
+<col>
+<col>
+<col>
+</colgroup>
+<thead><tr>
+<th>
+ 
+ Macro
+ 
+ </th>
+<th>
+ 
+ Section
+ 
+ </th>
+<th>
+ 
+ Description
+ 
+ </th>
+</tr></thead>
+<tbody>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_BCB_PARTIAL_SPECIALIZATION_BUG</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ The compiler exibits certain partial specialisation bug - probably
+ Borland C++ Builder specific.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_FUNCTION_SCOPE_USING_DECLARATION_BREAKS_ADL</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ Argument dependent lookup fails if there is a using declaration
+ for the symbol being looked up in the current scope. For example,
+ using <code class="computeroutput">boost::get_pointer</code>; prevents ADL from
+ finding overloads of <code class="computeroutput">get_pointer</code>
+ in namespaces nested inside boost (but not elsewhere). Probably
+ Borland specific.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_ADL_BARRIER</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ The compiler locates and searches namespaces that it should *not*
+ in fact search when performing argument dependent lookup.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_ARGUMENT_DEPENDENT_LOOKUP</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ Compiler does not implement argument-dependent lookup (also named
+ Koenig lookup); see std::3.4.2 [basic.koenig.lookup]
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_AUTO_PTR</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ If the compiler / library supplies non-standard or broken <code class="computeroutput">std::auto_ptr</code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_COMPLETE_VALUE_INITIALIZATION</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ Compiler has not completely implemented value-initialization. See
+ also <a href="../../../../utility/value_init.htm#compiler_issues" target="_top">The
+ Utility/Value Init docs</a>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CTYPE_FUNCTIONS</code>
+ 
+ </td>
+<td>
+ 
+ Platform
+ 
+ </td>
+<td>
+ 
+ The Platform does not provide functions for the character-classifying
+ operations <code class="computeroutput"><ctype.h></code> and <code class="computeroutput"><cctype></code>,
+ only macros.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CV_SPECIALIZATIONS</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ If template specialisations for cv-qualified types conflict with
+ a specialisation for a cv-unqualififed type.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CV_VOID_SPECIALIZATIONS</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ If template specialisations for cv-void types conflict with a specialisation
+ for void.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CWCHAR</code>
+ 
+ </td>
+<td>
+ 
+ Platform
+ 
+ </td>
+<td>
+ 
+ The Platform does not provide <code class="computeroutput"><wchar.h></code>
+ and <code class="computeroutput"><cwchar></code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CWCTYPE</code>
+ 
+ </td>
+<td>
+ 
+ Platform
+ 
+ </td>
+<td>
+ 
+ The Platform does not provide <code class="computeroutput"><wctype.h></code>
+ and <code class="computeroutput"><cwctype></code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_FENV_H</code>
+ 
+ </td>
+<td>
+ 
+ Platform, Standard library
+ 
+ </td>
+<td>
+ 
+ The C standard library doesn't provide <code class="computeroutput"><fenv.h></code>.
+ <boost/detail/fenv.hpp>
+ should be included instead of <code class="computeroutput"><fenv.h></code>
+ for maximum portability on platforms which do provide <code class="computeroutput"><fenv.h></code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_DEPENDENT_NESTED_DERIVATIONS</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ The compiler fails to compile a nested class that has a dependent
+ base class:
+
+<pre xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="table-programlisting">template<typename T>
+struct foo : {
+ template<typename U>
+ struct bar : public U {};
+</pre>
+
+ };
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_DEPENDENT_TYPES_IN_TEMPLATE_VALUE_PARAMETERS</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ Template value parameters cannot have a dependent type, for example:
+
+<pre xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="table-programlisting">template<class T, typename T::type value>
+class X { ... };
+</pre>
+
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_EXCEPTION_STD_NAMESPACE</code>
+ 
+ </td>
+<td>
+ 
+ Standard Library
+ 
+ </td>
+<td>
+ 
+ The standard library does not put some or all of the contents of
+ <code class="computeroutput"><exception></code> in namespace std.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_EXCEPTIONS</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ The compiler does not support exception handling (this setting
+ is typically required by many C++ compilers for embedded platforms).
+ Note that there is no requirement for boost libraries to honor
+ this configuration setting - indeed doing so may be impossible
+ in some cases. Those libraries that do honor this will typically
+ abort if a critical error occurs - you have been warned!
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_EXPLICIT_FUNCTION_TEMPLATE_ARGUMENTS</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ Can only use deduced template arguments when calling function template
+ instantiations.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_FUNCTION_TEMPLATE_ORDERING</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ The compiler does not perform function template ordering or its
+ function template ordering is incorrect.
+
+<pre xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="table-programlisting">// #1
+template<class T> void f(T);
+
+// #2
+template<class T,class U> void f(T(*)(U));
+
+void bar(int);
+
+f(&bar); // should choose #2.
+</pre>
+
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_INCLASS_MEMBER_INITIALIZATION</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ Compiler violates std::9.4.2/4.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_INTRINSIC_WCHAR_T</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ The C++ implementation does not provide <code class="computeroutput">wchar_t</code>,
+ or it is really a synonym for another integral type. Use this symbol
+ to decide whether it is appropriate to explicitly specialize a
+ template on <code class="computeroutput">wchar_t</code>
+ if there is already a specialization for other integer types.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_IOSFWD</code>
+ 
+ </td>
+<td>
+ 
+ std lib
+ 
+ </td>
+<td>
+ 
+ The standard library lacks <code class="computeroutput"><iosfwd></code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_IOSTREAM</code>
+ 
+ </td>
+<td>
+ 
+ std lib
+ 
+ </td>
+<td>
+ 
+ The standard library lacks <code class="computeroutput"><iostream></code>,
+ <code class="computeroutput"><istream></code> or <code class="computeroutput"><ostream></code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_IS_ABSTRACT</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ The C++ compiler does not support SFINAE with abstract types, this
+ is covered by <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/cwg_defects.html#337" target="_top">Core
+ Language DR337</a>, but is not part of the current standard.
+ Fortunately most compilers that support SFINAE also support this
+ DR.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_LIMITS</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The C++ implementation does not provide the <code class="computeroutput"><limits></code>
+ header. Never check for this symbol in library code; always include
+ <code class="computeroutput"><boost/limits.hpp></code>, which guarantees to provide
+ <code class="computeroutput">std::numeric_limits</code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_NUMERIC_LIMITS</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ C++11 additions to <code class="computeroutput">std::numeric_limits</code>
+ are not available for use. <code class="computeroutput">static
+ function numeric_limits<T>::lowest()</code> the lowest finite value representable
+ by the numeric type. <code class="computeroutput">static
+ int const
+ max_digits10</code> the number
+ of decimal digits that are required to make sure that two distinct
+ values of the type have distinct decimal representations. <code class="computeroutput">template<>
+ class numeric_limits<char16_t>;</code>, see also <code class="computeroutput">BOOST_NO_CXX11_CHAR16_T</code>,
+ <code class="computeroutput">template<>
+ class numeric_limits<char32_t>;</code> see also <code class="computeroutput">BOOST_NO_CXX11_CHAR32_T</code>.
+ Replaces BOOST_NO_NUMERIC_LIMITS_LOWEST.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_LIMITS_COMPILE_TIME_CONSTANTS</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ Constants such as <code class="computeroutput">numeric_limits<T>::is_signed</code>
+ are not available for use at compile-time.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_LONG_LONG_NUMERIC_LIMITS</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ There is no specialization for <code class="computeroutput">numeric_limits<long
+ long></code>
+ and <code class="computeroutput">numeric_limits<unsigned
+ long long></code>. <code class="computeroutput"><boost/limits.hpp></code>
+ will then add these specializations as a standard library "fix"
+ only if the compiler supports the <code class="computeroutput">long
+ long</code> datatype.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_MEMBER_FUNCTION_SPECIALIZATIONS</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ The compiler does not support the specialization of individual
+ member functions of template classes.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_MEMBER_TEMPLATE_KEYWORD</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ If the compiler supports member templates, but not the template
+ keyword when accessing member template classes.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_MEMBER_TEMPLATE_FRIENDS</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ Member template friend syntax (<code class="computeroutput">template<class
+ P>
+ friend class
+ frd;</code>)
+ described in the C++ Standard, 14.5.3, not supported.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_MEMBER_TEMPLATES</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ Member template functions not fully supported.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_MS_INT64_NUMERIC_LIMITS</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ There is no specialization for <code class="computeroutput">numeric_limits<__int64></code> and <code class="computeroutput">numeric_limits<unsigned
+ __int64></code>.
+ <code class="computeroutput"><boost/limits.hpp></code> will then add these specializations
+ as a standard library "fix", only if the compiler supports
+ the <code class="computeroutput">__int64</code> datatype.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_NESTED_FRIENDSHIP</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ Compiler doesn't allow a nested class to access private members
+ of its containing class. Probably Borland/CodeGear specific.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_OPERATORS_IN_NAMESPACE</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ Compiler requires inherited operator friend functions to be defined
+ at namespace scope, then using'ed to boost. Probably GCC specific.
+ See <boost/operators.hpp> for example.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_PARTIAL_SPECIALIZATION_IMPLICIT_DEFAULT_ARGS</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ The compiler does not correctly handle partial specializations
+ which depend upon default arguments in the primary template.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_POINTER_TO_MEMBER_CONST</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ The compiler does not correctly handle pointers to const member
+ functions, preventing use of these in overloaded function templates.
+ See <boost/functional.hpp> for example.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_POINTER_TO_MEMBER_TEMPLATE_PARAMETERS</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ Pointers to members don't work when used as template parameters.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_PRIVATE_IN_AGGREGATE</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ The compiler misreads 8.5.1, treating classes as non-aggregate
+ if they contain private or protected member functions.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_RTTI</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ The compiler may (or may not) have the typeid operator, but RTTI
+ on the dynamic type of an object is not supported.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_SFINAE</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ The compiler does not support the "Substitution Failure Is
+ Not An Error" meta-programming idiom.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_SFINAE_EXPR</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ The compiler does not support usage of SFINAE with arbitrary expressions.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_STD_ALLOCATOR</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The C++ standard library does not provide a standards conforming
+ <code class="computeroutput">std::allocator</code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_STD_DISTANCE</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The platform does not have a conforming version of <code class="computeroutput">std::distance</code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_STD_ITERATOR</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The C++ implementation fails to provide the <code class="computeroutput">std::iterator</code>
+ class.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_STD_ITERATOR_TRAITS</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The compiler does not provide a standard compliant implementation
+ of <code class="computeroutput">std::iterator_traits</code>. Note that the
+ compiler may still have a non-standard implementation.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_STD_LOCALE</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The standard library lacks <code class="computeroutput">std::locale</code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_STD_MESSAGES</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The standard library lacks a conforming <code class="computeroutput">std::messages</code>
+ facet.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_STD_MIN_MAX</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The C++ standard library does not provide the <code class="computeroutput">min()</code> and <code class="computeroutput">max()</code> template functions that should
+ be in <code class="computeroutput"><algorithm></code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_STD_OUTPUT_ITERATOR_ASSIGN</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ Defined if the standard library's output iterators are not assignable.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_STD_TYPEINFO</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The <typeinfo> header declares <code class="computeroutput">type_info</code>
+ in the global namespace instead of namespace std.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_STD_USE_FACET</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The standard library lacks a conforming <code class="computeroutput">std::use_facet</code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_STD_WSTREAMBUF</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The standard library's implementation of <code class="computeroutput">std::basic_streambuf<wchar_t></code> is either missing, incomplete,
+ or buggy.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_STD_WSTRING</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The standard library lacks <code class="computeroutput">std::wstring</code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_STDC_NAMESPACE</code>
+ 
+ </td>
+<td>
+ 
+ Compiler, Platform
+ 
+ </td>
+<td>
+ 
+ The contents of C++ standard headers for C library functions (the
+ <code class="computeroutput"><c...></code> headers) have not been placed
+ in namespace std. This test is difficult - some libraries "fake"
+ the std C functions by adding using declarations to import them
+ into namespace std, unfortunately they don't necessarily catch
+ all of them...
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_STRINGSTREAM</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The C++ implementation does not provide the <code class="computeroutput"><sstream></code>
+ header.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_SWPRINTF</code>
+ 
+ </td>
+<td>
+ 
+ Platform
+ 
+ </td>
+<td>
+ 
+ The platform does not have a conforming version of <code class="computeroutput">swprintf</code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_TEMPLATE_PARTIAL_SPECIALIZATION</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ Class template partial specialization (14.5.4 [temp.class.spec])
+ not supported.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_TEMPLATED_IOSTREAMS</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The standard library does not provide templated iostream classes.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_TEMPLATED_ITERATOR_CONSTRUCTORS</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The standard library does not provide templated iterator constructors
+ for its containers.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_TEMPLATE_TEMPLATES</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ The compiler does not support template template parameters.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_TYPEID</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ The compiler does not support the typeid operator at all.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_TYPENAME_WITH_CTOR</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ The typename keyword cannot be used when creating a temporary of
+ a Dependent type.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_UNREACHABLE_RETURN_DETECTION</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ If a return is unreachable, then no return statement should be
+ required, however some compilers insist on it, while other issue
+ a bunch of warnings if it is in fact present.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_USING_DECLARATION_OVERLOADS_FROM_TYPENAME_BASE</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ The compiler will not accept a using declaration that brings a
+ function from a typename used as a base class into a derived class
+ if functions of the same name are present in the derived class.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_USING_TEMPLATE</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ The compiler will not accept a using declaration that imports a
+ template class or function from another namespace. Originally a
+ Borland specific problem with imports to/from the global namespace,
+ extended to MSVC6 which has a specific issue with importing template
+ classes (but not functions).
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_VOID_RETURNS</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ The compiler does not allow a void function to return the result
+ of calling another void function.
+
+<pre xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="table-programlisting">void f() {}
+void g() { return f(); }
+</pre>
+
+ 
+ </td>
+</tr>
+</tbody>
+</table></div>
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="boost_config.boost_macro_reference.macros_that_describe_optional_features"></a><a name="config_features"></a><a class="link" href="boost_macro_reference.html#boost_config.boost_macro_reference.macros_that_describe_optional_features" title="Macros that describe optional features">Macros
+ that describe optional features</a>
+</h3></div></div></div>
+
+ The following macros describe features that are not required by the C++ standard.
+ The macro is only defined if the feature is present.
+ 
+<div class="informaltable"><table class="table">
+<colgroup>
+<col>
+<col>
+<col>
+</colgroup>
+<thead><tr>
+<th>
+ 
+ Macro
+ 
+ </th>
+<th>
+ 
+ Section
+ 
+ </th>
+<th>
+ 
+ Description
+ 
+ </th>
+</tr></thead>
+<tbody>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_BETHREADS</code>
+ 
+ </td>
+<td>
+ 
+ Platform
+ 
+ </td>
+<td>
+ 
+ The platform supports BeOS style threads.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_CLOCK_GETTIME</code>
+ 
+ </td>
+<td>
+ 
+ Platform
+ 
+ </td>
+<td>
+ 
+ The platform has the POSIX API <code class="computeroutput">clock_gettime</code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_DIRENT_H</code>
+ 
+ </td>
+<td>
+ 
+ Platform
+ 
+ </td>
+<td>
+ 
+ The platform has the POSIX header <code class="computeroutput"><dirent.h></code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_EXPM1</code>
+ 
+ </td>
+<td>
+ 
+ Platform
+ 
+ </td>
+<td>
+ 
+ The platform has the functions <code class="computeroutput">expm1</code>,
+ <code class="computeroutput">expm1f</code> and <code class="computeroutput">expm1l</code> in <code class="computeroutput"><math.h></code>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_FTIME</code>
+ 
+ </td>
+<td>
+ 
+ Platform
+ 
+ </td>
+<td>
+ 
+ The platform has the Win32 API type FTIME.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_GETSYSTEMTIMEASFILETIME</code>
+ 
+ </td>
+<td>
+ 
+ Platform
+ 
+ </td>
+<td>
+ 
+ The platform has the Win32 API GetSystemTimeAsFileTime.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_GETTIMEOFDAY</code>
+ 
+ </td>
+<td>
+ 
+ Platform
+ 
+ </td>
+<td>
+ 
+ The platform has the POSIX API <code class="computeroutput">gettimeofday</code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_HASH</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The C++ implementation provides the (SGI) hash_set and hash_map
+ classes. When defined, <code class="computeroutput">BOOST_HASH_SET_HEADER</code>
+ and <code class="computeroutput">BOOST_HASH_LIST_HEADER</code>
+ will contain the names of the header needed to access hash_set
+ and hash_map; <code class="computeroutput">BOOST_STD_EXTENSION_NAMESPACE</code>
+ will provide the namespace in which the two class templates reside.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_LOG1P</code>
+ 
+ </td>
+<td>
+ 
+ Platform
+ 
+ </td>
+<td>
+ 
+ The platform has the functions <code class="computeroutput">log1p</code>,
+ <code class="computeroutput">log1pf</code> and <code class="computeroutput">log1pl</code> in <code class="computeroutput"><math.h></code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_MACRO_USE_FACET</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The standard library lacks a conforming <code class="computeroutput">std::use_facet</code>,
+ but has a macro <code class="computeroutput">_USE(loc, Type)</code> that does the job. This is primarily
+ for the Dinkumware std lib.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_MS_INT64</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ The compiler supports the <code class="computeroutput">__int64</code>
+ data type.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_NANOSLEEP</code>
+ 
+ </td>
+<td>
+ 
+ Platform
+ 
+ </td>
+<td>
+ 
+ The platform has the POSIX API nanosleep.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_NL_TYPES_H</code>
+ 
+ </td>
+<td>
+ 
+ Platform
+ 
+ </td>
+<td>
+ 
+ The platform has an <code class="computeroutput"><nl_types.h></code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_NRVO</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ Indicated that the compiler supports the named return value optimization
+ (NRVO). Used to select the most efficient implementation for some
+ function. See <boost/operators.hpp> for example.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_PARTIAL_STD_ALLOCATOR</code>
+ 
+ </td>
+<td>
+ 
+ Standard Library
+ 
+ </td>
+<td>
+ 
+ The standard library has a partially conforming <code class="computeroutput">std::allocator</code>
+ class, but without any of the member templates.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_PTHREAD_DELAY_NP</code>
+ 
+ </td>
+<td>
+ 
+ Platform
+ 
+ </td>
+<td>
+ 
+ The platform has the POSIX API <code class="computeroutput">pthread_delay_np</code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_PTHREAD_MUTEXATTR_SETTYPE</code>
+ 
+ </td>
+<td>
+ 
+ Platform
+ 
+ </td>
+<td>
+ 
+ The platform has the POSIX API <code class="computeroutput">pthread_mutexattr_settype</code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_PTHREAD_YIELD</code>
+ 
+ </td>
+<td>
+ 
+ Platform
+ 
+ </td>
+<td>
+ 
+ The platform has the POSIX API <code class="computeroutput">pthread_yield</code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_PTHREADS</code>
+ 
+ </td>
+<td>
+ 
+ Platform
+ 
+ </td>
+<td>
+ 
+ The platform support POSIX style threads.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_SCHED_YIELD</code>
+ 
+ </td>
+<td>
+ 
+ Platform
+ 
+ </td>
+<td>
+ 
+ The platform has the POSIX API <code class="computeroutput">sched_yield</code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_SGI_TYPE_TRAITS</code>
+ 
+ </td>
+<td>
+ 
+ Compiler, Standard library
+ 
+ </td>
+<td>
+ 
+ The compiler has native support for SGI style type traits.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_STDINT_H</code>
+ 
+ </td>
+<td>
+ 
+ Platform
+ 
+ </td>
+<td>
+ 
+ The platform has a <code class="computeroutput"><stdint.h></code>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_SLIST</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The C++ implementation provides the (SGI) slist class. When defined,
+ <code class="computeroutput">BOOST_SLIST_HEADER</code>
+ will contain the name of the header needed to access <code class="computeroutput">slist</code> and <code class="computeroutput">BOOST_STD_EXTENSION_NAMESPACE</code>
+ will provide the namespace in which <code class="computeroutput">slist</code>
+ resides.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_STLP_USE_FACET</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The standard library lacks a conforming <code class="computeroutput">std::use_facet</code>,
+ but has a workaround class-version that does the job. This is primarily
+ for the STLport std lib.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_TR1_ARRAY</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The library has a TR1 conforming version of <code class="computeroutput"><array></code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_TR1_COMPLEX_OVERLOADS</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The library has a version of <code class="computeroutput"><complex></code>
+ that supports passing scalars to the complex number algorithms.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_TR1_COMPLEX_INVERSE_TRIG</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The library has a version of <code class="computeroutput"><complex></code>
+ that includes the new inverse trig functions from TR1.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_TR1_REFERENCE_WRAPPER</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The library has TR1 conforming reference wrappers in <code class="computeroutput"><functional></code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_TR1_RESULT_OF</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The library has a TR1 conforming result_of template in <code class="computeroutput"><functional></code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_TR1_MEM_FN</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The library has a TR1 conforming mem_fn function template in <code class="computeroutput"><functional></code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_TR1_BIND</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The library has a TR1 conforming bind function template in <code class="computeroutput"><functional></code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_TR1_FUNCTION</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The library has a TR1 conforming function class template in <code class="computeroutput"><functional></code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_TR1_HASH</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The library has a TR1 conforming hash function template in <code class="computeroutput"><functional></code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_TR1_SHARED_PTR</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The library has a TR1 conforming <code class="computeroutput">shared_ptr</code>
+ class template in <code class="computeroutput"><memory></code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_TR1_RANDOM</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The library has a TR1 conforming version of <code class="computeroutput"><random></code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_TR1_REGEX</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The library has a TR1 conforming version of <code class="computeroutput"><regex></code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_TR1_TUPLE</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The library has a TR1 conforming version of <code class="computeroutput"><tuple></code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_TR1_TYPE_TRAITS</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The library has a TR1 conforming version of <code class="computeroutput"><type_traits></code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_TR1_UTILITY</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The library has the TR1 additions to <code class="computeroutput"><utility></code>
+ (tuple interface to <code class="computeroutput">std::pair</code>).
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_TR1_UNORDERED_MAP</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The library has a TR1 conforming version of <code class="computeroutput"><unordered_map></code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_TR1_UNORDERED_SET</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The library has a TR1 conforming version of <code class="computeroutput"><unordered_set></code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_TR1</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ Implies all the other <code class="computeroutput">BOOST_HAS_TR1_*</code> macros should be set.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_THREADS</code>
+ 
+ </td>
+<td>
+ 
+ Platform, Compiler
+ 
+ </td>
+<td>
+ 
+ Defined if the compiler, in its current translation mode, supports
+ multiple threads of execution.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_TWO_ARG_USE_FACET</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ The standard library lacks a conforming std::use_facet, but has
+ a two argument version that does the job. This is primarily for
+ the Rogue Wave std lib.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_UNISTD_H</code>
+ 
+ </td>
+<td>
+ 
+ Platform
+ 
+ </td>
+<td>
+ 
+ The Platform provides <code class="computeroutput"><unistd.h></code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_WINTHREADS</code>
+ 
+ </td>
+<td>
+ 
+ Platform
+ 
+ </td>
+<td>
+ 
+ The platform supports MS Windows style threads.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_MSVC_STD_ITERATOR</code>
+ 
+ </td>
+<td>
+ 
+ Standard library
+ 
+ </td>
+<td>
+ 
+ Microsoft's broken version of <code class="computeroutput">std::iterator</code>
+ is being used. This implies that <code class="computeroutput">std::iterator</code>
+ takes no more than two template parameters.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_MSVC6_MEMBER_TEMPLATES</code>
+ 
+ </td>
+<td>
+ 
+ Compiler
+ 
+ </td>
+<td>
+ 
+ Microsoft Visual C++ 6.0 has enough member template idiosyncrasies
+ (being polite) that <code class="computeroutput">BOOST_NO_MEMBER_TEMPLATES</code>
+ is defined for this compiler. <code class="computeroutput">BOOST_MSVC6_MEMBER_TEMPLATES</code>
+ is defined to allow compiler specific workarounds. This macro gets
+ defined automatically if <code class="computeroutput">BOOST_NO_MEMBER_TEMPLATES</code>
+ is not defined - in other words this is treated as a strict subset
+ of the features required by the standard.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_STDINT_H</code>
+ 
+ </td>
+<td>
+ 
+ Platform
+ 
+ </td>
+<td>
+ 
+ There are no 1998 C++ Standard headers <code class="computeroutput"><stdint.h></code>
+ or <code class="computeroutput"><cstdint></code>, although the 1999 C Standard
+ does include <code class="computeroutput"><stdint.h></code>.
+ If <code class="computeroutput"><stdint.h></code> is present, <code class="computeroutput"><boost/stdint.h></code>
+ can make good use of it, so a flag is supplied (signalling presence;
+ thus the default is not present, conforming to the current C++
+ standard).
+ 
+ </td>
+</tr>
+</tbody>
+</table></div>
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="boost_config.boost_macro_reference.macros_that_describe_possible_c___future_features"></a><a class="link" href="boost_macro_reference.html#boost_config.boost_macro_reference.macros_that_describe_possible_c___future_features" title="Macros that describe possible C++ future features">Macros
+ that describe possible C++ future features</a>
+</h3></div></div></div>
+
+ The following macros describe features that may be included in some future
+ ISO C++ standard, but have not yet been approved for inclusion in the language.
+ 
+<div class="informaltable"><table class="table">
+<colgroup>
+<col>
+<col>
+</colgroup>
+<thead><tr>
+<th>
+ 
+ Macro
+ 
+ </th>
+<th>
+ 
+ Description
+ 
+ </th>
+</tr></thead>
+<tbody><tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_CONCEPTS</code>
+ 
+ </td>
+<td>
+ 
+ The compiler supports concepts.
+ 
+ </td>
+</tr></tbody>
+</table></div>
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="boost_config.boost_macro_reference.macros_that_describe_c__11_features_not_supported"></a><a class="link" href="boost_macro_reference.html#boost_config.boost_macro_reference.macros_that_describe_c__11_features_not_supported" title="Macros that describe C++11 features not supported">Macros
+ that describe C++11 features not supported</a>
+</h3></div></div></div>
+
+ The following macros describe features in the 2011 ISO C++ standard, formerly
+ known as C++0x, that are not yet supported by a particular compiler or library.
+ 
+<div class="informaltable"><table class="table">
+<colgroup>
+<col>
+<col>
+</colgroup>
+<thead><tr>
+<th>
+ 
+ Macro
+ 
+ </th>
+<th>
+ 
+ Description
+ 
+ </th>
+</tr></thead>
+<tbody>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_ALLOCATOR</code>
+ 
+ </td>
+<td>
+ 
+ The standard library does not provide a C++11 version of <code class="computeroutput">std::allocator</code> in <memory>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_ATOMIC_SP</code>
+ 
+ </td>
+<td>
+ 
+ The standard library <memory> does not support atomic smart
+ pointer operations.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_ARRAY</code>
+ 
+ </td>
+<td>
+ 
+ The standard library does not provide header <array>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_CHRONO</code>
+ 
+ </td>
+<td>
+ 
+ The standard library does not provide header <chrono>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_CODECVT</code>
+ 
+ </td>
+<td>
+ 
+ The standard library does not provide header <codecvt>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_CONDITION_VARIABLE</code>
+ 
+ </td>
+<td>
+ 
+ The standard library does not provide header <condition_variable>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_FORWARD_LIST</code>
+ 
+ </td>
+<td>
+ 
+ The standard library does not provide header <forward_list>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_FUNCTIONAL</code>
+ 
+ </td>
+<td>
+ 
+ The standard library does not provide a C++11 compatible version
+ of <functional>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_FUTURE</code>
+ 
+ </td>
+<td>
+ 
+ The standard library does not provide header <future>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_INITIALIZER_LIST</code>
+ 
+ </td>
+<td>
+ 
+ The standard library does not provide header <initializer_list>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_MUTEX</code>
+ 
+ </td>
+<td>
+ 
+ The standard library does not provide header <mutex>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_RANDOM</code>
+ 
+ </td>
+<td>
+ 
+ The standard library does not provide header <random>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_RATIO</code>
+ 
+ </td>
+<td>
+ 
+ The standard library does not provide header <ratio>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_REGEX</code>
+ 
+ </td>
+<td>
+ 
+ The standard library does not provide header <regex>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_SYSTEM_ERROR</code>
+ 
+ </td>
+<td>
+ 
+ The standard library does not provide header <system_error>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_THREAD</code>
+ 
+ </td>
+<td>
+ 
+ The standard library does not provide header <thread>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_TUPLE</code>
+ 
+ </td>
+<td>
+ 
+ The standard library does not provide header <tuple>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_TYPEINDEX</code>
+ 
+ </td>
+<td>
+ 
+ The standard library does not provide header <typeindex>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_TYPE_TRAITS</code>
+ 
+ </td>
+<td>
+ 
+ The standard library does not provide header <type_traits>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_UNORDERED_MAP</code>
+ 
+ </td>
+<td>
+ 
+ The standard library does not provide header <unordered_map>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_UNORDERED_SET</code>
+ 
+ </td>
+<td>
+ 
+ The standard library does not provide header <unordered_set>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_SMART_PTR</code>
+ 
+ </td>
+<td>
+ 
+ The standard library header <memory> has no shared_ptr and
+ unique_ptr.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_AUTO_DECLARATIONS</code>
+ 
+ </td>
+<td>
+ 
+ The compiler does not support type deduction for variables declared
+ with the <code class="computeroutput">auto</code> keyword
+ (<code class="computeroutput">auto var
+ = ...;</code>).
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_AUTO_MULTIDECLARATIONS</code>
+ 
+ </td>
+<td>
+ 
+ The compiler does not support type deduction for multiple variables
+ declared with the <code class="computeroutput">auto</code>
+ keyword (<code class="computeroutput">auto var
+ = ...,
+ *ptr
+ = ...;</code>).
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_CHAR16_T</code>
+ 
+ </td>
+<td>
+ 
+ The compiler does not support type <code class="computeroutput">char16_t</code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_CHAR32_T</code>
+ 
+ </td>
+<td>
+ 
+ The compiler does not support type <code class="computeroutput">char32_t</code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_TEMPLATE_ALIASES</code>
+ 
+ </td>
+<td>
+ 
+ The compiler does not support template aliases.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_CONSTEXPR</code>
+ 
+ </td>
+<td>
+ 
+ The compiler does not support <code class="computeroutput">constexpr</code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_DECLTYPE</code>
+ 
+ </td>
+<td>
+ 
+ The compiler does not support <code class="computeroutput">decltype</code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_DECLTYPE_N3276</code>
+ 
+ </td>
+<td>
+ 
+ The compiler does not support the extension to <code class="computeroutput">decltype</code>
+ described in N3276,
+ accepted in Madrid, March 2011.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_DEFAULTED_FUNCTIONS</code>
+ 
+ </td>
+<td>
+ 
+ The compiler does not support defaulted (<code class="computeroutput">=
+ default</code>) functions.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_DELETED_FUNCTIONS</code>
+ 
+ </td>
+<td>
+ 
+ The compiler does not support deleted (<code class="computeroutput">=
+ delete</code>) functions.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_EXPLICIT_CONVERSION_OPERATORS</code>
+ 
+ </td>
+<td>
+ 
+ The compiler does not support explicit conversion operators (<code class="computeroutput">explicit operator
+ T()</code>).
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_EXTERN_TEMPLATE</code>
+ 
+ </td>
+<td>
+ 
+ The compiler does not support explicit instantiation forward declarations
+ for templates (<code class="computeroutput">extern template ...</code>).
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_FUNCTION_TEMPLATE_DEFAULT_ARGS</code>
+ 
+ </td>
+<td>
+ 
+ The compiler does not support default template arguments for function
+ templates.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_LAMBDAS</code>
+ 
+ </td>
+<td>
+ 
+ The compiler does not support Lambdas.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_LOCAL_CLASS_TEMPLATE_PARAMETERS</code>
+ 
+ </td>
+<td>
+ 
+ The compiler does not allow to pass local classes as template parameters
+ (this macro intentionally does not control passing of unnamed types
+ as template parameters, see also N2657).
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_LONG_LONG</code>
+ 
+ </td>
+<td>
+ 
+ The compiler does not support <code class="computeroutput">long
+ long</code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_NOEXCEPT</code>
+ 
+ </td>
+<td>
+ 
+ The compiler does not support <code class="computeroutput">noexcept</code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_NULLPTR</code>
+ 
+ </td>
+<td>
+ 
+ The compiler does not support <code class="computeroutput">nullptr</code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_RANGE_BASED_FOR</code>
+ 
+ </td>
+<td>
+ 
+ The compiler does not support range-based for statements.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_RAW_LITERALS</code>
+ 
+ </td>
+<td>
+ 
+ The compiler does not support raw string literals.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_RVALUE_REFERENCES</code>
+ 
+ </td>
+<td>
+ 
+ The compiler does not support r-value references.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_SCOPED_ENUMS</code>
+ 
+ </td>
+<td>
+ 
+ The compiler does not support scoped enumerations (<code class="computeroutput">enum class</code>).
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_STATIC_ASSERT</code>
+ 
+ </td>
+<td>
+ 
+ The compiler does not support <code class="computeroutput">static_assert</code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_STD_UNORDERD</code>
+ 
+ </td>
+<td>
+ 
+ The standard library does not support <unordered_map> and
+ <unordered_set>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_UNICODE_LITERALS</code>
+ 
+ </td>
+<td>
+ 
+ The compiler does not support Unicode (<code class="computeroutput">u8</code>,
+ <code class="computeroutput">u</code>, <code class="computeroutput">U</code>) literals.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_UNIFIED_INITIALIZATION_SYNTAX</code>
+ 
+ </td>
+<td>
+ 
+ The compiler does not support the <a href="http://en.wikipedia.org/wiki/C%2B%2B0x#Uniform_initialization" target="_top">C++11
+ Unified Initialization Syntax</a>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_VARIADIC_TEMPLATES</code>
+ 
+ </td>
+<td>
+ 
+ The compiler does not support variadic templates.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_VARIADIC_MACROS</code>
+ 
+ </td>
+<td>
+ 
+ The compiler does not support variadic macros.
+ 
+ </td>
+</tr>
+</tbody>
+</table></div>
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="boost_config.boost_macro_reference.macros_that_allow_use_of_c__11_features_with_c__03_compilers"></a><a name="config_11_for_03"></a><a class="link" href="boost_macro_reference.html#boost_config.boost_macro_reference.macros_that_allow_use_of_c__11_features_with_c__03_compilers" title="Macros that allow use of C++11 features with C++03 compilers">Macros
+ that allow use of C++11 features with C++03 compilers</a>
+</h3></div></div></div>
+
+ The following macros allow use of C++11 features even with compilers that
+ do not yet provide compliant C++11 support.
+ 
+<div class="informaltable"><table class="table">
+<colgroup>
+<col>
+<col>
+</colgroup>
+<thead><tr>
+<th>
+ 
+ Macro
+ 
+ </th>
+<th>
+ 
+ Description
+ 
+ </th>
+</tr></thead>
+<tbody>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_CONSTEXPR</code>
+ 
+ </td>
+<td>
+ 
+ Some compilers don't support the use of <code class="computeroutput">constexpr</code>.
+ This macro expands to nothing on those compilers, and <code class="computeroutput">constexpr</code> elsewhere. For example,
+ when defining a constexpr function or constructor replace:
+
+<pre xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="table-programlisting">constexpr tuple();
+</pre>
+
+ with:
+
+<pre xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="table-programlisting">BOOST_CONSTEXPR tuple();
+</pre>
+
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_CONSTEXPR_OR_CONST</code>
+ 
+ </td>
+<td>
+ 
+ Some compilers don't support the use of <code class="computeroutput">constexpr</code>.
+ This macro expands to <code class="computeroutput">const</code>
+ on those compilers, and <code class="computeroutput">constexpr</code>
+ elsewhere. For example, when defining const expr variables replace:
+
+<pre xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="table-programlisting">static constexpr UIntType xor_mask = a;
+</pre>
+
+ with:
+
+<pre xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="table-programlisting">static BOOST_CONSTEXPR_OR_CONST UIntType xor_mask = a;
+</pre>
+
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_STATIC_CONSTEXPR</code>
+ 
+ </td>
+<td>
+ 
+ This is a shortcut for <code class="computeroutput">static
+ BOOST_CONSTEXPR_OR_CONST</code>.
+ For example, when defining const expr variables replace:
+
+<pre xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="table-programlisting">static constexpr UIntType xor_mask = a;
+</pre>
+
+ with:
+
+<pre xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="table-programlisting">BOOST_STATIC_CONSTEXPR UIntType xor_mask = a;
+</pre>
+
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+
+<pre xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="table-programlisting">BOOST_NOEXCEPT
+BOOST_NOEXCEPT_IF(Predicate)
+BOOST_NOEXCEPT_EXPR(Expression)
+</pre>
+
+ 
+ </td>
+<td>
+ 
+ If <code class="computeroutput">BOOST_NO_NOEXCEPT</code>
+ is defined (i.e. C++03 compliant compilers) these macros are defined
+ as:
+ 
+ <div class="blockquote"><blockquote class="blockquote">
+
+
+<pre xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="table-programlisting">#define BOOST_NOEXCEPT
+#define BOOST_NOEXCEPT_IF(Predicate)
+#define BOOST_NOEXCEPT_EXPR(Expression) false
+</pre>
+
+ 
+</blockquote></div>
+ 
+ If <code class="computeroutput">BOOST_NO_NOEXCEPT</code>
+ is not defined (i.e. C++11 compliant compilers) they are defined
+ as:
+ 
+ <div class="blockquote"><blockquote class="blockquote">
+
+
+<pre xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="table-programlisting">#define BOOST_NOEXCEPT noexcept
+#define BOOST_NOEXCEPT_IF(Predicate) noexcept((Predicate))
+#define BOOST_NOEXCEPT_EXPR(Expression) noexcept((Expression))
+</pre>
+
+ 
+</blockquote></div>
+ </td>
+</tr>
+</tbody>
+</table></div>
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="boost_config.boost_macro_reference.boost_helper_macros"></a><a name="config_helpers"></a><a class="link" href="boost_macro_reference.html#boost_config.boost_macro_reference.boost_helper_macros" title="Boost Helper Macros">Boost
+ Helper Macros</a>
+</h3></div></div></div>
+
+ The following macros are either simple helpers, or macros that provide workarounds
+ for compiler/standard library defects.
+ 
+<div class="informaltable"><table class="table">
+<colgroup>
+<col>
+<col>
+</colgroup>
+<thead><tr>
+<th>
+ 
+ Macro
+ 
+ </th>
+<th>
+ 
+ Description
+ 
+ </th>
+</tr></thead>
+<tbody>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_WORKAROUND</code>
+ 
+ </td>
+<td>
+ 
+ This macro is used where a compiler specific workaround is required
+ that is not otherwise described by one of the other Boost.Config
+ macros. To use the macro you must first
+
+<pre xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="table-programlisting">#include <boost/detail/workaround.hpp>
+</pre>
+
+ usage is then:
+
+<pre xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="table-programlisting">#if BOOST_WORKAROUND(MACRONAME, CONDITION)
+ // workaround code goes here...
+#else
+ // Standard conforming code goes here...
+#endif
+</pre>
+
+ where <code class="computeroutput">MACRONAME</code>
+ is a macro that usually describes the version number to be tested
+ against, and <code class="computeroutput">CONDITION</code>
+ is a comparison operator followed by a value. For example <code class="computeroutput">BOOST_WORKAROUND(BOOST_INTEL,
+ <= 1010)</code> would evaluate to <code class="computeroutput">1</code> for Intel C++ 10.1 and earlier.
+ 
+ 
+ The macro can also be used with <code class="computeroutput">BOOST_TESTED_AT</code>
+ if all current compiler versions exhibit the issue, but the issue
+ is expected to be fixed at some later point.
+ 
+ 
+ For example <code class="computeroutput">BOOST_WORKAROUND(__BORLANDC__, BOOST_TESTED_AT(0x590))</code> would normally evaluate to <code class="computeroutput">1</code> for all values of <code class="computeroutput">__BORLANDC__</code> unless
+ the macro <code class="computeroutput">BOOST_DETECT_OUTDATED_WORKAROUNDS</code>
+ is defined, in which case evaluates to <code class="computeroutput">(__BORLANDC__ <=
+ 0x590)</code>.
+ 
+ 
+ Note: the ultimate source of documentation
+ for this macro is in boost/detail/workaround.hpp.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_PREVENT_MACRO_SUBSTITUTION</code>
+ 
+ </td>
+<td>
+ 
+ Sometimes you have a function name with the same name as a C macro,
+ for example "min" and "max" member functions,
+ in which case one can prevent the function being expanded as a
+ macro using:
+
+<pre xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="table-programlisting">someclass.min BOOST_PREVENT_MACRO_SUBSTITUTION(arg1, arg2);
+</pre>
+
+ The following also works in most, but not all, contexts:
+
+<pre xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="table-programlisting">(someclass.max)(arg1, arg2);
+</pre>
+
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_DEDUCED_TYPENAME</code>
+ 
+ </td>
+<td>
+ 
+ Some compilers don't support the use of typename for dependent
+ types in deduced contexts. This macro expands to nothing on those
+ compilers, and typename elsewhere. For example, replace: <code class="computeroutput">template <class T> void
+ f(T,
+ typename T::type);</code> with: <code class="computeroutput">template
+ <class
+ T>
+ void f(T, BOOST_DEDUCED_TYPENAME
+ T::type);</code>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HASH_MAP_HEADER</code>
+ 
+ </td>
+<td>
+ 
+ The header to include to get the SGI <code class="computeroutput">hash_map</code>
+ class. This macro is only available if <code class="computeroutput">BOOST_HAS_HASH</code>
+ is defined.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HASH_SET_HEADER</code>
+ 
+ </td>
+<td>
+ 
+ The header to include to get the SGI <code class="computeroutput">hash_set</code>
+ class. This macro is only available if <code class="computeroutput">BOOST_HAS_HASH</code>
+ is defined.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_SLIST_HEADER</code>
+ 
+ </td>
+<td>
+ 
+ The header to include to get the SGI <code class="computeroutput">slist</code>
+ class. This macro is only available if <code class="computeroutput">BOOST_HAS_SLIST</code>
+ is defined.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_STD_EXTENSION_NAMESPACE</code>
+ 
+ </td>
+<td>
+ 
+ The namespace used for std library extensions (hashtable classes
+ etc).
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_STATIC_CONSTANT(Type, assignment)</code>
+ 
+ </td>
+<td>
+ 
+ On compilers which don't allow in-class initialization of static
+ integral constant members, we must use enums as a workaround if
+ we want the constants to be available at compile-time. This macro
+ gives us a convenient way to declare such constants. For example
+ instead of:
+
+<pre xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="table-programlisting">struct foo{
+ static const int value = 2;
+};
+</pre>
+
+ use:
+
+<pre xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="table-programlisting">struct foo{
+ BOOST_STATIC_CONSTANT(int, value = 2);
+};
+</pre>
+
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_UNREACHABLE_RETURN(result)</code>
+ 
+ </td>
+<td>
+ 
+ Normally evaluates to nothing, but evaluates to return x; if the
+ compiler requires a return, even when it can never be reached.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_EXPLICIT_TEMPLATE_TYPE(t)</code> <code class="computeroutput">BOOST_EXPLICIT_TEMPLATE_NON_TYPE(t,v)</code> <code class="computeroutput">BOOST_APPEND_EXPLICIT_TEMPLATE_TYPE(t)</code> <code class="computeroutput">BOOST_APPEND_EXPLICIT_TEMPLATE_NON_TYPE(t,v)</code>
+ 
+ </td>
+<td>
+ 
+ Some compilers silently "fold" different function template
+ instantiations if some of the template parameters don't appear
+ in the function parameter list. For instance:
+
+<pre xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="table-programlisting">#include <iostream>
+#include <ostream>
+#include <typeinfo>
+
+template <int n>
+void f() { std::cout << n << ' '; }
+
+template <typename T>
+void g() { std::cout << typeid(T).name() << ' '; }
+
+int main() {
+ f<1>();
+ f<2>();
+
+ g<int>();
+ g<double>();
+}
+</pre>
+
+ incorrectly outputs <code class="literal">2 2 double double</code> on VC++
+ 6. These macros, to be used in the function parameter list, fix
+ the problem without effects on the calling syntax. For instance,
+ in the case above write:
+
+<pre xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="table-programlisting">template <int n>
+void f(BOOST_EXPLICIT_TEMPLATE_NON_TYPE(int, n)) { ... }
+
+template <typename T>
+void g(BOOST_EXPLICIT_TEMPLATE_TYPE(T)) { ... }
+</pre>
+
+ Beware that they can declare (for affected compilers) a dummy defaulted
+ parameter, so they
+ 
+ 
+ a) should be always invoked at the end of the parameter list
+ 
+ 
+ b) can't be used if your function
+ template is multiply declared.
+ 
+ 
+ Furthermore, in order to add any needed comma separator, an <code class="computeroutput">APPEND_*</code>
+ version must be used when the macro invocation appears after a
+ normal parameter declaration or after the invocation of another
+ macro of this same group.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_USE_FACET(Type, loc)</code>
+ 
+ </td>
+<td>
+ 
+ When the standard library does not have a conforming <code class="computeroutput">std::use_facet</code> there are various workarounds
+ available, but they differ from library to library. This macro
+ provides a consistent way to access a locale's facets. For example,
+ replace: <code class="computeroutput">std::use_facet<Type>(loc);</code>
+ with: <code class="computeroutput">BOOST_USE_FACET(Type, loc);</code> Note do not add a <code class="computeroutput">std::</code>
+ prefix to the front of <code class="computeroutput">BOOST_USE_FACET</code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_FACET(Type, loc)</code>
+ 
+ </td>
+<td>
+ 
+ When the standard library does not have a comforming <code class="computeroutput">std::has_facet</code> there are various workarounds
+ available, but they differ from library to library. This macro
+ provides a consistent way to check a locale's facets. For example,
+ replace: <code class="computeroutput">std::has_facet<Type>(loc);</code>
+ with: <code class="computeroutput">BOOST_HAS_FACET(Type, loc);</code> Note do not add a <code class="computeroutput">std::</code>
+ prefix to the front of <code class="computeroutput">BOOST_HAS_FACET</code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NESTED_TEMPLATE</code>
+ 
+ </td>
+<td>
+ 
+ Member templates are supported by some compilers even though they
+ can't use the <code class="computeroutput">A::template
+ member<U></code>
+ syntax, as a workaround replace: <code class="computeroutput">typedef
+ typename A::template
+ rebind<U>
+ binder;</code>
+ with: <code class="computeroutput">typedef typename
+ A::BOOST_NESTED_TEMPLATE rebind<U> binder;</code>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_STRINGIZE(X)</code>
+ 
+ </td>
+<td>
+ 
+ Converts the parameter <code class="computeroutput">X</code>
+ to a string after macro replacement on <code class="computeroutput">X</code>
+ has been performed.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_JOIN(X,Y)</code>
+ 
+ </td>
+<td>
+ 
+ This piece of macro magic joins the two arguments together, even
+ when one of the arguments is itself a macro (see 16.3.1 in C++
+ standard). This is normally used to create a mangled name in combination
+ with a predefined macro such a __LINE__.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_FORCEINLINE</code>
+ 
+ </td>
+<td>
+ 
+ This macro can be used in place of the <code class="computeroutput">inline</code>
+ keyword to instruct the compiler that a function should always
+ be inlined. Overuse of this macro can lead to significant bloat,
+ while good use can increase performance in certain cases, such
+ as computation-intensive code built through generative programming
+ techniques.
+ 
+ 
+ Usage example:
+
+<pre xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="table-programlisting">template<class T>
+BOOST_FORCEINLINE T& f(T& t)
+{
+ return t;
+}
+</pre>
+
+ 
+ 
+ Note that use of this macro can lead to cryptic error messages
+ with some compilers. Consider defining it to <code class="computeroutput">inline</code>
+ before including the Boost.Config header in order to be able to
+ debug errors more easily.
+ 
+ </td>
+</tr>
+</tbody>
+</table></div>
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="boost_config.boost_macro_reference.boost_informational_macros"></a><a name="config_info_macros"></a><a class="link" href="boost_macro_reference.html#boost_config.boost_macro_reference.boost_informational_macros" title="Boost Informational Macros">Boost
+ Informational Macros</a>
+</h3></div></div></div>
+
+ The following macros describe boost features; these are, generally speaking
+ the only boost macros that should be tested in user code.
+ 
+<div class="informaltable"><table class="table">
+<colgroup>
+<col>
+<col>
+<col>
+</colgroup>
+<thead><tr>
+<th>
+ 
+ Macro
+ 
+ </th>
+<th>
+ 
+ Header
+ 
+ </th>
+<th>
+ 
+ Description
+ 
+ </th>
+</tr></thead>
+<tbody>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_VERSION</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput"><boost/version.hpp></code>
+ 
+ </td>
+<td>
+ 
+ Describes the boost version number in XYYYZZ format such that:
+ <code class="computeroutput">(BOOST_VERSION
+ % 100)</code> is the sub-minor version, <code class="computeroutput">((BOOST_VERSION
+ / 100) % 1000)</code>
+ is the minor version, and <code class="computeroutput">(BOOST_VERSION /
+ 100000)</code>
+ is the major version.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_INT64_T</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput"><boost/cstdint.hpp></code> <code class="computeroutput"><boost/stdint.h></code>
+ 
+ </td>
+<td>
+ 
+ Defined if there are no 64-bit integral types: <code class="computeroutput">int64_t</code>,
+ <code class="computeroutput">uint64_t</code> etc.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_INTEGRAL_INT64_T</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput"><boost/cstdint.hpp></code> <code class="computeroutput"><boost/stdint.h></code>
+ 
+ </td>
+<td>
+ 
+ Defined if <code class="computeroutput">int64_t</code>
+ as defined by <code class="computeroutput"><boost/cstdint.hpp></code>
+ is not usable in integral constant expressions.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_MSVC</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput"><boost/config.hpp></code>
+ 
+ </td>
+<td>
+ 
+ Defined if the compiler is really Microsoft Visual C++, as opposed
+ to one of the many other compilers that also define <code class="computeroutput">_MSC_VER</code>. Has the same value
+ as _MSC_VER.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_MSVC_FULL_VER</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput"><boost/config.hpp></code>
+ 
+ </td>
+<td>
+ 
+ Defined to a normalised 9 digit version of _MSC_FULL_VER (which
+ sometimes only has 8 digits), the macro has the form VVMMPPPPP
+ where VV is the major version number, MM is the minor version number,
+ and PPPPP is the compiler build number.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_INTEL</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput"><boost/config.hpp></code>
+ 
+ </td>
+<td>
+ 
+ Defined if the compiler is an Intel compiler, takes the same value
+ as the compiler version macro.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_CLANG</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput"><boost/config.hpp></code>
+ 
+ </td>
+<td>
+ 
+ Defined to 1 if the compiler is the Clang compiler.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_WINDOWS</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput"><boost/config.hpp></code>
+ 
+ </td>
+<td>
+ 
+ Defined if the Windows platform API is available.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_DINKUMWARE_STDLIB</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput"><boost/config.hpp></code>
+ 
+ </td>
+<td>
+ 
+ Defined if the dinkumware standard library is in use, takes the
+ same value as the Dinkumware library version macro <code class="computeroutput">_CPPLIB_VER</code> if defined, otherwise
+ 1.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_WREGEX</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput"><boost/regex.hpp></code>
+ 
+ </td>
+<td>
+ 
+ Defined if the regex library does not support wide character regular
+ expressions.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_COMPILER</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput"><boost/config.hpp></code>
+ 
+ </td>
+<td>
+ 
+ Defined as a string describing the name and version number of the
+ compiler in use. Mainly for debugging the configuration.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_STDLIB</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput"><boost/config.hpp></code>
+ 
+ </td>
+<td>
+ 
+ Defined as a string describing the name and version number of the
+ standard library in use. Mainly for debugging the configuration.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_PLATFORM</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput"><boost/config.hpp></code>
+ 
+ </td>
+<td>
+ 
+ Defined as a string describing the name of the platform. Mainly
+ for debugging the configuration.
+ 
+ </td>
+</tr>
+</tbody>
+</table></div>
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="boost_config.boost_macro_reference.boost_deprecated_macros"></a><a name="deprecated_macros"></a><a class="link" href="boost_macro_reference.html#boost_config.boost_macro_reference.boost_deprecated_macros" title="Boost Deprecated Macros">Boost
+ Deprecated Macros</a>
+</h3></div></div></div>
+
+ The following have been deprecated; please use the replacements instead.
+ They will be removed in a future version of boost.
+ 
+<div class="informaltable"><table class="table">
+<colgroup>
+<col>
+<col>
+<col>
+<col>
+</colgroup>
+<thead><tr>
+<th>
+ 
+ Deprecated Macro
+ 
+ </th>
+<th>
+ 
+ Replacement
+ 
+ </th>
+<th>
+ 
+ When deprecated
+ 
+ </th>
+<th>
+ 
+ When removed
+ 
+ </th>
+</tr></thead>
+<tbody>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_0X_HDR_ARRAY</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_ARRAY</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.50
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_0X_HDR_CHRONO</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_CHRONO</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.50
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_0X_HDR_CODECVT</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_CODECVT</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.50
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_0X_HDR_CONDITION_VARIABLE</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_CONDITION_VARIABLE</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.50
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_0X_HDR_FORWARD_LIST</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_FORWARD_LIST</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.50
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_0X_HDR_FUTURE</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_FUTURE</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.50
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_0X_HDR_INITIALIZER_LIST</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_INITIALIZER_LIST</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.50
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_INITIALIZER_LISTS</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_INITIALIZER_LIST</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.50
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_0X_HDR_MUTEX</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_MUTEX</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.50
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_0X_HDR_RANDOM</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_RANDOM</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.50
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_0X_HDR_RATIO</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_RATIO</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.50
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_0X_HDR_REGEX</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_REGEX</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.50
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_0X_HDR_SYSTEM_ERROR</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_SYSTEM_ERROR</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.50
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_0X_HDR_THREAD</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_THREAD</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.50
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_0X_HDR_TUPLE</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_TUPLE</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.50
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_0X_HDR_TYPE_TRAITS</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_TYPE_TRAITS</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.50
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_0X_HDR_TYPEINDEX</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_TYPEINDEX</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.50
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_0X_HDR_UNORDERED_SET</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_UNORDERED_SET</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.50
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_0X_HDR_UNORDERED_MAP</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_UNORDERED_MAP</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.50
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_STD_UNORDERED</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_HDR_UNORDERED_SET</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.50
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ </td>
+<td>
+ </td>
+<td>
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_AUTO_DECLARATIONS</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_AUTO_DECLARATIONS</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.51
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_AUTO_MULTIDECLARATIONS</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_AUTO_MULTIDECLARATIONS</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.51
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CHAR16_T</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_CHAR16_T</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.51
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CHAR32_T</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_CHAR32_T</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.51
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_TEMPLATE_ALIASES</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_TEMPLATE_ALIASES</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.51
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CONSTEXPR</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_CONSTEXPR</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.51
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_DECLTYPE</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_DECLTYPE</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.51
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_DECLTYPE_N3276</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_DECLTYPE_N3276</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.51
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_DEFAULTED_FUNCTIONS</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_DEFAULTED_FUNCTIONS</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.51
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_DELETED_FUNCTIONS</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_DELETED_FUNCTIONS</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.51
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_EXPLICIT_CONVERSION_OPERATORS</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_EXPLICIT_CONVERSION_OPERATORS</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.51
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_EXTERN_TEMPLATE</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_EXTERN_TEMPLATE</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.51
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_FUNCTION_TEMPLATE_DEFAULT_ARGS</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_FUNCTION_TEMPLATE_DEFAULT_ARGS</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.51
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_LAMBDAS</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_LAMBDAS</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.51
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_LOCAL_CLASS_TEMPLATE_PARAMETERS</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_LOCAL_CLASS_TEMPLATE_PARAMETERS</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.51
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_NOEXCEPT</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_NOEXCEPT</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.51
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_NULLPTR</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_NULLPTR</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.51
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_RAW_LITERALS</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_RAW_LITERALS</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.51
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_RVALUE_REFERENCES</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_RVALUE_REFERENCES</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.51
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_SCOPED_ENUMS</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_SCOPED_ENUMS</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.51
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_STATIC_ASSERT</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_STATIC_ASSERT</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.51
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_STD_UNORDERD</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_STD_UNORDERD</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.51
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_UNICODE_LITERALS</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_UNICODE_LITERALS</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.51
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_UNIFIED_INITIALIZATION_SYNTAX</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_UNIFIED_INITIALIZATION_SYNTAX</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.51
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_VARIADIC_TEMPLATES</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_VARIADIC_TEMPLATES</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.51
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_VARIADIC_MACROS</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_VARIADIC_MACROS</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.51
+ 
+ </td>
+<td>
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_NUMERIC_LIMITS_LOWEST</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CXX11_NUMERIC_LIMITS</code>
+ 
+ </td>
+<td>
+ 
+ Boost 1.51
+ 
+ </td>
+<td>
+ </td>
+</tr>
+</tbody>
+</table></div>
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="boost_config.boost_macro_reference.macros_for_libraries_with_separate_source_code"></a><a class="link" href="boost_macro_reference.html#boost_config.boost_macro_reference.macros_for_libraries_with_separate_source_code" title="Macros for libraries with separate source code">Macros
+ for libraries with separate source code</a>
+</h3></div></div></div>
+<div class="toc"><dl>
+<dt><a href="boost_macro_reference.html#boost_config.boost_macro_reference.macros_for_libraries_with_separate_source_code.macros_controlling_shared_library_symbol_visibility">Macros
+ controlling shared library symbol visibility</a></dt>
+<dt><a href="boost_macro_reference.html#boost_config.boost_macro_reference.macros_for_libraries_with_separate_source_code.abi_fixing">ABI
+ Fixing</a></dt>
+<dt><a href="boost_macro_reference.html#boost_config.boost_macro_reference.macros_for_libraries_with_separate_source_code.automatic_library_selection">Automatic
+ library selection</a></dt>
+</dl></div>
+
+ The following macros and helper headers are of use to authors whose libraries
+ include separate source code, and are intended to address several issues:
+ 
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem">
+ Controlling shared library symbol visibility
+ </li>
+<li class="listitem">
+ Fixing the ABI of the compiled library
+ </li>
+<li class="listitem">
+ Selecting which compiled library to link against based upon the compilers
+ settings
+ </li>
+</ul></div>
+
+ See <a href="http://svn.boost.org/trac/boost/wiki/Guidelines/Separate" target="_top">Guidelines
+ for Authors of Boost Libraries Containing Separate Source</a>
+ 
+<div class="section">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="boost_config.boost_macro_reference.macros_for_libraries_with_separate_source_code.macros_controlling_shared_library_symbol_visibility"></a><a class="link" href="boost_macro_reference.html#boost_config.boost_macro_reference.macros_for_libraries_with_separate_source_code.macros_controlling_shared_library_symbol_visibility" title="Macros controlling shared library symbol visibility">Macros
+ controlling shared library symbol visibility</a>
+</h4></div></div></div>
+
+ Some compilers support C++ extensions that control which symbols will be
+ exported from shared libraries such as dynamic shared objects (DSO's) on
+ Unix-like systems or dynamic-link libraries (DLL's) on Windows.
+ 
+
+ The Microsoft VC++ compiler has long supplied <code class="computeroutput">__declspec(dllexport)</code> and <code class="computeroutput">__declspec(dllimport)</code> extensions for this purpose, as do virtually
+ all other compilers targeting the Windows platform.
+ 
+
+ Modern versions of the GNU GCC compiler provide the <code class="computeroutput">__attribute__((visibility("default")))</code> extension to indicate that a symbol
+ should be exported. All other symbols may be hidden by using the <code class="computeroutput">-fvisibility-hidden</code>
+ or <code class="computeroutput">-fvisibility-ms-compat</code> compiler switches.
+ 
+
+ Boost supplies several macros to make it easier to manage symbol visibility
+ in a way that is portable between compilers and operating systems.
+ 
+<div class="informaltable"><table class="table">
+<colgroup>
+<col>
+<col>
+</colgroup>
+<thead><tr>
+<th>
+ 
+ Macro
+ 
+ </th>
+<th>
+ 
+ Description
+ 
+ </th>
+</tr></thead>
+<tbody>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_SYMBOL_EXPORT</code>
+ 
+ </td>
+<td>
+ 
+ Defines the syntax of a C++ language extension that indicates
+ a symbol is to be exported from a shared library. If the compiler
+ has no such extension, the macro is defined with no replacement
+ text.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_SYMBOL_IMPORT</code>
+ 
+ </td>
+<td>
+ 
+ Defines the syntax of a C++ language extension that indicates
+ a symbol is to be imported from a shared library. If the compiler
+ has no such extension, the macro is defined with no replacement
+ text.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_SYMBOL_VISIBLE</code>
+ 
+ </td>
+<td>
+ 
+ Defines the syntax of a C++ language extension that indicates
+ a symbol is to be globally visible. If the compiler has no such
+ extension, the macro is defined with no replacement text. Needed
+ for classes that are not otherwise exported, but are used by
+ RTTI. Examples include class for objects that will be thrown
+ as exceptions or used in dynamic_casts, across shared library
+ boundaries. For example, a header-only exception class might
+ look like this:
+
+<pre xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="table-programlisting">class BOOST_SYMBOL_VISIBLE my_exception : public std::runtime_error { ... };
+</pre>
+
+ Without BOOST_SYMBOL_VISIBLE, it would be impossible to catch
+ my_exception thrown from a shared library compiled by GCC with
+ the -fvisibility=hidden option.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_HAS_DECLSPEC</code>
+ 
+ </td>
+<td>
+ 
+ The compiler has C++ extensions <code class="computeroutput">__declspec(dllexport)</code> and <code class="computeroutput">__declspec(dllimport)</code> to control export/import of
+ symbols from shared libraries. Deprecated. This macro
+ is no longer necessary since BOOST_SYMBOL_EXPORT and BOOST_SYMBOL_IMPORT
+ are now supplied. It is provided to support legacy code.
+ 
+ </td>
+</tr>
+</tbody>
+</table></div>
+
+ Typical usage:
+ 
+
+ boost/foo/config.hpp
+ 
+<pre class="programlisting">...
+#if defined(BOOST_ALL_DYN_LINK) || defined(BOOST_FOO_DYN_LINK)
+# if defined(BOOST_FOO_SOURCE)
+# define BOOST_FOO_DECL BOOST_SYMBOL_EXPORT
+# else
+# define BOOST_FOO_DECL BOOST_SYMBOL_IMPORT
+# endif
+#else
+# define BOOST_FOO_DECL
+#endif
+...
+</pre>
+
+ boost/foo/foo.hpp
+ 
+<pre class="programlisting">#include <boost/foo/config.hpp>
+...
+class BOOST_FOO_DECL bar { ... };
+...
+void BOOST_FOO_DECL f();
+...
+</pre>
+
+ boost/libs/foo/src/foo.cpp
+ 
+<pre class="programlisting">#define BOOST_FOO_SOURCE
+#include <boost/foo/foo.hpp>
+...
+void BOOST_FOO_DECL f()
+{
+ ...
+}
+...
+</pre>
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="boost_config.boost_macro_reference.macros_for_libraries_with_separate_source_code.abi_fixing"></a><a class="link" href="boost_macro_reference.html#boost_config.boost_macro_reference.macros_for_libraries_with_separate_source_code.abi_fixing" title="ABI Fixing">ABI
+ Fixing</a>
+</h4></div></div></div>
+
+ When linking against a pre-compiled library it vital that the ABI used
+ by the compiler when building the library matches exactly
+ the ABI used by the code using the library. In this case ABI means things
+ like the struct packing arrangement used, the name mangling scheme used,
+ or the size of some types (enum types for example). This is separate from
+ things like threading support, or runtime library variations, which have
+ to be dealt with by build variants. To put this in perspective there is
+ one compiler (Borland's) that has so many compiler options that make subtle
+ changes to the ABI, that at least in theory there 3200 combinations, and
+ that's without considering runtime library variations. Fortunately these
+ variations can be managed by <code class="computeroutput">#pragma</code>'s
+ that tell the compiler what ABI to use for the types declared in your library.
+ In order to avoid sprinkling <code class="computeroutput">#pragma</code>'s
+ all over the boost headers, there are some prefix and suffix headers that
+ do the job. Typical usage is:
+ 
+
+ my_library.hpp
+ 
+<pre class="programlisting">#ifndef MY_INCLUDE_GUARD
+#define MY_INCLUDE_GUARD
+
+// all includes go here:
+<code class="literal">#include <boost/config.hpp></code>
+#include <whatever>
+
+<code class="literal">#include <boost/config/abi_prefix.hpp></code> // must be the last #include
+
+namespace boost {
+
+// your code goes here
+
+}
+
+<code class="literal">#include <boost/config/abi_suffix.hpp></code> // pops abi_prefix.hpp pragmas
+
+#endif // include guard
+</pre>
+
+ my_library.cpp
+ 
+<pre class="programlisting">...
+// nothing special need be done in the implementation file
+...
+</pre>
+
+ The user can disable this mechanism by defining <code class="computeroutput">BOOST_DISABLE_ABI_HEADERS</code>,
+ or they can define <code class="computeroutput">BOOST_ABI_PREFIX</code>
+ and/or <code class="computeroutput">BOOST_ABI_SUFFIX</code>
+ to point to their own prefix/suffix headers if they so wish.
+ 
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="boost_config.boost_macro_reference.macros_for_libraries_with_separate_source_code.automatic_library_selection"></a><a class="link" href="boost_macro_reference.html#boost_config.boost_macro_reference.macros_for_libraries_with_separate_source_code.automatic_library_selection" title="Automatic library selection">Automatic
+ library selection</a>
+</h4></div></div></div>
+
+ It is essential that users link to a build of a library which was built
+ against the same runtime library that their application will be built against
+ -if this does not happen then the library will not be binary compatible
+ with their own code- and there is a high likelihood that their application
+ will experience runtime crashes. These kinds of problems can be extremely
+ time consuming and difficult to debug, and often lead to frustrated users
+ and authors alike (simply selecting the right library to link against is
+ not as easy as it seems when their are 6-8 of them to chose from, and some
+ users seem to be blissfully unaware that there even are different runtimes
+ available to them).
+ 
+
+ To solve this issue, some compilers allow source code to contain <code class="computeroutput">#pragma</code>'s that instruct the linker
+ which library to link against, all the user need do is include the headers
+ they need, place the compiled libraries in their library search path, and
+ the compiler and linker do the rest. Boost.config supports this via the
+ header <code class="computeroutput"><boost/config/auto_link.hpp></code>, before including this header one or
+ more of the following macros need to be defined:
+ 
+<div class="variablelist">
+
+<dl>
+<dt><code class="computeroutput">BOOST_LIB_NAME</code></dt>
+<dd>
+ Required: An identifier containing the basename of the library, for
+ example 'boost_regex'.
+ </dd>
+<dt><code class="computeroutput">BOOST_DYN_LINK</code></dt>
+<dd>
+ Optional: when set link to dll rather than static library.
+ </dd>
+<dt><code class="computeroutput">BOOST_LIB_DIAGNOSTIC</code></dt>
+<dd>
+ Optional: when set the header will print out the name of the library
+ selected (useful for debugging).
+ </dd>
+</dl>
+</div>
+
+ If the compiler supports this mechanism, then it will be told to link against
+ the appropriately named library, the actual algorithm used to mangle the
+ name of the library is documented inside <code class="computeroutput"><boost/config/auto_link.hpp></code>
+ and has to match that used to create the libraries via bjam 's install
+ rules.
+ 
+
+ my_library.hpp
+ 
+<pre class="programlisting">...
+//
+// Don't include auto-linking code if the user has disabled it by
+// defining BOOST_ALL_NO_LIB, or BOOST_MY_LIBRARY_NO_LIB, or if this 
+// is one of our own source files (signified by BOOST_MY_LIBRARY_SOURCE):
+//
+#if !defined(BOOST_ALL_NO_LIB) && !defined(BOOST_MY_LIBRARY_NO_LIB) && !defined(BOOST_MY_LIBRARY_SOURCE)
+# define BOOST_LIB_NAME boost_my_library
+# ifdef BOOST_MY_LIBRARY_DYN_LINK
+# define BOOST_DYN_LINK
+# endif
+# include <boost/config/auto_link.hpp>
+#endif
+...
+</pre>
+
+ my_library.cpp
+ 
+<pre class="programlisting">// define BOOST_MY_LIBRARY_SOURCE so that the header knows that the
+// library is being built (possibly exporting rather than importing code)
+//
+#define BOOST_MY_LIBRARY_SOURCE
+
+#include <boost/my_library/my_library.hpp>
+...
+</pre>
+</div>
+</div>
+</div>
+<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
+<td align="left"></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Beman Dawes, Vesa Karvonen, John
+ Maddock
+ 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)
+ 
+</div></td>
+</tr></table>
+<hr>
+<div class="spirit-nav">
+<a accesskey="p" href="../index.html"><img src="../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.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="guidelines_for_boost_authors.html"><img src="../../../../../doc/src/images/next.png" alt="Next"></a>
+</div>
+</body>
+</html>

Added: website/public_html/live/doc/fixes/boost_1_52_0/libs/config/doc/html/boost_config/guidelines_for_boost_authors.html
==============================================================================
--- (empty file)
+++ website/public_html/live/doc/fixes/boost_1_52_0/libs/config/doc/html/boost_config/guidelines_for_boost_authors.html 2012-11-20 15:40:09 EST (Tue, 20 Nov 2012)
@@ -0,0 +1,377 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
+<title>Guidelines for Boost Authors</title>
+<link rel="stylesheet" href="../../../../../doc/src/boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="../index.html" title="Boost.Config">
+<link rel="up" href="../index.html" title="Boost.Config">
+<link rel="prev" href="boost_macro_reference.html" title="Boost Macro Reference">
+<link rel="next" href="rationale.html" title="Rationale">
+</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">Home</td>
+<td align="center">Libraries</td>
+<td align="center">People</td>
+<td align="center">FAQ</td>
+<td align="center">More</td>
+</tr></table>
+<hr>
+<div class="spirit-nav">
+<a accesskey="p" href="boost_macro_reference.html"><img src="../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.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="rationale.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="boost_config.guidelines_for_boost_authors"></a><a class="link" href="guidelines_for_boost_authors.html" title="Guidelines for Boost Authors">Guidelines for
+ Boost Authors</a>
+</h2></div></div></div>
+<div class="toc"><dl>
+<dt><a href="guidelines_for_boost_authors.html#boost_config.guidelines_for_boost_authors.warnings">Disabling
+ Compiler Warnings</a></dt>
+<dt><a href="guidelines_for_boost_authors.html#boost_config.guidelines_for_boost_authors.adding_new_defect_macros">Adding
+ New Defect Macros</a></dt>
+<dt><a href="guidelines_for_boost_authors.html#boost_config.guidelines_for_boost_authors.adding_new_feature_test_macros">Adding
+ New Feature Test Macros</a></dt>
+<dt><a href="guidelines_for_boost_authors.html#boost_config.guidelines_for_boost_authors.modifying_the_boost_configuration_headers">Modifying
+ the Boost Configuration Headers</a></dt>
+</dl></div>
+
+ The <boost/config.hpp>
+ header is used to pass configuration information to other boost files, allowing
+ them to cope with platform dependencies such as arithmetic byte ordering, compiler
+ pragmas, or compiler shortcomings. Without such configuration information,
+ many current compilers would not work with the Boost libraries.
+ 
+
+ Centralizing configuration information in this header reduces the number of
+ files that must be modified when porting libraries to new platforms, or when
+ compilers are updated. Ideally, no other files would have to be modified when
+ porting to a new platform.
+ 
+
+ Configuration headers are controversial because some view them as condoning
+ broken compilers and encouraging non-standard subsets. Adding settings for
+ additional platforms and maintaining existing settings can also be a problem.
+ In other words, configuration headers are a necessary evil rather than a desirable
+ feature. The boost config.hpp policy is designed to minimize the problems and
+ maximize the benefits of a configuration header.
+ 
+
+ Note that:
+ 
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem">
+ Boost library implementers are not required to "<code class="computeroutput">#include
+ <boost/config.hpp></code>", and are not required in any
+ way to support compilers that do not comply with the C++ Standard (ISO/IEC
+ 14882).
+ </li>
+<li class="listitem">
+ If a library implementer wishes to support some non-conforming compiler,
+ or to support some platform specific feature, "<code class="computeroutput">#include
+ <boost/config.hpp></code>" is the preferred way to obtain
+ configuration information not available from the standard headers such
+ as <code class="computeroutput"><climits></code>, etc.
+ </li>
+<li class="listitem">
+ If configuration information can be deduced from standard headers such
+ as <code class="computeroutput"><climits></code>, use those standard headers rather
+ than <code class="computeroutput"><boost/config.hpp></code>.
+ </li>
+<li class="listitem">
+ Boost files that use macros defined in <code class="computeroutput"><boost/config.hpp></code>
+ should have sensible, standard conforming, default behavior if the macro
+ is not defined. This means that the starting point for porting <code class="computeroutput"><boost/config.hpp></code> to a new platform is simply to define
+ nothing at all specific to that platform. In the rare case where there
+ is no sensible default behavior, an #error message should describe the
+ problem.
+ </li>
+<li class="listitem">
+ If a Boost library implementer wants something added to <code class="computeroutput">config.hpp</code>,
+ post a request on the Boost mailing list. There is no guarantee such a
+ request will be honored; the intent is to limit the complexity of config.hpp.
+ </li>
+<li class="listitem">
+ The intent is to support only compilers which appear on their way to becoming
+ C++ Standard compliant, and only recent releases of those compilers at
+ that.
+ </li>
+<li class="listitem">
+ The intent is not to disable mainstream features now well-supported by
+ the majority of compilers, such as namespaces, exceptions, RTTI, or templates.
+ </li>
+</ul></div>
+<div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="boost_config.guidelines_for_boost_authors.warnings"></a><a class="link" href="guidelines_for_boost_authors.html#boost_config.guidelines_for_boost_authors.warnings" title="Disabling Compiler Warnings">Disabling
+ Compiler Warnings</a>
+</h3></div></div></div>
+
+ The header <code class="computeroutput"><boost/config/warning_disable.hpp></code>
+ can be used to disable certain compiler warnings that are hard or impossible
+ to otherwise remove.
+ 
+
+ Note that:
+ 
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem">
+ This header should never be included
+ by another Boost header, it should only ever be
+ used by a library source file or a test case.
+ </li>
+<li class="listitem">
+ The header should be included before
+ you include any other header.
+ </li>
+<li class="listitem">
+ This header only disables warnings that are hard or impossible to otherwise
+ deal with, and which are typically emitted by one compiler only, or in
+ one compilers own standard library headers.
+ </li>
+</ul></div>
+
+ Currently it disables the following warnings:
+ 
+<div class="informaltable"><table class="table">
+<colgroup>
+<col>
+<col>
+</colgroup>
+<thead><tr>
+<th>
+ 
+ Compiler
+ 
+ </th>
+<th>
+ 
+ Warning
+ 
+ </th>
+</tr></thead>
+<tbody>
+<tr>
+<td>
+ 
+ Visual C++ 8 and later
+ 
+ </td>
+<td>
+ 
+ C4996:
+ Error 'function': was declared deprecated
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ Intel C++
+ 
+ </td>
+<td>
+ 
+ Warning 1786: relates to the use of "deprecated" standard
+ library functions rather like C4996 in Visual C++.
+ 
+ </td>
+</tr>
+</tbody>
+</table></div>
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="boost_config.guidelines_for_boost_authors.adding_new_defect_macros"></a><a class="link" href="guidelines_for_boost_authors.html#boost_config.guidelines_for_boost_authors.adding_new_defect_macros" title="Adding New Defect Macros">Adding
+ New Defect Macros</a>
+</h3></div></div></div>
+
+ When you need to add a new defect macro - either to fix a problem with an
+ existing library, or when adding a new library - distil the issue down to
+ a simple test case; often, at this point other (possibly better) workarounds
+ may become apparent. Secondly always post the test case code to the boost
+ mailing list and invite comments; remember that C++ is complex and that sometimes
+ what may appear a defect, may in fact turn out to be a problem with the authors
+ understanding of the standard.
+ 
+
+ When you name the macro, follow the <code class="computeroutput">BOOST_NO_</code>SOMETHING
+ naming convention, so that it's obvious that this is a macro reporting a
+ defect.
+ 
+
+ Finally, add the test program to the regression tests. You will need to place
+ the test case in a <code class="computeroutput">.ipp</code>
+ file with the following comments near the top:
+ 
+<pre class="programlisting">// MACRO: BOOST_NO_FOO
+// TITLE: foo
+// DESCRIPTION: If the compiler fails to support foo
+</pre>
+
+ These comments are processed by the autoconf script, so make sure the format
+ follows the one given. The file should be named "<code class="computeroutput">boost_no_foo.ipp</code>",
+ where foo is the defect description - try and keep the file name under the
+ Mac 30 character filename limit though. You will also need to provide a function
+ prototype "<code class="computeroutput">int test()</code>" that is declared in a namespace with
+ the same name as the macro, but in all lower case, and which returns zero
+ on success:
+ 
+<pre class="programlisting">namespace boost_no_foo {
+int test()
+{
+ // test code goes here:
+ //
+ return 0;
+}
+
+}
+</pre>
+
+ Once the test code is in place in libs/config/test, updating the configuration
+ test system proceeds as:
+ 
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem">
+ cd into <code class="computeroutput">libs/config/tools</code> and run <code class="computeroutput">bjam</code>.
+ This generates the <code class="computeroutput">.cpp</code>
+ file test cases from the <code class="computeroutput">.ipp</code> file, updates the libs/config/test/all/Jamfile.v2,
+ <code class="computeroutput">config_test.cpp</code> and <code class="computeroutput">config_info.cpp</code>. 
+ 
+ </li>
+<li class="listitem">
+ cd into <code class="computeroutput">libs/config/test/all</code> and run <code class="computeroutput">bjam
+ </code>MACRONAME<code class="computeroutput"> compiler-list</code>,
+ where MACRONAME is the name of the new macro, and
+ <code class="computeroutput">compiler-list</code> is a space separated
+ list of compilers to test with. The xxx_pass_test and the
+ xxx_fail_test should both report <code class="computeroutput">**passed**</code>. If MACRONAME
+ is not defined when it should be defined, xxx_pass_test will not report
+ <code class="computeroutput">**passed**</code>. If MACRONAME
+ is defined when it should not be defined, xxx_fail_test will not report
+ <code class="computeroutput">**passed**</code>. 
+ </li>
+<li class="listitem">
+ cd into <code class="computeroutput">libs/config/test</code> and run <code class="computeroutput">bjam
+ config_info config_test
+ </code><code class="computeroutput">compiler-list</code>.
+ <code class="computeroutput">config_info</code> should build
+ and run cleanly for all the compilers in <code class="computeroutput">compiler-list</code>
+ while <code class="computeroutput">config_test</code> should
+ fail for those that have the defect, and pass for those that do not.
+ </li>
+</ul></div>
+
+ Then you should:
+ 
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem">
+ Define the defect macro in those config headers that require it.
+ </li>
+<li class="listitem">
+ Document the macro in this documentation (please do not forget this step!!)
+ </li>
+<li class="listitem">
+ Commit everything.
+ </li>
+<li class="listitem">
+ Keep an eye on the regression tests for new failures in Boost.Config
+ caused by the addition.
+ </li>
+<li class="listitem">
+ Start using the macro.
+ </li>
+</ul></div>
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="boost_config.guidelines_for_boost_authors.adding_new_feature_test_macros"></a><a class="link" href="guidelines_for_boost_authors.html#boost_config.guidelines_for_boost_authors.adding_new_feature_test_macros" title="Adding New Feature Test Macros">Adding
+ New Feature Test Macros</a>
+</h3></div></div></div>
+
+ When you need to add a macro that describes a feature that the standard does
+ not require, follow the convention for adding a new defect macro (above),
+ but call the macro <code class="computeroutput">BOOST_HAS_FOO</code>,
+ and name the test file "<code class="computeroutput">boost_has_foo.ipp</code>".
+ Try not to add feature test macros unnecessarily, if there is a platform
+ specific macro that can already be used (for example <code class="computeroutput">_WIN32</code>,
+ <code class="computeroutput">__BEOS__</code>, or <code class="computeroutput">__linux</code>) to identify the feature then use
+ that. Try to keep the macro to a feature group, or header name, rather than
+ one specific API (for example <code class="computeroutput">BOOST_HAS_NL_TYPES_H</code>
+ rather than <code class="computeroutput">BOOST_HAS_CATOPEN</code>).
+ If the macro describes a POSIX feature group, then add boilerplate code to
+ <boost/config/suffix.hpp>
+ to auto-detect the feature where possible (if you are wondering why we can't
+ use POSIX feature test macro directly, remember that many of these features
+ can be added by third party libraries, and are not therefore identified inside
+ <code class="computeroutput"><unistd.h></code>).
+ 
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="boost_config.guidelines_for_boost_authors.modifying_the_boost_configuration_headers"></a><a class="link" href="guidelines_for_boost_authors.html#boost_config.guidelines_for_boost_authors.modifying_the_boost_configuration_headers" title="Modifying the Boost Configuration Headers">Modifying
+ the Boost Configuration Headers</a>
+</h3></div></div></div>
+
+ The aim of boost's configuration setup is that the configuration headers
+ should be relatively stable - a boost user should not have to recompile their
+ code just because the configuration for some compiler that they're not interested
+ in has changed. Separating the configuration into separate compiler/standard
+ library/platform sections provides for part of this stability, but boost
+ authors require some amount of restraint as well, in particular:
+ 
+
+ <boost/config.hpp>
+ should never change, don't alter this file.
+ 
+
+ <boost/config/user.hpp>
+ is included by default, don't add extra code to this file unless you have
+ to. If you do, please remember to update libs/config/tools/configure.in
+ as well.
+ 
+
+ <boost/config/suffix.hpp>
+ is always included so be careful about modifying this file as it breaks dependencies
+ for everyone. This file should include only "boilerplate" configuration
+ code, and generally should change only when new macros are added.
+ 
+
+ <boost/config/select_compiler_config.hpp>,
+ <boost/config/select_platform_config.hpp>
+ and <boost/config/select_stdlib_config.hpp>
+ are included by default and should change only if support for a new compiler/standard
+ library/platform is added.
+ 
+
+ The compiler/platform/standard library selection code is set up so that unknown
+ platforms are ignored and assumed to be fully standards compliant - this
+ gives unknown platforms a "sporting chance" of working "as
+ is" even without running the configure script.
+ 
+
+ When adding or modifying the individual mini-configs, assume that future,
+ as yet unreleased versions of compilers, have all the defects of the current
+ version. Although this is perhaps unnecessarily pessimistic, it cuts down
+ on the maintenance of these files, and experience suggests that pessimism
+ is better placed than optimism here!
+ 
+</div>
+</div>
+<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
+<td align="left"></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Beman Dawes, Vesa Karvonen, John
+ Maddock
+ 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)
+ 
+</div></td>
+</tr></table>
+<hr>
+<div class="spirit-nav">
+<a accesskey="p" href="boost_macro_reference.html"><img src="../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.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="rationale.html"><img src="../../../../../doc/src/images/next.png" alt="Next"></a>
+</div>
+</body>
+</html>

Added: website/public_html/live/doc/fixes/boost_1_52_0/libs/config/doc/html/boost_config/rationale.html
==============================================================================
--- (empty file)
+++ website/public_html/live/doc/fixes/boost_1_52_0/libs/config/doc/html/boost_config/rationale.html 2012-11-20 15:40:09 EST (Tue, 20 Nov 2012)
@@ -0,0 +1,124 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
+<title>Rationale</title>
+<link rel="stylesheet" href="../../../../../doc/src/boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="../index.html" title="Boost.Config">
+<link rel="up" href="../index.html" title="Boost.Config">
+<link rel="prev" href="guidelines_for_boost_authors.html" title="Guidelines for Boost Authors">
+<link rel="next" href="acknowledgements.html" title="Acknowledgements">
+</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">Home</td>
+<td align="center">Libraries</td>
+<td align="center">People</td>
+<td align="center">FAQ</td>
+<td align="center">More</td>
+</tr></table>
+<hr>
+<div class="spirit-nav">
+<a accesskey="p" href="guidelines_for_boost_authors.html"><img src="../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.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="acknowledgements.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="boost_config.rationale"></a><a class="link" href="rationale.html" title="Rationale">Rationale</a>
+</h2></div></div></div>
+<div class="toc"><dl>
+<dt>The problem</dt>
+<dt>The solution</dt>
+</dl></div>
+
+ The problem with many traditional "textbook" implementations of configuration
+ headers (where all the configuration options are in a single "monolithic"
+ header) is that they violate certain fundamental software engineering principles
+ which would have the effect of making boost more fragile, more difficult to
+ maintain and more difficult to use safely. You can find a description of the
+ principles from the <a href="http://www.objectmentor.com/resources/articles/Principles_and_Patterns.pdf" target="_top">following
+ article</a>.
+ 
+<div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="boost_config.rationale.the_problem"></a><a class="link" href="rationale.html#boost_config.rationale.the_problem" title="The problem">The problem</a>
+</h3></div></div></div>
+
+ Consider a situation in which you are concurrently developing on multiple
+ platforms. Then consider adding a new platform or changing the platform definitions
+ of an existing platform. What happens? Everything, and this does literally
+ mean everything, recompiles. Isn't it quite absurd that adding a new platform,
+ which has absolutely nothing to do with previously existing platforms, means
+ that all code on all existing platforms needs to be recompiled?
+ 
+
+ Effectively, there is an imposed physical dependency between platforms that
+ have nothing to do with each other. Essentially, the traditional solution
+ employed by configuration headers does not conform to the Open-Closed Principle:
+ 
+<div class="blockquote"><blockquote class="blockquote">
+ "A module should be open for extension but closed
+ for modification."
+ </blockquote></div>
+
+ Extending a traditional configuration header implies modifying existing code.
+ 
+
+ Furthermore, consider the complexity and fragility of the platform detection
+ code. What if a simple change breaks the detection on some minor platform?
+ What if someone accidentally or on purpose (as a workaround for some other
+ problem) defines some platform dependent macros that are used by the detection
+ code? A traditional configuration header is one of the most volatile headers
+ of the entire library, and more stable elements of Boost would depend on
+ it. This violates the Stable Dependencies Principle:
+ 
+<div class="blockquote"><blockquote class="blockquote">
+ "Depend in the direction of stability."
+ </blockquote></div>
+
+ After even a minor change to a traditional configuration header on one minor
+ platform, almost everything on every platform should be tested if we follow
+ sound software engineering practice.
+ 
+
+ Another important issue is that it is not always possible to submit changes
+ to <code class="computeroutput"><boost/config.hpp></code>.
+ Some boost users are currently working on platforms using tools and libraries
+ that are under strict Non-Disclosure Agreements. In this situation it is
+ impossible to submit changes to a traditional monolithic configuration header,
+ instead some method by which the user can insert their own configuration
+ code must be provided.
+ 
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="boost_config.rationale.the_solution"></a><a class="link" href="rationale.html#boost_config.rationale.the_solution" title="The solution">The solution</a>
+</h3></div></div></div>
+
+ The approach taken by boost's configuration headers is to separate configuration
+ into three orthogonal parts: the compiler, the standard library and the platform.
+ Each compiler/standard library/platform gets its own mini-configuration header,
+ so that changes to one compiler's configuration (for example) does not affect
+ other compilers. In addition there are measures that can be taken both to
+ omit the compiler/standard library/platform detection code (so that adding
+ support to a new platform does not break dependencies), or to freeze the
+ configuration completely; providing almost complete protection against dependency
+ changes.
+ 
+</div>
+</div>
+<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
+<td align="left"></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Beman Dawes, Vesa Karvonen, John
+ Maddock
+ 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)
+ 
+</div></td>
+</tr></table>
+<hr>
+<div class="spirit-nav">
+<a accesskey="p" href="guidelines_for_boost_authors.html"><img src="../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.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="acknowledgements.html"><img src="../../../../../doc/src/images/next.png" alt="Next"></a>
+</div>
+</body>
+</html>

Added: website/public_html/live/doc/fixes/boost_1_52_0/libs/config/doc/html/index.html
==============================================================================
--- (empty file)
+++ website/public_html/live/doc/fixes/boost_1_52_0/libs/config/doc/html/index.html 2012-11-20 15:40:09 EST (Tue, 20 Nov 2012)
@@ -0,0 +1,960 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
+<title>Boost.Config</title>
+<link rel="stylesheet" href="../../../../doc/src/boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="Boost.Config">
+<link rel="next" href="boost_config/boost_macro_reference.html" title="Boost Macro Reference">
+</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">Home</td>
+<td align="center">Libraries</td>
+<td align="center">People</td>
+<td align="center">FAQ</td>
+<td align="center">More</td>
+</tr></table>
+<hr>
+<div class="spirit-nav"><a accesskey="n" href="boost_config/boost_macro_reference.html"><img src="../../../../doc/src/images/next.png" alt="Next"></a></div>
+<div class="article">
+<div class="titlepage">
+<div>
+<div><h2 class="title">
+<a name="config"></a>Boost.Config</h2></div>
+<div><div class="authorgroup"><div class="author"><h3 class="author">
+Vesa Karvonen, John Maddock Beman Dawes
+</h3></div></div></div>
+<div>Copyright © 2001-2007 Beman Dawes, Vesa Karvonen, John
+ Maddock</div>
+<div><div class="legalnotice">
+<a name="config.legal"></a>
+ 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)
+ 
+</div></div>
+</div>
+<hr>
+</div>
+<div class="toc">
+Table of Contents
+<dl>
+<dt><a href="index.html#boost_config.configuring_boost_for_your_platform">Configuring
+ Boost for Your Platform</a></dt>
+<dd><dl>
+<dt><a href="index.html#boost_config.configuring_boost_for_your_platform.using_the_default_boost_configuration">Using
+ the default boost configuration</a></dt>
+<dt><a href="index.html#boost_config.configuring_boost_for_your_platform.the__boost_config_hpp__header">The
+ <boost/config.hpp> header</a></dt>
+<dt><a href="index.html#boost_config.configuring_boost_for_your_platform.using_the_configure_script">Using
+ the configure script</a></dt>
+<dt><a href="index.html#boost_config.configuring_boost_for_your_platform.user_settable_options">User
+ settable options</a></dt>
+<dt><a href="index.html#boost_config.configuring_boost_for_your_platform.advanced_configuration_usage">Advanced
+ configuration usage</a></dt>
+<dt><a href="index.html#boost_config.configuring_boost_for_your_platform.testing_the_boost_configuration">Testing
+ the boost configuration</a></dt>
+</dl></dd>
+<dt>Boost Macro Reference</dt>
+<dd><dl>
+<dt><a href="boost_config/boost_macro_reference.html#boost_config.boost_macro_reference.macros_that_describe_c__03_defects">Macros
+ that describe C++03 defects</a></dt>
+<dt><a href="boost_config/boost_macro_reference.html#boost_config.boost_macro_reference.macros_that_describe_optional_features">Macros
+ that describe optional features</a></dt>
+<dt><a href="boost_config/boost_macro_reference.html#boost_config.boost_macro_reference.macros_that_describe_possible_c___future_features">Macros
+ that describe possible C++ future features</a></dt>
+<dt><a href="boost_config/boost_macro_reference.html#boost_config.boost_macro_reference.macros_that_describe_c__11_features_not_supported">Macros
+ that describe C++11 features not supported</a></dt>
+<dt><a href="boost_config/boost_macro_reference.html#boost_config.boost_macro_reference.macros_that_allow_use_of_c__11_features_with_c__03_compilers">Macros
+ that allow use of C++11 features with C++03 compilers</a></dt>
+<dt><a href="boost_config/boost_macro_reference.html#boost_config.boost_macro_reference.boost_helper_macros">Boost
+ Helper Macros</a></dt>
+<dt><a href="boost_config/boost_macro_reference.html#boost_config.boost_macro_reference.boost_informational_macros">Boost
+ Informational Macros</a></dt>
+<dt><a href="boost_config/boost_macro_reference.html#boost_config.boost_macro_reference.boost_deprecated_macros">Boost
+ Deprecated Macros</a></dt>
+<dt><a href="boost_config/boost_macro_reference.html#boost_config.boost_macro_reference.macros_for_libraries_with_separate_source_code">Macros
+ for libraries with separate source code</a></dt>
+</dl></dd>
+<dt><a href="boost_config/guidelines_for_boost_authors.html">Guidelines for
+ Boost Authors</a></dt>
+<dd><dl>
+<dt><a href="boost_config/guidelines_for_boost_authors.html#boost_config.guidelines_for_boost_authors.warnings">Disabling
+ Compiler Warnings</a></dt>
+<dt><a href="boost_config/guidelines_for_boost_authors.html#boost_config.guidelines_for_boost_authors.adding_new_defect_macros">Adding
+ New Defect Macros</a></dt>
+<dt><a href="boost_config/guidelines_for_boost_authors.html#boost_config.guidelines_for_boost_authors.adding_new_feature_test_macros">Adding
+ New Feature Test Macros</a></dt>
+<dt><a href="boost_config/guidelines_for_boost_authors.html#boost_config.guidelines_for_boost_authors.modifying_the_boost_configuration_headers">Modifying
+ the Boost Configuration Headers</a></dt>
+</dl></dd>
+<dt>Rationale</dt>
+<dd><dl>
+<dt>The problem</dt>
+<dt>The solution</dt>
+</dl></dd>
+<dt>Acknowledgements</dt>
+</dl>
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="boost_config.configuring_boost_for_your_platform"></a><a class="link" href="index.html#boost_config.configuring_boost_for_your_platform" title="Configuring Boost for Your Platform">Configuring
+ Boost for Your Platform</a>
+</h2></div></div></div>
+<div class="toc"><dl>
+<dt><a href="index.html#boost_config.configuring_boost_for_your_platform.using_the_default_boost_configuration">Using
+ the default boost configuration</a></dt>
+<dt><a href="index.html#boost_config.configuring_boost_for_your_platform.the__boost_config_hpp__header">The
+ <boost/config.hpp> header</a></dt>
+<dt><a href="index.html#boost_config.configuring_boost_for_your_platform.using_the_configure_script">Using
+ the configure script</a></dt>
+<dt><a href="index.html#boost_config.configuring_boost_for_your_platform.user_settable_options">User
+ settable options</a></dt>
+<dt><a href="index.html#boost_config.configuring_boost_for_your_platform.advanced_configuration_usage">Advanced
+ configuration usage</a></dt>
+<dt><a href="index.html#boost_config.configuring_boost_for_your_platform.testing_the_boost_configuration">Testing
+ the boost configuration</a></dt>
+</dl></div>
+<div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="boost_config.configuring_boost_for_your_platform.using_the_default_boost_configuration"></a><a class="link" href="index.html#boost_config.configuring_boost_for_your_platform.using_the_default_boost_configuration" title="Using the default boost configuration">Using
+ the default boost configuration</a>
+</h3></div></div></div>
+
+ Boost comes already configured for most common compilers and platforms; you
+ should be able to use boost "as is". Since the compiler is configured
+ separately from the standard library, the default configuration should work
+ even if you replace the compiler's standard library with a third-party standard
+ library (like STLport).
+ 
+
+ Using boost "as is" without trying to reconfigure is the recommended
+ method for using boost. You can, however, run the configure script if you
+ want to, and there are regression tests provided that allow you to test the
+ current boost configuration with your particular compiler setup.
+ 
+
+ Boost library users can request support for additional compilers or platforms
+ by visiting our Trac
+ and submitting a support request.
+ 
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="boost_config.configuring_boost_for_your_platform.the__boost_config_hpp__header"></a><a class="link" href="index.html#boost_config.configuring_boost_for_your_platform.the__boost_config_hpp__header" title="The <boost/config.hpp> header">The
+ <boost/config.hpp> header</a>
+</h3></div></div></div>
+
+ Boost library implementations access configuration macros via
+ 
+<pre class="programlisting">#include <boost/config.hpp>
+</pre>
+
+ While Boost library users are not required to include that file directly,
+ or use those configuration macros, such use is acceptable. The configuration
+ macros are documented as to their purpose, usage, and limitations which makes
+ them usable by both Boost library and user code.
+ 
+
+ Boost <a class="link" href="boost_config/boost_macro_reference.html#config_info_macros">informational</a> or <a class="link" href="boost_config/boost_macro_reference.html#config_helpers">helper</a>
+ macros are designed for use by Boost users as well as for our own internal
+ use. Note however, that the <a class="link" href="boost_config/boost_macro_reference.html#config_features">feature test</a>
+ and <a class="link" href="boost_config/boost_macro_reference.html#config_defects">defect test</a> macros were designed
+ for internal use by Boost libraries, not user code, so they can change at
+ any time (though no gratuitous changes are made to them). Boost library problems
+ resulting from changes to the configuration macros are caught by the Boost
+ regression tests, so the Boost libraries are updated to account for those
+ changes. By contrast, Boost library user code can be adversely affected by
+ changes to the macros without warning. The best way to keep abreast of changes
+ to the macros used in user code is to monitor the discussions on the Boost
+ developers list.
+ 
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="boost_config.configuring_boost_for_your_platform.using_the_configure_script"></a><a name="config_config_script"></a><a class="link" href="index.html#boost_config.configuring_boost_for_your_platform.using_the_configure_script" title="Using the configure script">Using
+ the configure script</a>
+</h3></div></div></div>
+<div class="important"><table border="0" summary="Important">
+<tr>
+<td rowspan="2" align="center" valign="top" width="25"><img alt="[Important]" src="../../../../doc/src/images/important.png"></td>
+<th align="left">Important</th>
+</tr>
+<tr><td align="left" valign="top">
+ This configure script only sets up the Boost headers for use with a particular
+ compiler. It has no effect on Boost.Build, or how the libraries are built.
+ </td></tr>
+</table></div>
+
+ If you know that boost is incorrectly configured for your particular setup,
+ and you are on a UNIX like platform, then you may want to try and improve
+ things by running the boost configure script. From a shell command prompt
+ you will need to cd into <boost-root><code class="computeroutput">/libs/config/</code>
+ and type:
+ 
+<div class="blockquote"><blockquote class="blockquote">
+ <code class="computeroutput">sh ./configure</code>
+ </blockquote></div>
+
+ you will see a list of the items being checked as the script works its way
+ through the regression tests. Note that the configure script only really
+ auto-detects your compiler if it's called g++, c++ or CC. If you are using
+ some other compiler you will need to set one or more of the following environment
+ variables:
+ 
+<div class="informaltable"><table class="table">
+<colgroup>
+<col>
+<col>
+</colgroup>
+<thead><tr>
+<th>
+ 
+ Variable
+ 
+ </th>
+<th>
+ 
+ Description
+ 
+ </th>
+</tr></thead>
+<tbody>
+<tr>
+<td>
+ 
+ CXX
+ 
+ </td>
+<td>
+ 
+ The name of the compiler, for example <code class="computeroutput">c++</code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ CXXFLAGS
+ 
+ </td>
+<td>
+ 
+ The compiler flags to use, for example <code class="computeroutput">-O2</code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ LDFLAGS
+ 
+ </td>
+<td>
+ 
+ The linker flags to use, for example <code class="computeroutput">-L/mypath</code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ LIBS
+ 
+ </td>
+<td>
+ 
+ Any libraries to link in, for example <code class="computeroutput">-lpthread</code>.
+ 
+ </td>
+</tr>
+</tbody>
+</table></div>
+
+ For example to run the configure script with HP aCC, you might use something
+ like:
+ 
+<pre class="programlisting">export CXX="aCC"
+export CXXFLAGS="-Aa -DAportable -D__HPACC_THREAD_SAFE_RB_TREE \
+ -DRWSTD_MULTI_THREAD -DRW_MULTI_THREAD -D_REENTRANT -D_THREAD_SAFE"
+export LDFLAGS="-DAportable"
+export LIBS="-lpthread"
+sh ./configure
+</pre>
+
+ However you run the configure script, when it finishes you will find a new
+ header -<code class="computeroutput">user.hpp</code>- located in the <boost-root><code class="computeroutput">/libs/config/</code>
+ directory. Note that configure does not install this
+ header into your boost include path by default. This header contains
+ all the options generated by the configure script, plus a header-section
+ that contains the user settable options from the default version of <boost/config/user.hpp>
+ (located under <boost-root><code class="computeroutput">/boost/config/</code>).
+ There are two ways you can use this header:
+ 
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem">
+ Option 1: copy the header into <boost-root><code class="computeroutput">/boost/config/</code> so that it replaces the default user.hpp
+ provided by boost. This option allows only one configure-generated setup;
+ boost developers should avoid this option, as it incurs the danger of
+ accidentally committing a configure-modified <boost/config/user.hpp>
+ to the svn repository (something you will not be thanked for!).
+ </li>
+<li class="listitem">
+ Option 2: give the header a more memorable
+ name, and place it somewhere convenient; then, define the macro <code class="computeroutput">BOOST_USER_CONFIG</code> to point to it. For
+ example create a new sub-directory <boost-root><code class="computeroutput">/boost/config/</code> <code class="computeroutput">user/</code>, and copy the header there; for example
+ as <code class="computeroutput">multithread-gcc-config.hpp</code>. Then, when compiling add the command
+ line option: <code class="computeroutput">-DBOOST_USER_CONFIG="<boost/config/user/multithread-gcc-config.hpp>"</code>,
+ and boost will use the new configuration header. This option allows you
+ to generate more than one configuration header, and to keep them separate
+ from the boost source - so that updates to the source do not interfere
+ with your configuration.
+ </li>
+</ul></div>
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="boost_config.configuring_boost_for_your_platform.user_settable_options"></a><a name="config_user_settable"></a><a class="link" href="index.html#boost_config.configuring_boost_for_your_platform.user_settable_options" title="User settable options">User
+ settable options</a>
+</h3></div></div></div>
+
+ There are some configuration-options that represent user choices, rather
+ than compiler defects or platform specific options. These are listed in
+ <code class="computeroutput"><boost/config/user.hpp></code>
+ and at the start of a configure-generated <code class="computeroutput">user.hpp</code> header.
+ You can define these on the command line, or by editing <code class="computeroutput"><boost/config/user.hpp></code>, they are listed in the following table:
+ 
+<div class="informaltable"><table class="table">
+<colgroup>
+<col>
+<col>
+</colgroup>
+<thead><tr>
+<th>
+ 
+ Macro
+ 
+ </th>
+<th>
+ 
+ Description
+ 
+ </th>
+</tr></thead>
+<tbody>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_USER_CONFIG</code>
+ 
+ </td>
+<td>
+ 
+ When defined, it should point to the name of the user configuration
+ file to include prior to any boost configuration files. When not
+ defined, defaults to <boost/config/user.hpp>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_COMPILER_CONFIG</code>
+ 
+ </td>
+<td>
+ 
+ When defined, it should point to the name of the compiler configuration
+ file to use. Defining this cuts out the compiler selection logic,
+ and eliminates the dependency on the header containing that logic.
+ For example if you are using gcc, then you could define BOOST_COMPILER_CONFIG
+ to <boost/config/compiler/gcc.hpp>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_STDLIB_CONFIG</code>
+ 
+ </td>
+<td>
+ 
+ When defined, it should point to the name of the standard library
+ configuration file to use. Defining this cuts out the standard
+ library selection logic, and eliminates the dependency on the header
+ containing that logic. For example if you are using STLport, then
+ you could define <code class="computeroutput">BOOST_STDLIB_CONFIG</code>
+ to <boost/config/stdlib/stlport.hpp>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_PLATFORM_CONFIG</code>
+ 
+ </td>
+<td>
+ 
+ When defined, it should point to the name of the platform configuration
+ file to use. Defining this cuts out the platform selection logic,
+ and eliminates the dependency on the header containing that logic.
+ For example if you are compiling on linux, then you could define
+ <code class="computeroutput">BOOST_PLATFORM_CONFIG</code>
+ to <boost/config/platform/linux.hpp>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_COMPILER_CONFIG</code>
+ 
+ </td>
+<td>
+ 
+ When defined, no compiler configuration file is selected or included,
+ define when the compiler is fully conformant with the standard,
+ or where the user header (see <code class="computeroutput">BOOST_USER_CONFIG</code>),
+ has had any options necessary added to it, for example by an autoconf
+ generated configure script.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_STDLIB_CONFIG</code>
+ 
+ </td>
+<td>
+ 
+ When defined, no standard library configuration file is selected
+ or included, define when the standard library is fully conformant
+ with the standard, or where the user header (see <code class="computeroutput">BOOST_USER_CONFIG</code>), has had any
+ options necessary added to it, for example by an autoconf generated
+ configure script.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_PLATFORM_CONFIG</code>
+ 
+ </td>
+<td>
+ 
+ When defined, no platform configuration file is selected or included,
+ define when the platform is fully conformant with the standard
+ (and has no useful extra features), or where the user header (see
+ <code class="computeroutput">BOOST_USER_CONFIG</code>),
+ has had any options necessary added to it, for example by an autoconf
+ generated configure script.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_NO_CONFIG</code>
+ 
+ </td>
+<td>
+ 
+ Equivalent to defining all of <code class="computeroutput">BOOST_NO_COMPILER_CONFIG</code>,
+ <code class="computeroutput">BOOST_NO_STDLIB_CONFIG</code>
+ and <code class="computeroutput">BOOST_NO_PLATFORM_CONFIG</code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_STRICT_CONFIG</code>
+ 
+ </td>
+<td>
+ 
+ The normal behavior for compiler versions that are newer than the
+ last known version, is to assume that they have all the same defects
+ as the last known version. By setting this define, then compiler
+ versions that are newer than the last known version are assumed
+ to be fully conforming with the standard. This is probably most
+ useful for boost developers or testers, and for those who want
+ to use boost to test beta compiler versions.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_ASSERT_CONFIG</code>
+ 
+ </td>
+<td>
+ 
+ When this flag is set, if the config finds anything unknown, then
+ it will stop with a #error rather than continue. Boost regression
+ testers should set this define, as should anyone who wants to quickly
+ check whether boost is supported on their platform.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_DISABLE_THREADS</code>
+ 
+ </td>
+<td>
+ 
+ When defined, disables threading support, even if the compiler
+ in its current translation mode supports multiple threads.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_DISABLE_WIN32</code>
+ 
+ </td>
+<td>
+ 
+ When defined, disables the use of Win32 specific API's, even when
+ these are available. Also has the effect of setting <code class="computeroutput">BOOST_DISABLE_THREADS</code> unless
+ <code class="computeroutput">BOOST_HAS_PTHREADS</code>
+ is set. This option may be set automatically by the config system
+ when it detects that the compiler is in "strict mode".
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_DISABLE_ABI_HEADERS</code>
+ 
+ </td>
+<td>
+ 
+ Stops boost headers from including any prefix/suffix headers that
+ normally control things like struct packing and alignment.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_ABI_PREFIX</code>
+ 
+ </td>
+<td>
+ 
+ A prefix header to include in place of whatever boost.config would
+ normally select, any replacement should set up struct packing and
+ alignment options as required.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_ABI_SUFFIX</code>
+ 
+ </td>
+<td>
+ 
+ A suffix header to include in place of whatever boost.config would
+ normally select, any replacement should undo the effects of the
+ prefix header.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_ALL_DYN_LINK</code>
+ 
+ </td>
+<td>
+ 
+ Forces all libraries that have separate source, to be linked as
+ dll's rather than static libraries on Microsoft Windows (this macro
+ is used to turn on <code class="computeroutput">__declspec(dllimport)</code> modifiers, so that the compiler
+ knows which symbols to look for in a dll rather than in a static
+ library). Note that there may be some libraries that can only be
+ statically linked (Boost.Test for example) and others which may
+ only be dynamically linked (Boost.Thread for example), in these
+ cases this macro has no effect.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_</code>WHATEVER<code class="computeroutput">_DYN_LINK</code>
+ 
+ </td>
+<td>
+ 
+ Forces library "whatever" to be linked as a dll rather
+ than a static library on Microsoft Windows: replace the WHATEVER
+ part of the macro name with the name of the library that you want
+ to dynamically link to, for example use <code class="computeroutput">BOOST_DATE_TIME_DYN_LINK</code>
+ or <code class="computeroutput">BOOST_REGEX_DYN_LINK</code>
+ etc (this macro is used to turn on <code class="computeroutput">__declspec(dllimport)</code> modifiers, so that the compiler
+ knows which symbols to look for in a dll rather than in a static
+ library). Note that there may be some libraries that can only be
+ statically linked (Boost.Test for example) and others which may
+ only be dynamically linked (Boost.Thread for example), in these
+ cases this macro is unsupported.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_ALL_NO_LIB</code>
+ 
+ </td>
+<td>
+ 
+ Tells the config system not to automatically select which libraries
+ to link against. Normally if a compiler supports #pragma lib, then
+ the correct library build variant will be automatically selected
+ and linked against, simply by the act of including one of that
+ library's headers. This macro turns that feature off.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_</code>WHATEVER<code class="computeroutput">_NO_LIB</code>
+ 
+ </td>
+<td>
+ 
+ Tells the config system not to automatically select which library
+ to link against for library "whatever", replace WHATEVER
+ in the macro name with the name of the library; for example <code class="computeroutput">BOOST_DATE_TIME_NO_LIB</code> or <code class="computeroutput">BOOST_REGEX_NO_LIB</code>. Normally
+ if a compiler supports <code class="computeroutput">#pragma
+ lib</code>, then the correct
+ library build variant will be automatically selected and linked
+ against, simply by the act of including one of that library's headers.
+ This macro turns that feature off.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_LIB_DIAGNOSTIC</code>
+ 
+ </td>
+<td>
+ 
+ Causes the auto-linking code to output diagnostic messages indicating
+ the name of the library that is selected for linking.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">BOOST_LIB_TOOLSET</code>
+ 
+ </td>
+<td>
+ 
+ Overrides the name of the toolset part of the name of library being
+ linked to; note if defined this must be defined to a quoted string
+ literal, for example "abc".
+ 
+ </td>
+</tr>
+</tbody>
+</table></div>
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="boost_config.configuring_boost_for_your_platform.advanced_configuration_usage"></a><a class="link" href="index.html#boost_config.configuring_boost_for_your_platform.advanced_configuration_usage" title="Advanced configuration usage">Advanced
+ configuration usage</a>
+</h3></div></div></div>
+<div class="toc"><dl>
+<dt><a href="index.html#boost_config.configuring_boost_for_your_platform.advanced_configuration_usage.example_1__creating_our_own_frozen_configuration">Example
+ 1: creating our own frozen configuration</a></dt>
+<dt><a href="index.html#boost_config.configuring_boost_for_your_platform.advanced_configuration_usage.example_2__skipping_files_that_you_don_t_need">Example
+ 2: skipping files that you don't need</a></dt>
+<dt><a href="index.html#boost_config.configuring_boost_for_your_platform.advanced_configuration_usage.example_3__using_configure_script_to_freeze_the_boost_configuration">Example
+ 3: using configure script to freeze the boost configuration</a></dt>
+</dl></div>
+
+ By setting various macros on the compiler command line or by editing <boost/config/user.hpp>,
+ the boost configuration setup can be optimised in a variety of ways.
+ 
+
+ Boost's configuration is structured so that the user-configuration is included
+ first (defaulting to <boost/config/user.hpp>
+ if <code class="computeroutput">BOOST_USER_CONFIG</code> is not
+ defined). This sets up any user-defined policies, and gives the user-configuration
+ a chance to influence what happens next.
+ 
+
+ Next the compiler, standard library, and platform configuration files are
+ included. These are included via macros (<code class="computeroutput">BOOST_COMPILER_CONFIG</code>
+ etc, <a class="link" href="index.html#config_user_settable">see user settable macros</a>),
+ and if the corresponding macro is undefined then a separate header that detects
+ which compiler/standard library/platform is in use is included in order to
+ set these. The config can be told to ignore these headers altogether if the
+ corresponding <code class="computeroutput">BOOST_NO_XXX</code>
+ macro is set (for example <code class="computeroutput">BOOST_NO_COMPILER_CONFIG</code>
+ to disable including any compiler configuration file - <a class="link" href="index.html#config_user_settable">see
+ user settable macros</a>).
+ 
+
+ Finally the boost configuration header, includes <boost/config/suffix.hpp>;
+ this header contains any boiler plate configuration code - for example where
+ one boost macro being set implies that another must be set also.
+ 
+
+ The following usage examples represent just a few of the possibilities:
+ 
+<div class="section">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="boost_config.configuring_boost_for_your_platform.advanced_configuration_usage.example_1__creating_our_own_frozen_configuration"></a><a class="link" href="index.html#boost_config.configuring_boost_for_your_platform.advanced_configuration_usage.example_1__creating_our_own_frozen_configuration" title="Example 1: creating our own frozen configuration">Example
+ 1: creating our own frozen configuration</a>
+</h4></div></div></div>
+
+ Lets suppose that we're building boost with Visual C++ 6, and STLport 4.0.
+ Lets suppose also that we don't intend to update our compiler or standard
+ library any time soon. In order to avoid breaking dependencies when we
+ update boost, we may want to "freeze" our configuration headers,
+ so that we only have to rebuild our project if the boost code itself has
+ changed, and not because the boost config has been updated for more recent
+ versions of Visual C++ or STLport. We'll start by realising that the configuration
+ files in use are: <boost/config/compiler/visualc.hpp> for the compiler, <boost/config/stdlib/stlport.hpp> for the
standard library, and
+ <boost/config/platform/win32.hpp> for the platform. Next we'll
+ create our own private configuration directory: <code class="computeroutput">boost/config/mysetup/</code>, and copy the configuration files into
+ there. Finally, open up <boost/config/user.hpp>
+ and edit the following defines:
+ 
+<pre class="programlisting">#define BOOST_COMPILER_CONFIG "boost/config/mysetup/visualc.hpp"
+#define BOOST_STDLIB_CONFIG "boost/config/mysetup/stlport.hpp"
+#define BOOST_USER_CONFIG "boost/config/mysetup/win32.hpp"
+</pre>
+
+ Now when you use boost, its configuration header will go straight to our
+ "frozen" versions, and ignore the default versions, you will
+ now be insulated from any configuration changes when you update boost.
+ This technique is also useful if you want to modify some of the boost configuration
+ files; for example if you are working with a beta compiler release not
+ yet supported by boost.
+ 
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="boost_config.configuring_boost_for_your_platform.advanced_configuration_usage.example_2__skipping_files_that_you_don_t_need"></a><a class="link" href="index.html#boost_config.configuring_boost_for_your_platform.advanced_configuration_usage.example_2__skipping_files_that_you_don_t_need" title="Example 2: skipping files that you don't need">Example
+ 2: skipping files that you don't need</a>
+</h4></div></div></div>
+
+ Lets suppose that you're using boost with a compiler that is fully conformant
+ with the standard; you're not interested in the fact that older versions
+ of your compiler may have had bugs, because you know that your current
+ version does not need any configuration macros setting. In a case like
+ this, you can define <code class="computeroutput">BOOST_NO_COMPILER_CONFIG</code>
+ either on the command line, or in <boost/config/user.hpp>,
+ and miss out the compiler configuration header altogether (actually you
+ miss out two headers, one which works out what the compiler is, and one
+ that configures boost for it). This has two consequences: the first is
+ that less code has to be compiled, and the second that you have removed
+ a dependency on two boost headers.
+ 
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="boost_config.configuring_boost_for_your_platform.advanced_configuration_usage.example_3__using_configure_script_to_freeze_the_boost_configuration"></a><a class="link" href="index.html#boost_config.configuring_boost_for_your_platform.advanced_configuration_usage.example_3__using_configure_script_to_freeze_the_boost_configuration" title="Example 3: using configure script to freeze the boost configuration">Example
+ 3: using configure script to freeze the boost configuration</a>
+</h4></div></div></div>
+
+ If you are working on a unix-like platform then you can use the configure
+ script to generate a "frozen" configuration based on your current
+ compiler setup - <a class="link" href="index.html#config_config_script">see using the configure
+ script for more details</a>.
+ 
+</div>
+</div>
+<div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="boost_config.configuring_boost_for_your_platform.testing_the_boost_configuration"></a><a class="link" href="index.html#boost_config.configuring_boost_for_your_platform.testing_the_boost_configuration" title="Testing the boost configuration">Testing
+ the boost configuration</a>
+</h3></div></div></div>
+
+ The boost configuration library provides a full set of regression test programs
+ under the <boost-root><code class="computeroutput">/boost/config/</code>
+ <code class="computeroutput">test/</code>
+ sub-directory:
+ 
+<div class="informaltable"><table class="table">
+<colgroup>
+<col>
+<col>
+</colgroup>
+<thead><tr>
+<th>
+ 
+ File
+ 
+ </th>
+<th>
+ 
+ Description
+ 
+ </th>
+</tr></thead>
+<tbody>
+<tr>
+<td>
+ 
+ <code class="computeroutput">config_info.cpp</code>
+ 
+ </td>
+<td>
+ 
+ Prints out a detailed description of your compiler/standard library/platform
+ setup, plus your current boost configuration. The information provided
+ by this program useful in setting up the boost configuration files.
+ If you report that boost is incorrectly configured for your compiler/library/platform
+ then please include the output from this program when reporting
+ the changes required.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">config_test.cpp</code>
+ 
+ </td>
+<td>
+ 
+ A monolithic test program that includes most of the individual
+ test cases. This provides a quick check to see if boost is correctly
+ configured for your compiler/library/platform.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">limits_test.cpp</code>
+ 
+ </td>
+<td>
+ 
+ Tests your standard library's <code class="computeroutput">std::numeric_limits</code>
+ implementation (or its boost provided replacement if <code class="computeroutput">BOOST_NO_LIMITS</code> is defined).
+ This test file fails with most versions of numeric_limits, mainly
+ due to the way that some compilers treat NAN's and infinity.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">no_*pass.cpp</code>
+ 
+ </td>
+<td>
+ 
+ Individual compiler defect test files. Each of these should compile,
+ if one does not then the corresponding <code class="computeroutput">BOOST_NO_XXX</code>
+ macro needs to be defined - see each test file for specific details.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">no_*fail.cpp</code>
+ 
+ </td>
+<td>
+ 
+ Individual compiler defect test files. Each of these should not
+ compile, if one does then the corresponding <code class="computeroutput">BOOST_NO_XXX</code>
+ macro is defined when it need not be - see each test file for specific
+ details.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">has_*pass.cpp</code>
+ 
+ </td>
+<td>
+ 
+ Individual feature test files. If one of these does not compile
+ then the corresponding <code class="computeroutput">BOOST_HAS_XXX</code>
+ macro is defined when it should not be - see each test file for
+ specific details.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">has_*fail.cpp</code>
+ 
+ </td>
+<td>
+ 
+ Individual feature test files. If one of these does compile then
+ the corresponding <code class="computeroutput">BOOST_HAS_XXX</code>
+ macro can be safely defined - see each test file for specific details.
+ 
+ </td>
+</tr>
+</tbody>
+</table></div>
+
+ Although you can run the configuration regression tests as individual test
+ files, there are rather a lot of them, so there are a couple of shortcuts
+ to help you out:
+ 
+
+ If you have built the <a href="../../../../tools/regression/doc/index.html" target="_top">boost
+ regression test driver</a>, then you can use this to produce a nice html
+ formatted report of the results using the supplied test file.
+ 
+
+ Alternatively you can run the configure script like this:
+ 
+<div class="blockquote"><blockquote class="blockquote">
+ <code class="computeroutput">./configure
+ --enable-test</code>
+ </blockquote></div>
+
+ in which case the script will test the current configuration rather than
+ creating a new one from scratch.
+ 
+
+ If you are reporting the results of these tests for a new platform/library/compiler
+ then please include a log of the full compiler output, the output from <code class="computeroutput">config_info.cpp</code>, and the pass/fail test results.
+ 
+</div>
+</div>
+</div>
+<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
+<td align="left">Last revised: November 20, 2012 at 20:33:30 GMT</td>
+<td align="right"><div class="copyright-footer"></div></td>
+</tr></table>
+<hr>
+<div class="spirit-nav"><a accesskey="n" href="boost_config/boost_macro_reference.html"><img src="../../../../doc/src/images/next.png" alt="Next"></a></div>
+</body>
+</html>

Next message: marshall_at_[hidden]: "[Boost-commit] svn:boost r81444 - in trunk/boost: chrono signals2 signals2/detail"
Previous message: marshall_at_[hidden]: "[Boost-commit] svn:boost r81442 - in trunk/boost: detail random random/detail"

Date view	Thread view	Subject view	Author view