Boost-Commit :

Date view	Thread view	Subject view	Author view

Subject: [Boost-commit] svn:boost r71902 - in sandbox/local: boost/local libs/local/doc/html libs/local/doc/html/boost/local/function libs/local/doc/html/boost_local libs/local/doc/qbk
From: lorcaminiti_at_[hidden]
Date: 2011-05-12 13:30:53

Next message: phil_at_[hidden]: "[Boost-commit] svn:boost r71903 - sandbox/block_ptr/boost"
Previous message: antoshkka_at_[hidden]: "[Boost-commit] svn:boost r71901 - trunk/libs/conversion"

Author: lcaminiti
Date: 2011-05-12 13:30:50 EDT (Thu, 12 May 2011)
New Revision: 71902
URL: http://svn.boost.org/trac/boost/changeset/71902

Log:
Fixed docs.
Text files modified:
   sandbox/local/boost/local/block.hpp | 15 ++++++++++-
   sandbox/local/boost/local/exit.hpp | 15 ++++++++++-
   sandbox/local/boost/local/function.hpp | 22 ++++++++++++++--
   sandbox/local/libs/local/doc/html/BOOST_IDENTITY_TYPE.html | 2
   sandbox/local/libs/local/doc/html/BOOST_IDENTITY_VALUE.html | 2
   sandbox/local/libs/local/doc/html/BOOST_LOCAL_BLOCK.html | 8 +++--
   sandbox/local/libs/local/doc/html/BOOST_LOCAL_BLOCK_END.html | 2
   sandbox/local/libs/local/doc/html/BOOST_LOCAL_BLOCK_TPL.html | 2
   sandbox/local/libs/local/doc/html/BOOST_LOCAL_CONFIG_COMPLIANT.html | 2
   sandbox/local/libs/local/doc/html/BOOST_LOCAL_CONFIG_FUNCTION_ARITY_MAX.html | 2
   sandbox/local/libs/local/doc/html/BOOST_LOCAL_CONFIG_OVERLOAD_MAX.html | 2
   sandbox/local/libs/local/doc/html/BOOST_LOCAL_CONFIG_THIS_PARAM_NAME.html | 2
   sandbox/local/libs/local/doc/html/BOOST_LOCAL_EXIT.html | 8 +++--
   sandbox/local/libs/local/doc/html/BOOST_LOCAL_EXIT_END.html | 2
   sandbox/local/libs/local/doc/html/BOOST_LOCAL_EXIT_TPL.html | 2
   sandbox/local/libs/local/doc/html/BOOST_LOCAL_FUNCTION_NAME.html | 4 +-
   sandbox/local/libs/local/doc/html/BOOST_LOCAL_FUNCTION_PARAMS.html | 8 +++--
   sandbox/local/libs/local/doc/html/BOOST_LOCAL_FUNCTION_PARAMS_TPL.html | 2
   sandbox/local/libs/local/doc/html/BOOST_LOCAL_TYPEOF.html | 2
   sandbox/local/libs/local/doc/html/boost/local/function/overload.html | 22 ++++++++--------
   sandbox/local/libs/local/doc/html/boost_local/Advanced_Topics.html | 32 ++++++++++++------------
   sandbox/local/libs/local/doc/html/boost_local/Alternatives.html | 10 +++---
   sandbox/local/libs/local/doc/html/boost_local/Bibliography.html | 2
   sandbox/local/libs/local/doc/html/boost_local/Getting_Started.html | 15 ++++++-----
   sandbox/local/libs/local/doc/html/boost_local/Release_Notes.html | 13 ----------
   sandbox/local/libs/local/doc/html/boost_local/Tutorial.html | 52 ++++++++++++++++++++--------------------
   sandbox/local/libs/local/doc/html/index.html | 10 +++---
   sandbox/local/libs/local/doc/qbk/advanced_topics.qbk | 2
   sandbox/local/libs/local/doc/qbk/getting_started.qbk | 11 ++++---
   sandbox/local/libs/local/doc/qbk/local.qbk | 2
   sandbox/local/libs/local/doc/qbk/release_notes.qbk | 7 -----
   31 files changed, 154 insertions(+), 128 deletions(-)

Modified: sandbox/local/boost/local/block.hpp
==============================================================================
--- sandbox/local/boost/local/block.hpp (original)
+++ sandbox/local/boost/local/block.hpp 2011-05-12 13:30:50 EDT (Thu, 12 May 2011)
@@ -58,7 +58,7 @@
 * bound_list:
 * (bound_parameter1) (bound_parameter2) ...
 * bound_parameter:
- * [const] bind[&] variable_name
+ * [const] bind [(variable_type)] [&] variable_name
 * @endcode
 * Where the following lexical conventions have been used:
 * <c>token1 | token2</c> means either <c>token1</c> or <c>token2</c>;
@@ -96,6 +96,15 @@
 * to avoid portability issues.
 * }
 * @EndParams
+ *
+ * When the object <c>this</c> is specified as the name of the variable to
+ * bind, the body must use the special name <c>this_</c> to access the bound
+ * object.
+ * The special name <c>this_</c> is defined by the configuration macro
+ * @RefMacro{BOOST_LOCAL_CONFIG_THIS_PARAM_NAME}.
+ *
+ * Both the variadic and empty macro syntaxes are always disabled when the
+ * configuration macro @RefMacro{BOOST_LOCAL_CONFIG_COMPLIANT} is defined.
 *
 * @Note This macro cannot be used multiple times on the same line because it
 * internally uses the line number <c>__LINE__</c> to generate unique
@@ -103,7 +112,9 @@
 *
 * @See @RefSect{Tutorial} section, @RefSect2{Advanced_Topics, Advanced Topics}
 * section, @RefMacro{BOOST_LOCAL_BLOCK_TPL},
- * @RefMacro{BOOST_LOCAL_BLOCK_END}.
+ * @RefMacro{BOOST_LOCAL_BLOCK_END},
+ * @RefMacro{BOOST_LOCAL_CONFIG_THIS_PARAM_NAME},
+ * @RefMacro{BOOST_LOCAL_CONFIG_COMPLIANT}.
 */
#define BOOST_LOCAL_BLOCK(bindings) \
 BOOST_LOCAL_AUX_BLOCK(BOOST_LOCAL_FUNCTION_PARAMS, bindings)

Modified: sandbox/local/boost/local/exit.hpp
==============================================================================
--- sandbox/local/boost/local/exit.hpp (original)
+++ sandbox/local/boost/local/exit.hpp 2011-05-12 13:30:50 EDT (Thu, 12 May 2011)
@@ -60,7 +60,7 @@
 * bound_list:
 * (bound_parameter1) (bound_parameter2) ...
 * bound_parameter:
- * [const] bind[&] variable_name
+ * [const] bind [(variable_type)] [&] variable_name
 * @endcode
 * Where the following lexical conventions have been used:
 * <c>token1 | token2</c> means either <c>token1</c> or <c>token2</c>;
@@ -99,12 +99,23 @@
 * }
 * @EndParams
 *
+ * When the object <c>this</c> is specified as the name of the variable to
+ * bind, the body must use the special name <c>this_</c> to access the bound
+ * object.
+ * The special name <c>this_</c> is defined by the configuration macro
+ * @RefMacro{BOOST_LOCAL_CONFIG_THIS_PARAM_NAME}.
+ *
+ * Both the variadic and empty macro syntaxes are always disabled when the
+ * configuration macro @RefMacro{BOOST_LOCAL_CONFIG_COMPLIANT} is defined.
+ *
 * @Note This macro cannot be used multiple times on the same line because it
 * internally uses the line number <c>__LINE__</c> to generate unique
 * identifiers.
 *
 * @See @RefSect{Tutorial} section, @RefSect2{Advanced_Topics, Advanced Topics}
- * section, @RefMacro{BOOST_LOCAL_EXIT_TPL}, @RefMacro{BOOST_LOCAL_EXIT_END}.
+ * section, @RefMacro{BOOST_LOCAL_EXIT_TPL}, @RefMacro{BOOST_LOCAL_EXIT_END},
+ * @RefMacro{BOOST_LOCAL_CONFIG_THIS_PARAM_NAME},
+ * @RefMacro{BOOST_LOCAL_CONFIG_COMPLIANT}.
 */
#define BOOST_LOCAL_EXIT(binding_list) \
 BOOST_LOCAL_AUX_EXIT(BOOST_LOCAL_FUNCTION_PARAMS, binding_list)

Modified: sandbox/local/boost/local/function.hpp
==============================================================================
--- sandbox/local/boost/local/function.hpp (original)
+++ sandbox/local/boost/local/function.hpp 2011-05-12 13:30:50 EDT (Thu, 12 May 2011)
@@ -71,7 +71,7 @@
 * default_value:
 * default default_vale_expression
 * bound_parameter:
- * [const] bind[&] variable_name
+ * [const] bind [(variable_type)] [&] variable_name
 * @endcode
 * Where the following lexical conventions have been used:
 * <c>token1 | token2</c> means either <c>token1</c> or <c>token2</c>;
@@ -111,6 +111,18 @@
 * }
 * @EndParams
 *
+ * When the object <c>this</c> is specified as the name of the variable to
+ * bind, the body must use the special name <c>this_</c> to access the bound
+ * object.
+ * The special name <c>this_</c> is defined by the configuration macro
+ * @RefMacro{BOOST_LOCAL_CONFIG_THIS_PARAM_NAME}.
+ *
+ * The number of local function parameters (excluding bound variables) is
+ * specified by the configuration macro
+ * @RefMacro{BOOST_LOCAL_CONFIG_FUNCTION_ARITY_MAX}.
+ * Both the variadic and empty macro syntaxes are always disabled when the
+ * configuration macro @RefMacro{BOOST_LOCAL_CONFIG_COMPLIANT} is defined.
+ *
 * @Note Local functions are functors so they can be assigned to other functors
 * like <c>boost::function</c> (see Boost.Function).
 *
@@ -120,7 +132,10 @@
 *
 * @See @RefSect{Tutorial} section, @RefSect2{Advanced_Topics, Advanced Topics}
 * section, @RefMacro{BOOST_LOCAL_FUNCTION_PARAMS_TPL},
- * @RefMacro{BOOST_LOCAL_FUNCTION_NAME}, Boost.Function.
+ * @RefMacro{BOOST_LOCAL_FUNCTION_NAME},
+ * @RefMacro{BOOST_LOCAL_CONFIG_THIS_PARAM_NAME},
+ * @RefMacro{BOOST_LOCAL_CONFIG_FUNCTION_ARITY_MAX},
+ * @RefMacro{BOOST_LOCAL_CONFIG_COMPLIANT}, Boost.Function.
 */
