RubyGems - script_core - Versions diffs - 0.3.0 → 0.3.2 - Mend

script_core 0.3.0 → 0.3.2

Files changed (1057) hide show

data/ext/enterprise_script_service/msgpack/external/boost/preprocessor/doc/topics/variadic_macros.html ADDED Viewed

@@ -0,0 +1,262 @@
+<html>
+  <head>
+    <meta  content="text/html; charset=windows-1252"  http-equiv="content-type">
+    <title>variadic_macros.html</title>
+    <link  rel="stylesheet"  type="text/css"  href="../styles.css">
+    <style>
+    u { font-weight: normal; text-decoration: none; }
+    </style>
+  </head>
+  <body>
+    <h4>Variadic Macros</h4>
+    <div> Variadic macros are supported by a number of compilers. They are
+      macros of the form: </div>
+    <div  class="code">
+      <pre>#define SOME_MACRO(ZeroOrMoreParameters,...) macro expansion possible specifying __VA_ARGS__</pre>
+    </div>
+    <div> The '...' in the parameter list represents the variadic data when the
+      macro is invoked and the __VA_ARGS__ in the expansion represents the
+      variadic data in the expansion of the macro. Variadic data is of the form
+      of 1 or more preprocessor tokens separated by commas.<br>
+      <br>
+      The '...' must be the last parameter in the macro definition and there may
+      be 0 or more non-variadic parameters preceding it.<br>
+      <br>
+      In the expansion of the macro __VA_ARGS__ may be specified 0 or more times
+      to represent the variadic data. The variadic data in the expansion is a
+      comma separated list of preprocessor tokens representing the variadic data
+      which the invoker of the macro enters as the last arguments to the macro.<br>
+    </div>
+    <h4>Example<u> - Creating and invoking a variadic macro.</u></h4>
+    <div  class="code">
+      <pre>#define INITIALIZE_INT_ARRAY(array_name,...) \ <br> static int array_name[] = { __VA_ARGS__ }; \ <br> /**/<br><br> INITIALIZE_INT_ARRAY(myname,45,789,33510,9346,2)</pre>
+    </div>
+    <u> <span  style="font-weight: bold;">Preprocessor
+        Library Support<br>
+      </span></u>
+    <div>The library offers support for variadic macros for those
+      compilers
+      which support the feature. The library can automatically detect whether
+      a compiler supports variadic macros and sets the macro
+      BOOST_PP_VARIADICS accordingly to 1 if the compiler supports variadic
+      macros or 0 if the compiler does not support variadic macros.<br>
+      <br>
+      The end-user can #define BOOST_PP_VARIADICS to 1 or 0 himself in a
+      translation unit, before including any preprocessor header files, to
+      prevent the library from attempting to detect whether the compiler
+      supports variadic macros. This has the effect of manually turning on or
+      off variadic macro support in the library. Of course if one manually
+      turns on variadic macro support in the library, and one's compiler does
+      not support variadic macros, functionality in the library which uses
+      variadic macros will fail with error messages from the compiler.<br>
+      <br>
+      When BOOST_PP_VARIADICS is 1, the library offers some extended
+      functionality
+      by using variadic macros, and also offers extended support for working
+      with variadic data.<br><br>
+      <a  name="vmvcquirk"></a>Visual C++ has a
+      few quirks related to variadic macros which require the end-user to code
+      slightly differently. When BOOST_PP_VARIADICS is 1 and Visual C++ is the
+      compiler BOOST_PP_VARIADICS_MSVC is 1, else when BOOST_PP_VARIADICS is 1
+      and Visual C++ is not the compiler BOOST_PP_VARIADICS_MSVC is 0. When
+      BOOST_PP_VARIADICS is 0 then BOOST_PP_VARIADICS_MSVC is not defined.
+      In this way the end-user, when using variadic macros, can test for the
+      presence of Visual C++ as the compiler and code accordingly.<br>
+      <br>
+      Support for working with variadic
+      data is largely centered on being able to convert variadic data to
+      other library data types, since the
+      functionality for working with those Boost preprocessor library data
+      types is much greater than that for working with variadic data directly.<br>
+    </div>
+    <a  name="VNotation"></a>
+    <h4>Notation For Variadic Macros<br>
+    </h4>
+    <div>In the documentation, headers which have variadic macros,
+      and
+      variadic macros themselves, have a notation of '(v)' appended to them.
+      For the variadic macros themselves this signifies that
+      BOOST_PP_VARIADICS must be 1 for those variadic macros to be usable.
+      For variadic macros which have a non-variadic equivalent, the
+      non-variadic equivalent will be used if BOOST_PP_VARIADICS is set to 0.
+    </div>
+    <h4>Extended Functionality Using Variadic Macros<br>
+    </h4>
+    <div>Some macros in the library offer extended
+      functionality through the use of variadic macros.<br>
+      <br>
+      The variadic macro version offers the same functionality
+      as the non-variadic version, but because of the ability of the variadic
+      parameters to encompass a variable number of arguments, it also offers
+      an enhanced syntax using the same macro name.<br>
+      <br>
+      The macros in the library which offer this enhanced functionality are
+      all
+      centered on <i>tuple</i> manipulation. With variadic
+      macros it is
+      possible to
+      manipulate tuples without having to know the size of the tuple. So
+      while the invoker can still specify the size when using tuple macro
+      functionality, there are variadic versions of each of the tuple macros,
+      with the exact same name as the non-variadic macro, where the size need
+      not be specified.<br>
+    </div>
+    <h4>Extended Support For Variadic Data</h4>
+    <div>The library offers extended support for working with
+      variadic data
+      which goes beyond the functionality offered by the C++ specification
+      for variadic macros. It does this through preprocessor programming and
+      by using some of the other functionality in the library itself. Header
+      and macro names
+      in the library which offer extended support for working with variadic
+      data, and need the compiler to support variadic macros, are marked with
+      a (v)<sup> </sup>to indicate a variadic macro.<br>
+      <br>
+      The form of the functionality which the library offers is centered on
+      two macros which work with variadic data itself, and a set of macros
+      which convert between variadic data and other library data
+      types.<br>
+      <br>
+      The two macros are BOOST_PP_VARIADIC_ELEM and BOOST_PP_VARIADIC_SIZE,
+      which respectively return a particular token of variadic data and the
+      number of tokens of variadic data.<br>
+      <br>
+      The macros for converting variadic data to the library's data types are
+      BOOST_PP_VARIADIC_TO_ARRAY, BOOST_PP_VARIADIC_TO_LIST,
+      BOOST_PP_VARIADIC_TO_SEQ, and BOOST_PP_VARIADIC_TO_TUPLE.<br>
+      <br>
+      All of these macros need compiler support for variadic data and only
+      exist if BOOST_PP_VARIADICS is 1. <br>
+      <br>
+      The remaining four macros, which convert from a library data type
+      to comma-separated preprocessor tokens, which is the form of
+      variadic data, do not need compiler support for variadic
+      macros. These functions are BOOST_PP_ARRAY_ENUM, BOOST_PP_LIST_ENUM,
+      BOOST_PP_SEQ_ENUM, and BOOST_PP_TUPLE_ENUM. However if one wishes to
+      use this variadic data reliably as arguments to other macros, one needs
+      variadic macro support.<br>
+    </div>
+    <u  style="font-weight: bold;"> Using a Tuple Instead of an Array<br>
+    </u>
+    <div>An array as a preprocessor data type is a two-element tuple where the
+      first element is the array size and the second element is a tuple which
+      constitutes the array data. Because a tuple knows its own size when the
+      compiler supports variadic macros, there is no reason to use the array preprocessor
+      data type as opposed to the tuple preprocessor data type; the tuple data
+      type now has all of the functionality which the array data type has and is
+      syntactically easier to use. With variadic macro support, which is now
+      officially part of the latest C++ standard, the preprocessor array data
+      type is essentially obsolete for conforming C++ compilers. Only if your
+      compiler does not support variadic macros is the preprocessor array data
+      type still useful.</div>
+    <u  style="font-weight: bold;">Using Variadic Data</u>
+    <div>Variadic data exists in the
+      form of comma-separated preprocessor tokens. This is the case whether
+      the variadic data comes from the __VA_ARGS__ of a variadic macro, from
+      the conversion of a library's data type to variadic data, or the
+      manual construction of comma-separated preprocessing tokens by the
+      programmer writing a macro.<br>
+      <br>
+      The easiest way to work with
+      variadic data internally is to convert it to a library data type.
+      Library data types, whether an <i>array</i>, <i>list</i>,
+      <i>sequence</i>,
+      or <i>tuple</i>, have a rich set of functionality for
+      manipulating
+      data whereas
+      variadic data functionality in the library only allows one to access
+      the variadic data as a whole or to access a single token of the
+      variadic data at a time.<br>
+      <br>
+      The user of the library still may
+      choose to pass variadic data back into internal macros rather than
+      convert it to other library data types. There is no problem passing
+      variadic data as a whole to variadic macros as the last parameter of
+      the macro. However: <br>
+      <br>
+      <span  style="font-weight: bold;">Attempting to pass
+        variadic data as a
+        whole directly into a non-variadic macro is not guaranteed to work and
+        may fail.<br>
+      </span><br>
+      This occurs because of a preprocessor weakness in a number
+      of compilers, currently most notably Visual C++. Even passing variadic
+      data as arguments to a non-variadic macro, when it is not represented
+      in
+      the form of� __VA_ARGS__, may fail with certain compilers.<br>
+      <br>
+      What follows are very simple examples, showing how variadic data can be
+      passed to a non-variadic macro.<br>
+      <br>
+      First an example of what NOT to do.<br>
+    </div>
+    <h4>Example<u> - Passing variadic data as a whole to a
+        non-variadic
+        macro. DO NOT DO.</u></h4>
+    <div  class="code">
+      <pre>#define MACRO_ARG_2(x,y) BOOST_PP_ADD(x,y)<br>#define VAR_MACRO(...) __VA_ARGS__<br><br>/* The following should not be done and is not guaranteed to work with compilers. */<br><br><span
+ style="font-weight: bold;"><span  style="font-family: monospace;"></span></span>int xx = MACRO_ARG_2(VAR_MACRO(2,3));</pre>
+    </div>
+    <div> There are two ways to pass variadic data to a non-variadic
+      macro.
+      The
+      first of these is to pass the individual tokens of the variadic data
+      separately to the non-variadic macro using the BOOST_PP_VARIADIC_ELEM
+      macro in the library.<br>
+    </div>
+    <h4>Example<u> - Passing individual variadic data tokens to
+        a
+        non-variadic macro.<br>
+      </u></h4>
+    <div  class="code">
+      <pre>#define MACRO_ARG_2(x,y) BOOST_PP_ADD(x,y)<br>#define VAR_MACRO(...) __VA_ARGS__<br><br>/* The following will work correctly */<br><br>int xx = MACRO_ARG_2<br> (<br> BOOST_PP_VARIADIC_ELEM(0,VAR_MACRO(2,3)),<br> BOOST_PP_VARIADIC_ELEM(1,VAR_MACRO(2,3))<br> );</pre>
+    </div>
+    <div>The second way is to use a macro in the library called
+      BOOST_PP_OVERLOAD.
+      This macro allows one to "overload" a variadic macro to non-variadic
+      macros of different numbers of parameters, using a common prefix.
+    </div>
+    <h4>Example<u> - Passing variadic data as a whole to
+        BOOST_PP_OVERLOAD
+        and on to a non-variadic macro.<br>
+      </u></h4>
+    <div  class="code">
+      <pre>#define MACRO_ARG_2(x,y) BOOST_PP_ADD(x,y)<br>#define VAR_MACRO(...) __VA_ARGS__<br><br>/* The following will work correctly */<br><br>int xx = BOOST_PP_OVERLOAD(MACRO_ARG_,VAR_MACRO(2,3))(VAR_MACRO(2,3));<br><br>/* For Visual C++ it is necessary to do this */<br><br>int xx = <br>BOOST_PP_CAT(BOOST_PP_OVERLOAD(MACRO_ARG_,VAR_MACRO(2,3))(VAR_MACRO(2,3)),BOOST_PP_EMPTY());</pre>
+    </div>
+    <br>
+    <div>Although these techniques will work when passing variadic
+      data to
+      non-variadic macros, it is much better and less problematical to
+      work internally with the existing library data types and to only use
+      variadic
+      macros as an interface for end-users when there is a need to have a
+      macro which takes a
+      variable number of parameters.<br>
+    </div>
+    <b>See</b> <b>Also</b><br>
+    <ul>
+      <li><a  href="../ref/variadics.html">BOOST_PP_VARIADICS</a></li>
+      <li><a  href="../headers/tuple.html">Tuple Macros</a><br>
+      </li>
+      <li><a  href="../headers/variadic.html">Variadic
+          Macros<br>
+        </a></li>
+      <li><a  href="../ref/array_enum.html">BOOST_PP_ARRAY_ENUM</a></li>
+      <li><a  href="../ref/list_enum_r.html">BOOST_PP_LIST_ENUM</a></li>
+      <li><a  href="../ref/seq_enum.html">BOOST_PP_SEQ_ENUM</a></li>
+      <li><a  href="../ref/tuple_enum.html">BOOST_PP_TUPLE_ENUM</a></li>
+      <li><a  href="../ref/overload.html">BOOST_PP_OVERLOAD</a></li>
+    </ul>
+    <hr  size="1">
+    <div  style="margin-left: 0px;"> <i>� Copyright
+        Edward Diener
+        2011,2013,2016</i> </div>
+    <div  style="margin-left: 0px;">
+      <p><small>Distributed under the Boost Software License,
+          Version 1.0.
+          (See accompanying file <a  href="../../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a>
+          or copy at <a  href="http://www.boost.org/LICENSE_1_0.txt">www.boost.org/LICENSE_1_0.txt</a>)</small></p>
+    </div>
+</body></html>

