Boost-Commit :

Date view	Thread view	Subject view	Author view

Subject: [Boost-commit] svn:boost r63504 - in trunk/libs/config/doc/html: . boost_config
From: daniel_james_at_[hidden]
Date: 2010-07-02 14:55:06

Author: danieljames
Date: 2010-07-01 18:11:07 EDT (Thu, 01 Jul 2010)
New Revision: 63504
URL: http://svn.boost.org/trac/boost/changeset/63504

Log:
Rebuild config documentation.
Text files modified:
   trunk/libs/config/doc/html/boost_config/acknowledgements.html | 10
   trunk/libs/config/doc/html/boost_config/boost_macro_reference.html | 3759 ++++++++++++++++++++-------------------
   trunk/libs/config/doc/html/boost_config/guidelines_for_boost_authors.html | 260 +-
   trunk/libs/config/doc/html/boost_config/rationale.html | 40
   trunk/libs/config/doc/html/index.html | 720 +++---
   5 files changed, 2386 insertions(+), 2403 deletions(-)

Modified: trunk/libs/config/doc/html/boost_config/acknowledgements.html
==============================================================================
--- trunk/libs/config/doc/html/boost_config/acknowledgements.html (original)
+++ trunk/libs/config/doc/html/boost_config/acknowledgements.html 2010-07-01 18:11:07 EDT (Thu, 01 Jul 2010)
@@ -2,8 +2,8 @@
<head>
<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Acknowledgements</title>
-<link rel="stylesheet" href="../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<link rel="stylesheet" href="../../../../../doc/src/boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
<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">
@@ -19,9 +19,9 @@
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="rationale.html"><img src="../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../doc/html/images/home.png" alt="Home"></a>
+<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" lang="en">
+<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>
@@ -55,7 +55,7 @@
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="rationale.html"><img src="../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../doc/html/images/home.png" alt="Home"></a>
+<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>

Modified: trunk/libs/config/doc/html/boost_config/boost_macro_reference.html
==============================================================================
--- trunk/libs/config/doc/html/boost_config/boost_macro_reference.html (original)
+++ trunk/libs/config/doc/html/boost_config/boost_macro_reference.html 2010-07-01 18:11:07 EDT (Thu, 01 Jul 2010)
@@ -2,8 +2,8 @@
<head>
<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Boost Macro Reference</title>
-<link rel="stylesheet" href="../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<link rel="stylesheet" href="../../../../../doc/src/boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
<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">
@@ -20,9 +20,9 @@
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="../index.html"><img src="../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="guidelines_for_boost_authors.html"><img src="../../../../../doc/html/images/next.png" alt="Next"></a>
+<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" lang="en">
+<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>
@@ -44,7 +44,7 @@
</dl></div>
<a name="config_defects"></a>
 
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="boost_config.boost_macro_reference.macros_that_describe_defects"></a><a class="link" href="boost_macro_reference.html#boost_config.boost_macro_reference.macros_that_describe_defects" title="Macros that describe defects">Macros
 that describe defects</a>
@@ -62,240 +62,240 @@
</colgroup>
<thead><tr>
<th>
- 
- Macro
- 
+ 
+ Macro
+ 
 </th>
<th>
- 
- Section
- 
+ 
+ Section
+ 
 </th>
<th>
- 
- Description
- 
+ 
+ Description
+ 
 </th>
</tr></thead>
<tbody>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_BCB_PARTIAL_SPECIALIZATION_BUG</code>
- 
+ 
+ <code class="computeroutput">BOOST_BCB_PARTIAL_SPECIALIZATION_BUG</code>
+ 
 </td>
<td>
- 
- Compiler
- 
+ 
+ Compiler
+ 
 </td>
<td>
- 
- The compiler exibits certain partial specialisation bug - probably
- Borland C++ Builder specific.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_FUNCTION_SCOPE_USING_DECLARATION_BREAKS_ADL</code>
+ 
 </td>
<td>
- 
- Compiler
- 
+ 
+ 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.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_NO_ADL_BARRIER</code>
+ 
 </td>
<td>
- 
- Compiler
- 
+ 
+ Compiler
+ 
 </td>
<td>
- 
- The compiler locates and searches namespaces that it should *not*
- in fact search when performing argument dependent lookup.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_NO_ARGUMENT_DEPENDENT_LOOKUP</code>
+ 
 </td>
<td>
- 
- Compiler
- 
+ 
+ Compiler
+ 
 </td>
<td>
- 
- Compiler does not implement argument-dependent lookup (also named
- Koenig lookup); see std::3.4.2 [basic.koenig.lookup]
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_NO_AUTO_PTR</code>
+ 
 </td>
<td>
- 
- Standard library
- 
+ 
+ Standard library
+ 
 </td>
<td>
- 
- If the compiler / library supplies non-standard or broken <code class="computeroutput">std::auto_ptr</code>.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_NO_COMPLETE_VALUE_INITIALIZATION</code>
+ 
 </td>
<td>
- 
- Compiler
- 
+ 
+ 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>
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_NO_CTYPE_FUNCTIONS</code>
+ 
 </td>
<td>
- 
- Platform
- 
+ 
+ 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.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_NO_CV_SPECIALIZATIONS</code>
+ 
 </td>
<td>
- 
- Compiler
- 
+ 
+ Compiler
+ 
 </td>
<td>
- 
- If template specialisations for cv-qualified types conflict with
- a specialisation for a cv-unqualififed type.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_NO_CV_VOID_SPECIALIZATIONS</code>
+ 
 </td>
<td>
- 
- Compiler
- 
+ 
+ Compiler
+ 
 </td>
<td>
- 
- If template specialisations for cv-void types conflict with a specialisation
- for void.
- 
+ 
+ If template specialisations for cv-void types conflict with a specialisation
+ for void.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_CWCHAR</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_CWCHAR</code>
+ 
 </td>
<td>
- 
- Platform
- 
+ 
+ Platform
+ 
 </td>
<td>
- 
- The Platform does not provide <code class="computeroutput"><wchar.h></code>
- and <code class="computeroutput"><cwchar></code>.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_NO_CWCTYPE</code>
+ 
 </td>
<td>
- 
- Platform
- 
+ 
+ Platform
+ 
 </td>
<td>
- 
- The Platform does not provide <code class="computeroutput"><wctype.h></code>
- and <code class="computeroutput"><cwctype></code>.
- 
+ 
+ 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_DEPENDENT_NESTED_DERIVATIONS</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_DEPENDENT_NESTED_DERIVATIONS</code>
+ 
 </td>
<td>
- 
- Compiler
- 
+ 
+ Compiler
+ 
 </td>
<td>
- 
- The compiler fails to compile a nested class that has a dependent
- base class:
+ 
+ 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 : {
@@ -303,106 +303,106 @@
 struct bar : public U {};
</pre>

- };
- 
+ };
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_DEPENDENT_TYPES_IN_TEMPLATE_VALUE_PARAMETERS</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_DEPENDENT_TYPES_IN_TEMPLATE_VALUE_PARAMETERS</code>
+ 
 </td>
<td>
- 
- Compiler
- 
+ 
+ Compiler
+ 
 </td>
<td>
- 
- Template value parameters cannot have a dependent type, for example:
-
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_NO_EXCEPTION_STD_NAMESPACE</code>
+ 
 </td>
<td>
- 
- Standard Library
- 
+ 
+ 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.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_NO_EXCEPTIONS</code>
+ 
 </td>
<td>
- 
- Compiler
- 
+ 
+ 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!
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_NO_EXPLICIT_FUNCTION_TEMPLATE_ARGUMENTS</code>
+ 
 </td>
<td>
- 
- Compiler
- 
+ 
+ Compiler
+ 
 </td>
<td>
- 
- Can only use deduced template arguments when calling function template
- instantiations.
- 
+ 
+ Can only use deduced template arguments when calling function template
+ instantiations.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_FUNCTION_TEMPLATE_ORDERING</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_FUNCTION_TEMPLATE_ORDERING</code>
+ 
 </td>
<td>
- 
- Compiler
- 
+ 
+ Compiler
+ 
 </td>
<td>
- 
- The compiler does not perform function template ordering or its function
- template ordering is incorrect.
+ 
+ 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);
@@ -415,876 +415,875 @@
f(&bar); // should choose #2.
</pre>

- 
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_INCLASS_MEMBER_INITIALIZATION</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_INCLASS_MEMBER_INITIALIZATION</code>
+ 
 </td>
