Boost-Commit :

Date view	Thread view	Subject view	Author view

Subject: [Boost-commit] svn:boost r78221 - in trunk/libs: local_function/doc local_function/doc/html local_function/doc/html/boost_localfunction scope_exit/doc scope_exit/doc/html scope_exit/doc/html/scope_exit
From: lorcaminiti_at_[hidden]
Date: 2012-04-27 11:35:17

Next message: vicente.botet_at_[hidden]: "[Boost-commit] svn:boost r78222 - trunk/libs/thread/example"
Previous message: afojgo_at_[hidden]: "[Boost-commit] svn:boost r78220 - in sandbox/icl/libs/xplore/br1/sqlbrowser: . Dag"

Author: lcaminiti
Date: 2012-04-27 11:35:12 EDT (Fri, 27 Apr 2012)
New Revision: 78221
URL: http://svn.boost.org/trac/boost/changeset/78221

Log:
Updated docs to user [heading] instead of [h5] for excluding sections from TOC.
Text files modified:
   trunk/libs/local_function/doc/advanced_topics.qbk | 4 ++--
   trunk/libs/local_function/doc/alternatives.qbk | 4 ++--
   trunk/libs/local_function/doc/html/BOOST_LOCAL_FUNCTION.html | 2 +-
   trunk/libs/local_function/doc/html/BOOST_LOCAL_FUNCTION_CONFIG_ARITY_MAX.html | 2 +-
   trunk/libs/local_function/doc/html/BOOST_LOCAL_FUNCTION_CONFIG_BIND_MAX.html | 2 +-
   trunk/libs/local_function/doc/html/BOOST_LOCAL_FUNCTION_CONFIG_LOCALS_AS_TPARAMS.html | 2 +-
   trunk/libs/local_function/doc/html/BOOST_LOCAL_FUNCTION_ID.html | 2 +-
   trunk/libs/local_function/doc/html/BOOST_LOCAL_FUNCTION_NAME.html | 2 +-
   trunk/libs/local_function/doc/html/BOOST_LOCAL_FUNCTION_NAME_TPL.html | 2 +-
   trunk/libs/local_function/doc/html/BOOST_LOCAL_FUNCTION_TPL.html | 2 +-
   trunk/libs/local_function/doc/html/BOOST_LOCAL_FUNCTION_TPL_ID.html | 2 +-
   trunk/libs/local_function/doc/html/BOOST_LOCAL_FUNCTION_TYPEOF.html | 2 +-
   trunk/libs/local_function/doc/html/boost_localfunction/Advanced_Topics.html | 26 +++++++++++++-------------
   trunk/libs/local_function/doc/html/boost_localfunction/Alternatives.html | 8 ++++----
   trunk/libs/local_function/doc/html/boost_localfunction/Implementation.html | 8 ++++----
   trunk/libs/local_function/doc/html/boost_localfunction/No_Variadic_Macros.html | 8 ++++----
   trunk/libs/local_function/doc/html/boost_localfunction/Release_Notes.html | 20 ++++++++++----------
   trunk/libs/local_function/doc/html/index.html | 2 +-
   trunk/libs/local_function/doc/implementation.qbk | 4 ++--
   trunk/libs/local_function/doc/no_variadic_macros.qbk | 4 ++--
   trunk/libs/local_function/doc/release_notes.qbk | 10 +++++-----
   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 | 2 +-
   trunk/libs/scope_exit/doc/html/scope_exit/Alternatives.html | 20 ++++++++++----------
   trunk/libs/scope_exit/doc/html/scope_exit/No_Variadic_Macros.html | 8 ++++----
   trunk/libs/scope_exit/doc/scope_exit.qbk | 14 +++++++-------
   34 files changed, 90 insertions(+), 90 deletions(-)

Modified: trunk/libs/local_function/doc/advanced_topics.qbk
==============================================================================
--- trunk/libs/local_function/doc/advanced_topics.qbk (original)
+++ trunk/libs/local_function/doc/advanced_topics.qbk 2012-04-27 11:35:12 EDT (Fri, 27 Apr 2012)
@@ -464,7 +464,7 @@
]
]

-[h5 Operators]
+[heading Operators]

Local functions cannot be operators.
Naming a local function `operator...` will generate a compile-time error.
@@ -477,7 +477,7 @@

[operator_error]

-[h5 Goto]
+[heading Goto]

It is possible to jump with a `goto` within the local function body.
For example, the following compiles (see also [@../../test/goto.cpp =goto.cpp=]):

Modified: trunk/libs/local_function/doc/alternatives.qbk
==============================================================================
--- trunk/libs/local_function/doc/alternatives.qbk (original)
+++ trunk/libs/local_function/doc/alternatives.qbk 2012-04-27 11:35:12 EDT (Fri, 27 Apr 2012)
@@ -9,7 +9,7 @@

This section compares the features offered by this library with similar features offered by C++ and by other libraries.

-[h5 Features]
+[heading Features]

The following table compares local function features.

@@ -145,7 +145,7 @@
The comparison in this section does not include the __Boost_Lambda__ library because that library is obsolete and it was replaced by __Boost_Phoenix__.
The __Boost_Phoenix__ library version 3.0 is used for this comparison.

-[h5 Performances]
+[heading Performances]

The following tables compare run-times, compile-times, and binary sizes for the different alternatives to local functions presented in this section.

Modified: trunk/libs/local_function/doc/html/BOOST_LOCAL_FUNCTION.html
==============================================================================
--- trunk/libs/local_function/doc/html/BOOST_LOCAL_FUNCTION.html (original)
+++ trunk/libs/local_function/doc/html/BOOST_LOCAL_FUNCTION.html 2012-04-27 11:35:12 EDT (Fri, 27 Apr 2012)
@@ -33,7 +33,7 @@