data/ext/enterprise_script_service/msgpack/external/boost/preprocessor/doc/topics.html ADDED Viewed

@@ -0,0 +1,27 @@
+<html>
+<head>
+    <title>topics.html</title>
+	<link rel="stylesheet" type="text/css" href="styles.css">
+	<base target="desc">
+</head>
+<body>
+<h4>Topics <small><a href="contents.html" target="index">[back]</a></small></h4>
+<ul>
+	<li><a href="topics/motivation.html">motivation</a></li>
+	<li><a href="topics/problems.html">known problems of the preprocessor</a>	</li><li><a href="topics/techniques.html">techniques</a></li>
+	<li><a href="topics/incompatible.html">incompatibilities</a></li>
+	<li><a href="topics/reentrancy.html">reentrancy</a></li>
+	<li><a href="topics/local_iteration.html">local iteration</a></li>
+	<li><a href="topics/file_iteration.html">file iteration</a></li>
+	<li><a href="topics/evaluated_slots.html">evaluated slots</a></li>
+    <li><a href="topics/variadic_macros.html">variadic macros</a></li>
+</ul>
+<!--
+� Copyright Housemarque Oy 2002
+� Copyright Paul Mensonides 2002
+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)
+-->
+</body>
+</html>

data/ext/enterprise_script_service/msgpack/external/boost/preprocessor/include/boost/preprocessor/arithmetic/add.hpp ADDED Viewed