<td>
- 
- Compiler
- 
+ 
+ Compiler
+ 
 </td>
<td>
- 
- Compiler violates std::9.4.2/4.
- 
+ 
+ Compiler violates std::9.4.2/4.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_INTRINSIC_WCHAR_T</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_INTRINSIC_WCHAR_T</code>
+ 
 </td>
<td>
- 
- Compiler
- 
+ 
+ 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.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_NO_IOSFWD</code>
+ 
 </td>
<td>
- 
- std lib
- 
+ 
+ std lib
+ 
 </td>
<td>
- 
- The standard library lacks <code class="computeroutput"><iosfwd></code>.
- 
+ 
+ The standard library lacks <code class="computeroutput"><iosfwd></code>.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_IOSTREAM</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_IOSTREAM</code>
+ 
 </td>
<td>
- 
- std lib
- 
+ 
+ std lib
+ 
 </td>
<td>
- 
- The standard library lacks <code class="computeroutput"><iostream></code>,
- <code class="computeroutput"><istream></code> or <code class="computeroutput"><ostream></code>.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_NO_IS_ABSTRACT</code>
+ 
 </td>
<td>
- 
- Compiler
- 
+ 
+ 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.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_NO_LIMITS</code>
+ 
 </td>
<td>
- 
- Standard library
- 
+ 
+ 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>.
- 
+ 
+ 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_LIMITS_COMPILE_TIME_CONSTANTS</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_LIMITS_COMPILE_TIME_CONSTANTS</code>
+ 
 </td>
<td>
- 
- Standard library
- 
+ 
+ Standard library
+ 
 </td>
<td>
- 
- Constants such as <code class="computeroutput">numeric_limits<T>::is_signed</code>
- are not available for use at compile-time.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_NO_LONG_LONG_NUMERIC_LIMITS</code>
+ 
 </td>
<td>
- 
- Standard library
- 
+ 
+ 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.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_NO_MEMBER_FUNCTION_SPECIALIZATIONS</code>
+ 
 </td>
<td>
- 
- Compiler
- 
+ 
+ Compiler
+ 
 </td>
<td>
- 
- The compiler does not support the specialization of individual member
- functions of template classes.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_NO_MEMBER_TEMPLATE_KEYWORD</code>
+ 
 </td>
<td>
- 
- Compiler
- 
+ 
+ Compiler
+ 
 </td>
<td>
- 
- If the compiler supports member templates, but not the template keyword
- when accessing member template classes.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_NO_MEMBER_TEMPLATE_FRIENDS</code>
+ 
 </td>
<td>
- 
- Compiler
- 
+ 
+ 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.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_NO_MEMBER_TEMPLATES</code>
+ 
 </td>
<td>
- 
- Compiler
- 
+ 
+ Compiler
+ 
 </td>
<td>
- 
- Member template functions not fully supported.
- 
+ 
+ Member template functions not fully supported.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_MS_INT64_NUMERIC_LIMITS</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_MS_INT64_NUMERIC_LIMITS</code>
+ 
 </td>
<td>
- 
- Standard library
- 
+ 
+ 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.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_NO_NESTED_FRIENDSHIP</code>
+ 
 </td>
<td>
- 
- Compiler
- 
+ 
+ Compiler
+ 
 </td>
<td>
- 
- Compiler doesn't allow a nested class to access private members of
- its containing class. Probably Borland/CodeGear specific.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_NO_OPERATORS_IN_NAMESPACE</code>
+ 
 </td>
<td>
- 
- Compiler
- 
+ 
+ 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.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_NO_PARTIAL_SPECIALIZATION_IMPLICIT_DEFAULT_ARGS</code>
+ 
 </td>
<td>
- 
- Compiler
- 
+ 
+ Compiler
+ 
 </td>
<td>
- 
- The compiler does not correctly handle partial specializations which
- depend upon default arguments in the primary template.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_NO_POINTER_TO_MEMBER_CONST</code>
+ 
 </td>
<td>
- 
- Compiler
- 
+ 
+ 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.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_NO_POINTER_TO_MEMBER_TEMPLATE_PARAMETERS</code>
+ 
 </td>
<td>
- 
- Compiler
- 
+ 
+ Compiler
+ 
 </td>
<td>
- 
- Pointers to members don't work when used as template parameters.
- 
+ 
+ Pointers to members don't work when used as template parameters.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_PRIVATE_IN_AGGREGATE</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_PRIVATE_IN_AGGREGATE</code>
+ 
 </td>
<td>
- 
- Compiler
- 
+ 
+ Compiler
+ 
 </td>
<td>
- 
- The compiler misreads 8.5.1, treating classes as non-aggregate if
- they contain private or protected member functions.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_NO_RTTI</code>
+ 
 </td>
<td>
- 
- Compiler
- 
+ 
+ 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.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_NO_SFINAE</code>
+ 
 </td>
<td>
- 
- Compiler
- 
+ 
+ Compiler
+ 
 </td>
<td>
- 
- The compiler does not support the "Substitution Failure Is Not
- An Error" meta-programming idiom.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_NO_SFINAE_EXPR</code>
+ 
 </td>
<td>
- 
- Compiler
- 
+ 
+ Compiler
+ 
 </td>
<td>
- 
- The compiler does not support usage of SFINAE with arbitrary expressions.
- 
+ 
+ The compiler does not support usage of SFINAE with arbitrary expressions.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_STD_ALLOCATOR</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_STD_ALLOCATOR</code>
+ 
 </td>
<td>
- 
- Standard library
- 
+ 
+ Standard library
+ 
 </td>
<td>
- 
- The C++ standard library does not provide a standards conforming
- <code class="computeroutput">std::allocator</code>.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_NO_STD_DISTANCE</code>
+ 
 </td>
<td>
- 
- Standard library
- 
+ 
+ Standard library
+ 
 </td>
<td>
- 
- The platform does not have a conforming version of <code class="computeroutput">std::distance</code>.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_NO_STD_ITERATOR</code>
+ 
 </td>
<td>
- 
- Standard library
- 
+ 
+ Standard library
+ 
 </td>
<td>
- 
- The C++ implementation fails to provide the <code class="computeroutput">std::iterator</code>
- class.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_NO_STD_ITERATOR_TRAITS</code>
+ 
 </td>
<td>
- 
- Standard library
- 
+ 
+ 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.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_NO_STD_LOCALE</code>
+ 
 </td>
<td>
- 
- Standard library
- 
+ 
+ Standard library
+ 
 </td>
<td>
- 
- The standard library lacks <code class="computeroutput">std::locale</code>.
- 
+ 
+ The standard library lacks <code class="computeroutput">std::locale</code>.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_STD_MESSAGES</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_STD_MESSAGES</code>
+ 
 </td>
<td>
- 
- Standard library
- 
+ 
+ Standard library
+ 
 </td>
<td>
- 
- The standard library lacks a conforming <code class="computeroutput">std::messages</code>
- facet.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_NO_STD_MIN_MAX</code>
+ 
 </td>
<td>
- 
- Standard library
- 
+ 
+ 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>.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_NO_STD_OUTPUT_ITERATOR_ASSIGN</code>
+ 
 </td>
<td>
- 
- Standard library
- 
+ 
+ Standard library
+ 
 </td>
<td>
- 
- Defined if the standard library's output iterators are not assignable.
- 
+ 
+ Defined if the standard library's output iterators are not assignable.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_STD_TYPEINFO</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_STD_TYPEINFO</code>
+ 
 </td>
<td>
- 
- Standard library
- 
+ 
+ Standard library
+ 
 </td>
<td>
- 
- The <typeinfo> header declares <code class="computeroutput">type_info</code>
- in the global namespace instead of namespace std.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_NO_STD_USE_FACET</code>
+ 
 </td>
<td>
- 
- Standard library
- 
+ 
+ Standard library
+ 
 </td>
<td>
- 
- The standard library lacks a conforming <code class="computeroutput">std::use_facet</code>.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_NO_STD_WSTREAMBUF</code>
+ 
 </td>
<td>
- 
- Standard library
- 
+ 
+ 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.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_NO_STD_WSTRING</code>
+ 
 </td>
<td>
- 
- Standard library
- 
+ 
+ Standard library
+ 
 </td>