#define BOOST_LOCAL_FUNCTION_PARAMS(parameters) \
 BOOST_LOCAL_AUX_FUNCTION_PARAMS(parameters, \
@@ -202,7 +217,8 @@
 * @EndParams
 *
 * @See @RefMacro{BOOST_LOCAL_FUNCTION_PARAMS}, @RefSect{Tutorial} section,
- * @RefSect2{Advanced_Topics, Advanced Topics} section.
+ * @RefSect2{Advanced_Topics, Advanced Topics} section,
+ * @RefMacro{BOOST_LOCAL_CONFIG_COMPLIANT}.
 */
#define BOOST_LOCAL_FUNCTION_NAME(name) \
 BOOST_LOCAL_AUX_FUNCTION_NAME(name)

Modified: sandbox/local/libs/local/doc/html/BOOST_IDENTITY_TYPE.html
==============================================================================
--- sandbox/local/libs/local/doc/html/BOOST_IDENTITY_TYPE.html (original)
+++ sandbox/local/libs/local/doc/html/BOOST_IDENTITY_TYPE.html 2011-05-12 13:30:50 EDT (Thu, 12 May 2011)
@@ -33,7 +33,7 @@

BOOST_IDENTITY_TYPE(parenthesized_type)</pre></div>
<div class="refsect1">
-<a name="id925188"></a><h2>Description</h2>
+<a name="id925518"></a><h2>Description</h2>
This macro expands to an expression that can be passed as a single macro parameter even if it contains commas and that evaluates to the specified type at compile-time (see the <a class="link" href="boost_local/Advanced_Topics.html" title="Advanced Topics"> Advanced Topics</a> section).
For example <code class="computeroutput">BOOST_IDENTITY_TYPE((std::map<int, double>))</code> can be passed as a single macro parameter when instead <code class="computeroutput">std::map<int, double></code> cannot (because it contains a comma not wrapped by round parenthesis so it will be interpreted as two separate macro parameters by the preprocessor).
Parameters:

Modified: sandbox/local/libs/local/doc/html/BOOST_IDENTITY_VALUE.html
==============================================================================
--- sandbox/local/libs/local/doc/html/BOOST_IDENTITY_VALUE.html (original)
+++ sandbox/local/libs/local/doc/html/BOOST_IDENTITY_VALUE.html 2011-05-12 13:30:50 EDT (Thu, 12 May 2011)
@@ -33,7 +33,7 @@

BOOST_IDENTITY_VALUE(parenthesized_value)</pre></div>
<div class="refsect1">
-<a name="id925329"></a><h2>Description</h2>
+<a name="id925659"></a><h2>Description</h2>
This macro expands to an expression that can be passed as a single macro parameter even if it contains commas and that evaluates to the specified value at run-time (see the <a class="link" href="boost_local/Advanced_Topics.html" title="Advanced Topics"> Advanced Topics</a> section).
For example <code class="computeroutput">BOOST_IDENTITY_VALUE((key_sizeof<int, double>::value))</code> can be passed as a single macro parameter when instead <code class="computeroutput">key_sizeof<int, double>::value</code> cannot (because it contains a comma not wrapped by round parenthesis so it will be interpreted as two separate macro parameters by the preprocessor).
Parameters:

Modified: sandbox/local/libs/local/doc/html/BOOST_LOCAL_BLOCK.html
==============================================================================
--- sandbox/local/libs/local/doc/html/BOOST_LOCAL_BLOCK.html (original)
+++ sandbox/local/libs/local/doc/html/BOOST_LOCAL_BLOCK.html 2011-05-12 13:30:50 EDT (Thu, 12 May 2011)
@@ -33,7 +33,7 @@

BOOST_LOCAL_BLOCK(bindings)</pre></div>
<div class="refsect1">
-<a name="id919879"></a><h2>Description</h2>
+<a name="id919852"></a><h2>Description</h2>
This macro must be used within a declarative context, it must be followed by the local block body code and then by the <code class="computeroutput"><a class="link" href="BOOST_LOCAL_BLOCK_END.html" title="Macro BOOST_LOCAL_BLOCK_END">BOOST_LOCAL_BLOCK_END</a></code> macro (see the Tutorial section): 
<pre class="programlisting"> { // Some declarative context.
 ...
@@ -61,7 +61,7 @@
 bound_list:
 (bound_parameter1) (bound_parameter2) ...
 bound_parameter:
- [const] bind[&] variable_name
+ [const] bind [(variable_type)] [&] variable_name
</pre> Where the following lexical conventions have been used: <code class="computeroutput">token1 | token2</code> means either <code class="computeroutput">token1</code> or <code class="computeroutput">token2</code>; <code class="computeroutput">[token]</code> means either <code class="computeroutput">token</code> or nothing (i.e., <code class="computeroutput">token</code> is optional).On C99 and later compilers which support variadic macros, the above grammar can be modified as follow to define the variadic macro syntax that can also be used to specify the variables in scope to bind: <pre xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="table-programlisting"> void_list:
 void
 bound_list:
@@ -73,8 +73,10 @@
</table></div>


+When the object <code class="computeroutput">this</code> is specified as the name of the variable to bind, the body must use the special name <code class="computeroutput">this_</code> to access the bound object. The special name <code class="computeroutput">this_</code> is defined by the configuration macro <code class="computeroutput"><a class="link" href="BOOST_LOCAL_CONFIG_THIS_PARAM_NAME.html" title="Macro BOOST_LOCAL_CONFIG_THIS_PARAM_NAME">BOOST_LOCAL_CONFIG_THIS_PARAM_NAME</a></code>.
+Both the variadic and empty macro syntaxes are always disabled when the configuration macro <code class="computeroutput"><a class="link" href="BOOST_LOCAL_CONFIG_COMPLIANT.html" title="Macro BOOST_LOCAL_CONFIG_COMPLIANT">BOOST_LOCAL_CONFIG_COMPLIANT</a></code> is defined.
Note: This macro cannot be used multiple times on the same line because it internally uses the line number <code class="computeroutput">__LINE__</code> to generate unique identifiers.
-See: <a class="link" href="boost_local/Tutorial.html" title="Tutorial">Tutorial</a> section, <a class="link" href="boost_local/Advanced_Topics.html" title="Advanced Topics"> Advanced Topics</a> section, <code class="computeroutput"><a class="link" href="BOOST_LOCAL_BLOCK_TPL.html" title="Macro BOOST_LOCAL_BLOCK_TPL">BOOST_LOCAL_BLOCK_TPL</a></code>, <code class="computeroutput"><a class="link" href="BOOST_LOCAL_BLOCK_END.html" title="Macro BOOST_LOCAL_BLOCK_END">BOOST_LOCAL_BLOCK_END</a></code>. 
+See: <a class="link" href="boost_local/Tutorial.html" title="Tutorial">Tutorial</a> section, <a class="link" href="boost_local/Advanced_Topics.html" title="Advanced Topics"> Advanced Topics</a> section, <code class="computeroutput"><a class="link" href="BOOST_LOCAL_BLOCK_TPL.html" title="Macro BOOST_LOCAL_BLOCK_TPL">BOOST_LOCAL_BLOCK_TPL</a></code>, <code class="computeroutput"><a class="link" href="BOOST_LOCAL_BLOCK_END.html" title="Macro BOOST_LOCAL_BLOCK_END">BOOST_LOCAL_BLOCK_END</a></code>, <code class="computeroutput"><a class="link" href="BOOST_LOCAL_CONFIG_THIS_PARAM_NAME.html" title="Macro BOOST_LOCAL_CONFIG_THIS_PARAM_NAME">BOOST_LOCAL_CONFIG_THIS_PARAM_NAME</a></code>, <code class="computeroutput"><a class="link" href="BOOST_LOCAL_CONFIG_COMPLIANT.html" title="Macro BOOST_LOCAL_CONFIG_COMPLIANT">BOOST_LOCAL_CONFIG_COMPLIANT</a></code>. 
</div>
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>

Modified: sandbox/local/libs/local/doc/html/BOOST_LOCAL_BLOCK_END.html
==============================================================================
--- sandbox/local/libs/local/doc/html/BOOST_LOCAL_BLOCK_END.html (original)
+++ sandbox/local/libs/local/doc/html/BOOST_LOCAL_BLOCK_END.html 2011-05-12 13:30:50 EDT (Thu, 12 May 2011)
@@ -33,7 +33,7 @@

BOOST_LOCAL_BLOCK_END</pre></div>
<div class="refsect1">
-<a name="id920618"></a><h2>Description</h2>
+<a name="id920697"></a><h2>Description</h2>
This macro must follow the local block body code <code class="computeroutput">{ ... }</code> as shown in the <code class="computeroutput"><a class="link" href="BOOST_LOCAL_BLOCK.html" title="Macro BOOST_LOCAL_BLOCK">BOOST_LOCAL_BLOCK</a></code> documentation.
Note: This macro cannot be used multiple times on the same line because it internally uses the line number <code class="computeroutput">__LINE__</code> to generate unique identifiers.
See: <code class="computeroutput"><a class="link" href="BOOST_LOCAL_BLOCK.html" title="Macro BOOST_LOCAL_BLOCK">BOOST_LOCAL_BLOCK</a></code>, <a class="link" href="boost_local/Tutorial.html" title="Tutorial">Tutorial</a> section.

Modified: sandbox/local/libs/local/doc/html/BOOST_LOCAL_BLOCK_TPL.html
==============================================================================
--- sandbox/local/libs/local/doc/html/BOOST_LOCAL_BLOCK_TPL.html (original)
+++ sandbox/local/libs/local/doc/html/BOOST_LOCAL_BLOCK_TPL.html 2011-05-12 13:30:50 EDT (Thu, 12 May 2011)
@@ -33,7 +33,7 @@

BOOST_LOCAL_BLOCK_TPL(bindings)</pre></div>
<div class="refsect1">
-<a name="id920543"></a><h2>Description</h2>
+<a name="id920623"></a><h2>Description</h2>
See: <code class="computeroutput"><a class="link" href="BOOST_LOCAL_BLOCK.html" title="Macro BOOST_LOCAL_BLOCK">BOOST_LOCAL_BLOCK</a></code>, <a class="link" href="boost_local/Tutorial.html" title="Tutorial">Tutorial</a> section. 
</div>
</div>

Modified: sandbox/local/libs/local/doc/html/BOOST_LOCAL_CONFIG_COMPLIANT.html
==============================================================================
--- sandbox/local/libs/local/doc/html/BOOST_LOCAL_CONFIG_COMPLIANT.html (original)
+++ sandbox/local/libs/local/doc/html/BOOST_LOCAL_CONFIG_COMPLIANT.html 2011-05-12 13:30:50 EDT (Thu, 12 May 2011)
@@ -33,7 +33,7 @@

BOOST_LOCAL_CONFIG_COMPLIANT</pre></div>
<div class="refsect1">
-<a name="id920790"></a><h2>Description</h2>
+<a name="id920870"></a><h2>Description</h2>
If programmers leave this configuration macro undefined, its default value is to be left not defined.
If this macro is defined, variadic macros and empty macro parameters are not used by this library. Using variadic macros and empty macro parameters allows this library to provide the variadic macro and empty macro syntaxes which some programmers might find more readable than the sequencing macro syntax (see <code class="computeroutput"><a class="link" href="BOOST_LOCAL_FUNCTION_PARAMS.html" title="Macro BOOST_LOCAL_FUNCTION_PARAMS">BOOST_LOCAL_FUNCTION_PARAMS</a></code>, <code class="computeroutput"><a class="link" href="BOOST_LOCAL_BLOCK.html" title="Macro BOOST_LOCAL_BLOCK">BOOST_LOCAL_BLOCK</a></code>, and <code class="computeroutput"><a class="link" href="BOOST_LOCAL_EXIT.html" title="Macro BOOST_LOCAL_EXIT">BOOST_LOCAL_EXIT</a></code>). If this configuration macro is defined then only the sequencing macro syntax is allowed (regardless of whether the compiler supports variadic and e
mpty macros or not).
Warning: The variadic and empty macro syntaxes are not supported by all C++ compilers so they should be used with care to avoid portability issues (and this configuration macro can be defined to disable them).

Modified: sandbox/local/libs/local/doc/html/BOOST_LOCAL_CONFIG_FUNCTION_ARITY_MAX.html
==============================================================================
--- sandbox/local/libs/local/doc/html/BOOST_LOCAL_CONFIG_FUNCTION_ARITY_MAX.html (original)
+++ sandbox/local/libs/local/doc/html/BOOST_LOCAL_CONFIG_FUNCTION_ARITY_MAX.html 2011-05-12 13:30:50 EDT (Thu, 12 May 2011)
@@ -33,7 +33,7 @@

BOOST_LOCAL_CONFIG_FUNCTION_ARITY_MAX</pre></div>
<div class="refsect1">
-<a name="id920995"></a><h2>Description</h2>
+<a name="id921075"></a><h2>Description</h2>
If programmers leave this configuration macro undefined, its default value is <code class="computeroutput">5</code>.
This only refers to the number of local function parameters and not to the number of bound variables in scope (the limit on the number of bound variables is instead the maximum size allowed for a Boost.Preprocessor sequences).
Warning: Increasing this number will increase compilation time.

Modified: sandbox/local/libs/local/doc/html/BOOST_LOCAL_CONFIG_OVERLOAD_MAX.html
==============================================================================
--- sandbox/local/libs/local/doc/html/BOOST_LOCAL_CONFIG_OVERLOAD_MAX.html (original)
+++ sandbox/local/libs/local/doc/html/BOOST_LOCAL_CONFIG_OVERLOAD_MAX.html 2011-05-12 13:30:50 EDT (Thu, 12 May 2011)
@@ -33,7 +33,7 @@

BOOST_LOCAL_CONFIG_OVERLOAD_MAX</pre></div>
<div class="refsect1">
-<a name="id921091"></a><h2>Description</h2>
+<a name="id921171"></a><h2>Description</h2>
If programmers leave this configuration macro undefined, its default value is <code class="computeroutput">6</code>.
This number must be greater or equal than 2 (because a single function cannot be overloaded by itself) otherwise the library will generate a compile-time error.
Warning: Increasing this number will increase compilation time when the header file <code class="computeroutput">"boost/local/function/overload.hpp"</code> is included.

Modified: sandbox/local/libs/local/doc/html/BOOST_LOCAL_CONFIG_THIS_PARAM_NAME.html
==============================================================================
--- sandbox/local/libs/local/doc/html/BOOST_LOCAL_CONFIG_THIS_PARAM_NAME.html (original)
+++ sandbox/local/libs/local/doc/html/BOOST_LOCAL_CONFIG_THIS_PARAM_NAME.html 2011-05-12 13:30:50 EDT (Thu, 12 May 2011)
@@ -33,7 +33,7 @@

BOOST_LOCAL_CONFIG_THIS_PARAM_NAME</pre></div>
<div class="refsect1">
-<a name="id921202"></a><h2>Description</h2>
+<a name="id921282"></a><h2>Description</h2>
If programmers leave this configuration macro undefined, the default symbol used is <code class="computeroutput">this_</code>.
Warning: Programmers should not define this macro unless it is absolutely necessary (e.g., to avoid name clashes with another library which cannot be changed). Changing the symbol <code class="computeroutput">this_</code> effectively changes the public API of this library.
See: <a class="link" href="boost_local/Tutorial.html" title="Tutorial">Tutorial</a> section, <a class="link" href="boost_local/Getting_Started.html" title="Getting Started"> Getting Started</a> section.

Modified: sandbox/local/libs/local/doc/html/BOOST_LOCAL_EXIT.html
==============================================================================
--- sandbox/local/libs/local/doc/html/BOOST_LOCAL_EXIT.html (original)
+++ sandbox/local/libs/local/doc/html/BOOST_LOCAL_EXIT.html 2011-05-12 13:30:50 EDT (Thu, 12 May 2011)
@@ -33,7 +33,7 @@

BOOST_LOCAL_EXIT(binding_list)</pre></div>
<div class="refsect1">
-<a name="id921351"></a><h2>Description</h2>
+<a name="id921431"></a><h2>Description</h2>
This macro must be used within a declarative context, it must be followed by the local exit body code and then by the <code class="computeroutput"><a class="link" href="BOOST_LOCAL_EXIT_END.html" title="Macro BOOST_LOCAL_EXIT_END">BOOST_LOCAL_EXIT_END</a></code> macro (see the <a class="link" href="boost_local/Tutorial.html" title="Tutorial">Tutorial</a> section): 
<pre class="programlisting"> { // Some declarative context.
 ...
@@ -61,7 +61,7 @@
 bound_list:
 (bound_parameter1) (bound_parameter2) ...
 bound_parameter:
- [const] bind[&] variable_name
+ [const] bind [(variable_type)] [&] variable_name
</pre> Where the following lexical conventions have been used: <code class="computeroutput">token1 | token2</code> means either <code class="computeroutput">token1</code> or <code class="computeroutput">token2</code>; <code class="computeroutput">[token]</code> means either <code class="computeroutput">token</code> or nothing (i.e., <code class="computeroutput">token</code> is optional).On C99 and later compilers which support variadic macros, the above grammar can be modified as follow to define the variadic macro syntax that can also be used to specify the variables in scope to bind: <pre xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="table-programlisting"> void_list:
 void
 bound_list:
@@ -73,8 +73,10 @@
</table></div>


+When the object <code class="computeroutput">this</code> is specified as the name of the variable to bind, the body must use the special name <code class="computeroutput">this_</code> to access the bound object. The special name <code class="computeroutput">this_</code> is defined by the configuration macro <code class="computeroutput"><a class="link" href="BOOST_LOCAL_CONFIG_THIS_PARAM_NAME.html" title="Macro BOOST_LOCAL_CONFIG_THIS_PARAM_NAME">BOOST_LOCAL_CONFIG_THIS_PARAM_NAME</a></code>.
+Both the variadic and empty macro syntaxes are always disabled when the configuration macro <code class="computeroutput"><a class="link" href="BOOST_LOCAL_CONFIG_COMPLIANT.html" title="Macro BOOST_LOCAL_CONFIG_COMPLIANT">BOOST_LOCAL_CONFIG_COMPLIANT</a></code> is defined.
Note: This macro cannot be used multiple times on the same line because it internally uses the line number <code class="computeroutput">__LINE__</code> to generate unique identifiers.
-See: <a class="link" href="boost_local/Tutorial.html" title="Tutorial">Tutorial</a> section, <a class="link" href="boost_local/Advanced_Topics.html" title="Advanced Topics"> Advanced Topics</a> section, <code class="computeroutput"><a class="link" href="BOOST_LOCAL_EXIT_TPL.html" title="Macro BOOST_LOCAL_EXIT_TPL">BOOST_LOCAL_EXIT_TPL</a></code>, <code class="computeroutput"><a class="link" href="BOOST_LOCAL_EXIT_END.html" title="Macro BOOST_LOCAL_EXIT_END">BOOST_LOCAL_EXIT_END</a></code>. 
+See: <a class="link" href="boost_local/Tutorial.html" title="Tutorial">Tutorial</a> section, <a class="link" href="boost_local/Advanced_Topics.html" title="Advanced Topics"> Advanced Topics</a> section, <code class="computeroutput"><a class="link" href="BOOST_LOCAL_EXIT_TPL.html" title="Macro BOOST_LOCAL_EXIT_TPL">BOOST_LOCAL_EXIT_TPL</a></code>, <code class="computeroutput"><a class="link" href="BOOST_LOCAL_EXIT_END.html" title="Macro BOOST_LOCAL_EXIT_END">BOOST_LOCAL_EXIT_END</a></code>, <code class="computeroutput"><a class="link" href="BOOST_LOCAL_CONFIG_THIS_PARAM_NAME.html" title="Macro BOOST_LOCAL_CONFIG_THIS_PARAM_NAME">BOOST_LOCAL_CONFIG_THIS_PARAM_NAME</a></code>, <code class="computeroutput"><a class="link" href="BOOST_LOCAL_CONFIG_COMPLIANT.html" title="Macro BOOST_LOCAL_CONFIG_COMPLIANT">BOOST_LOCAL_CONFIG_COMPLIANT</a></code>. 
</div>
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>

Modified: sandbox/local/libs/local/doc/html/BOOST_LOCAL_EXIT_END.html
==============================================================================
--- sandbox/local/libs/local/doc/html/BOOST_LOCAL_EXIT_END.html (original)
+++ sandbox/local/libs/local/doc/html/BOOST_LOCAL_EXIT_END.html 2011-05-12 13:30:50 EDT (Thu, 12 May 2011)
@@ -33,7 +33,7 @@

BOOST_LOCAL_EXIT_END</pre></div>
<div class="refsect1">
-<a name="id922101"></a><h2>Description</h2>
+<a name="id922288"></a><h2>Description</h2>
This macro must follow the local exit body code <code class="computeroutput">{ ... }</code> as shown in the <code class="computeroutput"><a class="link" href="BOOST_LOCAL_EXIT.html" title="Macro BOOST_LOCAL_EXIT">BOOST_LOCAL_EXIT</a></code> documentation.
Note: This macro cannot be used multiple times on the same line because it internally uses the line number <code class="computeroutput">__LINE__</code> to generate unique identifiers.
See: <code class="computeroutput"><a class="link" href="BOOST_LOCAL_EXIT.html" title="Macro BOOST_LOCAL_EXIT">BOOST_LOCAL_EXIT</a></code>, <a class="link" href="boost_local/Tutorial.html" title="Tutorial">Tutorial</a> section.

Modified: sandbox/local/libs/local/doc/html/BOOST_LOCAL_EXIT_TPL.html
==============================================================================
--- sandbox/local/libs/local/doc/html/BOOST_LOCAL_EXIT_TPL.html (original)
+++ sandbox/local/libs/local/doc/html/BOOST_LOCAL_EXIT_TPL.html 2011-05-12 13:30:50 EDT (Thu, 12 May 2011)
@@ -33,7 +33,7 @@

BOOST_LOCAL_EXIT_TPL(binding_list)</pre></div>
<div class="refsect1">
-<a name="id922027"></a><h2>Description</h2>
+<a name="id922214"></a><h2>Description</h2>
See: <code class="computeroutput"><a class="link" href="BOOST_LOCAL_EXIT.html" title="Macro BOOST_LOCAL_EXIT">BOOST_LOCAL_EXIT</a></code>, <a class="link" href="boost_local/Tutorial.html" title="Tutorial">Tutorial</a> section. 
</div>
</div>

Modified: sandbox/local/libs/local/doc/html/BOOST_LOCAL_FUNCTION_NAME.html
==============================================================================
--- sandbox/local/libs/local/doc/html/BOOST_LOCAL_FUNCTION_NAME.html (original)
+++ sandbox/local/libs/local/doc/html/BOOST_LOCAL_FUNCTION_NAME.html 2011-05-12 13:30:50 EDT (Thu, 12 May 2011)
@@ -33,7 +33,7 @@

BOOST_LOCAL_FUNCTION_NAME(name)</pre></div>
<div class="refsect1">
-<a name="id923226"></a><h2>Description</h2>
+<a name="id923547"></a><h2>Description</h2>
This macro must follow the local function body code block <code class="computeroutput">{ ... }</code> as shown in the <code class="computeroutput"><a class="link" href="BOOST_LOCAL_FUNCTION_PARAMS.html" title="Macro BOOST_LOCAL_FUNCTION_PARAMS">BOOST_LOCAL_FUNCTION_PARAMS</a></code> documentation.
The local function name can be prefixed by the "keyword" <code class="computeroutput">inline</code>: 
<pre class="programlisting"> ... BOOST_LOCAL_FUNCTION_NAME(inline name)
@@ -58,7 +58,7 @@
</table></div>


-See: <code class="computeroutput"><a class="link" href="BOOST_LOCAL_FUNCTION_PARAMS.html" title="Macro BOOST_LOCAL_FUNCTION_PARAMS">BOOST_LOCAL_FUNCTION_PARAMS</a></code>, <a class="link" href="boost_local/Tutorial.html" title="Tutorial">Tutorial</a> section, <a class="link" href="boost_local/Advanced_Topics.html" title="Advanced Topics"> Advanced Topics</a> section. 
+See: <code class="computeroutput"><a class="link" href="BOOST_LOCAL_FUNCTION_PARAMS.html" title="Macro BOOST_LOCAL_FUNCTION_PARAMS">BOOST_LOCAL_FUNCTION_PARAMS</a></code>, <a class="link" href="boost_local/Tutorial.html" title="Tutorial">Tutorial</a> section, <a class="link" href="boost_local/Advanced_Topics.html" title="Advanced Topics"> Advanced Topics</a> section, <code class="computeroutput"><a class="link" href="BOOST_LOCAL_CONFIG_COMPLIANT.html" title="Macro BOOST_LOCAL_CONFIG_COMPLIANT">BOOST_LOCAL_CONFIG_COMPLIANT</a></code>. 
</div>
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>

Modified: sandbox/local/libs/local/doc/html/BOOST_LOCAL_FUNCTION_PARAMS.html
==============================================================================
--- sandbox/local/libs/local/doc/html/BOOST_LOCAL_FUNCTION_PARAMS.html (original)
+++ sandbox/local/libs/local/doc/html/BOOST_LOCAL_FUNCTION_PARAMS.html 2011-05-12 13:30:50 EDT (Thu, 12 May 2011)
@@ -33,7 +33,7 @@

BOOST_LOCAL_FUNCTION_PARAMS(parameters)</pre></div>
<div class="refsect1">
-<a name="id922268"></a><h2>Description</h2>
+<a name="id922455"></a><h2>Description</h2>
This macro must be used within a declarative context, it must follow the local function result type, it must be followed by the local function body code and then by the <code class="computeroutput"><a class="link" href="BOOST_LOCAL_FUNCTION_NAME.html" title="Macro BOOST_LOCAL_FUNCTION_NAME">BOOST_LOCAL_FUNCTION_NAME</a></code> macro (see the <a class="link" href="boost_local/Tutorial.html" title="Tutorial">Tutorial</a> and <a class="link" href="boost_local/Advanced_Topics.html" title="Advanced Topics"> Advanced Topics</a> sections): 
<pre class="programlisting"> { // Some declarative context.
 ...
@@ -69,7 +69,7 @@
 default_value:
 default default_vale_expression
 bound_parameter:
- [const] bind[&] variable_name
+ [const] bind [(variable_type)] [&] variable_name
</pre> Where the following lexical conventions have been used: <code class="computeroutput">token1 | token2</code> means either <code class="computeroutput">token1</code> or <code class="computeroutput">token2</code>; <code class="computeroutput">[token]</code> means either <code class="computeroutput">token</code> or nothing (i.e., <code class="computeroutput">token</code> is optional).On C99 and later compilers which support variadic macros, the above grammar can be modified as follow to define the variadic macro syntax that can also be used to specify the local functions parameters: <pre xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="table-programlisting"> void_list:
 void
 parameter_list:
@@ -83,9 +83,11 @@
</table></div>


+When the object <code class="computeroutput">this</code> is specified as the name of the variable to bind, the body must use the special name <code class="computeroutput">this_</code> to access the bound object. The special name <code class="computeroutput">this_</code> is defined by the configuration macro <code class="computeroutput"><a class="link" href="BOOST_LOCAL_CONFIG_THIS_PARAM_NAME.html" title="Macro BOOST_LOCAL_CONFIG_THIS_PARAM_NAME">BOOST_LOCAL_CONFIG_THIS_PARAM_NAME</a></code>.
+The number of local function parameters (excluding bound variables) is specified by the configuration macro <code class="computeroutput"><a class="link" href="BOOST_LOCAL_CONFIG_FUNCTION_ARITY_MAX.html" title="Macro BOOST_LOCAL_CONFIG_FUNCTION_ARITY_MAX">BOOST_LOCAL_CONFIG_FUNCTION_ARITY_MAX</a></code>. Both the variadic and empty macro syntaxes are always disabled when the configuration macro <code class="computeroutput"><a class="link" href="BOOST_LOCAL_CONFIG_COMPLIANT.html" title="Macro BOOST_LOCAL_CONFIG_COMPLIANT">BOOST_LOCAL_CONFIG_COMPLIANT</a></code> is defined.
Note: Local functions are functors so they can be assigned to other functors like <code class="computeroutput">boost::function</code> (see Boost.Function).
Note: This macro cannot be used multiple times on the same line because it internally uses the line number <code class="computeroutput">__LINE__</code> to generate unique identifiers.
-See: <a class="link" href="boost_local/Tutorial.html" title="Tutorial">Tutorial</a> section, <a class="link" href="boost_local/Advanced_Topics.html" title="Advanced Topics"> Advanced Topics</a> section, <code class="computeroutput"><a class="link" href="BOOST_LOCAL_FUNCTION_PARAMS_TPL.html" title="Macro BOOST_LOCAL_FUNCTION_PARAMS_TPL">BOOST_LOCAL_FUNCTION_PARAMS_TPL</a></code>, <code class="computeroutput"><a class="link" href="BOOST_LOCAL_FUNCTION_NAME.html" title="Macro BOOST_LOCAL_FUNCTION_NAME">BOOST_LOCAL_FUNCTION_NAME</a></code>, Boost.Function. 
+See: <a class="link" href="boost_local/Tutorial.html" title="Tutorial">Tutorial</a> section, <a class="link" href="boost_local/Advanced_Topics.html" title="Advanced Topics"> Advanced Topics</a> section, <code class="computeroutput"><a class="link" href="BOOST_LOCAL_FUNCTION_PARAMS_TPL.html" title="Macro BOOST_LOCAL_FUNCTION_PARAMS_TPL">BOOST_LOCAL_FUNCTION_PARAMS_TPL</a></code>, <code class="computeroutput"><a class="link" href="BOOST_LOCAL_FUNCTION_NAME.html" title="Macro BOOST_LOCAL_FUNCTION_NAME">BOOST_LOCAL_FUNCTION_NAME</a></code>, <code class="computeroutput"><a class="link" href="BOOST_LOCAL_CONFIG_THIS_PARAM_NAME.html" title="Macro BOOST_LOCAL_CONFIG_THIS_PARAM_NAME">BOOST_LOCAL_CONFIG_THIS_PARAM_NAME</a></code>, <code class="computeroutput"><a class="link" href="BOOST_LOCAL_CONFIG_FUNCTION_ARITY_MAX.html" title="Macro BOOST_LOCAL_CONFIG_FUNCTION_ARITY_MAX">BOOST_LOCAL_CONFIG_FUNCTION_ARITY_MAX</a></code>, <code class="computeroutput"><a class="li
nk" href="BOOST_LOCAL_CONFIG_COMPLIANT.html" title="Macro BOOST_LOCAL_CONFIG_COMPLIANT">BOOST_LOCAL_CONFIG_COMPLIANT</a></code>, Boost.Function. 
</div>
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>

Modified: sandbox/local/libs/local/doc/html/BOOST_LOCAL_FUNCTION_PARAMS_TPL.html
==============================================================================
--- sandbox/local/libs/local/doc/html/BOOST_LOCAL_FUNCTION_PARAMS_TPL.html (original)
+++ sandbox/local/libs/local/doc/html/BOOST_LOCAL_FUNCTION_PARAMS_TPL.html 2011-05-12 13:30:50 EDT (Thu, 12 May 2011)
@@ -33,7 +33,7 @@

BOOST_LOCAL_FUNCTION_PARAMS_TPL(parameters)</pre></div>
<div class="refsect1">
-<a name="id923151"></a><h2>Description</h2>
+<a name="id923472"></a><h2>Description</h2>
See: <code class="computeroutput"><a class="link" href="BOOST_LOCAL_FUNCTION_PARAMS.html" title="Macro BOOST_LOCAL_FUNCTION_PARAMS">BOOST_LOCAL_FUNCTION_PARAMS</a></code>, <a class="link" href="boost_local/Tutorial.html" title="Tutorial">Tutorial</a> section. 
</div>
</div>

Modified: sandbox/local/libs/local/doc/html/BOOST_LOCAL_TYPEOF.html
==============================================================================
--- sandbox/local/libs/local/doc/html/BOOST_LOCAL_TYPEOF.html (original)
+++ sandbox/local/libs/local/doc/html/BOOST_LOCAL_TYPEOF.html 2011-05-12 13:30:50 EDT (Thu, 12 May 2011)
@@ -33,7 +33,7 @@

BOOST_LOCAL_TYPEOF(bound_variable_name)</pre></div>
<div class="refsect1">
-<a name="id924860"></a><h2>Description</h2>
+<a name="id925190"></a><h2>Description</h2>
The type is fully qualified in that it contains the extra constant and reference qualifiers when they are specified for binding by constant and by reference. For example, if a variable named <code class="computeroutput">t</code> of type <code class="computeroutput">T</code> is: 
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">Bound by value using <code class="computeroutput">bind t</code> then <code class="computeroutput">BOOST_LOCAL_TYPEOF(t)</code> is <code class="computeroutput">T</code>. </li>

Modified: sandbox/local/libs/local/doc/html/boost/local/function/overload.html
==============================================================================
--- sandbox/local/libs/local/doc/html/boost/local/function/overload.html (original)
+++ sandbox/local/libs/local/doc/html/boost/local/function/overload.html 2011-05-12 13:30:50 EDT (Thu, 12 May 2011)
@@ -35,35 +35,35 @@
class <a class="link" href="overload.html" title="Class template overload">overload</a> {
public:
 // <a class="link" href="overload.html#boost.local.function.overloadconstruct-copy-destruct">construct/copy/destruct</a>
- <a class="link" href="overload.html#id429472-bb">overload</a>(const boost::function< F0 > &, const boost::function< F1 > &, ...);
+ <a class="link" href="overload.html#id429786-bb">overload</a>(const boost::function< F0 > &, const boost::function< F1 > &, ...);

- // <a class="link" href="overload.html#id429393-bb">public member functions</a>
- result_type< F0 > <a class="link" href="overload.html#id429397-bb">operator()</a>(arg0_type< F0 >, arg1_type< F0 >, ...) const;
- result_type< F1 > <a class="link" href="overload.html#id429434-bb">operator()</a>(arg0_type< F1 >, arg1_type< F1 >, ...) const;
+ // <a class="link" href="overload.html#id429708-bb">public member functions</a>
+ result_type< F0 > <a class="link" href="overload.html#id429712-bb">operator()</a>(arg0_type< F0 >, arg1_type< F0 >, ...) const;
+ result_type< F1 > <a class="link" href="overload.html#id429749-bb">operator()</a>(arg0_type< F1 >, arg1_type< F1 >, ...) const;
};</pre></div>
<div class="refsect1">
-<a name="id924221"></a><h2>Description</h2>
+<a name="id924552"></a><h2>Description</h2>
This functor aggregates together calls to functions of all the specified types.
The maximum number of overloaded function types is specified by the <code class="computeroutput"><a class="link" href="../../../BOOST_LOCAL_CONFIG_OVERLOAD_MAX.html" title="Macro BOOST_LOCAL_CONFIG_OVERLOAD_MAX">BOOST_LOCAL_CONFIG_OVERLOAD_MAX</a></code> configuration macro. The maximum number of function parameters for each of the specified function type is specified by the <code class="computeroutput"><a class="link" href="../../../BOOST_LOCAL_CONFIG_OVERLOAD_MAX.html" title="Macro BOOST_LOCAL_CONFIG_OVERLOAD_MAX">BOOST_LOCAL_CONFIG_OVERLOAD_MAX</a></code> configuration macro.
See: <a class="link" href="../../../boost_local/Advanced_Topics.html" title="Advanced Topics"> Advanced Topics</a> section, <code class="computeroutput"><a class="link" href="../../../BOOST_LOCAL_CONFIG_OVERLOAD_MAX.html" title="Macro BOOST_LOCAL_CONFIG_OVERLOAD_MAX">BOOST_LOCAL_CONFIG_OVERLOAD_MAX</a></code>, <code class="computeroutput"><a class="link" href="../../../BOOST_LOCAL_CONFIG_OVERLOAD_MAX.html" title="Macro BOOST_LOCAL_CONFIG_OVERLOAD_MAX">BOOST_LOCAL_CONFIG_OVERLOAD_MAX</a></code>. 
<div class="refsect2">
-<a name="id924301"></a><h3>
+<a name="id924631"></a><h3>
<a name="boost.local.function.overloadconstruct-copy-destruct"></a><code class="computeroutput">overload</code>
 public
 construct/copy/destruct</h3>
<div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
-<pre class="literallayout"><a name="id429472-bb"></a>overload(const boost::function< F0 > &, const boost::function< F1 > &, ...);</pre>Construct the overloading functor. Any functor that can be converted to a <code class="computeroutput">boost::function</code> funcotr can be specified (local functions, functio
n pointers, other functors, etc). 
+<pre class="literallayout"><a name="id429786-bb"></a>overload(const boost::function< F0 > &, const boost::function< F1 > &, ...);</pre>Construct the overloading functor. Any functor that can be converted to a <code class="computeroutput">boost::function</code> funcotr can be specified (local functions, functio
n pointers, other functors, etc). 
</li></ol></div>
</div>
<div class="refsect2">
-<a name="id924476"></a><h3>
-<a name="id429393-bb"></a><code class="computeroutput">overload</code> public member functions</h3>
+<a name="id924807"></a><h3>
+<a name="id429708-bb"></a><code class="computeroutput">overload</code> public member functions</h3>
<div class="orderedlist"><ol class="orderedlist" type="1">
<li class="listitem">
-<pre class="literallayout">result_type< F0 > <a name="id429397-bb"></a>operator()(arg0_type< F0 >, arg1_type< F0 >, ...) const;</pre>Call operator matching the signature of the first specified functor. This will in turn invoke the call operator of the first functor that was passed to the constructor. 
+<pre class="literallayout">result_type< F0 > <a name="id429712-bb"></a>operator()(arg0_type< F0 >, arg1_type< F0 >, ...) const;</pre>Call operator matching the signature of the first specified functor. This will in turn invoke the call operator of the first functor that was passed to the constructor. 
</li>
<li class="listitem">
-<pre class="literallayout">result_type< F1 > <a name="id429434-bb"></a>operator()(arg0_type< F1 >, arg1_type< F1 >, ...) const;</pre>Call operator matching the signature of the second specified functor. This will in turn invoke the call operator of the second functor that was passed to the constructor. 
+<pre class="literallayout">result_type< F1 > <a name="id429749-bb"></a>operator()(arg0_type< F1 >, arg1_type< F1 >, ...) const;</pre>Call operator matching the signature of the second specified functor. This will in turn invoke the call operator of the second functor that was passed to the constructor. 
</li>
</ol></div>
</div>

Modified: sandbox/local/libs/local/doc/html/boost_local/Advanced_Topics.html
==============================================================================
--- sandbox/local/libs/local/doc/html/boost_local/Advanced_Topics.html (original)
+++ sandbox/local/libs/local/doc/html/boost_local/Advanced_Topics.html 2011-05-12 13:30:50 EDT (Thu, 12 May 2011)
@@ -86,7 +86,7 @@

 In addition, local function parameter types cannot start with non-alphanumeric
 symbols (alphanumeric symbols are <code class="computeroutput">A-Z</code>, <code class="computeroutput">a-z</code>,
- and <code class="computeroutput">0-9</code>). [<a name="id881800" href="#ftn.id881800" class="footnote">16</a>] The library will generate (cryptic) preprocessor errors if a
+ and <code class="computeroutput">0-9</code>). [<a name="id881778" href="#ftn.id881778" class="footnote">16</a>] The library will generate (cryptic) preprocessor errors if a
 parameter type starts with a non-alphanumeric symbol.
 

@@ -225,7 +225,7 @@
<li class="listitem">
 Parenthesis to wrap the type expression (and therefore any commas <code class="computeroutput">,</code> that it contains) passed as parameter
 to the <code class="computeroutput"><a class="link" href="../BOOST_IDENTITY_TYPE.html" title="Macro BOOST_IDENTITY_TYPE">BOOST_IDENTITY_TYPE</a></code>
- macro. [<a name="id883236" href="#ftn.id883236" class="footnote">17</a>]
+ macro. [<a name="id883215" href="#ftn.id883215" class="footnote">17</a>]
 </li>
</ol></div>
<div class="note"><table border="0" summary="Note">
@@ -1358,7 +1358,7 @@
 the <a class="link" href="Alternatives.html" title="Appendix: Alternatives">Alternatives</a> section).
 However, inlined local functions have the limitation that they cannot be
 assigned to other functors (like <code class="computeroutput">boost::function</code>)
- and they cannot be passed as template parameters. [<a name="id903847" href="#ftn.id903847" class="footnote">18</a>] On C++0x compilers, <code class="computeroutput">inline</code>
+ and they cannot be passed as template parameters. [<a name="id903826" href="#ftn.id903826" class="footnote">18</a>] On C++0x compilers, <code class="computeroutput">inline</code>
 has no effect because this library will automatically generate code that
 uses C++0x specific features to inline the local function calls whenever
 possible even if the local function is not declared inlined (unless the
@@ -1629,7 +1629,7 @@

 It is possible to overload local functions by creating a <code class="computeroutput"><a class="link" href="../boost/local/function/overload.html" title="Class template overload">boost::local::function::overload</a></code>
 functor that aggregates together calls to different local functions with
- different signatures. Note that the header file <code class="computeroutput">"boost/local/function/overload.hpp"</code>
+ different signatures. Note that the header file <code class="computeroutput"><a class="link" href="../reference.html#header.boost.local.function.overload_hpp" title="Header <boost/local/function/overload.hpp>">boost/local/function/overload.hpp</a></code>
 needs to be included when using the <code class="computeroutput"><a class="link" href="../boost/local/function/overload.html" title="Class template overload">boost::local::function::overload</a></code>
 functor.
 
@@ -1800,7 +1800,7 @@
 functor can be constructed from any function type that can be converted to
 a <code class="computeroutput">boost::function</code>
 type (i.e., local functions but also function pointers and other function
- objects). [<a name="id912742" href="#ftn.id912742" class="footnote">19</a>] The <code class="computeroutput"><a class="link" href="../boost/local/function/overload.html" title="Class template overload">boost::local::function::overload</a></code>
+ objects). [<a name="id912714" href="#ftn.id912714" class="footnote">19</a>] The <code class="computeroutput"><a class="link" href="../boost/local/function/overload.html" title="Class template overload">boost::local::function::overload</a></code>
 functor provides overloaded call operators <code class="computeroutput">operator()</code> that match the signatures of all the specified
 function types.
 
@@ -2080,7 +2080,7 @@

 Local function parameters support the storage classifiers as usual in ISO
 C++. The <code class="computeroutput">auto</code> storage classifier
- is specified as: [<a name="id917355" href="#ftn.id917355" class="footnote">20</a>]
+ is specified as: [<a name="id917328" href="#ftn.id917328" class="footnote">20</a>]
 
<pre class="programlisting">auto parameter-type parameter-name
</pre>
@@ -2310,7 +2310,7 @@
<td>
 
 This is not supported because local functions are not member functions.
- [<a name="id918607" href="#ftn.id918607" class="footnote">a</a>]
+ [<a name="id918580" href="#ftn.id918580" class="footnote">a</a>]
 
 </td>
</tr>
@@ -2409,7 +2409,7 @@
 </td>
</tr>
</tbody>
-<tbody class="footnotes"><tr><td colspan="3"><div class="footnote">[<a id="ftn.id918607" href="#id918607" class="para">a</a>] 
+<tbody class="footnotes"><tr><td colspan="3"><div class="footnote">[<a id="ftn.id918580" href="#id918580" class="para">a</a>] 
 Rationale. In theory, it would
 be possible for a local functor class to inherit from another
 local functor class. However, this "inheritance" feature
@@ -2425,7 +2425,7 @@
 </h6>

 Local functions cannot be operators. Naming a local function <code class="computeroutput">operator...</code>
- will generate a compile-time error. [<a name="id918953" href="#ftn.id918953" class="footnote">21</a>]
+ will generate a compile-time error. [<a name="id918926" href="#ftn.id918926" class="footnote">21</a>]
 

 For example, the following code will not
@@ -2477,21 +2477,21 @@
</div>
<div class="footnotes">
 <hr width="100" align="left">
-<div class="footnote">[<a id="ftn.id881800" href="#id881800" class="para">16</a>] 
+<div class="footnote">[<a id="ftn.id881778" href="#id881778" class="para">16</a>] 
 Rationale. This limitation derives from
 the fact that <code class="computeroutput"><a class="link" href="../BOOST_LOCAL_FUNCTION_PARAMS.html" title="Macro BOOST_LOCAL_FUNCTION_PARAMS">BOOST_LOCAL_FUNCTION_PARAMS</a></code>
 uses preprocessor token concatenation to inspect the parameter type token
 to see if the token is a parameter or a bound variable. The C++ preprocessor
 does not allow to concatenate non-alphanumeric tokens.
 </div>
-<div class="footnote">[<a id="ftn.id883236" href="#id883236" class="para">17</a>] 
+<div class="footnote">[<a id="ftn.id883215" href="#id883215" class="para">17</a>] 
 Rationale. Using variadic macros,
 this extra set of parenthesis could be eliminated requiring only the
 parenthesis to invoke the <code class="computeroutput"><a class="link" href="../BOOST_IDENTITY_TYPE.html" title="Macro BOOST_IDENTITY_TYPE">BOOST_IDENTITY_TYPE</a></code>
 macro. However, this feature is currently not implemented and the double
 parenthesis are always needed when invoking this macro.
 </div>
-<div class="footnote">[<a id="ftn.id903847" href="#id903847" class="para">18</a>] 
+<div class="footnote">[<a id="ftn.id903826" href="#id903826" class="para">18</a>] 
 Rationale. This library uses an indirect
 function call via a function pointer in order to pass the local function
 as a template parameter (see the <a class="link" href="Implementation.html" title="Appendix: Implementation">Implementation</a>
@@ -2500,12 +2500,12 @@
 local functions do not use such indirect function pointer call (so they
 are more likely to be optimized) but because of that they cannot be passed
 as template parameters. The indirect function pointer call is needed on
- ISO C++ but it is not needed on C++0x (see [2657])
+ ISO C++ but it is not needed on C++0x (see [N2657])
 thus this library automatically generates local function calls that can
 be inlined on C++0x compilers (even when the local function is not declared
 inlined).
 </div>
-<div class="footnote">[<a id="ftn.id912742" href="#id912742" class="para">19</a>] 
+<div class="footnote">[<a id="ftn.id912714" href="#id912714" class="para">19</a>] 
 The <code class="computeroutput"><a class="link" href="../boost/local/function/overload.html" title="Class template overload">boost::local::function::overload</a></code>
 functor can aggregate any functor and it is not at all specific to local
 functions. Therefore, it might be preferable to move <code class="computeroutput"><a class="link" href="../boost/local/function/overload.html" title="Class template overload">boost::local::function::overload</a></code>
@@ -2513,7 +2513,7 @@
 to Boost.Function
 and to rename it as <code class="computeroutput">boost::function::overload</code>.
 </div>
-<div class="footnote">[<a id="ftn.id917355" href="#id917355" class="para">20</a>] 
+<div class="footnote">[<a id="ftn.id917328" href="#id917328" class="para">20</a>] 
 The <code class="computeroutput">auto</code> storage classifier
 is part of the ISO C++ standard and therefore supported by this library.
 However, the meaning and usage of the <code class="computeroutput">auto</code>
@@ -2521,7 +2521,7 @@
 storage classifier with the usual care in order to avoid writing ISO C++
 code that might not work on C++0x.
 </div>
-<div class="footnote">[<a id="ftn.id918953" href="#id918953" class="para">21</a>] 
+<div class="footnote">[<a id="ftn.id918926" href="#id918926" class="para">21</a>] 
 Rationale. This is the because a local
 function name must be a valid local variable name (the local variable to
 hold the local functor) and operators cannot be used as local variable

Modified: sandbox/local/libs/local/doc/html/boost_local/Alternatives.html
==============================================================================
--- sandbox/local/libs/local/doc/html/boost_local/Alternatives.html (original)
+++ sandbox/local/libs/local/doc/html/boost_local/Alternatives.html 2011-05-12 13:30:50 EDT (Thu, 12 May 2011)
@@ -216,7 +216,7 @@
<td>
 
 Yes. The ISO C++ standard does not allow to pass local types as
- template parameters (see [2657])
+ template parameters (see [N2657])
 but this library implements a "trick" to get around this
 limitation (see the <a class="link" href="Implementation.html" title="Appendix: Implementation">Implementation</a>
 section).
@@ -225,7 +225,7 @@
<td>
 
 No on ISO C++ compilers (but yes on C++0x compilers and some compilers
- like MSVC 8.0, see [2657]).
+ like MSVC 8.0, see [N2657]).
 
 </td>
<td>
@@ -644,7 +644,7 @@
 compiler optimization is enabled (using <code class="computeroutput">bjam
 release ...</code>).
 However, on compilers that allow to pass local types as template parameters
- (e.g., MSVC 8.0 or GCC 4.5.1 with C++0x features enabled, see also [2657])
+ (e.g., MSVC 8.0 or GCC 4.5.1 with C++0x features enabled, see also [N2657])
 this library generates optimized code that runs as fast as the fastest of
 the other approaches (see "Boost.Local"
 below). When this library local function is specified <code class="computeroutput">inline</code>
@@ -652,7 +652,7 @@
 Inline For-Loop" below) its run-times are always comparable to both
 the "Local Functor" and "Global Functor" approaches (for
 all these approaches, the local function cannot be portably passed as template
- parameter, see [2657],
+ parameter, see [N2657],
 so <code class="computeroutput">std::for_each</code> is replaced by a for-loop). Finally,
 this library run-times are always among the fastest when no compiler optimization
 is enabled (using <code class="computeroutput">bjam debug
@@ -668,7 +668,7 @@
 The run-time performance of this library local function is explained because
 on ISO C++ compliant compilers (e.g., GCC 4.3.4) this library needs to
 use a function pointer in order to pass the local functor class as a template
- parameter (see [2657]
+ parameter (see [N2657]
 and the <a class="link" href="Implementation.html" title="Appendix: Implementation">Implementation</a>
 section). For all tested compilers, this function pointer prevents the
 compiler optimization algorithms from inlining all the function calls.

Modified: sandbox/local/libs/local/doc/html/boost_local/Bibliography.html
==============================================================================
--- sandbox/local/libs/local/doc/html/boost_local/Bibliography.html (original)
+++ sandbox/local/libs/local/doc/html/boost_local/Bibliography.html 2011-05-12 13:30:50 EDT (Thu, 12 May 2011)
@@ -47,7 +47,7 @@
 Standards Committee, document no. N2550=08-0060, 2008.
 

- [2657]
+ [N2657]
 John Spicer. Local and Unamed Types as Template Arguments.
 The C++ Standard Committee, document no. NN2657-08-0167, 2008.

Modified: sandbox/local/libs/local/doc/html/boost_local/Getting_Started.html
==============================================================================
--- sandbox/local/libs/local/doc/html/boost_local/Getting_Started.html (original)
+++ sandbox/local/libs/local/doc/html/boost_local/Getting_Started.html 2011-05-12 13:30:50 EDT (Thu, 12 May 2011)
@@ -114,15 +114,16 @@

 The header files of this library are divided as follow:
 
-<pre class="programlisting"><code class="computeroutput"><a class="link" href="../reference.html#header.boost.local.function_hpp" title="Header <boost/local/function.hpp>">boost/local/function.hpp</a></code> local functions
-<code class="computeroutput"><a class="link" href="../reference.html#header.boost.local.block_hpp" title="Header <boost/local/block.hpp>">boost/local/block.hpp</a></code> local blocks
-<code class="computeroutput"><a class="link" href="../reference.html#header.boost.local.exit_hpp" title="Header <boost/local/exit.hpp>">boost/local/exit.hpp</a></code> local exits
-<code class="computeroutput"><a class="link" href="../reference.html#header.boost.local.typeof_hpp" title="Header <boost/local/typeof.hpp>">boost/local/typeof.hpp</a></code> bound variable type deduction
-<code class="computeroutput"><a class="link" href="../reference.html#header.boost.local.config_hpp" title="Header <boost/local/config.hpp>">boost/local/config.hpp</a></code> library configuration macros
+<pre class="programlisting"><code class="computeroutput"><a class="link" href="../reference.html#header.boost.local.function_hpp" title="Header <boost/local/function.hpp>">boost/local/function.hpp</a></code> local functions
+<code class="computeroutput"><a class="link" href="../reference.html#header.boost.local.function.overload_hpp" title="Header <boost/local/function/overload.hpp>">boost/local/function/overload.hpp</a></code> local function overloading
+<code class="computeroutput"><a class="link" href="../reference.html#header.boost.local.block_hpp" title="Header <boost/local/block.hpp>">boost/local/block.hpp</a></code> local blocks
+<code class="computeroutput"><a class="link" href="../reference.html#header.boost.local.exit_hpp" title="Header <boost/local/exit.hpp>">boost/local/exit.hpp</a></code> local exits
+<code class="computeroutput"><a class="link" href="../reference.html#header.boost.local.typeof_hpp" title="Header <boost/local/typeof.hpp>">boost/local/typeof.hpp</a></code> bound variable type deduction
+<code class="computeroutput"><a class="link" href="../reference.html#header.boost.local.config_hpp" title="Header <boost/local/config.hpp>">boost/local/config.hpp</a></code> library configuration macros
</pre>

 The followings are part of the library private API, they are not documented,
- and they should not be directly used by programmers: [<a name="id866222" href="#ftn.id866222" class="footnote">2</a>]
+ and they should not be directly used by programmers: [<a name="id866200" href="#ftn.id866200" class="footnote">2</a>]
 
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
@@ -160,7 +161,7 @@
</div>
<div class="footnotes">
 <hr width="100" align="left">
-<div class="footnote">[<a id="ftn.id866222" href="#id866222" class="para">2</a>] 
+<div class="footnote">[<a id="ftn.id866200" href="#id866200" class="para">2</a>] 
 Rationale. This library concatenates symbols
 specified by the programmers (e.g., the local function name) with other
 symbols (e.g., special prefixes or preprocessor line numbers) to make internal

Modified: sandbox/local/libs/local/doc/html/boost_local/Release_Notes.html
==============================================================================
--- sandbox/local/libs/local/doc/html/boost_local/Release_Notes.html (original)
+++ sandbox/local/libs/local/doc/html/boost_local/Release_Notes.html 2011-05-12 13:30:50 EDT (Thu, 12 May 2011)
@@ -76,19 +76,6 @@
</h3></div></div></div>
<div class="orderedlist"><ol class="orderedlist" type="1">
<li class="listitem">
- Verify compilation and run-times on all compilers one last time.
- </li>
-<li class="listitem">
- Consider adding <code class="computeroutput">types(...)</code> for "overloading as polymorphism".
- Still, a unbound parameter with multiple types will keep one single default
- value (because it's not worth the added complexity to support multiple
- default values for each different type as with <code class="computeroutput">defaults(...)</code>) -- document this.
- </li>
-<li class="listitem">
- Consider adding <code class="computeroutput">bind_type type</code> to specify the bound parameter
- type directly so not to use Boost.Typeof to deduce such a type.
- </li>
-<li class="listitem">
Rework factorial_impl and Implementation section.
</li>
<li class="listitem">

Modified: sandbox/local/libs/local/doc/html/boost_local/Tutorial.html
==============================================================================
--- sandbox/local/libs/local/doc/html/boost_local/Tutorial.html (original)
+++ sandbox/local/libs/local/doc/html/boost_local/Tutorial.html 2011-05-12 13:30:50 EDT (Thu, 12 May 2011)
@@ -115,12 +115,12 @@
 ... }</code>
 using the usual C++ syntax. The body is specified outside any of the macros
 so eventual compiler error messages and related line numbers retain their
- usual meaning and format. [<a name="id866922" href="#ftn.id866922" class="footnote">3</a>]
+ usual meaning and format. [<a name="id866901" href="#ftn.id866901" class="footnote">3</a>]
 

 The macro <code class="computeroutput"><a class="link" href="../BOOST_LOCAL_FUNCTION_NAME.html" title="Macro BOOST_LOCAL_FUNCTION_NAME">BOOST_LOCAL_FUNCTION_NAME</a></code>
 is used to end the local function definition and to specify the local function
- name. [<a name="id866959" href="#ftn.id866959" class="footnote">4</a>]
+ name. [<a name="id866937" href="#ftn.id866937" class="footnote">4</a>]
 

 For example, let's program a local function named <code class="computeroutput">add</code>
@@ -376,7 +376,7 @@
 This library also allows to specify default values for the local function
 parameters. However, the usual C++ syntax for default parameters that uses
 the assignment symbol <code class="computeroutput">=</code> cannot
- be used. [<a name="id869072" href="#ftn.id869072" class="footnote">5</a>] The keyword <code class="computeroutput">default</code>
+ be used. [<a name="id869049" href="#ftn.id869049" class="footnote">5</a>] The keyword <code class="computeroutput">default</code>
 is used instead:
 
<div class="informaltable"><table class="table">
@@ -518,7 +518,7 @@
 variables, the object <code class="computeroutput">this</code>,
 etc) can be bound to a local function declaration. The types of bound variables
 are automatically deduced by this library using Boost.Typeof.
- [<a name="id870459" href="#ftn.id870459" class="footnote">6</a>]
+ [<a name="id870436" href="#ftn.id870436" class="footnote">6</a>]
 
<div class="important"><table border="0" summary="Important">
<tr>
@@ -535,7 +535,7 @@
</table></div>

 This library introduces the new "keyword" <code class="computeroutput">bind</code>
- [<a name="id870541" href="#ftn.id870541" class="footnote">7</a>] which is used in place of the parameter type to specify the name
+ [<a name="id870518" href="#ftn.id870518" class="footnote">7</a>] which is used in place of the parameter type to specify the name
 of a variable in scope to bind. The variable can be bound by value:
 
<pre class="programlisting">bind variable-name // Bind by value.
@@ -581,7 +581,7 @@
 variable was not declared constant in the enclosing scope then it will not
 be bound as constant unless constant binding is forced using <code class="computeroutput">const bind ...</code> (note that binding by constant reference
 is not supported by <a href="http://en.wikipedia.org/wiki/C%2B%2B0x#Lambda_functions_and_expressions" target="_top">C++0x
- lambda</a> functions but it is supported by this library). [<a name="id870847" href="#ftn.id870847" class="footnote">8</a>] As with passing parameters to usual C++ functions, programmers
+ lambda</a> functions but it is supported by this library). [<a name="id870824" href="#ftn.id870824" class="footnote">8</a>] As with passing parameters to usual C++ functions, programmers
 might want to bind variables of complex types by (constant) reference instead
 than by value to avoid expensive copy operations when these variables are
 bound to a local function.
@@ -671,7 +671,7 @@
 when it is in scope (e.g., from an enclosing member function). This is done
 by using <code class="computeroutput">this</code> as the name of
 the variable to bind in the local function declaration and by using the special
- symbol <code class="computeroutput">this_</code> [<a name="id871910" href="#ftn.id871910" class="footnote">9</a>] (instead of <code class="computeroutput">this</code>)
+ symbol <code class="computeroutput">this_</code> [<a name="id871887" href="#ftn.id871887" class="footnote">9</a>] (instead of <code class="computeroutput">this</code>)
 to access the object within the local function body.
 

@@ -714,12 +714,12 @@

 When the object <code class="computeroutput">this</code> is bound
 to a local function, the local function body must use the special symbol
- <code class="computeroutput">this_</code> (instead of <code class="computeroutput">this</code>) to access the bound object. [<a name="id872220" href="#ftn.id872220" class="footnote">10</a>]
+ <code class="computeroutput">this_</code> (instead of <code class="computeroutput">this</code>) to access the bound object. [<a name="id872197" href="#ftn.id872197" class="footnote">10</a>]
 

 Unfortunately, mistakenly using <code class="computeroutput">this</code>
 within the local function body instead of <code class="computeroutput">this_</code>
- will not necessarily generate a compile-time error. [<a name="id872314" href="#ftn.id872314" class="footnote">11</a>] Programmers are responsible to make sure that <code class="computeroutput">this</code> is never used within a local function
+ will not necessarily generate a compile-time error. [<a name="id872290" href="#ftn.id872290" class="footnote">11</a>] Programmers are responsible to make sure that <code class="computeroutput">this</code> is never used within a local function
 body which should only use the special symbol <code class="computeroutput">this_</code>.
 
</td></tr>
@@ -906,7 +906,7 @@
<tr><td align="left" valign="top">
 A <code class="computeroutput">return;</code>
 instruction from within a local block jumps to the end of the local block
- body and it does not return the enclosing function. [<a name="id875710" href="#ftn.id875710" class="footnote">12</a>]
+ body and it does not return the enclosing function. [<a name="id875688" href="#ftn.id875688" class="footnote">12</a>]
 </td></tr>
</table></div>

@@ -1018,7 +1018,7 @@
</tr>
<tr><td align="left" valign="top">
 The execution of the local exit body code is guaranteed only if the program
- does not terminate because of an uncaught exception. [<a name="id876947" href="#ftn.id876947" class="footnote">13</a>]
+ does not terminate because of an uncaught exception. [<a name="id876925" href="#ftn.id876925" class="footnote">13</a>]
 </td></tr>
</table></div>

@@ -1123,7 +1123,7 @@
 Local exits are very similar to the scope exits provided
 by Boost.ScopeExit
 with the addition that they also support constant binding and binding of
- the object <code class="computeroutput">this</code>. [<a name="id878365" href="#ftn.id878365" class="footnote">14</a>] Local exits can be used to emulate the <a href="http://d.digitalmars.com" target="_top">D
+ the object <code class="computeroutput">this</code>. [<a name="id878344" href="#ftn.id878344" class="footnote">14</a>] Local exits can be used to emulate the <a href="http://d.digitalmars.com" target="_top">D
 Programming Language</a> scope guards (see the
 <a class="link" href="Examples.html#boost_local.Examples.Emulating_Ds_Scope_Guards" title="Emulating D's Scope Guards">Emulating
 D's Scope Guards</a> example).
@@ -1137,7 +1137,7 @@
 When local functions, local blocks, and local exits are programmed within
 templates, they need to be declared using the following special macros ending
 with the <code class="computeroutput">TPL</code> postfix (see
- the Reference section): [<a name="id878661" href="#ftn.id878661" class="footnote">15</a>]
+ the Reference section): [<a name="id878639" href="#ftn.id878639" class="footnote">15</a>]
 
<pre class="programlisting"><code class="computeroutput"><a class="link" href="../BOOST_LOCAL_FUNCTION_PARAMS_TPL.html" title="Macro BOOST_LOCAL_FUNCTION_PARAMS_TPL">BOOST_LOCAL_FUNCTION_PARAMS_TPL</a></code>(parameters)
<code class="computeroutput"><a class="link" href="../BOOST_LOCAL_BLOCK_TPL.html" title="Macro BOOST_LOCAL_BLOCK_TPL">BOOST_LOCAL_BLOCK_TPL</a></code>(bindings)
@@ -1272,20 +1272,20 @@
</div>
<div class="footnotes">
 <hr width="100" align="left">
-<div class="footnote">[<a id="ftn.id866922" href="#id866922" class="para">3</a>] 
+<div class="footnote">[<a id="ftn.id866901" href="#id866901" class="para">3</a>] 
 Rationale. If the local function body
 were instead passed as a macro parameter, it would be expanded on a single
 line of code (because macros always expand as a single line of code). Therefore,
 eventual compiler error line numbers would all report the same value and
 would no longer be useful to pinpoint the error.
 </div>
-<div class="footnote">[<a id="ftn.id866959" href="#id866959" class="para">4</a>] 
+<div class="footnote">[<a id="ftn.id866937" href="#id866937" class="para">4</a>] 
 Rationale. The local function name must
 be passed to the macro <code class="computeroutput"><a class="link" href="../BOOST_LOCAL_FUNCTION_NAME.html" title="Macro BOOST_LOCAL_FUNCTION_NAME">BOOST_LOCAL_FUNCTION_NAME</a></code>
 ending the function definition so this macro can declare a local variable
 with the local function name to hold the local function object.
 </div>
-<div class="footnote">[<a id="ftn.id869072" href="#id869072" class="para">5</a>] 
+<div class="footnote">[<a id="ftn.id869049" href="#id869049" class="para">5</a>] 
 Rationale. The assignment symbol <code class="computeroutput">=</code> cannot be used to specify default parameter
 values because default values are not part of the parameter type so they
 cannot be handled using template metaprogamming. Default parameter values
@@ -1298,7 +1298,7 @@
 symbol cannot be detected by preprocessor metaprogramming because it cannot
 be concatenated by the preprocessor).
 </div>