@@ -0,0 +1,51 @@
+# /* Copyright (C) 2001
+#  * Housemarque Oy
+#  * http://www.housemarque.com
+#  *
+#  * 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)
+#  */
+#
+# /* Revised by Paul Mensonides (2002) */
+#
+# /* See http://www.boost.org for most recent version. */
+#
+# ifndef BOOST_PREPROCESSOR_ARITHMETIC_ADD_HPP
+# define BOOST_PREPROCESSOR_ARITHMETIC_ADD_HPP
+#
+# include <boost/preprocessor/arithmetic/dec.hpp>
+# include <boost/preprocessor/arithmetic/inc.hpp>
+# include <boost/preprocessor/config/config.hpp>
+# include <boost/preprocessor/control/while.hpp>
+# include <boost/preprocessor/tuple/elem.hpp>
+#
+# /* BOOST_PP_ADD */
+#
+# if ~BOOST_PP_CONFIG_FLAGS() & BOOST_PP_CONFIG_EDG()
+#    define BOOST_PP_ADD(x, y) BOOST_PP_TUPLE_ELEM(2, 0, BOOST_PP_WHILE(BOOST_PP_ADD_P, BOOST_PP_ADD_O, (x, y)))
+# else
+#    define BOOST_PP_ADD(x, y) BOOST_PP_ADD_I(x, y)
+#    define BOOST_PP_ADD_I(x, y) BOOST_PP_TUPLE_ELEM(2, 0, BOOST_PP_WHILE(BOOST_PP_ADD_P, BOOST_PP_ADD_O, (x, y)))
+# endif
+#
+# define BOOST_PP_ADD_P(d, xy) BOOST_PP_TUPLE_ELEM(2, 1, xy)
+#
+# if ~BOOST_PP_CONFIG_FLAGS() & BOOST_PP_CONFIG_MWCC()
+#    define BOOST_PP_ADD_O(d, xy) BOOST_PP_ADD_O_I xy
+# else
+#    define BOOST_PP_ADD_O(d, xy) BOOST_PP_ADD_O_I(BOOST_PP_TUPLE_ELEM(2, 0, xy), BOOST_PP_TUPLE_ELEM(2, 1, xy))
+# endif
+#
+# define BOOST_PP_ADD_O_I(x, y) (BOOST_PP_INC(x), BOOST_PP_DEC(y))
+#
+# /* BOOST_PP_ADD_D */
+#
+# if ~BOOST_PP_CONFIG_FLAGS() & BOOST_PP_CONFIG_EDG()
+#    define BOOST_PP_ADD_D(d, x, y) BOOST_PP_TUPLE_ELEM(2, 0, BOOST_PP_WHILE_ ## d(BOOST_PP_ADD_P, BOOST_PP_ADD_O, (x, y)))
+# else
+#    define BOOST_PP_ADD_D(d, x, y) BOOST_PP_ADD_D_I(d, x, y)
+#    define BOOST_PP_ADD_D_I(d, x, y) BOOST_PP_TUPLE_ELEM(2, 0, BOOST_PP_WHILE_ ## d(BOOST_PP_ADD_P, BOOST_PP_ADD_O, (x, y)))
+# endif
+#
+# endif