<td>
- 
- The standard library lacks <code class="computeroutput">std::wstring</code>.
- 
+ 
+ The standard library lacks <code class="computeroutput">std::wstring</code>.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_STDC_NAMESPACE</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_STDC_NAMESPACE</code>
+ 
 </td>
<td>
- 
- Compiler, Platform
- 
+ 
+ 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...
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_NO_STRINGSTREAM</code>
+ 
 </td>
<td>
- 
- Standard library
- 
+ 
+ Standard library
+ 
 </td>
<td>
- 
- The C++ implementation does not provide the <code class="computeroutput"><sstream></code>
- header.
- 
+ 
+ The C++ implementation does not provide the <code class="computeroutput"><sstream></code>
+ header.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_SWPRINTF</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_SWPRINTF</code>
+ 
 </td>
<td>
- 
- Platform
- 
+ 
+ Platform
+ 
 </td>
<td>
- 
- The platform does not have a conforming version of <code class="computeroutput">swprintf</code>.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_NO_TEMPLATE_PARTIAL_SPECIALIZATION</code>
+ 
 </td>
<td>
- 
- Compiler
- 
+ 
+ Compiler
+ 
 </td>
<td>
- 
- Class template partial specialization (14.5.4 [temp.class.spec])
- not supported.
- 
+ 
+ Class template partial specialization (14.5.4 [temp.class.spec])
+ not supported.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_TEMPLATED_IOSTREAMS</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_TEMPLATED_IOSTREAMS</code>
+ 
 </td>
<td>
- 
- Standard library
- 
+ 
+ Standard library
+ 
 </td>
<td>
- 
- The standard library does not provide templated iostream classes.
- 
+ 
+ The standard library does not provide templated iostream classes.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_TEMPLATED_ITERATOR_CONSTRUCTORS</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_TEMPLATED_ITERATOR_CONSTRUCTORS</code>
+ 
 </td>
<td>
- 
- Standard library
- 
+ 
+ Standard library
+ 
 </td>
<td>
- 
- The standard library does not provide templated iterator constructors
- for its containers.
- 
+ 
+ The standard library does not provide templated iterator constructors
+ for its containers.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_TEMPLATE_TEMPLATES</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_TEMPLATE_TEMPLATES</code>
+ 
 </td>
<td>
- 
- Compiler
- 
+ 
+ Compiler
+ 
 </td>
<td>
- 
- The compiler does not support template template parameters.
- 
+ 
+ The compiler does not support template template parameters.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_TYPEID</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_TYPEID</code>
+ 
 </td>
<td>
- 
- Compiler
- 
+ 
+ Compiler
+ 
 </td>
<td>
- 
- The compiler does not support the typeid operator at all.
- 
+ 
+ The compiler does not support the typeid operator at all.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_TYPENAME_WITH_CTOR</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_TYPENAME_WITH_CTOR</code>
+ 
 </td>
<td>
- 
- Compiler
- 
+ 
+ Compiler
+ 
 </td>
<td>
- 
- The typename keyword cannot be used when creating a temporary of
- a Dependent type.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_NO_UNREACHABLE_RETURN_DETECTION</code>
+ 
 </td>
<td>
- 
- Compiler
- 
+ 
+ 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.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_NO_USING_DECLARATION_OVERLOADS_FROM_TYPENAME_BASE</code>
+ 
 </td>
<td>
- 
- Compiler
- 
+ 
+ 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.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_NO_USING_TEMPLATE</code>
+ 
 </td>
<td>
- 
- Compiler
- 
+ 
+ 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).
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_NO_VOID_RETURNS</code>
+ 
 </td>
<td>
- 
- Compiler
- 
+ 
+ Compiler
+ 
 </td>
<td>
- 
- The compiler does not allow a void function to return the result
- of calling another void function.
+ 
+ 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>
@@ -1292,7 +1291,7 @@
</div>
<a name="config_features"></a>
 
-<div class="section" lang="en">
+<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 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>
@@ -1309,881 +1308,882 @@
</colgroup>
<thead><tr>
<th>
- 
- Macro
- 
+ 
+ Macro
+ 
 </th>
<th>
- 
- Section
- 
+ 
+ Section
+ 
 </th>
<th>
- 
- Description
- 
+ 
+ Description
+ 
 </th>
</tr></thead>
<tbody>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_HAS_BETHREADS</code>
- 
+ 
+ <code class="computeroutput">BOOST_HAS_BETHREADS</code>
+ 
 </td>
<td>
- 
- Platform
- 
+ 
+ Platform
+ 
 </td>
<td>
- 
- The platform supports BeOS style threads.
- 
+ 
+ The platform supports BeOS style threads.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_HAS_CLOCK_GETTIME</code>
- 
+ 
+ <code class="computeroutput">BOOST_HAS_CLOCK_GETTIME</code>
+ 
 </td>
<td>
- 
- Platform
- 
+ 
+ Platform
+ 
 </td>
<td>
- 
- The platform has the POSIX API <code class="computeroutput">clock_gettime</code>.
- 
+ 
+ The platform has the POSIX API <code class="computeroutput">clock_gettime</code>.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_HAS_DIRENT_H</code>
- 
+ 
+ <code class="computeroutput">BOOST_HAS_DIRENT_H</code>
+ 
 </td>
<td>
- 
- Platform
- 
+ 
+ Platform
+ 
 </td>
<td>
- 
- The platform has the POSIX header <code class="computeroutput"><dirent.h></code>.
- 
+ 
+ The platform has the POSIX header <code class="computeroutput"><dirent.h></code>.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_HAS_EXPM1</code>
- 
+ 
+ <code class="computeroutput">BOOST_HAS_EXPM1</code>
+ 
 </td>
<td>
- 
- Platform
- 
+ 
+ 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>
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_HAS_FTIME</code>
+ 
 </td>
<td>
- 
- Platform
- 
+ 
+ Platform
+ 
 </td>
<td>
- 
- The platform has the Win32 API <code class="computeroutput">GetSystemTimeAsFileTime</code>.
- 
+ 
+ The platform has the Win32 API <code class="computeroutput">GetSystemTimeAsFileTime</code>.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_HAS_GETTIMEOFDAY</code>
- 
+ 
+ <code class="computeroutput">BOOST_HAS_GETTIMEOFDAY</code>
+ 
 </td>
<td>
- 
- Platform
- 
+ 
+ Platform
+ 
 </td>
<td>
- 
- The platform has the POSIX API <code class="computeroutput">gettimeofday</code>.
- 
+ 
+ The platform has the POSIX API <code class="computeroutput">gettimeofday</code>.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_HAS_HASH</code>
- 
+ 
+ <code class="computeroutput">BOOST_HAS_HASH</code>
+ 
 </td>
<td>
- 
- Standard library
- 
+ 
+ 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.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_HAS_LOG1P</code>
+ 
 </td>
<td>
- 
- Platform
- 
+ 
+ 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>.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_HAS_MACRO_USE_FACET</code>
+ 
 </td>
<td>
- 
- Standard library
- 
+ 
+ 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.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_HAS_MS_INT64</code>
+ 
 </td>
<td>
- 
- Compiler
- 
+ 
+ Compiler
+ 
 </td>
<td>
- 
- The compiler supports the <code class="computeroutput">__int64</code>
- data type.
- 
+ 
+ The compiler supports the <code class="computeroutput">__int64</code>
+ data type.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_HAS_NANOSLEEP</code>
- 
+ 
+ <code class="computeroutput">BOOST_HAS_NANOSLEEP</code>
+ 
 </td>
<td>
- 
- Platform
- 
+ 
+ Platform
+ 
 </td>
<td>
- 
- The platform has the POSIX API nanosleep.
- 
+ 
+ The platform has the POSIX API nanosleep.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_HAS_NL_TYPES_H</code>
- 
+ 
+ <code class="computeroutput">BOOST_HAS_NL_TYPES_H</code>
+ 
 </td>
<td>
- 
- Platform
- 
+ 
+ Platform
+ 
 </td>
<td>
- 
- The platform has an <code class="computeroutput"><nl_types.h></code>.
- 
+ 
+ The platform has an <code class="computeroutput"><nl_types.h></code>.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_HAS_NRVO</code>
- 
+ 
+ <code class="computeroutput">BOOST_HAS_NRVO</code>
+ 
 </td>
<td>
- 
- Compiler
- 
+ 
+ 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.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_HAS_PARTIAL_STD_ALLOCATOR</code>
+ 
 </td>
