diff --git a/doc/html/boost_config/acknowledgements.html b/doc/html/boost_config/acknowledgements.html index 87d6546a..95301d82 100644 --- a/doc/html/boost_config/acknowledgements.html +++ b/doc/html/boost_config/acknowledgements.html @@ -3,7 +3,7 @@
+
++
++
+
+ BOOST_CONSTEXPR
+
+ Some compilers don't support the use of constexpr
.
+ This macro expands to nothing on those compilers, and constexpr
elsewhere. For example,
+ when defining a constexpr function or constructor replace:
+
constexpr tuple(); ++
+ with: +
+BOOST_CONSTEXPR tuple(); ++
+
+
+ BOOST_CONSTEXPR_OR_CONST
+
+ Some compilers don't support the use of constexpr
.
+ This macro expands to const
+ on those compilers, and constexpr
+ elsewhere. For example, when defining const expr variables replace:
+
+
static constexpr UIntType xor_mask = a; ++
+ with: +
+static BOOST_CONSTEXPR_OR_CONST UIntType xor_mask = a; ++
+
+
+ BOOST_STATIC_CONSTEXPR
+
+ This is a shortcut for static
+ BOOST_CONSTEXPR_OR_CONST
For
+ example, when defining const expr variables replace:
+
static constexpr UIntType xor_mask = a; ++
+ with: +
+BOOST_STATIC_CONSTEXPR UIntType xor_mask = a; ++
+
++
+Note that:
-#include
<boost/config.hpp>
", and are not required in any
way to support compilers that do not comply with the C++ Standard (ISO/IEC
14882).
#include
<boost/config.hpp>
" is the preferred way to obtain
configuration information not available from the standard headers such
as <climits>
, etc.
<climits>
, use those standard headers rather
than <boost/config.hpp>
.
<boost/config.hpp>
should have sensible, standard conforming, default behavior if the macro
is not defined. This means that the starting point for porting <boost/config.hpp>
to a new platform is simply to define
@@ -88,25 +88,25 @@
is no sensible default behavior, an #error message should describe the
problem.
config.hpp
,
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.
The header <boost/config/warning_disable.hpp>
@@ -116,17 +116,17 @@
Note that:
-libs/config/tools
and run bjam
.
This generates the .cpp
file test cases from the .ipp
file, updates the libs/config/test/all/Jamfile.v2,
config_test.cpp
and config_info.cpp
.libs/config/test/all
and run bjam
MACRONAME compiler-list
,
where MACRONAME is the name of the new macro, and
@@ -253,7 +253,7 @@
is defined when it should not be defined, xxx_fail_test will not report
**passed**
.libs/config/test
and run bjam
config_info config_test
compiler-list
.
@@ -266,26 +266,26 @@
Then you should:
-<unistd.h>
).
Copyright © 2001 -2007 Beman Dawes, Vesa Karvonen, John Maddock
Distributed under the Boost Software License, Version 1.0. (See accompanying file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)
@@ -75,8 +75,8 @@+
+/boost/config/
).
There are two ways you can use this header:
-/boost/config/
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!).
BOOST_USER_CONFIG
to point to it. For
example create a new sub-directory <boost-root>/boost/config/
user/
, and copy the header there; for example
@@ -308,7 +310,9 @@
+
+The following usage examples represent just a few of the possibilities:
-Last revised: November 23, 2010 at 05:40:40 GMT |
+Last revised: November 25, 2010 at 10:30:55 GMT |