|
|
Boost-Commit : |
Subject: [Boost-commit] svn:boost r66252 - in trunk/libs/spirit/phoenix/doc: . html html/phoenix
From: hartmut.kaiser_at_[hidden]
Date: 2010-10-29 11:59:41
Author: hkaiser
Date: 2010-10-29 11:59:36 EDT (Fri, 29 Oct 2010)
New Revision: 66252
URL: http://svn.boost.org/trac/boost/changeset/66252
Log:
Phoenix: Applying doc patch
Text files modified:
trunk/libs/spirit/phoenix/doc/html/index.html | 16 ++++++------
trunk/libs/spirit/phoenix/doc/html/phoenix/acknowledgement.html | 4 +-
trunk/libs/spirit/phoenix/doc/html/phoenix/actors.html | 2
trunk/libs/spirit/phoenix/doc/html/phoenix/algorithm.html | 8 +++---
trunk/libs/spirit/phoenix/doc/html/phoenix/basics.html | 12 ++++----
trunk/libs/spirit/phoenix/doc/html/phoenix/composite.html | 52 ++++++++++++++++++++--------------------
trunk/libs/spirit/phoenix/doc/html/phoenix/container.html | 6 ++--
trunk/libs/spirit/phoenix/doc/html/phoenix/inside_phoenix.html | 36 +++++++++++++-------------
trunk/libs/spirit/phoenix/doc/html/phoenix/introduction.html | 4 +-
trunk/libs/spirit/phoenix/doc/html/phoenix/organization.html | 10 +++---
trunk/libs/spirit/phoenix/doc/html/phoenix/primitives.html | 18 ++++++------
trunk/libs/spirit/phoenix/doc/html/phoenix/references.html | 2
trunk/libs/spirit/phoenix/doc/html/phoenix/starter_kit.html | 18 ++++++------
trunk/libs/spirit/phoenix/doc/html/phoenix/wrap_up.html | 6 ++--
trunk/libs/spirit/phoenix/doc/users_manual.qbk | 34 +++++++++++++-------------
15 files changed, 114 insertions(+), 114 deletions(-)
Modified: trunk/libs/spirit/phoenix/doc/html/index.html
==============================================================================
--- trunk/libs/spirit/phoenix/doc/html/index.html (original)
+++ trunk/libs/spirit/phoenix/doc/html/index.html 2010-10-29 11:59:36 EDT (Fri, 29 Oct 2010)
@@ -3,7 +3,7 @@
<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Chapter 1. Phoenix 2.0</title>
<link rel="stylesheet" href="../../../../../doc/src/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
<link rel="home" href="index.html" title="Chapter 1. Phoenix 2.0">
<link rel="next" href="phoenix/introduction.html" title="Introduction">
</head>
@@ -31,7 +31,7 @@
<div><p class="copyright">Copyright © 2002-2005 Joel
de Guzman, Dan Marsden</p></div>
<div><div class="legalnotice">
-<a name="id759708"></a><p>
+<a name="id787948"></a><p>
Distributed under the Boost Software License, Version 1.0. (See accompanying
file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)
</p>
@@ -111,7 +111,7 @@
<span class="inlinemediaobject"><img src="images/lambda_cpp.png" alt="lambda_cpp"></span>
</p>
<a name="phoenix.preface.description"></a><h3>
-<a name="id759789"></a>
+<a name="id788021"></a>
<a class="link" href="index.html#phoenix.preface.description">Description</a>
</h3>
<p>
@@ -131,7 +131,7 @@
The library is organized in highly independent modules and layers.
</p>
<a name="phoenix.preface.how_to_use_this_manual"></a><h3>
-<a name="id759849"></a>
+<a name="id788062"></a>
<a class="link" href="index.html#phoenix.preface.how_to_use_this_manual">How to use this manual</a>
</h3>
<p>
@@ -154,7 +154,7 @@
icons precede some text to indicate:
</p>
<div class="table">
-<a name="id759887"></a><p class="title"><b>Table 1.1. Icons</b></p>
+<a name="id788082"></a><p class="title"><b>Table 1.1. Icons</b></p>
<div class="table-contents"><table class="table" summary="Icons">
<colgroup>
<col>
@@ -240,7 +240,7 @@
Repository</a>.
</p>
<a name="phoenix.preface.support"></a><h3>
-<a name="id760065"></a>
+<a name="id788258"></a>
<a class="link" href="index.html#phoenix.preface.support">Support</a>
</h3>
<p>
@@ -254,13 +254,13 @@
The news group mirrors the mailing list. Here is a link to the archives: http://news.gmane.org/gmane.comp.parsers.spirit.general.
</p>
<a name="phoenix.preface._emphasis_role__bold___emphasis____to_my_dear_daughter__phoenix__emphasis___emphasis_"></a><h3>
-<a name="id760124"></a>
+<a name="id788300"></a>
<a class="link" href="index.html#phoenix.preface._emphasis_role__bold___emphasis____to_my_dear_daughter__phoenix__emphasis___emphasis_"><span class="bold"><strong><span class="emphasis"><em>...To my dear daughter, Phoenix</em></span></strong></span></a>
</h3>
</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: July 19, 2010 at 19:06:12 GMT</small></p></td>
+<td align="left"><p><small>Last revised: October 29, 2010 at 15:56:26 GMT</small></p></td>
<td align="right"><div class="copyright-footer"></div></td>
</tr></table>
<hr>
Modified: trunk/libs/spirit/phoenix/doc/html/phoenix/acknowledgement.html
==============================================================================
--- trunk/libs/spirit/phoenix/doc/html/phoenix/acknowledgement.html (original)
+++ trunk/libs/spirit/phoenix/doc/html/phoenix/acknowledgement.html 2010-10-29 11:59:36 EDT (Fri, 29 Oct 2010)
@@ -3,7 +3,7 @@
<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Acknowledgement</title>
<link rel="stylesheet" href="../../../../../../doc/src/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
<link rel="home" href="../index.html" title="Chapter 1. Phoenix 2.0">
<link rel="up" href="../index.html" title="Chapter 1. Phoenix 2.0">
<link rel="prev" href="wrap_up.html" title="Wrap Up">
@@ -51,7 +51,7 @@
Aleksey Gurtovoy, DA MPL MAN!
</li>
<li class="listitem">
- Doug Gregor, always a source of inpiration.
+ Doug Gregor, always a source of inspiration.
</li>
<li class="listitem">
Dan Marsden, did almost all the work in bringing Phoenix-2 out the door.
Modified: trunk/libs/spirit/phoenix/doc/html/phoenix/actors.html
==============================================================================
--- trunk/libs/spirit/phoenix/doc/html/phoenix/actors.html (original)
+++ trunk/libs/spirit/phoenix/doc/html/phoenix/actors.html 2010-10-29 11:59:36 EDT (Fri, 29 Oct 2010)
@@ -3,7 +3,7 @@
<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Actors</title>
<link rel="stylesheet" href="../../../../../../doc/src/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
<link rel="home" href="../index.html" title="Chapter 1. Phoenix 2.0">
<link rel="up" href="../index.html" title="Chapter 1. Phoenix 2.0">
<link rel="prev" href="organization.html" title="Organization">
Modified: trunk/libs/spirit/phoenix/doc/html/phoenix/algorithm.html
==============================================================================
--- trunk/libs/spirit/phoenix/doc/html/phoenix/algorithm.html (original)
+++ trunk/libs/spirit/phoenix/doc/html/phoenix/algorithm.html 2010-10-29 11:59:36 EDT (Fri, 29 Oct 2010)
@@ -3,7 +3,7 @@
<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Algorithm</title>
<link rel="stylesheet" href="../../../../../../doc/src/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
<link rel="home" href="../index.html" title="Chapter 1. Phoenix 2.0">
<link rel="up" href="../index.html" title="Chapter 1. Phoenix 2.0">
<link rel="prev" href="container.html" title="Container">
@@ -80,7 +80,7 @@
</p>
</div>
<div class="table">
-<a name="id786989"></a><p class="title"><b>Table 1.7. Iteration Algorithms</b></p>
+<a name="id820937"></a><p class="title"><b>Table 1.7. Iteration Algorithms</b></p>
<div class="table-contents"><table class="table" summary="Iteration Algorithms">
<colgroup>
<col>
@@ -127,7 +127,7 @@
</table></div>
</div>
<br class="table-break"><div class="table">
-<a name="id787263"></a><p class="title"><b>Table 1.8. Querying Algorithms</b></p>
+<a name="id821180"></a><p class="title"><b>Table 1.8. Querying Algorithms</b></p>
<div class="table-contents"><table class="table" summary="Querying Algorithms">
<colgroup>
<col>
@@ -401,7 +401,7 @@
</table></div>
</div>
<br class="table-break"><div class="table">
-<a name="id789681"></a><p class="title"><b>Table 1.9. Transformation Algorithms</b></p>
+<a name="id823825"></a><p class="title"><b>Table 1.9. Transformation Algorithms</b></p>
<div class="table-contents"><table class="table" summary="Transformation Algorithms">
<colgroup>
<col>
Modified: trunk/libs/spirit/phoenix/doc/html/phoenix/basics.html
==============================================================================
--- trunk/libs/spirit/phoenix/doc/html/phoenix/basics.html (original)
+++ trunk/libs/spirit/phoenix/doc/html/phoenix/basics.html 2010-10-29 11:59:36 EDT (Fri, 29 Oct 2010)
@@ -3,7 +3,7 @@
<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Basics</title>
<link rel="stylesheet" href="../../../../../../doc/src/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
<link rel="home" href="../index.html" title="Chapter 1. Phoenix 2.0">
<link rel="up" href="../index.html" title="Chapter 1. Phoenix 2.0">
<link rel="prev" href="starter_kit.html" title="Starter Kit">
@@ -49,7 +49,7 @@
</p></td></tr>
</table></div>
<a name="phoenix.basics.partial_function_application"></a><h3>
-<a name="id763540"></a>
+<a name="id794071"></a>
<a class="link" href="basics.html#phoenix.basics.partial_function_application">Partial Function
Application</a>
</h3>
@@ -101,7 +101,7 @@
application.
</p>
<a name="phoenix.basics.stl_and_higher_order_functions"></a><h3>
-<a name="id763771"></a>
+<a name="id794262"></a>
<a class="link" href="basics.html#phoenix.basics.stl_and_higher_order_functions">STL and higher
order functions</a>
</h3>
@@ -133,7 +133,7 @@
</p></td></tr>
</table></div>
<a name="phoenix.basics.lazy_evaluation"></a><h3>
-<a name="id763976"></a>
+<a name="id794442"></a>
<a class="link" href="basics.html#phoenix.basics.lazy_evaluation">Lazy Evaluation</a>
</h3>
<p>
@@ -188,7 +188,7 @@
</span><span class="identifier">cout</span> <span class="special"><<</span> <span class="special">(</span><span class="identifier">arg1</span> <span class="special">%</span> <span class="number">2</span> <span class="special">==</span> <span class="number">1</span><span class="special">)(</span><span class="identifier">y</span><span class="special">)</span> <span class="special"><<</span> <span class="identifier">endl</span><span class="special">;</span> <span class="comment">// prints 0 or false
</span></pre>
<a name="phoenix.basics.forwarding_function_problem"></a><h3>
-<a name="id764488"></a>
+<a name="id795446"></a>
<a class="link" href="basics.html#phoenix.basics.forwarding_function_problem">Forwarding Function
Problem</a>
</h3>
@@ -218,7 +218,7 @@
Function Problem</a>" but prohibits code like above.
</p>
<a name="phoenix.basics.polymorphic_functions"></a><h3>
-<a name="id764657"></a>
+<a name="id795586"></a>
<a class="link" href="basics.html#phoenix.basics.polymorphic_functions">Polymorphic Functions</a>
</h3>
<p>
Modified: trunk/libs/spirit/phoenix/doc/html/phoenix/composite.html
==============================================================================
--- trunk/libs/spirit/phoenix/doc/html/phoenix/composite.html (original)
+++ trunk/libs/spirit/phoenix/doc/html/phoenix/composite.html 2010-10-29 11:59:36 EDT (Fri, 29 Oct 2010)
@@ -3,7 +3,7 @@
<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Composite</title>
<link rel="stylesheet" href="../../../../../../doc/src/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
<link rel="home" href="../index.html" title="Chapter 1. Phoenix 2.0">
<link rel="up" href="../index.html" title="Chapter 1. Phoenix 2.0">
<link rel="prev" href="primitives.html" title="Primitives">
@@ -227,11 +227,11 @@
operands is an actor object (see <a class="link" href="actors.html" title="Actors">actors</a>).
</li>
<li class="listitem">
- Unary operators are lazily evaluted if their argument is an actor object.
+ Unary operators are lazily evaluated if their argument is an actor object.
</li>
<li class="listitem">
Operator <code class="computeroutput"><span class="special">->*</span></code> is lazily
- evaluted if the left hand argument is an actor object.
+ evaluated if the left hand argument is an actor object.
</li>
<li class="listitem">
The result of a lazy operator is an actor object that can in turn allow
@@ -283,19 +283,19 @@
</span><span class="identifier">val</span><span class="special">(</span><span class="number">1</span><span class="special">)</span> <span class="special"><<</span> <span class="number">3</span><span class="special">;</span> <span class="comment">// Lazily evaluated
</span></pre>
<a name="phoenix.composite.operator.supported_operators"></a><h3>
-<a name="id771576"></a>
+<a name="id802994"></a>
<a class="link" href="composite.html#phoenix.composite.operator.supported_operators">Supported
operators</a>
</h3>
<a name="phoenix.composite.operator.unary_operators"></a><h4>
-<a name="id771597"></a>
+<a name="id803007"></a>
<a class="link" href="composite.html#phoenix.composite.operator.unary_operators">Unary operators</a>
</h4>
<pre class="programlisting"><span class="identifier">prefix</span><span class="special">:</span> <span class="special">~,</span> <span class="special">!,</span> <span class="special">-,</span> <span class="special">+,</span> <span class="special">++,</span> <span class="special">--,</span> <span class="special">&</span> <span class="special">(</span><span class="identifier">reference</span><span class="special">),</span> <span class="special">*</span> <span class="special">(</span><span class="identifier">dereference</span><span class="special">)</span>
<span class="identifier">postfix</span><span class="special">:</span> <span class="special">++,</span> <span class="special">--</span>
</pre>
<a name="phoenix.composite.operator.binary_operators"></a><h4>
-<a name="id771727"></a>
+<a name="id803113"></a>
<a class="link" href="composite.html#phoenix.composite.operator.binary_operators">Binary operators</a>
</h4>
<pre class="programlisting"><span class="special">=,</span> <span class="special">[],</span> <span class="special">+=,</span> <span class="special">-=,</span> <span class="special">*=,</span> <span class="special">/=,</span> <span class="special">%=,</span> <span class="special">&=,</span> <span class="special">|=,</span> <span class="special">^=,</span> <span class="special"><<=,</span> <span class="special">>>=</span>
@@ -304,7 +304,7 @@
<span class="special">&&,</span> <span class="special">||,</span> <span class="special">->*</span>
</pre>
<a name="phoenix.composite.operator.ternary_operator"></a><h4>
-<a name="id771926"></a>
+<a name="id803278"></a>
<a class="link" href="composite.html#phoenix.composite.operator.ternary_operator">Ternary operator</a>
</h4>
<pre class="programlisting"><span class="identifier">if_else</span><span class="special">(</span><span class="identifier">c</span><span class="special">,</span> <span class="identifier">a</span><span class="special">,</span> <span class="identifier">b</span><span class="special">)</span>
@@ -317,7 +317,7 @@
albeit in a lazy manner.
</p>
<a name="phoenix.composite.operator.member_pointer_operator"></a><h4>
-<a name="id772030"></a>
+<a name="id804450"></a>
<a class="link" href="composite.html#phoenix.composite.operator.member_pointer_operator">Member
pointer operator</a>
</h4>
@@ -358,7 +358,7 @@
<span class="special">(</span><span class="identifier">arg1</span><span class="special">->*&</span><span class="identifier">A</span><span class="special">::</span><span class="identifier">func</span><span class="special">)(</span><span class="identifier">arg2</span><span class="special">)(</span><span class="identifier">a</span><span class="special">,</span> <span class="identifier">i</span><span class="special">);</span> <span class="comment">// returns a->func(i)
</span></pre>
<div class="table">
-<a name="id772403"></a><p class="title"><b>Table 1.4. Include Files</b></p>
+<a name="id804758"></a><p class="title"><b>Table 1.4. Include Files</b></p>
<div class="table-contents"><table class="table" summary="Include Files">
<colgroup>
<col>
@@ -941,7 +941,7 @@
<code class="computeroutput"><span class="keyword">dynamic_cast</span></code>, <code class="computeroutput"><span class="keyword">const_cast</span></code> and <code class="computeroutput"><span class="keyword">reinterpret_cast</span></code>.
</p>
<a name="phoenix.composite.object.construction"></a><h3>
-<a name="id777481"></a>
+<a name="id810520"></a>
<a class="link" href="composite.html#phoenix.composite.object.construction">Construction</a>
</h3>
<p>
@@ -955,7 +955,7 @@
<pre class="programlisting"><span class="identifier">construct</span><span class="special"><</span><span class="identifier">T</span><span class="special">>(</span><span class="identifier">ctor_arg1</span><span class="special">,</span> <span class="identifier">ctor_arg2</span><span class="special">,</span> <span class="special">...,</span> <span class="identifier">ctor_argN</span><span class="special">);</span>
</pre>
<p>
- where the given parameters are the parameters to the contructor of the object
+ where the given parameters are the parameters to the constructor of the object
of type T (This implies, that type T is expected to have a constructor with
a corresponding set of parameter types.).
</p>
@@ -982,7 +982,7 @@
</p></td></tr>
</table></div>
<a name="phoenix.composite.object.new"></a><h3>
-<a name="id777797"></a>
+<a name="id810766"></a>
<a class="link" href="composite.html#phoenix.composite.object.new">New</a>
</h3>
<p>
@@ -996,7 +996,7 @@
<pre class="programlisting"><span class="identifier">new_</span><span class="special"><</span><span class="identifier">T</span><span class="special">>(</span><span class="identifier">ctor_arg1</span><span class="special">,</span> <span class="identifier">ctor_arg2</span><span class="special">,</span> <span class="special">...,</span> <span class="identifier">ctor_argN</span><span class="special">);</span>
</pre>
<p>
- where the given parameters are the parameters to the contructor of the object
+ where the given parameters are the parameters to the constructor of the object
of type T (This implies, that type T is expected to have a constructor with
a corresponding set of parameter types.).
</p>
@@ -1020,7 +1020,7 @@
</p></td></tr>
</table></div>
<a name="phoenix.composite.object.delete"></a><h3>
-<a name="id778089"></a>
+<a name="id810998"></a>
<a class="link" href="composite.html#phoenix.composite.object.delete">Delete</a>
</h3>
<p>
@@ -1042,7 +1042,7 @@
<pre class="programlisting"><span class="identifier">delete_</span><span class="special"><</span><span class="identifier">std</span><span class="special">::</span><span class="identifier">string</span><span class="special">>(</span><span class="identifier">arg1</span><span class="special">)</span> <span class="comment">// note the spelling of delete_ (with trailing underscore)
</span></pre>
<a name="phoenix.composite.object.casts"></a><h3>
-<a name="id778280"></a>
+<a name="id811153"></a>
<a class="link" href="composite.html#phoenix.composite.object.casts">Casts</a>
</h3>
<p>
@@ -1097,7 +1097,7 @@
This section deals with local variables and nested lambda scopes.
</p>
<a name="phoenix.composite.scope.local_variables"></a><h3>
-<a name="id778838"></a>
+<a name="id811596"></a>
<a class="link" href="composite.html#phoenix.composite.scope.local_variables">Local Variables</a>
</h3>
<pre class="programlisting"><span class="preprocessor">#include</span> <span class="special"><</span><span class="identifier">boost</span><span class="special">/</span><span class="identifier">spirit</span><span class="special">/</span><span class="identifier">home</span><span class="special">/</span><span class="identifier">phoenix</span><span class="special">/</span><span class="identifier">scope</span><span class="special">/</span><span class="identifier">local_variable</span><span class="special">.</span><span class="identifier">hpp</span><span class="special">></span>
@@ -1116,7 +1116,7 @@
<span class="identifier">actor</span><span class="special"><</span><span class="identifier">local_variable</span><span class="special"><</span><span class="identifier">size_key</span><span class="special">></span> <span class="special">></span> <span class="identifier">size</span><span class="special">;</span>
</pre>
<a name="phoenix.composite.scope.predefined_local_variables"></a><h3>
-<a name="id779063"></a>
+<a name="id811771"></a>
<a class="link" href="composite.html#phoenix.composite.scope.predefined_local_variables">Predefined
Local Variables</a>
</h3>
@@ -1128,7 +1128,7 @@
<pre class="programlisting"><span class="keyword">using</span> <span class="keyword">namespace</span> <span class="identifier">boost</span><span class="special">::</span><span class="identifier">phoenix</span><span class="special">::</span><span class="identifier">local_names</span><span class="special">;</span>
</pre>
<a name="phoenix.composite.scope.let"></a><h3>
-<a name="id779228"></a>
+<a name="id811894"></a>
<a class="link" href="composite.html#phoenix.composite.scope.let">let</a>
</h3>
<pre class="programlisting"><span class="preprocessor">#include</span> <span class="special"><</span><span class="identifier">boost</span><span class="special">/</span><span class="identifier">spirit</span><span class="special">/</span><span class="identifier">home</span><span class="special">/</span><span class="identifier">phoenix</span><span class="special">/</span><span class="identifier">scope</span><span class="special">/</span><span class="identifier">let</span><span class="special">.</span><span class="identifier">hpp</span><span class="special">></span>
@@ -1169,7 +1169,7 @@
<span class="special">]</span>
</pre>
<a name="phoenix.composite.scope.reference_preservation"></a><h3>
-<a name="id779579"></a>
+<a name="id812179"></a>
<a class="link" href="composite.html#phoenix.composite.scope.reference_preservation">Reference
Preservation</a>
</h3>
@@ -1221,7 +1221,7 @@
and <code class="computeroutput"><span class="identifier">ref</span></code>s are L-values. <code class="computeroutput"><span class="identifier">val</span></code>s are R-values.
</p>
<a name="phoenix.composite.scope.visibility"></a><h3>
-<a name="id780063"></a>
+<a name="id814217"></a>
<a class="link" href="composite.html#phoenix.composite.scope.visibility">Visibility</a>
</h3>
<p>
@@ -1271,7 +1271,7 @@
<span class="special">]</span>
</pre>
<a name="phoenix.composite.scope.lambda"></a><h3>
-<a name="id780472"></a>
+<a name="id814556"></a>
<a class="link" href="composite.html#phoenix.composite.scope.lambda">lambda</a>
</h3>
<pre class="programlisting"><span class="preprocessor">#include</span> <span class="special"><</span><span class="identifier">boost</span><span class="special">/</span><span class="identifier">spirit</span><span class="special">/</span><span class="identifier">home</span><span class="special">/</span><span class="identifier">phoenix</span><span class="special">/</span><span class="identifier">scope</span><span class="special">/</span><span class="identifier">lambda</span><span class="special">.</span><span class="identifier">hpp</span><span class="special">></span>
@@ -1434,7 +1434,7 @@
<span class="emphasis"><em>Binding</em></span> is the act of tying together a function to some
arguments for deferred (lazy) evaluation. Named <a class="link" href="composite.html#phoenix.composite.function" title="Function">Lazy
functions</a> require a bit of typing. Unlike (unnamed) lambda expressions,
- we need to write a functor somewhere offline, detached from the call site.
+ we need to write a functor somewhere off-line, detached from the call site.
If you wish to transform a plain function, member function or member variable
to a lambda expression, <code class="computeroutput"><span class="identifier">bind</span></code>
is your friend.
@@ -1447,7 +1447,7 @@
<tr><td align="left" valign="top"><p>
Take note that binders are monomorphic. Rather than binding functions,
the preferred way is to write true generic and polymorphic <a class="link" href="composite.html#phoenix.composite.function" title="Function">lazy-functions</a>.
- However, since most of the time we are dealing with adaptation of exisiting
+ However, since most of the time we are dealing with adaptation of existing
code, binders get the job done faster.
</p></td></tr>
</table></div>
@@ -1457,7 +1457,7 @@
function generates a suitable binder object, a <a class="link" href="composite.html" title="Composite">composite</a>.
</p>
<a name="phoenix.composite.bind.binding_functions"></a><h3>
-<a name="id782121"></a>
+<a name="id815865"></a>
<a class="link" href="composite.html#phoenix.composite.bind.binding_functions">Binding Functions</a>
</h3>
<pre class="programlisting"><span class="preprocessor">#include</span> <span class="special"><</span><span class="identifier">boost</span><span class="special">/</span><span class="identifier">spirit</span><span class="special">/</span><span class="identifier">home</span><span class="special">/</span><span class="identifier">phoenix</span><span class="special">/</span><span class="identifier">bind</span><span class="special">/</span><span class="identifier">bind_function</span><span class="special">.</span><span class="identifier">hpp</span><span class="special">></span>
@@ -1489,7 +1489,7 @@
will print out "4".
</p>
<a name="phoenix.composite.bind.binding_member_functions"></a><h3>
-<a name="id782474"></a>
+<a name="id816148"></a>
<a class="link" href="composite.html#phoenix.composite.bind.binding_member_functions">Binding Member
Functions</a>
</h3>
@@ -1522,7 +1522,7 @@
</span><span class="identifier">bind</span><span class="special">(&</span><span class="identifier">xyz</span><span class="special">::</span><span class="identifier">foo</span><span class="special">,</span> <span class="identifier">obj</span><span class="special">,</span> <span class="number">100</span><span class="special">)</span> <span class="comment">// obj.foo(100)
</span></pre>
<a name="phoenix.composite.bind.binding_member_variables"></a><h3>
-<a name="id782905"></a>
+<a name="id816495"></a>
<a class="link" href="composite.html#phoenix.composite.bind.binding_member_variables">Binding Member
Variables</a>
</h3>
Modified: trunk/libs/spirit/phoenix/doc/html/phoenix/container.html
==============================================================================
--- trunk/libs/spirit/phoenix/doc/html/phoenix/container.html (original)
+++ trunk/libs/spirit/phoenix/doc/html/phoenix/container.html 2010-10-29 11:59:36 EDT (Fri, 29 Oct 2010)
@@ -3,7 +3,7 @@
<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Container</title>
<link rel="stylesheet" href="../../../../../../doc/src/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
<link rel="home" href="../index.html" title="Chapter 1. Phoenix 2.0">
<link rel="up" href="../index.html" title="Chapter 1. Phoenix 2.0">
<link rel="prev" href="composite.html" title="Composite">
@@ -143,7 +143,7 @@
does not use the member "dot" syntax.
</p>
<div class="table">
-<a name="id783648"></a><p class="title"><b>Table 1.5. Sample usage</b></p>
+<a name="id817133"></a><p class="title"><b>Table 1.5. Sample usage</b></p>
<div class="table-contents"><table class="table" summary="Sample usage">
<colgroup>
<col>
@@ -221,7 +221,7 @@
</p>
</div>
<div class="table">
-<a name="id783986"></a><p class="title"><b>Table 1.6. Lazy STL Container Functions</b></p>
+<a name="id817425"></a><p class="title"><b>Table 1.6. Lazy STL Container Functions</b></p>
<div class="table-contents"><table class="table" summary="Lazy STL Container Functions">
<colgroup>
<col>
Modified: trunk/libs/spirit/phoenix/doc/html/phoenix/inside_phoenix.html
==============================================================================
--- trunk/libs/spirit/phoenix/doc/html/phoenix/inside_phoenix.html (original)
+++ trunk/libs/spirit/phoenix/doc/html/phoenix/inside_phoenix.html 2010-10-29 11:59:36 EDT (Fri, 29 Oct 2010)
@@ -3,7 +3,7 @@
<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Inside Phoenix</title>
<link rel="stylesheet" href="../../../../../../doc/src/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
<link rel="home" href="../index.html" title="Chapter 1. Phoenix 2.0">
<link rel="up" href="../index.html" title="Chapter 1. Phoenix 2.0">
<link rel="prev" href="algorithm.html" title="Algorithm">
@@ -45,7 +45,7 @@
<a name="phoenix.inside_phoenix.actors_in_detail"></a><a class="link" href="inside_phoenix.html#phoenix.inside_phoenix.actors_in_detail" title="Actors In Detail">Actors In Detail</a>
</h3></div></div></div>
<a name="phoenix.inside_phoenix.actors_in_detail.actor_concept"></a><h4>
-<a name="id795342"></a>
+<a name="id829814"></a>
<a class="link" href="inside_phoenix.html#phoenix.inside_phoenix.actors_in_detail.actor_concept">Actor
Concept</a>
</h4>
@@ -65,7 +65,7 @@
</p></td></tr>
</table></div>
<a name="phoenix.inside_phoenix.actors_in_detail.actor_template_class"></a><h4>
-<a name="id795408"></a>
+<a name="id829862"></a>
<a class="link" href="inside_phoenix.html#phoenix.inside_phoenix.actors_in_detail.actor_template_class">actor
template class</a>
</h4>
@@ -104,7 +104,7 @@
</span><span class="special">};</span>
</pre>
<div class="table">
-<a name="id796097"></a><p class="title"><b>Table 1.10. Actor Concept Requirements</b></p>
+<a name="id830992"></a><p class="title"><b>Table 1.10. Actor Concept Requirements</b></p>
<div class="table-contents"><table class="table" summary="Actor Concept Requirements">
<colgroup>
<col>
@@ -191,7 +191,7 @@
</table></div>
</div>
<br class="table-break"><a name="phoenix.inside_phoenix.actors_in_detail.eval_concept"></a><h4>
-<a name="id796380"></a>
+<a name="id831251"></a>
<a class="link" href="inside_phoenix.html#phoenix.inside_phoenix.actors_in_detail.eval_concept">Eval
Concept</a>
</h4>
@@ -205,7 +205,7 @@
<a class="link" href="inside_phoenix.html#phoenix.inside_phoenix.actor_example" title="Actor Example">next section</a>.
</p>
<div class="table">
-<a name="id796466"></a><p class="title"><b>Table 1.11. Eval Concept Requirements</b></p>
+<a name="id831306"></a><p class="title"><b>Table 1.11. Eval Concept Requirements</b></p>
<div class="table-contents"><table class="table" summary="Eval Concept Requirements">
<colgroup>
<col>
@@ -252,7 +252,7 @@
</table></div>
</div>
<br class="table-break"><a name="phoenix.inside_phoenix.actors_in_detail.constructors"></a><h4>
-<a name="id796619"></a>
+<a name="id831443"></a>
<a class="link" href="inside_phoenix.html#phoenix.inside_phoenix.actors_in_detail.constructors">Constructors</a>
</h4>
<p>
@@ -283,7 +283,7 @@
</td></tr>
</table></div>
<a name="phoenix.inside_phoenix.actors_in_detail.function_call_operators"></a><h4>
-<a name="id796684"></a>
+<a name="id831492"></a>
<a class="link" href="inside_phoenix.html#phoenix.inside_phoenix.actors_in_detail.function_call_operators">Function
Call Operators</a>
</h4>
@@ -313,7 +313,7 @@
</td></tr>
</table></div>
<a name="phoenix.inside_phoenix.actors_in_detail.environment"></a><h4>
-<a name="id796836"></a>
+<a name="id831604"></a>
<a class="link" href="inside_phoenix.html#phoenix.inside_phoenix.actors_in_detail.environment">Environment</a>
</h4>
<p>
@@ -324,7 +324,7 @@
class is a model of.
</p>
<div class="table">
-<a name="id796904"></a><p class="title"><b>Table 1.12. Environment Concept Requirements</b></p>
+<a name="id831653"></a><p class="title"><b>Table 1.12. Environment Concept Requirements</b></p>
<div class="table-contents"><table class="table" summary="Environment Concept Requirements">
<colgroup>
<col>
@@ -393,7 +393,7 @@
such as local variables, etc.
</p>
<a name="phoenix.inside_phoenix.actors_in_detail.apply_actor"></a><h4>
-<a name="id797100"></a>
+<a name="id831828"></a>
<a class="link" href="inside_phoenix.html#phoenix.inside_phoenix.actors_in_detail.apply_actor">apply_actor</a>
</h4>
<p>
@@ -434,7 +434,7 @@
<span class="special">}</span>
</pre>
<a name="phoenix.inside_phoenix.actors_in_detail.actor_result"></a><h4>
-<a name="id797697"></a>
+<a name="id832301"></a>
<a class="link" href="inside_phoenix.html#phoenix.inside_phoenix.actors_in_detail.actor_result">actor_result</a>
</h4>
<p>
@@ -502,7 +502,7 @@
The <code class="computeroutput"><span class="identifier">reference</span></code> template class
conforms to the <a class="link" href="inside_phoenix.html#phoenix.inside_phoenix.actors_in_detail.eval_concept"><code class="computeroutput"><span class="identifier">Eval</span></code></a> concept. It has a nested <code class="computeroutput"><span class="identifier">result</span></code> metafunction that reflects the return
type of its <code class="computeroutput"><span class="identifier">eval</span></code> member function,
- which peforms the actual function. <code class="computeroutput"><span class="identifier">reference</span><span class="special"><</span><span class="identifier">T</span><span class="special">></span></code>
+ which performs the actual function. <code class="computeroutput"><span class="identifier">reference</span><span class="special"><</span><span class="identifier">T</span><span class="special">></span></code>
stores a reference to a <code class="computeroutput"><span class="identifier">T</span></code>.
Its <code class="computeroutput"><span class="identifier">eval</span></code> member function
simply returns the reference. It does not make use of the environment <code class="computeroutput"><span class="identifier">Env</span></code>.
@@ -556,7 +556,7 @@
</p></td></tr>
</table></div>
<a name="phoenix.inside_phoenix.composites_in_detail.composite_template_class"></a><h3>
-<a name="id798837"></a>
+<a name="id834344"></a>
<a class="link" href="inside_phoenix.html#phoenix.inside_phoenix.composites_in_detail.composite_template_class">composite
template class</a>
</h3>
@@ -589,7 +589,7 @@
<span class="special">};</span>
</pre>
<a name="phoenix.inside_phoenix.composites_in_detail.evaltuple"></a><h3>
-<a name="id799366"></a>
+<a name="id834787"></a>
<a class="link" href="inside_phoenix.html#phoenix.inside_phoenix.composites_in_detail.evaltuple">EvalTuple</a>
</h3>
<p>
@@ -601,7 +601,7 @@
base class.
</p>
<a name="phoenix.inside_phoenix.composites_in_detail.evalpolicy"></a><h3>
-<a name="id799463"></a>
+<a name="id834849"></a>
<a class="link" href="inside_phoenix.html#phoenix.inside_phoenix.composites_in_detail.evalpolicy">EvalPolicy</a>
</h3>
<p>
@@ -616,7 +616,7 @@
<span class="inlinemediaobject"><img src="../images/funnel_out.png" alt="funnel_out"></span>
</p>
<div class="table">
-<a name="id799542"></a><p class="title"><b>Table 1.13. EvalPolicy Requirements</b></p>
+<a name="id834907"></a><p class="title"><b>Table 1.13. EvalPolicy Requirements</b></p>
<div class="table-contents"><table class="table" summary="EvalPolicy Requirements">
<colgroup>
<col>
@@ -703,7 +703,7 @@
<p>
Composites are never instantiated directly. Front end expression templates
are used to generate the composites. Using expression templates, we implement
- a DSEL (Domain Specific Embedded Language) that mimicks native C++. You've
+ a DSEL (Domain Specific Embedded Language) that mimics native C++. You've
seen this DSEL in action in the preceding sections. It is most evident in
the <a class="link" href="composite.html#phoenix.composite.statement" title="Statement">Statement</a> section.
</p>
Modified: trunk/libs/spirit/phoenix/doc/html/phoenix/introduction.html
==============================================================================
--- trunk/libs/spirit/phoenix/doc/html/phoenix/introduction.html (original)
+++ trunk/libs/spirit/phoenix/doc/html/phoenix/introduction.html 2010-10-29 11:59:36 EDT (Fri, 29 Oct 2010)
@@ -3,7 +3,7 @@
<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Introduction</title>
<link rel="stylesheet" href="../../../../../../doc/src/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
<link rel="home" href="../index.html" title="Chapter 1. Phoenix 2.0">
<link rel="up" href="../index.html" title="Chapter 1. Phoenix 2.0">
<link rel="prev" href="../index.html" title="Chapter 1. Phoenix 2.0">
@@ -41,7 +41,7 @@
FP as a programming discipline can, in fact, be applied to many programming
languages. In the realm of C++ for instance, we are seeing more FP techniques
being applied. C++ is sufficiently rich to support at least some of the most
- important facets of FP. C++ is a multiparadigm programming language. It is
+ important facets of FP. C++ is a multi-paradigm programming language. It is
not only procedural. It is not only object oriented. Beneath the core of the
standard C++ library, a closer look into STL gives us a glimpse of FP already
in place. It is obvious that the authors of STL know and practice FP. In the
Modified: trunk/libs/spirit/phoenix/doc/html/phoenix/organization.html
==============================================================================
--- trunk/libs/spirit/phoenix/doc/html/phoenix/organization.html (original)
+++ trunk/libs/spirit/phoenix/doc/html/phoenix/organization.html 2010-10-29 11:59:36 EDT (Fri, 29 Oct 2010)
@@ -3,7 +3,7 @@
<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Organization</title>
<link rel="stylesheet" href="../../../../../../doc/src/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
<link rel="home" href="../index.html" title="Chapter 1. Phoenix 2.0">
<link rel="up" href="../index.html" title="Chapter 1. Phoenix 2.0">
<link rel="prev" href="basics.html" title="Basics">
@@ -41,14 +41,14 @@
depend on higher layers. Modules in a layer do not depend on other modules
in the same layer. This means, for example, that Bind can be completely discarded
if it is not required; or one could perhaps take out Operator and Statement
- and just use Function, which may be desireable in a pure FP application.
+ and just use Function, which may be desirable in a pure FP application.
</p>
<p>
The library has grown from the original Phoenix but still comprises only header
files. There are no object files to link against.
</p>
<a name="phoenix.organization.core"></a><h3>
-<a name="id765034"></a>
+<a name="id795919"></a>
<a class="link" href="organization.html#phoenix.organization.core">Core</a>
</h3>
<p>
@@ -77,7 +77,7 @@
again be another composite.
</p>
<div class="table">
-<a name="id765093"></a><p class="title"><b>Table 1.2. Modules</b></p>
+<a name="id795970"></a><p class="title"><b>Table 1.2. Modules</b></p>
<div class="table-contents"><table class="table" summary="Modules">
<colgroup>
<col>
@@ -205,7 +205,7 @@
core module is defined in <code class="computeroutput"><span class="special"><</span><span class="identifier">boost</span><span class="special">/</span><span class="identifier">spirit</span><span class="special">/</span><span class="identifier">home</span><span class="special">/</span><span class="identifier">phoenix</span><span class="special">/</span><span class="identifier">core</span><span class="special">.</span><span class="identifier">hpp</span><span class="special">></span></code>.
</p>
<div class="table">
-<a name="id765410"></a><p class="title"><b>Table 1.3. Includes</b></p>
+<a name="id796271"></a><p class="title"><b>Table 1.3. Includes</b></p>
<div class="table-contents"><table class="table" summary="Includes">
<colgroup>
<col>
Modified: trunk/libs/spirit/phoenix/doc/html/phoenix/primitives.html
==============================================================================
--- trunk/libs/spirit/phoenix/doc/html/phoenix/primitives.html (original)
+++ trunk/libs/spirit/phoenix/doc/html/phoenix/primitives.html 2010-10-29 11:59:36 EDT (Fri, 29 Oct 2010)
@@ -3,7 +3,7 @@
<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Primitives</title>
<link rel="stylesheet" href="../../../../../../doc/src/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
<link rel="home" href="../index.html" title="Chapter 1. Phoenix 2.0">
<link rel="up" href="../index.html" title="Chapter 1. Phoenix 2.0">
<link rel="prev" href="actors.html" title="Actors">
@@ -55,7 +55,7 @@
an imaginary data-bin where a function argument will be placed.
</p>
<a name="phoenix.primitives.arguments.predefined_arguments"></a><h3>
-<a name="id766693"></a>
+<a name="id799096"></a>
<a class="link" href="primitives.html#phoenix.primitives.arguments.predefined_arguments">Predefined
Arguments</a>
</h3>
@@ -93,7 +93,7 @@
</p></td></tr>
</table></div>
<a name="phoenix.primitives.arguments.user_defined_arguments"></a><h3>
-<a name="id767253"></a>
+<a name="id799604"></a>
<a class="link" href="primitives.html#phoenix.primitives.arguments.user_defined_arguments">User
Defined Arguments</a>
</h3>
@@ -115,7 +115,7 @@
<pre class="programlisting"><span class="identifier">add</span><span class="special">(</span><span class="identifier">arg1</span><span class="special">,</span> <span class="number">6</span><span class="special">)</span>
</pre>
<a name="phoenix.primitives.arguments.evaluating_an_argument"></a><h3>
-<a name="id767420"></a>
+<a name="id799751"></a>
<a class="link" href="primitives.html#phoenix.primitives.arguments.evaluating_an_argument">Evaluating
an Argument</a>
</h3>
@@ -142,7 +142,7 @@
<span class="identifier">Hello</span> <span class="identifier">World</span>
</pre>
<a name="phoenix.primitives.arguments.extra_arguments"></a><h3>
-<a name="id767715"></a>
+<a name="id800021"></a>
<a class="link" href="primitives.html#phoenix.primitives.arguments.extra_arguments">Extra Arguments</a>
</h3>
<p>
@@ -180,7 +180,7 @@
<th align="left">Note</th>
</tr>
<tr><td align="left" valign="top"><p>
- There are a few reasons why enforcing strict arity is not desireable. A
+ There are a few reasons why enforcing strict arity is not desirable. A
case in point is the callback function. Typical callback functions provide
more information than is actually needed. Lambda functions are often used
as callbacks.
@@ -219,7 +219,7 @@
but, as we'll see later on, there are situations where this is unavoidable.
</p>
<a name="phoenix.primitives.values.evaluating_a_value"></a><h3>
-<a name="id768309"></a>
+<a name="id800546"></a>
<a class="link" href="primitives.html#phoenix.primitives.values.evaluating_a_value">Evaluating a
Value</a>
</h3>
@@ -275,13 +275,13 @@
<pre class="programlisting"><span class="identifier">add_assign</span><span class="special">(</span><span class="identifier">ref</span><span class="special">(</span><span class="identifier">i</span><span class="special">),</span> <span class="number">2</span><span class="special">)</span>
</pre>
<a name="phoenix.primitives.references.evaluating_a_reference"></a><h3>
-<a name="id769065"></a>
+<a name="id800975"></a>
<a class="link" href="primitives.html#phoenix.primitives.references.evaluating_a_reference">Evaluating
a Reference</a>
</h3>
<p>
References are actors. Hence, references can be evaluated. Such invocation
- gives the references's identity. Example:
+ gives the reference's identity. Example:
</p>
<pre class="programlisting"><span class="keyword">int</span> <span class="identifier">i</span> <span class="special">=</span> <span class="number">3</span><span class="special">;</span>
<span class="keyword">char</span> <span class="keyword">const</span><span class="special">*</span> <span class="identifier">s</span> <span class="special">=</span> <span class="string">"Hello World"</span><span class="special">;</span>
Modified: trunk/libs/spirit/phoenix/doc/html/phoenix/references.html
==============================================================================
--- trunk/libs/spirit/phoenix/doc/html/phoenix/references.html (original)
+++ trunk/libs/spirit/phoenix/doc/html/phoenix/references.html 2010-10-29 11:59:36 EDT (Fri, 29 Oct 2010)
@@ -3,7 +3,7 @@
<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>References</title>
<link rel="stylesheet" href="../../../../../../doc/src/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
<link rel="home" href="../index.html" title="Chapter 1. Phoenix 2.0">
<link rel="up" href="../index.html" title="Chapter 1. Phoenix 2.0">
<link rel="prev" href="acknowledgement.html" title="Acknowledgement">
Modified: trunk/libs/spirit/phoenix/doc/html/phoenix/starter_kit.html
==============================================================================
--- trunk/libs/spirit/phoenix/doc/html/phoenix/starter_kit.html (original)
+++ trunk/libs/spirit/phoenix/doc/html/phoenix/starter_kit.html 2010-10-29 11:59:36 EDT (Fri, 29 Oct 2010)
@@ -3,7 +3,7 @@
<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Starter Kit</title>
<link rel="stylesheet" href="../../../../../../doc/src/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
<link rel="home" href="../index.html" title="Chapter 1. Phoenix 2.0">
<link rel="up" href="../index.html" title="Chapter 1. Phoenix 2.0">
<link rel="prev" href="introduction.html" title="Introduction">
@@ -60,7 +60,7 @@
into high gear quickly.
</p>
<a name="phoenix.starter_kit.functors_everywhere"></a><h3>
-<a name="id760240"></a>
+<a name="id788386"></a>
<a class="link" href="starter_kit.html#phoenix.starter_kit.functors_everywhere">Functors everywhere</a>
</h3>
<p>
@@ -95,7 +95,7 @@
World"</span></code>.
</p>
<a name="phoenix.starter_kit.values.lazy_evaluation"></a><h3>
-<a name="id760388"></a>
+<a name="id788513"></a>
<a class="link" href="starter_kit.html#phoenix.starter_kit.values.lazy_evaluation">Lazy Evaluation</a>
</h3>
<p>
@@ -127,7 +127,7 @@
anything and defers the evaluation for later.
</p>
<a name="phoenix.starter_kit.values.callbacks"></a><h3>
-<a name="id760603"></a>
+<a name="id788702"></a>
<a class="link" href="starter_kit.html#phoenix.starter_kit.values.callbacks">Callbacks</a>
</h3>
<p>
@@ -159,7 +159,7 @@
<a name="phoenix.starter_kit.references"></a><a class="link" href="starter_kit.html#phoenix.starter_kit.references" title="References">References</a>
</h3></div></div></div>
<p>
- References are functions. They hold a reference to a value stored somehere.
+ References are functions. They hold a reference to a value stored somewhere.
For example, given:
</p>
<pre class="programlisting"><span class="keyword">int</span> <span class="identifier">i</span> <span class="special">=</span> <span class="number">3</span><span class="special">;</span>
@@ -295,7 +295,7 @@
</p>
</div>
<a name="phoenix.starter_kit.lazy_operators.first_practical_example"></a><h3>
-<a name="id761945"></a>
+<a name="id792647"></a>
<a class="link" href="starter_kit.html#phoenix.starter_kit.lazy_operators.first_practical_example">First
Practical Example</a>
</h3>
@@ -327,7 +327,7 @@
</pre>
<p>
The expression <code class="computeroutput"><span class="identifier">arg1</span> <span class="special">%</span>
- <span class="number">2</span> <span class="special">==</span> <span class="number">1</span></code> automagically creates a functor with the
+ <span class="number">2</span> <span class="special">==</span> <span class="number">1</span></code> auto-magically creates a functor with the
expected behavior. In FP, this unnamed function is called a lambda function.
Unlike the function pointer version, which is monomorphic (expects and works
only with a fixed type int argument), the Phoenix version is fully polymorphic
@@ -444,7 +444,7 @@
<span class="identifier">function</span><span class="special"><</span><span class="identifier">is_odd_impl</span><span class="special">></span> <span class="identifier">is_odd</span><span class="special">;</span>
</pre>
<a name="phoenix.starter_kit.lazy_functions.things_to_note_"></a><h3>
-<a name="id763023"></a>
+<a name="id793613"></a>
<a class="link" href="starter_kit.html#phoenix.starter_kit.lazy_functions.things_to_note_">Things
to note:</a>
</h3>
@@ -478,7 +478,7 @@
(See function.cpp)
</p>
<a name="phoenix.starter_kit.lazy_functions.predefined_lazy_functions"></a><h3>
-<a name="id763234"></a>
+<a name="id793802"></a>
<a class="link" href="starter_kit.html#phoenix.starter_kit.lazy_functions.predefined_lazy_functions">Predefined
Lazy Functions</a>
</h3>
Modified: trunk/libs/spirit/phoenix/doc/html/phoenix/wrap_up.html
==============================================================================
--- trunk/libs/spirit/phoenix/doc/html/phoenix/wrap_up.html (original)
+++ trunk/libs/spirit/phoenix/doc/html/phoenix/wrap_up.html 2010-10-29 11:59:36 EDT (Fri, 29 Oct 2010)
@@ -3,7 +3,7 @@
<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Wrap Up</title>
<link rel="stylesheet" href="../../../../../../doc/src/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
<link rel="home" href="../index.html" title="Chapter 1. Phoenix 2.0">
<link rel="up" href="../index.html" title="Chapter 1. Phoenix 2.0">
<link rel="prev" href="inside_phoenix.html" title="Inside Phoenix">
@@ -28,12 +28,12 @@
</h2></div></div></div>
<p>
Sooner or later more FP techniques become standard practice as people find
- the true value of this programming discipline outside the academe and into
+ the true value of this programming discipline outside the academy and into
the mainstream. In as much as structured programming of the 70s and object
oriented programming in the 80s and generic programming in the 90s shaped our
thoughts towards a more robust sense of software engineering, FP will certainly
be a paradigm that will catapult us towards more powerful software design and
- engineering onward into the new millenium.
+ engineering onward into the new millennium.
</p>
<p>
Let me quote Doug Gregor of Boost.org. About functional style programming libraries:
Modified: trunk/libs/spirit/phoenix/doc/users_manual.qbk
==============================================================================
--- trunk/libs/spirit/phoenix/doc/users_manual.qbk (original)
+++ trunk/libs/spirit/phoenix/doc/users_manual.qbk 2010-10-29 11:59:36 EDT (Fri, 29 Oct 2010)
@@ -121,7 +121,7 @@
FP as a programming discipline can, in fact, be applied to many programming
languages. In the realm of C++ for instance, we are seeing more FP techniques
being applied. C++ is sufficiently rich to support at least some of the most
-important facets of FP. C++ is a multiparadigm programming language. It is not
+important facets of FP. C++ is a multi-paradigm programming language. It is not
only procedural. It is not only object oriented. Beneath the core of the
standard C++ library, a closer look into STL gives us a glimpse of FP already in
place. It is obvious that the authors of STL know and practice FP. In the near
@@ -220,7 +220,7 @@
[endsect]
[section References]
-References are functions. They hold a reference to a value stored somehere.
+References are functions. They hold a reference to a value stored somewhere.
For example, given:
int i = 3;
@@ -333,7 +333,7 @@
find_if(c.begin(), c.end(), arg1 % 2 == 1)
-The expression `arg1 % 2 == 1` automagically creates a functor with the expected
+The expression `arg1 % 2 == 1` auto-magically creates a functor with the expected
behavior. In FP, this unnamed function is called a lambda function. Unlike the
function pointer version, which is monomorphic (expects and works only with a
fixed type int argument), the Phoenix version is fully polymorphic and works
@@ -618,7 +618,7 @@
Lower layers do not depend on higher layers. Modules in a layer do not depend on other modules in the same layer.
This means, for example, that Bind can be completely discarded if it is
not required; or one could perhaps take out Operator and Statement and just use Function,
-which may be desireable in a pure FP application.
+which may be desirable in a pure FP application.
The library has grown from the original Phoenix but still comprises only
header files. There are no object files to link against.
@@ -815,7 +815,7 @@
argument (`arg1`) and the fifth argument (`arg5`).
[note There are a few reasons why enforcing strict arity is not
-desireable. A case in point is the callback function. Typical callback functions
+desirable. A case in point is the callback function. Typical callback functions
provide more information than is actually needed. Lambda functions are often
used as callbacks.]
@@ -887,7 +887,7 @@
[h2 Evaluating a Reference]
References are actors. Hence, references can be evaluated. Such invocation gives
-the references's identity. Example:
+the reference's identity. Example:
int i = 3;
char const* s = "Hello World";
@@ -1060,8 +1060,8 @@
# A binary operator, except `->*` will be lazily evaluated when
/at least/ one of its operands is an actor object
(see [link phoenix.actors actors]).
-# Unary operators are lazily evaluted if their argument is an actor object.
-# Operator `->*` is lazily evaluted if the left hand argument is an actor object.
+# Unary operators are lazily evaluated if their argument is an actor object.
+# Operator `->*` is lazily evaluated if the left hand argument is an actor object.
# The result of a lazy operator is an actor object that can in turn allow the
applications of rules 1 and 2.
@@ -1523,7 +1523,7 @@
construct<T>(ctor_arg1, ctor_arg2, ..., ctor_argN);
-where the given parameters are the parameters to the contructor of the object of
+where the given parameters are the parameters to the constructor of the object of
type T (This implies, that type T is expected to have a constructor with a
corresponding set of parameter types.).
@@ -1548,7 +1548,7 @@
new_<T>(ctor_arg1, ctor_arg2, ..., ctor_argN);
-where the given parameters are the parameters to the contructor of the object of
+where the given parameters are the parameters to the constructor of the object of
type T (This implies, that type T is expected to have a constructor with a
corresponding set of parameter types.).
@@ -1882,14 +1882,14 @@
['Binding] is the act of tying together a function to some arguments for
deferred (lazy) evaluation. Named [link phoenix.composite.function Lazy functions]
require a bit of typing. Unlike (unnamed) lambda expressions, we need to write a
-functor somewhere offline, detached from the call site. If you wish to transform a
+functor somewhere off-line, detached from the call site. If you wish to transform a
plain function, member function or member variable to a lambda expression, `bind`
is your friend.
[note Take note that binders are monomorphic. Rather than binding
functions, the preferred way is to write true generic and polymorphic [link
phoenix.composite.function lazy-functions]. However, since most of the time we
-are dealing with adaptation of exisiting code, binders get the job done faster.]
+are dealing with adaptation of existing code, binders get the job done faster.]
There is a set of overloaded `bind` template functions. Each `bind(x)`
function generates a suitable binder object, a [link phoenix.composite
@@ -2430,7 +2430,7 @@
The `reference` template class conforms to the __eval__ concept. It has a nested
`result` metafunction that reflects the return type of its `eval` member
-function, which peforms the actual function. `reference<T>` stores a reference to
+function, which performs the actual function. `reference<T>` stores a reference to
a `T`. Its `eval` member function simply returns the reference. It does not make
use of the environment `Env`.
@@ -2533,7 +2533,7 @@
Composites are never instantiated directly. Front end expression templates are
used to generate the composites. Using expression templates, we implement a DSEL
-(Domain Specific Embedded Language) that mimicks native C++. You've seen this
+(Domain Specific Embedded Language) that mimics native C++. You've seen this
DSEL in action in the preceding sections. It is most evident in the
[link phoenix.composite.statement Statement] section.
@@ -2685,12 +2685,12 @@
[section Wrap Up]
Sooner or later more FP techniques become standard practice as people find the
-true value of this programming discipline outside the academe and into the
+true value of this programming discipline outside the academy and into the
mainstream. In as much as structured programming of the 70s and object oriented
programming in the 80s and generic programming in the 90s shaped our thoughts
towards a more robust sense of software engineering, FP will certainly be a
paradigm that will catapult us towards more powerful software design and
-engineering onward into the new millenium.
+engineering onward into the new millennium.
Let me quote Doug Gregor of Boost.org. About functional style programming
libraries:
@@ -2727,7 +2727,7 @@
# Jaakko Jarvi. DA Lambda MAN!
# Dave Abrahams, for his constant presence, wherever, whenever.
# Aleksey Gurtovoy, DA MPL MAN!
-# Doug Gregor, always a source of inpiration.
+# Doug Gregor, always a source of inspiration.
# Dan Marsden, did almost all the work in bringing Phoenix-2 out the door.
# Eric Niebler did a 2.0 pre-release review and wrote some range related code
that Phoenix stole and used in the algorithms.
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