<td>
- 
- Standard Library
- 
+ 
+ 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.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_HAS_PTHREAD_DELAY_NP</code>
+ 
 </td>
<td>
- 
- Platform
- 
+ 
+ Platform
+ 
 </td>
<td>
- 
- The platform has the POSIX API <code class="computeroutput">pthread_delay_np</code>.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_HAS_PTHREAD_MUTEXATTR_SETTYPE</code>
+ 
 </td>
<td>
- 
- Platform
- 
+ 
+ Platform
+ 
 </td>
<td>
- 
- The platform has the POSIX API <code class="computeroutput">pthread_mutexattr_settype</code>.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_HAS_PTHREAD_YIELD</code>
+ 
 </td>
<td>
- 
- Platform
- 
+ 
+ Platform
+ 
 </td>
<td>
- 
- The platform has the POSIX API <code class="computeroutput">pthread_yield</code>.
- 
+ 
+ The platform has the POSIX API <code class="computeroutput">pthread_yield</code>.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_HAS_PTHREADS</code>
- 
+ 
+ <code class="computeroutput">BOOST_HAS_PTHREADS</code>
+ 
 </td>
<td>
- 
- Platform
- 
+ 
+ Platform
+ 
 </td>
<td>
- 
- The platform support POSIX style threads.
- 
+ 
+ The platform support POSIX style threads.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_HAS_SCHED_YIELD</code>
- 
+ 
+ <code class="computeroutput">BOOST_HAS_SCHED_YIELD</code>
+ 
 </td>
<td>
- 
- Platform
- 
+ 
+ Platform
+ 
 </td>
<td>
- 
- The platform has the POSIX API <code class="computeroutput">sched_yield</code>.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_HAS_SGI_TYPE_TRAITS</code>
+ 
 </td>
<td>
- 
- Compiler, Standard library
- 
+ 
+ Compiler, Standard library
+ 
 </td>
<td>
- 
- The compiler has native support for SGI style type traits.
- 
+ 
+ The compiler has native support for SGI style type traits.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_HAS_STDINT_H</code>
- 
+ 
+ <code class="computeroutput">BOOST_HAS_STDINT_H</code>
+ 
 </td>
<td>
- 
- Platform
- 
+ 
+ Platform
+ 
 </td>
<td>
- 
- The platform has a <code class="computeroutput"><stdint.h></code>
- 
+ 
+ The platform has a <code class="computeroutput"><stdint.h></code>
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_HAS_SLIST</code>
- 
+ 
+ <code class="computeroutput">BOOST_HAS_SLIST</code>
+ 
 </td>
<td>
- 
- Standard library
- 
+ 
+ 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.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_HAS_STLP_USE_FACET</code>
+ 
 </td>
<td>
- 
- Standard library
- 
+ 
+ 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.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_HAS_TR1_ARRAY</code>
+ 
 </td>
<td>
- 
- Standard library
- 
+ 
+ Standard library
+ 
 </td>
<td>
- 
- The library has a TR1 conforming version of <code class="computeroutput"><array></code>.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_HAS_TR1_COMPLEX_OVERLOADS</code>
+ 
 </td>
<td>
- 
- Standard library
- 
+ 
+ Standard library
+ 
 </td>
<td>
- 
- The library has a version of <code class="computeroutput"><complex></code>
- that supports passing scalars to the complex number algorithms.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_HAS_TR1_COMPLEX_INVERSE_TRIG</code>
+ 
 </td>
<td>
- 
- Standard library
- 
+ 
+ Standard library
+ 
 </td>
<td>
- 
- The library has a version of <code class="computeroutput"><complex></code>
- that includes the new inverse trig functions from TR1.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_HAS_TR1_REFERENCE_WRAPPER</code>
+ 
 </td>
<td>
- 
- Standard library
- 
+ 
+ Standard library
+ 
 </td>
<td>
- 
- The library has TR1 conforming reference wrappers in <code class="computeroutput"><functional></code>.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_HAS_TR1_RESULT_OF</code>
+ 
 </td>
<td>
- 
- Standard library
- 
+ 
+ Standard library
+ 
 </td>
<td>
- 
- The library has a TR1 conforming result_of template in <code class="computeroutput"><functional></code>.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_HAS_TR1_MEM_FN</code>
+ 
 </td>
<td>
- 
- Standard library
- 
+ 
+ Standard library
+ 
 </td>
<td>
- 
- The library has a TR1 conforming mem_fn function template in <code class="computeroutput"><functional></code>.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_HAS_TR1_BIND</code>
+ 
 </td>
<td>
- 
- Standard library
- 
+ 
+ Standard library
+ 
 </td>
<td>
- 
- The library has a TR1 conforming bind function template in <code class="computeroutput"><functional></code>.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_HAS_TR1_FUNCTION</code>
+ 
 </td>
<td>
- 
- Standard library
- 
+ 
+ Standard library
+ 
 </td>
<td>
- 
- The library has a TR1 conforming function class template in <code class="computeroutput"><functional></code>.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_HAS_TR1_HASH</code>
+ 
 </td>
<td>
- 
- Standard library
- 
+ 
+ Standard library
+ 
 </td>
<td>
- 
- The library has a TR1 conforming hash function template in <code class="computeroutput"><functional></code>.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_HAS_TR1_SHARED_PTR</code>
+ 
 </td>
<td>
- 
- Standard library
- 
+ 
+ Standard library
+ 
 </td>
<td>
- 
- The library has a TR1 conforming <code class="computeroutput">shared_ptr</code>
- class template in <code class="computeroutput"><memory></code>.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_HAS_TR1_RANDOM</code>
+ 
 </td>
<td>
- 
- Standard library
- 
+ 
+ Standard library
+ 
 </td>
<td>
- 
- The library has a TR1 conforming version of <code class="computeroutput"><random></code>.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_HAS_TR1_REGEX</code>
+ 
 </td>
<td>
- 
- Standard library
- 
+ 
+ Standard library
+ 
 </td>
<td>
- 
- The library has a TR1 conforming version of <code class="computeroutput"><regex></code>.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_HAS_TR1_TUPLE</code>
+ 
 </td>
<td>
- 
- Standard library
- 
+ 
+ Standard library
+ 
 </td>
<td>
- 
- The library has a TR1 conforming version of <code class="computeroutput"><tuple></code>.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_HAS_TR1_TYPE_TRAITS</code>
+ 
 </td>
<td>
- 
- Standard library
- 
+ 
+ Standard library
+ 
 </td>
<td>
- 
- The library has a TR1 conforming version of <code class="computeroutput"><type_traits></code>.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_HAS_TR1_UTILITY</code>
+ 
 </td>
<td>
- 
- Standard library
- 
+ 
+ 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>).
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_HAS_TR1_UNORDERED_MAP</code>
+ 
 </td>
<td>
- 
- Standard library
- 
+ 
+ Standard library
+ 
 </td>
<td>
- 
- The library has a TR1 conforming version of <code class="computeroutput"><unordered_map></code>.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_HAS_TR1_UNORDERED_SET</code>
+ 
 </td>
<td>
- 
- Standard library
- 
+ 
+ Standard library
+ 
 </td>
<td>
- 
- The library has a TR1 conforming version of <code class="computeroutput"><unordered_set></code>.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_HAS_TR1</code>
+ 
 </td>
<td>
- 
- Standard library
- 
+ 
+ Standard library
+ 
 </td>
<td>
- 
- Implies all the other <code class="computeroutput">BOOST_HAS_TR1_*</code> macros should be set.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_HAS_THREADS</code>
+ 
 </td>
<td>
- 
- Platform, Compiler
- 
+ 
+ Platform, Compiler
+ 
 </td>
<td>
- 
- Defined if the compiler, in its current translation mode, supports
- multiple threads of execution.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_HAS_TWO_ARG_USE_FACET</code>
+ 
 </td>
<td>
- 
- Standard library
- 
+ 
+ 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.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_HAS_UNISTD_H</code>
+ 
 </td>
<td>
- 
- Platform
- 
+ 
+ Platform
+ 
 </td>
<td>
- 
- The Platform provides <code class="computeroutput"><unistd.h></code>.
- 
+ 
+ The Platform provides <code class="computeroutput"><unistd.h></code>.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_HAS_WINTHREADS</code>
- 
+ 
+ <code class="computeroutput">BOOST_HAS_WINTHREADS</code>
+ 
 </td>
