diff --git a/doc/html/boost_config/acknowledgements.html b/doc/html/boost_config/acknowledgements.html index 313bc296..ae598f9d 100644 --- a/doc/html/boost_config/acknowledgements.html +++ b/doc/html/boost_config/acknowledgements.html @@ -3,7 +3,7 @@ Acknowledgements - + @@ -21,7 +21,7 @@
PrevUpHome
-
+

Acknowledgements

diff --git a/doc/html/boost_config/boost_macro_reference.html b/doc/html/boost_config/boost_macro_reference.html index 57443b20..9f013c0a 100644 --- a/doc/html/boost_config/boost_macro_reference.html +++ b/doc/html/boost_config/boost_macro_reference.html @@ -3,7 +3,7 @@ Boost Macro Reference - + @@ -22,7 +22,7 @@
PrevUpHomeNext
-
+
@@ -46,7 +46,7 @@
Macros for libraries with separate source code
-
+

Macros that describe C++03 defects @@ -1338,7 +1338,7 @@

-
+

Macros that describe optional features @@ -1514,6 +1514,26 @@ + +

+ BOOST_HAS_INT128 +

+ + +

+ Compiler +

+ + +

+ The compiler has __int128 + and unsigned __int128 + as native types which are distinct from all the regular C++ integer + types. +

+ + +

BOOST_HAS_LOG1P @@ -2247,7 +2267,7 @@

-
+
-
+
-
+
-
+

Boost Helper Macros @@ -3481,7 +3501,7 @@

-
+

Boost Informational Macros @@ -3759,7 +3779,7 @@

-
+

Boost Deprecated Macros @@ -4704,7 +4724,7 @@

-
+

Macros for libraries with separate source code @@ -4721,14 +4741,14 @@ The following macros and helper headers are of use to authors whose libraries include separate source code, and are intended to address several issues:

-
    -
  • +
      +
    • Controlling shared library symbol visibility
      • -
    • +
    • Fixing the ABI of the compiled library
      • -
    • +
    • Selecting which compiled library to link against based upon the compilers settings
      • @@ -4737,7 +4757,7 @@ See Guidelines for Authors of Boost Libraries Containing Separate Source

      -
      +
      -
      +

      ABI Fixing @@ -4950,7 +4970,7 @@ to point to their own prefix/suffix headers if they so wish.

      -
      +

      Automatic library selection @@ -4977,7 +4997,7 @@

      -
      +
      BOOST_LIB_NAME

      Required: An identifier containing the basename of the library, for diff --git a/doc/html/boost_config/guidelines_for_boost_authors.html b/doc/html/boost_config/guidelines_for_boost_authors.html index 2a3dbea8..f64ef39b 100644 --- a/doc/html/boost_config/guidelines_for_boost_authors.html +++ b/doc/html/boost_config/guidelines_for_boost_authors.html @@ -3,7 +3,7 @@ Guidelines for Boost Authors - + @@ -22,7 +22,7 @@

      PrevUpHomeNext
      -
      +

      Guidelines for Boost Authors @@ -61,26 +61,26 @@

      Note that:

      -
        -
      • +
          +
        • Boost library implementers are not required to "#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).
          • -
        • +
        • If a library implementer wishes to support some non-conforming compiler, or to support some platform specific feature, "#include <boost/config.hpp>" is the preferred way to obtain configuration information not available from the standard headers such as <climits>, etc.
          • -
        • +
        • If configuration information can be deduced from standard headers such as <climits>, use those standard headers rather than <boost/config.hpp>.
          • -
        • +
        • Boost files that use macros defined in <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,22 +88,22 @@ is no sensible default behavior, an #error message should describe the problem.
          • -
        • +
        • If a Boost library implementer wants something added to 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 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.
          • -
        • +
        • The intent is not to disable mainstream features now well-supported by the majority of compilers, such as namespaces, exceptions, RTTI, or templates.
        -
        +

        Disabling Compiler Warnings @@ -116,17 +116,17 @@

        Note that:

        -
          -
        • +
            +
          • 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.
            • -
          • +
          • The header should be included before you include any other header.
            • -
          • +
          • 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. @@ -182,7 +182,7 @@
        -
        +

        Adding New Defect Macros @@ -233,15 +233,15 @@ Once the test code is in place in libs/config/test, updating the configuration test system proceeds as:

        -
          -
        • +
            +
          • cd into 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.

            • -
          • +
          • cd into 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**.

            • -
          • +
          • cd into libs/config/test and run bjam config_info config_test compiler-list. @@ -266,26 +266,26 @@

            Then you should:

            -
              -
            • +
                +
              • Define the defect macro in those config headers that require it.
                • -
              • +
              • Document the macro in this documentation (please do not forget this step!!)
                • -
              • +
              • Commit everything.
                • -
              • +
              • Keep an eye on the regression tests for new failures in Boost.Config caused by the addition.
                • -
              • +
              • Start using the macro.
            -
            +

            Adding New Feature Test Macros @@ -309,7 +309,7 @@ <unistd.h>).

            -
            +

            Modifying the Boost Configuration Headers diff --git a/doc/html/boost_config/rationale.html b/doc/html/boost_config/rationale.html index 8c769174..d795c63c 100644 --- a/doc/html/boost_config/rationale.html +++ b/doc/html/boost_config/rationale.html @@ -3,7 +3,7 @@ Rationale - + @@ -22,7 +22,7 @@
            PrevUpHomeNext
            -
            +
            @@ -39,7 +39,7 @@ principles from the following article.

            -
            +
            @@ -90,7 +90,7 @@ code must be provided.

            -
            +
            diff --git a/doc/html/index.html b/doc/html/index.html index a225c4db..90f9ad86 100644 --- a/doc/html/index.html +++ b/doc/html/index.html @@ -3,7 +3,7 @@ Boost.Config - + @@ -18,7 +18,7 @@
            Next
            -
            +

            @@ -97,7 +97,7 @@
            Acknowledgements

      -
      +
      -
      +

      Using the default boost configuration @@ -140,7 +140,7 @@ and submitting a support request.

      -
      +

      The <boost/config.hpp> header @@ -171,7 +171,7 @@ developers list.

      -
      +

      Using the configure script @@ -292,15 +292,15 @@ (located under <boost-root>/boost/config/). There are two ways you can use this header:

      -
        -
      • +
          +
        • Option 1: copy the header into <boost-root>/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 svn repository (something you will not be thanked for!).
          • -
        • +
        • Option 2: give the header a more memorable name, and place it somewhere convenient; then, define the macro 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 @@ -313,7 +313,7 @@
      -
      +

      User settable options @@ -679,7 +679,7 @@

      -
      +

      Advanced configuration usage @@ -723,7 +723,7 @@

      The following usage examples represent just a few of the possibilities:

      -
      +

      Example 1: creating our own frozen configuration @@ -755,7 +755,7 @@ yet supported by boost.

      -
      +

      Example 2: skipping files that you don't need @@ -774,7 +774,7 @@ a dependency on two boost headers.

      -
      +
      -
      +

      Testing the boost configuration @@ -951,7 +951,7 @@

      - +

      Last revised: September 10, 2012 at 15:21:59 GMT

      Last revised: October 25, 2012 at 12:28:15 GMT
      diff --git a/doc/macro_reference.qbk b/doc/macro_reference.qbk index bb27c64a..90aa9344 100644 --- a/doc/macro_reference.qbk +++ b/doc/macro_reference.qbk @@ -368,6 +368,9 @@ the names of the header needed to access hash_set and hash_map; `BOOST_STD_EXTENSION_NAMESPACE` will provide the namespace in which the two class templates reside. ]] +[[`BOOST_HAS_INT128`][Compiler][ +The compiler has `__int128` and `unsigned __int128` as native types which are distinct +from all the regular C++ integer types.]] [[`BOOST_HAS_LOG1P`][Platform][ The platform has the functions `log1p`, `log1pf` and `log1pl` in ``. ]]