Boost-Commit :

Date view	Thread view	Subject view	Author view

Subject: [Boost-commit] svn:boost r77899 - in trunk: boost/functional libs/functional/overloaded_function/doc libs/functional/overloaded_function/doc/html libs/functional/overloaded_function/doc/html/boost libs/functional/overloaded_function/doc/html/boost_functional_overloadedfunction libs/functional/overloaded_function/test libs/scope_exit/doc libs/scope_exit/doc/html libs/scope_exit/doc/html/scope_exit
From: lorcaminiti_at_[hidden]
Date: 2012-04-10 16:42:56

Next message: lorcaminiti_at_[hidden]: "[Boost-commit] svn:boost r77900 - trunk/boost/functional"
Previous message: igaztanaga_at_[hidden]: "[Boost-commit] svn:boost r77898 - trunk/boost/container/detail"

Author: lcaminiti
Date: 2012-04-10 16:42:53 EDT (Tue, 10 Apr 2012)
New Revision: 77899
URL: http://svn.boost.org/trac/boost/changeset/77899

Log:
Updated docs.
Text files modified:
   trunk/boost/functional/overloaded_function.hpp | 39 ++++++++++++++--------
   trunk/libs/functional/overloaded_function/doc/html/BOOST_FUNCTIONAL_OVERLOADED_FUNCTION_CONFIG_ARITY_MAX.html | 2
   trunk/libs/functional/overloaded_function/doc/html/BOOST_FUNCTIONAL_OVERLOADED_FUNCTION_CONFIG_OVERLOAD_MAX.html | 2
   trunk/libs/functional/overloaded_function/doc/html/boost/make_overloaded_function.html | 8 ++--
   trunk/libs/functional/overloaded_function/doc/html/boost/overloaded_function.html | 47 +++++++++++++++++---------
   trunk/libs/functional/overloaded_function/doc/html/boost_functional_overloadedfunction/Getting_Started.html | 9 ++--
   trunk/libs/functional/overloaded_function/doc/html/boost_functional_overloadedfunction/Tutorial.html | 70 +++++++++++++++++++++++++++++----------
   trunk/libs/functional/overloaded_function/doc/html/index.html | 43 ++++++++++++++++--------
   trunk/libs/functional/overloaded_function/doc/html/reference.html | 2
   trunk/libs/functional/overloaded_function/doc/overloaded_function.qbk | 34 ++++++++++++------
   trunk/libs/functional/overloaded_function/test/identity.hpp | 6 ++
   trunk/libs/functional/overloaded_function/test/make_decl.cpp | 5 +-
   trunk/libs/scope_exit/doc/html/BOOST_SCOPE_EXIT.html | 2
   trunk/libs/scope_exit/doc/html/BOOST_SCOPE_EXIT_ALL.html | 2
   trunk/libs/scope_exit/doc/html/BOOST_SCOPE_EXIT_ALL_ID.html | 2
   trunk/libs/scope_exit/doc/html/BOOST_SCOPE_EXIT_CONFIG_USE_LAMBDAS.html | 2
   trunk/libs/scope_exit/doc/html/BOOST_SCOPE_EXIT_END.html | 2
   trunk/libs/scope_exit/doc/html/BOOST_SCOPE_EXIT_END_ID.html | 2
   trunk/libs/scope_exit/doc/html/BOOST_SCOPE_EXIT_ID.html | 2
   trunk/libs/scope_exit/doc/html/BOOST_SCOPE_EXIT_TPL.html | 2
   trunk/libs/scope_exit/doc/html/BOOST_SCOPE_EXIT_TPL_ID.html | 2
   trunk/libs/scope_exit/doc/html/index.html | 4 +-
   trunk/libs/scope_exit/doc/html/scope_exit/Getting_Started.html | 10 ++--
   trunk/libs/scope_exit/doc/html/scope_exit/Tutorial.html | 4 +-
   trunk/libs/scope_exit/doc/scope_exit.qbk | 2
   25 files changed, 194 insertions(+), 111 deletions(-)

Modified: trunk/boost/functional/overloaded_function.hpp
==============================================================================
--- trunk/boost/functional/overloaded_function.hpp (original)
+++ trunk/boost/functional/overloaded_function.hpp 2012-04-10 16:42:53 EDT (Tue, 10 Apr 2012)
@@ -186,8 +186,8 @@
#else // DOXYGEN

/** @file
-_at_brief Overload distinct function pointers, function references, and function
-objects into a single function object.
+@brief Overload distinct function pointers, function references, and
+monomorphic function objects into a single function object.
*/