<td>
- 
- Platform
- 
+ 
+ Platform
+ 
 </td>
<td>
- 
- The platform supports MS Windows style threads.
- 
+ 
+ The platform supports MS Windows style threads.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_MSVC_STD_ITERATOR</code>
- 
+ 
+ <code class="computeroutput">BOOST_MSVC_STD_ITERATOR</code>
+ 
 </td>
<td>
- 
- Standard library
- 
+ 
+ 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.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_MSVC6_MEMBER_TEMPLATES</code>
+ 
 </td>
<td>
- 
- Compiler
- 
+ 
+ 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.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_HAS_STDINT_H</code>
+ 
 </td>
<td>
- 
- Platform
- 
+ 
+ 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).
- 
+ 
+ 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" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="boost_config.boost_macro_reference.macros_that_describe_possible_c__0x_features"></a><a class="link" href="boost_macro_reference.html#boost_config.boost_macro_reference.macros_that_describe_possible_c__0x_features" title="Macros that describe possible C++0x features">Macros
 that describe possible C++0x features</a>
@@ -2200,31 +2200,31 @@
</colgroup>
<thead><tr>
<th>
- 
- Macro
- 
+ 
+ Macro
+ 
 </th>
<th>
- 
- Description
- 
+ 
+ Description
+ 
 </th>
</tr></thead>
<tbody><tr>
<td>
- 
- <code class="computeroutput">BOOST_HAS_CONCEPTS</code>
- 
+ 
+ <code class="computeroutput">BOOST_HAS_CONCEPTS</code>
+ 
 </td>
<td>
- 
- The compiler supports concepts.
- 
+ 
+ The compiler supports concepts.
+ 
 </td>
</tr></tbody>
</table></div>
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="boost_config.boost_macro_reference.macros_that_describe_c__0x_features_not_supported"></a><a class="link" href="boost_macro_reference.html#boost_config.boost_macro_reference.macros_that_describe_c__0x_features_not_supported" title="Macros that describe C++0x features not supported">Macros
 that describe C++0x features not supported</a>
@@ -2240,594 +2240,595 @@
</colgroup>
<thead><tr>
<th>
- 
- Macro
- 
+ 
+ Macro
+ 
 </th>
<th>
- 
- Description
- 
+ 
+ Description
+ 
 </th>
</tr></thead>
<tbody>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_0X_HDR_ARRAY</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_0X_HDR_ARRAY</code>
+ 
 </td>
<td>
- 
- The standard library does not provide header <array>.
- 
+ 
+ The standard library does not provide header <array>.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_0X_HDR_CHRONO</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_0X_HDR_CHRONO</code>
+ 
 </td>
<td>
- 
- The standard library does not provide header <chrono>.
- 
+ 
+ The standard library does not provide header <chrono>.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_0X_HDR_CODECVT</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_0X_HDR_CODECVT</code>
+ 
 </td>
<td>
- 
- The standard library does not provide header <codecvt>.
- 
+ 
+ The standard library does not provide header <codecvt>.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_0X_HDR_CONCEPTS</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_0X_HDR_CONCEPTS</code>
+ 
 </td>
<td>
- 
- The standard library does not provide header <concepts>.
- 
+ 
+ The standard library does not provide header <concepts>.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_0X_HDR_CONDITION_VARIABLE</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_0X_HDR_CONDITION_VARIABLE</code>
+ 
 </td>
<td>
- 
- The standard library does not provide header <condition_variable>.
- 
+ 
+ The standard library does not provide header <condition_variable>.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_0X_HDR_CONTAINER_CONCEPTS</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_0X_HDR_CONTAINER_CONCEPTS</code>
+ 
 </td>
<td>
- 
- The standard library does not provide header <container_concepts>.
- 
+ 
+ The standard library does not provide header <container_concepts>.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_0X_HDR_FORWARD_LIST</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_0X_HDR_FORWARD_LIST</code>
+ 
 </td>
<td>
- 
- The standard library does not provide header <forward_list>.
- 
+ 
+ The standard library does not provide header <forward_list>.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_0X_HDR_FUTURE</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_0X_HDR_FUTURE</code>
+ 
 </td>
<td>
- 
- The standard library does not provide header <future>.
- 
+ 
+ The standard library does not provide header <future>.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_0X_HDR_INITIALIZER_LIST</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_0X_HDR_INITIALIZER_LIST</code>
+ 
 </td>
<td>
- 
- The standard library does not provide header <initializer_list>.
- 
+ 
+ The standard library does not provide header <initializer_list>.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_0X_HDR_ITERATOR_CONCEPTS</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_0X_HDR_ITERATOR_CONCEPTS</code>
+ 
 </td>
<td>
- 
- The standard library does not provide header <iterator_concepts>.
- 
+ 
+ The standard library does not provide header <iterator_concepts>.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_0X_HDR_MEMORY_CONCEPTS</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_0X_HDR_MEMORY_CONCEPTS</code>
+ 
 </td>
<td>
- 
- The standard library does not provide header <memory_concepts>.
- 
+ 
+ The standard library does not provide header <memory_concepts>.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_0X_HDR_MUTEX</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_0X_HDR_MUTEX</code>
+ 
 </td>
<td>
- 
- The standard library does not provide header <mutex>.
- 
+ 
+ The standard library does not provide header <mutex>.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_0X_HDR_RANDOM</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_0X_HDR_RANDOM</code>
+ 
 </td>
<td>
- 
- The standard library does not provide header <random>.
- 
+ 
+ The standard library does not provide header <random>.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_0X_HDR_RATIO</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_0X_HDR_RATIO</code>
+ 
 </td>
<td>
- 
- The standard library does not provide header <ratio>.
- 
+ 
+ The standard library does not provide header <ratio>.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_0X_HDR_REGEX</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_0X_HDR_REGEX</code>
+ 
 </td>
<td>
- 
- The standard library does not provide header <regex>.
- 
+ 
+ The standard library does not provide header <regex>.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_0X_HDR_SYSTEM_ERROR</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_0X_HDR_SYSTEM_ERROR</code>
+ 
 </td>
<td>
- 
- The standard library does not provide header <system_error>.
- 
+ 
+ The standard library does not provide header <system_error>.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_0X_HDR_THREAD</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_0X_HDR_THREAD</code>
+ 
 </td>
<td>
- 
- The standard library does not provide header <thread>.
- 
+ 
+ The standard library does not provide header <thread>.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_0X_HDR_TUPLE</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_0X_HDR_TUPLE</code>
+ 
 </td>
<td>
- 
- The standard library does not provide header <tuple>.
- 
+ 
+ The standard library does not provide header <tuple>.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_0X_HDR_TYPEINDEX</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_0X_HDR_TYPEINDEX</code>
+ 
 </td>
<td>
- 
- The standard library does not provide header <typeindex>.
- 
+ 
+ The standard library does not provide header <typeindex>.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_0X_HDR_TYPE_TRAITS</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_0X_HDR_TYPE_TRAITS</code>
+ 
 </td>
<td>
- 
- The standard library does not provide header <type_traits>.
- 
+ 
+ The standard library does not provide header <type_traits>.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_0X_HDR_UNORDERED_MAP</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_0X_HDR_UNORDERED_MAP</code>
+ 
 </td>
<td>
- 
- The standard library does not provide header <unordered_map>.
- 
+ 
+ The standard library does not provide header <unordered_map>.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_0X_HDR_UNORDERED_SET</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_0X_HDR_UNORDERED_SET</code>
+ 
 </td>
<td>
- 
- The standard library does not provide header <unordered_set>.
- 
+ 
+ The standard library does not provide header <unordered_set>.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_AUTO_DECLARATIONS</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_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>).
- 
+ 
+ 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_AUTO_MULTIDECLARATIONS</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_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>).
- 
+ 
+ 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_CHAR16_T</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_CHAR16_T</code>
+ 
 </td>
<td>
- 
- The compiler does not support type <code class="computeroutput">char16_t</code>.
- 
+ 
+ The compiler does not support type <code class="computeroutput">char16_t</code>.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_CHAR32_T</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_CHAR32_T</code>
+ 
 </td>
<td>
- 
- The compiler does not support type <code class="computeroutput">char32_t</code>.
- 
+ 
+ The compiler does not support type <code class="computeroutput">char32_t</code>.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_CONCEPTS</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_CONCEPTS</code>
+ 
 </td>