data/ext/enterprise_script_service/msgpack/external/boost/preprocessor/include/boost/preprocessor/arithmetic/dec.hpp ADDED Viewed

@@ -0,0 +1,289 @@
+# /* Copyright (C) 2001
+#  * Housemarque Oy
+#  * http://www.housemarque.com
+#  *
+#  * 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)
+#  */
+#
+# /* Revised by Paul Mensonides (2002) */
+#
+# /* See http://www.boost.org for most recent version. */
+#
+# ifndef BOOST_PREPROCESSOR_ARITHMETIC_DEC_HPP
+# define BOOST_PREPROCESSOR_ARITHMETIC_DEC_HPP
+#
+# include <boost/preprocessor/config/config.hpp>
+#
+# /* BOOST_PP_DEC */
+#
+# if ~BOOST_PP_CONFIG_FLAGS() & BOOST_PP_CONFIG_MWCC()
+#    define BOOST_PP_DEC(x) BOOST_PP_DEC_I(x)
+# else
+#    define BOOST_PP_DEC(x) BOOST_PP_DEC_OO((x))
+#    define BOOST_PP_DEC_OO(par) BOOST_PP_DEC_I ## par
+# endif
+#
+# define BOOST_PP_DEC_I(x) BOOST_PP_DEC_ ## x
+#
+# define BOOST_PP_DEC_0 0
+# define BOOST_PP_DEC_1 0
+# define BOOST_PP_DEC_2 1
+# define BOOST_PP_DEC_3 2
+# define BOOST_PP_DEC_4 3
+# define BOOST_PP_DEC_5 4
+# define BOOST_PP_DEC_6 5
+# define BOOST_PP_DEC_7 6
+# define BOOST_PP_DEC_8 7
+# define BOOST_PP_DEC_9 8
+# define BOOST_PP_DEC_10 9
+# define BOOST_PP_DEC_11 10
+# define BOOST_PP_DEC_12 11
+# define BOOST_PP_DEC_13 12
+# define BOOST_PP_DEC_14 13
+# define BOOST_PP_DEC_15 14
+# define BOOST_PP_DEC_16 15
+# define BOOST_PP_DEC_17 16
+# define BOOST_PP_DEC_18 17
+# define BOOST_PP_DEC_19 18
+# define BOOST_PP_DEC_20 19
+# define BOOST_PP_DEC_21 20
+# define BOOST_PP_DEC_22 21
+# define BOOST_PP_DEC_23 22
+# define BOOST_PP_DEC_24 23
+# define BOOST_PP_DEC_25 24
+# define BOOST_PP_DEC_26 25
+# define BOOST_PP_DEC_27 26
+# define BOOST_PP_DEC_28 27
+# define BOOST_PP_DEC_29 28
+# define BOOST_PP_DEC_30 29
+# define BOOST_PP_DEC_31 30
+# define BOOST_PP_DEC_32 31
+# define BOOST_PP_DEC_33 32
+# define BOOST_PP_DEC_34 33
+# define BOOST_PP_DEC_35 34
+# define BOOST_PP_DEC_36 35
+# define BOOST_PP_DEC_37 36
+# define BOOST_PP_DEC_38 37
+# define BOOST_PP_DEC_39 38
+# define BOOST_PP_DEC_40 39
+# define BOOST_PP_DEC_41 40
+# define BOOST_PP_DEC_42 41
+# define BOOST_PP_DEC_43 42
+# define BOOST_PP_DEC_44 43
+# define BOOST_PP_DEC_45 44
+# define BOOST_PP_DEC_46 45
+# define BOOST_PP_DEC_47 46
+# define BOOST_PP_DEC_48 47
+# define BOOST_PP_DEC_49 48
+# define BOOST_PP_DEC_50 49
+# define BOOST_PP_DEC_51 50
+# define BOOST_PP_DEC_52 51
+# define BOOST_PP_DEC_53 52
+# define BOOST_PP_DEC_54 53
+# define BOOST_PP_DEC_55 54
+# define BOOST_PP_DEC_56 55
+# define BOOST_PP_DEC_57 56
+# define BOOST_PP_DEC_58 57
+# define BOOST_PP_DEC_59 58
+# define BOOST_PP_DEC_60 59
+# define BOOST_PP_DEC_61 60
+# define BOOST_PP_DEC_62 61
+# define BOOST_PP_DEC_63 62
+# define BOOST_PP_DEC_64 63
+# define BOOST_PP_DEC_65 64
+# define BOOST_PP_DEC_66 65
+# define BOOST_PP_DEC_67 66
+# define BOOST_PP_DEC_68 67
+# define BOOST_PP_DEC_69 68
+# define BOOST_PP_DEC_70 69
+# define BOOST_PP_DEC_71 70
+# define BOOST_PP_DEC_72 71
+# define BOOST_PP_DEC_73 72
+# define BOOST_PP_DEC_74 73
+# define BOOST_PP_DEC_75 74
+# define BOOST_PP_DEC_76 75
+# define BOOST_PP_DEC_77 76
+# define BOOST_PP_DEC_78 77
+# define BOOST_PP_DEC_79 78
+# define BOOST_PP_DEC_80 79
+# define BOOST_PP_DEC_81 80
+# define BOOST_PP_DEC_82 81
+# define BOOST_PP_DEC_83 82
+# define BOOST_PP_DEC_84 83
+# define BOOST_PP_DEC_85 84
+# define BOOST_PP_DEC_86 85
+# define BOOST_PP_DEC_87 86
+# define BOOST_PP_DEC_88 87
+# define BOOST_PP_DEC_89 88
+# define BOOST_PP_DEC_90 89
+# define BOOST_PP_DEC_91 90
+# define BOOST_PP_DEC_92 91
+# define BOOST_PP_DEC_93 92
+# define BOOST_PP_DEC_94 93
+# define BOOST_PP_DEC_95 94
+# define BOOST_PP_DEC_96 95
+# define BOOST_PP_DEC_97 96
+# define BOOST_PP_DEC_98 97
+# define BOOST_PP_DEC_99 98
+# define BOOST_PP_DEC_100 99
+# define BOOST_PP_DEC_101 100
+# define BOOST_PP_DEC_102 101
+# define BOOST_PP_DEC_103 102
+# define BOOST_PP_DEC_104 103
+# define BOOST_PP_DEC_105 104
+# define BOOST_PP_DEC_106 105
+# define BOOST_PP_DEC_107 106
+# define BOOST_PP_DEC_108 107
+# define BOOST_PP_DEC_109 108
+# define BOOST_PP_DEC_110 109
+# define BOOST_PP_DEC_111 110
+# define BOOST_PP_DEC_112 111
+# define BOOST_PP_DEC_113 112
+# define BOOST_PP_DEC_114 113
+# define BOOST_PP_DEC_115 114
+# define BOOST_PP_DEC_116 115
+# define BOOST_PP_DEC_117 116
+# define BOOST_PP_DEC_118 117
+# define BOOST_PP_DEC_119 118
+# define BOOST_PP_DEC_120 119
+# define BOOST_PP_DEC_121 120
+# define BOOST_PP_DEC_122 121
+# define BOOST_PP_DEC_123 122
+# define BOOST_PP_DEC_124 123
+# define BOOST_PP_DEC_125 124
+# define BOOST_PP_DEC_126 125
+# define BOOST_PP_DEC_127 126
+# define BOOST_PP_DEC_128 127
+# define BOOST_PP_DEC_129 128
+# define BOOST_PP_DEC_130 129
+# define BOOST_PP_DEC_131 130
+# define BOOST_PP_DEC_132 131
+# define BOOST_PP_DEC_133 132
+# define BOOST_PP_DEC_134 133
+# define BOOST_PP_DEC_135 134
+# define BOOST_PP_DEC_136 135
+# define BOOST_PP_DEC_137 136
+# define BOOST_PP_DEC_138 137
+# define BOOST_PP_DEC_139 138
+# define BOOST_PP_DEC_140 139
+# define BOOST_PP_DEC_141 140
+# define BOOST_PP_DEC_142 141
+# define BOOST_PP_DEC_143 142
+# define BOOST_PP_DEC_144 143
+# define BOOST_PP_DEC_145 144
+# define BOOST_PP_DEC_146 145
+# define BOOST_PP_DEC_147 146
+# define BOOST_PP_DEC_148 147
+# define BOOST_PP_DEC_149 148
+# define BOOST_PP_DEC_150 149
+# define BOOST_PP_DEC_151 150
+# define BOOST_PP_DEC_152 151
+# define BOOST_PP_DEC_153 152
+# define BOOST_PP_DEC_154 153
+# define BOOST_PP_DEC_155 154
+# define BOOST_PP_DEC_156 155
+# define BOOST_PP_DEC_157 156
+# define BOOST_PP_DEC_158 157
+# define BOOST_PP_DEC_159 158
+# define BOOST_PP_DEC_160 159
+# define BOOST_PP_DEC_161 160
+# define BOOST_PP_DEC_162 161
+# define BOOST_PP_DEC_163 162
+# define BOOST_PP_DEC_164 163
+# define BOOST_PP_DEC_165 164
+# define BOOST_PP_DEC_166 165
+# define BOOST_PP_DEC_167 166
+# define BOOST_PP_DEC_168 167
+# define BOOST_PP_DEC_169 168
+# define BOOST_PP_DEC_170 169
+# define BOOST_PP_DEC_171 170
+# define BOOST_PP_DEC_172 171
+# define BOOST_PP_DEC_173 172
+# define BOOST_PP_DEC_174 173
+# define BOOST_PP_DEC_175 174
+# define BOOST_PP_DEC_176 175
+# define BOOST_PP_DEC_177 176
+# define BOOST_PP_DEC_178 177
+# define BOOST_PP_DEC_179 178
+# define BOOST_PP_DEC_180 179
+# define BOOST_PP_DEC_181 180
+# define BOOST_PP_DEC_182 181
+# define BOOST_PP_DEC_183 182
+# define BOOST_PP_DEC_184 183
+# define BOOST_PP_DEC_185 184
+# define BOOST_PP_DEC_186 185
+# define BOOST_PP_DEC_187 186
+# define BOOST_PP_DEC_188 187
+# define BOOST_PP_DEC_189 188
+# define BOOST_PP_DEC_190 189
+# define BOOST_PP_DEC_191 190
+# define BOOST_PP_DEC_192 191
+# define BOOST_PP_DEC_193 192
+# define BOOST_PP_DEC_194 193
+# define BOOST_PP_DEC_195 194
+# define BOOST_PP_DEC_196 195
+# define BOOST_PP_DEC_197 196
+# define BOOST_PP_DEC_198 197
+# define BOOST_PP_DEC_199 198
+# define BOOST_PP_DEC_200 199
+# define BOOST_PP_DEC_201 200
+# define BOOST_PP_DEC_202 201
+# define BOOST_PP_DEC_203 202
+# define BOOST_PP_DEC_204 203
+# define BOOST_PP_DEC_205 204
+# define BOOST_PP_DEC_206 205
+# define BOOST_PP_DEC_207 206
+# define BOOST_PP_DEC_208 207
+# define BOOST_PP_DEC_209 208
+# define BOOST_PP_DEC_210 209
+# define BOOST_PP_DEC_211 210
+# define BOOST_PP_DEC_212 211
+# define BOOST_PP_DEC_213 212
+# define BOOST_PP_DEC_214 213
+# define BOOST_PP_DEC_215 214
+# define BOOST_PP_DEC_216 215
+# define BOOST_PP_DEC_217 216
+# define BOOST_PP_DEC_218 217
+# define BOOST_PP_DEC_219 218
+# define BOOST_PP_DEC_220 219
+# define BOOST_PP_DEC_221 220
+# define BOOST_PP_DEC_222 221
+# define BOOST_PP_DEC_223 222
+# define BOOST_PP_DEC_224 223
+# define BOOST_PP_DEC_225 224
+# define BOOST_PP_DEC_226 225
+# define BOOST_PP_DEC_227 226
+# define BOOST_PP_DEC_228 227
+# define BOOST_PP_DEC_229 228
+# define BOOST_PP_DEC_230 229
+# define BOOST_PP_DEC_231 230
+# define BOOST_PP_DEC_232 231
+# define BOOST_PP_DEC_233 232
+# define BOOST_PP_DEC_234 233
+# define BOOST_PP_DEC_235 234
+# define BOOST_PP_DEC_236 235
+# define BOOST_PP_DEC_237 236
+# define BOOST_PP_DEC_238 237
+# define BOOST_PP_DEC_239 238
+# define BOOST_PP_DEC_240 239
+# define BOOST_PP_DEC_241 240
+# define BOOST_PP_DEC_242 241
+# define BOOST_PP_DEC_243 242
+# define BOOST_PP_DEC_244 243
+# define BOOST_PP_DEC_245 244
+# define BOOST_PP_DEC_246 245
+# define BOOST_PP_DEC_247 246
+# define BOOST_PP_DEC_248 247
+# define BOOST_PP_DEC_249 248
+# define BOOST_PP_DEC_250 249
+# define BOOST_PP_DEC_251 250
+# define BOOST_PP_DEC_252 251
+# define BOOST_PP_DEC_253 252
+# define BOOST_PP_DEC_254 253
+# define BOOST_PP_DEC_255 254
+# define BOOST_PP_DEC_256 255
+# define BOOST_PP_DEC_257 256
+#
+# endif