namespace boost {
@@ -196,18 +196,25 @@
@brief Function object to overload functions with distinct signatures.

This function object aggregates together calls to functions of all the
-specified function types <c>F1</c>, <c>F2</c>, etc.
-The specified function types must have distinct parameters from one another and
-they must be in the following format (which is the Boost.Function preferred
-syntax):
+specified function types <c>F1</c>, <c>F2</c>, etc which must have distinct
+function signatures from one another.
+
+@Params
+@Param{Fi,
+Each function type must be specified using the following syntax (which is
+Boost.Function's preferred syntax):
@code
- result_type (argument1_type, argumgnet2_type, ...)
+ result_type (argument1_type\, argumgnet2_type\, ...)
@endcode
+}
+@EndParams

In some cases, the @RefFunc{make_overloaded_function} function template can be
-useful to construct the overloaded function object without explicitly
+useful to construct an overloaded function object without explicitly
specifying the function types.

+At least two distinct function types must be specified (because there is
+nothing to overload between one or zero functions).
The maximum number of functions to overload is given by the
@RefMacro{BOOST_FUNCTIONAL_OVERLOADED_FUNCTION_CONFIG_OVERLOAD_MAX}
configuration macro.
@@ -232,6 +239,10 @@
 Any function pointer, function reference, and monomorphic function object
 that can be converted to a <c>boost::function</c> function object can be
 specified as parameter.
+
+ @Note Unfortunately, it is not possible to support polymorphic function
+ objects (as explained <a
+ href="http://lists.boost.org/Archives/boost/2012/03/191744.php">here</a>).
 */
 overloaded_function(const boost::function<F1>&,
 const boost::function<F2>&, ...);
@@ -270,24 +281,24 @@
function types.

This function template creates and returns an @RefClass{overloaded_function}
-function object that overloads all the specified functions <c>f1</c>,
-<c>f2</c>, etc.
+object that overloads all the specified functions <c>f1</c>, <c>f2</c>, etc.

The function types are internally determined from the template parameter types
so they do not need to be explicitly specified.
Therefore, this function template usually has a more concise syntax when
compared with @RefClass{overloaded_function}.
This is especially useful when the explicit type of the returned
-_at_RefClass{overloaded_function} does not need to be known (e.g., when used with Boost.Typeof's <c>BOOST_AUTO</c> (or C++11 <c>auto</c>) or when the overloaded
-function object is handled using a function template parameter, see the
-_at_RefSect{Tutorial} section).
+@RefClass{overloaded_function} object does not need to be known (e.g., when
+used with Boost.Typeof's <c>BOOST_AUTO</c>, C++11 <c>auto</c>, or when the
+overloaded function object is handled using a function template parameter, see
+the @RefSect{Tutorial} section).

The maximum number of functions to overload is given by the
@RefMacro{BOOST_FUNCTIONAL_OVERLOADED_FUNCTION_CONFIG_OVERLOAD_MAX}
configuration macro.

@Note In this documentation, <c>__function_type__</c> is a placeholder for a
-symbol that is specific to implementation of this library.
+symbol that is specific to the implementation of this library.

@See
 @RefSect{Tutorial} section,

Modified: trunk/libs/functional/overloaded_function/doc/html/BOOST_FUNCTIONAL_OVERLOADED_FUNCTION_CONFIG_ARITY_MAX.html
==============================================================================
--- trunk/libs/functional/overloaded_function/doc/html/BOOST_FUNCTIONAL_OVERLOADED_FUNCTION_CONFIG_ARITY_MAX.html (original)
+++ trunk/libs/functional/overloaded_function/doc/html/BOOST_FUNCTIONAL_OVERLOADED_FUNCTION_CONFIG_ARITY_MAX.html 2012-04-10 16:42:53 EDT (Tue, 10 Apr 2012)
@@ -33,7 +33,7 @@

BOOST_FUNCTIONAL_OVERLOADED_FUNCTION_CONFIG_ARITY_MAX</pre></div>
<div class="refsect1">
-<a name="id872024"></a><h2>Description</h2>
+<a name="id870708"></a><h2>Description</h2>
If this macro is left undefined by the user, it has a default value of 5 (increasing this number might increase compilation time). When specified by the user, this macro must be a non-negative integer number.
See: <a class="link" href="boost_functional_overloadedfunction/Getting_Started.html" title="Getting Started"> Getting Started</a>, <code class="computeroutput"><a class="link" href="boost/overloaded_function.html" title="Class template overloaded_function">boost::overloaded_function</a></code>. 
</div>

Modified: trunk/libs/functional/overloaded_function/doc/html/BOOST_FUNCTIONAL_OVERLOADED_FUNCTION_CONFIG_OVERLOAD_MAX.html
==============================================================================
--- trunk/libs/functional/overloaded_function/doc/html/BOOST_FUNCTIONAL_OVERLOADED_FUNCTION_CONFIG_OVERLOAD_MAX.html (original)
+++ trunk/libs/functional/overloaded_function/doc/html/BOOST_FUNCTIONAL_OVERLOADED_FUNCTION_CONFIG_OVERLOAD_MAX.html 2012-04-10 16:42:53 EDT (Tue, 10 Apr 2012)
@@ -33,7 +33,7 @@

BOOST_FUNCTIONAL_OVERLOADED_FUNCTION_CONFIG_OVERLOAD_MAX</pre></div>
<div class="refsect1">
-<a name="id872082"></a><h2>Description</h2>
+<a name="id870766"></a><h2>Description</h2>
If this macro is left undefined by the user, it has a default value of 5 (increasing this number might increase compilation time). When defined by the user, this macro must be an integer number greater or equal than 2 (because at least two distinct functions need to be specified in order to define an overload).
See: <a class="link" href="boost_functional_overloadedfunction/Getting_Started.html" title="Getting Started"> Getting Started</a>, <code class="computeroutput"><a class="link" href="boost/overloaded_function.html" title="Class template overloaded_function">boost::overloaded_function</a></code>. 
</div>

Modified: trunk/libs/functional/overloaded_function/doc/html/boost/make_overloaded_function.html
==============================================================================
--- trunk/libs/functional/overloaded_function/doc/html/boost/make_overloaded_function.html (original)
+++ trunk/libs/functional/overloaded_function/doc/html/boost/make_overloaded_function.html 2012-04-10 16:42:53 EDT (Tue, 10 Apr 2012)
@@ -36,11 +36,11 @@
<a class="link" href="overloaded_function.html" title="Class template overloaded_function">overloaded_function</a>< __function_type__< F1 >, __function_type__< F2 >,...>
make_overloaded_function(F1 f1, F2 f2, ...);</pre></div>
<div class="refsect1">
-<a name="id871843"></a><h2>Description</h2>
-This function template creates and returns an <code class="computeroutput"><code class="computeroutput"><a class="link" href="overloaded_function.html" title="Class template overloaded_function">overloaded_function</a></code></code> function object that overloads all the specified functions <code class="computeroutput">f1</code>, <code class="computeroutput">f2</code>, etc.
-The function types are internally determined from the template parameter types so they do not need to be explicitly specified. Therefore, this function template usually has a more concise syntax when compared with <code class="computeroutput"><code class="computeroutput"><a class="link" href="overloaded_function.html" title="Class template overloaded_function">overloaded_function</a></code></code>. This is especially useful when the explicit type of the returned <code class="computeroutput"><code class="computeroutput"><a class="link" href="overloaded_function.html" title="Class template overloaded_function">overloaded_function</a></code></code> does not need to be known (e.g., when used with Boost.Typeof's <code class="computeroutput">BOOST_AUTO</code> (or C++11 <code class="computeroutput">auto</code>) or when the overloaded function object is handled using a function template parameter, see the <a class="link" href="../boost_functional_overloadedfunction/Tutorial.html" title="Tutorial">Tutorial</a>
section).
+<a name="id870528"></a><h2>Description</h2>
+This function template creates and returns an <code class="computeroutput"><code class="computeroutput"><a class="link" href="overloaded_function.html" title="Class template overloaded_function">overloaded_function</a></code></code> object that overloads all the specified functions <code class="computeroutput">f1</code>, <code class="computeroutput">f2</code>, etc.
+The function types are internally determined from the template parameter types so they do not need to be explicitly specified. Therefore, this function template usually has a more concise syntax when compared with <code class="computeroutput"><code class="computeroutput"><a class="link" href="overloaded_function.html" title="Class template overloaded_function">overloaded_function</a></code></code>. This is especially useful when the explicit type of the returned <code class="computeroutput"><code class="computeroutput"><a class="link" href="overloaded_function.html" title="Class template overloaded_function">overloaded_function</a></code></code> object does not need to be known (e.g., when used with Boost.Typeof's <code class="computeroutput">BOOST_AUTO</code>, C++11 <code class="computeroutput">auto</code>, or when the overloaded function object is handled using a function template parameter, see the <a class="link" href="../boost_functional_overloadedfunction/Tutorial.html" title="Tutorial">Tutorial
</a> section).
The maximum number of functions to overload is given by the <code class="computeroutput"><code class="computeroutput"><a class="link" href="../BOOST_FUNCTIONAL_OVERLOADED_FUNCTION_CONFIG_OVERLOAD_MAX.html" title="Macro BOOST_FUNCTIONAL_OVERLOADED_FUNCTION_CONFIG_OVERLOAD_MAX">BOOST_FUNCTIONAL_OVERLOADED_FUNCTION_CONFIG_OVERLOAD_MAX</a></code></code> configuration macro.
-Note: In this documentation, <code class="computeroutput">__function_type__</code> is a placeholder for a symbol that is specific to implementation of this library.
+Note: In this documentation, <code class="computeroutput">__function_type__</code> is a placeholder for a symbol that is specific to the implementation of this library.
See: <a class="link" href="../boost_functional_overloadedfunction/Tutorial.html" title="Tutorial">Tutorial</a> section, <code class="computeroutput"><code class="computeroutput"><a class="link" href="overloaded_function.html" title="Class template overloaded_function">overloaded_function</a></code></code>, <code class="computeroutput"><code class="computeroutput"><a class="link" href="../BOOST_FUNCTIONAL_OVERLOADED_FUNCTION_CONFIG_OVERLOAD_MAX.html" title="Macro BOOST_FUNCTIONAL_OVERLOADED_FUNCTION_CONFIG_OVERLOAD_MAX">BOOST_FUNCTIONAL_OVERLOADED_FUNCTION_CONFIG_OVERLOAD_MAX</a></code></code>. 
</div>
</div>

Modified: trunk/libs/functional/overloaded_function/doc/html/boost/overloaded_function.html
==============================================================================
--- trunk/libs/functional/overloaded_function/doc/html/boost/overloaded_function.html (original)
+++ trunk/libs/functional/overloaded_function/doc/html/boost/overloaded_function.html 2012-04-10 16:42:53 EDT (Tue, 10 Apr 2012)
@@ -35,47 +35,60 @@
class <a class="link" href="overloaded_function.html" title="Class template overloaded_function">overloaded_function</a> {
public:
 // <a class="link" href="overloaded_function.html#boost.overloaded_functionconstruct-copy-destruct">construct/copy/destruct</a>
- <a class="link" href="overloaded_function.html#id299641-bb">overloaded_function</a>(const boost::function< F1 > &,
+ <a class="link" href="overloaded_function.html#id315888-bb">overloaded_function</a>(const boost::function< F1 > &,
 const boost::function< F2 > &, ...);

- // <a class="link" href="overloaded_function.html#id299571-bb">public member functions</a>
+ // <a class="link" href="overloaded_function.html#id315818-bb">public member functions</a>
 boost::function_traits< F1 >::result_type
- <a class="link" href="overloaded_function.html#id299574-bb">operator()</a>(typename boost::function_traits< F1 >::arg1_type,
+ <a class="link" href="overloaded_function.html#id315821-bb">operator()</a>(typename boost::function_traits< F1 >::arg1_type,
 typename boost::function_traits< F1 >::arg2_type, ...) const;
 boost::function_traits< F2 >::result_type
- <a class="link" href="overloaded_function.html#id299600-bb">operator()</a>(typename boost::function_traits< F2 >::arg1_type,
+ <a class="link" href="overloaded_function.html#id315847-bb">operator()</a>(typename boost::function_traits< F2 >::arg1_type,
 typename boost::function_traits< F2 >::arg2_type, ...) const;
};</pre></div>
<div class="refsect1">
-<a name="id870004"></a><h2>Description</h2>
-This function object aggregates together calls to functions of all the specified function types <code class="computeroutput">F1</code>, <code class="computeroutput">F2</code>, etc. The specified function types must have distinct parameters from one another and they must be in the following format (which is the Boost.Function preferred syntax): 
-<pre class="programlisting"> result_type (argument1_type, argumgnet2_type, ...)
-</pre>
-In some cases, the <code class="computeroutput"><a class="link" href="make_overloaded_function.html" title="Function template make_overloaded_function">make_overloaded_function</a></code> function template can be useful to construct the overloaded function object without explicitly specifying the function types.
-The maximum number of functions to overload is given by the <code class="computeroutput"><a class="link" href="../BOOST_FUNCTIONAL_OVERLOADED_FUNCTION_CONFIG_OVERLOAD_MAX.html" title="Macro BOOST_FUNCTIONAL_OVERLOADED_FUNCTION_CONFIG_OVERLOAD_MAX">BOOST_FUNCTIONAL_OVERLOADED_FUNCTION_CONFIG_OVERLOAD_MAX</a></code> configuration macro. The maximum number of function parameters for each of the specified function types is given by the <code class="computeroutput"><a class="link" href="../BOOST_FUNCTIONAL_OVERLOADED_FUNCTION_CONFIG_ARITY_MAX.html" title="Macro BOOST_FUNCTIONAL_OVERLOADED_FUNCTION_CONFIG_ARITY_MAX">BOOST_FUNCTIONAL_OVERLOADED_FUNCTION_CONFIG_ARITY_MAX</a></code> configuration macro.
+<a name="id869742"></a><h2>Description</h2>
+This function object aggregates together calls to functions of all the specified function types <code class="computeroutput">F1</code>, <code class="computeroutput">F2</code>, etc which must have distinct function signatures from one another.
+Parameters: 
+<div class="informaltable"><table class="table">
+<colgroup>
+<col>
+<col>
+</colgroup>
+<tbody><tr>
+<td><code class="computeroutput">Fi</code></td>
+<td>Each function type must be specified using the following syntax (which is Boost.Function's preferred syntax): <pre xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="table-programlisting"> result_type (argument1_type, argumgnet2_type, ...)
+</pre> </td>
+</tr></tbody>
+</table></div>
+
+
+In some cases, the <code class="computeroutput"><a class="link" href="make_overloaded_function.html" title="Function template make_overloaded_function">make_overloaded_function</a></code> function template can be useful to construct an overloaded function object without explicitly specifying the function types.
+At least two distinct function types must be specified (because there is nothing to overload between one or zero functions). The maximum number of functions to overload is given by the <code class="computeroutput"><a class="link" href="../BOOST_FUNCTIONAL_OVERLOADED_FUNCTION_CONFIG_OVERLOAD_MAX.html" title="Macro BOOST_FUNCTIONAL_OVERLOADED_FUNCTION_CONFIG_OVERLOAD_MAX">BOOST_FUNCTIONAL_OVERLOADED_FUNCTION_CONFIG_OVERLOAD_MAX</a></code> configuration macro. The maximum number of function parameters for each of the specified function types is given by the <code class="computeroutput"><a class="link" href="../BOOST_FUNCTIONAL_OVERLOADED_FUNCTION_CONFIG_ARITY_MAX.html" title="Macro BOOST_FUNCTIONAL_OVERLOADED_FUNCTION_CONFIG_ARITY_MAX">BOOST_FUNCTIONAL_OVERLOADED_FUNCTION_CONFIG_ARITY_MAX</a></code> configuration macro.
See: <a class="link" href="../boost_functional_overloadedfunction/Tutorial.html" title="Tutorial">Tutorial</a> section, <code class="computeroutput"><a class="link" href="make_overloaded_function.html" title="Function template make_overloaded_function">make_overloaded_function</a></code>, <code class="computeroutput"><a class="link" href="../BOOST_FUNCTIONAL_OVERLOADED_FUNCTION_CONFIG_OVERLOAD_MAX.html" title="Macro BOOST_FUNCTIONAL_OVERLOADED_FUNCTION_CONFIG_OVERLOAD_MAX">BOOST_FUNCTIONAL_OVERLOADED_FUNCTION_CONFIG_OVERLOAD_MAX</a></code>, <code class="computeroutput"><a class="link" href="../BOOST_FUNCTIONAL_OVERLOADED_FUNCTION_CONFIG_ARITY_MAX.html" title="Macro BOOST_FUNCTIONAL_OVERLOADED_FUNCTION_CONFIG_ARITY_MAX">BOOST_FUNCTIONAL_OVERLOADED_FUNCTION_CONFIG_ARITY_MAX</a></code>, Boost.Function. 
<div class="refsect2">
-<a name="id871216"></a><h3>
+<a name="id869890"></a><h3>
<a name="boost.overloaded_functionconstruct-copy-destruct"></a><code class="computeroutput">overloaded_function</code>
 public
 construct/copy/destruct</h3>
<div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
-<pre class="literallayout"><a name="id299641-bb"></a>overloaded_function(const boost::function< F1 > &,
- const boost::function< F2 > &, ...);</pre>Construct the overloaded function object. Any function pointer, function reference, and monomorphic function object that can be converted to a <code class="computeroutput">boost::function</code> function object can be specified as parameter. 
+<pre class="literallayout"><a name="id315888-bb"></a>overloaded_function(const boost::function< F1 > &,
+ const boost::function< F2 > &, ...);</pre>Construct the overloaded function object. Any function pointer, function reference, and monomorphic function object that can be converted to a <code class="computeroutput">boost::function</code> function object can be specified as parameter.
+Note: Unfortunately, it is not possible to support polymorphic function objects (as explained here). 
</li></ol></div>
</div>
<div class="refsect2">
-<a name="id871341"></a><h3>
-<a name="id299571-bb"></a><code class="computeroutput">overloaded_function</code> public member functions</h3>
+<a name="id870026"></a><h3>
+<a name="id315818-bb"></a><code class="computeroutput">overloaded_function</code> public member functions</h3>
<div class="orderedlist"><ol class="orderedlist" type="1">
<li class="listitem">
<pre class="literallayout">boost::function_traits< F1 >::result_type
-<a name="id299574-bb"></a>operator()(typename boost::function_traits< F1 >::arg1_type,
+<a name="id315821-bb"></a>operator()(typename boost::function_traits< F1 >::arg1_type,
 typename boost::function_traits< F1 >::arg2_type, ...) const;</pre>Call operator matching the signature of the function type specified as 1st template parameter. This will in turn invoke the call operator of the 1st function passed to the constructor. 
</li>
<li class="listitem">
<pre class="literallayout">boost::function_traits< F2 >::result_type
-<a name="id299600-bb"></a>operator()(typename boost::function_traits< F2 >::arg1_type,
+<a name="id315847-bb"></a>operator()(typename boost::function_traits< F2 >::arg1_type,
 typename boost::function_traits< F2 >::arg2_type, ...) const;</pre>Call operator matching the signature of the function type specified as 2nd template parameter. This will in turn invoke the call operator of the 2nd function passed to the constructor.
Note: Similar call operators are present for all specified function types <code class="computeroutput">F1</code>, <code class="computeroutput">F2</code>, etc (even if not exhaustively listed by this documentation). 
</li>

Modified: trunk/libs/functional/overloaded_function/doc/html/boost_functional_overloadedfunction/Getting_Started.html
==============================================================================
--- trunk/libs/functional/overloaded_function/doc/html/boost_functional_overloadedfunction/Getting_Started.html (original)
+++ trunk/libs/functional/overloaded_function/doc/html/boost_functional_overloadedfunction/Getting_Started.html 2012-04-10 16:42:53 EDT (Tue, 10 Apr 2012)
@@ -41,7 +41,7 @@
 and Platforms</a>
</h3></div></div></div>

- The authors originally developed and tested the library on:
+ The authors originally developed and tested this library on:
 
<div class="orderedlist"><ol class="orderedlist" type="1">
<li class="listitem">
@@ -56,7 +56,8 @@

 See the library <a href="http://www.boost.org/development/tests/release/developer/functional-overloaded_function.html" target="_top">regressions
 test results</a> for detailed information on supported compilers and
- platforms.
+ platforms. Check the library regression test Jamfile.v2
+ for any special configuration that might be required for a specific compiler.
 
</div>
<div class="section boost_functional_overloadedfunction_Getting_Started_installation">
@@ -72,9 +73,9 @@

 The maximum number of functions to overload is given by the <code class="computeroutput"><a class="link" href="../BOOST_FUNCTIONAL_OVERLOADED_FUNCTION_CONFIG_OVERLOAD_MAX.html" title="Macro BOOST_FUNCTIONAL_OVERLOADED_FUNCTION_CONFIG_OVERLOAD_MAX">BOOST_FUNCTIONAL_OVERLOADED_FUNCTION_CONFIG_OVERLOAD_MAX</a></code>
 configuration macro. The maximum number of function parameters for each of
- the specified function types is given by the <code class="computeroutput"><a class="link" href="../BOOST_FUNCTIONAL_OVERLOADED_FUNCTION_CONFIG_ARITY_MAX.html" title="Macro BOOST_FUNCTIONAL_OVERLOADED_FUNCTION_CONFIG_ARITY_MAX">BOOST_FUNCTIONAL_OVERLOADED_FUNCTION_CONFIG_ARITY_MAX</a></code>
+ the specified function type is given by the <code class="computeroutput"><a class="link" href="../BOOST_FUNCTIONAL_OVERLOADED_FUNCTION_CONFIG_ARITY_MAX.html" title="Macro BOOST_FUNCTIONAL_OVERLOADED_FUNCTION_CONFIG_ARITY_MAX">BOOST_FUNCTIONAL_OVERLOADED_FUNCTION_CONFIG_ARITY_MAX</a></code>
 configuration macro. All configuration macros have appropriate default values
- when they are left undefined by the user.
+ when they are left undefined.
 
</div>
</div>

Modified: trunk/libs/functional/overloaded_function/doc/html/boost_functional_overloadedfunction/Tutorial.html
==============================================================================
--- trunk/libs/functional/overloaded_function/doc/html/boost_functional_overloadedfunction/Tutorial.html (original)
+++ trunk/libs/functional/overloaded_function/doc/html/boost_functional_overloadedfunction/Tutorial.html 2012-04-10 16:42:53 EDT (Tue, 10 Apr 2012)
@@ -39,10 +39,20 @@
<a name="boost_functional_overloadedfunction.Tutorial.overloading"></a><a class="link" href="Tutorial.html#boost_functional_overloadedfunction.Tutorial.overloading" title="Overloading">Overloading</a>
</h3></div></div></div>

- Consider the following functions with distinct signatures:
+ Consider the following functions which have distinct signatures:
 

- [identity_decls]
+
+<pre class="programlisting">const std::string& identity_s(const std::string& x) // Function (as pointer).
+ { return x; }
+
+int identity_i_impl(int x) { return x; }
+int (&identity_i)(int) = identity_i_impl; // Function reference.
+
+double identity_d_impl(double x) { return x; }
+boost::function<double (double)> identity_d = identity_d_impl; // Functor.
+</pre>
+
 

 This library header <code class="computeroutput"><a class="link" href="../reference.html#header.boost.functional.overloaded_function_hpp" title="Header <boost/functional/overloaded_function.hpp>">boost/functional/overloaded_function.hpp</a></code>
@@ -61,16 +71,15 @@
> identity(identity_s, identity_i, identity_d);

// All calls via single `identity` function.
-BOOST_CHECK(identity("abc") == "abc");
-BOOST_CHECK(identity(123) == 123);
-BOOST_CHECK(identity(1.23) == 1.23);
+BOOST_TEST(identity("abc") == "abc");
+BOOST_TEST(identity(123) == 123);
+BOOST_TEST(identity(1.23) == 1.23);
</pre>

 

- Note how function types in the following format are passed as template parameters
- to <code class="computeroutput"><a class="link" href="../boost/overloaded_function.html" title="Class template overloaded_function">boost::overloaded_function</a></code>
- (this is the format of Boost.Function's
+ Note how each function type is passed as a template parameter of <code class="computeroutput"><a class="link" href="../boost/overloaded_function.html" title="Class template overloaded_function">boost::overloaded_function</a></code> using
+ the following syntax (this is Boost.Function's
 preferred syntax):
 
<pre class="programlisting">result-type (argument1-type, argument2-type, ...)
@@ -79,10 +88,10 @@
 Then the relative function pointers, function references, or <a href="http://en.wikipedia.org/wiki/Polymorphism_(computer_science)" target="_top">monomorphic
 function</a> objects are passed to the <code class="computeroutput"><a class="link" href="../boost/overloaded_function.html" title="Class template overloaded_function">boost::overloaded_function</a></code>
 constructor matching the order of the specified template parameters. [<a name="boost_functional_overloadedfunction.Tutorial.overloading.f0" href="#ftn.boost_functional_overloadedfunction.Tutorial.overloading.f0" class="footnote">2</a>] In the above example, <code class="computeroutput">identity_s</code>
- is passed as function pointer (the function address is automatically taken
- from the function name by compiler), <code class="computeroutput">identity_i</code>
- as function reference, and <code class="computeroutput">identity_d</code>
- as function object.
+ is passed as a function pointer (the function address is automatically taken
+ from the function name by the compiler), <code class="computeroutput">identity_i</code>
+ as a function reference, and <code class="computeroutput">identity_d</code>
+ as a function object.
 

 All specified function types must have distinct parameters from one another
@@ -114,9 +123,9 @@
<pre class="programlisting">BOOST_AUTO(identity, boost::make_overloaded_function(
 identity_s, identity_i, identity_d));

-BOOST_CHECK(identity("abc") == "abc");
-BOOST_CHECK(identity(123) == 123);
-BOOST_CHECK(identity(1.23) == 1.23);
+BOOST_TEST(identity("abc") == "abc");
+BOOST_TEST(identity(123) == 123);
+BOOST_TEST(identity(1.23) == 1.23);
</pre>

 
@@ -135,7 +144,7 @@

 Another case where <code class="computeroutput"><a class="link" href="../boost/make_overloaded_function.html" title="Function template make_overloaded_function">boost::make_overloaded_function</a></code>
 can be useful is when the overloaded function object is passed to a function
- template which can hide the specific <code class="computeroutput"><a class="link" href="../boost/overloaded_function.html" title="Class template overloaded_function">boost::overloaded_function</a></code>
+ template which can hold the specific <code class="computeroutput"><a class="link" href="../boost/overloaded_function.html" title="Class template overloaded_function">boost::overloaded_function</a></code>
 type using a template parameter. For example (see also make_call.cpp
 and identity.hpp):
 
@@ -143,9 +152,9 @@

<pre class="programlisting">template<typename F>
void check(F identity) {
- BOOST_CHECK(identity("abc") == "abc");
- BOOST_CHECK(identity(123) == 123);
- BOOST_CHECK(identity(1.23) == 1.23);
+ BOOST_TEST(identity("abc") == "abc");
+ BOOST_TEST(identity(123) == 123);
+ BOOST_TEST(identity(1.23) == 1.23);
}
</pre>

@@ -156,6 +165,27 @@
</pre>

 
+
+ The library implementation of <code class="computeroutput"><a class="link" href="../boost/make_overloaded_function.html" title="Function template make_overloaded_function">boost::make_overloaded_function</a></code>
+ uses Boost.Typeof
+ to automatically deduce some of the function types. In order to compile code
+ in Boost.Typeof
+ emulation mode, all types should be properly registered using <code class="computeroutput">BOOST_TYPEOF_REGISTER_TYPE</code> and <code class="computeroutput">BOOST_TYPEOF_REGISTER_TEMPLATE</code>, or appropriate
+ Boost.Typeof headers
+ should be included (see Boost.Typeof
+ for more information). For the above examples, it is sufficient to include
+ the Boost.Typeof
+ header that registers <code class="computeroutput">std::string</code>
+ (this library does not require to register <code class="computeroutput">boost::function</code>
+ for Boost.Typeof
+ emulation):
+ 
+
+
+<pre class="programlisting">#include <boost/typeof/std/string.hpp> // No need to register `boost::function`.
+</pre>
+
+ 
</div>
<div class="footnotes">
 <hr width="100" align="left">
@@ -171,6 +201,8 @@
 pointers and function references). Finally, monomorphic function objects
 are instances of classes with a non-template call operator of the form
 <code class="literal">result-type </code><code class="computeroutput">operator()(</code><code class="literal">argument1-type</code><code class="computeroutput">, ...)</code>.
+ Unfortunately, it is not possible to support polymorphic function objects
+ (see http://lists.boost.org/Archives/boost/2012/03/191744.php).
 </div>
<div class="footnote">[<a id="ftn.boost_functional_overloadedfunction.Tutorial.overloading.f1" href="#boost_functional_overloadedfunction.Tutorial.overloading.f1" class="para">3</a>] 
 Note that in C++ the function result type is not used for overload resolution

Modified: trunk/libs/functional/overloaded_function/doc/html/index.html
==============================================================================
--- trunk/libs/functional/overloaded_function/doc/html/index.html (original)
+++ trunk/libs/functional/overloaded_function/doc/html/index.html 2012-04-10 16:42:53 EDT (Tue, 10 Apr 2012)
@@ -66,21 +66,31 @@
<a name="boost_functional_overloadedfunction.Introduction"></a><a class="link" href="index.html#boost_functional_overloadedfunction.Introduction" title="Introduction">Introduction</a>
</h2></div></div></div>

- Consider the following functions with distinct signatures:
+ Consider the following functions which have distinct signatures:
 

- [identity_decls]
+
+<pre class="programlisting">const std::string& identity_s(const std::string& x) // Function (as pointer).
+ { return x; }
+
+int identity_i_impl(int x) { return x; }
+int (&identity_i)(int) = identity_i_impl; // Function reference.
+
+double identity_d_impl(double x) { return x; }
+boost::function<double (double)> identity_d = identity_d_impl; // Functor.
+</pre>
+
 

- Instead of calling them using their separate names (here <code class="computeroutput">BOOST_CHECK</code>
+ Instead of calling them using their separate names (here <code class="computeroutput">BOOST_TEST</code>
 is equivalent to <code class="computeroutput">assert</code>):
 [<a name="boost_functional_overloadedfunction.Introduction.f0" href="#ftn.boost_functional_overloadedfunction.Introduction.f0" class="footnote">1</a>]
 


-<pre class="programlisting">BOOST_CHECK(identity_s("abc") == "abc");
-BOOST_CHECK(identity_i(123) == 123);
-BOOST_CHECK(identity_d(1.23) == 1.23);
+<pre class="programlisting">BOOST_TEST(identity_s("abc") == "abc");
+BOOST_TEST(identity_i(123) == 123);
+BOOST_TEST(identity_d(1.23) == 1.23);
</pre>

 
@@ -100,9 +110,9 @@
> identity(identity_s, identity_i, identity_d);

// All calls via single `identity` function.
-BOOST_CHECK(identity("abc") == "abc");
-BOOST_CHECK(identity(123) == 123);
-BOOST_CHECK(identity(1.23) == 1.23);
+BOOST_TEST(identity("abc") == "abc");
+BOOST_TEST(identity(123) == 123);
+BOOST_TEST(identity(1.23) == 1.23);
</pre>

 
@@ -116,16 +126,19 @@
<div class="footnotes">
 <hr width="100" align="left">
<div class="footnote">[<a id="ftn.boost_functional_overloadedfunction.Introduction.f0" href="#boost_functional_overloadedfunction.Introduction.f0" class="para">1</a>] 
- In the examples presented in this documentation, <code class="computeroutput">BOOST_CHECK</code>
- is used instead of <code class="computeroutput">assert</code>
- because it allows to write regression tests using Boost.Test.
- The examples of this documentation are executed as part of the library test
- suite to verify that they always compile and run correctly.
+ In most of the examples presented in this documentation, the Boost.Detail/LightweightTest
+ (<code class="literal">boost/detail/lightweight_test.hpp</code>) macro <code class="computeroutput">BOOST_TEST</code> is used to check correctness
+ conditions (conceptually similar to <code class="computeroutput">assert</code>).
+ A failure of the checked condition does not abort the execution of the program,
+ it will instead make <code class="computeroutput">boost::report_errors</code>
+ return a non-zero program exit code. Using Boost.Detail/LightweightTest allows
+ to add the examples to the library regression tests so to make sure that
+ they always compile and run correctly.
 </div>
</div>
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
-<td align="left">Last revised: March 22, 2012 at 20:51:03 GMT</td>
+<td align="left">Last revised: April 10, 2012 at 20:37:20 GMT</td>
<td align="right"><div class="copyright-footer"></div></td>
</tr></table>
<hr>

Modified: trunk/libs/functional/overloaded_function/doc/html/reference.html
==============================================================================
--- trunk/libs/functional/overloaded_function/doc/html/reference.html (original)
+++ trunk/libs/functional/overloaded_function/doc/html/reference.html 2012-04-10 16:42:53 EDT (Tue, 10 Apr 2012)
@@ -32,7 +32,7 @@
<div class="section header_boost_functional_overloaded_function_hpp">
<div class="titlepage"><div><div><h3 class="title">
<a name="header.boost.functional.overloaded_function_hpp"></a>Header <boost/functional/overloaded_function.hpp></h3></div></div></div>
-Overload distinct function pointers, function references, and function objects into a single function object. 
+Overload distinct function pointers, function references, and monomorphic function objects into a single function object. 
<pre class="synopsis">namespace boost {
template<typename F1, typename F2, ... > class <a class="link" href="boost/overloaded_function.html" title="Class template overloaded_function">overloaded_function</a>;
template<typename F1, typename F2, ... >

Modified: trunk/libs/functional/overloaded_function/doc/overloaded_function.qbk
==============================================================================
--- trunk/libs/functional/overloaded_function/doc/overloaded_function.qbk (original)
+++ trunk/libs/functional/overloaded_function/doc/overloaded_function.qbk 2012-04-10 16:42:53 EDT (Tue, 10 Apr 2012)
@@ -27,6 +27,7 @@
[def __Boost_Function__ [@http://www.boost.org/libs/function Boost.Function]]
[def __Boost_Typeof__ [@http://www.boost.org/doc/libs/typeof Boost.Typeof]]

+[import ../test/identity.hpp]
[import ../test/functor.cpp]
[import ../test/make_decl.cpp]
[import ../test/make_call.cpp]
@@ -35,14 +36,15 @@

[section:Introduction Introduction]

-Consider the following functions with distinct signatures:
+Consider the following functions which have distinct signatures:

[identity_decls]

-Instead of calling them using their separate names (here `BOOST_CHECK` is equivalent to `assert`):
+Instead of calling them using their separate names (here `BOOST_TEST` is equivalent to `assert`):
[footnote
-In the examples presented in this documentation, `BOOST_CHECK` is used instead of `assert` because it allows to write regression tests using __Boost_Test__.
-The examples of this documentation are executed as part of the library test suite to verify that they always compile and run correctly.
+In most of the examples presented in this documentation, the Boost.Detail/LightweightTest (=boost/detail/lightweight_test.hpp=) macro `BOOST_TEST` is used to check correctness conditions (conceptually similar to `assert`).
+A failure of the checked condition does not abort the execution of the program, it will instead make `boost::report_errors` return a non-zero program exit code.
+Using Boost.Detail/LightweightTest allows to add the examples to the library regression tests so to make sure that they always compile and run correctly.
]

[identity_calls]
@@ -61,12 +63,13 @@

[section Compilers and Platforms]

-The authors originally developed and tested the library on:
+The authors originally developed and tested this library on:

# GNU Compiler Collection (GCC) C++ 4.5.3 (with and without C++11 features enabled `-std=c++0x`) on Cygwin.
# Miscrosoft Visual C++ (MSVC) 8.0 on Windows 7.

See the library [@http://www.boost.org/development/tests/release/developer/functional-overloaded_function.html regressions test results] for detailed information on supported compilers and platforms.
+Check the library regression test [@../../test/Jamfile.v2 =Jamfile.v2=] for any special configuration that might be required for a specific compiler.

[endsect]

@@ -77,8 +80,8 @@
Programmers can simply instruct the compiler where to find the library header files (`-I` option on GCC, `/I` option on MSVC, etc) and compile code using the library.

The maximum number of functions to overload is given by the [macroref BOOST_FUNCTIONAL_OVERLOADED_FUNCTION_CONFIG_OVERLOAD_MAX] configuration macro.
-The maximum number of function parameters for each of the specified function types is given by the [macroref BOOST_FUNCTIONAL_OVERLOADED_FUNCTION_CONFIG_ARITY_MAX] configuration macro.
-All configuration macros have appropriate default values when they are left undefined by the user.
+The maximum number of function parameters for each of the specified function type is given by the [macroref BOOST_FUNCTIONAL_OVERLOADED_FUNCTION_CONFIG_ARITY_MAX] configuration macro.
+All configuration macros have appropriate default values when they are left undefined.

[endsect]

@@ -90,7 +93,7 @@

[section Overloading]

-Consider the following functions with distinct signatures:
+Consider the following functions which have distinct signatures:

[identity_decls]

@@ -98,7 +101,7 @@

[identity_functor]

-Note how function types in the following format are passed as template parameters to [classref boost::overloaded_function] (this is the format of __Boost_Function__'s preferred syntax):
+Note how each function type is passed as a template parameter of [classref boost::overloaded_function] using the following syntax (this is __Boost_Function__'s preferred syntax):

``/result-type/`` (``/argument1-type/``, ``/argument2-type/``, ...)

@@ -108,8 +111,9 @@
Function references are of the form [^['result-type ]]`(&)(`[^['argument1-type]]`, ...)`.
Function types are of the form [^['result-type ]]`(`[^['argument1-type]]`, ...)` (note how they lack of both `*` and `&` when compared to function pointers and function references).
Finally, monomorphic function objects are instances of classes with a non-template call operator of the form [^['result-type ]]`operator()(`[^['argument1-type]]`, ...)`.
+Unfortunately, it is not possible to support polymorphic function objects (see [@http://lists.boost.org/Archives/boost/2012/03/191744.php]).
]
-In the above example, `identity_s` is passed as function pointer (the function address is automatically taken from the function name by compiler), `identity_i` as function reference, and `identity_d` as function object.
+In the above example, `identity_s` is passed as a function pointer (the function address is automatically taken from the function name by the compiler), `identity_i` as a function reference, and `identity_d` as a function object.

All specified function types must have distinct parameters from one another (so the overloaded calls can be resolved by this library).
[footnote
@@ -128,17 +132,23 @@
The [funcref boost::make_overloaded_function] function template can be useful when used together with __Boost_Typeof__'s `BOOST_AUTO` (or C++11 `auto`).
For example (see also [@../../test/make_decl.cpp =make_decl.cpp=] and [@../../test/identity.hpp =identity.hpp=]):

-[identity_make]
+[identity_make_decl]

Note how the overloaded function object `identity` has been created specifying only the functions `identity_s`, `identity_i`, `identity_d` and without specifying the function types `const std::string& (const std::string&)`, `int (int)`, and `double (double)` as required instead by [classref boost::overloaded_function].
Therefore, [funcref boost::make_overloaded_function] provides a more concise syntax in this context when compared with [classref boost::overloaded_function].

-Another case where [funcref boost::make_overloaded_function] can be useful is when the overloaded function object is passed to a function template which can hide the specific [classref boost::overloaded_function] type using a template parameter.
+Another case where [funcref boost::make_overloaded_function] can be useful is when the overloaded function object is passed to a function template which can hold the specific [classref boost::overloaded_function] type using a template parameter.
For example (see also [@../../test/make_call.cpp =make_call.cpp=] and [@../../test/identity.hpp =identity.hpp=]):

[identity_make_checks]
[identity_make_call]

+The library implementation of [funcref boost::make_overloaded_function] uses __Boost_Typeof__ to automatically deduce some of the function types.
+In order to compile code in __Boost_Typeof__ emulation mode, all types should be properly registered using `BOOST_TYPEOF_REGISTER_TYPE` and `BOOST_TYPEOF_REGISTER_TEMPLATE`, or appropriate __Boost_Typeof__ headers should be included (see __Boost_Typeof__ for more information).
+For the above examples, it is sufficient to include the __Boost_Typeof__ header that registers `std::string` (this library does not require to register `boost::function` for __Boost_Typeof__ emulation):
+
+[identity_typeof]
+
[endsect]

[endsect]

Modified: trunk/libs/functional/overloaded_function/test/identity.hpp
==============================================================================
--- trunk/libs/functional/overloaded_function/test/identity.hpp (original)
+++ trunk/libs/functional/overloaded_function/test/identity.hpp 2012-04-10 16:42:53 EDT (Tue, 10 Apr 2012)
@@ -9,10 +9,14 @@
#define IDENTITY_HPP_

#include <boost/function.hpp>
+//[identity_typeof
+#include <boost/typeof/std/string.hpp> // No need to register `boost::function`.
+//]
#include <string>

//[identity_decls
-const std::string& identity_s(const std::string& x) { return x; } // As pointer.
+const std::string& identity_s(const std::string& x) // Function (as pointer).
+ { return x; }

int identity_i_impl(int x) { return x; }
int (&identity_i)(int) = identity_i_impl; // Function reference.

Modified: trunk/libs/functional/overloaded_function/test/make_decl.cpp
==============================================================================
--- trunk/libs/functional/overloaded_function/test/make_decl.cpp (original)
+++ trunk/libs/functional/overloaded_function/test/make_decl.cpp 2012-04-10 16:42:53 EDT (Tue, 10 Apr 2012)
@@ -7,12 +7,11 @@

#include "identity.hpp"
#include <boost/functional/overloaded_function.hpp>
-#include <boost/typeof/typeof.hpp> // For `BOOST_AUTO`.
-#include <boost/typeof/std/string.hpp> // No need to register `boost::function`.
+#include <boost/typeof/typeof.hpp>
#include <boost/detail/lightweight_test.hpp>

int main() {
- //[identity_make
+ //[identity_make_decl
BOOST_AUTO(identity, boost::make_overloaded_function(
identity_s, identity_i, identity_d));

Modified: trunk/libs/scope_exit/doc/html/BOOST_SCOPE_EXIT.html
==============================================================================
--- trunk/libs/scope_exit/doc/html/BOOST_SCOPE_EXIT.html (original)
+++ trunk/libs/scope_exit/doc/html/BOOST_SCOPE_EXIT.html 2012-04-10 16:42:53 EDT (Tue, 10 Apr 2012)
@@ -33,7 +33,7 @@

BOOST_SCOPE_EXIT(capture_list)</pre></div>
<div class="refsect1">
-<a name="id881228"></a><h2>Description</h2>
+<a name="id857198"></a><h2>Description</h2>
The scope exit declaration schedules the execution of the scope exit body at the exit of the enclosing scope:
<pre class="programlisting"> { // Some local scope.
...

Modified: trunk/libs/scope_exit/doc/html/BOOST_SCOPE_EXIT_ALL.html
==============================================================================
--- trunk/libs/scope_exit/doc/html/BOOST_SCOPE_EXIT_ALL.html (original)
+++ trunk/libs/scope_exit/doc/html/BOOST_SCOPE_EXIT_ALL.html 2012-04-10 16:42:53 EDT (Tue, 10 Apr 2012)
@@ -33,7 +33,7 @@

BOOST_SCOPE_EXIT_ALL(capture_list)</pre></div>
<div class="refsect1">
-<a name="id882718"></a><h2>Description</h2>
+<a name="id858688"></a><h2>Description</h2>
This macro accepts a capture list starting with either <code class="computeroutput">&</code> or <code class="computeroutput">=</code> to capture all variables in scope by reference or value respectively (following the same syntax of C++11 lambdas). A part from that, this macro works like <code class="computeroutput"><a class="link" href="BOOST_SCOPE_EXIT.html" title="Macro BOOST_SCOPE_EXIT">BOOST_SCOPE_EXIT</a></code> (see <code class="computeroutput"><a class="link" href="BOOST_SCOPE_EXIT.html" title="Macro BOOST_SCOPE_EXIT">BOOST_SCOPE_EXIT</a></code> for more information):
<pre class="programlisting"> { // Some local scope.
...

Modified: trunk/libs/scope_exit/doc/html/BOOST_SCOPE_EXIT_ALL_ID.html
==============================================================================
--- trunk/libs/scope_exit/doc/html/BOOST_SCOPE_EXIT_ALL_ID.html (original)
+++ trunk/libs/scope_exit/doc/html/BOOST_SCOPE_EXIT_ALL_ID.html 2012-04-10 16:42:53 EDT (Tue, 10 Apr 2012)
@@ -33,7 +33,7 @@

BOOST_SCOPE_EXIT_ALL_ID(id, capture_list)</pre></div>
<div class="refsect1">
-<a name="id883371"></a><h2>Description</h2>
+<a name="id859341"></a><h2>Description</h2>
This macro is equivalent to <code class="computeroutput"><a class="link" href="BOOST_SCOPE_EXIT_ALL.html" title="Macro BOOST_SCOPE_EXIT_ALL">BOOST_SCOPE_EXIT_ALL</a></code> but it can be expanded multiple times on the same line if different identifiers <code class="computeroutput">id</code> are provided for each expansion (see <code class="computeroutput"><a class="link" href="BOOST_SCOPE_EXIT_ALL.html" title="Macro BOOST_SCOPE_EXIT_ALL">BOOST_SCOPE_EXIT_ALL</a></code> for more information). As with <code class="computeroutput"><a class="link" href="BOOST_SCOPE_EXIT_ALL.html" title="Macro BOOST_SCOPE_EXIT_ALL">BOOST_SCOPE_EXIT_ALL</a></code>, this macro is only available on C++11 compilers (specifically, on C++11 compilers that do not define the Boost.Config <code class="computeroutput">BOOST_NO_LAMBDAS</code> macro).
Parameters: 
<div class="informaltable"><table class="table">

Modified: trunk/libs/scope_exit/doc/html/BOOST_SCOPE_EXIT_CONFIG_USE_LAMBDAS.html
==============================================================================
--- trunk/libs/scope_exit/doc/html/BOOST_SCOPE_EXIT_CONFIG_USE_LAMBDAS.html (original)
+++ trunk/libs/scope_exit/doc/html/BOOST_SCOPE_EXIT_CONFIG_USE_LAMBDAS.html 2012-04-10 16:42:53 EDT (Tue, 10 Apr 2012)
@@ -33,7 +33,7 @@

BOOST_SCOPE_EXIT_CONFIG_USE_LAMBDAS</pre></div>
<div class="refsect1">
-<a name="id885498"></a><h2>Description</h2>
+<a name="id861468"></a><h2>Description</h2>
If programmers define this configuration macro on a C++11 compiler for which the Boost.Config macro <code class="computeroutput">BOOST_NO_LAMBDAS</code> is not defined, the <code class="computeroutput"><a class="link" href="BOOST_SCOPE_EXIT.html" title="Macro BOOST_SCOPE_EXIT">BOOST_SCOPE_EXIT</a></code> and <code class="computeroutput"><a class="link" href="BOOST_SCOPE_EXIT_TPL.html" title="Macro BOOST_SCOPE_EXIT_TPL">BOOST_SCOPE_EXIT_TPL</a></code> macros will use C++11 lambda functions to declare scope exits. By default this macro is not defined.
Warning: When scope exits are implemented using lambda functions, the syntax of the capture list follows the exact same syntax of C++11 lambda captures which is in general different from the legacy capture syntax of this library. For example, C++11 lambdas require to capture data members by capturing the object <code class="computeroutput">this</code> while this library always allowed to capture data members directly. Therefore, when this configuration macro is defined, <code class="computeroutput"><a class="link" href="BOOST_SCOPE_EXIT.html" title="Macro BOOST_SCOPE_EXIT">BOOST_SCOPE_EXIT</a></code> and <code class="computeroutput"><a class="link" href="BOOST_SCOPE_EXIT_TPL.html" title="Macro BOOST_SCOPE_EXIT_TPL">BOOST_SCOPE_EXIT_TPL</a></code> are no longer backward compatible (and this is why this macro is not defined by default).
A semicolon <code class="computeroutput">;</code> can be used instead of <code class="computeroutput"><a class="link" href="BOOST_SCOPE_EXIT_END.html" title="Macro BOOST_SCOPE_EXIT_END">BOOST_SCOPE_EXIT_END</a></code> when this configuration macro is defined (but it is recommended to always use <code class="computeroutput"><a class="link" href="BOOST_SCOPE_EXIT_END.html" title="Macro BOOST_SCOPE_EXIT_END">BOOST_SCOPE_EXIT_END</a></code> so to maximize portability).

Modified: trunk/libs/scope_exit/doc/html/BOOST_SCOPE_EXIT_END.html
==============================================================================
--- trunk/libs/scope_exit/doc/html/BOOST_SCOPE_EXIT_END.html (original)
+++ trunk/libs/scope_exit/doc/html/BOOST_SCOPE_EXIT_END.html 2012-04-10 16:42:53 EDT (Tue, 10 Apr 2012)
@@ -33,7 +33,7 @@

BOOST_SCOPE_EXIT_END</pre></div>
<div class="refsect1">
-<a name="id883531"></a><h2>Description</h2>
+<a name="id859502"></a><h2>Description</h2>
This macro must follow the closing curly bracket <code class="computeroutput">}</code> that ends the body of either <code class="computeroutput"><a class="link" href="BOOST_SCOPE_EXIT.html" title="Macro BOOST_SCOPE_EXIT">BOOST_SCOPE_EXIT</a></code> or <code class="computeroutput"><a class="link" href="BOOST_SCOPE_EXIT_TPL.html" title="Macro BOOST_SCOPE_EXIT_TPL">BOOST_SCOPE_EXIT_TPL</a></code>:
<pre class="programlisting"> { // Some local scope.
...

Modified: trunk/libs/scope_exit/doc/html/BOOST_SCOPE_EXIT_END_ID.html
==============================================================================
--- trunk/libs/scope_exit/doc/html/BOOST_SCOPE_EXIT_END_ID.html (original)
+++ trunk/libs/scope_exit/doc/html/BOOST_SCOPE_EXIT_END_ID.html 2012-04-10 16:42:53 EDT (Tue, 10 Apr 2012)
@@ -33,7 +33,7 @@

BOOST_SCOPE_EXIT_END_ID(id)</pre></div>
<div class="refsect1">
-<a name="id885366"></a><h2>Description</h2>
+<a name="id861336"></a><h2>Description</h2>
This macro is equivalent to <code class="computeroutput"><a class="link" href="BOOST_SCOPE_EXIT_END.html" title="Macro BOOST_SCOPE_EXIT_END">BOOST_SCOPE_EXIT_END</a></code> but it can be expanded multiple times on the same line if different identifiers <code class="computeroutput">id</code> are provided for each expansion (see <code class="computeroutput"><a class="link" href="BOOST_SCOPE_EXIT_END.html" title="Macro BOOST_SCOPE_EXIT_END">BOOST_SCOPE_EXIT_END</a></code> for more information).
Parameters: 
<div class="informaltable"><table class="table">

Modified: trunk/libs/scope_exit/doc/html/BOOST_SCOPE_EXIT_ID.html
==============================================================================
--- trunk/libs/scope_exit/doc/html/BOOST_SCOPE_EXIT_ID.html (original)
+++ trunk/libs/scope_exit/doc/html/BOOST_SCOPE_EXIT_ID.html 2012-04-10 16:42:53 EDT (Tue, 10 Apr 2012)
@@ -33,7 +33,7 @@

BOOST_SCOPE_EXIT_ID(id, capture_list)</pre></div>
<div class="refsect1">
-<a name="id882384"></a><h2>Description</h2>
+<a name="id858354"></a><h2>Description</h2>
This macro is equivalent to <code class="computeroutput"><a class="link" href="BOOST_SCOPE_EXIT.html" title="Macro BOOST_SCOPE_EXIT">BOOST_SCOPE_EXIT</a></code> but it can be expanded multiple times on the same line if different identifiers <code class="computeroutput">id</code> are provided for each expansion (see <code class="computeroutput"><a class="link" href="BOOST_SCOPE_EXIT.html" title="Macro BOOST_SCOPE_EXIT">BOOST_SCOPE_EXIT</a></code> for more information).
Parameters: 
<div class="informaltable"><table class="table">

Modified: trunk/libs/scope_exit/doc/html/BOOST_SCOPE_EXIT_TPL.html
==============================================================================
--- trunk/libs/scope_exit/doc/html/BOOST_SCOPE_EXIT_TPL.html (original)
+++ trunk/libs/scope_exit/doc/html/BOOST_SCOPE_EXIT_TPL.html 2012-04-10 16:42:53 EDT (Tue, 10 Apr 2012)
@@ -33,7 +33,7 @@

BOOST_SCOPE_EXIT_TPL(capture_list)</pre></div>
<div class="refsect1">
-<a name="id881832"></a><h2>Description</h2>
+<a name="id857802"></a><h2>Description</h2>
Various versions of the GCC compiler do not compile <code class="computeroutput"><a class="link" href="BOOST_SCOPE_EXIT.html" title="Macro BOOST_SCOPE_EXIT">BOOST_SCOPE_EXIT</a></code> inside function templates. As a workaround, <code class="computeroutput"><a class="link" href="BOOST_SCOPE_EXIT_TPL.html" title="Macro BOOST_SCOPE_EXIT_TPL">BOOST_SCOPE_EXIT_TPL</a></code> should be used instead of <code class="computeroutput"><a class="link" href="BOOST_SCOPE_EXIT.html" title="Macro BOOST_SCOPE_EXIT">BOOST_SCOPE_EXIT</a></code> in these cases:
<pre class="programlisting"> { // Some local scope.
...

Modified: trunk/libs/scope_exit/doc/html/BOOST_SCOPE_EXIT_TPL_ID.html
==============================================================================
--- trunk/libs/scope_exit/doc/html/BOOST_SCOPE_EXIT_TPL_ID.html (original)
+++ trunk/libs/scope_exit/doc/html/BOOST_SCOPE_EXIT_TPL_ID.html 2012-04-10 16:42:53 EDT (Tue, 10 Apr 2012)
@@ -33,7 +33,7 @@

BOOST_SCOPE_EXIT_TPL_ID(id, capture_list)</pre></div>
<div class="refsect1">
-<a name="id882547"></a><h2>Description</h2>
+<a name="id858518"></a><h2>Description</h2>
This macro is equivalent to <code class="computeroutput"><a class="link" href="BOOST_SCOPE_EXIT_TPL.html" title="Macro BOOST_SCOPE_EXIT_TPL">BOOST_SCOPE_EXIT_TPL</a></code> but it can be expanded multiple times on the same line if different identifiers <code class="computeroutput">id</code> are provided for each expansion (see <code class="computeroutput"><a class="link" href="BOOST_SCOPE_EXIT_TPL.html" title="Macro BOOST_SCOPE_EXIT_TPL">BOOST_SCOPE_EXIT_TPL</a></code> for more information). As with <code class="computeroutput"><a class="link" href="BOOST_SCOPE_EXIT_TPL.html" title="Macro BOOST_SCOPE_EXIT_TPL">BOOST_SCOPE_EXIT_TPL</a></code>, it is recommended to always use this macro when expanding scope exits multiple times on the same line within templates.
Parameters: 
<div class="informaltable"><table class="table">

Modified: trunk/libs/scope_exit/doc/html/index.html
==============================================================================
--- trunk/libs/scope_exit/doc/html/index.html (original)
+++ trunk/libs/scope_exit/doc/html/index.html 2012-04-10 16:42:53 EDT (Tue, 10 Apr 2012)
@@ -42,7 +42,7 @@
<dt>Introduction</dt>
<dt>Getting Started</dt>
<dd><dl>
-<dt>Documentation</dt>
+<dt>This Documentation</dt>
<dt><a href="scope_exit/Getting_Started.html#scope_exit.Getting_Started.compilers_and_platforms">Compilers
and Platforms</a></dt>
<dt>Installation</dt>
@@ -120,7 +120,7 @@
</div>
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
-<td align="left">Last revised: April 10, 2012 at 13:53:37 GMT</td>
+<td align="left">Last revised: April 10, 2012 at 20:41:46 GMT</td>
<td align="right"><div class="copyright-footer"></div></td>
</tr></table>
<hr>

Modified: trunk/libs/scope_exit/doc/html/scope_exit/Getting_Started.html
==============================================================================
--- trunk/libs/scope_exit/doc/html/scope_exit/Getting_Started.html (original)
+++ trunk/libs/scope_exit/doc/html/scope_exit/Getting_Started.html 2012-04-10 16:42:53 EDT (Tue, 10 Apr 2012)
@@ -27,7 +27,7 @@
<a name="scope_exit.Getting_Started"></a><a class="link" href="Getting_Started.html" title="Getting Started">Getting Started</a>
</h2></div></div></div>
<div class="toc"><dl>
-<dt>Documentation</dt>
+<dt>This Documentation</dt>
<dt><a href="Getting_Started.html#scope_exit.Getting_Started.compilers_and_platforms">Compilers
 and Platforms</a></dt>
<dt>Installation</dt>
@@ -35,9 +35,9 @@

 This section explains how to setup a system to use this library.
 
-<div class="section scope_exit_Getting_Started_documentation">
+<div class="section scope_exit_Getting_Started_this_documentation">
<div class="titlepage"><div><div><h3 class="title">
-<a name="scope_exit.Getting_Started.documentation"></a><a class="link" href="Getting_Started.html#scope_exit.Getting_Started.documentation" title="Documentation">Documentation</a>
+<a name="scope_exit.Getting_Started.this_documentation"></a><a class="link" href="Getting_Started.html#scope_exit.Getting_Started.this_documentation" title="This Documentation">This Documentation</a>
</h3></div></div></div>

 Programmers should have enough knowledge to use this library after reading
@@ -58,7 +58,7 @@
 conditions (conceptually similar to <code class="computeroutput">assert</code>).
 A failure of the checked condition does not abort the execution of the program,
 it will instead make <code class="computeroutput">boost::report_errors</code>
- return a non-zero program exit code. [<a name="scope_exit.Getting_Started.documentation.f0" href="#ftn.scope_exit.Getting_Started.documentation.f0" class="footnote">2</a>]
+ return a non-zero program exit code. [<a name="scope_exit.Getting_Started.this_documentation.f0" href="#ftn.scope_exit.Getting_Started.this_documentation.f0" class="footnote">2</a>]
 
</div>
<div class="section scope_exit_Getting_Started_compilers_and_platforms">
@@ -115,7 +115,7 @@
</div>
<div class="footnotes">
 <hr width="100" align="left">
-<div class="footnote">[<a id="ftn.scope_exit.Getting_Started.documentation.f0" href="#scope_exit.Getting_Started.documentation.f0" class="para">2</a>] 
+<div class="footnote">[<a id="ftn.scope_exit.Getting_Started.this_documentation.f0" href="#scope_exit.Getting_Started.this_documentation.f0" class="para">2</a>] 
 Rationale. Using Boost.Detail/LightweightTest
 allows to add the examples to the library regression tests so to make sure
 that they always compile and run correctly.

Modified: trunk/libs/scope_exit/doc/html/scope_exit/Tutorial.html
==============================================================================
--- trunk/libs/scope_exit/doc/html/scope_exit/Tutorial.html (original)
+++ trunk/libs/scope_exit/doc/html/scope_exit/Tutorial.html 2012-04-10 16:42:53 EDT (Tue, 10 Apr 2012)
@@ -439,12 +439,12 @@
 } BOOST_SCOPE_EXIT_END_ID(BOOST_PP_CAT(dec, __LINE__))

#define SCOPE_EXIT_INC_DEC_TPL(variable, offset) \
- BOOST_SCOPE_EXIT_ID_TPL(BOOST_PP_CAT(inc, __LINE__), \
+ BOOST_SCOPE_EXIT_TPL_ID(BOOST_PP_CAT(inc, __LINE__), \
 &variable, offset) { \
 variable += offset; \
 } BOOST_SCOPE_EXIT_END_ID(BOOST_PP_CAT(inc, __LINE__)) \
 \
- BOOST_SCOPE_EXIT_ID_TPL(BOOST_PP_CAT(dec, __LINE__), \
+ BOOST_SCOPE_EXIT_TPL_ID(BOOST_PP_CAT(dec, __LINE__), \
 &variable, offset) { \
 variable -= offset; \
 } BOOST_SCOPE_EXIT_END_ID(BOOST_PP_CAT(dec, __LINE__))

Modified: trunk/libs/scope_exit/doc/scope_exit.qbk
==============================================================================
--- trunk/libs/scope_exit/doc/scope_exit.qbk (original)
+++ trunk/libs/scope_exit/doc/scope_exit.qbk 2012-04-10 16:42:53 EDT (Tue, 10 Apr 2012)
@@ -84,7 +84,7 @@

This section explains how to setup a system to use this library.

-[section Documentation]
+[section This Documentation]

Programmers should have enough knowledge to use this library after reading the __Introduction__, __Getting_Started__, and __Tutorial__ sections.
The __Reference__ section can be consulted at a later point for quick reference.

Next message: lorcaminiti_at_[hidden]: "[Boost-commit] svn:boost r77900 - trunk/boost/functional"
Previous message: igaztanaga_at_[hidden]: "[Boost-commit] svn:boost r77898 - trunk/boost/container/detail"

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