<td>
- 
- The compiler does not support Concepts.
- 
+ 
+ The compiler does not support Concepts.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_TEMPLATE_ALIASES</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_TEMPLATE_ALIASES</code>
+ 
 </td>
<td>
- 
- The compiler does not support template aliases.
- 
+ 
+ The compiler does not support template aliases.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_CONSTEXPR</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_CONSTEXPR</code>
+ 
 </td>
<td>
- 
- The compiler does not support <code class="computeroutput">constexpr</code>.
- 
+ 
+ The compiler does not support <code class="computeroutput">constexpr</code>.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_DECLTYPE</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_DECLTYPE</code>
+ 
 </td>
<td>
- 
- The compiler does not support <code class="computeroutput">decltype</code>.
- 
+ 
+ The compiler does not support <code class="computeroutput">decltype</code>.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_DEFAULTED_FUNCTIONS</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_DEFAULTED_FUNCTIONS</code>
+ 
 </td>
<td>
- 
- The compiler does not support defaulted (<code class="computeroutput">=
- default</code>) functions.
- 
+ 
+ The compiler does not support defaulted (<code class="computeroutput">=
+ default</code>) functions.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_DELETED_FUNCTIONS</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_DELETED_FUNCTIONS</code>
+ 
 </td>
<td>
- 
- The compiler does not support deleted (<code class="computeroutput">=
- delete</code>) functions.
- 
+ 
+ The compiler does not support deleted (<code class="computeroutput">=
+ delete</code>) functions.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_EXPLICIT_CONVERSION_OPERATORS</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_EXPLICIT_CONVERSION_OPERATORS</code>
+ 
 </td>
<td>
- 
- The compiler does not support explicit conversion operators (<code class="computeroutput">explicit operator
- T()</code>).
- 
+ 
+ The compiler does not support explicit conversion operators (<code class="computeroutput">explicit operator
+ T()</code>).
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_EXTERN_TEMPLATE</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_EXTERN_TEMPLATE</code>
+ 
 </td>
<td>
- 
- The compiler does not support explicit instantiation forward declarations
- for templates (<code class="computeroutput">extern template ...</code>).
- 
+ 
+ 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_FUNCTION_TEMPLATE_DEFAULT_ARGS</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_FUNCTION_TEMPLATE_DEFAULT_ARGS</code>
+ 
 </td>
<td>
- 
- The compiler does not support default template arguments for function
- templates.
- 
+ 
+ The compiler does not support default template arguments for function
+ templates.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_INITIALIZER_LISTS</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_INITIALIZER_LISTS</code>
+ 
 </td>
<td>
- 
- The C++ compiler does not support C++0x initializer lists.
- 
+ 
+ The C++ compiler does not support C++0x initializer lists.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_LAMBDAS</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_LAMBDAS</code>
+ 
 </td>
<td>
- 
- The compiler does not support Lambdas.
- 
+ 
+ The compiler does not support Lambdas.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_LONG_LONG</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_LONG_LONG</code>
+ 
 </td>
<td>
- 
- The compiler does not support <code class="computeroutput">long
- long</code>.
- 
+ 
+ The compiler does not support <code class="computeroutput">long
+ long</code>.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_NULLPTR</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_NULLPTR</code>
+ 
 </td>
<td>
- 
- The compiler does not support 'nullptr'.
- 
+ 
+ The compiler does not support 'nullptr'.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_RAW_LITERALS</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_RAW_LITERALS</code>
+ 
 </td>
<td>
- 
- The compiler does not support raw string literals.
- 
+ 
+ The compiler does not support raw string literals.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_RVALUE_REFERENCES</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_RVALUE_REFERENCES</code>
+ 
 </td>
<td>
- 
- The compiler does not support r-value references.
- 
+ 
+ The compiler does not support r-value references.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_SCOPED_ENUMS</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_SCOPED_ENUMS</code>
+ 
 </td>
<td>
- 
- The compiler does not support scoped enumerations (<code class="computeroutput">enum class</code>).
- 
+ 
+ The compiler does not support scoped enumerations (<code class="computeroutput">enum class</code>).
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_STATIC_ASSERT</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_STATIC_ASSERT</code>
+ 
 </td>
<td>
- 
- The compiler does not support <code class="computeroutput">static_assert</code>.
- 
+ 
+ The compiler does not support <code class="computeroutput">static_assert</code>.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_STD_UNORDERD</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_STD_UNORDERD</code>
+ 
 </td>
<td>
- 
- The standard library does not support <unordered_map> and <unordered_set>.
- 
+ 
+ The standard library does not support <unordered_map> and
+ <unordered_set>.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_TEMPLATE_ALIASES</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_TEMPLATE_ALIASES</code>
+ 
 </td>
<td>
- 
- The compiler does not support template aliases.
- 
+ 
+ The compiler does not support template aliases.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_NO_UNICODE_LITERALS</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_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.
- 
+ 
+ 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_VARIADIC_TEMPLATES</code>
- 
+ 
+ <code class="computeroutput">BOOST_NO_VARIADIC_TEMPLATES</code>
+ 
 </td>
<td>
- 
- The compiler does not support variadic templates.
- 
+ 
+ The compiler does not support variadic templates.
+ 
 </td>
</tr>
</tbody>
@@ -2835,7 +2836,7 @@
</div>
<a name="config_helpers"></a>
 
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="boost_config.boost_macro_reference.boost_helper_macros"></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>
@@ -2851,33 +2852,33 @@
</colgroup>
<thead><tr>
<th>
- 
- Macro
- 
+ 
+ Macro
+ 
 </th>
<th>
- 
- Description
- 
+ 
+ Description
+ 
 </th>
</tr></thead>
<tbody>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_WORKAROUND</code>
- 
+ 
+ <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
+ 
+ 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:
+ 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...
@@ -2886,157 +2887,157 @@
#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.
- 
+ 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_DEDUCED_TYPENAME</code>
- 
+ 
+ <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>
- 
+ 
+ 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>
- 
+ 
+ <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.
- 
+ 
+ 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>
- 
+ 
+ <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.
- 
+ 
+ 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>
- 
+ 
+ <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.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_STD_EXTENSION_NAMESPACE</code>
+ 
 </td>
<td>
- 
- The namespace used for std library extensions (hashtable classes
- etc).
- 
+ 
+ The namespace used for std library extensions (hashtable classes
+ etc).
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_STATIC_CONSTANT(Type, assignment)</code>
- 
+ 
+ <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:
+ 
+ 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:
+ 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>
- 
+ 
+ <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.
- 
+ 
+ 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>
- 
+ 
+ <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:
+ 
+ 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>
@@ -3057,10 +3058,10 @@
}
</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:
+ 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)) { ... }
@@ -3069,105 +3070,105 @@
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.
- 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_USE_FACET(Type, loc)</code>
+ 
 </td>
<td>
- 
- When the standard library does not have a comforming <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>.
- 
+ 
+ When the standard library does not have a comforming <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>
- 
+ 
+ <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>.
- 
+ 
+ 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>
- 
+ 
+ <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>
- 
+ 
+ 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>
- 
+ 
+ <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.
- 
+ 
+ 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>
- 
+ 
+ <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__.
- 
+ 
+ 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>
</tbody>
@@ -3175,7 +3176,7 @@
</div>
<a name="config_info_macros"></a>
 
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="boost_config.boost_macro_reference.boost_informational_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>
@@ -3192,267 +3193,268 @@
</colgroup>
<thead><tr>
<th>
- 
- Macro
- 
+ 
+ Macro
+ 
 </th>
<th>
- 
- Header
- 
+ 
+ Header
+ 
 </th>
<th>
- 
- Description
- 
+ 
+ Description
+ 
 </th>
</tr></thead>
<tbody>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_VERSION</code>
- 
+ 
+ <code class="computeroutput">BOOST_VERSION</code>
+ 
 </td>
<td>
- 
- <code class="computeroutput"><boost/version.hpp></code>
- 
+ 
+ <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.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_NO_INT64_T</code>
+ 
 </td>
<td>
- 
- <code class="computeroutput"><boost/cstdint.hpp></code> <code class="computeroutput"><boost/stdint.h></code>
- 
+ 
+ <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.
- 
+ 
+ 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>
- 
+ 
+ <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>
- 
+ 
+ <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.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_MSVC</code>
+ 
 </td>
<td>
- 
- <code class="computeroutput"><boost/config.hpp></code>
- 
+ 
+ <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.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_MSVC_FULL_VER</code>
+ 
 </td>