-<div class="footnote">[<a id="ftn.id870459" href="#id870459" class="para">6</a>] 
+<div class="footnote">[<a id="ftn.id870436" href="#id870436" class="para">6</a>] 
 Rationale. By binding a variable in scope,
 the local function declaration is specifying that such a variable should
 be accessible within the local function body regardless of its type. Semantically,
@@ -1311,7 +1311,7 @@
 For example, this is useful for maintenance because if a bound variable
 type is changed, the local function declaration does not have to change.
 </div>
-<div class="footnote">[<a id="ftn.id870541" href="#id870541" class="para">7</a>] 
+<div class="footnote">[<a id="ftn.id870518" href="#id870518" class="para">7</a>] 
 Obviously, the token <code class="computeroutput">bind</code>
 is not a keyword of the C++ language. This library parses the token <code class="computeroutput">bind</code> during macro expansion using preprocessor
 metaprogramming (see the <a class="link" href="Implementation.html" title="Appendix: Implementation">Implementation</a>
@@ -1320,7 +1320,7 @@
 level within the syntax defined by the macros of this library -- thus it
 is referred to as a "keyword" only within quotes.
 </div>
-<div class="footnote">[<a id="ftn.id870847" href="#id870847" class="para">8</a>] 
+<div class="footnote">[<a id="ftn.id870824" href="#id870824" class="para">8</a>] 
 An historical note: Constant binding of variables in scope was the main
 use case that originally motivated the authors in developing this library.
 The authors needed to locally create a chuck of code to assert some correctness
@@ -1335,13 +1335,13 @@
 generates an error because the bound variable is of <code class="computeroutput">const</code>
 type within the local function body.
 </div>
-<div class="footnote">[<a id="ftn.id871910" href="#id871910" class="para">9</a>] 
+<div class="footnote">[<a id="ftn.id871887" href="#id871887" class="para">9</a>] 
 Rationale. The special name <code class="computeroutput">this_</code> was chosen following <a href="http://boost.2283326.n4.nabble.com/local-this-or-this-td3423912.html" target="_top">Boost
 practises</a> which postfix with an underscore identifiers that are
 named after keywords (the C++ keyword <code class="computeroutput">this</code>
 in this case).
 </div>
-<div class="footnote">[<a id="ftn.id872220" href="#id872220" class="para">10</a>] 
+<div class="footnote">[<a id="ftn.id872197" href="#id872197" class="para">10</a>] 
 Rationale. This limitation comes from
 the fact that <code class="computeroutput">this</code> is a
 reserved C++ keyword so it cannot be used as the name of the internal
@@ -1355,7 +1355,7 @@
 behaviour of <code class="computeroutput">static_cast</code></a>
 (which might not work on all platforms at the cost of portability).
 </div>
-<div class="footnote">[<a id="ftn.id872314" href="#id872314" class="para">11</a>] 
+<div class="footnote">[<a id="ftn.id872290" href="#id872290" class="para">11</a>] 
 Rationale. The local function body cannot
 be a static member function of the local functor object in order to support
 recursion (because the local function name is specified by the <code class="computeroutput"><a class="link" href="../BOOST_LOCAL_FUNCTION_NAME.html" title="Macro BOOST_LOCAL_FUNCTION_NAME">BOOST_LOCAL_FUNCTION_NAME</a></code>
@@ -1368,7 +1368,7 @@
 Therefore, from within the local function body the variable <code class="computeroutput">this</code> is visible but it refers to the local
 functor and not to the bound object.
 </div>
-<div class="footnote">[<a id="ftn.id875710" href="#id875710" class="para">12</a>] 
+<div class="footnote">[<a id="ftn.id875688" href="#id875688" class="para">12</a>] 
 Rationale. Programmers might expect
 <code class="computeroutput">return;</code>
 to exit the enclosing function instead of the local block (or local exit),
@@ -1386,7 +1386,7 @@
 <code class="computeroutput">BOOST_LOCAL_RETURN;</code>)
 to exit local blocks (and local exits).
 </div>
-<div class="footnote">[<a id="ftn.id876947" href="#id876947" class="para">13</a>] 
+<div class="footnote">[<a id="ftn.id876925" href="#id876925" class="para">13</a>] 
 Rationale. This library (as well as
 <a href="http://www.boost.org/doc/libs/release/libs/scope_exit/doc/html/index.html" target="_top">Boost.ScopeExit</a>)
 uses the destructor of a local variable to automatically execute the
@@ -1397,7 +1397,7 @@
 scope exit code even if the main program terminates because of an uncaught
 exception.)
 </div>
