RubyGems - script_core - Versions diffs - 0.0.5 → 0.0.6 - Mend

script_core 0.0.5 → 0.0.6

Files changed (1076) hide show

data/ext/enterprise_script_service/msgpack/external/boost/predef/doc/html/predef/check_utilities.html DELETED Viewed

@@ -1,159 +0,0 @@
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
-<title>Check Utilities</title>
-<link rel="stylesheet" href="../boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
-<link rel="home" href="../index.html" title="Predef 1.4.1">
-<link rel="up" href="../index.html" title="Predef 1.4.1">
-<link rel="prev" href="reference/version_definition_macros.html" title="Version definition macros">
-<link rel="next" href="history.html" title="History">
-</head>
-<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
-<div class="spirit-nav">
-<a accesskey="p" href="reference/version_definition_macros.html"><img src="../images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../images/home.png" alt="Home"></a><a accesskey="n" href="history.html"><img src="../images/next.png" alt="Next"></a>
-</div>
-<div class="section">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="predef.check_utilities"></a><a class="link" href="check_utilities.html" title="Check Utilities">Check Utilities</a>
-</h2></div></div></div>
-<p>
-      The <code class="computeroutput"><span class="identifier">predef_check</span></code> utility provides
-      a facility for building a program that will check a given set of expressions
-      against the definitions it detected when it was built.
-    </p>
-<h4>
-<a name="predef.check_utilities.h0"></a>
-      <span class="phrase"><a name="predef.check_utilities.predef_check_programs"></a></span><a class="link" href="check_utilities.html#predef.check_utilities.predef_check_programs"><code class="literal">predef_check</code>
-      programs</a>
-    </h4>
-<p>
-      Even though there is only one <code class="computeroutput"><span class="identifier">predef_check</span></code>
-      program, there are variations for each of the languages that are detected by
-      Predef to match the convention for sources files. For all of them one invokes
-      with a list of expression arguments. The expressions are evaluated within the
-      context of the particular <code class="literal">predef_check</code> program and if they
-      all are true zero (0) is returned. Otherwise the index of the first false expression
-      is returned.
-    </p>
-<p>
-      The expression syntax is simple:
-    </p>
-<pre class="programlisting">predef-definition [ relational-operator version-value ]
-</pre>
-<p>
-      <em class="replaceable"><code>predef-definition</code></em> can be any of the Predef definitions.
-      For example <code class="computeroutput"><span class="identifier">BOOST_COMP_GCC</span></code>.
-    </p>
-<p>
-      <em class="replaceable"><code>relational-operator</code></em> can be any of: <code class="literal">&gt;</code>,
-      <code class="literal">&lt;</code>, <code class="literal">&gt;=</code>, <code class="literal">&lt;=</code>,
-      <code class="literal">==</code> and <code class="literal">!=</code>.
-    </p>
-<p>
-      <em class="replaceable"><code>version-number</code></em> can be a full or partial version
-      triplet value. If it's a partial version triple it is completed with zeros.
-      That is <code class="literal">x.y</code> is equivalent to <code class="literal">x.y.0</code> and
-      <code class="literal">x</code> is equivalent to <code class="literal">x.0.0</code>.
-    </p>
-<p>
-      The <em class="replaceable"><code>relations-operator</code></em> and <em class="replaceable"><code>version-number</code></em>
-      can be ommited. In which case it is equivalent to:
-    </p>
-<pre class="programlisting">predef-definition &gt; 0.0.0
-</pre>
-<h4>
-<a name="predef.check_utilities.h1"></a>
-      <span class="phrase"><a name="predef.check_utilities.using_with_boost_build"></a></span><a class="link" href="check_utilities.html#predef.check_utilities.using_with_boost_build">Using
-      with Boost.Build</a>
-    </h4>
-<p>
-      You can use the <code class="literal">predef_check</code> programs directly from Boost
-      Build to configure target requirements. This is useful for controlling what
-      gets built as part of your project based on the detailed version information
-      available in Predef. The basic use is simple:
-    </p>
-<pre class="programlisting">import path-to-predef-src/tools/check/predef
-    : check require
-    : predef-check predef-require ;
-exe my_windows_program : windows_source.cpp
-    : [ predef-require "BOOST_OS_WINDOWS" ] ;
-</pre>
-<p>
-      That simple use case will skip building the <code class="literal">my_windows_program</code>
-      unless one is building for Windows. Like the direct <code class="literal">predef_check</code>
-      you can pass mutiple expressions using relational comparisons. For example:
-    </p>
-<pre class="programlisting">import path-to-predef-src/tools/check/predef
-    : check require
-    : predef-check predef-require ;
-lib my_special_lib : source.cpp
-    : [ predef-require "BOOST_OS_WINDOWS != 0" "BOOST_OS_VMS != 0"] ;
-</pre>
-<p>
-      And in that case the <code class="literal">my_special_lib</code> is built only when the
-      OS is not Windows or VMS. The <code class="literal">requires</code> rule is a special
-      case of the <code class="literal">check</code> rule. And is defined in terms of it:
-    </p>
-<pre class="programlisting">rule require ( expressions + : language ? )
-{
-    return [ check $(expressions) : $(language) : : &lt;build&gt;no ] ;
-}
-</pre>
-<p>
-      The expression can also use explicit "and", "or" logical
-      operators to for more complex checks:
-    </p>
-<pre class="programlisting">import path-to-predef-src/tools/check/predef
-    : check require
-    : predef-check predef-require ;
-lib my_special_lib : source.cpp
-    : [ predef-require "BOOST_OS_WINDOWS" or "BOOST_OS_VMS"] ;
-</pre>
-<p>
-      You can use the <code class="literal">check</code> rule for more control and to implement
-      something other than control of what gets built. The definition for the <code class="literal">check</code>
-      rule is:
-    </p>
-<pre class="programlisting">rule check ( expressions + : language ? : true-properties * : false-properties * )
-</pre>
-<p>
-      When invoked as a reuirement of a Boost Build target this rule will add the
-      <code class="literal">true-properties</code> to the target if all the <code class="literal">expressions</code>
-      evaluate to true. Otherwise the <code class="literal">false-properties</code> get added
-      as requirements. For example you could use it to enable or disable features
-      in your programs:
-    </p>
-<pre class="programlisting">import path-to-predef-src/tools/check/predef
-    : check require
-    : predef-check predef-require ;
-exe my_special_exe : source.cpp
-    : [ predef-check "BOOST_OS_WINDOWS == 0"
-        : : &lt;define&gt;ENABLE_WMF=0
-        : &lt;define&gt;ENABLE_WMF=1 ] ;
-</pre>
-<p>
-      For both <code class="literal">check</code> and <code class="literal">require</code> the <code class="literal">language</code>
-      argument controls which variant of the <code class="literal">predef_check</code> program
-      is used to check the expressions. It defaults to "c++", but can be
-      any of: "c", "cpp", "objc", and "objcpp".
-    </p>
-</div>
-<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
-<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright &#169; 2005, 2008-2016 Rene Rivera<br>Copyright &#169; 2015 Charly Chevalier<br>Copyright &#169; 2015 Joel Falcou<p>
-        Distributed under the Boost Software License, Version 1.0. (See accompanying
-        file LICENSE_1_0.txt or copy at <a href="http://www.boost.org/LICENSE_1_0.txt" target="_top">http://www.boost.org/LICENSE_1_0.txt</a>)
-      </p>
-</div></td>
-</tr></table>
-<hr>
-<div class="spirit-nav">
-<a accesskey="p" href="reference/version_definition_macros.html"><img src="../images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../images/home.png" alt="Home"></a><a accesskey="n" href="history.html"><img src="../images/next.png" alt="Next"></a>
-</div>
-</body>
-</html>

data/ext/enterprise_script_service/msgpack/external/boost/predef/doc/html/predef/history.html DELETED Viewed

@@ -1,159 +0,0 @@
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
-<title>History</title>
-<link rel="stylesheet" href="../boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
-<link rel="home" href="../index.html" title="Predef 1.4.1">
-<link rel="up" href="../index.html" title="Predef 1.4.1">
-<link rel="prev" href="check_utilities.html" title="Check Utilities">
-<link rel="next" href="to_do.html" title="To Do">
-</head>
-<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
-<div class="spirit-nav">
-<a accesskey="p" href="check_utilities.html"><img src="../images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../images/home.png" alt="Home"></a><a accesskey="n" href="to_do.html"><img src="../images/next.png" alt="Next"></a>
-</div>
-<div class="section">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="predef.history"></a><a class="link" href="history.html" title="History">History</a>
-</h2></div></div></div>
-<h4>
-<a name="predef.history.h0"></a>
-      <span class="phrase"><a name="predef.history.1_4_1"></a></span><a class="link" href="history.html#predef.history.1_4_1">1.4.1</a>
-    </h4>
-<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
-<li class="listitem">
-          Small fixes for some redefinition errors, and mispelled macros.
-        </li>
-<li class="listitem">
-          Slightly rearrangement of structure to comply with current library requirements.
-        </li>
-</ul></div>
-<h4>
-<a name="predef.history.h1"></a>
-      <span class="phrase"><a name="predef.history.1_4"></a></span><a class="link" href="history.html#predef.history.1_4">1.4</a>
-    </h4>
-<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
-<li class="listitem">
-          Add detection of SIMD hardware. With the addition of the <code class="computeroutput"><span class="identifier">BOOST_HW_</span><span class="special">*</span></code>
-          category (from Charly Chevalier).
-        </li>
-<li class="listitem">
-          Add compile only version of check utilities to address cross-compile use
-          cases. And changed the BBv2 check support to use compile only checks.
-        </li>
-<li class="listitem">
-          Fix test warnings.
-        </li>
-<li class="listitem">
-          Fix typos on <code class="computeroutput"><span class="identifier">AVAILABLE</span></code>
-          macros for Windows Platform. (from Vemund Handeland)
-        </li>
-</ul></div>
-<h4>
-<a name="predef.history.h2"></a>
-      <span class="phrase"><a name="predef.history.1_3"></a></span><a class="link" href="history.html#predef.history.1_3">1.3</a>
-    </h4>
-<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
-<li class="listitem">
-          Fix many problems with <code class="computeroutput"><span class="identifier">predef_check</span></code>
-          functionality.
-        </li>
-<li class="listitem">
-          Update SunPro detection to accomodate latest version of compiler from Oracle.
-        </li>
-<li class="listitem">
-          Addition of Travis-CI and Appveyor testing.
-        </li>
-<li class="listitem">
-          Add <code class="computeroutput"><span class="keyword">and</span></code> and <code class="computeroutput"><span class="keyword">or</span></code> logical operators for <code class="computeroutput"><span class="identifier">predef_check</span></code>
-          expression on the Boost Build side.
-        </li>
-<li class="listitem">
-          Fix <code class="computeroutput"><span class="identifier">BOOST_ARCH_PARISC</span></code> to
-          correctly spelled name (from Graham Hanson).
-        </li>
-<li class="listitem">
-          Fix <code class="computeroutput"><span class="identifier">MAKE_YYYYM</span></code> macros to
-          correctly limit the month (from rick68).
-        </li>
-</ul></div>
-<h4>
-<a name="predef.history.h3"></a>
-      <span class="phrase"><a name="predef.history.1_2"></a></span><a class="link" href="history.html#predef.history.1_2">1.2</a>
-    </h4>
-<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
-<li class="listitem">
-          Account for skip in Visual Studio product version vs. compiler version.
-          This supports version of VS 2015 an onward.
-        </li>
-<li class="listitem">
-          Add detection of Haiku OS (from Jessica Hamilton).
-        </li>
-<li class="listitem">
-          Some fixes to endian detection for Android (from mstahl-at-redhat.com).
-        </li>
-<li class="listitem">
-          Add missing <code class="computeroutput"><span class="identifier">BOOST_PREDEF_MAKE_0X_VVRRPP</span></code>
-          macro (from Erik Lindahl).
-        </li>
-<li class="listitem">
-          Add <code class="computeroutput"><span class="identifier">predef_check</span></code> program
-          and BBv2 integration for build configuration checks.
-        </li>
-</ul></div>
-<h4>
-<a name="predef.history.h4"></a>
-      <span class="phrase"><a name="predef.history.1_1"></a></span><a class="link" href="history.html#predef.history.1_1">1.1</a>
-    </h4>
-<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
-<li class="listitem">
-          Addition of <code class="computeroutput"><span class="identifier">BOOST_PLAT_</span><span class="special">*</span></code> platform definitions for MinGW and Windows
-          platform variants.
-        </li>
-<li class="listitem">
-          Detection of ARM architecture for Windows compilers to target mobile devices
-          of Windows 8.
-        </li>
-<li class="listitem">
-          Improved ARM detection for 64 bit ARM.
-        </li>
-<li class="listitem">
-          Added detection of iOS an an operating system.
-        </li>
-<li class="listitem">
-          Improved detection of endianess on some platforms.
-        </li>
-<li class="listitem">
-          Addition of exclusive plus emulated definitions for platform and compiler
-          detection.
-        </li>
-</ul></div>
-<div class="warning"><table border="0" summary="Warning">
-<tr>
-<td rowspan="2" align="center" valign="top" width="25"><img alt="[Warning]" src="../images/warning.png"></td>
-<th align="left">Warning</th>
-</tr>
-<tr><td align="left" valign="top"><p>
-        The big change for this version is the restructuring of the definitions to
-        avoid duplicate definitions in one category. That is, only one <code class="computeroutput"><span class="identifier">BOOST_OS_</span><span class="special">*</span></code>,
-        <code class="computeroutput"><span class="identifier">BOOST_COMP_</span><span class="special">*</span></code>,
-        and <code class="computeroutput"><span class="identifier">BOOST_PLAT_</span><span class="special">*</span></code>
-        variant will be detected (except for sub-categories).
-      </p></td></tr>
-</table></div>
-</div>
-<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
-<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright &#169; 2005, 2008-2016 Rene Rivera<br>Copyright &#169; 2015 Charly Chevalier<br>Copyright &#169; 2015 Joel Falcou<p>
-        Distributed under the Boost Software License, Version 1.0. (See accompanying
-        file LICENSE_1_0.txt or copy at <a href="http://www.boost.org/LICENSE_1_0.txt" target="_top">http://www.boost.org/LICENSE_1_0.txt</a>)
-      </p>
-</div></td>
-</tr></table>
-<hr>
-<div class="spirit-nav">
-<a accesskey="p" href="check_utilities.html"><img src="../images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../images/home.png" alt="Home"></a><a accesskey="n" href="to_do.html"><img src="../images/next.png" alt="Next"></a>
-</div>
-</body>
-</html>

data/ext/enterprise_script_service/msgpack/external/boost/predef/doc/html/predef/introduction.html DELETED Viewed

@@ -1,205 +0,0 @@
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
-<title>Introduction</title>
-<link rel="stylesheet" href="../boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
-<link rel="home" href="../index.html" title="Predef 1.4.1">
-<link rel="up" href="../index.html" title="Predef 1.4.1">
-<link rel="prev" href="../index.html" title="Predef 1.4.1">
-<link rel="next" href="using_the_predefs.html" title="Using the predefs">
-</head>
-<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
-<div class="spirit-nav">
-<a accesskey="p" href="../index.html"><img src="../images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../images/home.png" alt="Home"></a><a accesskey="n" href="using_the_predefs.html"><img src="../images/next.png" alt="Next"></a>
-</div>
-<div class="section">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="predef.introduction"></a><a class="link" href="introduction.html" title="Introduction">Introduction</a>
-</h2></div></div></div>
-<p>
-      This library defines a set of compiler, architecture, operating system, library,
-      and other version numbers from the information it can gather of C, C++, Objective
-      C, and Objective C++ predefined macros or those defined in generally available
-      headers. The idea for this library grew out of a proposal to extend the Boost
-      Config library to provide more, and consistent, information than the feature
-      definitions it supports. What follows is an edited version of that brief proposal.
-    </p>
-<h4>
-<a name="predef.introduction.h0"></a>
-      <span class="phrase"><a name="predef.introduction.proposal"></a></span><a class="link" href="introduction.html#predef.introduction.proposal">Proposal</a>
-    </h4>
-<p>
-      The idea is to define a set of macros to identify compilers and consistently
-      represent their version. This includes:
-    </p>
-<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
-<li class="listitem">
-          A unique BOOST_VERSION_NUMBER(major,minor,patch) macro to specify version
-          numbers (unfortunately, the name BOOST_VERSION is already taken to designate
-          the version number of boost itself).
-        </li>
-<li class="listitem">
-          A compiler identification macro, suitable for use in <code class="computeroutput"><span class="preprocessor">#if</span></code>/<code class="computeroutput"><span class="preprocessor">#elif</span></code> directives, for each of the supported
-          compilers. All macros would be defined, regardless of the compiler. The
-          one macro corresponding to the compiler being used would be defined, in
-          terms of BOOST_VERSION_NUMBER, to carry the exact compiler version. All
-          other macros would expand to an expression evaluating to false (for instance,
-          the token 0) to indicate that the corresponding compiler is not present.
-        </li>
-<li class="listitem">
-          "Null values" could be set, for all macros, in boost/config/select_compiler.hpp;
-          then, for each compiler the corresponding identification macro would be
-          #undef and re-#defined in the corresponding boost/compiler/(cc).hpp; however
-          in the context of the Boost.Config infrastructure using a "prefix"
-          header (to be introduced) or boost/config/suffix.hpp is a better solution.
-        </li>
-</ul></div>
-<h4>
-<a name="predef.introduction.h1"></a>
-      <span class="phrase"><a name="predef.introduction.current_library"></a></span><a class="link" href="introduction.html#predef.introduction.current_library">Current
-      Library</a>
-    </h4>
-<p>
-      The current Predef library is now, both an independent library, and expanded
-      in scope. It includes detection and definition of architectures, compilers,
-      languages, libraries, operating systems, and endianness. The key benefits are:
-    </p>
-<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
-<li class="listitem">
-          Version numbers that are always defined so that one doesn't have to guard
-          with <code class="computeroutput"><span class="preprocessor">#ifdef</span></code>.
-        </li>
-<li class="listitem">
-          Guard macros that can be used for <code class="computeroutput"><span class="preprocessor">#ifdef</span></code>
-          checks.
-        </li>
-<li class="listitem">
-          All possible definitions are included with the single <code class="computeroutput"><span class="preprocessor">#include</span>
-          <span class="special">&lt;</span><span class="identifier">boost</span><span class="special">/</span><span class="identifier">predef</span><span class="special">.</span><span class="identifier">h</span><span class="special">&gt;</span></code>
-          so that it's friendly to precompiled header usage.
-        </li>
-<li class="listitem">
-          Specific definitions can be included, ex. <code class="computeroutput"><span class="preprocessor">#include</span>
-          <span class="special">&lt;</span><span class="identifier">boost</span><span class="special">/</span><span class="identifier">predef</span><span class="special">/</span><span class="identifier">os</span><span class="special">/</span><span class="identifier">windows</span><span class="special">.</span><span class="identifier">h</span><span class="special">&gt;</span></code>
-          for single checks.
-        </li>
-<li class="listitem">
-          Predefs can be directly used in both preprocessor and compiler expressions
-          for comparison to other similarly defined values.
-        </li>
-<li class="listitem">
-          The headers are usable from multiple languages, that support the C preprocessor.
-          In particular C++, C, Objective C, and Objective C++.
-        </li>
-</ul></div>
-<h4>
-<a name="predef.introduction.h2"></a>
-      <span class="phrase"><a name="predef.introduction.design_choices"></a></span><a class="link" href="introduction.html#predef.introduction.design_choices">Design
-      choices</a>
-    </h4>
-<p>
-      An important design choice concerns how to represent compiler versions by means
-      of a single integer number suitable for use in preprocessing directives. Let's
-      do some calculation. The "basic" signed type for preprocessing constant-expressions
-      is long in C90 (and C++, as of 2006) and intmax_t in C99. The type long shall
-      at least be able to represent the number <code class="literal">+2 147 483 647</code>.
-      This means the most significant digit can only be 0, 1 or 2; and if we want
-      all decimal digits to be able to vary between 0 and 9, the largest range we
-      can consider is <code class="literal">[0, 999 999 999]</code>. Distributing evenly, this
-      means 3 decimal digits for each version number part.
-    </p>
-<p>
-      So we can:
-    </p>
-<div class="orderedlist"><ol class="orderedlist" type="1">
-<li class="listitem">
-          use an uneven distribution or
-        </li>
-<li class="listitem">
-          use more bits (a larger type) or
-        </li>
-<li class="listitem">
-          use 3/3/3 and have the particular compiler/platform/stdlib deal with setting
-          the numbers within the 3-digit range.
-        </li>
-</ol></div>
-<p>
-      It appears relatively safe to go for the first option and set it at 2/2/5.
-      That covers CodeWarrior and others, which are up to and past 10 for the major
-      number. Some compilers use the build number in lieu of the patch one; five
-      digits (which is already reached by VC++ 8) seems a reasonable limit even in
-      this case.
-    </p>
-<div class="note"><table border="0" summary="Note">
-<tr>
-<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.png"></td>
-<th align="left">Note</th>
-</tr>
-<tr><td align="left" valign="top"><p>
-        A 2/2/6 scheme would allow for bigger patch/build numbers at the cost, for
-        instance, of limiting the major version number to 20 (or, with further constraints,
-        to 21).
-      </p></td></tr>
-</table></div>
-<p>
-      It might reassure the reader that this decision is actually encoded in one
-      place in the code; the definition of <code class="computeroutput"><span class="identifier">BOOST_VERSION_NUMBER</span></code>.
-    </p>
-<h4>
-<a name="predef.introduction.h3"></a>
-      <span class="phrase"><a name="predef.introduction.future_work"></a></span><a class="link" href="introduction.html#predef.introduction.future_work">Future
-      work</a>
-    </h4>
-<p>
-      Even though the basics of this library are done, there is much work that can
-      be done:
-    </p>
-<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
-<li class="listitem">
-          Right now we limit the detection of libraries to known built-in predefined
-          macros, and to guaranteed to exist system and library headers. It might
-          be interesting to add something like auto-configuration predefs. This way
-          we can add definitions for user specific libraries and features.
-        </li>
-<li class="listitem">
-          Along with the above, it might be good to add some user control as to which
-          headers are included with the top-level header. Although in the current
-          form of the library this is less of an issue as one can include the specific
-          headers one needs.
-        </li>
-<li class="listitem">
-          Additionally, even if there is no auto-configure style option.. It would
-          be good to add optionally included headers so that user can get consistent
-          version number definitions for libraries they use.
-        </li>
-<li class="listitem">
-          Having a consistent set of version number definitions opens the door to
-          improving the user level syntax of libraries that do checks against version
-          numbers. Specifically Boost Config's <code class="computeroutput"><span class="identifier">BOOST_WORKAROUND</span></code>
-          macro would benefit from a more readable syntax. As would the <code class="computeroutput"><span class="identifier">BOOST_TESTED_AT</span></code> detail macro.
-        </li>
-<li class="listitem">
-          And obviously there's lots of work to do in reformulating the existing
-          Boost libraries to use the Predef library once it's accepted.
-        </li>
-<li class="listitem">
-          And there's the continuing work of adding definitions for present and future
-          compilers, platforms, architectures, languages, and libraries.
-        </li>
-</ul></div>
-</div>
-<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
-<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright &#169; 2005, 2008-2016 Rene Rivera<br>Copyright &#169; 2015 Charly Chevalier<br>Copyright &#169; 2015 Joel Falcou<p>
-        Distributed under the Boost Software License, Version 1.0. (See accompanying
-        file LICENSE_1_0.txt or copy at <a href="http://www.boost.org/LICENSE_1_0.txt" target="_top">http://www.boost.org/LICENSE_1_0.txt</a>)
-      </p>
-</div></td>
-</tr></table>
-<hr>
-<div class="spirit-nav">
-<a accesskey="p" href="../index.html"><img src="../images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../images/home.png" alt="Home"></a><a accesskey="n" href="using_the_predefs.html"><img src="../images/next.png" alt="Next"></a>
-</div>
-</body>
-</html>