<td>
- 
- <code class="computeroutput"><boost/config.hpp></code>
- 
+ 
+ <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.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_INTEL</code>
+ 
 </td>
<td>
- 
- <code class="computeroutput"><boost/config.hpp></code>
- 
+ 
+ <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.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_CLANG</code>
+ 
 </td>
<td>
- 
- <code class="computeroutput"><boost/config.hpp></code>
- 
+ 
+ <code class="computeroutput"><boost/config.hpp></code>
+ 
 </td>
<td>
- 
- Defined to 1 if the compiler is the Clang compiler.
- 
+ 
+ Defined to 1 if the compiler is the Clang compiler.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_WINDOWS</code>
- 
+ 
+ <code class="computeroutput">BOOST_WINDOWS</code>
+ 
 </td>
<td>
- 
- <code class="computeroutput"><boost/config.hpp></code>
- 
+ 
+ <code class="computeroutput"><boost/config.hpp></code>
+ 
 </td>
<td>
- 
- Defined if the Windows platfrom API is available.
- 
+ 
+ Defined if the Windows platfrom API is available.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_DINKUMWARE_STDLIB</code>
- 
+ 
+ <code class="computeroutput">BOOST_DINKUMWARE_STDLIB</code>
+ 
 </td>
<td>
- 
- <code class="computeroutput"><boost/config.hpp></code>
- 
+ 
+ <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.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_NO_WREGEX</code>
+ 
 </td>
<td>
- 
- <code class="computeroutput"><boost/regex.hpp></code>
- 
+ 
+ <code class="computeroutput"><boost/regex.hpp></code>
+ 
 </td>
<td>
- 
- Defined if the regex library does not support wide character regular
- expressions.
- 
+ 
+ Defined if the regex library does not support wide character regular
+ expressions.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_COMPILER</code>
- 
+ 
+ <code class="computeroutput">BOOST_COMPILER</code>
+ 
 </td>
<td>
- 
- <code class="computeroutput"><boost/config.hpp></code>
- 
+ 
+ <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.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_STDLIB</code>
+ 
 </td>
<td>
- 
- <code class="computeroutput"><boost/config.hpp></code>
- 
+ 
+ <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.
- 
+ 
+ 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>
- 
+ 
+ <code class="computeroutput">BOOST_PLATFORM</code>
+ 
 </td>
<td>
- 
- <code class="computeroutput"><boost/config.hpp></code>
- 
+ 
+ <code class="computeroutput"><boost/config.hpp></code>
+ 
 </td>
<td>
- 
- Defined as a string describing the name of the platform. Mainly for
- debugging the configuration.
- 
+ 
+ Defined as a string describing the name of the platform. Mainly
+ for debugging the configuration.
+ 
 </td>
</tr>
</tbody>
</table></div>
</div>
-<div class="section" lang="en">
+<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>
@@ -3469,23 +3471,23 @@
 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 type="disc">
-<li>
- Controlling shared library symbol visibility
- </li>
-<li>
- Fixing the ABI of the compiled library
- </li>
-<li>
- Selecting which compiled library to link against based upon the compilers
- settings
- </li>
+<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" lang="en">
+<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>
@@ -3515,85 +3517,86 @@
</colgroup>
<thead><tr>
<th>
- 
- Macro
- 
+ 
+ Macro
+ 
 </th>
<th>
- 
- Description
- 
+ 
+ Description
+ 
 </th>
</tr></thead>
<tbody>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_SYMBOL_EXPORT</code>
- 
+ 
+ <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.
- 
+ 
+ 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>
- 
+ 
+ <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.
- 
+ 
+ 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>
- 
+ 
+ <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:
+ 
+ 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.
- 
+ 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>
- 
+ 
+ <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.
- 
+ 
+ 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>
@@ -3639,7 +3642,7 @@
...
</pre>
</div>
-<div class="section" lang="en">
+<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>
@@ -3697,7 +3700,7 @@
 to point to their own prefix/suffix headers if they so wish.
 
</div>
-<div class="section" lang="en">
+<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>
@@ -3727,18 +3730,18 @@
<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>
+ 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>
+ 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>
+ Optional: when set the header will print out the name of the library
+ selected (useful for debugging).
+ </dd>
</dl>
</div>

@@ -3790,7 +3793,7 @@
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="../index.html"><img src="../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="guidelines_for_boost_authors.html"><img src="../../../../../doc/html/images/next.png" alt="Next"></a>
+<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>

Modified: trunk/libs/config/doc/html/boost_config/guidelines_for_boost_authors.html
==============================================================================
--- trunk/libs/config/doc/html/boost_config/guidelines_for_boost_authors.html (original)
+++ trunk/libs/config/doc/html/boost_config/guidelines_for_boost_authors.html 2010-07-01 18:11:07 EDT (Thu, 01 Jul 2010)
@@ -2,8 +2,8 @@
<head>
<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Guidelines for Boost Authors</title>
-<link rel="stylesheet" href="../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<link rel="stylesheet" href="../../../../../doc/src/boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
<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">
@@ -20,9 +20,9 @@
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="boost_macro_reference.html"><img src="../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="rationale.html"><img src="../../../../../doc/html/images/next.png" alt="Next"></a>
+<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" lang="en">
+<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>
@@ -61,49 +61,49 @@

 Note that:
 
-<div class="itemizedlist"><ul type="disc">
-<li>
- 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>
- 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>
- 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>
- 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>
- 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>
- 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>
- The intent is not to disable mainstream features now well-supported by the
- majority of compilers, such as namespaces, exceptions, RTTI, or templates.
- </li>
+<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" lang="en">
+<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>
@@ -116,21 +116,21 @@

 Note that:
 
-<div class="itemizedlist"><ul type="disc">
-<li>
- 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>
- The header should be included before you
- include any other header.
- </li>
-<li>
- 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>
+<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:
@@ -142,47 +142,47 @@
</colgroup>
<thead><tr>
<th>
- 
- Compiler
- 
+ 
+ Compiler
+ 
 </th>
<th>
- 
- Warning
- 
+ 
+ Warning
+ 
 </th>
</tr></thead>
<tbody>
<tr>
<td>
- 
- Visual C++ 8 and later
- 
+ 
+ Visual C++ 8 and later
+ 
 </td>
<td>
- 
- C4996:
- Error 'function': was declared deprecated
- 
+ 
+ C4996:
+ Error 'function': was declared deprecated
+ 
 </td>
</tr>
<tr>
<td>
- 
- Intel C++
- 
+ 
+ Intel C++
+ 
 </td>
<td>
- 
- Warning 1786: relates to the use of "deprecated" standard
- library functions rather like C4996 in Visual C++.
- 
+ 
+ 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" lang="en">
+<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>
@@ -233,57 +233,59 @@
 Once the test code is in place in libs/config/test, updating the configuration
 test system proceeds as:
 
-<div class="itemizedlist"><ul type="disc">
-<li>
- 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>
- 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>
- 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>
+<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 type="disc">
-<li>
- Define the defect macro in those config headers that require it.
- </li>
-<li>
- Document the macro in this documentation (please do not forget this step!!)
- </li>
-<li>
- Commit everything.
- </li>
-<li>
- Keep an eye on the regression tests for new failures in Boost.Config caused
- by the addition.
- </li>
-<li>
- Start using the macro.
- </li>
+<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" lang="en">
+<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>
@@ -307,7 +309,7 @@
 <code class="computeroutput"><unistd.h></code>).
 
</div>
-<div class="section" lang="en">
+<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>
@@ -368,7 +370,7 @@
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="boost_macro_reference.html"><img src="../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="rationale.html"><img src="../../../../../doc/html/images/next.png" alt="Next"></a>
+<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>

Modified: trunk/libs/config/doc/html/boost_config/rationale.html
==============================================================================
--- trunk/libs/config/doc/html/boost_config/rationale.html (original)
+++ trunk/libs/config/doc/html/boost_config/rationale.html 2010-07-01 18:11:07 EDT (Thu, 01 Jul 2010)
@@ -2,8 +2,8 @@
<head>
<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Rationale</title>
-<link rel="stylesheet" href="../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<link rel="stylesheet" href="../../../../../doc/src/boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
<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">
@@ -20,9 +20,9 @@
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="guidelines_for_boost_authors.html"><img src="../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="acknowledgements.html"><img src="../../../../../doc/html/images/next.png" alt="Next"></a>
+<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" lang="en">
+<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>
@@ -39,7 +39,7 @@
 principles from the <a href="http://www.objectmentor.com/resources/articles/Principles_and_Patterns.pdf" target="_top">following
 article</a>.
 