-<div class="footnote">[<a id="ftn.id878365" href="#id878365" class="para">14</a>] 
+<div class="footnote">[<a id="ftn.id878344" href="#id878344" class="para">14</a>] 
 Rationale. This library could be merged
 together with Boost.ScopeExit
 into a new library named Boost.Scope (from the meaning of the word "scope"
@@ -1426,7 +1426,7 @@
 name of "<a href="http://gcc.gnu.org/onlinedocs/gcc/Nested-Functions.html" target="_top">nested
 functions</a>" (GCC compiler extension).
 </div>
-<div class="footnote">[<a id="ftn.id878661" href="#id878661" class="para">15</a>] 
+<div class="footnote">[<a id="ftn.id878639" href="#id878639" class="para">15</a>] 
 Rationale. Within templates, this library
 needs to use <code class="computeroutput">typename</code> to explicitly
 indicate that some expressions evaluate to a type. Because C++ does not

Modified: sandbox/local/libs/local/doc/html/index.html
==============================================================================
--- sandbox/local/libs/local/doc/html/index.html (original)
+++ sandbox/local/libs/local/doc/html/index.html 2011-05-12 13:30:50 EDT (Thu, 12 May 2011)
@@ -27,7 +27,7 @@
</h3></div></div></div>
<div>Copyright © 2009-2011 Lorenzo Caminiti</div>
<div><div class="legalnotice">
-<a name="id863775"></a>
+<a name="id808786"></a>
 Use, modification, and distribution is subject to the Boost Software License,
 Version 1.0 (see accompanying file LICENSE_1_0.txt or a copy at http://www.boost.org/LICENSE_1_0.txt).
 
@@ -85,7 +85,7 @@
<li class="listitem">
 Local functions can be passed as template parameters (e.g., they can be
 conveniently passed to STL algorithms, this is in contrast to functors
- implemented using local classes see [2657]
+ implemented using local classes see [N2657]
 and the <a class="link" href="boost_local/Alternatives.html" title="Appendix: Alternatives">Alternatives</a> section).
 </li>
<li class="listitem">
@@ -344,7 +344,7 @@
 by reference, by constant value, and by constant reference. In addition,
 the object <code class="computeroutput">this</code> can be bound
 (eventually by constant value but never by reference or constant reference
- [<a name="id865478" href="#ftn.id865478" class="footnote">1</a>] ) from within a non-static member function (see the <a class="link" href="boost_local/Tutorial.html" title="Tutorial">Tutorial</a>
+ [<a name="id865441" href="#ftn.id865441" class="footnote">1</a>] ) from within a non-static member function (see the <a class="link" href="boost_local/Tutorial.html" title="Tutorial">Tutorial</a>
 section). For example, the variable <code class="computeroutput">factor</code>
 is bound by constant value so it cannot be mistakenly modified by the local
 function body. The variable <code class="computeroutput">sum</code>
@@ -420,13 +420,13 @@
</div>
<div class="footnotes">
 <hr width="100" align="left">
-<div class="footnote">[<a id="ftn.id865478" href="#id865478" class="para">1</a>] 
+<div class="footnote">[<a id="ftn.id865441" href="#id865441" class="para">1</a>] 
 C++ does not allow to obtain a reference to the pointer <code class="computeroutput">this</code>.
 </div>
</div>
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
-<td align="left">Last revised: May 12, 2011 at 16:01:45 GMT</td>
+<td align="left">Last revised: May 12, 2011 at 17:28:50 GMT</td>
<td align="right"><div class="copyright-footer"></div></td>
</tr></table>
<hr>

Modified: sandbox/local/libs/local/doc/qbk/advanced_topics.qbk
==============================================================================
--- sandbox/local/libs/local/doc/qbk/advanced_topics.qbk (original)
+++ sandbox/local/libs/local/doc/qbk/advanced_topics.qbk 2011-05-12 13:30:50 EDT (Thu, 12 May 2011)
@@ -333,7 +333,7 @@
[section Overloading Local Functions]

It is possible to overload local functions by creating a `__boost__local__function__overload__` functor that aggregates together calls to different local functions with different signatures.
-Note that the header file `"boost/local/function/overload.hpp"` needs to be included when using the `__boost__local__function__overload__` functor.
+Note that the header file [headerref boost/local/function/overload.hpp] needs to be included when using the `__boost__local__function__overload__` functor.

In the following example, the overloaded functor `print` can be called with signatures from either the local function `print_string`, or the local function `print_double`, or the local function `print_double` with the extra default parameter `name`, or the function pointer `print_add`:

Modified: sandbox/local/libs/local/doc/qbk/getting_started.qbk
==============================================================================
--- sandbox/local/libs/local/doc/qbk/getting_started.qbk (original)
+++ sandbox/local/libs/local/doc/qbk/getting_started.qbk 2011-05-12 13:30:50 EDT (Thu, 12 May 2011)
@@ -44,11 +44,12 @@

The header files of this library are divided as follow:

- ``[headerref boost/local/function.hpp] /local functions/``
- ``[headerref boost/local/block.hpp] /local blocks/``
- ``[headerref boost/local/exit.hpp] /local exits/``
- ``[headerref boost/local/typeof.hpp] /bound variable type deduction/``
- ``[headerref boost/local/config.hpp] /library configuration macros/``
+ ``[headerref boost/local/function.hpp] /local functions/``
+ ``[headerref boost/local/function/overload.hpp] /local function overloading/``
+ ``[headerref boost/local/block.hpp] /local blocks/``
+ ``[headerref boost/local/exit.hpp] /local exits/``
+ ``[headerref boost/local/typeof.hpp] /bound variable type deduction/``
+ ``[headerref boost/local/config.hpp] /library configuration macros/``

The followings are part of the library private API, they are not documented, and they should not be directly used by programmers:
[footnote

Modified: sandbox/local/libs/local/doc/qbk/local.qbk
==============================================================================
--- sandbox/local/libs/local/doc/qbk/local.qbk (original)
+++ sandbox/local/libs/local/doc/qbk/local.qbk 2011-05-12 13:30:50 EDT (Thu, 12 May 2011)
@@ -41,7 +41,7 @@
[def __N2511__ [@http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2008/n2511.html \[N2511\]]]
[def __N2529__ [@http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2008/n2529.pdf \[N2529\]]]
[def __N2550__ [@http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2008/n2550.pdf \[N2550\]]]
-[def __N2657__ [@http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2008/n2657.htm \[2657\]]]
+[def __N2657__ [@http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2008/n2657.html \[N2657\]]]

[def __Introduction__ [link boost_local.Introduction Introduction]]
[def __Getting_Started__ [link boost_local.Getting_Started Getting Started]]

Modified: sandbox/local/libs/local/doc/qbk/release_notes.qbk
==============================================================================
--- sandbox/local/libs/local/doc/qbk/release_notes.qbk (original)
+++ sandbox/local/libs/local/doc/qbk/release_notes.qbk 2011-05-12 13:30:50 EDT (Thu, 12 May 2011)
@@ -28,13 +28,6 @@

[section TODO]

-# Verify compilation and run-times on all compilers one last time.
-
-# Consider adding `types(...)` for "overloading as polymorphism".
-Still, a unbound parameter with multiple types will keep one single default value (because it's not worth the added complexity to support multiple default values for each different type as with `defaults(...)`) -- document this.
-
-# Consider adding `bind_type type` to specify the bound parameter type directly so not to use Boost.Typeof to deduce such a type.
-
# Rework factorial_impl and Implementation section.

# Finalize Acknowledge section.

Next message: phil_at_[hidden]: "[Boost-commit] svn:boost r71903 - sandbox/block_ptr/boost"
Previous message: antoshkka_at_[hidden]: "[Boost-commit] svn:boost r71901 - trunk/libs/conversion"

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