</span>BOOST_LOCAL_FUNCTION(declarations)</pre></div>
<div class="refsect1">
-<a name="id859236"></a><h2>Description</h2>
+<a name="id839242"></a><h2>Description</h2>
<p>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_localfunction/Tutorial.html" title="Tutorial">Tutorial</a> and <a class="link" href="boost_localfunction/Advanced_Topics.html" title="Advanced Topics"> Advanced Topics</a> sections): </p>
<pre class="programlisting"><span class="special">{</span> <span class="comment">// Some declarative context.</span>
<span class="special">...</span>

Modified: trunk/libs/local_function/doc/html/BOOST_LOCAL_FUNCTION_CONFIG_ARITY_MAX.html
==============================================================================
--- trunk/libs/local_function/doc/html/BOOST_LOCAL_FUNCTION_CONFIG_ARITY_MAX.html (original)
+++ trunk/libs/local_function/doc/html/BOOST_LOCAL_FUNCTION_CONFIG_ARITY_MAX.html 2012-04-27 11:35:12 EDT (Fri, 27 Apr 2012)
@@ -33,7 +33,7 @@

</span>BOOST_LOCAL_FUNCTION_CONFIG_ARITY_MAX</pre></div>
<div class="refsect1">
-<a name="id861380"></a><h2>Description</h2>
+<a name="id842001"></a><h2>Description</h2>
<p>If programmers leave this configuration macro undefined, its default value is <code class="computeroutput">5</code> (increasing this number might increase compilation time). When defined by programmers, this macro must be a non-negative integer number.</p>
<p><span class="bold"><strong>Note:</strong></span> This macro specifies the maximum number of local function parameters excluding bound variables (which are instead specified by <code class="computeroutput"><a class="link" href="BOOST_LOCAL_FUNCTION_CONFIG_BIND_MAX.html" title="Macro BOOST_LOCAL_FUNCTION_CONFIG_BIND_MAX">BOOST_LOCAL_FUNCTION_CONFIG_BIND_MAX</a></code>).</p>
<p><span class="bold"><strong>See:</strong></span> <a class="link" href="boost_localfunction/Tutorial.html" title="Tutorial">Tutorial</a> section, <a class="link" href="boost_localfunction/Getting_Started.html" title="Getting Started"> Getting Started</a> section, <code class="computeroutput"><a class="link" href="BOOST_LOCAL_FUNCTION_CONFIG_BIND_MAX.html" title="Macro BOOST_LOCAL_FUNCTION_CONFIG_BIND_MAX">BOOST_LOCAL_FUNCTION_CONFIG_BIND_MAX</a></code>. </p>

Modified: trunk/libs/local_function/doc/html/BOOST_LOCAL_FUNCTION_CONFIG_BIND_MAX.html
==============================================================================
--- trunk/libs/local_function/doc/html/BOOST_LOCAL_FUNCTION_CONFIG_BIND_MAX.html (original)
+++ trunk/libs/local_function/doc/html/BOOST_LOCAL_FUNCTION_CONFIG_BIND_MAX.html 2012-04-27 11:35:12 EDT (Fri, 27 Apr 2012)
@@ -33,7 +33,7 @@

</span>BOOST_LOCAL_FUNCTION_CONFIG_BIND_MAX</pre></div>
<div class="refsect1">
-<a name="id861454"></a><h2>Description</h2>
+<a name="id842075"></a><h2>Description</h2>
<p>If programmers leave this configuration macro undefined, its default value is <code class="computeroutput">10</code> (increasing this number might increase compilation time). When defined by programmers, this macro must be a non-negative integer number.</p>
<p><span class="bold"><strong>Note:</strong></span> This macro specifies the maximum number of bound variables excluding local function parameters (which are instead specified by <code class="computeroutput"><a class="link" href="BOOST_LOCAL_FUNCTION_CONFIG_ARITY_MAX.html" title="Macro BOOST_LOCAL_FUNCTION_CONFIG_ARITY_MAX">BOOST_LOCAL_FUNCTION_CONFIG_ARITY_MAX</a></code>).</p>
<p><span class="bold"><strong>See:</strong></span> <a class="link" href="boost_localfunction/Tutorial.html" title="Tutorial">Tutorial</a> section, <a class="link" href="boost_localfunction/Getting_Started.html" title="Getting Started"> Getting Started</a> section, <code class="computeroutput"><a class="link" href="BOOST_LOCAL_FUNCTION_CONFIG_ARITY_MAX.html" title="Macro BOOST_LOCAL_FUNCTION_CONFIG_ARITY_MAX">BOOST_LOCAL_FUNCTION_CONFIG_ARITY_MAX</a></code>. </p>

Modified: trunk/libs/local_function/doc/html/BOOST_LOCAL_FUNCTION_CONFIG_LOCALS_AS_TPARAMS.html
==============================================================================
--- trunk/libs/local_function/doc/html/BOOST_LOCAL_FUNCTION_CONFIG_LOCALS_AS_TPARAMS.html (original)
+++ trunk/libs/local_function/doc/html/BOOST_LOCAL_FUNCTION_CONFIG_LOCALS_AS_TPARAMS.html 2012-04-27 11:35:12 EDT (Fri, 27 Apr 2012)
@@ -33,7 +33,7 @@

</span>BOOST_LOCAL_FUNCTION_CONFIG_LOCALS_AS_TPARAMS</pre></div>
<div class="refsect1">
-<a name="id861529"></a><h2>Description</h2>
+<a name="id842150"></a><h2>Description</h2>
<p>If this macro is defined to <code class="computeroutput">1</code>, this library will assume that the compiler allows to pass local classes as template parameters: </p>
<pre class="programlisting"> <span class="keyword">template</span><span class="special"><</span><span class="keyword">typename</span> <span class="identifier">T</span><span class="special">></span> <span class="keyword">void</span> <span class="identifier">f</span><span class="special">(</span><span class="keyword">void</span><span class="special">)</span> <span class="special">{</span><span class="special">}</span>

Modified: trunk/libs/local_function/doc/html/BOOST_LOCAL_FUNCTION_ID.html
==============================================================================
--- trunk/libs/local_function/doc/html/BOOST_LOCAL_FUNCTION_ID.html (original)
+++ trunk/libs/local_function/doc/html/BOOST_LOCAL_FUNCTION_ID.html 2012-04-27 11:35:12 EDT (Fri, 27 Apr 2012)
@@ -33,7 +33,7 @@

</span>BOOST_LOCAL_FUNCTION_ID(id, declarations)</pre></div>
<div class="refsect1">
-<a name="id860164"></a><h2>Description</h2>
+<a name="id840171"></a><h2>Description</h2>
<p>This macro is equivalent to <code class="computeroutput"><a class="link" href="BOOST_LOCAL_FUNCTION.html" title="Macro BOOST_LOCAL_FUNCTION">BOOST_LOCAL_FUNCTION</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 the <a class="link" href="boost_localfunction/Advanced_Topics.html" title="Advanced Topics"> Advanced Topics</a> section).</p>
<p><span class="bold"><strong>Parameters:</strong></span> </p>
<div class="informaltable"><table class="table">

Modified: trunk/libs/local_function/doc/html/BOOST_LOCAL_FUNCTION_NAME.html
==============================================================================
--- trunk/libs/local_function/doc/html/BOOST_LOCAL_FUNCTION_NAME.html (original)
+++ trunk/libs/local_function/doc/html/BOOST_LOCAL_FUNCTION_NAME.html 2012-04-27 11:35:12 EDT (Fri, 27 Apr 2012)
@@ -33,7 +33,7 @@

</span>BOOST_LOCAL_FUNCTION_NAME(qualified_name)</pre></div>
<div class="refsect1">
-<a name="id860548"></a><h2>Description</h2>
+<a name="id841169"></a><h2>Description</h2>
<p>This macro must follow the local function body code block <code class="computeroutput">{ ... }</code>: </p>
<pre class="programlisting"><span class="special">{</span> <span class="comment">// Some declarative context.</span>
<span class="special">...</span>

Modified: trunk/libs/local_function/doc/html/BOOST_LOCAL_FUNCTION_NAME_TPL.html
==============================================================================
--- trunk/libs/local_function/doc/html/BOOST_LOCAL_FUNCTION_NAME_TPL.html (original)
+++ trunk/libs/local_function/doc/html/BOOST_LOCAL_FUNCTION_NAME_TPL.html 2012-04-27 11:35:12 EDT (Fri, 27 Apr 2012)
@@ -33,7 +33,7 @@

</span>BOOST_LOCAL_FUNCTION_NAME_TPL(name)</pre></div>
<div class="refsect1">
-<a name="id860960"></a><h2>Description</h2>
+<a name="id841581"></a><h2>Description</h2>
<p>This macro must be used instead of <code class="computeroutput"><a class="link" href="BOOST_LOCAL_FUNCTION_NAME.html" title="Macro BOOST_LOCAL_FUNCTION_NAME">BOOST_LOCAL_FUNCTION_NAME</a></code> when declaring a local function within a template. A part from that, this macro has the exact same syntax a <code class="computeroutput"><a class="link" href="BOOST_LOCAL_FUNCTION_NAME.html" title="Macro BOOST_LOCAL_FUNCTION_NAME">BOOST_LOCAL_FUNCTION_NAME</a></code> (see <code class="computeroutput"><a class="link" href="BOOST_LOCAL_FUNCTION_NAME.html" title="Macro BOOST_LOCAL_FUNCTION_NAME">BOOST_LOCAL_FUNCTION_NAME</a></code> for more information): </p>
<pre class="programlisting"><span class="special">{</span> <span class="comment">// Some declarative context within a template.</span>
<span class="special">...</span>

Modified: trunk/libs/local_function/doc/html/BOOST_LOCAL_FUNCTION_TPL.html
==============================================================================
--- trunk/libs/local_function/doc/html/BOOST_LOCAL_FUNCTION_TPL.html (original)
+++ trunk/libs/local_function/doc/html/BOOST_LOCAL_FUNCTION_TPL.html 2012-04-27 11:35:12 EDT (Fri, 27 Apr 2012)
@@ -33,7 +33,7 @@

</span>BOOST_LOCAL_FUNCTION_TPL(declarations)</pre></div>
<div class="refsect1">
-<a name="id859948"></a><h2>Description</h2>
+<a name="id839955"></a><h2>Description</h2>
<p>This macro must be used instead of <code class="computeroutput"><a class="link" href="BOOST_LOCAL_FUNCTION.html" title="Macro BOOST_LOCAL_FUNCTION">BOOST_LOCAL_FUNCTION</a></code> when declaring a local function within a template. A part from that, this macro has the exact same syntax a <code class="computeroutput"><a class="link" href="BOOST_LOCAL_FUNCTION.html" title="Macro BOOST_LOCAL_FUNCTION">BOOST_LOCAL_FUNCTION</a></code> (see <code class="computeroutput"><a class="link" href="BOOST_LOCAL_FUNCTION.html" title="Macro BOOST_LOCAL_FUNCTION">BOOST_LOCAL_FUNCTION</a></code> for more information): </p>
<pre class="programlisting"><span class="special">{</span> <span class="comment">// Some declarative context within a template.</span>
<span class="special">...</span>

Modified: trunk/libs/local_function/doc/html/BOOST_LOCAL_FUNCTION_TPL_ID.html
==============================================================================
--- trunk/libs/local_function/doc/html/BOOST_LOCAL_FUNCTION_TPL_ID.html (original)
+++ trunk/libs/local_function/doc/html/BOOST_LOCAL_FUNCTION_TPL_ID.html 2012-04-27 11:35:12 EDT (Fri, 27 Apr 2012)
@@ -33,7 +33,7 @@

</span>BOOST_LOCAL_FUNCTION_TPL_ID(id, declarations)</pre></div>
<div class="refsect1">
-<a name="id860342"></a><h2>Description</h2>
+<a name="id840348"></a><h2>Description</h2>
<p>This macro must be used instead of <code class="computeroutput"><a class="link" href="BOOST_LOCAL_FUNCTION_TPL.html" title="Macro BOOST_LOCAL_FUNCTION_TPL">BOOST_LOCAL_FUNCTION_TPL</a></code> when declaring multiple local functions on the same line within a template. A part from that, this macro has the exact same syntax as <code class="computeroutput"><a class="link" href="BOOST_LOCAL_FUNCTION_TPL.html" title="Macro BOOST_LOCAL_FUNCTION_TPL">BOOST_LOCAL_FUNCTION_TPL</a></code> (see <code class="computeroutput"><a class="link" href="BOOST_LOCAL_FUNCTION_TPL.html" title="Macro BOOST_LOCAL_FUNCTION_TPL">BOOST_LOCAL_FUNCTION_TPL</a></code> for more information).</p>
<p><span class="bold"><strong>Parameters:</strong></span> </p>
<div class="informaltable"><table class="table">

Modified: trunk/libs/local_function/doc/html/BOOST_LOCAL_FUNCTION_TYPEOF.html
==============================================================================
--- trunk/libs/local_function/doc/html/BOOST_LOCAL_FUNCTION_TYPEOF.html (original)
+++ trunk/libs/local_function/doc/html/BOOST_LOCAL_FUNCTION_TYPEOF.html 2012-04-27 11:35:12 EDT (Fri, 27 Apr 2012)
@@ -33,7 +33,7 @@

</span>BOOST_LOCAL_FUNCTION_TYPEOF(bound_variable_name)</pre></div>
<div class="refsect1">
-<a name="id861159"></a><h2>Description</h2>
+<a name="id841780"></a><h2>Description</h2>
<p>This macro can be used within the local functions body to refer to the bound variable types so to declare local variables, check concepts (using Boost.ConceptCheck), etc (see the <a class="link" href="boost_localfunction/Advanced_Topics.html" title="Advanced Topics"> Advanced Topics</a> section). This way the local function can be programmed entirely without explicitly specifying the bound variable types thus facilitating maintenance (e.g., if the type of a bound variable changes in the enclosing scope, the local function code does not have to change).</p>
<p><span class="bold"><strong>Parameters:</strong></span> </p>
<div class="informaltable"><table class="table">

Modified: trunk/libs/local_function/doc/html/boost_localfunction/Advanced_Topics.html
==============================================================================
--- trunk/libs/local_function/doc/html/boost_localfunction/Advanced_Topics.html (original)
+++ trunk/libs/local_function/doc/html/boost_localfunction/Advanced_Topics.html 2012-04-27 11:35:12 EDT (Fri, 27 Apr 2012)
@@ -781,8 +781,8 @@
<span class="special">></span> <span class="identifier">add</span><span class="special">(</span><span class="identifier">add_s</span><span class="special">,</span> <span class="identifier">add_d</span><span class="special">,</span> <span class="identifier">add_d</span><span class="special">,</span> <span class="identifier">add_i</span><span class="special">);</span> <span class="comment">// Overloaded function object.</span>

<span class="identifier">BOOST_TEST</span><span class="special">(</span><span class="identifier">add</span><span class="special">(</span><span class="string">"xyz"</span><span class="special">)</span> <span class="special">==</span> <span class="string">"abcxyz"</span><span class="special">);</span> <span class="comment">// Call `add_s`.</span>
-<span class="identifier">BOOST_TEST</span><span class="special">(</span><span class="identifier">fabs</span><span class="special">(</span><span class="identifier">add</span><span class="special">(</span><span class="number">3.21</span><span class="special">)</span> <span class="special">-</span> <span class="number">4.44</span><span class="special">)</span> <span class="special"><</span> <span class="number">0.001</span><span class="special">);</span> <span class="comment">// Call `add_d` (no default).</span>
-<span class="identifier">BOOST_TEST</span><span class="special">(</span><span class="identifier">fabs</span><span class="special">(</span><span class="identifier">add</span><span class="special">(</span><span class="number">3.21</span><span class="special">,</span> <span class="number">40.0</span><span class="special">)</span> <span class="special">-</span> <span class="number">44.44</span><span class="special">)</span> <span class="special"><</span> <span class="number">0.001</span><span class="special">);</span> <span class="comment">// Call `add_d`.</span>
+<span class="identifier">BOOST_TEST</span><span class="special">((</span><span class="number">4.44</span> <span class="special">-</span> <span class="identifier">add</span><span class="special">(</span><span class="number">3.21</span><span class="special">))</span> <span class="special"><=</span> <span class="number">0.001</span><span class="special">);</span> <span class="comment">// Call `add_d` (no default).</span>
+<span class="identifier">BOOST_TEST</span><span class="special">((</span><span class="number">44.44</span> <span class="special">-</span> <span class="identifier">add</span><span class="special">(</span><span class="number">3.21</span><span class="special">,</span> <span class="number">40.0</span><span class="special">))</span> <span class="special"><=</span> <span class="number">0.001</span><span class="special">);</span> <span class="comment">// Call `add_d`.</span>
<span class="identifier">BOOST_TEST</span><span class="special">(</span><span class="identifier">add</span><span class="special">(</span><span class="number">1</span><span class="special">,</span> <span class="number">2</span><span class="special">)</span> <span class="special">==</span> <span class="number">3</span><span class="special">);</span> <span class="comment">// Call `add_i`.</span>
</pre>
<p>
@@ -901,18 +901,18 @@
     <span class="special">}</span> <span class="identifier">BOOST_LOCAL_FUNCTION_NAME</span><span class="special">(</span><span class="identifier">dec</span><span class="special">)</span>

<span class="preprocessor">#define</span> <span class="identifier">LOCAL_INC_DEC_TPL</span><span class="special">(</span><span class="identifier">offset</span><span class="special">)</span> <span class="special">\</span>
- <span class="keyword">int</span> <span class="identifier">BOOST_LOCAL_FUNCTION_TPL_ID</span><span class="special">(</span><span class="identifier">BOOST_PP_CAT</span><span class="special">(</span><span class="identifier">inc</span><span class="special">,</span> <span class="identifier">__LINE__</span><span class="special">),</span> <span class="special">\</span>
- <span class="keyword">const</span> <span class="identifier">bind</span> <span class="identifier">offset</span><span class="special">,</span> <span class="keyword">const</span> <span class="keyword">int</span> <span class="identifier">x</span><span class="special">)</span> <span class="special">{</span> <span class="special">\</span>
+ <span class="identifier">T</span> <span class="identifier">BOOST_LOCAL_FUNCTION_TPL_ID</span><span class="special">(</span><span class="identifier">BOOST_PP_CAT</span><span class="special">(</span><span class="identifier">inc</span><span class="special">,</span> <span class="identifier">__LINE__</span><span class="special">),</span> <span class="special">\</span>
+ <span class="keyword">const</span> <span class="identifier">bind</span> <span class="identifier">offset</span><span class="special">,</span> <span class="keyword">const</span> <span class="identifier">T</span> <span class="identifier">x</span><span class="special">)</span> <span class="special">{</span> <span class="special">\</span>
         <span class="keyword">return</span> <span class="identifier">x</span> <span class="special">+</span> <span class="identifier">offset</span><span class="special">;</span> <span class="special">\</span>
- <span class="special">}</span> <span class="identifier">BOOST_LOCAL_FUNCTION_NAME</span><span class="special">(</span><span class="identifier">inc</span><span class="special">)</span> <span class="special">\</span>
+ <span class="special">}</span> <span class="identifier">BOOST_LOCAL_FUNCTION_NAME_TPL</span><span class="special">(</span><span class="identifier">inc</span><span class="special">)</span> <span class="special">\</span>
     <span class="special">\</span>
- <span class="keyword">int</span> <span class="identifier">BOOST_LOCAL_FUNCTION_TPL_ID</span><span class="special">(</span><span class="identifier">BOOST_PP_CAT</span><span class="special">(</span><span class="identifier">dec</span><span class="special">,</span> <span class="identifier">__LINE__</span><span class="special">),</span> <span class="special">\</span>
- <span class="keyword">const</span> <span class="identifier">bind</span> <span class="identifier">offset</span><span class="special">,</span> <span class="keyword">const</span> <span class="keyword">int</span> <span class="identifier">x</span><span class="special">)</span> <span class="special">{</span> <span class="special">\</span>
+ <span class="identifier">T</span> <span class="identifier">BOOST_LOCAL_FUNCTION_TPL_ID</span><span class="special">(</span><span class="identifier">BOOST_PP_CAT</span><span class="special">(</span><span class="identifier">dec</span><span class="special">,</span> <span class="identifier">__LINE__</span><span class="special">),</span> <span class="special">\</span>
+ <span class="keyword">const</span> <span class="identifier">bind</span> <span class="identifier">offset</span><span class="special">,</span> <span class="keyword">const</span> <span class="identifier">T</span> <span class="identifier">x</span><span class="special">)</span> <span class="special">{</span> <span class="special">\</span>
         <span class="keyword">return</span> <span class="identifier">x</span> <span class="special">-</span> <span class="identifier">offset</span><span class="special">;</span> <span class="special">\</span>
- <span class="special">}</span> <span class="identifier">BOOST_LOCAL_FUNCTION_NAME</span><span class="special">(</span><span class="identifier">dec</span><span class="special">)</span>
+ <span class="special">}</span> <span class="identifier">BOOST_LOCAL_FUNCTION_NAME_TPL</span><span class="special">(</span><span class="identifier">dec</span><span class="special">)</span>

<span class="keyword">template</span><span class="special"><</span><span class="keyword">typename</span> <span class="identifier">T</span><span class="special">></span>
-<span class="keyword">void</span> <span class="identifier">f</span><span class="special">(</span><span class="keyword">int</span> <span class="identifier">delta</span><span class="special">)</span> <span class="special">{</span>
+<span class="keyword">void</span> <span class="identifier">f</span><span class="special">(</span><span class="identifier">T</span> <span class="keyword">const</span><span class="special">&</span> <span class="identifier">delta</span><span class="special">)</span> <span class="special">{</span>
     <span class="identifier">LOCAL_INC_DEC_TPL</span><span class="special">(</span><span class="identifier">delta</span><span class="special">)</span> <span class="comment">// Multiple local functions on same line.</span>
     <span class="comment">/** @todo back to BOOST_TEST(dec(inc(123)) == 123)) and doc that on vacpp compiler composition doesn't work */</span>
     <span class="identifier">BOOST_TEST</span><span class="special">(</span><span class="identifier">inc</span><span class="special">(</span><span class="number">123</span><span class="special">)</span> <span class="special">==</span> <span class="number">123</span> <span class="special">+</span> <span class="identifier">delta</span><span class="special">);</span>
@@ -1210,10 +1210,10 @@
                     to dynamic binding or base function calls.
                   </p></div></td></tr></tbody>
</table></div>
-<h6>
+<h5>
<a name="boost_localfunction.Advanced_Topics.limitations__operators__etc_.h0"></a>
         <span><a name="boost_localfunction.Advanced_Topics.limitations__operators__etc_.operators"></a></span><a class="link" href="Advanced_Topics.html#boost_localfunction.Advanced_Topics.limitations__operators__etc_.operators">Operators</a>
- </h6>
+ </h5>
<p>
         Local functions cannot be operators. Naming a local function <code class="computeroutput"><span class="keyword">operator</span><span class="special">...</span></code>
         will generate a compile-time error. <sup>[<a name="boost_localfunction.Advanced_Topics.limitations__operators__etc_.f1" href="#ftn.boost_localfunction.Advanced_Topics.limitations__operators__etc_.f1" class="footnote">28</a>]</sup>
@@ -1229,10 +1229,10 @@
</pre>
<p>
       </p>
-<h6>
+<h5>
<a name="boost_localfunction.Advanced_Topics.limitations__operators__etc_.h1"></a>
         <span><a name="boost_localfunction.Advanced_Topics.limitations__operators__etc_.goto"></a></span><a class="link" href="Advanced_Topics.html#boost_localfunction.Advanced_Topics.limitations__operators__etc_.goto">Goto</a>
- </h6>
+ </h5>
<p>
         It is possible to jump with a <code class="computeroutput"><span class="keyword">goto</span></code>
         within the local function body. For example, the following compiles (see

Modified: trunk/libs/local_function/doc/html/boost_localfunction/Alternatives.html
==============================================================================
--- trunk/libs/local_function/doc/html/boost_localfunction/Alternatives.html (original)
+++ trunk/libs/local_function/doc/html/boost_localfunction/Alternatives.html 2012-04-27 11:35:12 EDT (Fri, 27 Apr 2012)
@@ -30,10 +30,10 @@
       This section compares the features offered by this library with similar features
       offered by C++ and by other libraries.
     </p>
-<h6>
+<h4>
<a name="boost_localfunction.Alternatives.h0"></a>
       <span><a name="boost_localfunction.Alternatives.features"></a></span><a class="link" href="Alternatives.html#boost_localfunction.Alternatives.features">Features</a>
- </h6>
+ </h4>
<p>
       The following table compares local function features.
     </p>
@@ -748,10 +748,10 @@
       The Boost.Phoenix library
       version 3.0 is used for this comparison.
     </p>
-<h6>
+<h4>
<a name="boost_localfunction.Alternatives.h1"></a>
       <span><a name="boost_localfunction.Alternatives.performances"></a></span><a class="link" href="Alternatives.html#boost_localfunction.Alternatives.performances">Performances</a>
- </h6>
+ </h4>
<p>
       The following tables compare run-times, compile-times, and binary sizes for
       the different alternatives to local functions presented in this section.

Modified: trunk/libs/local_function/doc/html/boost_localfunction/Implementation.html
==============================================================================
--- trunk/libs/local_function/doc/html/boost_localfunction/Implementation.html (original)
+++ trunk/libs/local_function/doc/html/boost_localfunction/Implementation.html 2012-04-27 11:35:12 EDT (Fri, 27 Apr 2012)
@@ -42,11 +42,11 @@
         listed here.
       </p></td></tr>
</table></div>
-<h6>
+<h4>
<a name="boost_localfunction.Implementation.h0"></a>
       <span><a name="boost_localfunction.Implementation.local_classes_as_template_parameters"></a></span><a class="link" href="Implementation.html#boost_localfunction.Implementation.local_classes_as_template_parameters">Local
       Classes as Template Parameters</a>
- </h6>
+ </h4>
<p>
       This library uses a local class to implement the local function object. However,
       in C++03
@@ -161,11 +161,11 @@
       in order to take full advantage of compiler optimizations that inline the local
       function calls.
     </p>
-<h6>
+<h4>
<a name="boost_localfunction.Implementation.h1"></a>
       <span><a name="boost_localfunction.Implementation.parsing_macros"></a></span><a class="link" href="Implementation.html#boost_localfunction.Implementation.parsing_macros">Parsing
       Macros</a>
- </h6>
+ </h4>
<p>
       This library macros can parse the list of specified parameters and detect if
       any of the bound variable names matches the token <code class="computeroutput"><span class="identifier">this_</span></code>

Modified: trunk/libs/local_function/doc/html/boost_localfunction/No_Variadic_Macros.html
==============================================================================
--- trunk/libs/local_function/doc/html/boost_localfunction/No_Variadic_Macros.html (original)
+++ trunk/libs/local_function/doc/html/boost_localfunction/No_Variadic_Macros.html 2012-04-27 11:35:12 EDT (Fri, 27 Apr 2012)
@@ -31,10 +31,10 @@
       This section illustrates an alternative syntax for compilers without variadic
       macro support.
     </p>
-<h6>
+<h4>
<a name="boost_localfunction.No_Variadic_Macros.h0"></a>
       <span><a name="boost_localfunction.No_Variadic_Macros.sequence_syntax"></a></span><a class="link" href="No_Variadic_Macros.html#boost_localfunction.No_Variadic_Macros.sequence_syntax">Sequence Syntax</a>
- </h6>
+ </h4>
<p>
       Most modern compilers support <a href="http://en.wikipedia.org/wiki/Variadic_macro" target="_top">variaid
       macros</a> (notably, these include GCC, MSVC, and all C++11
@@ -113,10 +113,10 @@
</pre>
<p>
     </p>
-<h6>
+<h4>
<a name="boost_localfunction.No_Variadic_Macros.h1"></a>
       <span><a name="boost_localfunction.No_Variadic_Macros.examples"></a></span><a class="link" href="No_Variadic_Macros.html#boost_localfunction.No_Variadic_Macros.examples">Examples</a>
- </h6>
+ </h4>
<p>
       For reference, the following is a list of most of the examples presented in
       this documentation reprogrammed using the sequence syntax instead of the comma-separated

Modified: trunk/libs/local_function/doc/html/boost_localfunction/Release_Notes.html
==============================================================================
--- trunk/libs/local_function/doc/html/boost_localfunction/Release_Notes.html (original)
+++ trunk/libs/local_function/doc/html/boost_localfunction/Release_Notes.html 2012-04-27 11:35:12 EDT (Fri, 27 Apr 2012)
@@ -30,11 +30,11 @@
       This section lists the major changes between different library releases (in
       chronological order).
     </p>
-<h6>
+<h4>
<a name="boost_localfunction.Release_Notes.h0"></a>
       <span><a name="boost_localfunction.Release_Notes.version_1_0_0__2012_04_12_"></a></span><a class="link" href="Release_Notes.html#boost_localfunction.Release_Notes.version_1_0_0__2012_04_12_">Version
       1.0.0 (2012-04-12)</a>
- </h6>
+ </h4>
<div class="orderedlist"><ol class="orderedlist" type="1">
<li class="listitem">
           Incorporated all comments from the <a href="http://lists.boost.org/boost-announce/2011/12/0340.php" target="_top">Boost
@@ -77,11 +77,11 @@
           Fixed compilation on Boost regression test platforms.
         </li>
</ol></div>
-<h6>
+<h4>
<a name="boost_localfunction.Release_Notes.h1"></a>
       <span><a name="boost_localfunction.Release_Notes.version_0_2_0__2011_05_14_"></a></span><a class="link" href="Release_Notes.html#boost_localfunction.Release_Notes.version_0_2_0__2011_05_14_">Version
       0.2.0 (2011-05-14)</a>
- </h6>
+ </h4>
<div class="orderedlist"><ol class="orderedlist" type="1">
<li class="listitem">
           Replaced parenthesized syntax with variadic and sequencing macro syntaxes.
@@ -118,11 +118,11 @@
           one another.
         </li>
</ol></div>
-<h6>
+<h4>
<a name="boost_localfunction.Release_Notes.h2"></a>
       <span><a name="boost_localfunction.Release_Notes.version_0_1_1__2011_01_10_"></a></span><a class="link" href="Release_Notes.html#boost_localfunction.Release_Notes.version_0_1_1__2011_01_10_">Version
       0.1.1 (2011-01-10)</a>
- </h6>
+ </h4>
<div class="orderedlist"><ol class="orderedlist" type="1">
<li class="listitem">
           Uploaded library source into Boost SVN sandbox.
@@ -134,19 +134,19 @@
           Added Release section to documentation.
         </li>
</ol></div>
-<h6>
+<h4>
<a name="boost_localfunction.Release_Notes.h3"></a>
       <span><a name="boost_localfunction.Release_Notes.version_0_1_0__2011_01_03_"></a></span><a class="link" href="Release_Notes.html#boost_localfunction.Release_Notes.version_0_1_0__2011_01_03_">Version
       0.1.0 (2011-01-03)</a>
- </h6>
+ </h4>
<div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
           Shared with Boost for first round of comments.
         </li></ol></div>
-<h6>
+<h4>
<a name="boost_localfunction.Release_Notes.h4"></a>
       <span><a name="boost_localfunction.Release_Notes.version_0_0_1__2010_12_15_"></a></span><a class="link" href="Release_Notes.html#boost_localfunction.Release_Notes.version_0_0_1__2010_12_15_">Version
       0.0.1 (2010-12-15)</a>
- </h6>
+ </h4>
<div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
           Completed development, examples, and documentation.
         </li></ol></div>

Modified: trunk/libs/local_function/doc/html/index.html
==============================================================================
--- trunk/libs/local_function/doc/html/index.html (original)
+++ trunk/libs/local_function/doc/html/index.html 2012-04-27 11:35:12 EDT (Fri, 27 Apr 2012)
@@ -226,7 +226,7 @@
</div>
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
-<td align="left"><p><small>Last revised: April 13, 2012 at 00:19:19 GMT</small></p></td>
+<td align="left"><p><small>Last revised: April 27, 2012 at 15:28:13 GMT</small></p></td>
<td align="right"><div class="copyright-footer"></div></td>
</tr></table>
<hr>

Modified: trunk/libs/local_function/doc/implementation.qbk
==============================================================================
--- trunk/libs/local_function/doc/implementation.qbk (original)
+++ trunk/libs/local_function/doc/implementation.qbk 2012-04-27 11:35:12 EDT (Fri, 27 Apr 2012)
@@ -14,7 +14,7 @@
There is absolutely no guarantee that the library implementation uses the exact code listed here.
]

-[h5 Local Classes as Template Parameters]
+[heading Local Classes as Template Parameters]

This library uses a local class to implement the local function object.
However, in __CXX03__ local classes (and therefore the local function objects they implement) cannot be passed as template parameters (e.g., to the `std::for_each` algorithm), this is instead possible in __CXX11__, MSVC, and some other compilers (see __N2657__ and __Boost_Config__'s `BOOST_NO_LOCAL_CLASS_TEMPLATE_PARAMETERS`).
@@ -34,7 +34,7 @@
However, neither one of the two tricks was observed to allow for compiler optimizations that inline the local function calls (because they rely on one indirect function call via either a function pointer or a virtual function respectively).
Therefore, on compilers that accept local classes as template parameters (MSVC, __CXX11__, etc, see __N2657__ and __Boost_Config__'s `BOOST_NO_LOCAL_CLASS_TEMPLATE_PARAMETERS`), this library automatically generates code that passes the local class type directly as template parameter without using neither one of these two tricks in order to take full advantage of compiler optimizations that inline the local function calls.

-[h5 Parsing Macros]
+[heading Parsing Macros]

This library macros can parse the list of specified parameters and detect if any of the bound variable names matches the token `this_` (to generate special code to bind the object in scope), or if the variable is bound by `const` (to generate special code to bind by constant), etc.
The parameter tokens are inspected using preprocessor meta-programming and specifically using the macros defined by the files in the =boost/local_function/detail/preprocessor/keyword/= directory.

Modified: trunk/libs/local_function/doc/no_variadic_macros.qbk
==============================================================================
--- trunk/libs/local_function/doc/no_variadic_macros.qbk (original)
+++ trunk/libs/local_function/doc/no_variadic_macros.qbk 2012-04-27 11:35:12 EDT (Fri, 27 Apr 2012)
@@ -9,7 +9,7 @@

This section illustrates an alternative syntax for compilers without variadic macro support.

-[h5 Sequence Syntax]
+[heading Sequence Syntax]

Most modern compilers support [@http://en.wikipedia.org/wiki/Variadic_macro variaid macros] (notably, these include GCC, MSVC, and all __CXX11__ compilers).
However, in the rare case that programmers need to use this library on a compiler without variadic macros, this library also allows to specify its macro parameters using a __Boost_Preprocessor__ sequence where tokens are separated by round parenthesis `()`:
@@ -33,7 +33,7 @@

[ten_void]

-[h5 Examples]
+[heading Examples]

For reference, the following is a list of most of the examples presented in this documentation reprogrammed using the sequence syntax instead of the comma-separated syntax (in alphabetic order):

Modified: trunk/libs/local_function/doc/release_notes.qbk
==============================================================================
--- trunk/libs/local_function/doc/release_notes.qbk (original)
+++ trunk/libs/local_function/doc/release_notes.qbk 2012-04-27 11:35:12 EDT (Fri, 27 Apr 2012)
@@ -9,7 +9,7 @@

This section lists the major changes between different library releases (in chronological order).

-[h5 Version 1.0.0 (2012-04-12)]
+[heading Version 1.0.0 (2012-04-12)]

# Incorporated all comments from the [@http://lists.boost.org/boost-announce/2011/12/0340.php Boost review of this library].
# Removed local blocks and local exits.
@@ -23,7 +23,7 @@
# Added `..._ID` macros for multiple expansions on the same line.
# Fixed compilation on Boost regression test platforms.

-[h5 Version 0.2.0 (2011-05-14)]
+[heading Version 0.2.0 (2011-05-14)]

# Replaced parenthesized syntax with variadic and sequencing macro syntaxes.
# Profiled library performances against other approaches.
@@ -36,17 +36,17 @@
# Added functor to overload local functions (and functors in general).
# Implemented support for nesting local functions, blocks, and exits into one another.

-[h5 Version 0.1.1 (2011-01-10)]
+[heading Version 0.1.1 (2011-01-10)]

# Uploaded library source into Boost SVN sandbox.
# Fixed prev/next arrows and other minor layouts in documentation.
# Added Release section to documentation.

-[h5 Version 0.1.0 (2011-01-03)]
+[heading Version 0.1.0 (2011-01-03)]

# Shared with Boost for first round of comments.

-[h5 Version 0.0.1 (2010-12-15)]
+[heading Version 0.0.1 (2010-12-15)]

# Completed development, examples, and documentation.

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-27 11:35:12 EDT (Fri, 27 Apr 2012)
@@ -33,7 +33,7 @@

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

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-27 11:35:12 EDT (Fri, 27 Apr 2012)
@@ -33,7 +33,7 @@

</span>BOOST_SCOPE_EXIT_ALL(capture_list)</pre></div>
<div class="refsect1">
-<a name="id816102"></a><h2>Description</h2>
+<a name="id811732"></a><h2>Description</h2>
<p>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):</p>
<pre class="programlisting"> <span class="special">{</span> <span class="comment">// Some local scope.</span>
<span class="special">...</span>

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-27 11:35:12 EDT (Fri, 27 Apr 2012)
@@ -33,7 +33,7 @@

</span>BOOST_SCOPE_EXIT_ALL_ID(id, capture_list)</pre></div>
<div class="refsect1">
-<a name="id816754"></a><h2>Description</h2>
+<a name="id812385"></a><h2>Description</h2>
<p>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).</p>
<p><span class="bold"><strong>Parameters:</strong></span> </p>
<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-27 11:35:12 EDT (Fri, 27 Apr 2012)
@@ -33,7 +33,7 @@

</span>BOOST_SCOPE_EXIT_CONFIG_USE_LAMBDAS</pre></div>
<div class="refsect1">
-<a name="id818882"></a><h2>Description</h2>
+<a name="id814513"></a><h2>Description</h2>
<p>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.</p>
<p><span class="bold"><strong>Warning:</strong></span> 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).</p>
<p>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).</p>

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-27 11:35:12 EDT (Fri, 27 Apr 2012)
@@ -33,7 +33,7 @@

</span>BOOST_SCOPE_EXIT_END</pre></div>
<div class="refsect1">
-<a name="id816915"></a><h2>Description</h2>
+<a name="id812546"></a><h2>Description</h2>
<p>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>:</p>
<pre class="programlisting"> <span class="special">{</span> <span class="comment">// Some local scope.</span>
<span class="special">...</span>

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-27 11:35:12 EDT (Fri, 27 Apr 2012)
@@ -33,7 +33,7 @@

</span>BOOST_SCOPE_EXIT_END_ID(id)</pre></div>
<div class="refsect1">
-<a name="id818750"></a><h2>Description</h2>
+<a name="id814381"></a><h2>Description</h2>
<p>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).</p>
<p><span class="bold"><strong>Parameters:</strong></span> </p>
<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-27 11:35:12 EDT (Fri, 27 Apr 2012)
@@ -33,7 +33,7 @@

</span>BOOST_SCOPE_EXIT_ID(id, capture_list)</pre></div>
<div class="refsect1">
-<a name="id815768"></a><h2>Description</h2>
+<a name="id811399"></a><h2>Description</h2>
<p>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).</p>
<p><span class="bold"><strong>Parameters:</strong></span> </p>
<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-27 11:35:12 EDT (Fri, 27 Apr 2012)
@@ -33,7 +33,7 @@

</span>BOOST_SCOPE_EXIT_TPL(capture_list)</pre></div>
<div class="refsect1">
-<a name="id815216"></a><h2>Description</h2>
+<a name="id810847"></a><h2>Description</h2>
<p>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:</p>
<pre class="programlisting"> <span class="special">{</span> <span class="comment">// Some local scope.</span>
<span class="special">...</span>

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-27 11:35:12 EDT (Fri, 27 Apr 2012)
@@ -33,7 +33,7 @@

</span>BOOST_SCOPE_EXIT_TPL_ID(id, capture_list)</pre></div>
<div class="refsect1">
-<a name="id815931"></a><h2>Description</h2>
+<a name="id811562"></a><h2>Description</h2>
<p>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.</p>
<p><span class="bold"><strong>Parameters:</strong></span> </p>
<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-27 11:35:12 EDT (Fri, 27 Apr 2012)
@@ -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"><p><small>Last revised: April 13, 2012 at 16:49:31 GMT</small></p></td>
+<td align="left"><p><small>Last revised: April 27, 2012 at 15:30:51 GMT</small></p></td>
<td align="right"><div class="copyright-footer"></div></td>
</tr></table>
<hr>

Modified: trunk/libs/scope_exit/doc/html/scope_exit/Alternatives.html
==============================================================================
--- trunk/libs/scope_exit/doc/html/scope_exit/Alternatives.html (original)
+++ trunk/libs/scope_exit/doc/html/scope_exit/Alternatives.html 2012-04-27 11:35:12 EDT (Fri, 27 Apr 2012)
@@ -29,10 +29,10 @@
<p>
       This section presents some alternative and related work to <a class="link" href="../index.html" title="Chapter 1. Boost.ScopeExit 1.1.0">Boost.ScopeExit</a>.
     </p>
-<h6>
+<h4>
<a name="scope_exit.Alternatives.h0"></a>
       <span><a name="scope_exit.Alternatives.try_catch"></a></span><a class="link" href="Alternatives.html#scope_exit.Alternatives.try_catch">Try-Catch</a>
- </h6>
+ </h4>
<p>
       This is an example of using a badly designed <code class="computeroutput"><span class="identifier">file</span></code>
       class. An instance of <code class="computeroutput"><span class="identifier">file</span></code>
@@ -93,10 +93,10 @@
</pre>
<p>
     </p>
-<h6>
+<h4>
<a name="scope_exit.Alternatives.h1"></a>
       <span><a name="scope_exit.Alternatives.raii"></a></span><a class="link" href="Alternatives.html#scope_exit.Alternatives.raii">RAII</a>
- </h6>
+ </h4>
<p>
       <a href="http://www.research.att.com/~bs/glossary.html#Gresource-acquisition-is-initialization" target="_top">RAII</a>
       is absolutely perfect for the <code class="computeroutput"><span class="identifier">file</span></code>
@@ -145,11 +145,11 @@
       Or with specialized containers such as Boost.PointerContainer
       or Boost.Multi-Index.
     </p>
-<h6>
+<h4>
<a name="scope_exit.Alternatives.h2"></a>
       <span><a name="scope_exit.Alternatives.scope_guards"></a></span><a class="link" href="Alternatives.html#scope_exit.Alternatives.scope_guards">Scope
       Guards</a>
- </h6>
+ </h4>
<p>
       Imagine that a new currency rate is introduced before performing a transaction
       (see also []):
@@ -240,11 +240,11 @@
</pre>
<p>
     </p>
-<h6>
+<h4>
<a name="scope_exit.Alternatives.h3"></a>
       <span><a name="scope_exit.Alternatives.the_d_programming_language"></a></span><a class="link" href="Alternatives.html#scope_exit.Alternatives.the_d_programming_language">The
       D Programming Language</a>
- </h6>
+ </h4>
<p>
       <a class="link" href="../index.html" title="Chapter 1. Boost.ScopeExit 1.1.0">Boost.ScopeExit</a> is similar to scope(exit)
       feature built into the D
@@ -262,11 +262,11 @@
       variable (similarly to some examples presented in the <a class="link" href="Tutorial.html" title="Tutorial">Tutorial</a>
       section).
     </p>
-<h6>
+<h4>
<a name="scope_exit.Alternatives.h4"></a>
       <span><a name="scope_exit.Alternatives.c__11_lambdas"></a></span><a class="link" href="Alternatives.html#scope_exit.Alternatives.c__11_lambdas">C++11
       Lambdas</a>
- </h6>
+ </h4>
<p>
       Using C++11 lambdas, it is relatively easy to implement the <a class="link" href="../index.html" title="Chapter 1. Boost.ScopeExit 1.1.0">Boost.ScopeExit</a>
       construct. For example (see also world_cxx11_lambda.cpp):

Modified: trunk/libs/scope_exit/doc/html/scope_exit/No_Variadic_Macros.html
==============================================================================
--- trunk/libs/scope_exit/doc/html/scope_exit/No_Variadic_Macros.html (original)
+++ trunk/libs/scope_exit/doc/html/scope_exit/No_Variadic_Macros.html 2012-04-27 11:35:12 EDT (Fri, 27 Apr 2012)
@@ -30,11 +30,11 @@
       This section presents an alternative syntax for compilers without variadic
       macro support.
     </p>
-<h6>
+<h4>
<a name="scope_exit.No_Variadic_Macros.h0"></a>
       <span><a name="scope_exit.No_Variadic_Macros.sequence_syntax"></a></span><a class="link" href="No_Variadic_Macros.html#scope_exit.No_Variadic_Macros.sequence_syntax">Sequence
       Syntax</a>
- </h6>
+ </h4>
<p>
       Most modern compilers support variadic macros (notably, these include GCC,
       MSVC, and all C++11 compilers). <sup>[<a name="scope_exit.No_Variadic_Macros.f0" href="#ftn.scope_exit.No_Variadic_Macros.f0" class="footnote">10</a>]</sup> However, in the rare case that programmers need to use this library
@@ -150,10 +150,10 @@
</pre>
<p>
     </p>
-<h6>
+<h4>
<a name="scope_exit.No_Variadic_Macros.h1"></a>
       <span><a name="scope_exit.No_Variadic_Macros.examples"></a></span><a class="link" href="No_Variadic_Macros.html#scope_exit.No_Variadic_Macros.examples">Examples</a>
- </h6>
+ </h4>
<p>
       For reference, the following is a list of most of the examples presented in
       this documentation reprogrammed using the Boost.Preprocessor

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-27 11:35:12 EDT (Fri, 27 Apr 2012)
@@ -294,7 +294,7 @@

This section presents some alternative and related work to __Boost_ScopeExit__.

-[h5 Try-Catch]
+[heading Try-Catch]

This is an example of using a badly designed `file` class.
An instance of `file` does not close the file in its destructor, a programmer is expected to call the `close` member function explicitly.
@@ -314,7 +314,7 @@

[try_catch_good]

-[h5 RAII]
+[heading RAII]

__RAII__ is absolutely perfect for the `file` class introduced above.
Use of a properly designed `file` class would look like:
@@ -352,7 +352,7 @@

Or with specialized containers such as __Boost_PointerContainer__ or __Boost_Multi_Index__.

-[h5 Scope Guards]
+[heading Scope Guards]

Imagine that a new currency rate is introduced before performing a transaction (see also []):

@@ -403,7 +403,7 @@

[scope_guard_exit]

-[h5 The D Programming Language]
+[heading The D Programming Language]

__Boost_ScopeExit__ is similar to __D_scope_exit__ feature built into the __D__ programming language.

@@ -411,7 +411,7 @@
Unfortunately, these are not possible in C++ because failure or success conditions cannot be determined by calling `std::uncaught_exception` (see [@http://www.gotw.ca/gotw/047.htm Guru of the Week #47] for details about `std::uncaught_exception` and if it has any good use at all).
However, this is not a big problem because these two __D__'s constructs can be expressed in terms of __D_scope_exit__ and a `bool commit` variable (similarly to some examples presented in the __Tutorial__ section).

-[h5 C++11 Lambdas]
+[heading C++11 Lambdas]

Using C++11 lambdas, it is relatively easy to implement the __Boost_ScopeExit__ construct.
For example (see also [@../../example/world_cxx11_lambda.cpp =world_cxx11_lambda.cpp=]):
@@ -426,7 +426,7 @@

This section presents an alternative syntax for compilers without variadic macro support.

-[h5 Sequence Syntax]
+[heading Sequence Syntax]

Most modern compilers support variadic macros (notably, these include GCC, MSVC, and all C++11 compilers).
[footnote
@@ -455,7 +455,7 @@

[world_void]

-[h5 Examples]
+[heading Examples]

For reference, the following is a list of most of the examples presented in this documentation reprogrammed using the __Boost_Preprocessor__ sequence syntax instead of comma-separated lists (in alphabetic order):

Next message: vicente.botet_at_[hidden]: "[Boost-commit] svn:boost r78222 - trunk/libs/thread/example"
Previous message: afojgo_at_[hidden]: "[Boost-commit] svn:boost r78220 - in sandbox/icl/libs/xplore/br1/sqlbrowser: . Dag"

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