-<div class="section" lang="en">
+<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>
@@ -56,16 +56,10 @@
 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>
+<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.
 
@@ -78,15 +72,9 @@
 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>
+<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
@@ -102,7 +90,7 @@
 code must be provided.
 
</div>
-<div class="section" lang="en">
+<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>
@@ -129,7 +117,7 @@
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="guidelines_for_boost_authors.html"><img src="../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="acknowledgements.html"><img src="../../../../../doc/html/images/next.png" alt="Next"></a>
+<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>

Modified: trunk/libs/config/doc/html/index.html
==============================================================================
--- trunk/libs/config/doc/html/index.html (original)
+++ trunk/libs/config/doc/html/index.html 2010-07-01 18:11:07 EDT (Thu, 01 Jul 2010)
@@ -2,8 +2,8 @@
<head>
<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Boost.Config</title>
-<link rel="stylesheet" href="../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<link rel="stylesheet" href="../../../../doc/src/boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
<link rel="home" href="index.html" title="Boost.Config">
<link rel="next" href="boost_config/boost_macro_reference.html" title="Boost Macro Reference">
</head>
@@ -17,8 +17,8 @@
<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/html/images/next.png" alt="Next"></a></div>
-<div class="article" lang="en">
+<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">
@@ -28,7 +28,7 @@
</h3></div></div></div>
<div>Copyright © 2001 -2007 Beman Dawes, Vesa Karvonen, John Maddock</div>
<div><div class="legalnotice">
-<a name="id873629"></a>
+<a name="id759700"></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)
 
@@ -92,7 +92,7 @@
<dt>Acknowledgements</dt>
</dl>
</div>
-<div class="section" lang="en">
+<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>
@@ -111,7 +111,7 @@
<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" lang="en">
+<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>
@@ -135,7 +135,7 @@
 and submitting a support request.
 
</div>
-<div class="section" lang="en">
+<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>
@@ -168,14 +168,14 @@
</div>
<a name="config_config_script"></a>
 
-<div class="section" lang="en">
+<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 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/html/images/important.png"></td>
+<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">
@@ -190,15 +190,9 @@
 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>
+<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
@@ -213,63 +207,63 @@
</colgroup>
<thead><tr>
<th>
- 
- Variable
- 
+ 
+ Variable
+ 
 </th>
<th>
- 
- Description
- 
+ 
+ Description
+ 
 </th>
</tr></thead>
<tbody>
<tr>
<td>
- 
- CXX
- 
+ 
+ CXX
+ 
 </td>
<td>
- 
- The name of the compiler, for example <code class="computeroutput">c++</code>.
- 
+ 
+ The name of the compiler, for example <code class="computeroutput">c++</code>.
+ 
 </td>
</tr>
<tr>
<td>
- 
- CXXFLAGS
- 
+ 
+ CXXFLAGS
+ 
 </td>
<td>
- 
- The compiler flags to use, for example <code class="computeroutput">-O2</code>.
- 
+ 
+ The compiler flags to use, for example <code class="computeroutput">-O2</code>.
+ 
 </td>
</tr>
<tr>
<td>
- 
- LDFLAGS
- 
+ 
+ LDFLAGS
+ 
 </td>
<td>
- 
- The linker flags to use, for example <code class="computeroutput">-L/mypath</code>.
- 
+ 
+ The linker flags to use, for example <code class="computeroutput">-L/mypath</code>.
+ 
 </td>
</tr>
<tr>
<td>
- 
- LIBS
- 
+ 
+ LIBS
+ 
 </td>
<td>
- 
- Any libraries to link in, for example <code class="computeroutput">-lpthread</code>.
- 
+ 
+ Any libraries to link in, for example <code class="computeroutput">-lpthread</code>.
+ 
 </td>
</tr>
</tbody>
@@ -295,30 +289,30 @@
 (located under <boost-root><code class="computeroutput">/boost/config/</code>).
 There are two ways you can use this header:
 
-<div class="itemizedlist"><ul type="disc">
-<li>
-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 cvs repository (something you will not be thanked for!).
- </li>
-<li>
-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>
+<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 cvs 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>
<a name="config_user_settable"></a>
 
-<div class="section" lang="en">
+<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 class="link" href="index.html#boost_config.configuring_boost_for_your_platform.user_settable_options" title="User settable options">User
 settable options</a>
@@ -337,352 +331,354 @@
</colgroup>
<thead><tr>
<th>
- 
- Macro
- 
+ 
+ Macro
+ 
 </th>
<th>
- 
- Description
- 
+ 
+ Description
+ 
 </th>
</tr></thead>
<tbody>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_USER_CONFIG</code>
- 
+ 
+ <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>.
- 
+ 
+ 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>
- 
+ 
+ <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>.
- 
+ 
+ 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>
- 
+ 
+ <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>.
- 
+ 
+ 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>
- 
+ 
+ <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>.
- 
+ 
+ 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>
- 
+ 
+ <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.
- 
+ 
+ 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>
- 
+ 
+ <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.
- 
+ 
+ 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>
- 
+ 
+ <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.
- 
+ 
+ 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>
- 
+ 
+ <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>.
- 
+ 
+ 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>
- 
+ 
+ <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.
- 
+ 
+ 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>
- 
+ 
+ <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.
- 
+ 
+ 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>
- 
+ 
+ <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.
- 
+ 
+ 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>
- 
+ 
+ <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".
- 
+ 
+ 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>
- 
+ 
+ <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.
- 
+ 
+ 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>
- 
+ 
+ <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.
- 
+ 
+ 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>
- 
+ 
+ <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.
- 
+ 
+ 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>
- 
+ 
+ <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.Threads for example), in these cases
- this macro has no effect.
- 
+ 
+ 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.Threads 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>
- 
+ 
+ <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.Threads for example), in these cases
- this macro is unsupported.
- 
+ 
+ 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.Threads for example), in these
+ cases this macro is unsupported.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">BOOST_ALL_NO_LIB</code>
- 
+ 
+ <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.
- 
+ 
+ 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>
- 
+ 
+ <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.
- 
+ 
+ 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>
- 
+ 
+ <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.
- 
+ 
+ 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>
- 
+ 
+ <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".
- 
+ 
+ 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" lang="en">
+<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>
@@ -726,7 +722,7 @@

 The following usage examples represent just a few of the possibilities:
 
-<div class="section" lang="en">
+<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>
@@ -758,7 +754,7 @@
 yet supported by boost.
 
</div>
-<div class="section" lang="en">
+<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>
@@ -777,7 +773,7 @@
 a dependency on two boost headers.
 
</div>
-<div class="section" lang="en">
+<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>
@@ -790,7 +786,7 @@
 
</div>
</div>
-<div class="section" lang="en">
+<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>
@@ -808,119 +804,119 @@
</colgroup>
<thead><tr>
<th>
- 
- File
- 
+ 
+ File
+ 
 </th>
<th>
- 
- Description
- 
+ 
+ Description
+ 
 </th>
</tr></thead>
<tbody>
<tr>
<td>
- 
- <code class="computeroutput">config_info.cpp</code>
- 
+ 
+ <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.
- 
+ 
+ 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>
- 
+ 
+ <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.
- 
+ 
+ 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>
- 
+ 
+ <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.
- 
+ 
+ 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>
- 
+ 
+ <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.
- 
+ 
+ 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>
- 
+ 
+ <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.
- 
+ 
+ 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>
- 
+ 
+ <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.
- 
+ 
+ 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>
- 
+ 
+ <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.
- 
+ 
+ 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>
@@ -938,16 +934,10 @@

 Alternatively you can run the configure script like this:
 
-<div class="blockquote"><blockquote class="blockquote">
-
- 
-
- <code class="computeroutput">./configure
- --enable-test</code>
- 
-
- 
-</blockquote></div>
+<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.
@@ -960,10 +950,10 @@
</div>
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
-<td align="left">Last revised: June 11, 2010 at 11:20:15 GMT</td>
+<td align="left">Last revised: June 30, 2010 at 23:58:03 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/html/images/next.png" alt="Next"></a></div>
+<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>

Date view	Thread view	Subject view	Author view

Boost-Commit list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk