|
|
Boost-Commit : |
Subject: [Boost-commit] svn:boost r69531 - in sandbox/SOC/2010/phoenix3/libs/phoenix: doc doc/examples doc/html doc/html/phoenix doc/html/phoenix/examples doc/html/phoenix/inside doc/html/phoenix/inside/expression doc/html/phoenix/modules doc/html/phoenix/modules/core doc/html/phoenix/modules/stl doc/html/phoenix/starter_kit doc/inside doc/modules example
From: thom.heller_at_[hidden]
Date: 2011-03-03 15:18:17
Author: theller
Date: 2011-03-03 15:18:12 EST (Thu, 03 Mar 2011)
New Revision: 69531
URL: http://svn.boost.org/trac/boost/changeset/69531
Log:
Changes from mjcaisse's review
Added:
sandbox/SOC/2010/phoenix3/libs/phoenix/example/factorial.cpp (contents, props changed)
Text files modified:
sandbox/SOC/2010/phoenix3/libs/phoenix/doc/actor.qbk | 2 +-
sandbox/SOC/2010/phoenix3/libs/phoenix/doc/examples/adding.qbk | 6 +++---
sandbox/SOC/2010/phoenix3/libs/phoenix/doc/examples/extending_actors.qbk | 2 +-
sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/index.html | 14 +++++++-------
sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/basics.html | 10 +++++-----
sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/examples/adding_an_expression.html | 11 +++++------
sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/examples/extending_actors.html | 10 +++++-----
sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/inside.html | 4 ++--
sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/inside/actions.html | 6 +++---
sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/inside/actor.html | 28 ++++++++++++++--------------
sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/inside/custom_terminals.html | 8 ++++----
sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/inside/expression.html | 20 ++++++++++----------
sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/inside/expression/boost_phoenix_define_expression.html | 10 +++++-----
sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/inside/expression/boost_phoenix_define_expression_ext.html | 10 +++++-----
sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/inside/expression/boost_phoenix_define_expression_ext_vararg.html | 10 +++++-----
sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/inside/expression/boost_phoenix_define_expression_vararg.html | 10 +++++-----
sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/inside/placeholder_unification.html | 2 +-
sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/modules/core/arguments.html | 8 ++++----
sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/modules/core/nothing.html | 2 +-
sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/modules/core/references.html | 8 ++++----
sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/modules/core/values.html | 2 +-
sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/modules/operator.html | 12 ++++++------
sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/modules/stl/algorithm.html | 6 +++---
sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/modules/stl/container.html | 4 ++--
sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/organization.html | 6 +++---
sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/starter_kit.html | 2 +-
sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/starter_kit/lazy_functions.html | 4 ++--
sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/starter_kit/lazy_operators.html | 2 +-
sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/starter_kit/values.html | 4 ++--
sandbox/SOC/2010/phoenix3/libs/phoenix/doc/inside.qbk | 2 +-
sandbox/SOC/2010/phoenix3/libs/phoenix/doc/inside/actions.qbk | 2 +-
sandbox/SOC/2010/phoenix3/libs/phoenix/doc/inside/actor.qbk | 10 +++++-----
sandbox/SOC/2010/phoenix3/libs/phoenix/doc/inside/custom_terminal.qbk | 8 ++++----
sandbox/SOC/2010/phoenix3/libs/phoenix/doc/inside/expression.qbk | 17 ++++++++---------
sandbox/SOC/2010/phoenix3/libs/phoenix/doc/inside/placeholder.qbk | 2 +-
sandbox/SOC/2010/phoenix3/libs/phoenix/doc/modules/core.qbk | 4 ++--
36 files changed, 133 insertions(+), 135 deletions(-)
Modified: sandbox/SOC/2010/phoenix3/libs/phoenix/doc/actor.qbk
==============================================================================
--- sandbox/SOC/2010/phoenix3/libs/phoenix/doc/actor.qbk (original)
+++ sandbox/SOC/2010/phoenix3/libs/phoenix/doc/actor.qbk 2011-03-03 15:18:12 EST (Thu, 03 Mar 2011)
@@ -50,7 +50,7 @@
The actor class accepts the arguments through a set of function call operators
for 0 to `BOOST_PHOENIX_LIMIT` arities (Don't worry about the details, for now. Note, for example,
-that we skimp over the details regarding `return_type`). The arguments
+that we skimed over the details regarding `return_type`). The arguments
are then forwarded to the actor's `Expr` for evaluation.
[endsect]
Modified: sandbox/SOC/2010/phoenix3/libs/phoenix/doc/examples/adding.qbk
==============================================================================
--- sandbox/SOC/2010/phoenix3/libs/phoenix/doc/examples/adding.qbk (original)
+++ sandbox/SOC/2010/phoenix3/libs/phoenix/doc/examples/adding.qbk 2011-03-03 15:18:12 EST (Thu, 03 Mar 2011)
@@ -66,7 +66,7 @@
}}
`while_eval` is an example of how to evaluate an expression. It gets called in
-the `rule::while` action. `while_gen` and `while? are the expression template
+the `rule::while` action. `while_gen` and `while_` are the expression template
front ends. Let's break this apart to undestand what's happening. Let's start at
the bottom. It's easier that way.
@@ -87,8 +87,8 @@
expression::while_<Cond, Do>::type
-where `Cond` is the type of `cond` and `Do` is the type of `do_`. Notice how we are using phoenix's
-[link phoenix.inside.expression Expression) mechanism here
+where `Cond` is the type of `cond` and `Do` is the type of `do_`. Notice how we are using Phoenix's
+[link phoenix.inside.expression Expression] mechanism here
template <typename Do>
typename expression::while_<Cond, Do>::type const
Modified: sandbox/SOC/2010/phoenix3/libs/phoenix/doc/examples/extending_actors.qbk
==============================================================================
--- sandbox/SOC/2010/phoenix3/libs/phoenix/doc/examples/extending_actors.qbk (original)
+++ sandbox/SOC/2010/phoenix3/libs/phoenix/doc/examples/extending_actors.qbk 2011-03-03 15:18:12 EST (Thu, 03 Mar 2011)
@@ -13,7 +13,7 @@
library, and one of the many customization points. The default actor implementation
provides several operator() overloads which deal with the evaluation of expressions.
-For some uses cases this might not be enough. For convenience it is thinkable to
+For some use cases this might not be enough. For convenience it is thinkable to
provide custom member functions which generate new expressions. An example is the
[link phoenix.modules.statement.___if_else_____statement '''if_else_'''
Statement] which provides an additional else member for generating a lazy if-else
Modified: sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/index.html
==============================================================================
--- sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/index.html (original)
+++ sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/index.html 2011-03-03 15:18:12 EST (Thu, 03 Mar 2011)
@@ -26,7 +26,7 @@
</h3></div></div>
<div><p class="copyright">Copyright © 2002-2005, 2010 Joel de Guzman, Dan Marsden, Thomas Heller</p></div>
<div><div class="legalnotice">
-<a name="id674261"></a><p>
+<a name="id626474"></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>
@@ -134,7 +134,7 @@
</dl>
</div>
<a name="phoenix.preface"></a><h2>
-<a name="id704958"></a>
+<a name="id657171"></a>
<a class="link" href="index.html#phoenix.preface">Preface</a>
</h2>
<div class="blockquote"><blockquote class="blockquote"><p>
@@ -153,7 +153,7 @@
<span class="inlinemediaobject"><img src="images/lambda_cpp.png" alt="lambda_cpp"></span>
</p>
<a name="phoenix.description"></a><h3>
-<a name="id673064"></a>
+<a name="id625278"></a>
<a class="link" href="index.html#phoenix.description">Description</a>
</h3>
<p>
@@ -171,7 +171,7 @@
library is organized in highly independent modules and layers.
</p>
<a name="phoenix.how_to_use_this_manual"></a><h3>
-<a name="id673111"></a>
+<a name="id625325"></a>
<a class="link" href="index.html#phoenix.how_to_use_this_manual">How to use this manual</a>
</h3>
<p>
@@ -193,7 +193,7 @@
icons precede some text to indicate:
</p>
<div class="table">
-<a name="id673146"></a><p class="title"><b>Table 1.1. Icons</b></p>
+<a name="id625359"></a><p class="title"><b>Table 1.1. Icons</b></p>
<div class="table-contents"><table class="table" summary="Icons">
<colgroup>
<col>
@@ -282,12 +282,12 @@
</p>
</div>
<a name="phoenix._emphasis_role__bold___emphasis____to_joel_s_dear_daughter__phoenix__emphasis___emphasis_"></a><h3>
-<a name="id713914"></a>
+<a name="id666128"></a>
<a class="link" href="index.html#phoenix._emphasis_role__bold___emphasis____to_joel_s_dear_daughter__phoenix__emphasis___emphasis_"><span class="bold"><strong><span class="emphasis"><em>...To Joel's dear daughter, Phoenix</em></span></strong></span></a>
</h3>
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
-<td align="left"><p><small>Last revised: February 26, 2011 at 15:17:32 GMT</small></p></td>
+<td align="left"><p><small>Last revised: March 03, 2011 at 20:16:27 GMT</small></p></td>
<td align="right"><div class="copyright-footer"></div></td>
</tr></table>
<hr>
Modified: sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/basics.html
==============================================================================
--- sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/basics.html (original)
+++ sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/basics.html 2011-03-03 15:18:12 EST (Thu, 03 Mar 2011)
@@ -42,7 +42,7 @@
</p></td></tr>
</table></div>
<a name="phoenix.basics.partial_function_application"></a><h4>
-<a name="id717300"></a>
+<a name="id669514"></a>
<a class="link" href="basics.html#phoenix.basics.partial_function_application">Partial Function
Application</a>
</h4>
@@ -94,7 +94,7 @@
black boxes anymore.
</p>
<a name="phoenix.basics.stl_and_higher_order_functions"></a><h4>
-<a name="id717516"></a>
+<a name="id669729"></a>
<a class="link" href="basics.html#phoenix.basics.stl_and_higher_order_functions">STL and higher
order functions</a>
</h4>
@@ -126,7 +126,7 @@
</p></td></tr>
</table></div>
<a name="phoenix.basics.lazy_evaluation"></a><h4>
-<a name="id717727"></a>
+<a name="id669940"></a>
<a class="link" href="basics.html#phoenix.basics.lazy_evaluation">Lazy Evaluation</a>
</h4>
<p>
@@ -181,7 +181,7 @@
</span><span class="identifier">std</span><span class="special">::</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">std</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><h4>
-<a name="id718269"></a>
+<a name="id670483"></a>
<a class="link" href="basics.html#phoenix.basics.forwarding_function_problem">Forwarding Function
Problem</a>
</h4>
@@ -222,7 +222,7 @@
</p></td></tr>
</table></div>
<a name="phoenix.basics.polymorphic_functions"></a><h4>
-<a name="id718408"></a>
+<a name="id670621"></a>
<a class="link" href="basics.html#phoenix.basics.polymorphic_functions">Polymorphic Functions</a>
</h4>
<p>
Modified: sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/examples/adding_an_expression.html
==============================================================================
--- sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/examples/adding_an_expression.html (original)
+++ sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/examples/adding_an_expression.html 2011-03-03 15:18:12 EST (Thu, 03 Mar 2011)
@@ -79,9 +79,9 @@
<p>
<code class="computeroutput"><span class="identifier">while_eval</span></code> is an example
of how to evaluate an expression. It gets called in the <code class="computeroutput"><span class="identifier">rule</span><span class="special">::</span><span class="keyword">while</span></code> action.
- <code class="computeroutput"><span class="identifier">while_gen</span></code> and `while? are
- the expression template front ends. Let's break this apart to undestand what's
- happening. Let's start at the bottom. It's easier that way.
+ <code class="computeroutput"><span class="identifier">while_gen</span></code> and <code class="computeroutput"><span class="identifier">while_</span></code> are the expression template front
+ ends. Let's break this apart to undestand what's happening. Let's start at
+ the bottom. It's easier that way.
</p>
<p>
When you write:
@@ -108,9 +108,8 @@
where <code class="computeroutput"><span class="identifier">Cond</span></code> is the type of
<code class="computeroutput"><span class="identifier">cond</span></code> and <code class="computeroutput"><span class="identifier">Do</span></code>
is the type of <code class="computeroutput"><span class="identifier">do_</span></code>. Notice
- how we are using phoenix's <a class="link" href="../inside/expression.html" title="Phoenix Expressions">Expression)
- mechanism here</a>[link phoenix.inside.expression Expression) mechanism
- here
+ how we are using Phoenix's <a class="link" href="../inside/expression.html" title="Phoenix Expressions">Expression</a>
+ mechanism here
</p>
<pre class="programlisting"><span class="keyword">template</span> <span class="special"><</span><span class="keyword">typename</span> <span class="identifier">Do</span><span class="special">></span>
<span class="keyword">typename</span> <span class="identifier">expression</span><span class="special">::</span><span class="identifier">while_</span><span class="special"><</span><span class="identifier">Cond</span><span class="special">,</span> <span class="identifier">Do</span><span class="special">>::</span><span class="identifier">type</span> <span class="keyword">const</span>
Modified: sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/examples/extending_actors.html
==============================================================================
--- sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/examples/extending_actors.html (original)
+++ sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/examples/extending_actors.html 2011-03-03 15:18:12 EST (Thu, 03 Mar 2011)
@@ -26,7 +26,7 @@
evaluation of expressions.
</p>
<p>
- For some uses cases this might not be enough. For convenience it is thinkable
+ For some use cases this might not be enough. For convenience it is thinkable
to provide custom member functions which generate new expressions. An example
is the <a class="link" href="../modules/statement/___if_else_____statement.html" title="if_else_ Statement">if_else_
Statement</a>
@@ -39,7 +39,7 @@
on how to implement a custom actor which is usable as if it were a STL Container.
</p>
<a name="phoenix.examples.extending_actors.requirements"></a><h5>
-<a name="id767396"></a>
+<a name="id719608"></a>
<a class="link" href="extending_actors.html#phoenix.examples.extending_actors.requirements">Requirements</a>
</h5>
<p>
@@ -141,7 +141,7 @@
Additionally, we want all the operator() overloads of the regular actor.
</p>
<a name="phoenix.examples.extending_actors.defining_the_actor"></a><h5>
-<a name="id767709"></a>
+<a name="id719921"></a>
<a class="link" href="extending_actors.html#phoenix.examples.extending_actors.defining_the_actor">Defining
the actor</a>
</h5>
@@ -174,7 +174,7 @@
<span class="special">};</span>
</pre>
<a name="phoenix.examples.extending_actors.using_the_actor"></a><h5>
-<a name="id768594"></a>
+<a name="id720805"></a>
<a class="link" href="extending_actors.html#phoenix.examples.extending_actors.using_the_actor">Using the
actor</a>
</h5>
@@ -231,7 +231,7 @@
Wow, that was easy!
</p>
<a name="phoenix.examples.extending_actors.adding_life_to_the_actor"></a><h5>
-<a name="id769261"></a>
+<a name="id721472"></a>
<a class="link" href="extending_actors.html#phoenix.examples.extending_actors.adding_life_to_the_actor">Adding
life to the actor</a>
</h5>
Modified: sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/inside.html
==============================================================================
--- sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/inside.html (original)
+++ sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/inside.html 2011-03-03 15:18:12 EST (Thu, 03 Mar 2011)
@@ -36,8 +36,8 @@
<p>
This chapter explains in more detail how the library operates. The information
henceforth should not be necessary to those who are interested in just using
- the library. However, a microscopic view might prove to be beneficial to moderate
- to advanced programmers who wish to extend the library.
+ the library. However, a microscopic view might prove to be beneficial to advanced
+ programmers who wish to extend the library.
</p>
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
Modified: sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/inside/actions.html
==============================================================================
--- sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/inside/actions.html (original)
+++ sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/inside/actions.html 2011-03-03 15:18:12 EST (Thu, 03 Mar 2011)
@@ -84,7 +84,7 @@
how the Phoenix AST will be traversed.
</p>
<a name="phoenix.inside.actions.writing_an_action"></a><h5>
-<a name="id756487"></a>
+<a name="id708698"></a>
<a class="link" href="actions.html#phoenix.inside.actions.writing_an_action">Writing an Action</a>
</h5>
<p>
@@ -133,8 +133,8 @@
be full fletched <a href="http://www.boost.org/doc/libs/release/doc/html/Transform.html" target="_top">Proto
Transforms</a>, you can in fact use any proto expression you can imagine
as the action. Phoenix predifines a set of callables and transform to deal
- with the Context information passed along and of course every phoenix expression
- can be used as a phoenix grammar or <a href="http://www.boost.org/doc/libs/release/doc/html/boost/proto/pass_through.html" target="_top">Proto
+ with the Context information passed along and of course every Phoenix expression
+ can be used as a Phoenix grammar or <a href="http://www.boost.org/doc/libs/release/doc/html/boost/proto/pass_through.html" target="_top">Proto
Pass Through Transform</a>.
</p>
<div class="variablelist">
Modified: sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/inside/actor.html
==============================================================================
--- sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/inside/actor.html (original)
+++ sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/inside/actor.html 2011-03-03 15:18:12 EST (Thu, 03 Mar 2011)
@@ -20,7 +20,7 @@
<a name="phoenix.inside.actor"></a><a class="link" href="actor.html" title="Actors in Detail">Actors in Detail</a>
</h3></div></div></div>
<a name="phoenix.inside.actor.actor"></a><h5>
-<a name="id747948"></a>
+<a name="id700161"></a>
<a class="link" href="actor.html#phoenix.inside.actor.actor">Actor</a>
</h5>
<p>
@@ -70,7 +70,7 @@
</span><span class="special">};</span>
</pre>
<div class="table">
-<a name="id748466"></a><p class="title"><b>Table 1.9. Actor Concept Requirements</b></p>
+<a name="id700679"></a><p class="title"><b>Table 1.9. Actor Concept Requirements</b></p>
<div class="table-contents"><table class="table" summary="Actor Concept Requirements">
<colgroup>
<col>
@@ -136,7 +136,7 @@
</table></div>
</div>
<br class="table-break"><a name="phoenix.inside.actor.function_call_operators"></a><h5>
-<a name="id748767"></a>
+<a name="id700981"></a>
<a class="link" href="actor.html#phoenix.inside.actor.function_call_operators">Function Call
Operators</a>
</h5>
@@ -169,7 +169,7 @@
</td></tr>
</table></div>
<a name="phoenix.inside.actor.context"></a><h5>
-<a name="id748874"></a>
+<a name="id701087"></a>
<a class="link" href="actor.html#phoenix.inside.actor.context">Context</a>
</h5>
<p>
@@ -180,7 +180,7 @@
all information necessary to evaluate the given expression.
</p>
<div class="table">
-<a name="id748919"></a><p class="title"><b>Table 1.10. Context Concept Requirements</b></p>
+<a name="id701132"></a><p class="title"><b>Table 1.10. Context Concept Requirements</b></p>
<div class="table-contents"><table class="table" summary="Context Concept Requirements">
<colgroup>
<col>
@@ -278,7 +278,7 @@
</table></div>
</div>
<br class="table-break"><a name="phoenix.inside.actor.environment"></a><h5>
-<a name="id749286"></a>
+<a name="id701499"></a>
<a class="link" href="actor.html#phoenix.inside.actor.environment">Environment</a>
</h5>
<p>
@@ -297,13 +297,13 @@
such as local variables, etc.
</p>
<a name="phoenix.inside.actor.actions"></a><h5>
-<a name="id749351"></a>
+<a name="id701565"></a>
<a class="link" href="actor.html#phoenix.inside.actor.actions">Actions</a>
</h5>
<p>
Actions is the part of Phoenix which are responsible for giving the actual
expressions a specific behaviour. During the traversal of the Phoenix Expression
- Tree theses actions are called whenever a specified rule in the grammar matches.
+ Tree these actions are called whenever a specified rule in the grammar matches.
</p>
<pre class="programlisting"><span class="keyword">struct</span> <span class="identifier">actions</span>
<span class="special">{</span>
@@ -314,7 +314,7 @@
<p>
The nested <code class="computeroutput"><span class="identifier">when</span></code> template
is required to be <a href="http://www.boost.org/doc/libs/release/doc/html/PrimitiveTransform.html" target="_top">Proto
- Primitive Transform</a>. No Worries, you don't have to learn Boost.Proto
+ Primitive Transform</a>. No worries, you don't have to learn Boost.Proto
just yet! Phoenix provides some wrappers to let you define simple actions
without the need to dive deep into proto.
</p>
@@ -331,12 +331,12 @@
<span class="special">};</span>
</pre>
<p>
- For more Information on how to use the default_actions class and how to attach
+ For more information on how to use the default_actions class and how to attach
custom actions to the evaluation process, see <a class="link" href="actions.html" title="More on Actions">more
on actions</a>.
</p>
<a name="phoenix.inside.actor.evaluation"></a><h5>
-<a name="id749635"></a>
+<a name="id701848"></a>
<a class="link" href="actor.html#phoenix.inside.actor.evaluation">Evaluation</a>
</h5>
<pre class="programlisting"><span class="keyword">struct</span> <span class="identifier">evaluator</span>
@@ -353,7 +353,7 @@
</p>
<p>
The evaluator is called by the <code class="computeroutput"><span class="identifier">actor</span></code>
- functio operator overloads after the context is built up. For reference,
+ function operator overloads after the context is built up. For reference,
here is a typical <code class="computeroutput"><span class="identifier">actor</span><span class="special">::</span><span class="keyword">operator</span><span class="special">()</span></code>
that accepts two arguments:
</p>
@@ -367,13 +367,13 @@
<span class="special">}</span>
</pre>
<a name="phoenix.inside.actor.result_of__actor"></a><h5>
-<a name="id750140"></a>
+<a name="id702353"></a>
<a class="link" href="actor.html#phoenix.inside.actor.result_of__actor">result_of::actor</a>
</h5>
<p>
For reasons of symmetry to the family of <code class="computeroutput"><span class="identifier">actor</span><span class="special">::</span><span class="keyword">operator</span><span class="special">()</span></code> there is a special metafunction usable
for actor result type calculation named <code class="computeroutput"><span class="identifier">result_of</span><span class="special">::</span><span class="identifier">actor</span></code>.
- This metafunction allows us to directly to specify the types of the parameters
+ This metafunction allows us to directly specify the types of the parameters
to be passed to the <code class="computeroutput"><span class="identifier">actor</span><span class="special">::</span><span class="keyword">operator</span><span class="special">()</span></code> function. Here's a typical <code class="computeroutput"><span class="identifier">actor_result</span></code> that accepts two arguments:
</p>
<pre class="programlisting"><span class="keyword">namespace</span> <span class="identifier">result_of</span>
Modified: sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/inside/custom_terminals.html
==============================================================================
--- sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/inside/custom_terminals.html (original)
+++ sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/inside/custom_terminals.html 2011-03-03 15:18:12 EST (Thu, 03 Mar 2011)
@@ -20,9 +20,9 @@
<a name="phoenix.inside.custom_terminals"></a><a class="link" href="custom_terminals.html" title="Custom Terminals">Custom Terminals</a>
</h3></div></div></div>
<p>
- Custom Terminals are used in phoenix to handle special values transparently.
- For example, as phoenix captures everything by value, we needed to use <code class="computeroutput"><span class="identifier">boost</span><span class="special">::</span><span class="identifier">reference_wrapper</span></code> to bring in reference
- semantics into phoenix.
+ Custom Terminals are used in Phoenix to handle special values transparently.
+ For example, as Phoenix captures everything by value, we needed to use <code class="computeroutput"><span class="identifier">boost</span><span class="special">::</span><span class="identifier">reference_wrapper</span></code> to bring reference semantics
+ into Phoenix.
</p>
<p>
Custom terminals could be any wrapper class:
@@ -31,7 +31,7 @@
<span class="keyword">struct</span> <span class="identifier">is_custom_terminal</span><span class="special">;</span>
</pre>
<p>
- needs to be specialized in order for phoenix to recognize this wrapper type.
+ needs to be specialized in order for Phoenix to recognize this wrapper type.
<code class="computeroutput"><span class="identifier">default_action</span></code> calls <code class="computeroutput"><span class="identifier">custom_terminal</span><span class="special"><</span><span class="identifier">T</span><span class="special">></span></code>.
</p>
<p>
Modified: sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/inside/expression.html
==============================================================================
--- sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/inside/expression.html (original)
+++ sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/inside/expression.html 2011-03-03 15:18:12 EST (Thu, 03 Mar 2011)
@@ -30,11 +30,11 @@
Expression</a> Concept. These expressions are wrapped inside an <a class="link" href="actor.html" title="Actors in Detail">Actor</a> template. The <code class="computeroutput"><span class="identifier">actor</span></code>
provides the function call operator which evaluates the expressions. The
<code class="computeroutput"><span class="identifier">actor</span></code> is the domain specific
- wrapper around phoenix expressions.
+ wrapper around Phoenix expressions.
</p>
<p>
By design, Phoenix Expressions do not carry any information on how they will
- be evaluated later on. They are the data structure on which the <code class="computeroutput"><span class="identifier">Actions</span></code> will work on.
+ be evaluated later on. They are the data structure on which the <code class="computeroutput"><span class="identifier">Actions</span></code> will work.
</p>
<p>
The library provides a convenience template to define expressions:
@@ -155,13 +155,13 @@
</p></td></tr>
</table></div>
<a name="phoenix.inside.expression.meta_grammar"></a><h5>
-<a name="id751553"></a>
+<a name="id703766"></a>
<a class="link" href="expression.html#phoenix.inside.expression.meta_grammar">meta_grammar</a>
</h5>
<p>
- Defining Expressions is only part of the game to make it a valid Phoenix
+ Defining expressions is only part of the game to make it a valid Phoenix
Expression. In order to use the expressions in the Phoenix domain, we need
- to "register" our newly created to our grammar.
+ to "register" them to our grammar.
</p>
<p>
The <code class="computeroutput"><span class="identifier">meta_grammar</span></code> is a struct
@@ -183,7 +183,7 @@
you include this grammar gets extended by various expressions.
</p>
<a name="phoenix.inside.expression.example"></a><h5>
-<a name="id751784"></a>
+<a name="id703997"></a>
<a class="link" href="expression.html#phoenix.inside.expression.example">Example</a>
</h5>
<p>
@@ -218,7 +218,7 @@
<span class="special">}</span>
</pre>
<p>
- Look of it really works:
+ Look if it really works:
</p>
<pre class="programlisting"><span class="identifier">plus</span><span class="special">(</span><span class="number">6</span><span class="special">,</span> <span class="number">5</span><span class="special">)();</span>
</pre>
@@ -246,18 +246,18 @@
</tr>
<tr><td align="left" valign="top"><p>
The example shown here only works because <code class="computeroutput"><span class="identifier">default_actions</span></code>
- know how to handle an expression having the <code class="computeroutput"><span class="identifier">proto</span><span class="special">::</span><span class="identifier">tag</span><span class="special">::</span><span class="identifier">plus</span></code>
+ knows how to handle an expression having the <code class="computeroutput"><span class="identifier">proto</span><span class="special">::</span><span class="identifier">tag</span><span class="special">::</span><span class="identifier">plus</span></code>
and two children. This is because <code class="computeroutput"><span class="identifier">default_actions</span></code>
uses the <code class="computeroutput"><span class="identifier">proto</span><span class="special">::</span><span class="identifier">_default</span><span class="special"><</span><span class="identifier">meta_grammar</span><span class="special">></span></code>
transform to evaluate operators and functions. Learn more about actions
- <a class="link" href="actions.html" title="More on Actions">here</a>
+ <a class="link" href="actions.html" title="More on Actions">here</a>.
</p></td></tr>
</table></div>
<p>
When having more and more expressions, you start to realize that this is
a very repetetive task. Phoenix provides boilerplate macros that make defining
Phoenix Expressions as you have seen in the <a class="link" href="expression.html" title="Phoenix Expressions">previous
- section</a> look like a piece of cake. ]
+ section</a> look like a piece of cake.
</p>
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
Modified: sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/inside/expression/boost_phoenix_define_expression.html
==============================================================================
--- sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/inside/expression/boost_phoenix_define_expression.html (original)
+++ sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/inside/expression/boost_phoenix_define_expression.html 2011-03-03 15:18:12 EST (Thu, 03 Mar 2011)
@@ -20,7 +20,7 @@
<a name="phoenix.inside.expression.boost_phoenix_define_expression"></a><a class="link" href="boost_phoenix_define_expression.html" title="BOOST_PHOENIX_DEFINE_EXPRESSION">BOOST_PHOENIX_DEFINE_EXPRESSION</a>
</h4></div></div></div>
<a name="phoenix.inside.expression.boost_phoenix_define_expression.description"></a><h6>
-<a name="id752605"></a>
+<a name="id704818"></a>
<a class="link" href="boost_phoenix_define_expression.html#phoenix.inside.expression.boost_phoenix_define_expression.description">Description</a>
</h6>
<p>
@@ -29,7 +29,7 @@
create Phoenix Expressions
</p>
<a name="phoenix.inside.expression.boost_phoenix_define_expression.synopsis"></a><h6>
-<a name="id752639"></a>
+<a name="id704853"></a>
<a class="link" href="boost_phoenix_define_expression.html#phoenix.inside.expression.boost_phoenix_define_expression.synopsis">Synopsis</a>
</h6>
<pre class="programlisting"><span class="identifier">BOOST_PHOENIX_DEFINE_EXPRESSION</span><span class="special">(</span>
@@ -40,7 +40,7 @@
<span class="special">)</span>
</pre>
<a name="phoenix.inside.expression.boost_phoenix_define_expression.semantics"></a><h6>
-<a name="id752744"></a>
+<a name="id704958"></a>
<a class="link" href="boost_phoenix_define_expression.html#phoenix.inside.expression.boost_phoenix_define_expression.semantics">Semantics</a>
</h6>
<p>
@@ -88,13 +88,13 @@
This macros also adds a specialization for <code class="computeroutput"><span class="identifier">meta_grammar</span><span class="special">::</span><span class="identifier">case_</span><span class="special"><</span><span class="identifier">tag</span><span class="special">::</span><span class="identifier">name</span><span class="special">></span></code>.
</p>
<a name="phoenix.inside.expression.boost_phoenix_define_expression.header"></a><h6>
-<a name="id753232"></a>
+<a name="id705445"></a>
<a class="link" href="boost_phoenix_define_expression.html#phoenix.inside.expression.boost_phoenix_define_expression.header">Header</a>
</h6>
<pre class="programlisting"><span class="preprocessor">#include</span> <span class="special"><</span><span class="identifier">boost</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">expression</span><span class="special">.</span><span class="identifier">hpp</span><span class="special">></span>
</pre>
<a name="phoenix.inside.expression.boost_phoenix_define_expression.example"></a><h6>
-<a name="id753314"></a>
+<a name="id705527"></a>
<a class="link" href="boost_phoenix_define_expression.html#phoenix.inside.expression.boost_phoenix_define_expression.example">Example</a>
</h6>
<p>
Modified: sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/inside/expression/boost_phoenix_define_expression_ext.html
==============================================================================
--- sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/inside/expression/boost_phoenix_define_expression_ext.html (original)
+++ sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/inside/expression/boost_phoenix_define_expression_ext.html 2011-03-03 15:18:12 EST (Thu, 03 Mar 2011)
@@ -20,7 +20,7 @@
<a name="phoenix.inside.expression.boost_phoenix_define_expression_ext"></a><a class="link" href="boost_phoenix_define_expression_ext.html" title="BOOST_PHOENIX_DEFINE_EXPRESSION_EXT">BOOST_PHOENIX_DEFINE_EXPRESSION_EXT</a>
</h4></div></div></div>
<a name="phoenix.inside.expression.boost_phoenix_define_expression_ext.description"></a><h6>
-<a name="id754546"></a>
+<a name="id706759"></a>
<a class="link" href="boost_phoenix_define_expression_ext.html#phoenix.inside.expression.boost_phoenix_define_expression_ext.description">Description</a>
</h6>
<p>
@@ -29,7 +29,7 @@
create Phoenix Expressions
</p>
<a name="phoenix.inside.expression.boost_phoenix_define_expression_ext.synopsis"></a><h6>
-<a name="id754580"></a>
+<a name="id706794"></a>
<a class="link" href="boost_phoenix_define_expression_ext.html#phoenix.inside.expression.boost_phoenix_define_expression_ext.synopsis">Synopsis</a>
</h6>
<pre class="programlisting"><span class="identifier">BOOST_PHOENIX_DEFINE_EXPRESSION_EXT</span><span class="special">(</span>
@@ -43,7 +43,7 @@
<span class="special">)</span>
</pre>
<a name="phoenix.inside.expression.boost_phoenix_define_expression_ext.semantics"></a><h6>
-<a name="id754721"></a>
+<a name="id706934"></a>
<a class="link" href="boost_phoenix_define_expression_ext.html#phoenix.inside.expression.boost_phoenix_define_expression_ext.semantics">Semantics</a>
</h6>
<p>
@@ -92,13 +92,13 @@
This macros also adds a specialization for <code class="computeroutput"><span class="identifier">meta_grammar</span><span class="special">::</span><span class="identifier">case_</span><span class="special"><</span><span class="identifier">tag</span><span class="special">::</span><span class="identifier">name</span><span class="special">></span></code>.
</p>
<a name="phoenix.inside.expression.boost_phoenix_define_expression_ext.header"></a><h6>
-<a name="id755221"></a>
+<a name="id707434"></a>
<a class="link" href="boost_phoenix_define_expression_ext.html#phoenix.inside.expression.boost_phoenix_define_expression_ext.header">Header</a>
</h6>
<pre class="programlisting"><span class="preprocessor">#include</span> <span class="special"><</span><span class="identifier">boost</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">expression</span><span class="special">.</span><span class="identifier">hpp</span><span class="special">></span>
</pre>
<a name="phoenix.inside.expression.boost_phoenix_define_expression_ext.example"></a><h6>
-<a name="id755304"></a>
+<a name="id707517"></a>
<a class="link" href="boost_phoenix_define_expression_ext.html#phoenix.inside.expression.boost_phoenix_define_expression_ext.example">Example</a>
</h6>
<pre class="programlisting"><span class="identifier">BOOST_PHOENIX_DEFINE_EXPRESSION_EXT</span><span class="special">(</span>
Modified: sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/inside/expression/boost_phoenix_define_expression_ext_vararg.html
==============================================================================
--- sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/inside/expression/boost_phoenix_define_expression_ext_vararg.html (original)
+++ sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/inside/expression/boost_phoenix_define_expression_ext_vararg.html 2011-03-03 15:18:12 EST (Thu, 03 Mar 2011)
@@ -20,7 +20,7 @@
<a name="phoenix.inside.expression.boost_phoenix_define_expression_ext_vararg"></a><a class="link" href="boost_phoenix_define_expression_ext_vararg.html" title="BOOST_PHOENIX_DEFINE_EXPRESSION_EXT_VARARG">BOOST_PHOENIX_DEFINE_EXPRESSION_EXT_VARARG</a>
</h4></div></div></div>
<a name="phoenix.inside.expression.boost_phoenix_define_expression_ext_vararg.description"></a><h6>
-<a name="id755465"></a>
+<a name="id707679"></a>
<a class="link" href="boost_phoenix_define_expression_ext_vararg.html#phoenix.inside.expression.boost_phoenix_define_expression_ext_vararg.description">Description</a>
</h6>
<p>
@@ -29,7 +29,7 @@
create Phoenix Expressions
</p>
<a name="phoenix.inside.expression.boost_phoenix_define_expression_ext_vararg.synopsis"></a><h6>
-<a name="id755501"></a>
+<a name="id707715"></a>
<a class="link" href="boost_phoenix_define_expression_ext_vararg.html#phoenix.inside.expression.boost_phoenix_define_expression_ext_vararg.synopsis">Synopsis</a>
</h6>
<pre class="programlisting"><span class="identifier">BOOST_PHOENIX_DEFINE_EXPRESSION_EXT_VARARG</span><span class="special">(</span>
@@ -43,7 +43,7 @@
<span class="special">)</span>
</pre>
<a name="phoenix.inside.expression.boost_phoenix_define_expression_ext_vararg.semantics"></a><h6>
-<a name="id755643"></a>
+<a name="id707857"></a>
<a class="link" href="boost_phoenix_define_expression_ext_vararg.html#phoenix.inside.expression.boost_phoenix_define_expression_ext_vararg.semantics">Semantics</a>
</h6>
<p>
@@ -92,13 +92,13 @@
<span class="special">}</span>
</pre>
<a name="phoenix.inside.expression.boost_phoenix_define_expression_ext_vararg.header"></a><h6>
-<a name="id756109"></a>
+<a name="id708320"></a>
<a class="link" href="boost_phoenix_define_expression_ext_vararg.html#phoenix.inside.expression.boost_phoenix_define_expression_ext_vararg.header">Header</a>
</h6>
<pre class="programlisting"><span class="preprocessor">#include</span> <span class="special"><</span><span class="identifier">boost</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">expression</span><span class="special">.</span><span class="identifier">hpp</span><span class="special">></span>
</pre>
<a name="phoenix.inside.expression.boost_phoenix_define_expression_ext_vararg.example"></a><h6>
-<a name="id756192"></a>
+<a name="id708403"></a>
<a class="link" href="boost_phoenix_define_expression_ext_vararg.html#phoenix.inside.expression.boost_phoenix_define_expression_ext_vararg.example">Example</a>
</h6>
<p>
Modified: sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/inside/expression/boost_phoenix_define_expression_vararg.html
==============================================================================
--- sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/inside/expression/boost_phoenix_define_expression_vararg.html (original)
+++ sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/inside/expression/boost_phoenix_define_expression_vararg.html 2011-03-03 15:18:12 EST (Thu, 03 Mar 2011)
@@ -20,7 +20,7 @@
<a name="phoenix.inside.expression.boost_phoenix_define_expression_vararg"></a><a class="link" href="boost_phoenix_define_expression_vararg.html" title="BOOST_PHOENIX_DEFINE_EXPRESSION_VARARG">BOOST_PHOENIX_DEFINE_EXPRESSION_VARARG</a>
</h4></div></div></div>
<a name="phoenix.inside.expression.boost_phoenix_define_expression_vararg.description"></a><h6>
-<a name="id753662"></a>
+<a name="id705876"></a>
<a class="link" href="boost_phoenix_define_expression_vararg.html#phoenix.inside.expression.boost_phoenix_define_expression_vararg.description">Description</a>
</h6>
<p>
@@ -29,7 +29,7 @@
create Phoenix Expressions
</p>
<a name="phoenix.inside.expression.boost_phoenix_define_expression_vararg.synopsis"></a><h6>
-<a name="id753698"></a>
+<a name="id705912"></a>
<a class="link" href="boost_phoenix_define_expression_vararg.html#phoenix.inside.expression.boost_phoenix_define_expression_vararg.synopsis">Synopsis</a>
</h6>
<pre class="programlisting"><span class="identifier">BOOST_PHOENIX_DEFINE_EXPRESSION_VARARG</span><span class="special">(</span>
@@ -42,7 +42,7 @@
<span class="special">)</span>
</pre>
<a name="phoenix.inside.expression.boost_phoenix_define_expression_vararg.semantics"></a><h6>
-<a name="id753830"></a>
+<a name="id706043"></a>
<a class="link" href="boost_phoenix_define_expression_vararg.html#phoenix.inside.expression.boost_phoenix_define_expression_vararg.semantics">Semantics</a>
</h6>
<p>
@@ -90,13 +90,13 @@
<span class="special">}</span>
</pre>
<a name="phoenix.inside.expression.boost_phoenix_define_expression_vararg.header"></a><h6>
-<a name="id754282"></a>
+<a name="id706495"></a>
<a class="link" href="boost_phoenix_define_expression_vararg.html#phoenix.inside.expression.boost_phoenix_define_expression_vararg.header">Header</a>
</h6>
<pre class="programlisting"><span class="preprocessor">#include</span> <span class="special"><</span><span class="identifier">boost</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">expression</span><span class="special">.</span><span class="identifier">hpp</span><span class="special">></span>
</pre>
<a name="phoenix.inside.expression.boost_phoenix_define_expression_vararg.example"></a><h6>
-<a name="id754365"></a>
+<a name="id706578"></a>
<a class="link" href="boost_phoenix_define_expression_vararg.html#phoenix.inside.expression.boost_phoenix_define_expression_vararg.example">Example</a>
</h6>
<pre class="programlisting"><span class="identifier">BOOST_PHOENIX_DEFINE_EXPRESSION_VARARG</span><span class="special">(</span>
Modified: sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/inside/placeholder_unification.html
==============================================================================
--- sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/inside/placeholder_unification.html (original)
+++ sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/inside/placeholder_unification.html 2011-03-03 15:18:12 EST (Thu, 03 Mar 2011)
@@ -30,7 +30,7 @@
</pre>
<p>
To adapt your own placeholder, the nested value needs to be greater than
- 0 for your types. This is done with specializing this trait.
+ 0 for your types. This is done by specializing this trait.
</p>
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
Modified: sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/modules/core/arguments.html
==============================================================================
--- sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/modules/core/arguments.html (original)
+++ sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/modules/core/arguments.html 2011-03-03 15:18:12 EST (Thu, 03 Mar 2011)
@@ -31,7 +31,7 @@
an imaginary data-bin where a function argument will be placed.
</p>
<a name="phoenix.modules.core.arguments.predefined_arguments"></a><h6>
-<a name="id721354"></a>
+<a name="id673567"></a>
<a class="link" href="arguments.html#phoenix.modules.core.arguments.predefined_arguments">Predefined
Arguments</a>
</h6>
@@ -75,7 +75,7 @@
</p></td></tr>
</table></div>
<a name="phoenix.modules.core.arguments.user_defined_arguments"></a><h6>
-<a name="id721879"></a>
+<a name="id674092"></a>
<a class="link" href="arguments.html#phoenix.modules.core.arguments.user_defined_arguments">User
Defined Arguments</a>
</h6>
@@ -97,7 +97,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.modules.core.arguments.evaluating_an_argument"></a><h6>
-<a name="id722030"></a>
+<a name="id674244"></a>
<a class="link" href="arguments.html#phoenix.modules.core.arguments.evaluating_an_argument">Evaluating
an Argument</a>
</h6>
@@ -124,7 +124,7 @@
<span class="identifier">Hello</span> <span class="identifier">World</span>
</pre>
<a name="phoenix.modules.core.arguments.extra_arguments"></a><h6>
-<a name="id722327"></a>
+<a name="id674541"></a>
<a class="link" href="arguments.html#phoenix.modules.core.arguments.extra_arguments">Extra Arguments</a>
</h6>
<p>
Modified: sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/modules/core/nothing.html
==============================================================================
--- sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/modules/core/nothing.html (original)
+++ sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/modules/core/nothing.html 2011-03-03 15:18:12 EST (Thu, 03 Mar 2011)
@@ -23,7 +23,7 @@
</pre>
<p>
Finally, the <code class="computeroutput"><span class="identifier">expression</span><span class="special">::</span><span class="identifier">null</span><span class="special"><</span><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">void_</span><span class="special">>::</span><span class="identifier">type</span></code>
- does nothing; (a "bum", if you will :-). There's a sole <code class="computeroutput"><span class="identifier">expression</span><span class="special">::</span><span class="identifier">null</span><span class="special"><</span><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">void_</span><span class="special">>::</span><span class="identifier">type</span></code> instance named "nothing".
+ does nothing; (a "bum", if you will :-) ). There's a sole <code class="computeroutput"><span class="identifier">expression</span><span class="special">::</span><span class="identifier">null</span><span class="special"><</span><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">void_</span><span class="special">>::</span><span class="identifier">type</span></code> instance named "nothing".
This actor is actually useful in situations where we don't want to do anything.
(See <a class="link" href="../statement/for_statement.html" title="for_ Statement">for_ Statement</a>
for example).
Modified: sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/modules/core/references.html
==============================================================================
--- sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/modules/core/references.html (original)
+++ sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/modules/core/references.html 2011-03-03 15:18:12 EST (Thu, 03 Mar 2011)
@@ -37,8 +37,8 @@
<p>
In C++, we can pass in a reference to a variable as the first argument
in our example above. Yet, by default, the library forces arguments passed
- to partially applied functions functions to be immutable values (see <a class="link" href="values.html" title="Values">Values</a>). To achieve our intent,
- we use:
+ to partially applied functions to be immutable values (see <a class="link" href="values.html" title="Values">Values</a>).
+ To achieve our intent, we use:
</p>
<pre class="programlisting"><span class="identifier">expression</span><span class="special">::</span><span class="identifier">reference</span><span class="special"><</span><span class="identifier">T</span><span class="special">>::</span><span class="identifier">type</span>
</pre>
@@ -59,7 +59,7 @@
<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.modules.core.references.evaluating_a_reference"></a><h6>
-<a name="id720951"></a>
+<a name="id673165"></a>
<a class="link" href="references.html#phoenix.modules.core.references.evaluating_a_reference">Evaluating
a Reference</a>
</h6>
@@ -75,7 +75,7 @@
prints out "3 Hello World"
</p>
<a name="phoenix.modules.core.references.constant_references"></a><h6>
-<a name="id721088"></a>
+<a name="id673301"></a>
<a class="link" href="references.html#phoenix.modules.core.references.constant_references">Constant
References</a>
</h6>
Modified: sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/modules/core/values.html
==============================================================================
--- sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/modules/core/values.html (original)
+++ sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/modules/core/values.html 2011-03-03 15:18:12 EST (Thu, 03 Mar 2011)
@@ -47,7 +47,7 @@
but, as we'll see later on, there are situations where this is unavoidable.
</p>
<a name="phoenix.modules.core.values.evaluating_a_value"></a><h3>
-<a name="id720470"></a>
+<a name="id672683"></a>
<a class="link" href="values.html#phoenix.modules.core.values.evaluating_a_value">Evaluating
a Value</a>
</h3>
Modified: sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/modules/operator.html
==============================================================================
--- sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/modules/operator.html (original)
+++ sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/modules/operator.html 2011-03-03 15:18:12 EST (Thu, 03 Mar 2011)
@@ -134,18 +134,18 @@
</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.modules.operator.supported_operators"></a><h5>
-<a name="id724696"></a>
+<a name="id676910"></a>
<a class="link" href="operator.html#phoenix.modules.operator.supported_operators">Supported operators</a>
</h5>
<a name="phoenix.modules.operator.unary_operators"></a><h5>
-<a name="id724715"></a>
+<a name="id676928"></a>
<a class="link" href="operator.html#phoenix.modules.operator.unary_operators">Unary operators</a>
</h5>
<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.modules.operator.binary_operators"></a><h5>
-<a name="id724846"></a>
+<a name="id677060"></a>
<a class="link" href="operator.html#phoenix.modules.operator.binary_operators">Binary operators</a>
</h5>
<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>
@@ -154,7 +154,7 @@
<span class="special">&&,</span> <span class="special">||,</span> <span class="special">->*</span>
</pre>
<a name="phoenix.modules.operator.ternary_operator"></a><h5>
-<a name="id725048"></a>
+<a name="id677261"></a>
<a class="link" href="operator.html#phoenix.modules.operator.ternary_operator">Ternary operator</a>
</h5>
<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>
@@ -167,7 +167,7 @@
albeit in a lazy manner.
</p>
<a name="phoenix.modules.operator.member_pointer_operator"></a><h5>
-<a name="id725149"></a>
+<a name="id677362"></a>
<a class="link" href="operator.html#phoenix.modules.operator.member_pointer_operator">Member pointer
operator</a>
</h5>
@@ -208,7 +208,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>
<a name="phoenix.modules.operator.include_files"></a><h5>
-<a name="id725529"></a>
+<a name="id677742"></a>
<a class="link" href="operator.html#phoenix.modules.operator.include_files">Include Files</a>
</h5>
<div class="informaltable"><table class="table">
Modified: sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/modules/stl/algorithm.html
==============================================================================
--- sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/modules/stl/algorithm.html (original)
+++ sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/modules/stl/algorithm.html 2011-03-03 15:18:12 EST (Thu, 03 Mar 2011)
@@ -73,7 +73,7 @@
</p>
</div>
<div class="table">
-<a name="id739419"></a><p class="title"><b>Table 1.6. Iteration Algorithms</b></p>
+<a name="id691632"></a><p class="title"><b>Table 1.6. Iteration Algorithms</b></p>
<div class="table-contents"><table class="table" summary="Iteration Algorithms">
<colgroup>
<col>
@@ -128,7 +128,7 @@
</table></div>
</div>
<br class="table-break"><div class="table">
-<a name="id739697"></a><p class="title"><b>Table 1.7. Querying Algorithms</b></p>
+<a name="id691910"></a><p class="title"><b>Table 1.7. Querying Algorithms</b></p>
<div class="table-contents"><table class="table" summary="Querying Algorithms">
<colgroup>
<col>
@@ -441,7 +441,7 @@
</table></div>
</div>
<br class="table-break"><div class="table">
-<a name="id742169"></a><p class="title"><b>Table 1.8. Transformation Algorithms</b></p>
+<a name="id694383"></a><p class="title"><b>Table 1.8. Transformation Algorithms</b></p>
<div class="table-contents"><table class="table" summary="Transformation Algorithms">
<colgroup>
<col>
Modified: sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/modules/stl/container.html
==============================================================================
--- sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/modules/stl/container.html (original)
+++ sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/modules/stl/container.html 2011-03-03 15:18:12 EST (Thu, 03 Mar 2011)
@@ -137,7 +137,7 @@
does not use the member "dot" syntax.
</p>
<div class="table">
-<a name="id736368"></a><p class="title"><b>Table 1.4. Sample usage</b></p>
+<a name="id688581"></a><p class="title"><b>Table 1.4. Sample usage</b></p>
<div class="table-contents"><table class="table" summary="Sample usage">
<colgroup>
<col>
@@ -215,7 +215,7 @@
</p>
</div>
<div class="table">
-<a name="id736707"></a><p class="title"><b>Table 1.5. Lazy STL Container Functions</b></p>
+<a name="id688921"></a><p class="title"><b>Table 1.5. Lazy STL Container Functions</b></p>
<div class="table-contents"><table class="table" summary="Lazy STL Container Functions">
<colgroup>
<col>
Modified: sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/organization.html
==============================================================================
--- sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/organization.html (original)
+++ sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/organization.html 2011-03-03 15:18:12 EST (Thu, 03 Mar 2011)
@@ -52,7 +52,7 @@
files. There are no object files to link against.
</p>
<a name="phoenix.organization.core"></a><h3>
-<a name="id718800"></a>
+<a name="id671013"></a>
<a class="link" href="organization.html#phoenix.organization.core">Core</a>
</h3>
<p>
@@ -72,7 +72,7 @@
can again be another expression.
</p>
<div class="table">
-<a name="id718838"></a><p class="title"><b>Table 1.2. Modules</b></p>
+<a name="id671051"></a><p class="title"><b>Table 1.2. Modules</b></p>
<div class="table-contents"><table class="table" summary="Modules">
<colgroup>
<col>
@@ -200,7 +200,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">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="id719126"></a><p class="title"><b>Table 1.3. Includes</b></p>
+<a name="id671339"></a><p class="title"><b>Table 1.3. Includes</b></p>
<div class="table-contents"><table class="table" summary="Includes">
<colgroup>
<col>
Modified: sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/starter_kit.html
==============================================================================
--- sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/starter_kit.html (original)
+++ sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/starter_kit.html 2011-03-03 15:18:12 EST (Thu, 03 Mar 2011)
@@ -52,7 +52,7 @@
into high gear quickly.
</p>
<a name="phoenix.starter_kit.functors_everywhere"></a><h4>
-<a name="id714019"></a>
+<a name="id666232"></a>
<a class="link" href="starter_kit.html#phoenix.starter_kit.functors_everywhere">Functors everywhere</a>
</h4>
<p>
Modified: sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/starter_kit/lazy_functions.html
==============================================================================
--- sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/starter_kit/lazy_functions.html (original)
+++ sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/starter_kit/lazy_functions.html 2011-03-03 15:18:12 EST (Thu, 03 Mar 2011)
@@ -45,7 +45,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><h5>
-<a name="id716820"></a>
+<a name="id669033"></a>
<a class="link" href="lazy_functions.html#phoenix.starter_kit.lazy_functions.things_to_note_">Things
to note:</a>
</h5>
@@ -75,7 +75,7 @@
(See function.cpp)
</p>
<a name="phoenix.starter_kit.lazy_functions.predefined_lazy_functions"></a><h5>
-<a name="id716998"></a>
+<a name="id669211"></a>
<a class="link" href="lazy_functions.html#phoenix.starter_kit.lazy_functions.predefined_lazy_functions">Predefined
Lazy Functions</a>
</h5>
Modified: sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/starter_kit/lazy_operators.html
==============================================================================
--- sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/starter_kit/lazy_operators.html (original)
+++ sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/starter_kit/lazy_operators.html 2011-03-03 15:18:12 EST (Thu, 03 Mar 2011)
@@ -69,7 +69,7 @@
</p>
</div>
<a name="phoenix.starter_kit.lazy_operators.first_practical_example"></a><h5>
-<a name="id715747"></a>
+<a name="id667960"></a>
<a class="link" href="lazy_operators.html#phoenix.starter_kit.lazy_operators.first_practical_example">First
Practical Example</a>
</h5>
Modified: sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/starter_kit/values.html
==============================================================================
--- sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/starter_kit/values.html (original)
+++ sandbox/SOC/2010/phoenix3/libs/phoenix/doc/html/phoenix/starter_kit/values.html 2011-03-03 15:18:12 EST (Thu, 03 Mar 2011)
@@ -32,7 +32,7 @@
World"</span></code>.
</p>
<a name="phoenix.starter_kit.values.lazy_evaluation"></a><h5>
-<a name="id714183"></a>
+<a name="id666396"></a>
<a class="link" href="values.html#phoenix.starter_kit.values.lazy_evaluation">Lazy Evaluation</a>
</h5>
<p>
@@ -64,7 +64,7 @@
anything and defers the evaluation for later.
</p>
<a name="phoenix.starter_kit.values.callbacks"></a><h5>
-<a name="id714408"></a>
+<a name="id666621"></a>
<a class="link" href="values.html#phoenix.starter_kit.values.callbacks">Callbacks</a>
</h5>
<p>
Modified: sandbox/SOC/2010/phoenix3/libs/phoenix/doc/inside.qbk
==============================================================================
--- sandbox/SOC/2010/phoenix3/libs/phoenix/doc/inside.qbk (original)
+++ sandbox/SOC/2010/phoenix3/libs/phoenix/doc/inside.qbk 2011-03-03 15:18:12 EST (Thu, 03 Mar 2011)
@@ -11,7 +11,7 @@
This chapter explains in more detail how the library operates. The information
henceforth should not be necessary to those who are interested in just using the
-library. However, a microscopic view might prove to be beneficial to moderate
+library. However, a microscopic view might prove to be beneficial
to advanced programmers who wish to extend the library.
[include inside/actor.qbk]
Modified: sandbox/SOC/2010/phoenix3/libs/phoenix/doc/inside/actions.qbk
==============================================================================
--- sandbox/SOC/2010/phoenix3/libs/phoenix/doc/inside/actions.qbk (original)
+++ sandbox/SOC/2010/phoenix3/libs/phoenix/doc/inside/actions.qbk 2011-03-03 15:18:12 EST (Thu, 03 Mar 2011)
@@ -75,7 +75,7 @@
[*But there is more:] As Actions /can/ be full fletched __proto_transforms__, you can
in fact use any proto expression you can imagine as the action. Phoenix predifines a
set of callables and transform to deal with the Context information passed along and
-of course every phoenix expression can be used as a phoenix grammar or
+of course every Phoenix expression can be used as a Phoenix grammar or
__proto_pass_through_transform__.
[variablelist
Modified: sandbox/SOC/2010/phoenix3/libs/phoenix/doc/inside/actor.qbk
==============================================================================
--- sandbox/SOC/2010/phoenix3/libs/phoenix/doc/inside/actor.qbk (original)
+++ sandbox/SOC/2010/phoenix3/libs/phoenix/doc/inside/actor.qbk 2011-03-03 15:18:12 EST (Thu, 03 Mar 2011)
@@ -132,7 +132,7 @@
[heading Actions]
Actions is the part of Phoenix which are responsible for giving the actual expressions
-a specific behaviour. During the traversal of the Phoenix Expression Tree theses actions
+a specific behaviour. During the traversal of the Phoenix Expression Tree these actions
are called whenever a specified rule in the grammar matches.
struct actions
@@ -142,7 +142,7 @@
};
The nested `when` template is required to be __proto_primitive_transform__. No
-Worries, you don't have to learn __proto__ just yet! Phoenix provides some wrappers
+worries, you don't have to learn __proto__ just yet! Phoenix provides some wrappers
to let you define simple actions without the need to dive deep into proto.
Phoenix ships with a predefined `default_actions` class that evaluates the expressions with
@@ -156,7 +156,7 @@
{};
};
-For more Information on how to use the default_actions class and how to attach custom actions
+For more information on how to use the default_actions class and how to attach custom actions
to the evaluation process, see [link phoenix.inside.actions more on actions].
[heading Evaluation]
@@ -172,7 +172,7 @@
The evaluation of a Phoenix expression is started by a call to the function call operator of
`evaluator`.
-The evaluator is called by the `actor` functio operator overloads after the context is built up.
+The evaluator is called by the `actor` function operator overloads after the context is built up.
For reference, here is a typical `actor::operator()` that accepts two arguments:
template <typename T0, typename T1>
@@ -188,7 +188,7 @@
For reasons of symmetry to the family of `actor::operator()` there is a special
metafunction usable for actor result type calculation named `result_of::actor`. This
-metafunction allows us to directly to specify the types of the parameters to be
+metafunction allows us to directly specify the types of the parameters to be
passed to the `actor::operator()` function. Here's a typical `actor_result` that
accepts two arguments:
Modified: sandbox/SOC/2010/phoenix3/libs/phoenix/doc/inside/custom_terminal.qbk
==============================================================================
--- sandbox/SOC/2010/phoenix3/libs/phoenix/doc/inside/custom_terminal.qbk (original)
+++ sandbox/SOC/2010/phoenix3/libs/phoenix/doc/inside/custom_terminal.qbk 2011-03-03 15:18:12 EST (Thu, 03 Mar 2011)
@@ -9,16 +9,16 @@
[section Custom Terminals]
-Custom Terminals are used in phoenix to handle special values transparently.
-For example, as phoenix captures everything by value, we needed to use
-`boost::reference_wrapper` to bring in reference semantics into phoenix.
+Custom Terminals are used in Phoenix to handle special values transparently.
+For example, as Phoenix captures everything by value, we needed to use
+`boost::reference_wrapper` to bring reference semantics into Phoenix.
Custom terminals could be any wrapper class:
template <typename T>
struct is_custom_terminal;
-needs to be specialized in order for phoenix to recognize this wrapper type.
+needs to be specialized in order for Phoenix to recognize this wrapper type.
`default_action` calls `custom_terminal<T>`.
Example:
Modified: sandbox/SOC/2010/phoenix3/libs/phoenix/doc/inside/expression.qbk
==============================================================================
--- sandbox/SOC/2010/phoenix3/libs/phoenix/doc/inside/expression.qbk (original)
+++ sandbox/SOC/2010/phoenix3/libs/phoenix/doc/inside/expression.qbk 2011-03-03 15:18:12 EST (Thu, 03 Mar 2011)
@@ -12,11 +12,10 @@
A Phoenix Expression is a model of the __proto_expr__ Concept. These expressions
are wrapped inside an [link phoenix.inside.actor Actor] template. The `actor` provides
the function call operator which evaluates the expressions.
-The `actor` is the domain specific wrapper around phoenix expressions.
+The `actor` is the domain specific wrapper around Phoenix expressions.
By design, Phoenix Expressions do not carry any information on how they will be
-evaluated later on. They are the data structure on which the `Actions` will work
-on.
+evaluated later on. They are the data structure on which the `Actions` will work.
The library provides a convenience template to define expressions:
@@ -59,8 +58,8 @@
[heading meta_grammar]
-Defining Expressions is only part of the game to make it a valid Phoenix Expression.
-In order to use the expressions in the Phoenix domain, we need to "register" our newly created
+Defining expressions is only part of the game to make it a valid Phoenix Expression.
+In order to use the expressions in the Phoenix domain, we need to "register" them
to our grammar.
The `meta_grammar` is a struct for exactly that purpose. It is an openly extendable __proto__ Grammar:
@@ -107,7 +106,7 @@
return expression::plus<Lhs, Rhs>::make(lhs, rhs);
}
-Look of it really works:
+Look if it really works:
plus(6, 5)();
@@ -125,11 +124,11 @@
See [@../../example/define_expression.cpp define_expression.cpp] for the full example.
[note
- The example shown here only works because `default_actions` know how to handle
+ The example shown here only works because `default_actions` knows how to handle
an expression having the `proto::tag::plus` and two children. This is because
`default_actions` uses the `proto::_default<meta_grammar>` transform to
evaluate operators and functions. Learn more about actions
- [link phoenix.inside.actions here]
+ [link phoenix.inside.actions here].
]
[/section Boilerplate Macros]
@@ -138,7 +137,7 @@
repetetive task. Phoenix provides boilerplate macros that make defining Phoenix
Expressions as you have seen in the
[link phoenix.inside.expression previous section] look like a piece of cake.
-]
+
[/
These expressions generate the following:
Modified: sandbox/SOC/2010/phoenix3/libs/phoenix/doc/inside/placeholder.qbk
==============================================================================
--- sandbox/SOC/2010/phoenix3/libs/phoenix/doc/inside/placeholder.qbk (original)
+++ sandbox/SOC/2010/phoenix3/libs/phoenix/doc/inside/placeholder.qbk 2011-03-03 15:18:12 EST (Thu, 03 Mar 2011)
@@ -19,6 +19,6 @@
};
To adapt your own placeholder, the nested value needs to be greater than 0
-for your types. This is done with specializing this trait.
+for your types. This is done by specializing this trait.
[endsect]
Modified: sandbox/SOC/2010/phoenix3/libs/phoenix/doc/modules/core.qbk
==============================================================================
--- sandbox/SOC/2010/phoenix3/libs/phoenix/doc/modules/core.qbk (original)
+++ sandbox/SOC/2010/phoenix3/libs/phoenix/doc/modules/core.qbk 2011-03-03 15:18:12 EST (Thu, 03 Mar 2011)
@@ -67,7 +67,7 @@
In C++, we can pass in a reference to a variable as the first argument in our
example above. Yet, by default, the library forces arguments passed to partially
-applied functions functions to be immutable values (see [link phoenix.modules.core.values
+applied functions to be immutable values (see [link phoenix.modules.core.values
Values]). To achieve our intent, we use:
expression::reference<T>::type
@@ -229,7 +229,7 @@
#include <boost/phoenix/core/nothing.hpp>
-Finally, the `expression::null<mpl::void_>::type` does nothing; (a "bum", if you will :-).
+Finally, the `expression::null<mpl::void_>::type` does nothing; (a "bum", if you will :-) ).
There's a sole `expression::null<mpl::void_>::type` instance named "nothing". This actor is
actually useful in situations where we don't want to do anything. (See
[link phoenix.modules.statement.for_statement for_ Statement] for example).
Added: sandbox/SOC/2010/phoenix3/libs/phoenix/example/factorial.cpp
==============================================================================
--- (empty file)
+++ sandbox/SOC/2010/phoenix3/libs/phoenix/example/factorial.cpp 2011-03-03 15:18:12 EST (Thu, 03 Mar 2011)
@@ -0,0 +1,45 @@
+/*=============================================================================
+ Copyright (c) 2001-2003 Joel de Guzman
+
+ 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)
+==============================================================================*/
+#include <vector>
+#include <algorithm>
+#include <iostream>
+#include <boost/phoenix/core.hpp>
+#include <boost/phoenix/function.hpp>
+
+struct factorial_impl
+{
+ template <typename Sig>
+ struct result;
+
+ template <typename Arg>
+ struct result<This(Arg)>
+ : result<This(Arg const &)>
+ {};
+
+ template <typename Arg>
+ struct result<This(Arg &)>
+ {
+ typedef Arg type;
+ };
+
+ template <typename Arg>
+ Arg operator()(Arg n) const
+ {
+ return (n <= 0) ? 1 : n * this->operator()(n-1);
+ }
+};
+
+
+int
+main()
+{
+ boost::phoenix::function<factorial_impl> factorial;
+ using namespace boost::phoenix::arg_names::arg1;
+ int i = 4;
+ std::cout << factorial(arg1)(i) << std::endl;
+ return 0;
+}
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