Boost-Commit :

Date view	Thread view	Subject view	Author view

Subject: [Boost-commit] svn:boost r64168 - in trunk/libs/spirit: phoenix/doc/html phoenix/doc/html/phoenix repository/doc/html repository/doc/html/spirit_repository repository/doc/html/spirit_repository/karma_components repository/doc/html/spirit_repository/karma_components/directives repository/doc/html/spirit_repository/karma_components/nonterminal repository/doc/html/spirit_repository/qi_components repository/doc/html/spirit_repository/qi_components/directives repository/doc/html/spirit_repository/qi_components/nonterminal repository/doc/html/spirit_repository/qi_components/primitive
From: daniel_james_at_[hidden]
Date: 2010-07-19 16:15:57

Author: danieljames
Date: 2010-07-19 16:15:52 EDT (Mon, 19 Jul 2010)
New Revision: 64168
URL: http://svn.boost.org/trac/boost/changeset/64168

Log:
Rebuild spirit documentation for phoenix + repository.
Text files modified:
   trunk/libs/spirit/phoenix/doc/html/index.html | 205 +++---
   trunk/libs/spirit/phoenix/doc/html/phoenix/acknowledgement.html | 117 +-
   trunk/libs/spirit/phoenix/doc/html/phoenix/actors.html | 52
   trunk/libs/spirit/phoenix/doc/html/phoenix/algorithm.html | 1221 ++++++++++++++++++++-------------------
   trunk/libs/spirit/phoenix/doc/html/phoenix/basics.html | 178 ++---
   trunk/libs/spirit/phoenix/doc/html/phoenix/composite.html | 1095 ++++++++++++++++-------------------
   trunk/libs/spirit/phoenix/doc/html/phoenix/container.html | 734 ++++++++++++-----------
   trunk/libs/spirit/phoenix/doc/html/phoenix/inside_phoenix.html | 768 ++++++++++++------------
   trunk/libs/spirit/phoenix/doc/html/phoenix/introduction.html | 25
   trunk/libs/spirit/phoenix/doc/html/phoenix/organization.html | 384 ++++++------
   trunk/libs/spirit/phoenix/doc/html/phoenix/primitives.html | 259 +++----
   trunk/libs/spirit/phoenix/doc/html/phoenix/references.html | 117 +-
   trunk/libs/spirit/phoenix/doc/html/phoenix/starter_kit.html | 385 ++++++------
   trunk/libs/spirit/phoenix/doc/html/phoenix/wrap_up.html | 47
   trunk/libs/spirit/repository/doc/html/index.html | 18
   trunk/libs/spirit/repository/doc/html/spirit_repository/karma_components.html | 12
   trunk/libs/spirit/repository/doc/html/spirit_repository/karma_components/directives.html | 12
   trunk/libs/spirit/repository/doc/html/spirit_repository/karma_components/directives/karma_confix_generator.html | 122 +--
   trunk/libs/spirit/repository/doc/html/spirit_repository/karma_components/nonterminal.html | 12
   trunk/libs/spirit/repository/doc/html/spirit_repository/karma_components/nonterminal/subrule.html | 286 ++++----
   trunk/libs/spirit/repository/doc/html/spirit_repository/preface.html | 189 +++---
   trunk/libs/spirit/repository/doc/html/spirit_repository/qi_components.html | 12
   trunk/libs/spirit/repository/doc/html/spirit_repository/qi_components/directives.html | 12
   trunk/libs/spirit/repository/doc/html/spirit_repository/qi_components/directives/confix.html | 116 +--
   trunk/libs/spirit/repository/doc/html/spirit_repository/qi_components/directives/distinct.html | 104 +--
   trunk/libs/spirit/repository/doc/html/spirit_repository/qi_components/nonterminal.html | 12
   trunk/libs/spirit/repository/doc/html/spirit_repository/qi_components/nonterminal/subrule.html | 717 +++++++++++-----------
   trunk/libs/spirit/repository/doc/html/spirit_repository/qi_components/primitive.html | 12
   trunk/libs/spirit/repository/doc/html/spirit_repository/qi_components/primitive/flush_multi_pass.html | 48
   29 files changed, 3559 insertions(+), 3712 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-07-19 16:15:52 EDT (Mon, 19 Jul 2010)
@@ -1,37 +1,37 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title>Chapter 1. Phoenix 2.0</title>
-<link rel="stylesheet" href="../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.66.1">
-<link rel="start" href="index.html" title="Chapter 1. Phoenix 2.0">
+<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">
+<link rel="home" href="index.html" title="Chapter 1. Phoenix 2.0">
<link rel="next" href="phoenix/introduction.html" title="Introduction">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
<table cellpadding="2" width="100%"><tr>
<td valign="top"><img alt="Boost C++ Libraries" width="277" height="86" src="../../../../../boost.png"></td>
<td align="center">Home</td>
-<td align="center">Libraries</td>
+<td align="center">Libraries</td>
<td align="center">People</td>
<td align="center">FAQ</td>
<td align="center">More</td>
</tr></table>
<hr>
-<div class="spirit-nav"><a accesskey="n" href="phoenix/introduction.html"><img src="../../../../../doc/html/images/next.png" alt="Next"></a></div>
-<div class="chapter" lang="en">
+<div class="spirit-nav"><a accesskey="n" href="phoenix/introduction.html"><img src="../../../../../doc/src/images/next.png" alt="Next"></a></div>
+<div class="chapter">
<div class="titlepage"><div>
<div><h2 class="title">
-<a name="phoenix"></a>Chapter 1. Phoenix 2.0</h2></div>
+<a name="phoenix"></a>Chapter 1. Phoenix 2.0</h2></div>
<div><div class="author"><h3 class="author">
Joel de Guzman
</h3></div></div>
<div><div class="author"><h3 class="author">
Dan Marsden
</h3></div></div>
-<div>Copyright © 2002-2005 Joel
+<div>Copyright © 2002-2005 Joel
 de Guzman, Dan Marsden</div>
<div><div class="legalnotice">
-<a name="id385274"></a>
+<a name="id759708"></a>
 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)
 
@@ -91,40 +91,29 @@
<dt>References</dt>
</dl>
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="phoenix.preface"></a>Preface</h2></div></div></div>
-<div class="blockquote"><blockquote class="blockquote">
-
- 
-
- Functional programming is so called because a program consists
- entirely of functions. The main program itself is written as a function
- which receives the program's input as its argument and delivers the program's
- output as its result. Typically the main function is defined in terms of
- other functions, which in turn are defined in terms of still more functions
- until at the bottom level the functions are language primitives.
- 
-
- 
-</blockquote></div>
-<div class="blockquote"><blockquote class="blockquote">
-
- 
-
- John Hughes-- Why Functional
- Programming Matters
- 
-
- 
-</blockquote></div>
+<a name="phoenix.preface"></a><a class="link" href="index.html#phoenix.preface" title="Preface">Preface</a>
+</h2></div></div></div>
+<div class="blockquote"><blockquote class="blockquote">
+ Functional programming is so called because a program consists
+ entirely of functions. The main program itself is written as a function which
+ receives the program's input as its argument and delivers the program's output
+ as its result. Typically the main function is defined in terms of other functions,
+ which in turn are defined in terms of still more functions until at the bottom
+ level the functions are language primitives.
+ </blockquote></div>
+<div class="blockquote"><blockquote class="blockquote">
+ John Hughes-- Why Functional Programming
+ Matters
+ </blockquote></div>

 <img src="images/lambda_cpp.png" alt="lambda_cpp">
 
-<a name="phoenix.preface.description"></a><h2>
-<a name="id385804"></a>
- Description
- </h2>
+<a name="phoenix.preface.description"></a><h3>
+<a name="id759789"></a>
+ <a class="link" href="index.html#phoenix.preface.description">Description</a>
+ </h3>

 Phoenix enables Functional Programming (FP) in C++. The design and implementation
 of Phoenix is highly influenced by FC++
@@ -141,10 +130,10 @@
 the library into small pieces, without fear that the pieces won't work anymore.
 The library is organized in highly independent modules and layers.
 
-<a name="phoenix.preface.how_to_use_this_manual"></a><h2>
-<a name="id455895"></a>
- How to use this manual
- </h2>
+<a name="phoenix.preface.how_to_use_this_manual"></a><h3>
+<a name="id759849"></a>
+ <a class="link" href="index.html#phoenix.preface.how_to_use_this_manual">How to use this manual</a>
+ </h3>

 The Phoenix library is organized in logical modules. This documentation provides
 a user's guide and reference for each module in the library. A simple and clear
@@ -165,8 +154,8 @@
 icons precede some text to indicate:
 
<div class="table">
-<a name="id455925"></a>Table 1.1. Icons
-<table class="table" summary="Icons">
+<a name="id759887"></a>Table 1.1. Icons
+<div class="table-contents"><table class="table" summary="Icons">
<colgroup>
<col>
<col>
@@ -174,86 +163,86 @@
</colgroup>
<thead><tr>
<th>
- 
- Icon
- 
- </th>
+ 
+ Icon
+ 
+ </th>
<th>
- 
- Name
- 
- </th>
+ 
+ Name
+ 
+ </th>
<th>
- 
- Meaning
- 
- </th>
+ 
+ Meaning
+ 
+ </th>
</tr></thead>
<tbody>
<tr>
<td>
- 
- <img src="images/note.png" alt="note">
- 
- </td>
+ 
+ <img src="images/note.png" alt="note">
+ 
+ </td>
<td>
- 
- Note
- 
- </td>
+ 
+ Note
+ 
+ </td>
<td>
- 
- Information provided is auxiliary but will give the reader a deeper insight
- into a specific topic. May be skipped.
- 
- </td>
+ 
+ Information provided is auxiliary but will give the reader a deeper
+ insight into a specific topic. May be skipped.
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <img src="images/alert.png" alt="alert">
- 
- </td>
+ 
+ <img src="images/alert.png" alt="alert">
+ 
+ </td>
<td>
- 
- Alert
- 
- </td>
+ 
+ Alert
+ 
+ </td>
<td>
- 
- Information provided is of utmost importance.
- 
- </td>
+ 
+ Information provided is of utmost importance.
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <img src="images/tip.png" alt="tip">
- 
- </td>
+ 
+ <img src="images/tip.png" alt="tip">
+ 
+ </td>
<td>
- 
- Tip
- 
- </td>
+ 
+ Tip
+ 
+ </td>
<td>
- 
- A potentially useful and helpful piece of information.
- 
- </td>
+ 
+ A potentially useful and helpful piece of information.
+ 
+ </td>
</tr>
</tbody>
-</table>
+</table></div>
</div>
-
+ 
 This documentation is automatically generated by Spirit QuickBook documentation
 tool. QuickBook can be found in the <a href="http://spirit.sourceforge.net/repository/applications/show_contents.php" target="_top">Spirit
 Repository</a>.
 
-<a name="phoenix.preface.support"></a><h2>
-<a name="id387296"></a>
- Support
- </h2>
+<a name="phoenix.preface.support"></a><h3>
+<a name="id760065"></a>
+ <a class="link" href="index.html#phoenix.preface.support">Support</a>
+ </h3>

 Please direct all questions to Spirit's mailing list. You can subscribe to
 the <a href="https://lists.sourceforge.net/lists/listinfo/spirit-general" target="_top">Spirit
@@ -264,17 +253,17 @@
 NNTP news portal</a> (thanks to Gmane).
 The news group mirrors the mailing list. Here is a link to the archives: http://news.gmane.org/gmane.comp.parsers.spirit.general.
 
-<a name="phoenix.preface._emphasis_role__bold___emphasis____to_my_dear_daughter__phoenix__emphasis___emphasis_"></a><h2>
-<a name="id387363"></a>
- ...To my dear daughter, Phoenix
- </h2>
+<a name="phoenix.preface._emphasis_role__bold___emphasis____to_my_dear_daughter__phoenix__emphasis___emphasis_"></a><h3>
+<a name="id760124"></a>
+ <a class="link" href="index.html#phoenix.preface._emphasis_role__bold___emphasis____to_my_dear_daughter__phoenix__emphasis___emphasis_">...To my dear daughter, Phoenix</a>
+ </h3>
</div>
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
-<td align="left">Last revised: July 23, 2008 at 17:24:10 GMT</td>
+<td align="left">Last revised: July 19, 2010 at 19:06:12 GMT</td>
<td align="right"><div class="copyright-footer"></div></td>
</tr></table>
<hr>
-<div class="spirit-nav"><a accesskey="n" href="phoenix/introduction.html"><img src="../../../../../doc/html/images/next.png" alt="Next"></a></div>
+<div class="spirit-nav"><a accesskey="n" href="phoenix/introduction.html"><img src="../../../../../doc/src/images/next.png" alt="Next"></a></div>
</body>
</html>

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-07-19 16:15:52 EDT (Mon, 19 Jul 2010)
@@ -1,11 +1,11 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Acknowledgement</title>
-<link rel="stylesheet" href="../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.66.1">
-<link rel="start" href="../index.html" title="Chapter 1. Phoenix 2.0">
-<link rel="up" href="../index.html" title="Chapter 1. Phoenix 2.0">
+<link rel="stylesheet" href="../../../../../../doc/src/boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
+<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">
<link rel="next" href="references.html" title="References">
</head>
@@ -13,70 +13,71 @@
<table cellpadding="2" width="100%"><tr>
<td valign="top"><img alt="Boost C++ Libraries" width="277" height="86" src="../../../../../../boost.png"></td>
<td align="center">Home</td>
-<td align="center">Libraries</td>
+<td align="center">Libraries</td>
<td align="center">People</td>
<td align="center">FAQ</td>
<td align="center">More</td>
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="wrap_up.html"><img src="../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="references.html"><img src="../../../../../../doc/html/images/next.png" alt="Next"></a>
+<a accesskey="p" href="wrap_up.html"><img src="../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="references.html"><img src="../../../../../../doc/src/images/next.png" alt="Next"></a>
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="phoenix.acknowledgement"></a>Acknowledgement</h2></div></div></div>
-<div class="orderedlist"><ol type="1">
-<li>
- Hartmut Kaiser implemented the original lazy casts and constructors based
- on his original work on Spirit SE "semantic expressions" (the precursor
- to Phoenix).
- </li>
-<li>
- Angus Leeming implemented the container functions on Phoenix-1 which I then
- ported to Phoenix-2.
- </li>
-<li>
- Daniel Wallin helped with the scope module, local variables, let and lambda
- and the algorithms. I frequently discuss design issues with Daniel on Yahoo
- Messenger.
- </li>
-<li>
- Jaakko Jarvi. DA Lambda MAN!
- </li>
-<li>
- Dave Abrahams, for his constant presence, wherever, whenever.
- </li>
-<li>
- Aleksey Gurtovoy, DA MPL MAN!
- </li>
-<li>
- Doug Gregor, always a source of inpiration.
- </li>
-<li>
- Dan Marsden, did almost all the work in bringing Phoenix-2 out the door.
- </li>
-<li>
- Eric Niebler did a 2.0 pre-release review and wrote some range related code
- that Phoenix stole and used in the algorithms.
- </li>
-<li>
- Thorsten Ottosen; Eric's range_ex code began life as "container_algo"
- in the old boost sandbox, by Thorsten in 2002-2003.
- </li>
-<li>
- Jeremy Siek, even prior to Thorsten, in 2001, started the "container_algo".
- </li>
-<li>
- Vladimir Prus wrote the mutating algorithms code from the Boost Wiki.
- </li>
-<li>
- Daryle Walker did a 2.0 pre-release review.
- </li>
+<a name="phoenix.acknowledgement"></a><a class="link" href="acknowledgement.html" title="Acknowledgement">Acknowledgement</a>
+</h2></div></div></div>
+<div class="orderedlist"><ol class="orderedlist" type="1">
+<li class="listitem">
+ Hartmut Kaiser implemented the original lazy casts and constructors based
+ on his original work on Spirit SE "semantic expressions" (the
+ precursor to Phoenix).
+ </li>
+<li class="listitem">
+ Angus Leeming implemented the container functions on Phoenix-1 which I
+ then ported to Phoenix-2.
+ </li>
+<li class="listitem">
+ Daniel Wallin helped with the scope module, local variables, let and lambda
+ and the algorithms. I frequently discuss design issues with Daniel on Yahoo
+ Messenger.
+ </li>
+<li class="listitem">
+ Jaakko Jarvi. DA Lambda MAN!
+ </li>
+<li class="listitem">
+ Dave Abrahams, for his constant presence, wherever, whenever.
+ </li>
+<li class="listitem">
+ Aleksey Gurtovoy, DA MPL MAN!
+ </li>
+<li class="listitem">
+ Doug Gregor, always a source of inpiration.
+ </li>
+<li class="listitem">
+ Dan Marsden, did almost all the work in bringing Phoenix-2 out the door.
+ </li>
+<li class="listitem">
+ Eric Niebler did a 2.0 pre-release review and wrote some range related
+ code that Phoenix stole and used in the algorithms.
+ </li>
+<li class="listitem">
+ Thorsten Ottosen; Eric's range_ex code began life as "container_algo"
+ in the old boost sandbox, by Thorsten in 2002-2003.
+ </li>
+<li class="listitem">
+ Jeremy Siek, even prior to Thorsten, in 2001, started the "container_algo".
+ </li>
+<li class="listitem">
+ Vladimir Prus wrote the mutating algorithms code from the Boost Wiki.
+ </li>
+<li class="listitem">
+ Daryle Walker did a 2.0 pre-release review.
+ </li>
</ol></div>
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2002-2005 Joel
+<td align="right"><div class="copyright-footer">Copyright © 2002-2005 Joel
 de Guzman, Dan Marsden
 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)
@@ -85,7 +86,7 @@
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="wrap_up.html"><img src="../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="references.html"><img src="../../../../../../doc/html/images/next.png" alt="Next"></a>
+<a accesskey="p" href="wrap_up.html"><img src="../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="references.html"><img src="../../../../../../doc/src/images/next.png" alt="Next"></a>
</div>
</body>
</html>

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-07-19 16:15:52 EDT (Mon, 19 Jul 2010)
@@ -1,11 +1,11 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Actors</title>
-<link rel="stylesheet" href="../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.66.1">
-<link rel="start" href="../index.html" title="Chapter 1. Phoenix 2.0">
-<link rel="up" href="../index.html" title="Chapter 1. Phoenix 2.0">
+<link rel="stylesheet" href="../../../../../../doc/src/boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
+<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">
<link rel="next" href="primitives.html" title="Primitives">
</head>
@@ -13,42 +13,42 @@
<table cellpadding="2" width="100%"><tr>
<td valign="top"><img alt="Boost C++ Libraries" width="277" height="86" src="../../../../../../boost.png"></td>
<td align="center">Home</td>
-<td align="center">Libraries</td>
+<td align="center">Libraries</td>
<td align="center">People</td>
<td align="center">FAQ</td>
<td align="center">More</td>
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="organization.html"><img src="../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="primitives.html"><img src="../../../../../../doc/html/images/next.png" alt="Next"></a>
+<a accesskey="p" href="organization.html"><img src="../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="primitives.html"><img src="../../../../../../doc/src/images/next.png" alt="Next"></a>
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="phoenix.actors"></a>Actors</h2></div></div></div>
+<a name="phoenix.actors"></a><a class="link" href="actors.html" title="Actors">Actors</a>
+</h2></div></div></div>

- The <tt class="computeroutput">Actor</tt> is the main concept
+ The <code class="computeroutput">Actor</code> is the main concept
 behind the library. Actors are function objects. An actor can accept 0 to
- <tt class="computeroutput">PHOENIX_LIMIT</tt> arguments.
+ <code class="computeroutput">PHOENIX_LIMIT</code> arguments.
 
<div class="note"><table border="0" summary="Note">
<tr>
-<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../../../../../../doc/html/images/note.png"></td>
+<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../../../../../../doc/src/images/note.png"></td>
<th align="left">Note</th>
</tr>
-<tr><td colspan="2" align="left" valign="top">
- You can set <tt class="computeroutput">PHOENIX_LIMIT</tt>,
- the predefined maximum arity an actor can take. By default, <tt class="computeroutput">PHOENIX_LIMIT</tt> is set to 10.
+<tr><td align="left" valign="top">
+ You can set <code class="computeroutput">PHOENIX_LIMIT</code>,
+ the predefined maximum arity an actor can take. By default, <code class="computeroutput">PHOENIX_LIMIT</code> is set to 10.
 </td></tr>
</table></div>

- Phoenix supplies an <tt class="computeroutput">actor</tt> class
- template whose specializations model the <tt class="computeroutput">Actor</tt>
- concept. <tt class="computeroutput">actor</tt> has one template
- parameter, <tt class="computeroutput">Eval</tt>, that supplies
+ Phoenix supplies an <code class="computeroutput">actor</code> class
+ template whose specializations model the <code class="computeroutput">Actor</code>
+ concept. <code class="computeroutput">actor</code> has one template
+ parameter, <code class="computeroutput">Eval</code>, that supplies
 the smarts to evaluate the resulting function.
 
-<pre class="programlisting">
-template <typename Eval>
+<pre class="programlisting">template <typename Eval>
struct actor : Eval
{
 return_type
@@ -67,16 +67,16 @@
</pre>

 The actor class accepts the arguments through a set of function call operators
- for 0 to <tt class="computeroutput">PHOENIX_LIMIT</tt> arities
+ for 0 to <code class="computeroutput">PHOENIX_LIMIT</code> arities
 (Don't worry about the details, for now. Note, for example, that we skimp over
- the details regarding <tt class="computeroutput">return_type</tt>).
- The arguments are then forwarded to the actor's <tt class="computeroutput">Eval</tt>
+ the details regarding <code class="computeroutput">return_type</code>).
+ The arguments are then forwarded to the actor's <code class="computeroutput">Eval</code>
 for evaluation.
 
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2002-2005 Joel
+<td align="right"><div class="copyright-footer">Copyright © 2002-2005 Joel
 de Guzman, Dan Marsden
 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)
@@ -85,7 +85,7 @@
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="organization.html"><img src="../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="primitives.html"><img src="../../../../../../doc/html/images/next.png" alt="Next"></a>
+<a accesskey="p" href="organization.html"><img src="../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="primitives.html"><img src="../../../../../../doc/src/images/next.png" alt="Next"></a>
</div>
</body>
</html>

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-07-19 16:15:52 EDT (Mon, 19 Jul 2010)
@@ -1,11 +1,11 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Algorithm</title>
-<link rel="stylesheet" href="../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.66.1">
-<link rel="start" href="../index.html" title="Chapter 1. Phoenix 2.0">
-<link rel="up" href="../index.html" title="Chapter 1. Phoenix 2.0">
+<link rel="stylesheet" href="../../../../../../doc/src/boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
+<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">
<link rel="next" href="inside_phoenix.html" title="Inside Phoenix">
</head>
@@ -13,24 +13,24 @@
<table cellpadding="2" width="100%"><tr>
<td valign="top"><img alt="Boost C++ Libraries" width="277" height="86" src="../../../../../../boost.png"></td>
<td align="center">Home</td>
-<td align="center">Libraries</td>
+<td align="center">Libraries</td>
<td align="center">People</td>
<td align="center">FAQ</td>
<td align="center">More</td>
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="container.html"><img src="../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="inside_phoenix.html"><img src="../../../../../../doc/html/images/next.png" alt="Next"></a>
+<a accesskey="p" href="container.html"><img src="../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="inside_phoenix.html"><img src="../../../../../../doc/src/images/next.png" alt="Next"></a>
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="phoenix.algorithm"></a>Algorithm</h2></div></div></div>
-<pre class="programlisting">
-#include <boost/spirit/home/phoenix/algorithm.hpp>
+<a name="phoenix.algorithm"></a><a class="link" href="algorithm.html" title="Algorithm">Algorithm</a>
+</h2></div></div></div>
+<pre class="programlisting">#include <boost/spirit/home/phoenix/algorithm.hpp>
</pre>

 The algorithm module provides wrappers for the standard algorithms in the
- <tt class="computeroutput"><algorithm></tt> and <tt class="computeroutput"><numeric></tt>
+ <code class="computeroutput"><algorithm></code> and <code class="computeroutput"><numeric></code>
 headers.
 

@@ -38,8 +38,7 @@
 querying, modelling the Boost.MPL
 library. The different algorithm classes can be included using the headers:
 
-<pre class="programlisting">
-#include <boost/spirit/home/phoenix/stl/algorithm/iteration.hpp>
+<pre class="programlisting">#include <boost/spirit/home/phoenix/stl/algorithm/iteration.hpp>
#include <boost/spirit/home/phoenix/stl/algorithm/transformation.hpp>
#include <boost/spirit/home/phoenix/stl/algorithm/querying.hpp>
</pre>
@@ -52,8 +51,7 @@

 For example, using the standard copy algorithm to copy between 2 arrays:
 
-<pre class="programlisting">
-int array[] = {1, 2, 3};
+<pre class="programlisting">int array[] = {1, 2, 3};
int output[3];
std::copy(array, array + 3, output); // We have to provide iterators
 // to both the start and end of array
@@ -61,8 +59,7 @@

 The analogous code using the phoenix algorithm module is:
 
-<pre class="programlisting">
-int array[] = {1, 2, 3};
+<pre class="programlisting">int array[] = {1, 2, 3};
int output[3];
copy(arg1, arg2)(array, output); // Notice only 2 arguments, the end of
 // array is established automatically
@@ -76,874 +73,924 @@
 The following tables describe the different categories of algorithms, and their
 semantics.
 
-<div class="sidebar">
+<div class="sidebar">
+
+
 <img src="../images/tip.png" alt="tip"> Arguments in brackets denote optional parameters.
- </div>
+ 
+</div>
<div class="table">
-<a name="id486434"></a>Table 1.7. Iteration Algorithms
-<table class="table" summary="Iteration Algorithms">
+<a name="id786989"></a>Table 1.7. Iteration Algorithms
+<div class="table-contents"><table class="table" summary="Iteration Algorithms">
<colgroup>
<col>
<col>
</colgroup>
<thead><tr>
<th>
- 
- Function
- 
- </th>
+ 
+ Function
+ 
+ </th>
<th>
- 
- stl Semantics
- 
- </th>
+ 
+ stl Semantics
+ 
+ </th>
</tr></thead>
<tbody>
<tr>
<td>
- 
- <tt class="computeroutput">for_each(r, c)</tt>
- 
- </td>
-<td>
- 
- <tt class="computeroutput">for_each(begin(r), end(r), f)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">for_each(r, c)</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">for_each(begin(r), end(r), f)</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">accumulate(r, o[, f])</tt>
- 
- </td>
-<td>
- 
- <tt class="computeroutput">accumulate(begin(r), end(r), o[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">accumulate(r, o[, f])</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">accumulate(begin(r), end(r), o[, f])</code>
+ 
+ </td>
</tr>
</tbody>
-</table>
+</table></div>
</div>
-<div class="table">
-<a name="id486741"></a>Table 1.8. Querying Algorithms
-<table class="table" summary="Querying Algorithms">
+ <div class="table">
+<a name="id787263"></a>Table 1.8. Querying Algorithms
+<div class="table-contents"><table class="table" summary="Querying Algorithms">
<colgroup>
<col>
<col>
</colgroup>
<thead><tr>
<th>
- 
- Function
- 
- </th>
+ 
+ Function
+ 
+ </th>
<th>
- 
- stl Semantics
- 
- </th>
+ 
+ stl Semantics
+ 
+ </th>
</tr></thead>
<tbody>
<tr>
<td>
- 
- <tt class="computeroutput">find(r, a)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">find(r, a)</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">find(begin(r), end(r), a)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">find(begin(r), end(r), a)</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">find_if(r, f)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">find_if(r, f)</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">find_if(begin(r), end(r), f)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">find_if(begin(r), end(r), f)</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">find_end(r1, r2[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">find_end(r1, r2[,
+ f])</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">find_end(begin(r1), end(r1), begin(r2), end(r2)[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">find_end(begin(r1),
+ end(r1),
+ begin(r2),
+ end(r2)[,
+ f])</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">find_first_of(r1, r2[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">find_first_of(r1, r2[,
+ f])</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">find_first_of(begin(r1), end(r1), begin(r2), end(r2)[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">find_first_of(begin(r1),
+ end(r1),
+ begin(r2),
+ end(r2)[,
+ f])</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">adjacent_find(r[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">adjacent_find(r[, f])</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">adjacent_find(begin(r), end(r)[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">adjacent_find(begin(r), end(r)[,
+ f])</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">count(r, a)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">count(r, a)</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">count(begin(r), end(r), a)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">count(begin(r), end(r), a)</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">count_if(r, f)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">count_if(r, f)</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">count_if(begin(r), end(r), f)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">count_if(begin(r), end(r), f)</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">distance(r)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">distance(r)</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">distance(begin(r), end(r))</tt>
- 
- </td>
+ 
+ <code class="computeroutput">distance(begin(r), end(r))</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">mismatch(r, i[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">mismatch(r, i[, f])</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">mismatch(begin(r), end(r), i[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">mismatch(begin(r), end(r), i[, f])</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">equal(r, i[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">equal(r, i[, f])</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">equal(begin(r), end(r), i[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">equal(begin(r), end(r), i[, f])</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">search(r1, r2[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">search(r1, r2[,
+ f])</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">search(begin(r1), end(r1), begin(r2), end(r2)[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">search(begin(r1),
+ end(r1),
+ begin(r2),
+ end(r2)[,
+ f])</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">lower_bound(r, a[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">lower_bound(r, a[, f])</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">lower_bound(begin(r), end(r), a[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">lower_bound(begin(r), end(r), a[, f])</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">upper_bound(r, a[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">upper_bound(r, a[, f])</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">upper_bound(begin(r), end(r), a[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">upper_bound(begin(r), end(r), a[, f])</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">equal_range(r, a[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">equal_range(r, a[, f])</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">equal_range(begin(r), end(r), a[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">equal_range(begin(r), end(r), a[, f])</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">binary_search(r, a[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">binary_search(r, a[, f])</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">binary_search(begin(r), end(r), a[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">binary_search(begin(r), end(r), a[, f])</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">includes(r1, r2[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">includes(r1, r2[,
+ f])</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">includes(begin(r1), end(r1), begin(r2), end(r2)[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">includes(begin(r1),
+ end(r1),
+ begin(r2),
+ end(r2)[,
+ f])</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">min_element(r[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">min_element(r[, f])</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">min_element(begin(r), end(r)[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">min_element(begin(r), end(r)[,
+ f])</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">max_element(r[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">max_element(r[, f])</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">max_element(begin(r), end(r)[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">max_element(begin(r), end(r)[,
+ f])</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">lexicographical_compare(r1, r2[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">lexicographical_compare(r1, r2[, f])</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">lexicographical_compare(begin(r1), end(r1), begin(r2), end(r2)[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">lexicographical_compare(begin(r1), end(r1), begin(r2), end(r2)[, f])</code>
+ 
+ </td>
</tr>
</tbody>
-</table>
+</table></div>
</div>
-<div class="table">
-<a name="id489465"></a>Table 1.9. Transformation Algorithms
-<table class="table" summary="Transformation Algorithms">
+ <div class="table">
+<a name="id789681"></a>Table 1.9. Transformation Algorithms
+<div class="table-contents"><table class="table" summary="Transformation Algorithms">
<colgroup>
<col>
<col>
</colgroup>
<thead><tr>
<th>
- 
- Function
- 
- </th>
+ 
+ Function
+ 
+ </th>
<th>
- 
- stl Semantics
- 
- </th>
+ 
+ stl Semantics
+ 
+ </th>
</tr></thead>
<tbody>
<tr>
<td>
- 
- <tt class="computeroutput">copy(r, o)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">copy(r, o)</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">copy(begin(r), end(r), o)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">copy(begin(r), end(r), o)</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">copy_backward(r, o)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">copy_backward(r, o)</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">copy_backward(begin(r), end(r), o)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">copy_backward(begin(r), end(r), o)</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">transform(r, o, f)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">transform(r, o, f)</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">transform(begin(r), end(r), o, f)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">transform(begin(r), end(r), o, f)</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">transform(r, i, o, f)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">transform(r, i, o, f)</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">transform(begin(r), end(r), i, o, f)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">transform(begin(r), end(r), i, o, f)</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">replace(r, a, b)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">replace(r, a, b)</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">replace(begin(r), end(r), a, b)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">replace(begin(r), end(r), a, b)</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">replace_if(r, f, a)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">replace_if(r, f, a)</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">replace(begin(r), end(r), f, a)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">replace(begin(r), end(r), f, a)</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">replace_copy(r, o, a, b)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">replace_copy(r, o, a, b)</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">replace_copy(begin(r), end(r), o, a, b)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">replace_copy(begin(r), end(r), o, a, b)</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">replace_copy_if(r, o, f, a)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">replace_copy_if(r, o, f, a)</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">replace_copy_if(begin(r), end(r), o, f, a)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">replace_copy_if(begin(r), end(r), o, f, a)</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">fill(r, a)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">fill(r, a)</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">fill(begin(r), end(r), a)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">fill(begin(r), end(r), a)</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">fill_n(r, n, a)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">fill_n(r, n, a)</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">fill_n(begin(r), n, a)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">fill_n(begin(r), n, a)</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">generate(r, f)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">generate(r, f)</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">generate(begin(r), end(r), f)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">generate(begin(r), end(r), f)</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">generate_n(r, n, f)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">generate_n(r, n, f)</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">generate_n(begin(r), n, f)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">generate_n(begin(r), n, f)</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">remove(r, a)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">remove(r, a)</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">remove(begin(r), end(r), a)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">remove(begin(r), end(r), a)</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">remove_if(r, f)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">remove_if(r, f)</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">remove_if(begin(r), end(r), f)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">remove_if(begin(r), end(r), f)</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">remove_copy(r, o, a)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">remove_copy(r, o, a)</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">remove_copy(begin(r), end(r), o, a)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">remove_copy(begin(r), end(r), o, a)</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">remove_copy_if(r, o, f)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">remove_copy_if(r, o, f)</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">remove_copy_if(begin(r), end(r), o, f)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">remove_copy_if(begin(r), end(r), o, f)</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">unique(r[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">unique(r[, f])</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">unique(begin(r), end(r)[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">unique(begin(r), end(r)[,
+ f])</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">unique_copy(r, o[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">unique_copy(r, o[, f])</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">unique_copy(begin(r), end(r), o[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">unique_copy(begin(r), end(r), o[, f])</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">reverse(r)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">reverse(r)</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">reverse(begin(r), end(r))</tt>
- 
- </td>
+ 
+ <code class="computeroutput">reverse(begin(r), end(r))</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">reverse_copy(r, o)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">reverse_copy(r, o)</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">reverse_copy(begin(r), end(r), o)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">reverse_copy(begin(r), end(r), o)</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">rotate(r, m)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">rotate(r, m)</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">rotate(begin(r), m, end(r))</tt>
- 
- </td>
+ 
+ <code class="computeroutput">rotate(begin(r), m, end(r))</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">rotate_copy(r, m, o)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">rotate_copy(r, m, o)</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">rotate_copy(begin(r), m, end(r), o)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">rotate_copy(begin(r), m, end(r), o)</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">random_shuffle(r[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">random_shuffle(r[, f])</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">random_shuffle(begin(r), end(r), f)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">random_shuffle(begin(r), end(r), f)</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">partition(r, f)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">partition(r, f)</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">partition(begin(r), end(r), f)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">partition(begin(r), end(r), f)</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">stable_partition(r, f)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">stable_partition(r, f)</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">stable_partition(begin(r), end(r), f)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">stable_partition(begin(r), end(r), f)</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">sort(r[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">sort(r[, f])</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">sort(begin(r), end(r)[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">sort(begin(r), end(r)[,
+ f])</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">stable_sort(r[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">stable_sort(r[, f])</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">stable_sort(begin(r), end(r)[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">stable_sort(begin(r), end(r)[,
+ f])</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">partial_sort(r, m[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">partial_sort(r, m[, f])</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">partial_sort(begin(r), m, end(r)[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">partial_sort(begin(r), m, end(r)[,
+ f])</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">partial_sort_copy(r1, r2[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">partial_sort_copy(r1, r2[, f])</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">partial_sort_copy(begin(r1), end(r1), begin(r2), end(r2)[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">partial_sort_copy(begin(r1), end(r1), begin(r2), end(r2)[, f])</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">nth_element(r, n[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">nth_element(r, n[, f])</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">nth_element(begin(r), n, end(r)[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">nth_element(begin(r), n, end(r)[,
+ f])</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">merge(r1, r2, o[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">merge(r1, r2, o[, f])</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">merge(begin(r1), end(r1), begin(r2), end(r2), o[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">merge(begin(r1),
+ end(r1),
+ begin(r2),
+ end(r2),
+ o[,
+ f])</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">inplace_merge(r, m[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">inplace_merge(r, m[, f])</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">inplace_merge(begin(r), m, end(r)[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">inplace_merge(begin(r), m, end(r)[,
+ f])</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">set_union(r1, r2, o[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">set_union(r1, r2, o[, f])</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">set_union(begin(r1), end(r1), begin(r2), end(r2)[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">set_union(begin(r1),
+ end(r1),
+ begin(r2),
+ end(r2)[,
+ f])</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">set_intersection(r1, r2, o[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">set_intersection(r1, r2, o[, f])</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">set_intersection(begin(r1), end(r1), begin(r2), end(r2)[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">set_intersection(begin(r1), end(r1), begin(r2), end(r2)[, f])</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">set_difference(r1, r2, o[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">set_difference(r1, r2, o[, f])</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">set_difference(begin(r1), end(r1), begin(r2), end(r2)[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">set_difference(begin(r1),
+ end(r1),
+ begin(r2),
+ end(r2)[,
+ f])</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">set_symmetric_difference(r1, r2, o[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">set_symmetric_difference(r1, r2, o[, f])</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">set_symmetric_difference(begin(r1), end(r1), begin(r2), end(r2)[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">set_symmetric_difference(begin(r1), end(r1), begin(r2), end(r2)[, f])</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">push_heap(r[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">push_heap(r[, f])</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">push_heap(begin(r), end(r)[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">push_heap(begin(r), end(r)[,
+ f])</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">pop_heap(r[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">pop_heap(r[, f])</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">pop_heap(begin(r), end(r)[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">pop_heap(begin(r), end(r)[,
+ f])</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">make_heap(r[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">make_heap(r[, f])</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">make_heap(begin(r), end(r)[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">make_heap(begin(r), end(r)[,
+ f])</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">sort_heap(r[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">sort_heap(r[, f])</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">sort_heap(begin(r), end(r)[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">sort_heap(begin(r), end(r)[,
+ f])</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">next_permutation(r[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">next_permutation(r[, f])</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">next_permutation(begin(r), end(r)[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">next_permutation(begin(r), end(r)[, f])</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">prev_permutation(r[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">prev_permutation(r[, f])</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">prev_permutation(begin(r), end(r)[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">prev_permutation(begin(r), end(r)[, f])</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">inner_product(r, o, a[, f1, f2])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">inner_product(r, o, a[, f1, f2])</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">inner_product(begin(r), end(r), o[, f1, f2])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">inner_product(begin(r), end(r), o[, f1, f2])</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">partial_sum(r, o[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">partial_sum(r, o[, f])</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">partial_sum(begin(r), end(r), o[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">partial_sum(begin(r), end(r), o[, f])</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">adjacent_difference(r, o[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">adjacent_difference(r, o[, f])</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">adjacent_difference(begin(r), end(r), o[, f])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">adjacent_difference(begin(r), end(r), o[, f])</code>
+ 
+ </td>
</tr>
</tbody>
-</table>
+</table></div>
</div>
+ 
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2002-2005 Joel
+<td align="right"><div class="copyright-footer">Copyright © 2002-2005 Joel
 de Guzman, Dan Marsden
 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)
@@ -952,7 +999,7 @@
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="container.html"><img src="../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="inside_phoenix.html"><img src="../../../../../../doc/html/images/next.png" alt="Next"></a>
+<a accesskey="p" href="container.html"><img src="../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="inside_phoenix.html"><img src="../../../../../../doc/src/images/next.png" alt="Next"></a>
</div>
</body>
</html>

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-07-19 16:15:52 EDT (Mon, 19 Jul 2010)
@@ -1,11 +1,11 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Basics</title>
-<link rel="stylesheet" href="../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.66.1">
-<link rel="start" href="../index.html" title="Chapter 1. Phoenix 2.0">
-<link rel="up" href="../index.html" title="Chapter 1. Phoenix 2.0">
+<link rel="stylesheet" href="../../../../../../doc/src/boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
+<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">
<link rel="next" href="organization.html" title="Organization">
</head>
@@ -13,45 +13,46 @@
<table cellpadding="2" width="100%"><tr>
<td valign="top"><img alt="Boost C++ Libraries" width="277" height="86" src="../../../../../../boost.png"></td>
<td align="center">Home</td>
-<td align="center">Libraries</td>
+<td align="center">Libraries</td>
<td align="center">People</td>
<td align="center">FAQ</td>
<td align="center">More</td>
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="starter_kit.html"><img src="../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="organization.html"><img src="../../../../../../doc/html/images/next.png" alt="Next"></a>
+<a accesskey="p" href="starter_kit.html"><img src="../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="organization.html"><img src="../../../../../../doc/src/images/next.png" alt="Next"></a>
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="phoenix.basics"></a>Basics</h2></div></div></div>
+<a name="phoenix.basics"></a><a class="link" href="basics.html" title="Basics">Basics</a>
+</h2></div></div></div>

 Almost everything is a function in the Phoenix library that can be evaluated
- as <tt class="computeroutput">f(a1, a2, ..., an)</tt>, where n is the function's
+ as <code class="computeroutput">f(a1, a2, ..., an)</code>, where n is the function's
 arity, or number of arguments that the function expects. Operators are also
- functions. For example, <tt class="computeroutput">a + b</tt> is just
- a function with arity == 2 (or binary). <tt class="computeroutput">a
- + b</tt>
- is the same as <tt class="computeroutput">add(a, b)</tt>, <tt class="computeroutput">a
- + b + c</tt> is the
- same as <tt class="computeroutput">add(add(a, b),
- c)</tt>.
+ functions. For example, <code class="computeroutput">a + b</code> is just
+ a function with arity == 2 (or binary). <code class="computeroutput">a
+ + b</code>
+ is the same as <code class="computeroutput">add(a, b)</code>, <code class="computeroutput">a
+ + b + c</code> is the
+ same as <code class="computeroutput">add(add(a, b),
+ c)</code>.
 
<div class="note"><table border="0" summary="Note">
<tr>
-<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../../../../../../doc/html/images/note.png"></td>
+<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../../../../../../doc/src/images/note.png"></td>
<th align="left">Note</th>
</tr>
-<tr><td colspan="2" align="left" valign="top">
+<tr><td align="left" valign="top">
 Amusingly, functions may even return functions. We shall see what this means
 in a short while.
 </td></tr>
</table></div>
-<a name="phoenix.basics.partial_function_application"></a><h2>
-<a name="id459690"></a>
- <a href="basics.html#phoenix.basics.partial_function_application">Partial Function
+<a name="phoenix.basics.partial_function_application"></a><h3>
+<a name="id763540"></a>
+ <a class="link" href="basics.html#phoenix.basics.partial_function_application">Partial Function
 Application</a>
- </h2>
+ </h3>

 Think of a function as a black box. You pass arguments and it returns something
 back. The figure below depicts the typical scenario.
@@ -61,23 +62,23 @@
 

 A fully evaluated function is one in which all the arguments are given. All
- functions in plain C++ are fully evaluated. When you call the <tt class="computeroutput">sin(x)</tt> function, you have to pass a number x. The
- function will return a result in return: the sin of x. When you call the <tt class="computeroutput">add(x, y)</tt>
+ functions in plain C++ are fully evaluated. When you call the <code class="computeroutput">sin(x)</code> function, you have to pass a number x. The
+ function will return a result in return: the sin of x. When you call the <code class="computeroutput">add(x, y)</code>
 function, you have to pass two numbers x and y. The function will return the
- sum of the two numbers. The figure below is a fully evaluated <tt class="computeroutput">add</tt> function.
+ sum of the two numbers. The figure below is a fully evaluated <code class="computeroutput">add</code> function.
 

 <img src="../images/adder.png" alt="adder">
 

 A partially applied function, on the other hand, is one in which not all the
- arguments are supplied. If we are able to partially apply the function <tt class="computeroutput">add</tt> above, we may pass only the first argument.
+ arguments are supplied. If we are able to partially apply the function <code class="computeroutput">add</code> above, we may pass only the first argument.
 In doing so, the function does not have all the required information it needs
 to perform its task to compute and return a result. What it returns instead
 is another function, a lambda function --another black box. Unlike the original
- <tt class="computeroutput">add</tt> function which has an arity
+ <code class="computeroutput">add</code> function which has an arity
 of 2, the resulting lambda function has an arity of 1. Why? because we already
- supplied part of the input: <tt class="computeroutput">2</tt>
+ supplied part of the input: <code class="computeroutput">2</code>
 

 <img src="../images/add2.png" alt="add2">
@@ -85,7 +86,7 @@

 Now, when we shove in a number into our lambda function, it will return 2 plus
 whatever we pass in. The lambda function essentially remembers 1) the original
- function, <tt class="computeroutput">add</tt>, and 2) the partial
+ function, <code class="computeroutput">add</code>, and 2) the partial
 input, 2. The figure below illustrates a case where we pass 3 to our lambda
 function, which then returns 5:
 
@@ -93,59 +94,58 @@
 <img src="../images/add2_call.png" alt="add2_call">
 

- Obviously, partially applying the <tt class="computeroutput">add</tt>
+ Obviously, partially applying the <code class="computeroutput">add</code>
 function, as we see above, cannot be done directly in C++ where we are expected
 to supply all the arguments that a function expects. That's where the Phoenix
 library comes in. The library provides the facilities to do partial function
 application.
 
-<a name="phoenix.basics.stl_and_higher_order_functions"></a><h2>
-<a name="id459960"></a>
- <a href="basics.html#phoenix.basics.stl_and_higher_order_functions">STL and higher
+<a name="phoenix.basics.stl_and_higher_order_functions"></a><h3>
+<a name="id763771"></a>
+ <a class="link" href="basics.html#phoenix.basics.stl_and_higher_order_functions">STL and higher
 order functions</a>
- </h2>
+ </h3>

 So, what's all the fuss? What makes partial function application so useful?
- Recall our original example in the <a href="starter_kit.html" title="Starter Kit">previous
+ Recall our original example in the <a class="link" href="starter_kit.html" title="Starter Kit">previous
 section</a>:
 
-<pre class="programlisting">
-find_if(c.begin(), c.end(), arg1 % 2 == 1)
+<pre class="programlisting">find_if(c.begin(), c.end(), arg1 % 2 == 1)
</pre>

- The expression <tt class="computeroutput">arg1 %
- 2 == 1</tt> evaluates to a lambda function. <tt class="computeroutput">arg1</tt> is a placeholder for an argument to
+ The expression <code class="computeroutput">arg1 %
+ 2 == 1</code> evaluates to a lambda function. <code class="computeroutput">arg1</code> is a placeholder for an argument to
 be supplied later. Hence, since there's only one unsupplied argument, the lambda
- function has an arity 1. It just so happens that <tt class="computeroutput">find_if</tt>
- supplies the unsupplied argument as it loops from <tt class="computeroutput">c.begin()</tt>
- to <tt class="computeroutput">c.end()</tt>.
+ function has an arity 1. It just so happens that <code class="computeroutput">find_if</code>
+ supplies the unsupplied argument as it loops from <code class="computeroutput">c.begin()</code>
+ to <code class="computeroutput">c.end()</code>.
 
<div class="note"><table border="0" summary="Note">
<tr>
-<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../../../../../../doc/html/images/note.png"></td>
+<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../../../../../../doc/src/images/note.png"></td>
<th align="left">Note</th>
</tr>
-<tr><td colspan="2" align="left" valign="top">
+<tr><td align="left" valign="top">
 Higher order functions are functions which can take other functions as arguments,
 and may also return functions as results. Higher order functions are functions
 that are treated like any other objects and can be used as arguments and
 return values from functions.
 </td></tr>
</table></div>
-<a name="phoenix.basics.lazy_evaluation"></a><h2>
-<a name="id460216"></a>
- Lazy Evaluation
- </h2>
+<a name="phoenix.basics.lazy_evaluation"></a><h3>
+<a name="id763976"></a>
+ <a class="link" href="basics.html#phoenix.basics.lazy_evaluation">Lazy Evaluation</a>
+ </h3>

 In Phoenix, to put it more accurately, function evaluation has two stages:
 
-<div class="orderedlist"><ol type="1">
-<li>
- Partial application
- </li>
-<li>
- Final evaluation
- </li>
+<div class="orderedlist"><ol class="orderedlist" type="1">
+<li class="listitem">
+ Partial application
+ </li>
+<li class="listitem">
+ Final evaluation
+ </li>
</ol></div>

 The first stage is handled by a set of generator functions. These are your
@@ -158,17 +158,15 @@

 If we look more closely, the first step involves partial function application:
 
-<pre class="programlisting">
-arg1 % 2 == 1
+<pre class="programlisting">arg1 % 2 == 1
</pre>

- The second step is the actual function invocation (done inside the <tt class="computeroutput">find_if</tt> function. These are the back-ends
+ The second step is the actual function invocation (done inside the <code class="computeroutput">find_if</code> function. These are the back-ends
 (often, the final invocation is never actually seen by the client). In our
- example, the <tt class="computeroutput">find_if</tt>, if we
+ example, the <code class="computeroutput">find_if</code>, if we
 take a look inside, we'll see something like:
 
-<pre class="programlisting">
-template <class InputIterator, class Predicate>
+<pre class="programlisting">template <class InputIterator, class Predicate>
InputIterator
find_if(InputIterator first, InputIterator last, Predicate pred)
{
@@ -183,21 +181,20 @@
 the first and second steps juxtaposed in order to illustrate the complete semantics
 of Phoenix expressions. Examples:
 
-<pre class="programlisting">
-int x = 1;
+<pre class="programlisting">int x = 1;
int y = 2;

cout << (arg1 % 2 == 1)(x) << endl; // prints 1 or true
cout << (arg1 % 2 == 1)(y) << endl; // prints 0 or false
</pre>
-<a name="phoenix.basics.forwarding_function_problem"></a><h2>
-<a name="id460845"></a>
- <a href="basics.html#phoenix.basics.forwarding_function_problem">Forwarding Function
+<a name="phoenix.basics.forwarding_function_problem"></a><h3>
+<a name="id764488"></a>
+ <a class="link" href="basics.html#phoenix.basics.forwarding_function_problem">Forwarding Function
 Problem</a>
- </h2>
+ </h3>

 Usually, we, as clients, write the call-back functions while libraries (such
- as STL) provide the callee (e.g. <tt class="computeroutput">find_if</tt>).
+ as STL) provide the callee (e.g. <code class="computeroutput">find_if</code>).
 In case the role is reversed, e.g. if you have to write an STL algorithm that
 takes in a predicate, or develop a GUI library that accepts event handlers,
 you have to be aware of a little known problem in C++ called the "<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2002/n1385.htm" target="_top">Forwarding
@@ -206,53 +203,50 @@

 Look again at the code above:
 
-<pre class="programlisting">
-(arg1 % 2 == 1)(x)
+<pre class="programlisting">(arg1 % 2 == 1)(x)
</pre>

 Notice that, in the second-stage (the final evaluation), we used a variable
- <tt class="computeroutput">x</tt>. Be aware that the second
+ <code class="computeroutput">x</code>. Be aware that the second
 stage cannot accept non-const temporaries and literal constants. Hence, this
 will fail:
 
-<pre class="programlisting">
-(arg1 % 2 == 1)(123) // Error!
+<pre class="programlisting">(arg1 % 2 == 1)(123) // Error!
</pre>

 Disallowing non-const rvalues partially solves the "<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2002/n1385.htm" target="_top">Forwarding
 Function Problem</a>" but prohibits code like above.
 
-<a name="phoenix.basics.polymorphic_functions"></a><h2>
-<a name="id461055"></a>
- Polymorphic Functions
- </h2>
+<a name="phoenix.basics.polymorphic_functions"></a><h3>
+<a name="id764657"></a>
+ <a class="link" href="basics.html#phoenix.basics.polymorphic_functions">Polymorphic Functions</a>
+ </h3>

 Unless otherwise noted, Phoenix generated functions are fully polymorphic.
- For instance, the <tt class="computeroutput">add</tt> example
+ For instance, the <code class="computeroutput">add</code> example
 above can apply to integers, floating points, user defined complex numbers
 or even strings. Example:
 
-<pre class="programlisting">
-std::string h("Hello");
+<pre class="programlisting">std::string h("Hello");
char const* w = " World";
std::string r = add(arg1, arg2)(h, w);
</pre>

- evaluates to <tt class="computeroutput">std::string("Hello
- World")</tt>. The observant
+ evaluates to <code class="computeroutput">std::string("Hello
+ World")</code>. The observant
 reader might notice that this function call in fact takes in heterogeneous
- arguments where <tt class="computeroutput">arg1</tt> is of
- type <tt class="computeroutput">std::string</tt> and <tt class="computeroutput">arg2</tt>
- is of type <tt class="computeroutput">char const*</tt>. <tt class="computeroutput">add</tt>
- still works because the C++ standard library allows the expression <tt class="computeroutput">a + b</tt>
- where <tt class="computeroutput">a</tt> is a <tt class="computeroutput">std::string</tt>
- and <tt class="computeroutput">b</tt> is a <tt class="computeroutput">char
- const*</tt>.
+ arguments where <code class="computeroutput">arg1</code> is of
+ type <code class="computeroutput">std::string</code> and <code class="computeroutput">arg2</code>
+ is of type <code class="computeroutput">char const*</code>. <code class="computeroutput">add</code>
+ still works because the C++ standard library allows the expression <code class="computeroutput">a + b</code>
+ where <code class="computeroutput">a</code> is a <code class="computeroutput">std::string</code>
+ and <code class="computeroutput">b</code> is a <code class="computeroutput">char
+ const*</code>.
 
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2002-2005 Joel
+<td align="right"><div class="copyright-footer">Copyright © 2002-2005 Joel
 de Guzman, Dan Marsden
 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)
@@ -261,7 +255,7 @@
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="starter_kit.html"><img src="../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="organization.html"><img src="../../../../../../doc/html/images/next.png" alt="Next"></a>
+<a accesskey="p" href="starter_kit.html"><img src="../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="organization.html"><img src="../../../../../../doc/src/images/next.png" alt="Next"></a>
</div>
</body>
</html>

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-07-19 16:15:52 EDT (Mon, 19 Jul 2010)
@@ -1,11 +1,11 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Composite</title>
-<link rel="stylesheet" href="../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.66.1">
-<link rel="start" href="../index.html" title="Chapter 1. Phoenix 2.0">
-<link rel="up" href="../index.html" title="Chapter 1. Phoenix 2.0">
+<link rel="stylesheet" href="../../../../../../doc/src/boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
+<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">
<link rel="next" href="container.html" title="Container">
</head>
@@ -13,18 +13,19 @@
<table cellpadding="2" width="100%"><tr>
<td valign="top"><img alt="Boost C++ Libraries" width="277" height="86" src="../../../../../../boost.png"></td>
<td align="center">Home</td>
-<td align="center">Libraries</td>
+<td align="center">Libraries</td>
<td align="center">People</td>
<td align="center">FAQ</td>
<td align="center">More</td>
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="primitives.html"><img src="../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="container.html"><img src="../../../../../../doc/html/images/next.png" alt="Next"></a>
+<a accesskey="p" href="primitives.html"><img src="../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="container.html"><img src="../../../../../../doc/src/images/next.png" alt="Next"></a>
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="phoenix.composite"></a>Composite</h2></div></div></div>
+<a name="phoenix.composite"></a><a class="link" href="composite.html" title="Composite">Composite</a>
+</h2></div></div></div>
<div class="toc"><dl>
<dt>Function</dt>
<dt>Operator</dt>
@@ -46,12 +47,12 @@
 
<div class="note"><table border="0" summary="Note">
<tr>
-<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../../../../../../doc/html/images/note.png"></td>
+<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../../../../../../doc/src/images/note.png"></td>
<th align="left">Note</th>
</tr>
-<tr><td colspan="2" align="left" valign="top">
- You can set <tt class="computeroutput">PHOENIX_COMPOSITE_LIMIT</tt>,
- the predefined maximum actors a composite can take. By default, <tt class="computeroutput">PHOENIX_COMPOSITE_LIMIT</tt> is set to <tt class="computeroutput">PHOENIX_LIMIT</tt> (See Actors).
+<tr><td align="left" valign="top">
+ You can set <code class="computeroutput">PHOENIX_COMPOSITE_LIMIT</code>,
+ the predefined maximum actors a composite can take. By default, <code class="computeroutput">PHOENIX_COMPOSITE_LIMIT</code> is set to <code class="computeroutput">PHOENIX_LIMIT</code> (See <a class="link" href="actors.html" title="Actors">Actors</a>).
 </td></tr>
</table></div>

@@ -59,14 +60,14 @@
 since a composite is itself an actor. This makes the composite a recursive
 structure. The actual evaluation is handled by a composite specific eval policy.
 
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="phoenix.composite.function"></a>Function</h3></div></div></div>
-<pre class="programlisting">
-#include <boost/spirit/home/phoenix/function/function.hpp>
+<a name="phoenix.composite.function"></a><a class="link" href="composite.html#phoenix.composite.function" title="Function">Function</a>
+</h3></div></div></div>
+<pre class="programlisting">#include <boost/spirit/home/phoenix/function/function.hpp>
</pre>

- The <tt class="computeroutput">function</tt> class template
+ The <code class="computeroutput">function</code> class template
 provides a mechanism for implementing lazily evaluated functions. Syntactically,
 a lazy function looks like an ordinary C/C++ function. The function call
 looks familiar and feels the same as ordinary C++ functions. However, unlike
@@ -74,34 +75,34 @@
 

 Unlike ordinary function pointers or functor objects that need to be explicitly
- bound through the bind function (see Bind),
+ bound through the bind function (see <a class="link" href="composite.html#phoenix.composite.bind" title="Bind">Bind</a>),
 the argument types of these functions are automatically lazily bound.
 

 In order to create a lazy function, we need to implement a model of the FunctionEval
- concept. For a function that takes <tt class="computeroutput">N</tt>
+ concept. For a function that takes <code class="computeroutput">N</code>
 arguments, a model of FunctionEval must provide:
 
-<div class="itemizedlist"><ul type="disc">
-<li>
- An <tt class="computeroutput">operator()</tt>
- that implements that takes <tt class="computeroutput">N</tt>
- arguments, and implements the function logic.
- </li>
-<li>
- A nested metafunction <tt class="computeroutput">result<A1, ... AN></tt> that takes the types of the <tt class="computeroutput">N</tt> arguments to the function and returns
- the result type of the function. (There is a special case for function
- objects that accept no arguments. Such nullary functors are only required
- to define a typedef <tt class="computeroutput">result_type</tt>
- that reflects the return type of its <tt class="computeroutput">operator()</tt>).
- </li>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem">
+ An <code class="computeroutput">operator()</code>
+ that implements that takes <code class="computeroutput">N</code>
+ arguments, and implements the function logic.
+ </li>
+<li class="listitem">
+ A nested metafunction <code class="computeroutput">result<A1, ... AN></code>
+ that takes the types of the <code class="computeroutput">N</code>
+ arguments to the function and returns the result type of the function.
+ (There is a special case for function objects that accept no arguments.
+ Such nullary functors are only required to define a typedef <code class="computeroutput">result_type</code> that reflects the return
+ type of its <code class="computeroutput">operator()</code>).
+ </li>
</ul></div>

 For example, the following type implements the FunctionEval concept, in order
 to provide a lazy factorial function:
 
-<pre class="programlisting">
-struct factorial_impl
+<pre class="programlisting">struct factorial_impl
{
 template <typename Arg>
 struct result
@@ -120,28 +121,25 @@
 (See factorial.cpp)
 

- Having implemented the <tt class="computeroutput">factorial_impl</tt>
- type, we can declare and instantiate a lazy <tt class="computeroutput">factorial</tt>
+ Having implemented the <code class="computeroutput">factorial_impl</code>
+ type, we can declare and instantiate a lazy <code class="computeroutput">factorial</code>
 function this way:
 
-<pre class="programlisting">
-function<factorial_impl> factorial;
+<pre class="programlisting">function<factorial_impl> factorial;
</pre>

- Invoking a lazy function such as <tt class="computeroutput">factorial</tt>
- does not immediately execute the function object <tt class="computeroutput">factorial_impl</tt>.
- Instead, an actor object is created
+ Invoking a lazy function such as <code class="computeroutput">factorial</code>
+ does not immediately execute the function object <code class="computeroutput">factorial_impl</code>.
+ Instead, an <a class="link" href="actors.html" title="Actors">actor</a> object is created
 and returned to the caller. Example:
 
-<pre class="programlisting">
-factorial(arg1)
+<pre class="programlisting">factorial(arg1)
</pre>

 does nothing more than return an actor. A second function call will invoke
 the actual factorial function. Example:
 
-<pre class="programlisting">
-int i = 4;
+<pre class="programlisting">int i = 4;
cout << factorial(arg1)(i);
</pre>

@@ -152,69 +150,68 @@
 instance of the model of FunctionEval may be passed on to the constructor.
 Example:
 
-<pre class="programlisting">
-function<factorial_impl> factorial(ftor);
+<pre class="programlisting">function<factorial_impl> factorial(ftor);
</pre>

 where ftor is an instance of factorial_impl (this is not necessary in this
- case as <tt class="computeroutput">factorial_impl</tt> does
+ case as <code class="computeroutput">factorial_impl</code> does
 not require any state).
 
-<div class="sidebar">
+<div class="sidebar">
+
+
 <img src="../images/alert.png" alt="alert"> Take care though when using function objects with state
 because they are often copied repeatedly, and state may change in one of
 the copies, rather than the original.
- </div>
+ 
</div>
-<div class="section" lang="en">
+</div>
+<div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="phoenix.composite.operator"></a>Operator</h3></div></div></div>
+<a name="phoenix.composite.operator"></a><a class="link" href="composite.html#phoenix.composite.operator" title="Operator">Operator</a>
+</h3></div></div></div>

 This facility provides a mechanism for lazily evaluating operators. Syntactically,
 a lazy operator looks and feels like an ordinary C/C++ infix, prefix or postfix
 operator. The operator application looks the same. However, unlike ordinary
 operators, the actual operator execution is deferred. Samples:
 
-<pre class="programlisting">
-arg1 + arg2
+<pre class="programlisting">arg1 + arg2
1 + arg1 * arg2
1 / -arg1
arg1 < 150
</pre>

- We have seen the lazy operators in action (see <a href="starter_kit.html" title="Starter Kit">Quick
+ We have seen the lazy operators in action (see <a class="link" href="starter_kit.html" title="Starter Kit">Quick
 Start</a>). Let's go back and examine them a little bit further:
 
-<pre class="programlisting">
-find_if(c.begin(), c.end(), arg1 % 2 == 1)
+<pre class="programlisting">find_if(c.begin(), c.end(), arg1 % 2 == 1)
</pre>

- Through operator overloading, the expression <tt class="computeroutput">arg1
- % 2 == 1</tt> actually
- generates an actor. This actor object is passed on to STL's <tt class="computeroutput">find_if</tt> function. From the viewpoint of
+ Through operator overloading, the expression <code class="computeroutput">arg1
+ % 2 == 1</code> actually
+ generates an actor. This actor object is passed on to STL's <code class="computeroutput">find_if</code> function. From the viewpoint of
 STL, the composite is simply a function object expecting a single argument
- of the containers value_type. For each element in <tt class="computeroutput">c</tt>,
- the element is passed on as an argument <tt class="computeroutput">arg1</tt>
+ of the containers value_type. For each element in <code class="computeroutput">c</code>,
+ the element is passed on as an argument <code class="computeroutput">arg1</code>
 to the actor (function object). The actor checks if this is an odd value
- based on the expression <tt class="computeroutput">arg1 % 2 ==
- 1</tt> where arg1 is replaced by the container's
+ based on the expression <code class="computeroutput">arg1 % 2 ==
+ 1</code> where arg1 is replaced by the container's
 element.
 

- Like lazy functions (see function),
+ Like lazy functions (see <a class="link" href="composite.html#phoenix.composite.function" title="Function">function</a>),
 lazy operators are not immediately executed when invoked. Instead, an actor
- (see actors) object is created and
+ (see <a class="link" href="actors.html" title="Actors">actors</a>) object is created and
 returned to the caller. Example:
 
-<pre class="programlisting">
-(arg1 + arg2) * arg3
+<pre class="programlisting">(arg1 + arg2) * arg3
</pre>

 does nothing more than return an actor. A second function call will evaluate
 the actual operators. Example:
 
-<pre class="programlisting">
-int i = 4, j = 5, k = 6;
+<pre class="programlisting">int i = 4, j = 5, k = 6;
cout << ((arg1 + arg2) * arg3)(i, j, k);
</pre>

@@ -223,114 +220,108 @@

 Operator expressions are lazily evaluated following four simple rules:
 
-<div class="orderedlist"><ol type="1">
-<li>
- A binary operator, except <tt class="computeroutput">->*</tt>
- will be lazily evaluated when at least one of its
- operands is an actor object (see actors).
- </li>
-<li>
- Unary operators are lazily evaluted if their argument is an actor object.
- </li>
-<li>
- Operator <tt class="computeroutput">->*</tt> is lazily
- evaluted if the left hand argument is an actor object.
- </li>
-<li>
- The result of a lazy operator is an actor object that can in turn allow
- the applications of rules 1 and 2.
- </li>
+<div class="orderedlist"><ol class="orderedlist" type="1">
+<li class="listitem">
+ A binary operator, except <code class="computeroutput">->*</code>
+ will be lazily evaluated when at least one of its
+ 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.
+ </li>
+<li class="listitem">
+ Operator <code class="computeroutput">->*</code> is lazily
+ evaluted 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
+ the applications of rules 1 and 2.
+ </li>
</ol></div>

 For example, to check the following expression is lazily evaluated:
 
-<pre class="programlisting">
--(arg1 + 3 + 6)
+<pre class="programlisting">-(arg1 + 3 + 6)
</pre>
-<div class="orderedlist"><ol type="1">
-<li>
- Following rule 1, <tt class="computeroutput">arg1 + 3</tt> is lazily
- evaluated since <tt class="computeroutput">arg1</tt> is
- an actor (see primitives).
- </li>
-<li>
- The result of this <tt class="computeroutput">arg1 + 3</tt> expression
- is an actor object, following rule 4.
- </li>
-<li>
- Continuing, <tt class="computeroutput">arg1 +
- 3 + 6</tt> is again lazily evaluated. Rule 2.
- </li>
-<li>
- By rule 4 again, the result of <tt class="computeroutput">arg1
- + 3 + 6</tt> is an
- actor object.
- </li>
-<li>
- As <tt class="computeroutput">arg1 +
- 3 + 6</tt> is an actor, <tt class="computeroutput">-(arg1 + 3 + 6)</tt> is lazily evaluated. Rule 2.
- </li>
+<div class="orderedlist"><ol class="orderedlist" type="1">
+<li class="listitem">
+ Following rule 1, <code class="computeroutput">arg1 + 3</code> is
+ lazily evaluated since <code class="computeroutput">arg1</code>
+ is an actor (see <a class="link" href="primitives.html" title="Primitives">primitives</a>).
+ </li>
+<li class="listitem">
+ The result of this <code class="computeroutput">arg1 + 3</code> expression
+ is an actor object, following rule 4.
+ </li>
+<li class="listitem">
+ Continuing, <code class="computeroutput">arg1 +
+ 3 + 6</code> is again lazily evaluated. Rule 2.
+ </li>
+<li class="listitem">
+ By rule 4 again, the result of <code class="computeroutput">arg1
+ + 3 + 6</code> is
+ an actor object.
+ </li>
+<li class="listitem">
+ As <code class="computeroutput">arg1 +
+ 3 + 6</code> is an actor, <code class="computeroutput">-(arg1 + 3 + 6)</code> is lazily evaluated. Rule 2.
+ </li>
</ol></div>

 Lazy-operator application is highly contagious. In most cases, a single
- <tt class="computeroutput">argN</tt> actor infects all its
+ <code class="computeroutput">argN</code> actor infects all its
 immediate neighbors within a group (first level or parenthesized expression).
 

 Note that at least one operand of any operator must be a valid actor for
 lazy evaluation to take effect. To force lazy evaluation of an ordinary expression,
- we can use <tt class="computeroutput">ref(x)</tt>, <tt class="computeroutput">val(x)</tt> or <tt class="computeroutput">cref(x)</tt>
- to transform an operand into a valid actor object (see primitives.
+ we can use <code class="computeroutput">ref(x)</code>, <code class="computeroutput">val(x)</code> or <code class="computeroutput">cref(x)</code>
+ to transform an operand into a valid actor object (see <a class="link" href="primitives.html" title="Primitives">primitives</a>.
 For example:
 
-<pre class="programlisting">
-1 << 3; // Immediately evaluated
+<pre class="programlisting">1 << 3; // Immediately evaluated
val(1) << 3; // Lazily evaluated
</pre>
-<a name="phoenix.composite.operator.supported_operators"></a><h2>
-<a name="id469184"></a>
- <a href="composite.html#phoenix.composite.operator.supported_operators">Supported
+<a name="phoenix.composite.operator.supported_operators"></a><h3>
+<a name="id771576"></a>
+ <a class="link" href="composite.html#phoenix.composite.operator.supported_operators">Supported
 operators</a>
- </h2>
-<a name="phoenix.composite.operator.unary_operators"></a><h3>
-<a name="id469209"></a>
- Unary operators
 </h3>
-<pre class="programlisting">
-prefix: ~, !, -, +, ++, --, & (reference), * (dereference)
+<a name="phoenix.composite.operator.unary_operators"></a><h4>
+<a name="id771597"></a>
+ <a class="link" href="composite.html#phoenix.composite.operator.unary_operators">Unary operators</a>
+ </h4>
+<pre class="programlisting">prefix: ~, !, -, +, ++, --, & (reference), * (dereference)
postfix: ++, --
</pre>
-<a name="phoenix.composite.operator.binary_operators"></a><h3>
-<a name="id469357"></a>
- Binary operators
- </h3>
-<pre class="programlisting">
-=, [], +=, -=, *=, /=, %=, &=, |=, ^=, <<=, >>=
+<a name="phoenix.composite.operator.binary_operators"></a><h4>
+<a name="id771727"></a>
+ <a class="link" href="composite.html#phoenix.composite.operator.binary_operators">Binary operators</a>
+ </h4>
+<pre class="programlisting">=, [], +=, -=, *=, /=, %=, &=, |=, ^=, <<=, >>=
+, -, *, /, %, &, |, ^, <<, >>
==, !=, <, >, <=, >=
&&, ||, ->*
</pre>
-<a name="phoenix.composite.operator.ternary_operator"></a><h3>
-<a name="id469580"></a>
- Ternary operator
- </h3>
-<pre class="programlisting">
-if_else(c, a, b)
+<a name="phoenix.composite.operator.ternary_operator"></a><h4>
+<a name="id771926"></a>
+ <a class="link" href="composite.html#phoenix.composite.operator.ternary_operator">Ternary operator</a>
+ </h4>
+<pre class="programlisting">if_else(c, a, b)
</pre>

 The ternary operator deserves special mention. Since C++ does not allow us
- to overload the conditional expression: <tt class="computeroutput">c
- ? a : b</tt>, the
+ to overload the conditional expression: <code class="computeroutput">c
+ ? a : b</code>, the
 if_else pseudo function is provided for this purpose. The behavior is identical,
 albeit in a lazy manner.
 
-<a name="phoenix.composite.operator.member_pointer_operator"></a><h3>
-<a name="id469700"></a>
- <a href="composite.html#phoenix.composite.operator.member_pointer_operator">Member
+<a name="phoenix.composite.operator.member_pointer_operator"></a><h4>
+<a name="id772030"></a>
+ <a class="link" href="composite.html#phoenix.composite.operator.member_pointer_operator">Member
 pointer operator</a>
- </h3>
-<pre class="programlisting">
-a->*member_object_pointer
+ </h4>
+<pre class="programlisting">a->*member_object_pointer
a->*member_function_pointer
</pre>

@@ -342,8 +333,7 @@
 If the right hand side is a member object pointer, the result is an actor
 which, when evaluated, returns a reference to that member. For example:
 
-<pre class="programlisting">
-struct A
+<pre class="programlisting">struct A
{
 int member;
};
@@ -357,8 +347,7 @@
 If the right hand side is a member function pointer, the result is an actor
 which, when invoked, calls the specified member function. For example:
 
-<pre class="programlisting">
-struct A
+<pre class="programlisting">struct A
{
 int func(int);
};
@@ -369,140 +358,142 @@
(arg1->*&A::func)(arg2)(a, i); // returns a->func(i)
</pre>
<div class="table">
-<a name="id470127"></a>Table 1.4. Include Files
-<table class="table" summary="Include Files">
+<a name="id772403"></a>Table 1.4. Include Files
+<div class="table-contents"><table class="table" summary="Include Files">
<colgroup>
<col>
<col>
</colgroup>
<thead><tr>
<th>
- 
- Operators
- 
- </th>
+ 
+ Operators
+ 
+ </th>
<th>
- 
- File
- 
- </th>
+ 
+ File
+ 
+ </th>
</tr></thead>
<tbody>
<tr>
<td>
- 
- <tt class="computeroutput">-</tt>, <tt class="computeroutput">+</tt>,
- <tt class="computeroutput">++</tt>, <tt class="computeroutput">--</tt>,
- <tt class="computeroutput">+=</tt>, <tt class="computeroutput">-=</tt>,
- <tt class="computeroutput">*=</tt>, <tt class="computeroutput">/=</tt>,
- <tt class="computeroutput">%=</tt>, <tt class="computeroutput">*</tt>,
- <tt class="computeroutput">/</tt>, <tt class="computeroutput">%</tt>
- 
- </td>
+ 
+ <code class="computeroutput">-</code>, <code class="computeroutput">+</code>,
+ <code class="computeroutput">++</code>, <code class="computeroutput">--</code>, <code class="computeroutput">+=</code>,
+ <code class="computeroutput">-=</code>, <code class="computeroutput">*=</code>, <code class="computeroutput">/=</code>,
+ <code class="computeroutput">%=</code>, <code class="computeroutput">*</code>, <code class="computeroutput">/</code>,
+ <code class="computeroutput">%</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">#include <boost/spirit/home/phoenix/operator/arithmetic.hpp></tt>
- 
- </td>
+ 
+ <code class="computeroutput">#include <boost/spirit/home/phoenix/operator/arithmetic.hpp></code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">&=</tt>, <tt class="computeroutput">|=</tt>, <tt class="computeroutput">^=</tt>,
- <tt class="computeroutput"><<=</tt>, <tt class="computeroutput">>>=</tt>, <tt class="computeroutput">&</tt>,
- <tt class="computeroutput">|</tt>, <tt class="computeroutput">^</tt>,
- <tt class="computeroutput"><<</tt>, <tt class="computeroutput">>></tt>
- 
- </td>
+ 
+ <code class="computeroutput">&=</code>, <code class="computeroutput">|=</code>, <code class="computeroutput">^=</code>,
+ <code class="computeroutput"><<=</code>, <code class="computeroutput">>>=</code>, <code class="computeroutput">&</code>,
+ <code class="computeroutput">|</code>, <code class="computeroutput">^</code>,
+ <code class="computeroutput"><<</code>, <code class="computeroutput">>></code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">#include <boost/spirit/home/phoenix/operator/bitwise.hpp></tt>
- 
- </td>
+ 
+ <code class="computeroutput">#include <boost/spirit/home/phoenix/operator/bitwise.hpp></code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">==</tt>, <tt class="computeroutput">!=</tt>,
- <tt class="computeroutput"><</tt>, <tt class="computeroutput"><=</tt>,
- <tt class="computeroutput">></tt>, <tt class="computeroutput">>=</tt>
- 
- </td>
+ 
+ <code class="computeroutput">==</code>, <code class="computeroutput">!=</code>, <code class="computeroutput"><</code>,
+ <code class="computeroutput"><=</code>, <code class="computeroutput">></code>, <code class="computeroutput">>=</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">#include <boost/spirit/home/phoenix/operator/comparison.hpp></tt>
- 
- </td>
+ 
+ <code class="computeroutput">#include <boost/spirit/home/phoenix/operator/comparison.hpp></code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput"><<</tt>, <tt class="computeroutput">>></tt>
- 
- </td>
+ 
+ <code class="computeroutput"><<</code>, <code class="computeroutput">>></code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">#include <boost/spirit/home/phoenix/operator/io.hpp></tt>
- 
- </td>
+ 
+ <code class="computeroutput">#include <boost/spirit/home/phoenix/operator/io.hpp></code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">!</tt>, &&, <tt class="computeroutput">||</tt>
- 
- </td>
+ 
+ <code class="computeroutput">!</code>, &&, <code class="computeroutput">||</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">#include <boost/spirit/home/phoenix/operator/logical.hpp></tt>
- 
- </td>
+ 
+ <code class="computeroutput">#include <boost/spirit/home/phoenix/operator/logical.hpp></code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">&x</tt>,
- <tt class="computeroutput">*p</tt>,
- <tt class="computeroutput">=</tt>, <tt class="computeroutput">[]</tt>
- 
- </td>
+ 
+ <code class="computeroutput">&x</code>,
+ <code class="computeroutput">*p</code>,
+ <code class="computeroutput">=</code>, <code class="computeroutput">[]</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">#include <boost/spirit/home/phoenix/operator/self.hpp></tt>
- 
- </td>
+ 
+ <code class="computeroutput">#include <boost/spirit/home/phoenix/operator/self.hpp></code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">if_else(c, a, b)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">if_else(c,
+ a,
+ b)</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">#include <boost/spirit/home/phoenix/operator/if_else.hpp></tt>
- 
- </td>
+ 
+ <code class="computeroutput">#include <boost/spirit/home/phoenix/operator/if_else.hpp></code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">->*</tt>
- 
- </td>
+ 
+ <code class="computeroutput">->*</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">#include <boost/spirit/home/phoenix/operator/member.hpp></tt>
- 
- </td>
+ 
+ <code class="computeroutput">#include <boost/spirit/home/phoenix/operator/member.hpp></code>
+ 
+ </td>
</tr>
</tbody>
-</table>
+</table></div>
</div>
+ 
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="phoenix.composite.statement"></a>Statement</h3></div></div></div>
+<a name="phoenix.composite.statement"></a><a class="link" href="composite.html#phoenix.composite.statement" title="Statement">Statement</a>
+</h3></div></div></div>
<div class="toc"><dl>
<dt><a href="composite.html#phoenix.composite.statement.block_statement">Block
 Statement</a></dt>
@@ -519,7 +510,7 @@
<dt>throw_</dt>
</dl></div>

- Lazy statements...
+ Lazy statements...
 

 The primitives and composite building blocks presented so far are sufficiently
@@ -527,11 +518,10 @@
 functions and lazy-operators. How about lazy-statements? First, an appetizer:
 

- Print all odd-numbered contents of an STL container using <tt class="computeroutput">std::for_each</tt>
+ Print all odd-numbered contents of an STL container using <code class="computeroutput">std::for_each</code>
 (all_odds.cpp):
 
-<pre class="programlisting">
-for_each(c.begin(), c.end(),
+<pre class="programlisting">for_each(c.begin(), c.end(),
 if_(arg1 % 2 == 1)
 [
 cout << arg1 << ' '
@@ -544,18 +534,18 @@

 Yes, it is valid C++. The sample code above is as close as you can get to
 the syntax of C++. This stylized C++ syntax differs from actual C++ code.
- First, the <tt class="computeroutput">if</tt> has a trailing
+ First, the <code class="computeroutput">if</code> has a trailing
 underscore. Second, the block uses square brackets instead of the familiar
 curly braces {}.
 
<div class="note"><table border="0" summary="Note">
<tr>
-<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../../../../../../doc/html/images/note.png"></td>
+<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../../../../../../doc/src/images/note.png"></td>
<th align="left">Note</th>
</tr>
-<tr><td colspan="2" align="left" valign="top">
+<tr><td align="left" valign="top">

- C++ in C++?
+ C++ in C++?
 

 In as much as Spirit
@@ -566,31 +556,28 @@

 Here are more examples with annotations. The code almost speaks for itself.
 
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="phoenix.composite.statement.block_statement"></a><a href="composite.html#phoenix.composite.statement.block_statement" title="Block
- Statement">Block
- Statement</a></h4></div></div></div>
-<pre class="programlisting">
-#include <boost/spirit/home/phoenix/statement/sequence.hpp>
+<a name="phoenix.composite.statement.block_statement"></a><a class="link" href="composite.html#phoenix.composite.statement.block_statement" title="Block Statement">Block
+ Statement</a>
+</h4></div></div></div>
+<pre class="programlisting">#include <boost/spirit/home/phoenix/statement/sequence.hpp>
</pre>

 Syntax:
 
-<pre class="programlisting">
-statement,
+<pre class="programlisting">statement,
statement,
....
statement
</pre>

 Basically, these are comma separated statements. Take note that unlike
- the C/C++ semicolon, the comma is a separator put in-between
+ the C/C++ semicolon, the comma is a separator put in-between
 statements. This is like Pascal's semicolon separator, rather than C/C++'s
 semicolon terminator. For example:
 
-<pre class="programlisting">
-statement,
+<pre class="programlisting">statement,
statement,
statement, // ERROR!
</pre>
@@ -599,8 +586,7 @@
 can be grouped using the parentheses. Again, the last statement in a group
 should not have a trailing comma.
 
-<pre class="programlisting">
-statement,
+<pre class="programlisting">statement,
statement,
(
 statement,
@@ -611,8 +597,7 @@

 Outside the square brackets, block statements should be grouped. For example:
 
-<pre class="programlisting">
-for_each(c.begin(), c.end(),
+<pre class="programlisting">for_each(c.begin(), c.end(),
 (
 do_this(arg1),
 do_that(arg1)
@@ -627,34 +612,32 @@
 chain (and spits out an error for zero arguments).
 
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="phoenix.composite.statement.if__statement"></a>if_ Statement</h4></div></div></div>
-<pre class="programlisting">
-#include <boost/spirit/home/phoenix/statement/if.hpp>
+<a name="phoenix.composite.statement.if__statement"></a><a class="link" href="composite.html#phoenix.composite.statement.if__statement" title="if_ Statement">if_ Statement</a>
+</h4></div></div></div>
+<pre class="programlisting">#include <boost/spirit/home/phoenix/statement/if.hpp>
</pre>

- We have seen the <tt class="computeroutput">if_</tt> statement.
+ We have seen the <code class="computeroutput">if_</code> statement.
 The syntax is:
 
-<pre class="programlisting">
-if_(conditional_expression)
+<pre class="programlisting">if_(conditional_expression)
[
 sequenced_statements
]
</pre>
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="phoenix.composite.statement.if_else__statement"></a>ifelse statement</h4></div></div></div>
-<pre class="programlisting">
-#include <boost/spirit/home/phoenix/statement/if.hpp>
+<a name="phoenix.composite.statement.if_else__statement"></a><a class="link" href="composite.html#phoenix.composite.statement.if_else__statement" title="ifelse statement">ifelse statement</a>
+</h4></div></div></div>
+<pre class="programlisting">#include <boost/spirit/home/phoenix/statement/if.hpp>
</pre>

 The syntax is
 
-<pre class="programlisting">
-if_(conditional_expression)
+<pre class="programlisting">if_(conditional_expression)
[
 sequenced_statements
]
@@ -664,16 +647,15 @@
]
</pre>

- Take note that <tt class="computeroutput">else</tt> has a
- leading dot and a trailing underscore: <tt class="computeroutput">.else_</tt>
+ Take note that <code class="computeroutput">else</code> has a
+ leading dot and a trailing underscore: <code class="computeroutput">.else_</code>
 

- Example: This code prints out all the elements and appends <tt class="computeroutput">" > 5"</tt>, <tt class="computeroutput">"
- == 5"</tt> or <tt class="computeroutput">" < 5"</tt>
+ Example: This code prints out all the elements and appends <code class="computeroutput">" > 5"</code>, <code class="computeroutput">"
+ == 5"</code> or <code class="computeroutput">" < 5"</code>
 depending on the element's actual value:
 
-<pre class="programlisting">
-for_each(c.begin(), c.end(),
+<pre class="programlisting">for_each(c.begin(), c.end(),
 if_(arg1 > 5)
 [
 cout << arg1 << " > 5\n"
@@ -692,23 +674,21 @@
);
</pre>

- Notice how the <tt class="computeroutput">if_else_</tt>
+ Notice how the <code class="computeroutput">if_else_</code>
 statement is nested.
 
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="phoenix.composite.statement.switch__statement"></a><a href="composite.html#phoenix.composite.statement.switch__statement" title="switch_
- statement">switch_
- statement</a></h4></div></div></div>
-<pre class="programlisting">
-#include <boost/spirit/home/phoenix/statement/switch.hpp>
+<a name="phoenix.composite.statement.switch__statement"></a><a class="link" href="composite.html#phoenix.composite.statement.switch__statement" title="switch_ statement">switch_
+ statement</a>
+</h4></div></div></div>
+<pre class="programlisting">#include <boost/spirit/home/phoenix/statement/switch.hpp>
</pre>

 The syntax is:
 
-<pre class="programlisting">
-switch_(integral_expression)
+<pre class="programlisting">switch_(integral_expression)
[
 case_<integral_value>(sequenced_statements),
 ...
@@ -720,12 +700,11 @@
 Note unlike a normal switch statement, cases do not fall through.
 

- Example: This code prints out <tt class="computeroutput">"one"</tt>,
- <tt class="computeroutput">"two"</tt> or <tt class="computeroutput">"other value"</tt> depending on the
+ Example: This code prints out <code class="computeroutput">"one"</code>,
+ <code class="computeroutput">"two"</code> or <code class="computeroutput">"other value"</code> depending on the
 element's actual value:
 
-<pre class="programlisting">
-for_each(c.begin(), c.end(),
+<pre class="programlisting">for_each(c.begin(), c.end(),
 switch_(arg1)
 [
 case_<1>(cout << val("one") << '\n'),
@@ -735,19 +714,17 @@
);
</pre>
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="phoenix.composite.statement.while__statement"></a><a href="composite.html#phoenix.composite.statement.while__statement" title="while_
- Statement">while_
- Statement</a></h4></div></div></div>
-<pre class="programlisting">
-#include <boost/spirit/home/phoenix/statement/while.hpp>
+<a name="phoenix.composite.statement.while__statement"></a><a class="link" href="composite.html#phoenix.composite.statement.while__statement" title="while_ Statement">while_
+ Statement</a>
+</h4></div></div></div>
+<pre class="programlisting">#include <boost/spirit/home/phoenix/statement/while.hpp>
</pre>

 The syntax is:
 
-<pre class="programlisting">
-while_(conditional_expression)
+<pre class="programlisting">while_(conditional_expression)
[
 sequenced_statements
]
@@ -757,8 +734,7 @@
 out the number at each step. A newline terminates the printout of each
 value.
 
-<pre class="programlisting">
-for_each(c.begin(), c.end(),
+<pre class="programlisting">for_each(c.begin(), c.end(),
 (
 while_(arg1--)
 [
@@ -769,32 +745,30 @@
);
</pre>
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="phoenix.composite.statement.do_while__statement"></a>dowhile Statement</h4></div></div></div>
-<pre class="programlisting">
-#include <boost/spirit/home/phoenix/statement/do_while.hpp>
+<a name="phoenix.composite.statement.do_while__statement"></a><a class="link" href="composite.html#phoenix.composite.statement.do_while__statement" title="dowhile Statement">dowhile Statement</a>
+</h4></div></div></div>
+<pre class="programlisting">#include <boost/spirit/home/phoenix/statement/do_while.hpp>
</pre>

 The syntax is:
 
-<pre class="programlisting">
-do_
+<pre class="programlisting">do_
[
 sequenced_statements
]
.while_(conditional_expression)
</pre>

- Again, take note that <tt class="computeroutput">while</tt>
- has a leading dot and a trailing underscore: <tt class="computeroutput">.while_</tt>
+ Again, take note that <code class="computeroutput">while</code>
+ has a leading dot and a trailing underscore: <code class="computeroutput">.while_</code>
 

 Example: This code is almost the same as the previous example above with
 a slight twist in logic.
 
-<pre class="programlisting">
-for_each(c.begin(), c.end(),
+<pre class="programlisting">for_each(c.begin(), c.end(),
 (
 do_
 [
@@ -806,17 +780,16 @@
);
</pre>
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="phoenix.composite.statement.for__statement"></a>for_ Statement</h4></div></div></div>
-<pre class="programlisting">
-#include <boost/spirit/home/phoenix/statement/for.hpp>
+<a name="phoenix.composite.statement.for__statement"></a><a class="link" href="composite.html#phoenix.composite.statement.for__statement" title="for_ Statement">for_ Statement</a>
+</h4></div></div></div>
+<pre class="programlisting">#include <boost/spirit/home/phoenix/statement/for.hpp>
</pre>

 The syntax is:
 
-<pre class="programlisting">
-for_(init_statement, conditional_expression, step_statement)
+<pre class="programlisting">for_(init_statement, conditional_expression, step_statement)
[
 sequenced_statements
]
@@ -825,14 +798,13 @@
 It is again very similar to the C++ for statement. Take note that the init_statement,
 conditional_expression and stepstatement are
 separated by the comma instead of the semi-colon and each must be present
- (i.e. `for(,,)` is invalid). This is a case where the nothing actor can be useful.
+ (i.e. `for(,,)` is invalid). This is a case where the <a class="link" href="primitives.html#phoenix.primitives.nothing" title="Nothing">nothing</a> actor can be useful.
 

 Example: This code prints each element N times where N is the element's
 value. A newline terminates the printout of each value.
 
-<pre class="programlisting">
-int iii;
+<pre class="programlisting">int iii;
for_each(c.begin(), c.end(),
 (
 for_(ref(iii) = 0, ref(iii) < arg1, ++ref(iii))
@@ -846,33 +818,31 @@

 As before, all these are lazily evaluated. The result of such statements
 are in fact composites that are passed on to STL's for_each function. In
- the viewpoint of <tt class="computeroutput">for_each</tt>,
+ the viewpoint of <code class="computeroutput">for_each</code>,
 what was passed is just a functor, no more, no less.
 
<div class="note"><table border="0" summary="Note">
<tr>
-<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../../../../../../doc/html/images/note.png"></td>
+<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../../../../../../doc/src/images/note.png"></td>
<th align="left">Note</th>
</tr>
-<tr><td colspan="2" align="left" valign="top">
+<tr><td align="left" valign="top">
 Unlike lazy functions and lazy operators, lazy statements always return
 void.
 </td></tr>
</table></div>
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="phoenix.composite.statement.try__catch__statement"></a><a href="composite.html#phoenix.composite.statement.try__catch__statement" title="try_
- catch_ Statement">try_
- catch_ Statement</a></h4></div></div></div>
-<pre class="programlisting">
-#include <boost/spirit/home/phoenix/statement/try_catch.hpp>
+<a name="phoenix.composite.statement.try__catch__statement"></a><a class="link" href="composite.html#phoenix.composite.statement.try__catch__statement" title="try_ catch_ Statement">try_
+ catch_ Statement</a>
+</h4></div></div></div>
+<pre class="programlisting">#include <boost/spirit/home/phoenix/statement/try_catch.hpp>
</pre>

 The syntax is:
 
-<pre class="programlisting">
-try_
+<pre class="programlisting">try_
[
 sequenced_statements
]
@@ -891,12 +861,11 @@
 required after the catch.
 

- Example: The following code calls the (lazy) function <tt class="computeroutput">f</tt>
+ Example: The following code calls the (lazy) function <code class="computeroutput">f</code>
 for each element, and prints messages about different exception types it
 catches.
 
-<pre class="programlisting">
-try_
+<pre class="programlisting">try_
[
 f(arg1)
]
@@ -914,11 +883,11 @@
]
</pre>
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="phoenix.composite.statement.throw_"></a>throw_</h4></div></div></div>
-<pre class="programlisting">
-#include <boost/spirit/home/phoenix/statement/throw.hpp>
+<a name="phoenix.composite.statement.throw_"></a><a class="link" href="composite.html#phoenix.composite.statement.throw_" title="throw_">throw_</a>
+</h4></div></div></div>
+<pre class="programlisting">#include <boost/spirit/home/phoenix/statement/throw.hpp>
</pre>

 As a natural companion to the try/catch support, the statement module provides
@@ -927,22 +896,19 @@

 The syntax to throw an exception is:
 
-<pre class="programlisting">
-throw_(exception_expression)
+<pre class="programlisting">throw_(exception_expression)
</pre>

 The syntax to rethrow an exception is:
 
-<pre class="programlisting">
-throw_()
+<pre class="programlisting">throw_()
</pre>

 Example: This code extends the try/catch example, rethrowing exceptions
 derived from runtime_error or exception, and translating other exception
 types to runtime_errors.
 
-<pre class="programlisting">
-try_
+<pre class="programlisting">try_
[
 f(arg1)
]
@@ -964,30 +930,29 @@
</pre>
</div>
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="phoenix.composite.object"></a>Object</h3></div></div></div>
+<a name="phoenix.composite.object"></a><a class="link" href="composite.html#phoenix.composite.object" title="Object">Object</a>
+</h3></div></div></div>

 The Object module deals with object construction, destruction and conversion.
 The module provides "lazy" versions of C++'s
- object constructor, <tt class="computeroutput">new</tt>, <tt class="computeroutput">delete</tt>, <tt class="computeroutput">static_cast</tt>,
- <tt class="computeroutput">dynamic_cast</tt>, <tt class="computeroutput">const_cast</tt> and <tt class="computeroutput">reinterpret_cast</tt>.
+ object constructor, <code class="computeroutput">new</code>, <code class="computeroutput">delete</code>, <code class="computeroutput">static_cast</code>,
+ <code class="computeroutput">dynamic_cast</code>, <code class="computeroutput">const_cast</code> and <code class="computeroutput">reinterpret_cast</code>.
 
-<a name="phoenix.composite.object.construction"></a><h2>
-<a name="id475908"></a>
- Construction
- </h2>
+<a name="phoenix.composite.object.construction"></a><h3>
+<a name="id777481"></a>
+ <a class="link" href="composite.html#phoenix.composite.object.construction">Construction</a>
+ </h3>

- Lazy constructors...
+ Lazy constructors...
 
-<pre class="programlisting">
-#include <boost/spirit/home/phoenix/object/construct.hpp>
+<pre class="programlisting">#include <boost/spirit/home/phoenix/object/construct.hpp>
</pre>

 Lazily construct an object from an arbitrary set of arguments:
 
-<pre class="programlisting">
-construct<T>(ctor_arg1, ctor_arg2, ..., ctor_argN);
+<pre class="programlisting">construct<T>(ctor_arg1, ctor_arg2, ..., ctor_argN);
</pre>

 where the given parameters are the parameters to the contructor of the object
@@ -997,41 +962,38 @@

 Example:
 
-<pre class="programlisting">
-construct<std::string>(arg1, arg2)
+<pre class="programlisting">construct<std::string>(arg1, arg2)
</pre>

- Constructs a <tt class="computeroutput">std::string</tt> from <tt class="computeroutput">arg1</tt>
- and <tt class="computeroutput">arg2</tt>.
+ Constructs a <code class="computeroutput">std::string</code> from <code class="computeroutput">arg1</code>
+ and <code class="computeroutput">arg2</code>.
 
<div class="note"><table border="0" summary="Note">
<tr>
-<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../../../../../../doc/html/images/note.png"></td>
+<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../../../../../../doc/src/images/note.png"></td>
<th align="left">Note</th>
</tr>
-<tr><td colspan="2" align="left" valign="top">
+<tr><td align="left" valign="top">
 The maximum number of actual parameters is limited by the preprocessor
 constant PHOENIX_COMPOSITE_LIMIT. Note though, that this limit should not
- be greater than PHOENIX_LIMIT. By default, <tt class="computeroutput">PHOENIX_COMPOSITE_LIMIT</tt>
- is set to <tt class="computeroutput">PHOENIX_LIMIT</tt>
- (See Actors).
+ be greater than PHOENIX_LIMIT. By default, <code class="computeroutput">PHOENIX_COMPOSITE_LIMIT</code>
+ is set to <code class="computeroutput">PHOENIX_LIMIT</code>
+ (See <a class="link" href="actors.html" title="Actors">Actors</a>).
 </td></tr>
</table></div>
-<a name="phoenix.composite.object.new"></a><h2>
-<a name="id476272"></a>
- New
- </h2>
+<a name="phoenix.composite.object.new"></a><h3>
+<a name="id777797"></a>
+ <a class="link" href="composite.html#phoenix.composite.object.new">New</a>
+ </h3>

- Lazy new...
+ Lazy new...
 
-<pre class="programlisting">
-#include <boost/spirit/home/phoenix/object/new.hpp>
+<pre class="programlisting">#include <boost/spirit/home/phoenix/object/new.hpp>
</pre>

 Lazily construct an object, on the heap, from an arbitrary set of arguments:
 
-<pre class="programlisting">
-new_<T>(ctor_arg1, ctor_arg2, ..., ctor_argN);
+<pre class="programlisting">new_<T>(ctor_arg1, ctor_arg2, ..., ctor_argN);
</pre>

 where the given parameters are the parameters to the contructor of the object
@@ -1041,38 +1003,35 @@

 Example:
 
-<pre class="programlisting">
-new_<std::string>(arg1, arg2) // note the spelling of new_ (with trailing underscore)
+<pre class="programlisting">new_<std::string>(arg1, arg2) // note the spelling of new_ (with trailing underscore)
</pre>

- Creates a <tt class="computeroutput">std::string</tt> from <tt class="computeroutput">arg1</tt>
- and <tt class="computeroutput">arg2</tt> on the heap.
+ Creates a <code class="computeroutput">std::string</code> from <code class="computeroutput">arg1</code>
+ and <code class="computeroutput">arg2</code> on the heap.
 
<div class="note"><table border="0" summary="Note">
<tr>
-<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../../../../../../doc/html/images/note.png"></td>
+<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../../../../../../doc/src/images/note.png"></td>
<th align="left">Note</th>
</tr>
-<tr><td colspan="2" align="left" valign="top">
+<tr><td align="left" valign="top">
 Again, the maximum number of actual parameters is limited by the preprocessor
 constant PHOENIX_COMPOSITE_LIMIT. See the note above.
 </td></tr>
</table></div>
-<a name="phoenix.composite.object.delete"></a><h2>
-<a name="id476608"></a>
- Delete
- </h2>
+<a name="phoenix.composite.object.delete"></a><h3>
+<a name="id778089"></a>
+ <a class="link" href="composite.html#phoenix.composite.object.delete">Delete</a>
+ </h3>

- Lazy delete...
+ Lazy delete...
 
-<pre class="programlisting">
-#include <boost/spirit/home/phoenix/object/delete.hpp>
+<pre class="programlisting">#include <boost/spirit/home/phoenix/object/delete.hpp>
</pre>

 Lazily delete an object, from the heap:
 
-<pre class="programlisting">
-delete_(arg);
+<pre class="programlisting">delete_(arg);
</pre>

 where arg is assumed to be a pointer to an object.
@@ -1080,18 +1039,16 @@

 Example:
 
-<pre class="programlisting">
-delete_<std::string>(arg1) // note the spelling of delete_ (with trailing underscore)
+<pre class="programlisting">delete_<std::string>(arg1) // note the spelling of delete_ (with trailing underscore)
</pre>
-<a name="phoenix.composite.object.casts"></a><h2>
-<a name="id476828"></a>
- Casts
- </h2>
+<a name="phoenix.composite.object.casts"></a><h3>
+<a name="id778280"></a>
+ <a class="link" href="composite.html#phoenix.composite.object.casts">Casts</a>
+ </h3>

- Lazy casts...
+ Lazy casts...
 
-<pre class="programlisting">
-#include <boost/spirit/home/phoenix/object/static_cast.hpp>
+<pre class="programlisting">#include <boost/spirit/home/phoenix/object/static_cast.hpp>
#include <boost/spirit/home/phoenix/object/dynamic_cast.hpp>
#include <boost/spirit/home/phoenix/object/const_cast.hpp>
#include <boost/spirit/home/phoenix/object/reinterpret_cast.hpp>
@@ -1102,8 +1059,7 @@
 known C++ casts. Take note however that the lazy versions have a trailing
 underscore.
 
-<pre class="programlisting">
-static_cast_<T>(lambda_expression)
+<pre class="programlisting">static_cast_<T>(lambda_expression)
dynamic_cast_<T>(lambda_expression)
const_cast_<T>(lambda_expression)
reinterpret_cast_<T>(lambda_expression)
@@ -1111,17 +1067,17 @@

 Example:
 
-<pre class="programlisting">
-static_cast_<Base*>(&arg1)
+<pre class="programlisting">static_cast_<Base*>(&arg1)
</pre>

- Static-casts the address of <tt class="computeroutput">arg1</tt>
- to a <tt class="computeroutput">Base*</tt>.
+ Static-casts the address of <code class="computeroutput">arg1</code>
+ to a <code class="computeroutput">Base*</code>.
 
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="phoenix.composite.scope"></a>Scope</h3></div></div></div>
+<a name="phoenix.composite.scope"></a><a class="link" href="composite.html#phoenix.composite.scope" title="Scope">Scope</a>
+</h3></div></div></div>

 Up until now, the most basic ingredient is missing: creation of and access
 to local variables in the stack. When recursion comes into play, you will
@@ -1140,107 +1096,97 @@

 This section deals with local variables and nested lambda scopes.
 
-<a name="phoenix.composite.scope.local_variables"></a><h2>
-<a name="id477747"></a>
- Local Variables
- </h2>
-<pre class="programlisting">
-#include <boost/spirit/home/phoenix/scope/local_variable.hpp>
+<a name="phoenix.composite.scope.local_variables"></a><h3>
+<a name="id778838"></a>
+ <a class="link" href="composite.html#phoenix.composite.scope.local_variables">Local Variables</a>
+ </h3>
+<pre class="programlisting">#include <boost/spirit/home/phoenix/scope/local_variable.hpp>
</pre>

 We use an instance of:
 
-<pre class="programlisting">
-actor<local_variable<Key> >
+<pre class="programlisting">actor<local_variable<Key> >
</pre>

 to represent a local variable. The local variable acts as an imaginary data-bin
- where a local, stack based data will be placed. <tt class="computeroutput">Key</tt>
+ where a local, stack based data will be placed. <code class="computeroutput">Key</code>
 is an arbitrary type that is used to identify the local variable. Example:
 
-<pre class="programlisting">
-struct size_key;
+<pre class="programlisting">struct size_key;
actor<local_variable<size_key> > size;
</pre>
-<a name="phoenix.composite.scope.predefined_local_variables"></a><h2>
-<a name="id477871"></a>
- <a href="composite.html#phoenix.composite.scope.predefined_local_variables">Predefined
+<a name="phoenix.composite.scope.predefined_local_variables"></a><h3>
+<a name="id779063"></a>
+ <a class="link" href="composite.html#phoenix.composite.scope.predefined_local_variables">Predefined
 Local Variables</a>
- </h2>
+ </h3>

- There are a few predefined instances of <tt class="computeroutput">actor<local_variable<Key> ></tt>
- named <tt class="computeroutput">_a</tt>..<tt class="computeroutput">_z</tt>
- that you can already use. To make use of them, simply use the <tt class="computeroutput">namespace boost::phoenix::local_names</tt>:
- 
-<pre class="programlisting">
-using namespace boost::phoenix::local_names;
-</pre>
-<a name="phoenix.composite.scope.let"></a><h2>
-<a name="id478058"></a>
- let
- </h2>
-<pre class="programlisting">
-#include <boost/spirit/home/phoenix/scope/let.hpp>
+ There are a few predefined instances of <code class="computeroutput">actor<local_variable<Key> ></code>
+ named <code class="computeroutput">_a</code>..<code class="computeroutput">_z</code>
+ that you can already use. To make use of them, simply use the <code class="computeroutput">namespace boost::phoenix::local_names</code>:
+ 
+<pre class="programlisting">using namespace boost::phoenix::local_names;
+</pre>
+<a name="phoenix.composite.scope.let"></a><h3>
+<a name="id779228"></a>
+ <a class="link" href="composite.html#phoenix.composite.scope.let">let</a>
+ </h3>
+<pre class="programlisting">#include <boost/spirit/home/phoenix/scope/let.hpp>
</pre>

 You declare local variables using the syntax:
 
-<pre class="programlisting">
-let(local-declarations)
+<pre class="programlisting">let(local-declarations)
[
 let-body
]
</pre>

- <tt class="computeroutput">let</tt> allows 1..N local variable
- declarations (where N == <tt class="computeroutput">PHOENIX_LOCAL_LIMIT</tt>).
+ <code class="computeroutput">let</code> allows 1..N local variable
+ declarations (where N == <code class="computeroutput">PHOENIX_LOCAL_LIMIT</code>).
 Each declaration follows the form:
 
-<pre class="programlisting">
-local-id = lambda-expression
+<pre class="programlisting">local-id = lambda-expression
</pre>
<div class="note"><table border="0" summary="Note">
<tr>
-<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../../../../../../doc/html/images/note.png"></td>
+<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../../../../../../doc/src/images/note.png"></td>
<th align="left">Note</th>
</tr>
-<tr><td colspan="2" align="left" valign="top">
- You can set <tt class="computeroutput">PHOENIX_LOCAL_LIMIT</tt>,
+<tr><td align="left" valign="top">
+ You can set <code class="computeroutput">PHOENIX_LOCAL_LIMIT</code>,
 the predefined maximum local variable declarations in a let expression.
- By default, <tt class="computeroutput">PHOENIX_LOCAL_LIMIT</tt>
- is set to <tt class="computeroutput">PHOENIX_LIMIT</tt>.
+ By default, <code class="computeroutput">PHOENIX_LOCAL_LIMIT</code>
+ is set to <code class="computeroutput">PHOENIX_LIMIT</code>.
 </td></tr>
</table></div>

 Example:
 
-<pre class="programlisting">
-let(_a = 123, _b = 456)
+<pre class="programlisting">let(_a = 123, _b = 456)
[
 _a + _b
]
</pre>
-<a name="phoenix.composite.scope.reference_preservation"></a><h2>
-<a name="id478463"></a>
- <a href="composite.html#phoenix.composite.scope.reference_preservation">Reference
+<a name="phoenix.composite.scope.reference_preservation"></a><h3>
+<a name="id779579"></a>
+ <a class="link" href="composite.html#phoenix.composite.scope.reference_preservation">Reference
 Preservation</a>
- </h2>
+ </h3>

 The type of the local variable assumes the type of the lambda- expression.
 Type deduction is reference preserving. For example:
 
-<pre class="programlisting">
-let(_a = arg1, _b = 456)
+<pre class="programlisting">let(_a = arg1, _b = 456)
</pre>

- <tt class="computeroutput">_a</tt> assumes the type of <tt class="computeroutput">arg1</tt>: a reference to an argument, while
- <tt class="computeroutput">_b</tt> has type <tt class="computeroutput">int</tt>.
+ <code class="computeroutput">_a</code> assumes the type of <code class="computeroutput">arg1</code>: a reference to an argument, while
+ <code class="computeroutput">_b</code> has type <code class="computeroutput">int</code>.
 

 Consider this:
 
-<pre class="programlisting">
-int i = 1;
+<pre class="programlisting">int i = 1;

let(_a = arg1)
[
@@ -1256,8 +1202,7 @@

 While with this:
 
-<pre class="programlisting">
-int i = 1;
+<pre class="programlisting">int i = 1;

let(_a = val(arg1))
[
@@ -1272,20 +1217,19 @@
 

 Reference preservation is necessary because we need to have L-value access
- to outer lambda-scopes (especially the arguments). <tt class="computeroutput">arg</tt>s
- and <tt class="computeroutput">ref</tt>s are L-values. <tt class="computeroutput">val</tt>s are R-values.
+ to outer lambda-scopes (especially the arguments). <code class="computeroutput">arg</code>s
+ and <code class="computeroutput">ref</code>s are L-values. <code class="computeroutput">val</code>s are R-values.
 
-<a name="phoenix.composite.scope.visibility"></a><h2>
-<a name="id479015"></a>
- Visibility
- </h2>
+<a name="phoenix.composite.scope.visibility"></a><h3>
+<a name="id780063"></a>
+ <a class="link" href="composite.html#phoenix.composite.scope.visibility">Visibility</a>
+ </h3>

 The scope and lifetimes of the local variables is limited within the let-body.
- <tt class="computeroutput">let</tt> blocks can be nested.
+ <code class="computeroutput">let</code> blocks can be nested.
 A local variable may hide an outer local variable. For example:
 
-<pre class="programlisting">
-let(_x = 1, _y = ", World")
+<pre class="programlisting">let(_x = 1, _y = ", World")
[
 // _x here is an int: 1

@@ -1300,8 +1244,7 @@
 refer to any LHS local-id. At this point, the local-ids are not in scope
 yet; they will only be in scope in the let-body. The code below is in error:
 
-<pre class="programlisting">
-let(
+<pre class="programlisting">let(
 _a = 1
 , _b = _a // Error: _a is not in scope yet
)
@@ -1316,8 +1259,7 @@
 the let, the RHS of a local-declaration can refer to a local variable of
 an outer scope:
 
-<pre class="programlisting">
-let(_a = 1)
+<pre class="programlisting">let(_a = 1)
[
 let(
 _a = 1
@@ -1328,20 +1270,18 @@
 ]
]
</pre>
-<a name="phoenix.composite.scope.lambda"></a><h2>
-<a name="id479480"></a>
- lambda
- </h2>
-<pre class="programlisting">
-#include <boost/spirit/home/phoenix/scope/lambda.hpp>
+<a name="phoenix.composite.scope.lambda"></a><h3>
+<a name="id780472"></a>
+ <a class="link" href="composite.html#phoenix.composite.scope.lambda">lambda</a>
+ </h3>
+<pre class="programlisting">#include <boost/spirit/home/phoenix/scope/lambda.hpp>
</pre>

 A lot of times, you'd want to write a lazy function that accepts one or more
 functions (higher order functions). STL algorithms come to mind, for example.
- Consider a lazy version of <tt class="computeroutput">stl::for_each</tt>:
+ Consider a lazy version of <code class="computeroutput">stl::for_each</code>:
 
-<pre class="programlisting">
-struct for_each_impl
+<pre class="programlisting">struct for_each_impl
{
 template <typename C, typename F>
 struct result
@@ -1359,28 +1299,26 @@
function<for_each_impl> const for_each = for_each_impl();
</pre>

- Notice that the function accepts another function, <tt class="computeroutput">f</tt>
- as an argument. The scope of this function, <tt class="computeroutput">f</tt>,
- is limited within the <tt class="computeroutput">operator()</tt>. When <tt class="computeroutput">f</tt>
- is called inside <tt class="computeroutput">std::for_each</tt>, it exists in a new scope, along
+ Notice that the function accepts another function, <code class="computeroutput">f</code>
+ as an argument. The scope of this function, <code class="computeroutput">f</code>,
+ is limited within the <code class="computeroutput">operator()</code>. When <code class="computeroutput">f</code>
+ is called inside <code class="computeroutput">std::for_each</code>, it exists in a new scope, along
 with new arguments and, possibly, local variables. This new scope is not
- at all related to the outer scopes beyond the <tt class="computeroutput">operator()</tt>.
+ at all related to the outer scopes beyond the <code class="computeroutput">operator()</code>.
 

 Simple syntax:
 
-<pre class="programlisting">
-lambda
+<pre class="programlisting">lambda
[
 lambda-body
]
</pre>

- Like <tt class="computeroutput">let</tt>, local variables
- may be declared, allowing 1..N local variable declarations (where N == <tt class="computeroutput">PHOENIX_LOCAL_LIMIT</tt>):
+ Like <code class="computeroutput">let</code>, local variables
+ may be declared, allowing 1..N local variable declarations (where N == <code class="computeroutput">PHOENIX_LOCAL_LIMIT</code>):
 
-<pre class="programlisting">
-lambda(local-declarations)
+<pre class="programlisting">lambda(local-declarations)
[
 lambda-body
]
@@ -1391,56 +1329,53 @@
 to any LHS local-id. The local-ids are not in scope yet; they will be in
 scope only in the lambda-body:
 
-<pre class="programlisting">
-lambda(
+<pre class="programlisting">lambda(
 _a = 1
 , _b = _a // Error: _a is not in scope yet
)
</pre>

- See <a href="composite.html#phoenix.composite.scope.visibility"><tt class="computeroutput">let</tt>
+ See <a class="link" href="composite.html#phoenix.composite.scope.visibility"><code class="computeroutput">let</code>
 Visibility</a> above for more information.
 

- Example: Using our lazy <tt class="computeroutput">for_each</tt>
+ Example: Using our lazy <code class="computeroutput">for_each</code>
 let's print all the elements in a container:
 
-<pre class="programlisting">
-for_each(arg1, lambda[cout << arg1])
+<pre class="programlisting">for_each(arg1, lambda[cout << arg1])
</pre>

 As far as the arguments are concerned (arg1..argN), the scope in which the
- lambda-body exists is totally new. The left <tt class="computeroutput">arg1</tt>
- refers to the argument passed to <tt class="computeroutput">for_each</tt>
- (a container). The right <tt class="computeroutput">arg1</tt>
- refers to the argument passed by <tt class="computeroutput">std::for_each</tt>
- when we finally get to call <tt class="computeroutput">operator()</tt> in our <tt class="computeroutput">for_each_impl</tt>
+ lambda-body exists is totally new. The left <code class="computeroutput">arg1</code>
+ refers to the argument passed to <code class="computeroutput">for_each</code>
+ (a container). The right <code class="computeroutput">arg1</code>
+ refers to the argument passed by <code class="computeroutput">std::for_each</code>
+ when we finally get to call <code class="computeroutput">operator()</code> in our <code class="computeroutput">for_each_impl</code>
 above (a container element).
 

 Yet, we may wish to get information from outer scopes. While we do not have
 access to arguments in outer scopes, what we still have is access to local
 variables from outer scopes. We may only be able to pass argument related
- information from outer <tt class="computeroutput">lambda</tt>
+ information from outer <code class="computeroutput">lambda</code>
 scopes through the local variables.
 
<div class="note"><table border="0" summary="Note">
<tr>
-<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../../../../../../doc/html/images/note.png"></td>
+<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../../../../../../doc/src/images/note.png"></td>
<th align="left">Note</th>
</tr>
-<tr><td colspan="2" align="left" valign="top">
- This is a crucial difference between <tt class="computeroutput">let</tt>
- and <tt class="computeroutput">lambda</tt>: <tt class="computeroutput">let</tt> does not introduce new arguments;
- <tt class="computeroutput">lambda</tt> does.
+<tr><td align="left" valign="top">
+ This is a crucial difference between <code class="computeroutput">let</code>
+ and <code class="computeroutput">lambda</code>: <code class="computeroutput">let</code> does not introduce new arguments;
+ <code class="computeroutput">lambda</code> does.
 </td></tr>
</table></div>

- Another example: Using our lazy <tt class="computeroutput">for_each</tt>,
- and a lazy <tt class="computeroutput">push_back</tt>:
+ Another example: Using our lazy <code class="computeroutput">for_each</code>,
+ and a lazy <code class="computeroutput">push_back</code>:
 
-<pre class="programlisting">
-struct push_back_impl
+<pre class="programlisting">struct push_back_impl
{
 template <typename C, typename T>
 struct result
@@ -1460,22 +1395,21 @@

 write a lambda expression that accepts:
 
-<div class="orderedlist"><ol type="1">
-<li>
- a 2-dimensional container (e.g. <tt class="computeroutput">vector<vector<int> ></tt>)
- </li>
-<li>
- a container element (e.g. <tt class="computeroutput">int</tt>)
- </li>
+<div class="orderedlist"><ol class="orderedlist" type="1">
+<li class="listitem">
+ a 2-dimensional container (e.g. <code class="computeroutput">vector<vector<int> ></code>)
+ </li>
+<li class="listitem">
+ a container element (e.g. <code class="computeroutput">int</code>)
+ </li>
</ol></div>

- and pushes-back the element to each of the <tt class="computeroutput">vector<int></tt>.
+ and pushes-back the element to each of the <code class="computeroutput">vector<int></code>.
 

 Solution:
 
-<pre class="programlisting">
-for_each(arg1,
+<pre class="programlisting">for_each(arg1,
 lambda(_a = arg2)
 [
 push_back(arg1, _a)
@@ -1484,150 +1418,139 @@
</pre>

 Since we do not have access to the arguments of the outer scopes beyond the
- lambda-body, we introduce a local variable <tt class="computeroutput">_a</tt>
- that captures the second outer argument: <tt class="computeroutput">arg2</tt>.
+ lambda-body, we introduce a local variable <code class="computeroutput">_a</code>
+ that captures the second outer argument: <code class="computeroutput">arg2</code>.
 Hence: _a = arg2. This local variable is visible inside the lambda scope.
 

 (See lambda.cpp)
 
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="phoenix.composite.bind"></a>Bind</h3></div></div></div>
+<a name="phoenix.composite.bind"></a><a class="link" href="composite.html#phoenix.composite.bind" title="Bind">Bind</a>
+</h3></div></div></div>

 Binding is the act of tying together a function to some
- arguments for deferred (lazy) evaluation. Named <a href="composite.html#phoenix.composite.function" title="Function">Lazy
+ 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.
 If you wish to transform a plain function, member function or member variable
- to a lambda expression, <tt class="computeroutput">bind</tt>
+ to a lambda expression, <code class="computeroutput">bind</code>
 is your friend.
 
<div class="note"><table border="0" summary="Note">
<tr>
-<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../../../../../../doc/html/images/note.png"></td>
+<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../../../../../../doc/src/images/note.png"></td>
<th align="left">Note</th>
</tr>
-<tr><td colspan="2" align="left" valign="top">
+<tr><td align="left" valign="top">
 Take note that binders are monomorphic. Rather than binding functions,
- the preferred way is to write true generic and polymorphic lazy-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
 code, binders get the job done faster.
 </td></tr>
</table></div>

- There is a set of overloaded <tt class="computeroutput">bind</tt>
- template functions. Each <tt class="computeroutput">bind(x)</tt>
- function generates a suitable binder object, a composite.
- 
-<a name="phoenix.composite.bind.binding_functions"></a><h2>
-<a name="id481353"></a>
- Binding Functions
- </h2>
-<pre class="programlisting">
-#include <boost/spirit/home/phoenix/bind/bind_function.hpp>
+ There is a set of overloaded <code class="computeroutput">bind</code>
+ template functions. Each <code class="computeroutput">bind(x)</code>
+ function generates a suitable binder object, a <a class="link" href="composite.html" title="Composite">composite</a>.
+ 
+<a name="phoenix.composite.bind.binding_functions"></a><h3>
+<a name="id782121"></a>
+ <a class="link" href="composite.html#phoenix.composite.bind.binding_functions">Binding Functions</a>
+ </h3>
+<pre class="programlisting">#include <boost/spirit/home/phoenix/bind/bind_function.hpp>
</pre>

- Example, given a function <tt class="computeroutput">foo</tt>:
+ Example, given a function <code class="computeroutput">foo</code>:
 
-<pre class="programlisting">
-void foo(int n)
+<pre class="programlisting">void foo(int n)
{
 std::cout << n << std::endl;
}
</pre>

- Here's how the function <tt class="computeroutput">foo</tt>
+ Here's how the function <code class="computeroutput">foo</code>
 may be bound:
 
-<pre class="programlisting">
-bind(&foo, arg1)
+<pre class="programlisting">bind(&foo, arg1)
</pre>

- This is now a full-fledged composite
+ This is now a full-fledged <a class="link" href="composite.html" title="Composite">composite</a>
 that can finally be evaluated by another function call invocation. A second
- function call will invoke the actual <tt class="computeroutput">foo</tt>
+ function call will invoke the actual <code class="computeroutput">foo</code>
 function. Example:
 
-<pre class="programlisting">
-int i = 4;
+<pre class="programlisting">int i = 4;
bind(&foo, arg1)(i);
</pre>

 will print out "4".
 
-<a name="phoenix.composite.bind.binding_member_functions"></a><h2>
-<a name="id481759"></a>
- <a href="composite.html#phoenix.composite.bind.binding_member_functions">Binding Member
+<a name="phoenix.composite.bind.binding_member_functions"></a><h3>
+<a name="id782474"></a>
+ <a class="link" href="composite.html#phoenix.composite.bind.binding_member_functions">Binding Member
 Functions</a>
- </h2>
-<pre class="programlisting">
-#include <boost/spirit/home/phoenix/bind/bind_member_function.hpp>
+ </h3>
+<pre class="programlisting">#include <boost/spirit/home/phoenix/bind/bind_member_function.hpp>
</pre>

 Binding member functions can be done similarly. A bound member function takes
 in a pointer or reference to an object as the first argument. For instance,
 given:
 
-<pre class="programlisting">
-struct xyz
+<pre class="programlisting">struct xyz
{
 void foo(int) const;
};
</pre>

- <tt class="computeroutput">xyz</tt>'s <tt class="computeroutput">foo</tt>
+ <code class="computeroutput">xyz</code>'s <code class="computeroutput">foo</code>
 member function can be bound as:
 
-<pre class="programlisting">
-bind(&xyz::foo, obj, arg1) // obj is an xyz object
+<pre class="programlisting">bind(&xyz::foo, obj, arg1) // obj is an xyz object
</pre>

 Take note that a lazy-member functions expects the first argument to be a
 pointer or reference to an object. Both the object (reference or pointer)
 and the arguments can be lazily bound. Examples:
 
-<pre class="programlisting">
-xyz obj;
+<pre class="programlisting">xyz obj;
bind(&xyz::foo, arg1, arg2) // arg1.foo(arg2)
bind(&xyz::foo, obj, arg1) // obj.foo(arg1)
bind(&xyz::foo, obj, 100) // obj.foo(100)
</pre>
-<a name="phoenix.composite.bind.binding_member_variables"></a><h2>
-<a name="id482250"></a>
- <a href="composite.html#phoenix.composite.bind.binding_member_variables">Binding Member
+<a name="phoenix.composite.bind.binding_member_variables"></a><h3>
+<a name="id782905"></a>
+ <a class="link" href="composite.html#phoenix.composite.bind.binding_member_variables">Binding Member
 Variables</a>
- </h2>
-<pre class="programlisting">
-#include <boost/spirit/home/phoenix/bind/bind_member_variable.hpp>
+ </h3>
+<pre class="programlisting">#include <boost/spirit/home/phoenix/bind/bind_member_variable.hpp>
</pre>

 Member variables can also be bound much like member functions. Member variables
- are not functions. Yet, like the ref(x) that acts like a nullary function
+ are not functions. Yet, like the <a class="link" href="primitives.html#phoenix.primitives.references" title="References"><code class="computeroutput">ref(x)</code></a> that acts like a nullary function
 returning a reference to the data, member variables, when bound, act like
 a unary function, taking in a pointer or reference to an object as its argument
 and returning a reference to the bound member variable. For instance, given:
 
-<pre class="programlisting">
-struct xyz
+<pre class="programlisting">struct xyz
{
 int v;
};
</pre>

- <tt class="computeroutput">xyz::v</tt> can be bound as:
+ <code class="computeroutput">xyz::v</code> can be bound as:
 
-<pre class="programlisting">
-bind(&xyz::v, obj) // obj is an xyz object
+<pre class="programlisting">bind(&xyz::v, obj) // obj is an xyz object
</pre>

 As noted, just like the bound member function, a bound member variable also
 expects the first (and only) argument to be a pointer or reference to an
 object. The object (reference or pointer) can be lazily bound. Examples:
 
-<pre class="programlisting">
-xyz obj;
+<pre class="programlisting">xyz obj;
bind(&xyz::v, arg1) // arg1.v
bind(&xyz::v, obj) // obj.v
bind(&xyz::v, arg1)(obj) = 4 // obj.v = 4
@@ -1636,7 +1559,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2002-2005 Joel
+<td align="right"><div class="copyright-footer">Copyright © 2002-2005 Joel
 de Guzman, Dan Marsden
 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)
@@ -1645,7 +1568,7 @@
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="primitives.html"><img src="../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="container.html"><img src="../../../../../../doc/html/images/next.png" alt="Next"></a>
+<a accesskey="p" href="primitives.html"><img src="../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="container.html"><img src="../../../../../../doc/src/images/next.png" alt="Next"></a>
</div>
</body>
</html>

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-07-19 16:15:52 EDT (Mon, 19 Jul 2010)
@@ -1,11 +1,11 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Container</title>
-<link rel="stylesheet" href="../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.66.1">
-<link rel="start" href="../index.html" title="Chapter 1. Phoenix 2.0">
-<link rel="up" href="../index.html" title="Chapter 1. Phoenix 2.0">
+<link rel="stylesheet" href="../../../../../../doc/src/boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
+<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">
<link rel="next" href="algorithm.html" title="Algorithm">
</head>
@@ -13,20 +13,20 @@
<table cellpadding="2" width="100%"><tr>
<td valign="top"><img alt="Boost C++ Libraries" width="277" height="86" src="../../../../../../boost.png"></td>
<td align="center">Home</td>
-<td align="center">Libraries</td>
+<td align="center">Libraries</td>
<td align="center">People</td>
<td align="center">FAQ</td>
<td align="center">More</td>
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="composite.html"><img src="../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="algorithm.html"><img src="../../../../../../doc/html/images/next.png" alt="Next"></a>
+<a accesskey="p" href="composite.html"><img src="../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="algorithm.html"><img src="../../../../../../doc/src/images/next.png" alt="Next"></a>
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="phoenix.container"></a>Container</h2></div></div></div>
-<pre class="programlisting">
-#include <boost/spirit/home/phoenix/container.hpp>
+<a name="phoenix.container"></a><a class="link" href="container.html" title="Container">Container</a>
+</h2></div></div></div>
+<pre class="programlisting">#include <boost/spirit/home/phoenix/container.hpp>
</pre>

 The container module predefines a set of lazy functions that work on STL containers.
@@ -38,104 +38,104 @@
 Lazy functions are provided for all of the member functions of the following
 containers:
 
-<div class="itemizedlist"><ul type="disc">
-<li>
- deque
- </li>
-<li>
- list
- </li>
-<li>
- map
- </li>
-<li>
- multimap
- </li>
-<li>
- vector
- </li>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem">
+ deque
+ </li>
+<li class="listitem">
+ list
+ </li>
+<li class="listitem">
+ map
+ </li>
+<li class="listitem">
+ multimap
+ </li>
+<li class="listitem">
+ vector
+ </li>
</ul></div>

 Indeed, should your class have member functions with the same names and signatures
 as those listed below, then it will automatically be supported. To summarize,
 lazy functions are provided for member functions:
 
-<div class="itemizedlist"><ul type="disc">
-<li>
- assign
- </li>
-<li>
- at
- </li>
-<li>
- back
- </li>
-<li>
- begin
- </li>
-<li>
- capacity
- </li>
-<li>
- clear
- </li>
-<li>
- empty
- </li>
-<li>
- end
- </li>
-<li>
- erase
- </li>
-<li>
- front
- </li>
-<li>
- get_allocator
- </li>
-<li>
- insert
- </li>
-<li>
- key_comp
- </li>
-<li>
- max_size
- </li>
-<li>
- pop_back
- </li>
-<li>
- pop_front
- </li>
-<li>
- push_back
- </li>
-<li>
- push_front
- </li>
-<li>
- rbegin
- </li>
-<li>
- rend
- </li>
-<li>
- reserve
- </li>
-<li>
- resize
- </li>
-<li>
- size
- </li>
-<li>
- splice
- </li>
-<li>
- value_comp
- </li>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem">
+ assign
+ </li>
+<li class="listitem">
+ at
+ </li>
+<li class="listitem">
+ back
+ </li>
+<li class="listitem">
+ begin
+ </li>
+<li class="listitem">
+ capacity
+ </li>
+<li class="listitem">
+ clear
+ </li>
+<li class="listitem">
+ empty
+ </li>
+<li class="listitem">
+ end
+ </li>
+<li class="listitem">
+ erase
+ </li>
+<li class="listitem">
+ front
+ </li>
+<li class="listitem">
+ get_allocator
+ </li>
+<li class="listitem">
+ insert
+ </li>
+<li class="listitem">
+ key_comp
+ </li>
+<li class="listitem">
+ max_size
+ </li>
+<li class="listitem">
+ pop_back
+ </li>
+<li class="listitem">
+ pop_front
+ </li>
+<li class="listitem">
+ push_back
+ </li>
+<li class="listitem">
+ push_front
+ </li>
+<li class="listitem">
+ rbegin
+ </li>
+<li class="listitem">
+ rend
+ </li>
+<li class="listitem">
+ reserve
+ </li>
+<li class="listitem">
+ resize
+ </li>
+<li class="listitem">
+ size
+ </li>
+<li class="listitem">
+ splice
+ </li>
+<li class="listitem">
+ value_comp
+ </li>
</ul></div>

 The lazy functions' names are the same as the corresponding member function.
@@ -143,417 +143,423 @@
 does not use the member "dot" syntax.
 
<div class="table">
-<a name="id482988"></a>Table 1.5. Sample usage
-<table class="table" summary="Sample usage">
+<a name="id783648"></a>Table 1.5. Sample usage
+<div class="table-contents"><table class="table" summary="Sample usage">
<colgroup>
<col>
<col>
</colgroup>
<thead><tr>
<th>
- 
- "Normal" version
- 
- </th>
+ 
+ "Normal" version
+ 
+ </th>
<th>
- 
- "Lazy" version
- 
- </th>
+ 
+ "Lazy" version
+ 
+ </th>
</tr></thead>
<tbody>
<tr>
<td>
- 
- <tt class="computeroutput">my_vector.at(5)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">my_vector.at(5)</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">at(arg1, 5)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">at(arg1,
+ 5)</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">my_list.size()</tt>
- 
- </td>
+ 
+ <code class="computeroutput">my_list.size()</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">size(arg1)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">size(arg1)</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">my_vector1.swap(my_vector2)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">my_vector1.swap(my_vector2)</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">swap(arg1, arg2)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">swap(arg1,
+ arg2)</code>
+ 
+ </td>
</tr>
</tbody>
-</table>
+</table></div>
</div>
-
+ 
 Notice that member functions with names that clash with stl algorithms are
 absent. This will be provided in Phoenix's algorithm module.
 

- No support is provided here for lazy versions of <tt class="computeroutput">operator+=</tt>, <tt class="computeroutput">operator[]</tt> etc. Such operators are not specific to STL
- containers and lazy versions can therefore be found in operators.
+ No support is provided here for lazy versions of <code class="computeroutput">operator+=</code>, <code class="computeroutput">operator[]</code> etc. Such operators are not specific to STL
+ containers and lazy versions can therefore be found in <a class="link" href="composite.html#phoenix.composite.operator" title="Operator">operators</a>.
 

 The following table describes the container functions and their semantics.
 
-<div class="sidebar">
+<div class="sidebar">
+
+
 <img src="../images/tip.png" alt="tip"> Arguments in brackets denote optional parameters.
- </div>
+ 
+</div>
<div class="table">
-<a name="id483365"></a>Table 1.6. Lazy STL Container Functions
-<table class="table" summary="Lazy STL Container Functions">
+<a name="id783986"></a>Table 1.6. Lazy STL Container Functions
+<div class="table-contents"><table class="table" summary="Lazy STL Container Functions">
<colgroup>
<col>
<col>
</colgroup>
<thead><tr>
<th>
- 
- Function
- 
- </th>
+ 
+ Function
+ 
+ </th>
<th>
- 
- Semantics
- 
- </th>
+ 
+ Semantics
+ 
+ </th>
</tr></thead>
<tbody>
<tr>
<td>
- 
- <tt class="computeroutput">assign(c, a[, b, c])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">assign(c, a[, b, c])</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">c.assign(a[, b, c])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">c.assign(a[, b, c])</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">at(c, i)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">at(c, i)</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">c.at(i)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">c.at(i)</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">back(c)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">back(c)</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">c.back()</tt>
- 
- </td>
+ 
+ <code class="computeroutput">c.back()</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">begin(c)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">begin(c)</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">c.begin()</tt>
- 
- </td>
+ 
+ <code class="computeroutput">c.begin()</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">capacity(c)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">capacity(c)</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">c.capacity()</tt>
- 
- </td>
+ 
+ <code class="computeroutput">c.capacity()</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">clear(c)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">clear(c)</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">c.clear()</tt>
- 
- </td>
+ 
+ <code class="computeroutput">c.clear()</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">empty(c)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">empty(c)</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">c.empty()</tt>
- 
- </td>
+ 
+ <code class="computeroutput">c.empty()</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">end(c)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">end(c)</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">c.end()</tt>
- 
- </td>
+ 
+ <code class="computeroutput">c.end()</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">erase(c, a[, b])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">erase(c, a[, b])</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">c.erase(a[, b])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">c.erase(a[, b])</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">front(c)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">front(c)</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">c.front()</tt>
- 
- </td>
+ 
+ <code class="computeroutput">c.front()</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">get_allocator(c)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">get_allocator(c)</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">c.get_allocator()</tt>
- 
- </td>
+ 
+ <code class="computeroutput">c.get_allocator()</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">insert(c, a[, b, c])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">insert(c, a[, b, c])</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">c.insert(a[, b, c])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">c.insert(a[, b, c])</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">key_comp(c)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">key_comp(c)</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">c.key_comp()</tt>
- 
- </td>
+ 
+ <code class="computeroutput">c.key_comp()</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">max_size(c)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">max_size(c)</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">c.max_size()</tt>
- 
- </td>
+ 
+ <code class="computeroutput">c.max_size()</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">pop_back(c)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">pop_back(c)</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">c.pop_back()</tt>
- 
- </td>
+ 
+ <code class="computeroutput">c.pop_back()</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">pop_front(c)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">pop_front(c)</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">c.pop_front()</tt>
- 
- </td>
+ 
+ <code class="computeroutput">c.pop_front()</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">push_back(c, d)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">push_back(c, d)</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">c.push_back(d)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">c.push_back(d)</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">push_front(c, d)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">push_front(c, d)</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">c.push_front(d)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">c.push_front(d)</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">pop_front(c)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">pop_front(c)</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">c.pop_front()</tt>
- 
- </td>
+ 
+ <code class="computeroutput">c.pop_front()</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">rbegin(c)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">rbegin(c)</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">c.rbegin()</tt>
- 
- </td>
+ 
+ <code class="computeroutput">c.rbegin()</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">rend(c)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">rend(c)</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">c.rend()</tt>
- 
- </td>
+ 
+ <code class="computeroutput">c.rend()</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">reserve(c, n)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">reserve(c, n)</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">c.reserve(n)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">c.reserve(n)</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">resize(c, a[, b])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">resize(c, a[, b])</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">c.resize(a[, b])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">c.resize(a[, b])</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">size(c)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">size(c)</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">c.size()</tt>
- 
- </td>
+ 
+ <code class="computeroutput">c.size()</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">splice(c, a[, b, c, d])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">splice(c, a[, b, c, d])</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">c.splice(a[, b, c, d])</tt>
- 
- </td>
+ 
+ <code class="computeroutput">c.splice(a[, b, c, d])</code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">value_comp(c)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">value_comp(c)</code>
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">c.value_comp()</tt>
- 
- </td>
+ 
+ <code class="computeroutput">c.value_comp()</code>
+ 
+ </td>
</tr>
</tbody>
-</table>
+</table></div>
</div>
+ 
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2002-2005 Joel
+<td align="right"><div class="copyright-footer">Copyright © 2002-2005 Joel
 de Guzman, Dan Marsden
 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)
@@ -562,7 +568,7 @@
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="composite.html"><img src="../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="algorithm.html"><img src="../../../../../../doc/html/images/next.png" alt="Next"></a>
+<a accesskey="p" href="composite.html"><img src="../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="algorithm.html"><img src="../../../../../../doc/src/images/next.png" alt="Next"></a>
</div>
</body>
</html>

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-07-19 16:15:52 EDT (Mon, 19 Jul 2010)
@@ -1,11 +1,11 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Inside Phoenix</title>
-<link rel="stylesheet" href="../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.66.1">
-<link rel="start" href="../index.html" title="Chapter 1. Phoenix 2.0">
-<link rel="up" href="../index.html" title="Chapter 1. Phoenix 2.0">
+<link rel="stylesheet" href="../../../../../../doc/src/boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
+<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">
<link rel="next" href="wrap_up.html" title="Wrap Up">
</head>
@@ -13,18 +13,19 @@
<table cellpadding="2" width="100%"><tr>
<td valign="top"><img alt="Boost C++ Libraries" width="277" height="86" src="../../../../../../boost.png"></td>
<td align="center">Home</td>
-<td align="center">Libraries</td>
+<td align="center">Libraries</td>
<td align="center">People</td>
<td align="center">FAQ</td>
<td align="center">More</td>
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="algorithm.html"><img src="../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="wrap_up.html"><img src="../../../../../../doc/html/images/next.png" alt="Next"></a>
+<a accesskey="p" href="algorithm.html"><img src="../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="wrap_up.html"><img src="../../../../../../doc/src/images/next.png" alt="Next"></a>
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="phoenix.inside_phoenix"></a>Inside Phoenix</h2></div></div></div>
+<a name="phoenix.inside_phoenix"></a><a class="link" href="inside_phoenix.html" title="Inside Phoenix">Inside Phoenix</a>
+</h2></div></div></div>
<div class="toc"><dl>
<dt>Actors In Detail</dt>
<dt>Actor Example</dt>
@@ -39,40 +40,40 @@
 the library. However, a microscopic view might prove to be beneficial to moderate
 to advanced programmers who wish to extend the library.
 
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="phoenix.inside_phoenix.actors_in_detail"></a>Actors In Detail</h3></div></div></div>
-<a name="phoenix.inside_phoenix.actors_in_detail.actor_concept"></a><h3>
-<a name="id495846"></a>
- <a href="inside_phoenix.html#phoenix.inside_phoenix.actors_in_detail.actor_concept">Actor
+<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 class="link" href="inside_phoenix.html#phoenix.inside_phoenix.actors_in_detail.actor_concept">Actor
 Concept</a>
- </h3>
+ </h4>

- The main concept is the <tt class="computeroutput">Actor</tt>.
+ The main concept is the <code class="computeroutput">Actor</code>.
 Actors are function objects (that can accept 0 to N arguments (where N is
 a predefined maximum).
 
<div class="note"><table border="0" summary="Note">
<tr>
-<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../../../../../../doc/html/images/note.png"></td>
+<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../../../../../../doc/src/images/note.png"></td>
<th align="left">Note</th>
</tr>
-<tr><td colspan="2" align="left" valign="top">
- You can set <tt class="computeroutput">PHOENIX_LIMIT</tt>,
- the predefined maximum arity an actor can take. By default, <tt class="computeroutput">PHOENIX_LIMIT</tt> is set to 10.
+<tr><td align="left" valign="top">
+ You can set <code class="computeroutput">PHOENIX_LIMIT</code>,
+ the predefined maximum arity an actor can take. By default, <code class="computeroutput">PHOENIX_LIMIT</code> is set to 10.
 </td></tr>
</table></div>
-<a name="phoenix.inside_phoenix.actors_in_detail.actor_template_class"></a><h3>
-<a name="id495923"></a>
- <a href="inside_phoenix.html#phoenix.inside_phoenix.actors_in_detail.actor_template_class">actor
+<a name="phoenix.inside_phoenix.actors_in_detail.actor_template_class"></a><h4>
+<a name="id795408"></a>
+ <a class="link" href="inside_phoenix.html#phoenix.inside_phoenix.actors_in_detail.actor_template_class">actor
 template class</a>
- </h3>
+ </h4>

- The <tt class="computeroutput">actor</tt> template class
- models the <tt class="computeroutput">Actor</tt> concept:
+ The <code class="computeroutput">actor</code> template class
+ models the <code class="computeroutput">Actor</code> concept:
 
-<pre class="programlisting">
-template <typename Eval>
+<pre class="programlisting">template <typename Eval>
struct actor : Eval
{
 typedef Eval eval_type;
@@ -103,167 +104,171 @@
};
</pre>
<div class="table">
-<a name="id496708"></a>Table 1.10. Actor Concept Requirements
-<table class="table" summary="Actor Concept Requirements">
+<a name="id796097"></a>Table 1.10. Actor Concept Requirements
+<div class="table-contents"><table class="table" summary="Actor Concept Requirements">
<colgroup>
<col>
<col>
</colgroup>
<thead><tr>
<th>
- 
- Expression
- 
- </th>
+ 
+ Expression
+ 
+ </th>
<th>
- 
- Result/Semantics
- 
- </th>
+ 
+ Result/Semantics
+ 
+ </th>
</tr></thead>
<tbody>
<tr>
<td>
- 
- <tt class="computeroutput">T::eval_type</tt>
- 
- </td>
+ 
+ <code class="computeroutput">T::eval_type</code>
+ 
+ </td>
<td>
- 
- The actor's Eval type
- 
- </td>
+ 
+ The actor's Eval type
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">T()</tt>
- 
- </td>
+ 
+ <code class="computeroutput">T()</code>
+ 
+ </td>
<td>
- 
- Default Constructor
- 
- </td>
+ 
+ Default Constructor
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">T(base)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">T(base)</code>
+ 
+ </td>
<td>
- 
- Constructor from Eval
- 
- </td>
+ 
+ Constructor from Eval
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">T(arg0, arg1, ..., argN)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">T(arg0,
+ arg1,
+ ..., argN)</code>
+ 
+ </td>
<td>
- 
- Pass through constructors
- 
- </td>
+ 
+ Pass through constructors
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">x(arg0, arg1, ..., argN)</tt>
- 
- </td>
+ 
+ <code class="computeroutput">x(arg0,
+ arg1,
+ ..., argN)</code>
+ 
+ </td>
<td>
- 
- Function call operators
- 
- </td>
+ 
+ Function call operators
+ 
+ </td>
</tr>
</tbody>
-</table>
+</table></div>
</div>
-<a name="phoenix.inside_phoenix.actors_in_detail.eval_concept"></a><h3>
-<a name="id497020"></a>
- <a href="inside_phoenix.html#phoenix.inside_phoenix.actors_in_detail.eval_concept">Eval
+ <a name="phoenix.inside_phoenix.actors_in_detail.eval_concept"></a><h4>
+<a name="id796380"></a>
+ <a class="link" href="inside_phoenix.html#phoenix.inside_phoenix.actors_in_detail.eval_concept">Eval
 Concept</a>
- </h3>
+ </h4>

- The <tt class="computeroutput">actor</tt> template class
- has a single template parameter, <tt class="computeroutput">Eval</tt>,
- from which it derives from. While the <tt class="computeroutput">Actor</tt>
- concept represents a function, the <tt class="computeroutput">Eval</tt>
- concept represents the function body. The requirements for <tt class="computeroutput">Eval</tt> are intentionally kept simple, to
+ The <code class="computeroutput">actor</code> template class
+ has a single template parameter, <code class="computeroutput">Eval</code>,
+ from which it derives from. While the <code class="computeroutput">Actor</code>
+ concept represents a function, the <code class="computeroutput">Eval</code>
+ concept represents the function body. The requirements for <code class="computeroutput">Eval</code> are intentionally kept simple, to
 make it easy to write models of the concept. We shall see an example in the
- next section.
+ <a class="link" href="inside_phoenix.html#phoenix.inside_phoenix.actor_example" title="Actor Example">next section</a>.
 
<div class="table">
-<a name="id497115"></a>Table 1.11. Eval Concept Requirements
-<table class="table" summary="Eval Concept Requirements">
+<a name="id796466"></a>Table 1.11. Eval Concept Requirements
+<div class="table-contents"><table class="table" summary="Eval Concept Requirements">
<colgroup>
<col>
<col>
</colgroup>
<thead><tr>
<th>
- 
- Expression
- 
- </th>
+ 
+ Expression
+ 
+ </th>
<th>
- 
- Result/Semantics
- 
- </th>
+ 
+ Result/Semantics
+ 
+ </th>
</tr></thead>
<tbody>
<tr>
<td>
- 
- <tt class="computeroutput">return x.eval(env)</tt>
- 
- </td>
-<td>
- 
- Evaluates the function (see Environment below)
- 
- </td>
+ 
+ <code class="computeroutput">return x.eval(env)</code>
+ 
+ </td>
+<td>
+ 
+ Evaluates the function (see Environment below)
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">T::result<Env>::type</tt>
- 
- </td>
-<td>
- 
- The return type of eval (see Environment below)
- 
- </td>
+ 
+ <code class="computeroutput">T::result<Env>::type</code>
+ 
+ </td>
+<td>
+ 
+ The return type of eval (see Environment below)
+ 
+ </td>
</tr>
</tbody>
-</table>
+</table></div>
</div>
-<a name="phoenix.inside_phoenix.actors_in_detail.constructors"></a><h3>
-<a name="id497287"></a>
- Constructors
- </h3>
+ <a name="phoenix.inside_phoenix.actors_in_detail.constructors"></a><h4>
+<a name="id796619"></a>
+ <a class="link" href="inside_phoenix.html#phoenix.inside_phoenix.actors_in_detail.constructors">Constructors</a>
+ </h4>

 In addition to a default constructor and an constructor from a Eval object,
 there are templated (pass through) constructors for 1 to N arguments (N ==
- <tt class="computeroutput">PHOENIX_LIMIT</tt>). These constructors
- simply forward the arguments to the <tt class="computeroutput">base</tt>.
+ <code class="computeroutput">PHOENIX_LIMIT</code>). These constructors
+ simply forward the arguments to the <code class="computeroutput">base</code>.
 
<div class="note"><table border="0" summary="Note">
<tr>
-<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../../../../../../doc/html/images/note.png"></td>
+<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../../../../../../doc/src/images/note.png"></td>
<th align="left">Note</th>
</tr>
-<tr><td colspan="2" align="left" valign="top">
+<tr><td align="left" valign="top">

- Parametric Base Class Pattern
+ Parametric Base Class Pattern
 

 Notice that actor derives from its template argument Eval. This is the
@@ -277,172 +282,168 @@
 
</td></tr>
</table></div>
-<a name="phoenix.inside_phoenix.actors_in_detail.function_call_operators"></a><h3>
-<a name="id497372"></a>
- <a href="inside_phoenix.html#phoenix.inside_phoenix.actors_in_detail.function_call_operators">Function
+<a name="phoenix.inside_phoenix.actors_in_detail.function_call_operators"></a><h4>
+<a name="id796684"></a>
+ <a class="link" href="inside_phoenix.html#phoenix.inside_phoenix.actors_in_detail.function_call_operators">Function
 Call Operators</a>
- </h3>
+ </h4>

- There are N function call operators for 0 to N arguments (N == <tt class="computeroutput">PHOENIX_LIMIT</tt>). The actor class accepts
- the arguments and forwards the arguments to the actor's base <tt class="computeroutput">Eval</tt> for evaluation.
+ There are N function call operators for 0 to N arguments (N == <code class="computeroutput">PHOENIX_LIMIT</code>). The actor class accepts
+ the arguments and forwards the arguments to the actor's base <code class="computeroutput">Eval</code> for evaluation.
 
<div class="note"><table border="0" summary="Note">
<tr>
-<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../../../../../../doc/html/images/note.png"></td>
+<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../../../../../../doc/src/images/note.png"></td>
<th align="left">Note</th>
</tr>
-<tr><td colspan="2" align="left" valign="top">
+<tr><td align="left" valign="top">

- Forwarding Function Problem
+ Forwarding Function Problem
 

 The function call operators cannot accept non-const temporaries and literal
 constants. There is a known issue with current C++ called the "<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2002/n1385.htm" target="_top">Forwarding
 Function Problem</a>". The problem is that given an arbitrary
- function <tt class="computeroutput">F</tt>, using current
- C++ language rules, one cannot create a forwarding function <tt class="computeroutput">FF</tt> that transparently assumes the arguments
- of <tt class="computeroutput">F</tt>. Disallowing non-const
+ function <code class="computeroutput">F</code>, using current
+ C++ language rules, one cannot create a forwarding function <code class="computeroutput">FF</code> that transparently assumes the arguments
+ of <code class="computeroutput">F</code>. Disallowing non-const
 rvalues arguments partially solves the problem but prohibits code such
- as <tt class="computeroutput">f(1, 2, 3);</tt>.
+ as <code class="computeroutput">f(1, 2, 3);</code>.
 
</td></tr>
</table></div>
-<a name="phoenix.inside_phoenix.actors_in_detail.environment"></a><h3>
-<a name="id497544"></a>
- Environment
- </h3>
-
- On an actor function call, before calling the actor's <tt class="computeroutput">Eval::eval</tt>
- for evaluation, the actor creates an environment.
- Basically, the environment packages the arguments in a tuple. The <tt class="computeroutput">Environment</tt> is a concept, of which, the
- <tt class="computeroutput">basic_environment</tt> template
+<a name="phoenix.inside_phoenix.actors_in_detail.environment"></a><h4>
+<a name="id796836"></a>
+ <a class="link" href="inside_phoenix.html#phoenix.inside_phoenix.actors_in_detail.environment">Environment</a>
+ </h4>
+
+ On an actor function call, before calling the actor's <code class="computeroutput">Eval::eval</code>
+ for evaluation, the actor creates an environment.
+ Basically, the environment packages the arguments in a tuple. The <code class="computeroutput">Environment</code> is a concept, of which, the
+ <code class="computeroutput">basic_environment</code> template
 class is a model of.
 
<div class="table">
-<a name="id497623"></a>Table 1.12. Environment Concept Requirements
-<table class="table" summary="Environment Concept Requirements">
+<a name="id796904"></a>Table 1.12. Environment Concept Requirements
+<div class="table-contents"><table class="table" summary="Environment Concept Requirements">
<colgroup>
<col>
<col>
</colgroup>
<thead><tr>
<th>
- 
- Expression
- 
- </th>
+ 
+ Expression
+ 
+ </th>
<th>
- 
- Result/Semantics
- 
- </th>
+ 
+ Result/Semantics
+ 
+ </th>
</tr></thead>
<tbody>
<tr>
<td>
- 
- <tt class="computeroutput">x.args()</tt>
- 
- </td>
+ 
+ <code class="computeroutput">x.args()</code>
+ 
+ </td>
<td>
- 
- The arguments in a tie (a tuple of references)
- 
- </td>
+ 
+ The arguments in a tie (a tuple of references)
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">T::args_type</tt>
- 
- </td>
+ 
+ <code class="computeroutput">T::args_type</code>
+ 
+ </td>
<td>
- 
- The arguments' types in an MPL sequence
- 
- </td>
+ 
+ The arguments' types in an MPL sequence
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">T::tie_type</tt>
- 
- </td>
+ 
+ <code class="computeroutput">T::tie_type</code>
+ 
+ </td>
<td>
- 
- The tie (tuple of references) type
- 
- </td>
+ 
+ The tie (tuple of references) type
+ 
+ </td>
</tr>
</tbody>
-</table>
+</table></div>
</div>
-
+ 
 Schematically:
 

 <img src="../images/funnel_in.png" alt="funnel_in">
 

- Other parts of the library (e.g. the scope module) extends the <tt class="computeroutput">Environment</tt> concept to hold other information
+ Other parts of the library (e.g. the scope module) extends the <code class="computeroutput">Environment</code> concept to hold other information
 such as local variables, etc.
 
-<a name="phoenix.inside_phoenix.actors_in_detail.apply_actor"></a><h3>
-<a name="id497839"></a>
- apply_actor
- </h3>
+<a name="phoenix.inside_phoenix.actors_in_detail.apply_actor"></a><h4>
+<a name="id797100"></a>
+ <a class="link" href="inside_phoenix.html#phoenix.inside_phoenix.actors_in_detail.apply_actor">apply_actor</a>
+ </h4>

- <tt class="computeroutput">apply_actor</tt> is a standard
- MPL style metafunction that simply calls the Action's <tt class="computeroutput">result</tt>
+ <code class="computeroutput">apply_actor</code> is a standard
+ MPL style metafunction that simply calls the Action's <code class="computeroutput">result</code>
 nested metafunction:
 
-<pre class="programlisting">
-template <typename Action, typename Env>
+<pre class="programlisting">template <typename Action, typename Env>
struct apply_actor
{
 typedef typename Action::template result<Env>::type type;
};
</pre>

- After evaluating the arguments and doing some computation, the <tt class="computeroutput">eval</tt> member function returns something
- back to the client. To do this, the forwarding function (the actor's <tt class="computeroutput">operator()</tt>)
+ After evaluating the arguments and doing some computation, the <code class="computeroutput">eval</code> member function returns something
+ back to the client. To do this, the forwarding function (the actor's <code class="computeroutput">operator()</code>)
 needs to know the return type of the eval member function that it is calling.
- For this purpose, models of <tt class="computeroutput">Eval</tt>
+ For this purpose, models of <code class="computeroutput">Eval</code>
 are required to provide a nested template class:
 
-<pre class="programlisting">
-template <typename Env>
+<pre class="programlisting">template <typename Env>
struct result;
</pre>

- This nested class provides the result type information returned by the <tt class="computeroutput">Eval</tt>'s <tt class="computeroutput">eval</tt>
- member function. The nested template class <tt class="computeroutput">result</tt>
- should have a typedef <tt class="computeroutput">type</tt>
- that reflects the return type of its member function <tt class="computeroutput">eval</tt>.
+ This nested class provides the result type information returned by the <code class="computeroutput">Eval</code>'s <code class="computeroutput">eval</code>
+ member function. The nested template class <code class="computeroutput">result</code>
+ should have a typedef <code class="computeroutput">type</code>
+ that reflects the return type of its member function <code class="computeroutput">eval</code>.
 

- For reference, here's a typical <tt class="computeroutput">actor::operator()</tt> that accepts two arguments:
+ For reference, here's a typical <code class="computeroutput">actor::operator()</code> that accepts two arguments:
 
-<pre class="programlisting">
-template <typename T0, typename T1>
+<pre class="programlisting">template <typename T0, typename T1>
typename apply_actor<eval_type, basic_environment<T0, T1> >::type
operator()(T0& _0, T1& _1) const
{
 return eval_type::eval(basic_environment<T0, T1>(_0, _1));
}
</pre>
-<a name="phoenix.inside_phoenix.actors_in_detail.actor_result"></a><h3>
-<a name="id498520"></a>
- actor_result
- </h3>
+<a name="phoenix.inside_phoenix.actors_in_detail.actor_result"></a><h4>
+<a name="id797697"></a>
+ <a class="link" href="inside_phoenix.html#phoenix.inside_phoenix.actors_in_detail.actor_result">actor_result</a>
+ </h4>

- For reasons of symmetry to the family of <tt class="computeroutput">actor::operator()</tt> there is a special metafunction usable
- for actor result type calculation named <tt class="computeroutput">actor_result</tt>.
+ For reasons of symmetry to the family of <code class="computeroutput">actor::operator()</code> there is a special metafunction usable
+ for actor result type calculation named <code class="computeroutput">actor_result</code>.
 This metafunction allows us to directly to specify the types of the parameters
- to be passed to the <tt class="computeroutput">actor::operator()</tt> function. Here's a typical <tt class="computeroutput">actor_result</tt> that accepts two arguments:
+ to be passed to the <code class="computeroutput">actor::operator()</code> function. Here's a typical <code class="computeroutput">actor_result</code> that accepts two arguments:
 
-<pre class="programlisting">
-template <typename Action, typename T0, typename T1>
+<pre class="programlisting">template <typename Action, typename T0, typename T1>
struct actor_result
{
 typedef basic_environment<T0, T1> env_type;
@@ -450,19 +451,19 @@
};
</pre>
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="phoenix.inside_phoenix.actor_example"></a>Actor Example</h3></div></div></div>
+<a name="phoenix.inside_phoenix.actor_example"></a><a class="link" href="inside_phoenix.html#phoenix.inside_phoenix.actor_example" title="Actor Example">Actor Example</a>
+</h3></div></div></div>

 Let us see a very simple prototypical example of an actor. This is not a
- toy example. This is actually part of the library. Remember the reference?.
+ toy example. This is actually part of the library. Remember the <a class="link" href="primitives.html#phoenix.primitives.references" title="References"><code class="computeroutput">reference</code></a>?.
 

- First, we have a model of the <tt class="computeroutput">Eval</tt>
- concept: the <tt class="computeroutput">reference</tt>:
+ First, we have a model of the <code class="computeroutput">Eval</code>
+ concept: the <code class="computeroutput">reference</code>:
 
-<pre class="programlisting">
-template <typename T>
+<pre class="programlisting">template <typename T>
struct reference
{
 template <typename Env>
@@ -484,14 +485,13 @@
};
</pre>

- Models of <tt class="computeroutput">Eval</tt> are never
+ Models of <code class="computeroutput">Eval</code> are never
 created directly and its instances never exist alone. We have to wrap it
- inside the <tt class="computeroutput">actor</tt> template
- class to be useful. The <tt class="computeroutput">ref</tt>
+ inside the <code class="computeroutput">actor</code> template
+ class to be useful. The <code class="computeroutput">ref</code>
 template function does this for us:
 
-<pre class="programlisting">
-template <typename T>
+<pre class="programlisting">template <typename T>
actor<reference<T> > const
ref(T& v)
{
@@ -499,69 +499,68 @@
}
</pre>

- The <tt class="computeroutput">reference</tt> template class
- conforms to the Eval concept. It has a nested <tt class="computeroutput">result</tt> metafunction that reflects the return
- type of its <tt class="computeroutput">eval</tt> member function,
- which peforms the actual function. <tt class="computeroutput">reference<T></tt>
- stores a reference to a <tt class="computeroutput">T</tt>.
- Its <tt class="computeroutput">eval</tt> member function
- simply returns the reference. It does not make use of the environment <tt class="computeroutput">Env</tt>.
+ The <code class="computeroutput">reference</code> template class
+ conforms to the <a class="link" href="inside_phoenix.html#phoenix.inside_phoenix.actors_in_detail.eval_concept"><code class="computeroutput">Eval</code></a> concept. It has a nested <code class="computeroutput">result</code> metafunction that reflects the return
+ type of its <code class="computeroutput">eval</code> member function,
+ which peforms the actual function. <code class="computeroutput">reference<T></code>
+ stores a reference to a <code class="computeroutput">T</code>.
+ Its <code class="computeroutput">eval</code> member function
+ simply returns the reference. It does not make use of the environment <code class="computeroutput">Env</code>.
 

 Pretty simple...
 
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="phoenix.inside_phoenix.composites_in_detail"></a><a href="inside_phoenix.html#phoenix.inside_phoenix.composites_in_detail" title="Composites
- In Detail">Composites
- In Detail</a></h3></div></div></div>
+<a name="phoenix.inside_phoenix.composites_in_detail"></a><a class="link" href="inside_phoenix.html#phoenix.inside_phoenix.composites_in_detail" title="Composites In Detail">Composites
+ In Detail</a>
+</h3></div></div></div>

 We stated before that composites are actors that are composed of zero or
- more actors (see Composite). This
+ more actors (see <a class="link" href="composite.html" title="Composite">Composite</a>). This
 is not quite accurate. The definition was sufficient at that point where
 we opted to keep things simple and not bury the reader with details which
 she might not need anyway.
 

- Actually, a composite is a model of the Eval concept (more on this later).
+ Actually, a composite is a model of the <a class="link" href="inside_phoenix.html#phoenix.inside_phoenix.actors_in_detail.eval_concept"><code class="computeroutput">Eval</code></a> concept (more on this later).
 At the same time, it is also composed of 0..N (where N is a predefined maximum)
- Eval instances and an eval policy.
- The individual Eval instances are stored in a tuple.
+ <a class="link" href="inside_phoenix.html#phoenix.inside_phoenix.actors_in_detail.eval_concept"><code class="computeroutput">Eval</code></a> instances and an eval policy.
+ The individual <a class="link" href="inside_phoenix.html#phoenix.inside_phoenix.actors_in_detail.eval_concept"><code class="computeroutput">Eval</code></a> instances are stored in a tuple.
 
<div class="note"><table border="0" summary="Note">
<tr>
-<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../../../../../../doc/html/images/note.png"></td>
+<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../../../../../../doc/src/images/note.png"></td>
<th align="left">Note</th>
</tr>
-<tr><td colspan="2" align="left" valign="top">
+<tr><td align="left" valign="top">
 In a sense, the original definition of "composite", more or less,
- will do just fine because Eval instances never exist alone
- and are always wrapped in an <tt class="computeroutput">actor</tt>
+ will do just fine because <a class="link" href="inside_phoenix.html#phoenix.inside_phoenix.actors_in_detail.eval_concept"><code class="computeroutput">Eval</code></a> instances never exist alone
+ and are always wrapped in an <code class="computeroutput">actor</code>
 template class which inherits from it anyway. The resulting actor IS-AN
- Eval.
+ <a class="link" href="inside_phoenix.html#phoenix.inside_phoenix.actors_in_detail.eval_concept"><code class="computeroutput">Eval</code></a>.
 </td></tr>
</table></div>
<div class="note"><table border="0" summary="Note">
<tr>
-<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../../../../../../doc/html/images/note.png"></td>
+<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../../../../../../doc/src/images/note.png"></td>
<th align="left">Note</th>
</tr>
-<tr><td colspan="2" align="left" valign="top">
- You can set <tt class="computeroutput">PHOENIX_COMPOSITE_LIMIT</tt>,
- the predefined maximum <tt class="computeroutput">Eval</tt>s
- (actors) a composite can take. By default, <tt class="computeroutput">PHOENIX_COMPOSITE_LIMIT</tt>
- is set to <tt class="computeroutput">PHOENIX_LIMIT</tt>
- (See Actors).
+<tr><td align="left" valign="top">
+ You can set <code class="computeroutput">PHOENIX_COMPOSITE_LIMIT</code>,
+ the predefined maximum <code class="computeroutput">Eval</code>s
+ (actors) a composite can take. By default, <code class="computeroutput">PHOENIX_COMPOSITE_LIMIT</code>
+ is set to <code class="computeroutput">PHOENIX_LIMIT</code>
+ (See <a class="link" href="actors.html" title="Actors">Actors</a>).
 </td></tr>
</table></div>
-<a name="phoenix.inside_phoenix.composites_in_detail.composite_template_class"></a><h2>
-<a name="id499816"></a>
- <a href="inside_phoenix.html#phoenix.inside_phoenix.composites_in_detail.composite_template_class">composite
+<a name="phoenix.inside_phoenix.composites_in_detail.composite_template_class"></a><h3>
+<a name="id798837"></a>
+ <a class="link" href="inside_phoenix.html#phoenix.inside_phoenix.composites_in_detail.composite_template_class">composite
 template class</a>
- </h2>
-<pre class="programlisting">
-template <typename EvalPolicy, typename EvalTuple>
+ </h3>
+<pre class="programlisting">template <typename EvalPolicy, typename EvalTuple>
struct composite : EvalTuple
{
 typedef EvalTuple base_type;
@@ -589,27 +588,27 @@
 eval(Env const& env) const;
};
</pre>
-<a name="phoenix.inside_phoenix.composites_in_detail.evaltuple"></a><h2>
-<a name="id500422"></a>
- EvalTuple
- </h2>
-
- <tt class="computeroutput">EvalTuple</tt>, holds all the
- Eval instances. The <tt class="computeroutput">composite</tt> template class inherits from
- it. In addition to a default constructor and a constructor from an <tt class="computeroutput">EvalTuple</tt> object, there are templated (pass
- through) constructors for 1 to N arguments (again, where N == <tt class="computeroutput">PHOENIX_COMPOSITE_LIMIT</tt>). These constructors
- simply forward the arguments to the <tt class="computeroutput">EvalTuple</tt>
+<a name="phoenix.inside_phoenix.composites_in_detail.evaltuple"></a><h3>
+<a name="id799366"></a>
+ <a class="link" href="inside_phoenix.html#phoenix.inside_phoenix.composites_in_detail.evaltuple">EvalTuple</a>
+ </h3>
+
+ <code class="computeroutput">EvalTuple</code>, holds all the
+ <a class="link" href="inside_phoenix.html#phoenix.inside_phoenix.actors_in_detail.eval_concept"><code class="computeroutput">Eval</code></a> instances. The <code class="computeroutput">composite</code> template class inherits from
+ it. In addition to a default constructor and a constructor from an <code class="computeroutput">EvalTuple</code> object, there are templated (pass
+ through) constructors for 1 to N arguments (again, where N == <code class="computeroutput">PHOENIX_COMPOSITE_LIMIT</code>). These constructors
+ simply forward the arguments to the <code class="computeroutput">EvalTuple</code>
 base class.
 
-<a name="phoenix.inside_phoenix.composites_in_detail.evalpolicy"></a><h2>
-<a name="id500533"></a>
- EvalPolicy
- </h2>
-
- The composite's <tt class="computeroutput">eval</tt> member
- function calls its <tt class="computeroutput">EvalPolicy</tt>'s
- <tt class="computeroutput">eval</tt> member function (a static
- member function) passing in the environment
+<a name="phoenix.inside_phoenix.composites_in_detail.evalpolicy"></a><h3>
+<a name="id799463"></a>
+ <a class="link" href="inside_phoenix.html#phoenix.inside_phoenix.composites_in_detail.evalpolicy">EvalPolicy</a>
+ </h3>
+
+ The composite's <code class="computeroutput">eval</code> member
+ function calls its <code class="computeroutput">EvalPolicy</code>'s
+ <code class="computeroutput">eval</code> member function (a static
+ member function) passing in the <a class="link" href="inside_phoenix.html#phoenix.inside_phoenix.actors_in_detail.environment">environment</a>
 and each of its actors, in parallel. The following diagram illustrates what's
 happening:
 
@@ -617,67 +616,68 @@
 <img src="../images/funnel_out.png" alt="funnel_out">
 
<div class="table">
-<a name="id500623"></a>Table 1.13. EvalPolicy Requirements
-<table class="table" summary="EvalPolicy Requirements">
+<a name="id799542"></a>Table 1.13. EvalPolicy Requirements
+<div class="table-contents"><table class="table" summary="EvalPolicy Requirements">
<colgroup>
<col>
<col>
</colgroup>
<thead><tr>
<th>
- 
- Expression
- 
- </th>
+ 
+ Expression
+ 
+ </th>
<th>
- 
- Result/Semantics
- 
- </th>
+ 
+ Result/Semantics
+ 
+ </th>
</tr></thead>
<tbody>
<tr>
<td>
- 
- <tt class="computeroutput">x.eval<RT>(env, eval0,
- eval1,
- ..., evalN)</tt>
- 
- </td>
-<td>
- 
- Evaluate the composite
- 
- </td>
+ 
+ <code class="computeroutput">x.eval<RT>(env,
+ eval0,
+ eval1,
+ ..., evalN)</code>
+ 
+ </td>
+<td>
+ 
+ Evaluate the composite
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <tt class="computeroutput">T::result<Env, Eval0,
- Eval1,
- Eval2,
- ..., EvalN>::type</tt>
- 
- </td>
-<td>
- 
- The return type of eval
- 
- </td>
+ 
+ <code class="computeroutput">T::result<Env,
+ Eval0,
+ Eval1,
+ Eval2,
+ ..., EvalN>::type</code>
+ 
+ </td>
+<td>
+ 
+ The return type of eval
+ 
+ </td>
</tr>
</tbody>
-</table>
+</table></div>
</div>
-
- The <tt class="computeroutput">EvalPolicy</tt> is expected
- to have a nested template class <tt class="computeroutput">result</tt>
- which has a typedef <tt class="computeroutput">type</tt>
- that reflects the return type of its member function <tt class="computeroutput">eval</tt>.
+ 
+ The <code class="computeroutput">EvalPolicy</code> is expected
+ to have a nested template class <code class="computeroutput">result</code>
+ which has a typedef <code class="computeroutput">type</code>
+ that reflects the return type of its member function <code class="computeroutput">eval</code>.
 Here's a typical example of the composite's eval member function for a 2-actor
 composite:
 
-<pre class="programlisting">
-template <typename Env>
+<pre class="programlisting">template <typename Env>
typename result<Env>::type
eval(Env const& env) const
{
@@ -690,9 +690,10 @@
}
</pre>
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="phoenix.inside_phoenix.composing"></a>Composing</h3></div></div></div>
+<a name="phoenix.inside_phoenix.composing"></a><a class="link" href="inside_phoenix.html#phoenix.inside_phoenix.composing" title="Composing">Composing</a>
+</h3></div></div></div>
<div class="toc"><dl>
<dt>compose</dt>
<dt>as_composite</dt>
@@ -704,73 +705,68 @@
 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 DSEL in action in the preceding sections. It is most evident in
- the Statement section.
+ the <a class="link" href="composite.html#phoenix.composite.statement" title="Statement">Statement</a> section.
 

 There are some facilities in the library to make composition of composites
- easier. We have a set of overloaded <tt class="computeroutput">compose</tt>
- functions and an <tt class="computeroutput">as_composite</tt>
+ easier. We have a set of overloaded <code class="computeroutput">compose</code>
+ functions and an <code class="computeroutput">as_composite</code>
 metafunction. Together, these helpers make composing a breeze. We'll provide
- an <a href="inside_phoenix.html#phoenix.inside_phoenix.composing.composite_example" title="Composite
- Example">example
+ an <a class="link" href="inside_phoenix.html#phoenix.inside_phoenix.composing.composite_example" title="Composite Example">example
 of a composite</a> later to see why.
 
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="phoenix.inside_phoenix.composing.compose"></a>compose</h4></div></div></div>
-<pre class="programlisting">
-compose<EvalPolicy>(arg0, arg1, arg2, ..., argN);
+<a name="phoenix.inside_phoenix.composing.compose"></a><a class="link" href="inside_phoenix.html#phoenix.inside_phoenix.composing.compose" title="compose">compose</a>
+</h4></div></div></div>
+<pre class="programlisting">compose<EvalPolicy>(arg0, arg1, arg2, ..., argN);
</pre>

- Given an EvalPolicy and some arguments
- <tt class="computeroutput">arg0</tt>...argN, returns a
- proper <tt class="computeroutput">composite</tt>. The arguments
+ Given an <a class="link" href="inside_phoenix.html#phoenix.inside_phoenix.composites_in_detail.evalpolicy"><code class="computeroutput">EvalPolicy</code></a> and some arguments
+ <code class="computeroutput">arg0</code>...argN, returns a
+ proper <code class="computeroutput">composite</code>. The arguments
 may or may not be phoenix actors (primitives of composites). If not, the
 arguments are converted to actors appropriately. For example:
 
-<pre class="programlisting">
-compose<X>(3)
+<pre class="programlisting">compose<X>(3)
</pre>

- converts the argument <tt class="computeroutput">3</tt> to
- an <tt class="computeroutput">actor<value<int> >(3)</tt>.
+ converts the argument <code class="computeroutput">3</code> to
+ an <code class="computeroutput">actor<value<int> >(3)</code>.
 
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="phoenix.inside_phoenix.composing.as_composite"></a>as_composite</h4></div></div></div>
-<pre class="programlisting">
-as_composite<EvalPolicy, Arg0, Arg1, Arg2, ..., ArgN>::type
+<a name="phoenix.inside_phoenix.composing.as_composite"></a><a class="link" href="inside_phoenix.html#phoenix.inside_phoenix.composing.as_composite" title="as_composite">as_composite</a>
+</h4></div></div></div>
+<pre class="programlisting">as_composite<EvalPolicy, Arg0, Arg1, Arg2, ..., ArgN>::type
</pre>

- This is the metafunction counterpart of <tt class="computeroutput">compose</tt>.
- Given an EvalPolicy and some argument types
- <tt class="computeroutput">Arg0</tt>...ArgN, returns a
- proper <tt class="computeroutput">composite</tt> type.
+ This is the metafunction counterpart of <code class="computeroutput">compose</code>.
+ Given an <a class="link" href="inside_phoenix.html#phoenix.inside_phoenix.composites_in_detail.evalpolicy"><code class="computeroutput">EvalPolicy</code></a> and some argument types
+ <code class="computeroutput">Arg0</code>...ArgN, returns a
+ proper <code class="computeroutput">composite</code> type.
 For example:
 
-<pre class="programlisting">
-as_composite<X, int>::type
+<pre class="programlisting">as_composite<X, int>::type
</pre>

- is the composite type of the <tt class="computeroutput">compose<X>(3)</tt>
+ is the composite type of the <code class="computeroutput">compose<X>(3)</code>
 expression above.
 
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="phoenix.inside_phoenix.composing.composite_example"></a><a href="inside_phoenix.html#phoenix.inside_phoenix.composing.composite_example" title="Composite
- Example">Composite
- Example</a></h4></div></div></div>
+<a name="phoenix.inside_phoenix.composing.composite_example"></a><a class="link" href="inside_phoenix.html#phoenix.inside_phoenix.composing.composite_example" title="Composite Example">Composite
+ Example</a>
+</h4></div></div></div>

 Now, let's examine an example. Again, this is not a toy example. This is
- actually part of the library. Remember the <a href="composite.html#phoenix.composite.statement.while__statement" title="while_
- Statement"><tt class="computeroutput">while_</tt></a> lazy statement? Putting
+ actually part of the library. Remember the <a class="link" href="composite.html#phoenix.composite.statement.while__statement" title="while_ Statement"><code class="computeroutput">while_</code></a> lazy statement? Putting
 together everything we've learned so far, we will present it here in its
 entirety (verbatim):
 
-<pre class="programlisting">
-struct while_eval
+<pre class="programlisting">struct while_eval
{
 template <typename Env, typename Cond, typename Do>
 struct result
@@ -811,26 +807,24 @@
}
</pre>

- <tt class="computeroutput">while_eval</tt> is an example
- of an EvalPolicy. <tt class="computeroutput">while_gen</tt>
- and <tt class="computeroutput">while_</tt> are the expression
+ <code class="computeroutput">while_eval</code> is an example
+ of an <a class="link" href="inside_phoenix.html#phoenix.inside_phoenix.composites_in_detail.evalpolicy"><code class="computeroutput">EvalPolicy</code></a>. <code class="computeroutput">while_gen</code>
+ and <code class="computeroutput">while_</code> are the expression
 template front ends. Let's break this apart to understand what's happening.
 Let's start at the bottom. It's easier that way.
 

 When you write:
 
-<pre class="programlisting">
-while_(cond)
+<pre class="programlisting">while_(cond)
</pre>

- we generate an instance of <tt class="computeroutput">while_gen<Cond></tt>, where <tt class="computeroutput">Cond</tt>
- is the type of <tt class="computeroutput">cond</tt>. <tt class="computeroutput">cond</tt> can be an arbitrarily complex actor
- expression. The <tt class="computeroutput">while_gen</tt>
- template class has an <tt class="computeroutput">operator[]</tt> accepting another expression. If we write:
+ we generate an instance of <code class="computeroutput">while_gen<Cond></code>, where <code class="computeroutput">Cond</code>
+ is the type of <code class="computeroutput">cond</code>. <code class="computeroutput">cond</code> can be an arbitrarily complex actor
+ expression. The <code class="computeroutput">while_gen</code>
+ template class has an <code class="computeroutput">operator[]</code> accepting another expression. If we write:
 
-<pre class="programlisting">
-while_(cond)
+<pre class="programlisting">while_(cond)
[
 do_
]
@@ -838,17 +832,15 @@

 it will generate a proper composite with the type:
 
-<pre class="programlisting">
-as_composite<while_eval, Cond, Do>::type
+<pre class="programlisting">as_composite<while_eval, Cond, Do>::type
</pre>

- where <tt class="computeroutput">Cond</tt> is the type
- of <tt class="computeroutput">cond</tt> and <tt class="computeroutput">Do</tt> is the type of <tt class="computeroutput">do_</tt>.
- Notice how we are using phoenix's composition
- (<tt class="computeroutput">compose</tt> and <tt class="computeroutput">as_composite</tt>) mechanisms here
+ where <code class="computeroutput">Cond</code> is the type
+ of <code class="computeroutput">cond</code> and <code class="computeroutput">Do</code> is the type of <code class="computeroutput">do_</code>.
+ Notice how we are using phoenix's <a class="link" href="inside_phoenix.html#phoenix.inside_phoenix.composing" title="Composing">composition</a>
+ (<code class="computeroutput">compose</code> and <code class="computeroutput">as_composite</code>) mechanisms here
 
-<pre class="programlisting">
-template <typename Do>
+<pre class="programlisting">template <typename Do>
actor<typename as_composite<while_eval, Cond, Do>::type>
operator[](Do const& do_) const
{
@@ -856,25 +848,25 @@
}
</pre>

- Finally, the <tt class="computeroutput">while_eval</tt>
+ Finally, the <code class="computeroutput">while_eval</code>
 does its thing:
 
-<pre class="programlisting">
-while (cond.eval(env))
+<pre class="programlisting">while (cond.eval(env))
 do_.eval(env);
</pre>

- <tt class="computeroutput">cond</tt> and <tt class="computeroutput">do_</tt>, at this point, are instances of
- Eval. <tt class="computeroutput">cond</tt>
- and <tt class="computeroutput">do_</tt> are the Eval elements held by the composite's
- EvalTuple. <tt class="computeroutput">env</tt>
- is the Environment.
+ <code class="computeroutput">cond</code> and <code class="computeroutput">do_</code>, at this point, are instances of
+ <a class="link" href="inside_phoenix.html#phoenix.inside_phoenix.actors_in_detail.eval_concept"><code class="computeroutput">Eval</code></a>. <code class="computeroutput">cond</code>
+ and <code class="computeroutput">do_</code> are the <a class="link" href="inside_phoenix.html#phoenix.inside_phoenix.actors_in_detail.eval_concept"><code class="computeroutput">Eval</code></a> elements held by the composite's
+ <a class="link" href="inside_phoenix.html#phoenix.inside_phoenix.composites_in_detail.evaltuple"><code class="computeroutput">EvalTuple</code></a>. <code class="computeroutput">env</code>
+ is the <a class="link" href="inside_phoenix.html#phoenix.inside_phoenix.actors_in_detail.environment"><code class="computeroutput">Environment</code></a>.
 
</div>
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="phoenix.inside_phoenix.extending"></a>Extending</h3></div></div></div>
+<a name="phoenix.inside_phoenix.extending"></a><a class="link" href="inside_phoenix.html#phoenix.inside_phoenix.extending" title="Extending">Extending</a>
+</h3></div></div></div>

 We've shown how it is very easy to extend phoenix by writing new primitives
 and composites. The modular design of Phoenix makes it extremely extensible.
@@ -894,7 +886,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2002-2005 Joel
+<td align="right"><div class="copyright-footer">Copyright © 2002-2005 Joel
 de Guzman, Dan Marsden
 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)
@@ -903,7 +895,7 @@
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="algorithm.html"><img src="../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="wrap_up.html"><img src="../../../../../../doc/html/images/next.png" alt="Next"></a>
+<a accesskey="p" href="algorithm.html"><img src="../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="wrap_up.html"><img src="../../../../../../doc/src/images/next.png" alt="Next"></a>
</div>
</body>
</html>

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-07-19 16:15:52 EDT (Mon, 19 Jul 2010)
@@ -1,30 +1,31 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Introduction</title>
-<link rel="stylesheet" href="../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.66.1">
-<link rel="start" 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">
+<link rel="stylesheet" href="../../../../../../doc/src/boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
+<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">
<link rel="next" href="starter_kit.html" title="Starter Kit">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
<table cellpadding="2" width="100%"><tr>
<td valign="top"><img alt="Boost C++ Libraries" width="277" height="86" src="../../../../../../boost.png"></td>
<td align="center">Home</td>
-<td align="center">Libraries</td>
+<td align="center">Libraries</td>
<td align="center">People</td>
<td align="center">FAQ</td>
<td align="center">More</td>
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="../index.html"><img src="../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="starter_kit.html"><img src="../../../../../../doc/html/images/next.png" alt="Next"></a>
+<a accesskey="p" href="../index.html"><img src="../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="starter_kit.html"><img src="../../../../../../doc/src/images/next.png" alt="Next"></a>
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="phoenix.introduction"></a>Introduction</h2></div></div></div>
+<a name="phoenix.introduction"></a><a class="link" href="introduction.html" title="Introduction">Introduction</a>
+</h2></div></div></div>

 <img src="../images/banner.png" alt="banner">
 
@@ -55,7 +56,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2002-2005 Joel
+<td align="right"><div class="copyright-footer">Copyright © 2002-2005 Joel
 de Guzman, Dan Marsden
 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)
@@ -64,7 +65,7 @@
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="../index.html"><img src="../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="starter_kit.html"><img src="../../../../../../doc/html/images/next.png" alt="Next"></a>
+<a accesskey="p" href="../index.html"><img src="../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="starter_kit.html"><img src="../../../../../../doc/src/images/next.png" alt="Next"></a>
</div>
</body>
</html>

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-07-19 16:15:52 EDT (Mon, 19 Jul 2010)
@@ -1,11 +1,11 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Organization</title>
-<link rel="stylesheet" href="../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.66.1">
-<link rel="start" href="../index.html" title="Chapter 1. Phoenix 2.0">
-<link rel="up" href="../index.html" title="Chapter 1. Phoenix 2.0">
+<link rel="stylesheet" href="../../../../../../doc/src/boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
+<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">
<link rel="next" href="actors.html" title="Actors">
</head>
@@ -13,18 +13,19 @@
<table cellpadding="2" width="100%"><tr>
<td valign="top"><img alt="Boost C++ Libraries" width="277" height="86" src="../../../../../../boost.png"></td>
<td align="center">Home</td>
-<td align="center">Libraries</td>
+<td align="center">Libraries</td>
<td align="center">People</td>
<td align="center">FAQ</td>
<td align="center">More</td>
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="basics.html"><img src="../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="actors.html"><img src="../../../../../../doc/html/images/next.png" alt="Next"></a>
+<a accesskey="p" href="basics.html"><img src="../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="actors.html"><img src="../../../../../../doc/src/images/next.png" alt="Next"></a>
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="phoenix.organization"></a>Organization</h2></div></div></div>
+<a name="phoenix.organization"></a><a class="link" href="organization.html" title="Organization">Organization</a>
+</h2></div></div></div>

 Care and attention to detail was given, painstakingly, to the design and implementation
 of Phoenix.
@@ -46,25 +47,25 @@
 The library has grown from the original Phoenix but still comprises only header
 files. There are no object files to link against.
 
-<a name="phoenix.organization.core"></a><h2>
-<a name="id461546"></a>
- Core
- </h2>
+<a name="phoenix.organization.core"></a><h3>
+<a name="id765034"></a>
+ <a class="link" href="organization.html#phoenix.organization.core">Core</a>
+ </h3>

 The lowest two layers comprise the core.
 

- The <tt class="computeroutput">Actor</tt> is the main concept
+ The <code class="computeroutput">Actor</code> is the main concept
 behind the library. Lazy functions are abstracted as actors. There are only
 2 kinds of actors:
 
-<div class="orderedlist"><ol type="1">
-<li>
- Primitives
- </li>
-<li>
- Composites
- </li>
+<div class="orderedlist"><ol class="orderedlist" type="1">
+<li class="listitem">
+ Primitives
+ </li>
+<li class="listitem">
+ Composites
+ </li>
</ol></div>

 Primitives provide the basic building blocks of functionality within Phoenix.
@@ -76,272 +77,275 @@
 again be another composite.
 
<div class="table">
-<a name="id461610"></a>Table 1.2. Modules
-<table class="table" summary="Modules">
+<a name="id765093"></a>Table 1.2. Modules
+<div class="table-contents"><table class="table" summary="Modules">
<colgroup>
<col>
<col>
</colgroup>
<thead><tr>
<th>
- 
- Module
- 
- </th>
+ 
+ Module
+ 
+ </th>
<th>
- 
- Description
- 
- </th>
+ 
+ Description
+ 
+ </th>
</tr></thead>
<tbody>
<tr>
<td>
- 
- Function
- 
- </td>
+ 
+ Function
+ 
+ </td>
<td>
- 
- Lazy functions support (e.g. <tt class="computeroutput">add</tt>)
- 
- </td>
+ 
+ Lazy functions support (e.g. <code class="computeroutput">add</code>)
+ 
+ </td>
</tr>
<tr>
<td>
- 
- Operator
- 
- </td>
+ 
+ Operator
+ 
+ </td>
<td>
- 
- Lazy operators support (e.g. <tt class="computeroutput">+</tt>)
- 
- </td>
+ 
+ Lazy operators support (e.g. <code class="computeroutput">+</code>)
+ 
+ </td>
</tr>
<tr>
<td>
- 
- Statement
- 
- </td>
+ 
+ Statement
+ 
+ </td>
<td>
- 
- Lazy statments (e.g. <tt class="computeroutput">if_</tt>,
- <tt class="computeroutput">while_</tt>)
- 
- </td>
+ 
+ Lazy statments (e.g. <code class="computeroutput">if_</code>,
+ <code class="computeroutput">while_</code>)
+ 
+ </td>
</tr>
<tr>
<td>
- 
- Object
- 
- </td>
+ 
+ Object
+ 
+ </td>
<td>
- 
- Lazy casts (e.g. <tt class="computeroutput">static_cast_</tt>),
- object creation destruction (e.g. <tt class="computeroutput">new_</tt>,
- <tt class="computeroutput">delete_</tt>)
- 
- </td>
+ 
+ Lazy casts (e.g. <code class="computeroutput">static_cast_</code>),
+ object creation destruction (e.g. <code class="computeroutput">new_</code>,
+ <code class="computeroutput">delete_</code>)
+ 
+ </td>
</tr>
<tr>
<td>
- 
- Scope
- 
- </td>
+ 
+ Scope
+ 
+ </td>
<td>
- 
- Support for scopes, local variables and lambda-lambda
- 
- </td>
+ 
+ Support for scopes, local variables and lambda-lambda
+ 
+ </td>
</tr>
<tr>
<td>
- 
- Bind
- 
- </td>
+ 
+ Bind
+ 
+ </td>
<td>
- 
- Lazy functions from free functions, member functions or member variables.
- 
- </td>
+ 
+ Lazy functions from free functions, member functions or member variables.
+ 
+ </td>
</tr>
<tr>
<td>
- 
- Container
- 
- </td>
+ 
+ Container
+ 
+ </td>
<td>
- 
- Set of predefined "lazy" functions that work on STL containers
- and sequences (e.g. <tt class="computeroutput">push_back</tt>).
- 
- </td>
+ 
+ Set of predefined "lazy" functions that work on STL containers
+ and sequences (e.g. <code class="computeroutput">push_back</code>).
+ 
+ </td>
</tr>
<tr>
<td>
- 
- Algorithm
- 
- </td>
+ 
+ Algorithm
+ 
+ </td>
<td>
- 
- Set of predefined "lazy" versions of the STL algorithms (e.g.
- <tt class="computeroutput">find_if</tt>).
- 
- </td>
+ 
+ Set of predefined "lazy" versions of the STL algorithms
+ (e.g. <code class="computeroutput">find_if</code>).
+ 
+ </td>
</tr>
</tbody>
-</table>
+</table></div>
</div>
-
+ 
 Each module is defined in a header file with the same name. For example, the
- core module is defined in <tt class="computeroutput"><boost/spirit/home/phoenix/core.hpp></tt>.
+ core module is defined in <code class="computeroutput"><boost/spirit/home/phoenix/core.hpp></code>.
 
<div class="table">
-<a name="id461986"></a>Table 1.3. Includes
-<table class="table" summary="Includes">
+<a name="id765410"></a>Table 1.3. Includes
+<div class="table-contents"><table class="table" summary="Includes">
<colgroup>
<col>
<col>
</colgroup>
<thead><tr>
<th>
- 
- Module
- 
- </th>
+ 
+ Module
+ 
+ </th>
<th>
- 
- File
- 
- </th>
+ 
+ File
+ 
+ </th>
</tr></thead>
<tbody>
<tr>
<td>
- 
- Core
- 
- </td>
+ 
+ Core
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">#include <boost/spirit/home/phoenix/core.hpp></tt>
- 
- </td>
+ 
+ <code class="computeroutput">#include <boost/spirit/home/phoenix/core.hpp></code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- Function
- 
- </td>
+ 
+ Function
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">#include <boost/spirit/home/phoenix/function.hpp></tt>
- 
- </td>
+ 
+ <code class="computeroutput">#include <boost/spirit/home/phoenix/function.hpp></code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- Operator
- 
- </td>
+ 
+ Operator
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">#include <boost/spirit/home/phoenix/operator.hpp></tt>
- 
- </td>
+ 
+ <code class="computeroutput">#include <boost/spirit/home/phoenix/operator.hpp></code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- Statement
- 
- </td>
+ 
+ Statement
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">#include <boost/spirit/home/phoenix/statement.hpp></tt>
- 
- </td>
+ 
+ <code class="computeroutput">#include <boost/spirit/home/phoenix/statement.hpp></code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- Object
- 
- </td>
+ 
+ Object
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">#include <boost/spirit/home/phoenix/object.hpp></tt>
- 
- </td>
+ 
+ <code class="computeroutput">#include <boost/spirit/home/phoenix/object.hpp></code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- Scope
- 
- </td>
+ 
+ Scope
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">#include <boost/spirit/home/phoenix/scope.hpp></tt>
- 
- </td>
+ 
+ <code class="computeroutput">#include <boost/spirit/home/phoenix/scope.hpp></code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- Bind
- 
- </td>
+ 
+ Bind
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">#include <boost/spirit/home/phoenix/bind.hpp></tt>
- 
- </td>
+ 
+ <code class="computeroutput">#include <boost/spirit/home/phoenix/bind.hpp></code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- Container
- 
- </td>
+ 
+ Container
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">#include <boost/spirit/home/phoenix/container.hpp></tt>
- 
- </td>
+ 
+ <code class="computeroutput">#include <boost/spirit/home/phoenix/container.hpp></code>
+ 
+ </td>
</tr>
<tr>
<td>
- 
- Algorithm
- 
- </td>
+ 
+ Algorithm
+ 
+ </td>
<td>
- 
- <tt class="computeroutput">#include <boost/spirit/home/phoenix/algorithm.hpp></tt>
- 
- </td>
+ 
+ <code class="computeroutput">#include <boost/spirit/home/phoenix/algorithm.hpp></code>
+ 
+ </td>
</tr>
</tbody>
-</table>
+</table></div>
</div>
-<div class="sidebar">
+ <div class="sidebar">
+
+
 <img src="../images/tip.png" alt="tip"> Finer grained include files are available per feature;
 see the succeeding sections.
- </div>
+ 
+</div>
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2002-2005 Joel
+<td align="right"><div class="copyright-footer">Copyright © 2002-2005 Joel
 de Guzman, Dan Marsden
 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)
@@ -350,7 +354,7 @@
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="basics.html"><img src="../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="actors.html"><img src="../../../../../../doc/html/images/next.png" alt="Next"></a>
+<a accesskey="p" href="basics.html"><img src="../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="actors.html"><img src="../../../../../../doc/src/images/next.png" alt="Next"></a>
</div>
</body>
</html>

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-07-19 16:15:52 EDT (Mon, 19 Jul 2010)
@@ -1,11 +1,11 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Primitives</title>
-<link rel="stylesheet" href="../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.66.1">
-<link rel="start" href="../index.html" title="Chapter 1. Phoenix 2.0">
-<link rel="up" href="../index.html" title="Chapter 1. Phoenix 2.0">
+<link rel="stylesheet" href="../../../../../../doc/src/boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
+<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">
<link rel="next" href="composite.html" title="Composite">
</head>
@@ -13,18 +13,19 @@
<table cellpadding="2" width="100%"><tr>
<td valign="top"><img alt="Boost C++ Libraries" width="277" height="86" src="../../../../../../boost.png"></td>
<td align="center">Home</td>
-<td align="center">Libraries</td>
+<td align="center">Libraries</td>
<td align="center">People</td>
<td align="center">FAQ</td>
<td align="center">More</td>
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="actors.html"><img src="../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="composite.html"><img src="../../../../../../doc/html/images/next.png" alt="Next"></a>
+<a accesskey="p" href="actors.html"><img src="../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="composite.html"><img src="../../../../../../doc/src/images/next.png" alt="Next"></a>
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="phoenix.primitives"></a>Primitives</h2></div></div></div>
+<a name="phoenix.primitives"></a><a class="link" href="primitives.html" title="Primitives">Primitives</a>
+</h2></div></div></div>
<div class="toc"><dl>
<dt>Arguments</dt>
<dt>Values</dt>
@@ -38,92 +39,86 @@
 is extensible. New primitives can be added anytime. Right out of the box, there
 are only a few primitives. This section shall deal with these preset primitives.
 
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="phoenix.primitives.arguments"></a>Arguments</h3></div></div></div>
-<pre class="programlisting">
-#include <boost/spirit/home/phoenix/core/argument.hpp>
+<a name="phoenix.primitives.arguments"></a><a class="link" href="primitives.html#phoenix.primitives.arguments" title="Arguments">Arguments</a>
+</h3></div></div></div>
+<pre class="programlisting">#include <boost/spirit/home/phoenix/core/argument.hpp>
</pre>

 We use an instance of:
 
-<pre class="programlisting">
-actor<argument<N> >
+<pre class="programlisting">actor<argument<N> >
</pre>

 to represent the Nth function argument. The argument placeholder acts as
 an imaginary data-bin where a function argument will be placed.
 
-<a name="phoenix.primitives.arguments.predefined_arguments"></a><h2>
-<a name="id463599"></a>
- <a href="primitives.html#phoenix.primitives.arguments.predefined_arguments">Predefined
+<a name="phoenix.primitives.arguments.predefined_arguments"></a><h3>
+<a name="id766693"></a>
+ <a class="link" href="primitives.html#phoenix.primitives.arguments.predefined_arguments">Predefined
 Arguments</a>
- </h2>
+ </h3>

- There are a few predefined instances of <tt class="computeroutput">actor<argument<N>
- ></tt> named <tt class="computeroutput">arg1</tt>..<tt class="computeroutput">argN</tt>, and its BLL
- counterpart <tt class="computeroutput">_1</tt>..<tt class="computeroutput">_N</tt>. (where N is a predefined maximum).
+ There are a few predefined instances of <code class="computeroutput">actor<argument<N>
+ ></code> named <code class="computeroutput">arg1</code>..<code class="computeroutput">argN</code>, and its BLL
+ counterpart <code class="computeroutput">_1</code>..<code class="computeroutput">_N</code>. (where N is a predefined maximum).
 

- Here are some sample preset definitions of <tt class="computeroutput">arg1</tt>..<tt class="computeroutput">argN</tt>
+ Here are some sample preset definitions of <code class="computeroutput">arg1</code>..<code class="computeroutput">argN</code>
 
-<pre class="programlisting">
-actor<argument<0> > const arg1 = argument<0>();
+<pre class="programlisting">actor<argument<0> > const arg1 = argument<0>();
actor<argument<1> > const arg2 = argument<1>();
actor<argument<2> > const arg3 = argument<2>();
</pre>

 and its BLL
- <tt class="computeroutput">_1</tt>..<tt class="computeroutput">_N</tt>
+ <code class="computeroutput">_1</code>..<code class="computeroutput">_N</code>
 style counterparts:
 
-<pre class="programlisting">
-actor<argument<0> > const _1 = argument<0>();
+<pre class="programlisting">actor<argument<0> > const _1 = argument<0>();
actor<argument<1> > const _2 = argument<1>();
actor<argument<2> > const _3 = argument<2>();
</pre>
<div class="note"><table border="0" summary="Note">
<tr>
-<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../../../../../../doc/html/images/note.png"></td>
+<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../../../../../../doc/src/images/note.png"></td>
<th align="left">Note</th>
</tr>
-<tr><td colspan="2" align="left" valign="top">
- You can set <tt class="computeroutput">PHOENIX_ARG_LIMIT</tt>,
- the predefined maximum placeholder index. By default, <tt class="computeroutput">PHOENIX_ARG_LIMIT</tt>
- is set to <tt class="computeroutput">PHOENIX_LIMIT</tt>
- (See Actors).
+<tr><td align="left" valign="top">
+ You can set <code class="computeroutput">PHOENIX_ARG_LIMIT</code>,
+ the predefined maximum placeholder index. By default, <code class="computeroutput">PHOENIX_ARG_LIMIT</code>
+ is set to <code class="computeroutput">PHOENIX_LIMIT</code>
+ (See <a class="link" href="actors.html" title="Actors">Actors</a>).
 </td></tr>
</table></div>
-<a name="phoenix.primitives.arguments.user_defined_arguments"></a><h2>
-<a name="id464325"></a>
- <a href="primitives.html#phoenix.primitives.arguments.user_defined_arguments">User
+<a name="phoenix.primitives.arguments.user_defined_arguments"></a><h3>
+<a name="id767253"></a>
+ <a class="link" href="primitives.html#phoenix.primitives.arguments.user_defined_arguments">User
 Defined Arguments</a>
- </h2>
+ </h3>

- When appropriate, you can define your own <tt class="computeroutput">argument<N></tt>
+ When appropriate, you can define your own <code class="computeroutput">argument<N></code>
 names. For example:
 
-<pre class="programlisting">
-actor<argument<0> > x; // note zero based index
+<pre class="programlisting">actor<argument<0> > x; // note zero based index
</pre>

- <tt class="computeroutput">x</tt> may now be used as a parameter
+ <code class="computeroutput">x</code> may now be used as a parameter
 to a lazy function:
 
-<pre class="programlisting">
-add(x, 6)
+<pre class="programlisting">add(x, 6)
</pre>

 which is equivalent to:
 
-<pre class="programlisting">
-add(arg1, 6)
+<pre class="programlisting">add(arg1, 6)
</pre>
-<a name="phoenix.primitives.arguments.evaluating_an_argument"></a><h2>
-<a name="id464544"></a>
- <a href="primitives.html#phoenix.primitives.arguments.evaluating_an_argument">Evaluating
+<a name="phoenix.primitives.arguments.evaluating_an_argument"></a><h3>
+<a name="id767420"></a>
+ <a class="link" href="primitives.html#phoenix.primitives.arguments.evaluating_an_argument">Evaluating
 an Argument</a>
- </h2>
+ </h3>

 An argument, when evaluated, selects the Nth argument from the those passed
 in by the client.
@@ -131,8 +126,7 @@

 For example:
 
-<pre class="programlisting">
-char c = 'A';
+<pre class="programlisting">char c = 'A';
int i = 123;
const char* s = "Hello World";

@@ -143,53 +137,49 @@

 will print out:
 
-<pre class="programlisting">
-A
+<pre class="programlisting">A
123
Hello World
</pre>
-<a name="phoenix.primitives.arguments.extra_arguments"></a><h2>
-<a name="id464915"></a>
- Extra Arguments
- </h2>
+<a name="phoenix.primitives.arguments.extra_arguments"></a><h3>
+<a name="id767715"></a>
+ <a class="link" href="primitives.html#phoenix.primitives.arguments.extra_arguments">Extra Arguments</a>
+ </h3>

 In C and C++, a function can have extra arguments that are not at all used
 by the function body itself. These extra arguments are simply ignored.
 

 Phoenix also allows extra arguments to be passed. For example, recall our
- original <tt class="computeroutput">add</tt> function:
+ original <code class="computeroutput">add</code> function:
 
-<pre class="programlisting">
-add(arg1, arg2)
+<pre class="programlisting">add(arg1, arg2)
</pre>

 We know now that partially applying this function results to a function that
 expects 2 arguments. However, the library is a bit more lenient and allows
- the caller to supply more arguments than is actually required. Thus, <tt class="computeroutput">add</tt> actually allows 2 or more
+ the caller to supply more arguments than is actually required. Thus, <code class="computeroutput">add</code> actually allows 2 or more
 arguments. For instance, with:
 
-<pre class="programlisting">
-add(arg1, arg2)(x, y, z)
+<pre class="programlisting">add(arg1, arg2)(x, y, z)
</pre>

- the third argument <tt class="computeroutput">z</tt> is ignored.
+ the third argument <code class="computeroutput">z</code> is ignored.
 Taking this further, in-between arguments are also ignored. Example:
 
-<pre class="programlisting">
-add(arg1, arg5)(a, b, c, d, e)
+<pre class="programlisting">add(arg1, arg5)(a, b, c, d, e)
</pre>

- Here, arguments b, c, and d are ignored. The function <tt class="computeroutput">add</tt>
- takes in the first argument (<tt class="computeroutput">arg1</tt>)
- and the fifth argument (<tt class="computeroutput">arg5</tt>).
+ Here, arguments b, c, and d are ignored. The function <code class="computeroutput">add</code>
+ takes in the first argument (<code class="computeroutput">arg1</code>)
+ and the fifth argument (<code class="computeroutput">arg5</code>).
 
<div class="note"><table border="0" summary="Note">
<tr>
-<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../../../../../../doc/html/images/note.png"></td>
+<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../../../../../../doc/src/images/note.png"></td>
<th align="left">Note</th>
</tr>
-<tr><td colspan="2" align="left" valign="top">
+<tr><td align="left" valign="top">
 There are a few reasons why enforcing strict arity is not desireable. A
 case in point is the callback function. Typical callback functions provide
 more information than is actually needed. Lambda functions are often used
@@ -197,112 +187,103 @@
 </td></tr>
</table></div>
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="phoenix.primitives.values"></a>Values</h3></div></div></div>
-<pre class="programlisting">
-#include <boost/spirit/home/phoenix/core/value.hpp>
+<a name="phoenix.primitives.values"></a><a class="link" href="primitives.html#phoenix.primitives.values" title="Values">Values</a>
+</h3></div></div></div>
+<pre class="programlisting">#include <boost/spirit/home/phoenix/core/value.hpp>
</pre>

 Whenever we see a constant in a partially applied function, an
 
-<pre class="programlisting">
-actor<value<T> >
+<pre class="programlisting">actor<value<T> >
</pre>

 (where T is the type of the constant) is automatically created for us. For
 instance:
 
-<pre class="programlisting">
-add(arg1, 6)
+<pre class="programlisting">add(arg1, 6)
</pre>

- Passing a second argument, <tt class="computeroutput">6</tt>,
- an <tt class="computeroutput">actor<value<int> ></tt>
+ Passing a second argument, <code class="computeroutput">6</code>,
+ an <code class="computeroutput">actor<value<int> ></code>
 is implicitly created behind the scenes. This is also equivalent to:
 
-<pre class="programlisting">
-add(arg1, val(6))
+<pre class="programlisting">add(arg1, val(6))
</pre>

- <tt class="computeroutput">val(x)</tt> generates
- an <tt class="computeroutput">actor<value<T> ></tt> where <tt class="computeroutput">T</tt>
- is the type of <tt class="computeroutput">x</tt>. In most
- cases, there's no need to explicitly use <tt class="computeroutput">val</tt>,
+ <code class="computeroutput">val(x)</code> generates
+ an <code class="computeroutput">actor<value<T> ></code> where <code class="computeroutput">T</code>
+ is the type of <code class="computeroutput">x</code>. In most
+ cases, there's no need to explicitly use <code class="computeroutput">val</code>,
 but, as we'll see later on, there are situations where this is unavoidable.
 
-<a name="phoenix.primitives.values.evaluating_a_value"></a><h2>
-<a name="id465687"></a>
- <a href="primitives.html#phoenix.primitives.values.evaluating_a_value">Evaluating a
+<a name="phoenix.primitives.values.evaluating_a_value"></a><h3>
+<a name="id768309"></a>
+ <a class="link" href="primitives.html#phoenix.primitives.values.evaluating_a_value">Evaluating a
 Value</a>
- </h2>
+ </h3>

 Like arguments, values are also actors. As such, values can be evaluated.
 Invoking a value gives the value's identity. Example:
 
-<pre class="programlisting">
-cout << val(3)() << val("Hello World")();
+<pre class="programlisting">cout << val(3)() << val("Hello World")();
</pre>

 prints out "3 Hello World".
 
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="phoenix.primitives.references"></a>References</h3></div></div></div>
-<pre class="programlisting">
-#include <boost/spirit/home/phoenix/core/reference.hpp>
+<a name="phoenix.primitives.references"></a><a class="link" href="primitives.html#phoenix.primitives.references" title="References">References</a>
+</h3></div></div></div>
+<pre class="programlisting">#include <boost/spirit/home/phoenix/core/reference.hpp>
</pre>

 Values are immutable constants. Attempting to modify a value will result
 in a compile time error. When we want the function to modify the parameter,
- we use a reference instead. For instance, imagine a lazy function <tt class="computeroutput">add_assign</tt>:
+ we use a reference instead. For instance, imagine a lazy function <code class="computeroutput">add_assign</code>:
 
-<pre class="programlisting">
-void add_assign(T& x, T y) { x += y; } // pseudo code
+<pre class="programlisting">void add_assign(T& x, T y) { x += y; } // pseudo code
</pre>

 Here, we want the first function argument, x, to be mutable. Obviously, we
 cannot write:
 
-<pre class="programlisting">
-add_assign(1, 2) // error first argument is immutable
+<pre class="programlisting">add_assign(1, 2) // error first argument is immutable
</pre>

 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 Values).
+ partially applied functions functions to be immutable values (see <a class="link" href="primitives.html#phoenix.primitives.values" title="Values">Values</a>).
 To achieve our intent, we use:
 
-<pre class="programlisting">
-actor<reference<T> >
+<pre class="programlisting">actor<reference<T> >
</pre>

- This is similar to <tt class="computeroutput">actor<value<T>
- ></tt> above but instead holds a reference
+ This is similar to <code class="computeroutput">actor<value<T>
+ ></code> above but instead holds a reference
 to a variable.
 

- We normally don't instantiate <tt class="computeroutput">actor<reference<T>
- ></tt> objects directly. Instead we
- use <tt class="computeroutput">ref</tt>. For example (where
- <tt class="computeroutput">i</tt> is an <tt class="computeroutput">int</tt>
+ We normally don't instantiate <code class="computeroutput">actor<reference<T>
+ ></code> objects directly. Instead we
+ use <code class="computeroutput">ref</code>. For example (where
+ <code class="computeroutput">i</code> is an <code class="computeroutput">int</code>
 variable):
 
-<pre class="programlisting">
-add_assign(ref(i), 2)
+<pre class="programlisting">add_assign(ref(i), 2)
</pre>
-<a name="phoenix.primitives.references.evaluating_a_reference"></a><h2>
-<a name="id466317"></a>
- <a href="primitives.html#phoenix.primitives.references.evaluating_a_reference">Evaluating
+<a name="phoenix.primitives.references.evaluating_a_reference"></a><h3>
+<a name="id769065"></a>
+ <a class="link" href="primitives.html#phoenix.primitives.references.evaluating_a_reference">Evaluating
 a Reference</a>
- </h2>
+ </h3>

 References are actors. Hence, references can be evaluated. Such invocation
 gives the references's identity. Example:
 
-<pre class="programlisting">
-int i = 3;
+<pre class="programlisting">int i = 3;
char const* s = "Hello World";
cout << ref(i)() << ref(s)();
</pre>
@@ -310,39 +291,39 @@
 prints out "3 Hello World"
 
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="phoenix.primitives.constant_references"></a>Constant References</h3></div></div></div>
-<pre class="programlisting">
-#include <boost/spirit/home/phoenix/core/reference.hpp>
+<a name="phoenix.primitives.constant_references"></a><a class="link" href="primitives.html#phoenix.primitives.constant_references" title="Constant References">Constant References</a>
+</h3></div></div></div>
+<pre class="programlisting">#include <boost/spirit/home/phoenix/core/reference.hpp>
</pre>

- Another free function <tt class="computeroutput">cref(cv)</tt>
- may also be used. <tt class="computeroutput">cref(cv)</tt> creates
- an <tt class="computeroutput">actor<reference<T const&> ></tt>
- object. This is similar to <tt class="computeroutput">actor<value<T>
- ></tt> but when the data to be passed
- as argument to a function is heavy and expensive to copy by value, the <tt class="computeroutput">cref(cv)</tt> offers a lighter alternative.
+ Another free function <code class="computeroutput">cref(cv)</code>
+ may also be used. <code class="computeroutput">cref(cv)</code> creates
+ an <code class="computeroutput">actor<reference<T const&> ></code>
+ object. This is similar to <code class="computeroutput">actor<value<T>
+ ></code> but when the data to be passed
+ as argument to a function is heavy and expensive to copy by value, the <code class="computeroutput">cref(cv)</code> offers a lighter alternative.
 
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="phoenix.primitives.nothing"></a>Nothing</h3></div></div></div>
-<pre class="programlisting">
-#include <boost/spirit/home/phoenix/core/nothing.hpp>
+<a name="phoenix.primitives.nothing"></a><a class="link" href="primitives.html#phoenix.primitives.nothing" title="Nothing">Nothing</a>
+</h3></div></div></div>
+<pre class="programlisting">#include <boost/spirit/home/phoenix/core/nothing.hpp>
</pre>

- Finally, the <tt class="computeroutput">actor<null_actor></tt>
- does nothing; (a "bum", if you will :-). There's a sole <tt class="computeroutput">actor<null_actor></tt>
+ Finally, the <code class="computeroutput">actor<null_actor></code>
+ does nothing; (a "bum", if you will :-). There's a sole <code class="computeroutput">actor<null_actor></code>
 instance named "nothing". This actor is actually useful in situations
- where we don't want to do anything. (See <a href="composite.html#phoenix.composite.statement.for__statement" title="for_ Statement">for_
+ where we don't want to do anything. (See <a class="link" href="composite.html#phoenix.composite.statement.for__statement" title="for_ Statement">for_
 Statement</a> for example).
 
</div>
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2002-2005 Joel
+<td align="right"><div class="copyright-footer">Copyright © 2002-2005 Joel
 de Guzman, Dan Marsden
 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)
@@ -351,7 +332,7 @@
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="actors.html"><img src="../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="composite.html"><img src="../../../../../../doc/html/images/next.png" alt="Next"></a>
+<a accesskey="p" href="actors.html"><img src="../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="composite.html"><img src="../../../../../../doc/src/images/next.png" alt="Next"></a>
</div>
</body>
</html>

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-07-19 16:15:52 EDT (Mon, 19 Jul 2010)
@@ -1,81 +1,82 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>References</title>
-<link rel="stylesheet" href="../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.66.1">
-<link rel="start" href="../index.html" title="Chapter 1. Phoenix 2.0">
-<link rel="up" href="../index.html" title="Chapter 1. Phoenix 2.0">
+<link rel="stylesheet" href="../../../../../../doc/src/boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
+<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">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
<table cellpadding="2" width="100%"><tr>
<td valign="top"><img alt="Boost C++ Libraries" width="277" height="86" src="../../../../../../boost.png"></td>
<td align="center">Home</td>
-<td align="center">Libraries</td>
+<td align="center">Libraries</td>
<td align="center">People</td>
<td align="center">FAQ</td>
<td align="center">More</td>
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="acknowledgement.html"><img src="../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/html/images/home.png" alt="Home"></a>
+<a accesskey="p" href="acknowledgement.html"><img src="../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/src/images/home.png" alt="Home"></a>
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="phoenix.references"></a>References</h2></div></div></div>
-<div class="orderedlist"><ol type="1">
-<li>
- Why Functional Programming Matters, John Hughes, 1989. Available online at
- http://www.math.chalmers.se/~rjmh/Papers/whyfp.html.
- </li>
-<li>
- Boost.Lambda library, Jaakko Jarvi, 1999-2004 Jaakko Jarvi, Gary Powell.
- Available online at http://www.boost.org/libs/lambda/.
- </li>
-<li>
- Functional Programming in C++ using the FC++ Library: a short article introducing
- FC++, Brian McNamara and Yannis Smaragdakis, August 2003. Available online
- at http://www.cc.gatech.edu/~yannis/fc++/.
- </li>
-<li>
- Side-effects and partial function application in C++, Jaakko Jarvi and Gary
- Powell, 2001. Available online at http://osl.iu.edu/~jajarvi/publications/papers/mpool01.pdf.
- </li>
-<li>
- Spirit Version 1.8.1, Joel de Guzman, Nov 2004. Available online at http://www.boost.org/libs/spirit/.
- </li>
-<li>
- The Boost MPL Library, Aleksey Gurtovoy and David Abrahams, 2002-2004. Available
- online at http://www.boost.org/libs/mpl/.
- </li>
-<li>
- Generic Programming Redesign of Patterns, Proceedings of the 5th European
- Conference on Pattern Languages of Programs, (EuroPLoP'2000) Irsee, Germany,
- July 2000. Available online at http://www.coldewey.com/europlop2000/papers/geraud%2Bduret.zip.
- </li>
-<li>
- A Gentle Introduction to Haskell, Paul Hudak, John Peterson and Joseph Fasel,
- 1999. Available online at http://www.haskell.org/tutorial/.
- </li>
-<li>
- Large scale software design, John Lackos, ISBN 0201633620, Addison-Wesley,
- July 1996.
- </li>
-<li>
- Design Patterns, Elements of Reusable Object-Oriented Software, Erich Gamma,
- Richard Helm, Ralph Jhonson, and John Vlissides, Addison-Wesley, 1995.
- </li>
-<li>
- The Forwarding Problem: Arguments Peter Dimov, Howard E. Hinnant, Dave Abrahams,
- September 09, 2002. Available online: <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2002/n1385.htm" target="_top">Forwarding
- Function Problem</a>.
- </li>
+<a name="phoenix.references"></a><a class="link" href="references.html" title="References">References</a>
+</h2></div></div></div>
+<div class="orderedlist"><ol class="orderedlist" type="1">
+<li class="listitem">
+ Why Functional Programming Matters, John Hughes, 1989. Available online
+ at http://www.math.chalmers.se/~rjmh/Papers/whyfp.html.
+ </li>
+<li class="listitem">
+ Boost.Lambda library, Jaakko Jarvi, 1999-2004 Jaakko Jarvi, Gary Powell.
+ Available online at http://www.boost.org/libs/lambda/.
+ </li>
+<li class="listitem">
+ Functional Programming in C++ using the FC++ Library: a short article introducing
+ FC++, Brian McNamara and Yannis Smaragdakis, August 2003. Available online
+ at http://www.cc.gatech.edu/~yannis/fc++/.
+ </li>
+<li class="listitem">
+ Side-effects and partial function application in C++, Jaakko Jarvi and
+ Gary Powell, 2001. Available online at http://osl.iu.edu/~jajarvi/publications/papers/mpool01.pdf.
+ </li>
+<li class="listitem">
+ Spirit Version 1.8.1, Joel de Guzman, Nov 2004. Available online at http://www.boost.org/libs/spirit/.
+ </li>
+<li class="listitem">
+ The Boost MPL Library, Aleksey Gurtovoy and David Abrahams, 2002-2004.
+ Available online at http://www.boost.org/libs/mpl/.
+ </li>
+<li class="listitem">
+ Generic Programming Redesign of Patterns, Proceedings of the 5th European
+ Conference on Pattern Languages of Programs, (EuroPLoP'2000) Irsee, Germany,
+ July 2000. Available online at http://www.coldewey.com/europlop2000/papers/geraud%2Bduret.zip.
+ </li>
+<li class="listitem">
+ A Gentle Introduction to Haskell, Paul Hudak, John Peterson and Joseph
+ Fasel, 1999. Available online at http://www.haskell.org/tutorial/.
+ </li>
+<li class="listitem">
+ Large scale software design, John Lackos, ISBN 0201633620, Addison-Wesley,
+ July 1996.
+ </li>
+<li class="listitem">
+ Design Patterns, Elements of Reusable Object-Oriented Software, Erich Gamma,
+ Richard Helm, Ralph Jhonson, and John Vlissides, Addison-Wesley, 1995.
+ </li>
+<li class="listitem">
+ The Forwarding Problem: Arguments Peter Dimov, Howard E. Hinnant, Dave
+ Abrahams, September 09, 2002. Available online: <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2002/n1385.htm" target="_top">Forwarding
+ Function Problem</a>.
+ </li>
</ol></div>
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2002-2005 Joel
+<td align="right"><div class="copyright-footer">Copyright © 2002-2005 Joel
 de Guzman, Dan Marsden
 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)
@@ -84,7 +85,7 @@
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="acknowledgement.html"><img src="../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/html/images/home.png" alt="Home"></a>
+<a accesskey="p" href="acknowledgement.html"><img src="../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/src/images/home.png" alt="Home"></a>
</div>
</body>
</html>

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-07-19 16:15:52 EDT (Mon, 19 Jul 2010)
@@ -1,11 +1,11 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Starter Kit</title>
-<link rel="stylesheet" href="../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.66.1">
-<link rel="start" href="../index.html" title="Chapter 1. Phoenix 2.0">
-<link rel="up" href="../index.html" title="Chapter 1. Phoenix 2.0">
+<link rel="stylesheet" href="../../../../../../doc/src/boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
+<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">
<link rel="next" href="basics.html" title="Basics">
</head>
@@ -13,18 +13,19 @@
<table cellpadding="2" width="100%"><tr>
<td valign="top"><img alt="Boost C++ Libraries" width="277" height="86" src="../../../../../../boost.png"></td>
<td align="center">Home</td>
-<td align="center">Libraries</td>
+<td align="center">Libraries</td>
<td align="center">People</td>
<td align="center">FAQ</td>
<td align="center">More</td>
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="introduction.html"><img src="../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="basics.html"><img src="../../../../../../doc/html/images/next.png" alt="Next"></a>
+<a accesskey="p" href="introduction.html"><img src="../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="basics.html"><img src="../../../../../../doc/src/images/next.png" alt="Next"></a>
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="phoenix.starter_kit"></a>Starter Kit</h2></div></div></div>
+<a name="phoenix.starter_kit"></a><a class="link" href="starter_kit.html" title="Starter Kit">Starter Kit</a>
+</h2></div></div></div>
<div class="toc"><dl>
<dt>Values</dt>
<dt>References</dt>
@@ -58,10 +59,10 @@
 to provide you with annotated exemplars instead. Hopefully, this will get you
 into high gear quickly.
 
-<a name="phoenix.starter_kit.functors_everywhere"></a><h2>
-<a name="id387510"></a>
- Functors everywhere
- </h2>
+<a name="phoenix.starter_kit.functors_everywhere"></a><h3>
+<a name="id760240"></a>
+ <a class="link" href="starter_kit.html#phoenix.starter_kit.functors_everywhere">Functors everywhere</a>
+ </h3>

 Phoenix is built on function objects (functors). The functor is the main building
 block. We compose functors to build more complex functors... to build more
@@ -69,72 +70,73 @@
 
<div class="note"><table border="0" summary="Note">
<tr>
-<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../../../../../../doc/html/images/note.png"></td>
+<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../../../../../../doc/src/images/note.png"></td>
<th align="left">Note</th>
</tr>
-<tr><td colspan="2" align="left" valign="top">
+<tr><td align="left" valign="top">
 Functors are so ubiquitous in Phoenix that, in the manual, the words "functor"
 and "function" are used interchangeably.
 </td></tr>
</table></div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="phoenix.starter_kit.values"></a>Values</h3></div></div></div>
+<a name="phoenix.starter_kit.values"></a><a class="link" href="starter_kit.html#phoenix.starter_kit.values" title="Values">Values</a>
+</h3></div></div></div>

 Values are functions! Examples:
 
-<pre class="programlisting">
-val(3)
+<pre class="programlisting">val(3)
val("Hello, World")
</pre>

 The first evaluates to a nullary function (a function taking no arguments)
- that returns an <tt class="computeroutput">int</tt>, <tt class="computeroutput">3</tt>. The second evaluates to a nullary function
- that returns a <tt class="computeroutput">char const(&)[13]</tt>, <tt class="computeroutput">"Hello,
- World"</tt>.
- 
-<a name="phoenix.starter_kit.values.lazy_evaluation"></a><h2>
-<a name="id385403"></a>
- Lazy Evaluation
- </h2>
+ that returns an <code class="computeroutput">int</code>, <code class="computeroutput">3</code>. The second evaluates to a nullary function
+ that returns a <code class="computeroutput">char const(&)[13]</code>, <code class="computeroutput">"Hello,
+ World"</code>.
+ 
+<a name="phoenix.starter_kit.values.lazy_evaluation"></a><h3>
+<a name="id760388"></a>
+ <a class="link" href="starter_kit.html#phoenix.starter_kit.values.lazy_evaluation">Lazy Evaluation</a>
+ </h3>

- Confused? <tt class="computeroutput">val(3)</tt> is a unary
+ Confused? <code class="computeroutput">val(3)</code> is a unary
 function, you say? Yes it is. However, read carefully: "evaluates
- to a nullary function". <tt class="computeroutput">val(3)</tt>
- evaluates to (returns) a nullary function. Aha! <tt class="computeroutput">val(3)</tt>
- returns a function! So, since <tt class="computeroutput">val(3)</tt>
+ to a nullary function". <code class="computeroutput">val(3)</code>
+ evaluates to (returns) a nullary function. Aha! <code class="computeroutput">val(3)</code>
+ returns a function! So, since <code class="computeroutput">val(3)</code>
 returns a function, you can invoke it. Example:
 
-<pre class="programlisting">
-cout << val(3)() << endl;
+<pre class="programlisting">cout << val(3)() << endl;
</pre>

 (See values.cpp)
 
-<div class="sidebar">
- <img src="../images/tip.png" alt="tip"> Learn more about values here.
- </div>
+<div class="sidebar">
+
+
+ <img src="../images/tip.png" alt="tip"> Learn more about values <a class="link" href="primitives.html#phoenix.primitives.values" title="Values">here.</a>
+ 
+</div>

 The second function call (the one with no arguments) calls the nullary function
- which then returns <tt class="computeroutput">3</tt>. The need
+ which then returns <code class="computeroutput">3</code>. The need
 for a second function call is the reason why the function is said to be
- Lazily Evaluated. The
+ Lazily Evaluated. The
 first call doesn't do anything. You need a second call to finally evaluate
 the thing. The first call lazily evaluates the function; i.e. doesn't do
 anything and defers the evaluation for later.
 
-<a name="phoenix.starter_kit.values.callbacks"></a><h2>
-<a name="id456050"></a>
- Callbacks
- </h2>
+<a name="phoenix.starter_kit.values.callbacks"></a><h3>
+<a name="id760603"></a>
+ <a class="link" href="starter_kit.html#phoenix.starter_kit.values.callbacks">Callbacks</a>
+ </h3>

 It may not be immediately apparent how lazy evaluation can be useful by just
 looking at the example above. Putting the first and second function call
- in a single line is really not very useful. However, thinking of <tt class="computeroutput">val(3)</tt> as a callback function (and in most cases
+ in a single line is really not very useful. However, thinking of <code class="computeroutput">val(3)</code> as a callback function (and in most cases
 they are actually used that way), will make it clear. Example:
 
-<pre class="programlisting">
-template <typename F>
+<pre class="programlisting">template <typename F>
void print(F f)
{
 cout << f() << endl;
@@ -152,42 +154,45 @@
 (See callback.cpp)
 
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="phoenix.starter_kit.references"></a>References</h3></div></div></div>
+<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>

 References are functions. They hold a reference to a value stored somehere.
 For example, given:
 
-<pre class="programlisting">
-int i = 3;
+<pre class="programlisting">int i = 3;
char const* s = "Hello World";
</pre>

- we create <tt class="computeroutput">references</tt> to
- <tt class="computeroutput">i</tt> and <tt class="computeroutput">s</tt>
+ we create <code class="computeroutput">references</code> to
+ <code class="computeroutput">i</code> and <code class="computeroutput">s</code>
 this way:
 
-<pre class="programlisting">
-ref(i)
+<pre class="programlisting">ref(i)
ref(s)
</pre>

- Like <tt class="computeroutput">val</tt>, the expressions
- above evaluates to a nullary function; the first one returning an <tt class="computeroutput">int&</tt>,
- and the second one returning a <tt class="computeroutput">char
- const*&</tt>.
+ Like <code class="computeroutput">val</code>, the expressions
+ above evaluates to a nullary function; the first one returning an <code class="computeroutput">int&</code>,
+ and the second one returning a <code class="computeroutput">char
+ const*&</code>.
 

 (See references.cpp)
 
-<div class="sidebar">
- <img src="../images/tip.png" alt="tip"> Learn more about references here.
- </div>
+<div class="sidebar">
+
+
+ <img src="../images/tip.png" alt="tip"> Learn more about references <a class="link" href="primitives.html#phoenix.primitives.references" title="References">here.</a>
+ 
+</div>
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="phoenix.starter_kit.arguments"></a>Arguments</h3></div></div></div>
+<a name="phoenix.starter_kit.arguments"></a><a class="link" href="starter_kit.html#phoenix.starter_kit.arguments" title="Arguments">Arguments</a>
+</h3></div></div></div>

 Arguments are also functions? You bet!
 
@@ -198,17 +203,15 @@
 arg3, arg4 and so on (and it's BLL
 counterparts: _1, _2, _3, _4 and so on). Examples:
 
-<pre class="programlisting">
-arg1 // one-or-more argument function that returns its first argument
+<pre class="programlisting">arg1 // one-or-more argument function that returns its first argument
arg2 // two-or-more argument function that returns its second argument
arg3 // three-or-more argument function that returns its third argument
</pre>

- <tt class="computeroutput">argN</tt> returns the Nth argument.
+ <code class="computeroutput">argN</code> returns the Nth argument.
 Examples:
 
-<pre class="programlisting">
-int i = 3;
+<pre class="programlisting">int i = 3;
char const* s = "Hello World";
cout << arg1(i) << endl; // prints 3
cout << arg2(i, s) << endl; // prints "Hello World"
@@ -216,61 +219,65 @@

 (See arguments.cpp)
 
-<div class="sidebar">
- <img src="../images/tip.png" alt="tip"> Learn more about arguments here.
- </div>
+<div class="sidebar">
+
+
+ <img src="../images/tip.png" alt="tip"> Learn more about arguments <a class="link" href="primitives.html#phoenix.primitives.arguments" title="Arguments">here.</a>
+ 
+</div>
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="phoenix.starter_kit.composites"></a>Composites</h3></div></div></div>
+<a name="phoenix.starter_kit.composites"></a><a class="link" href="starter_kit.html#phoenix.starter_kit.composites" title="Composites">Composites</a>
+</h3></div></div></div>

- What we have seen so far, are what are called primitives.
+ What we have seen so far, are what are called primitives.
 You can think of primitives (such as values, references and arguments) as
 atoms.
 

 Things start to get interesting when we start composing
- primitives to form composites. The composites
+ primitives to form composites. The composites
 can, in turn, be composed to form even more complex composites.
 
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="phoenix.starter_kit.lazy_operators"></a>Lazy Operators</h3></div></div></div>
+<a name="phoenix.starter_kit.lazy_operators"></a><a class="link" href="starter_kit.html#phoenix.starter_kit.lazy_operators" title="Lazy Operators">Lazy Operators</a>
+</h3></div></div></div>

 You can use the usual set of operators to form composites. Examples:
 
-<pre class="programlisting">
-arg1 * arg1
+<pre class="programlisting">arg1 * arg1
ref(x) = arg1 + ref(z)
arg1 = arg2 + (3 * arg3)
ref(x) = arg1[arg2] // assuming arg1 is indexable and arg2 is a valid index
</pre>

- Note the expression: <tt class="computeroutput">3 *
- arg3</tt>. This expression is actually
- a short-hand equivalent to: <tt class="computeroutput">val(3)
- * arg3</tt>.
+ Note the expression: <code class="computeroutput">3 *
+ arg3</code>. This expression is actually
+ a short-hand equivalent to: <code class="computeroutput">val(3)
+ * arg3</code>.
 In most cases, like above, you can get away with it. But in some cases, you
- will have to explicitly wrap your values in <tt class="computeroutput">val</tt>.
+ will have to explicitly wrap your values in <code class="computeroutput">val</code>.
 Rules of thumb:
 
-<div class="itemizedlist"><ul type="disc">
-<li>
- In a binary expression (e.g. <tt class="computeroutput">3 * arg3</tt>),
- at least one of the operands must be a phoenix primitive or composite.
- </li>
-<li>
- In a unary expression (e.g. <tt class="computeroutput">arg1++</tt>), the single operand must be a phoenix
- primitive or composite.
- </li>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem">
+ In a binary expression (e.g. <code class="computeroutput">3
+ * arg3</code>),
+ at least one of the operands must be a phoenix primitive or composite.
+ </li>
+<li class="listitem">
+ In a unary expression (e.g. <code class="computeroutput">arg1++</code>), the single operand must be a phoenix
+ primitive or composite.
+ </li>
</ul></div>

 If these basic rules are not followed, the result is either in error, or
 is immediately evaluated. Some examples:
 
-<pre class="programlisting">
-ref(x) = 123 // lazy
+<pre class="programlisting">ref(x) = 123 // lazy
x = 123 // immediate

ref(x)[0] // lazy
@@ -281,78 +288,80 @@
x[ref(i)] // illegal (x is not a phoenix primitive or composite)
ref(x[ref(i)]) // illegal (x is not a phoenix primitive or composite)
</pre>
-<div class="sidebar">
- <img src="../images/tip.png" alt="tip"> Learn more about operators here.
- </div>
-<a name="phoenix.starter_kit.lazy_operators.first_practical_example"></a><h2>
-<a name="id457702"></a>
- <a href="starter_kit.html#phoenix.starter_kit.lazy_operators.first_practical_example">First
+<div class="sidebar">
+
+
+ <img src="../images/tip.png" alt="tip"> Learn more about operators <a class="link" href="composite.html#phoenix.composite.operator" title="Operator">here.</a>
+ 
+</div>
+<a name="phoenix.starter_kit.lazy_operators.first_practical_example"></a><h3>
+<a name="id761945"></a>
+ <a class="link" href="starter_kit.html#phoenix.starter_kit.lazy_operators.first_practical_example">First
 Practical Example</a>
- </h2>
+ </h3>

 We've covered enough ground to present a real world example. We want to find
 the first odd number in an STL container. Normally we use a functor (function
- object) or a function pointer and pass that in to STL's <tt class="computeroutput">find_if</tt>
+ object) or a function pointer and pass that in to STL's <code class="computeroutput">find_if</code>
 generic function:
 

 Write a function:
 
-<pre class="programlisting">
-bool
+<pre class="programlisting">bool
is_odd(int arg1)
{
 return arg1 % 2 == 1;
}
</pre>

- Pass a pointer to the function to STL's <tt class="computeroutput">find_if</tt>
+ Pass a pointer to the function to STL's <code class="computeroutput">find_if</code>
 algorithm:
 
-<pre class="programlisting">
-find_if(c.begin(), c.end(), &is_odd)
+<pre class="programlisting">find_if(c.begin(), c.end(), &is_odd)
</pre>

 Using Phoenix, the same can be achieved directly with a one-liner:
 
-<pre class="programlisting">
-find_if(c.begin(), c.end(), arg1 % 2 == 1)
+<pre class="programlisting">find_if(c.begin(), c.end(), arg1 % 2 == 1)
</pre>

- The expression <tt class="computeroutput">arg1 %
- 2 == 1</tt> automagically creates a functor with the
+ The expression <code class="computeroutput">arg1 %
+ 2 == 1</code> automagically 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 with any container (of ints, of longs, of bignum, etc.) as long
- as its elements can handle the <tt class="computeroutput">arg1
- % 2 == 1</tt> expression.
+ as its elements can handle the <code class="computeroutput">arg1
+ % 2 == 1</code> expression.
 

 (See find_if.cpp)
 
-<div class="sidebar">
- <img src="../images/tip.png" alt="tip"> ...That's it, we're done.
+<div class="sidebar">
+
+
+ <img src="../images/tip.png" alt="tip"> ...That's it, we're done.
 Well if you wish to know a little bit more, read on...
- </div>
+ 
+</div>
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="phoenix.starter_kit.lazy_statements"></a>Lazy Statements</h3></div></div></div>
+<a name="phoenix.starter_kit.lazy_statements"></a><a class="link" href="starter_kit.html#phoenix.starter_kit.lazy_statements" title="Lazy Statements">Lazy Statements</a>
+</h3></div></div></div>

 Lazy statements? Sure. There are lazy versions of the C++ statements we all
 know and love. For example:
 
-<pre class="programlisting">
-if_(arg1 > 5)
+<pre class="programlisting">if_(arg1 > 5)
 cout << arg1
</pre>

 Say, for example, we wish to print all the elements that are greater than
 5 (separated by a comma) in a vector. Here's how we write it:
 
-<pre class="programlisting">
-for_each(v.begin(), v.end(),
+<pre class="programlisting">for_each(v.begin(), v.end(),
 if_(arg1 > 5)
 [
 cout << arg1 << ", "
@@ -362,43 +371,49 @@

 (See if.cpp)
 
-<div class="sidebar">
- <img src="../images/tip.png" alt="tip"> Learn more about statements here.
- </div>
+<div class="sidebar">
+
+
+ <img src="../images/tip.png" alt="tip"> Learn more about statements <a class="link" href="composite.html#phoenix.composite.statement" title="Statement">here.</a>
+ 
+</div>
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="phoenix.starter_kit.construct__new__delete__casts"></a><a href="starter_kit.html#phoenix.starter_kit.construct__new__delete__casts" title="Construct,
- New, Delete, Casts">Construct,
- New, Delete, Casts</a></h3></div></div></div>
+<a name="phoenix.starter_kit.construct__new__delete__casts"></a><a class="link" href="starter_kit.html#phoenix.starter_kit.construct__new__delete__casts" title="Construct, New, Delete, Casts">Construct,
+ New, Delete, Casts</a>
+</h3></div></div></div>

 You'll probably want to work with objects. There are lazy versions of constructor
- calls, <tt class="computeroutput">new</tt>, <tt class="computeroutput">delete</tt>
+ calls, <code class="computeroutput">new</code>, <code class="computeroutput">delete</code>
 and the suite of C++ casts. Examples:
 
-<pre class="programlisting">
-construct<std::string>(arg1, arg2) // constructs a std::string from arg1, arg2
+<pre class="programlisting">construct<std::string>(arg1, arg2) // constructs a std::string from arg1, arg2
new_<std::string>(arg1, arg2) // makes a new std::string from arg1, arg2
delete_(arg1) // deletes arg1 (assumed to be a pointer)
static_cast_<int*>(arg1) // static_cast's arg1 to an int*
</pre>
<div class="note"><table border="0" summary="Note">
<tr>
-<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../../../../../../doc/html/images/note.png"></td>
+<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../../../../../../doc/src/images/note.png"></td>
<th align="left">Note</th>
</tr>
-<tr><td colspan="2" align="left" valign="top">
+<tr><td align="left" valign="top">
 Take note that, by convention, names that conflict with C++ reserved words
- are appended with a single trailing underscore <tt class="computeroutput">'_'</tt>
+ are appended with a single trailing underscore <code class="computeroutput">'_'</code>
 </td></tr>
</table></div>
-<div class="sidebar">
- <img src="../images/tip.png" alt="tip"> Learn more about this here.
- </div>
+<div class="sidebar">
+
+
+ <img src="../images/tip.png" alt="tip"> Learn more about this <a class="link" href="composite.html#phoenix.composite.object" title="Object">here.</a>
+ 
+</div>
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="phoenix.starter_kit.lazy_functions"></a>Lazy Functions</h3></div></div></div>
+<a name="phoenix.starter_kit.lazy_functions"></a><a class="link" href="starter_kit.html#phoenix.starter_kit.lazy_functions" title="Lazy Functions">Lazy Functions</a>
+</h3></div></div></div>

 As you write more lambda functions, you'll notice certain patterns that you
 wish to refactor as reusable functions. When you reach that point, you'll
@@ -408,11 +423,10 @@
 

 Lazy functions are your friends. The library provides a facility to make
- lazy functions. The code below is a rewrite of the <tt class="computeroutput">is_odd</tt>
+ lazy functions. The code below is a rewrite of the <code class="computeroutput">is_odd</code>
 function using the facility:
 
-<pre class="programlisting">
-struct is_odd_impl
+<pre class="programlisting">struct is_odd_impl
{
 template <typename Arg>
 struct result
@@ -429,73 +443,76 @@

function<is_odd_impl> is_odd;
</pre>
-<a name="phoenix.starter_kit.lazy_functions.things_to_note_"></a><h2>
-<a name="id459051"></a>
- <a href="starter_kit.html#phoenix.starter_kit.lazy_functions.things_to_note_">Things
+<a name="phoenix.starter_kit.lazy_functions.things_to_note_"></a><h3>
+<a name="id763023"></a>
+ <a class="link" href="starter_kit.html#phoenix.starter_kit.lazy_functions.things_to_note_">Things
 to note:</a>
- </h2>
-<div class="itemizedlist"><ul type="disc">
-<li>
-<tt class="computeroutput">result</tt> is a nested metafunction
- that reflects the return type of the function (in this case, bool). This
- makes the function fully polymorphic: It can work with arbitrary <tt class="computeroutput">Arg</tt> types.
- </li>
-<li>
- There are as many Args in the <tt class="computeroutput">result</tt>
- metafunction as in the actual <tt class="computeroutput">operator()</tt>.
- </li>
-<li>
-<tt class="computeroutput">is_odd_impl</tt> implements
- the function.
- </li>
-<li>
-<tt class="computeroutput">is_odd</tt>, an instance of
- <tt class="computeroutput">function<is_odd_impl></tt>,
- is the lazy function.
- </li>
+ </h3>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem">
+ <code class="computeroutput">result</code> is a nested metafunction
+ that reflects the return type of the function (in this case, bool). This
+ makes the function fully polymorphic: It can work with arbitrary <code class="computeroutput">Arg</code> types.
+ </li>
+<li class="listitem">
+ There are as many Args in the <code class="computeroutput">result</code>
+ metafunction as in the actual <code class="computeroutput">operator()</code>.
+ </li>
+<li class="listitem">
+ <code class="computeroutput">is_odd_impl</code> implements
+ the function.
+ </li>
+<li class="listitem">
+ <code class="computeroutput">is_odd</code>, an instance of
+ <code class="computeroutput">function<is_odd_impl></code>,
+ is the lazy function.
+ </li>
</ul></div>

- Now, <tt class="computeroutput">is_odd</tt> is a truly lazy
+ Now, <code class="computeroutput">is_odd</code> is a truly lazy
 function that we can use in conjunction with the rest of phoenix. Example:
 
-<pre class="programlisting">
-find_if(c.begin(), c.end(), is_odd(arg1));
+<pre class="programlisting">find_if(c.begin(), c.end(), is_odd(arg1));
</pre>

 (See function.cpp)
 
-<a name="phoenix.starter_kit.lazy_functions.predefined_lazy_functions"></a><h2>
-<a name="id459305"></a>
- <a href="starter_kit.html#phoenix.starter_kit.lazy_functions.predefined_lazy_functions">Predefined
+<a name="phoenix.starter_kit.lazy_functions.predefined_lazy_functions"></a><h3>
+<a name="id763234"></a>
+ <a class="link" href="starter_kit.html#phoenix.starter_kit.lazy_functions.predefined_lazy_functions">Predefined
 Lazy Functions</a>
- </h2>
+ </h3>

 The library is chock full of STL savvy, predefined lazy functions covering
 the whole of the STL containers, iterators and algorithms. For example, there
 are lazy versions of container related operations such as assign, at, back,
- begin, pop_back, pop_front, push_back, push_front, etc. (See Container).
+ begin, pop_back, pop_front, push_back, push_front, etc. (See <a class="link" href="container.html" title="Container">Container</a>).
 
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h3 class="title">
-<a name="phoenix.starter_kit.more"></a>More</h3></div></div></div>
+<a name="phoenix.starter_kit.more"></a><a class="link" href="starter_kit.html#phoenix.starter_kit.more" title="More">More</a>
+</h3></div></div></div>

 As mentioned earlier, this chapter is not a thorough discourse of the library.
 It is meant only to cover enough ground to get you into high gear as quickly
- as possible. Some advanced stuff is not discussed here (e.g. Scopes);
+ as possible. Some advanced stuff is not discussed here (e.g. <a class="link" href="composite.html#phoenix.composite.scope" title="Scope">Scopes</a>);
 nor are features that provide alternative (short-hand) ways to do the same
- things (e.g. Bind vs. Lazy
+ things (e.g. <a class="link" href="composite.html#phoenix.composite.bind" title="Bind">Bind</a> vs. Lazy
 Functions).
 
-<div class="sidebar">
- <img src="../images/tip.png" alt="tip"> ...If you still wish to learn
- more, the read on...
- </div>
+<div class="sidebar">
+
+
+ <img src="../images/tip.png" alt="tip"> ...If you still wish to learn
+ more, the read on...
+ 
+</div>
</div>
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2002-2005 Joel
+<td align="right"><div class="copyright-footer">Copyright © 2002-2005 Joel
 de Guzman, Dan Marsden
 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)
@@ -504,7 +521,7 @@
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="introduction.html"><img src="../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="basics.html"><img src="../../../../../../doc/html/images/next.png" alt="Next"></a>
+<a accesskey="p" href="introduction.html"><img src="../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="basics.html"><img src="../../../../../../doc/src/images/next.png" alt="Next"></a>
</div>
</body>
</html>

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-07-19 16:15:52 EDT (Mon, 19 Jul 2010)
@@ -1,11 +1,11 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Wrap Up</title>
-<link rel="stylesheet" href="../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.66.1">
-<link rel="start" href="../index.html" title="Chapter 1. Phoenix 2.0">
-<link rel="up" href="../index.html" title="Chapter 1. Phoenix 2.0">
+<link rel="stylesheet" href="../../../../../../doc/src/boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
+<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">
<link rel="next" href="acknowledgement.html" title="Acknowledgement">
</head>
@@ -13,18 +13,19 @@
<table cellpadding="2" width="100%"><tr>
<td valign="top"><img alt="Boost C++ Libraries" width="277" height="86" src="../../../../../../boost.png"></td>
<td align="center">Home</td>
-<td align="center">Libraries</td>
+<td align="center">Libraries</td>
<td align="center">People</td>
<td align="center">FAQ</td>
<td align="center">More</td>
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="inside_phoenix.html"><img src="../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="acknowledgement.html"><img src="../../../../../../doc/html/images/next.png" alt="Next"></a>
+<a accesskey="p" href="inside_phoenix.html"><img src="../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="acknowledgement.html"><img src="../../../../../../doc/src/images/next.png" alt="Next"></a>
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="phoenix.wrap_up"></a>Wrap Up</h2></div></div></div>
+<a name="phoenix.wrap_up"></a><a class="link" href="wrap_up.html" title="Wrap Up">Wrap Up</a>
+</h2></div></div></div>

 Sooner or later more FP techniques become standard practice as people find
 the true value of this programming discipline outside the academe and into
@@ -37,21 +38,15 @@

 Let me quote Doug Gregor of Boost.org. About functional style programming libraries:
 
-<div class="blockquote"><blockquote class="blockquote">
-
- 
-
- They're gaining acceptance, but are somewhat stunted by the ubiquitousness
- of broken compilers. The C++ community is moving deeper into the so-called
- "STL- style" programming paradigm, which brings many aspects
- of functional programming into the fold. Look at, for instance, the Spirit
- parser to see how such function objects can be used to build Yacc-like
- grammars with semantic actions that can build abstract syntax trees on
- the fly. This type of functional composition is gaining momentum.
- 
-
- 
-</blockquote></div>
+<div class="blockquote"><blockquote class="blockquote">
+ They're gaining acceptance, but are somewhat stunted by the ubiquitousness
+ of broken compilers. The C++ community is moving deeper into the so-called
+ "STL- style" programming paradigm, which brings many aspects of
+ functional programming into the fold. Look at, for instance, the Spirit parser
+ to see how such function objects can be used to build Yacc-like grammars
+ with semantic actions that can build abstract syntax trees on the fly. This
+ type of functional composition is gaining momentum.
+ </blockquote></div>

 Indeed. Phoenix is another attempt to introduce more FP techniques into the
 mainstream. Not only is it a tool that will make life easier for the programmer.
@@ -67,7 +62,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2002-2005 Joel
+<td align="right"><div class="copyright-footer">Copyright © 2002-2005 Joel
 de Guzman, Dan Marsden
 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)
@@ -76,7 +71,7 @@
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="inside_phoenix.html"><img src="../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="acknowledgement.html"><img src="../../../../../../doc/html/images/next.png" alt="Next"></a>
+<a accesskey="p" href="inside_phoenix.html"><img src="../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="acknowledgement.html"><img src="../../../../../../doc/src/images/next.png" alt="Next"></a>
</div>
</body>
</html>

Modified: trunk/libs/spirit/repository/doc/html/index.html
==============================================================================
--- trunk/libs/spirit/repository/doc/html/index.html (original)
+++ trunk/libs/spirit/repository/doc/html/index.html 2010-07-19 16:15:52 EDT (Mon, 19 Jul 2010)
@@ -2,8 +2,8 @@
<head>
<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Spirit Repository 0.1</title>
-<link rel="stylesheet" href="../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
+<link rel="stylesheet" href="../../../../../doc/src/boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
<link rel="home" href="index.html" title="Spirit Repository 0.1">
<link rel="next" href="spirit_repository/preface.html" title="Preface">
</head>
@@ -11,14 +11,14 @@
<table cellpadding="2" width="100%"><tr>
<td valign="top"><img alt="Boost C++ Libraries" width="277" height="86" src="../../../../../boost.png"></td>
<td align="center">Home</td>
-<td align="center">Libraries</td>
+<td align="center">Libraries</td>
<td align="center">People</td>
<td align="center">FAQ</td>
<td align="center">More</td>
</tr></table>
<hr>
-<div class="spirit-nav"><a accesskey="n" href="spirit_repository/preface.html"><img src="../../../../../doc/html/images/next.png" alt="Next"></a></div>
-<div class="article" title="Spirit Repository 0.1">
+<div class="spirit-nav"><a accesskey="n" href="spirit_repository/preface.html"><img src="../../../../../doc/src/images/next.png" alt="Next"></a></div>
+<div class="article">
<div class="titlepage">
<div>
<div><h2 class="title">
@@ -32,8 +32,8 @@
</h3></div>
</div></div>
<div>Copyright © 2001-2010 Joel de Guzman, Hartmut Kaiser</div>
-<div><div class="legalnotice" title="Legal Notice">
-<a name="id619442"></a>
+<div><div class="legalnotice">
+<a name="id759740"></a>
 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)
 
@@ -79,10 +79,10 @@
</div>
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
-<td align="left">Last revised: December 30, 2009 at 16:13:16 GMT</td>
+<td align="left">Last revised: July 19, 2010 at 19:04:13 GMT</td>
<td align="right"><div class="copyright-footer"></div></td>
</tr></table>
<hr>
-<div class="spirit-nav"><a accesskey="n" href="spirit_repository/preface.html"><img src="../../../../../doc/html/images/next.png" alt="Next"></a></div>
+<div class="spirit-nav"><a accesskey="n" href="spirit_repository/preface.html"><img src="../../../../../doc/src/images/next.png" alt="Next"></a></div>
</body>
</html>

Modified: trunk/libs/spirit/repository/doc/html/spirit_repository/karma_components.html
==============================================================================
--- trunk/libs/spirit/repository/doc/html/spirit_repository/karma_components.html (original)
+++ trunk/libs/spirit/repository/doc/html/spirit_repository/karma_components.html 2010-07-19 16:15:52 EDT (Mon, 19 Jul 2010)
@@ -2,8 +2,8 @@
<head>
<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Karma Components</title>
-<link rel="stylesheet" href="../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
+<link rel="stylesheet" href="../../../../../../doc/src/boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
<link rel="home" href="../index.html" title="Spirit Repository 0.1">
<link rel="up" href="../index.html" title="Spirit Repository 0.1">
<link rel="prev" href="qi_components/nonterminal/subrule.html" title="Qi subrules">
@@ -13,16 +13,16 @@
<table cellpadding="2" width="100%"><tr>
<td valign="top"><img alt="Boost C++ Libraries" width="277" height="86" src="../../../../../../boost.png"></td>
<td align="center">Home</td>
-<td align="center">Libraries</td>
+<td align="center">Libraries</td>
<td align="center">People</td>
<td align="center">FAQ</td>
<td align="center">More</td>
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="qi_components/nonterminal/subrule.html"><img src="../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="karma_components/directives.html"><img src="../../../../../../doc/html/images/next.png" alt="Next"></a>
+<a accesskey="p" href="qi_components/nonterminal/subrule.html"><img src="../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="karma_components/directives.html"><img src="../../../../../../doc/src/images/next.png" alt="Next"></a>
</div>
-<div class="section" title="Karma Components">
+<div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
<a name="spirit_repository.karma_components"></a><a class="link" href="karma_components.html" title="Karma Components">Karma Components</a>
</h2></div></div></div>
@@ -47,7 +47,7 @@
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="qi_components/nonterminal/subrule.html"><img src="../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="karma_components/directives.html"><img src="../../../../../../doc/html/images/next.png" alt="Next"></a>
+<a accesskey="p" href="qi_components/nonterminal/subrule.html"><img src="../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="karma_components/directives.html"><img src="../../../../../../doc/src/images/next.png" alt="Next"></a>
</div>
</body>
</html>

Modified: trunk/libs/spirit/repository/doc/html/spirit_repository/karma_components/directives.html
==============================================================================
--- trunk/libs/spirit/repository/doc/html/spirit_repository/karma_components/directives.html (original)
+++ trunk/libs/spirit/repository/doc/html/spirit_repository/karma_components/directives.html 2010-07-19 16:15:52 EDT (Mon, 19 Jul 2010)
@@ -2,8 +2,8 @@
<head>
<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Karma Generator Directives</title>
-<link rel="stylesheet" href="../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
+<link rel="stylesheet" href="../../../../../../../doc/src/boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
<link rel="home" href="../../index.html" title="Spirit Repository 0.1">
<link rel="up" href="../karma_components.html" title="Karma Components">
<link rel="prev" href="../karma_components.html" title="Karma Components">
@@ -13,16 +13,16 @@
<table cellpadding="2" width="100%"><tr>
<td valign="top"><img alt="Boost C++ Libraries" width="277" height="86" src="../../../../../../../boost.png"></td>
<td align="center">Home</td>
-<td align="center">Libraries</td>
+<td align="center">Libraries</td>
<td align="center">People</td>
<td align="center">FAQ</td>
<td align="center">More</td>
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="../karma_components.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../karma_components.html"><img src="../../../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../../index.html"><img src="../../../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="directives/karma_confix_generator.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
+<a accesskey="p" href="../karma_components.html"><img src="../../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../karma_components.html"><img src="../../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../../index.html"><img src="../../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="directives/karma_confix_generator.html"><img src="../../../../../../../doc/src/images/next.png" alt="Next"></a>
</div>
-<div class="section" title="Karma Generator Directives">
+<div class="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="spirit_repository.karma_components.directives"></a><a class="link" href="directives.html" title="Karma Generator Directives"> Karma
Generator Directives</a>
@@ -40,7 +40,7 @@
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="../karma_components.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../karma_components.html"><img src="../../../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../../index.html"><img src="../../../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="directives/karma_confix_generator.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
+<a accesskey="p" href="../karma_components.html"><img src="../../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../karma_components.html"><img src="../../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../../index.html"><img src="../../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="directives/karma_confix_generator.html"><img src="../../../../../../../doc/src/images/next.png" alt="Next"></a>
</div>
</body>
</html>

Modified: trunk/libs/spirit/repository/doc/html/spirit_repository/karma_components/directives/karma_confix_generator.html
==============================================================================
--- trunk/libs/spirit/repository/doc/html/spirit_repository/karma_components/directives/karma_confix_generator.html (original)
+++ trunk/libs/spirit/repository/doc/html/spirit_repository/karma_components/directives/karma_confix_generator.html 2010-07-19 16:15:52 EDT (Mon, 19 Jul 2010)
@@ -2,8 +2,8 @@
<head>
<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Karma Confix Generator</title>
-<link rel="stylesheet" href="../../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
+<link rel="stylesheet" href="../../../../../../../../doc/src/boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
<link rel="home" href="../../../index.html" title="Spirit Repository 0.1">
<link rel="up" href="../directives.html" title="Karma Generator Directives">
<link rel="prev" href="../directives.html" title="Karma Generator Directives">
@@ -13,22 +13,22 @@
<table cellpadding="2" width="100%"><tr>
<td valign="top"><img alt="Boost C++ Libraries" width="277" height="86" src="../../../../../../../../boost.png"></td>
<td align="center">Home</td>
-<td align="center">Libraries</td>
+<td align="center">Libraries</td>
<td align="center">People</td>
<td align="center">FAQ</td>
<td align="center">More</td>
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="../directives.html"><img src="../../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../directives.html"><img src="../../../../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../../../index.html"><img src="../../../../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="../nonterminal.html"><img src="../../../../../../../../doc/html/images/next.png" alt="Next"></a>
+<a accesskey="p" href="../directives.html"><img src="../../../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../directives.html"><img src="../../../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../../../index.html"><img src="../../../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="../nonterminal.html"><img src="../../../../../../../../doc/src/images/next.png" alt="Next"></a>
</div>
-<div class="section" title="Karma Confix Generator">
+<div class="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="spirit_repository.karma_components.directives.karma_confix_generator"></a><a class="link" href="karma_confix_generator.html" title="Karma Confix Generator">Karma
 Confix Generator</a>
</h4></div></div></div>
<a name="spirit_repository.karma_components.directives.karma_confix_generator.description"></a><h6>
-<a name="id635192"></a>
+<a name="id771856"></a>
 <a class="link" href="karma_confix_generator.html#spirit_repository.karma_components.directives.karma_confix_generator.description">Description</a>
 </h6>

@@ -93,20 +93,20 @@
 tag using a simple: <code class="computeroutput">ol["Some text"]</code> (which results in <code class="computeroutput"><ol>Some text</ol></code>).
 
<a name="spirit_repository.karma_components.directives.karma_confix_generator.header"></a><h6>
-<a name="id636089"></a>
+<a name="id772961"></a>
 <a class="link" href="karma_confix_generator.html#spirit_repository.karma_components.directives.karma_confix_generator.header">Header</a>
 </h6>
<pre class="programlisting">// forwards to <boost/spirit/repository/home/karma/directive/confix.hpp>
#include <boost/spirit/repository/include/karma_confix.hpp>
</pre>
<a name="spirit_repository.karma_components.directives.karma_confix_generator.synopsis"></a><h6>
-<a name="id636162"></a>
+<a name="id773061"></a>
 <a class="link" href="karma_confix_generator.html#spirit_repository.karma_components.directives.karma_confix_generator.synopsis">Synopsis</a>
 </h6>
<pre class="programlisting">confix(prefix, suffix)[subject]
</pre>
<a name="spirit_repository.karma_components.directives.karma_confix_generator.parameters"></a><h6>
-<a name="id636210"></a>
+<a name="id773128"></a>
 <a class="link" href="karma_confix_generator.html#spirit_repository.karma_components.directives.karma_confix_generator.parameters">Parameters</a>
 </h6>
<div class="informaltable"><table class="table">
@@ -116,57 +116,57 @@
</colgroup>
<thead><tr>
<th>
- 
- Parameter
- 
+ 
+ Parameter
+ 
 </th>
<th>
- 
- Description
- 
+ 
+ Description
+ 
 </th>
</tr></thead>
<tbody>
<tr>
<td>
- 
- <code class="computeroutput">prefix</code>
- 
+ 
+ <code class="computeroutput">prefix</code>
+ 
 </td>
<td>
- 
- The generator construct to use to format the opening (the prefix).
- The prefix is the part generated before any
- output as generated by the <code class="computeroutput">subject</code>.
- 
+ 
+ The generator construct to use to format the opening (the prefix).
+ The prefix is the part generated before
+ any output as generated by the <code class="computeroutput">subject</code>.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">suffix</code>
- 
+ 
+ <code class="computeroutput">suffix</code>
+ 
 </td>
<td>
- 
- The generator construct to use to format the ending (the suffix).
- The suffix is the part generated after any
- output as generated by the <code class="computeroutput">subject</code>.
- 
+ 
+ The generator construct to use to format the ending (the suffix).
+ The suffix is the part generated after any
+ output as generated by the <code class="computeroutput">subject</code>.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">subject</code>
- 
+ 
+ <code class="computeroutput">subject</code>
+ 
 </td>
<td>
- 
- The generator construct to use to format the actual output in between
- the <code class="computeroutput">prefix</code> and
- <code class="computeroutput">suffix</code> parts.
- 
+ 
+ The generator construct to use to format the actual output in
+ between the <code class="computeroutput">prefix</code>
+ and <code class="computeroutput">suffix</code> parts.
+ 
 </td>
</tr>
</tbody>
@@ -175,7 +175,7 @@
 All three parameters can be arbitrary complex generators themselves.
 
<a name="spirit_repository.karma_components.directives.karma_confix_generator.attribute"></a><h6>
-<a name="id636368"></a>
+<a name="id773327"></a>
 <a class="link" href="karma_confix_generator.html#spirit_repository.karma_components.directives.karma_confix_generator.attribute">Attribute</a>
 </h6>

@@ -187,7 +187,7 @@
 
<pre class="programlisting">a: A --> confix(p, s)[a]: A
</pre>
-<div class="note" title="Note"><table border="0" summary="Note">
+<div class="note"><table border="0" summary="Note">
<tr>
<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../../../images/note.png"></td>
<th align="left">Note</th>
@@ -202,7 +202,7 @@
 </td></tr>
</table></div>
<a name="spirit_repository.karma_components.directives.karma_confix_generator.example"></a><h6>
-<a name="id636544"></a>
+<a name="id773559"></a>
 <a class="link" href="karma_confix_generator.html#spirit_repository.karma_components.directives.karma_confix_generator.example">Example</a>
 </h6>

@@ -211,7 +211,7 @@
 styles and a function prototype (for the full example code see here: confix.cpp)
 
<a name="spirit_repository.karma_components.directives.karma_confix_generator.prerequisites"></a><h6>
-<a name="id636574"></a>
+<a name="id773606"></a>
 <a class="link" href="karma_confix_generator.html#spirit_repository.karma_components.directives.karma_confix_generator.prerequisites">Prerequisites</a>
 </h6>

@@ -221,35 +221,27 @@
 generator.
 

- 
-
-
+

<pre class="programlisting">#include <boost/spirit/include/karma.hpp>
#include <boost/spirit/repository/include/karma_confix.hpp>
</pre>

- 
-
 

 To make all the code below more readable we introduce the following namespaces.
 

- 
-
-
+

<pre class="programlisting">using namespace boost::spirit;
using namespace boost::spirit::ascii;
using boost::spirit::repository::confix;
</pre>

- 
-
 
<a name="spirit_repository.karma_components.directives.karma_confix_generator.generating_different_comment_styles"></a><h6>
-<a name="id636817"></a>
+<a name="id773903"></a>
 <a class="link" href="karma_confix_generator.html#spirit_repository.karma_components.directives.karma_confix_generator.generating_different_comment_styles">Generating
 Different Comment Styles</a>
 </h6>
@@ -258,9 +250,7 @@
 a C++ comment:
 

- 
-
-
+

<pre class="programlisting">// C++ comment
std::cout <<
@@ -271,8 +261,6 @@
 ) << std::endl;
</pre>

- 
-
 

 This code snippet will obviouly generate <code class="computeroutput">//
@@ -280,9 +268,7 @@
 comment proves to be straightforward:
 

- 
-
-
+

<pre class="programlisting">// C comment
std::cout <<
@@ -293,15 +279,13 @@
 ) << std::endl;
</pre>

- 
-
 

 which again will generate <code class="computeroutput">/* This is a comment
 */ </code>.
 
<a name="spirit_repository.karma_components.directives.karma_confix_generator.generating_a_function_prototype"></a><h6>
-<a name="id638757"></a>
+<a name="id774271"></a>
 <a class="link" href="karma_confix_generator.html#spirit_repository.karma_components.directives.karma_confix_generator.generating_a_function_prototype">Generating
 a Function Prototype</a>
 </h6>
@@ -310,9 +294,7 @@
 names is simple as well:
 

- 
-
-
+

<pre class="programlisting">// Generate a function call with an arbitrary parameter list
std::vector<std::string> parameters;
@@ -328,8 +310,6 @@
 ) << std::endl;
</pre>

- 
-
 

 which generates the expected output: <code class="computeroutput">func(par1,par2,par3)</code>.
@@ -345,7 +325,7 @@
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="../directives.html"><img src="../../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../directives.html"><img src="../../../../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../../../index.html"><img src="../../../../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="../nonterminal.html"><img src="../../../../../../../../doc/html/images/next.png" alt="Next"></a>
+<a accesskey="p" href="../directives.html"><img src="../../../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../directives.html"><img src="../../../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../../../index.html"><img src="../../../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="../nonterminal.html"><img src="../../../../../../../../doc/src/images/next.png" alt="Next"></a>
</div>
</body>
</html>

Modified: trunk/libs/spirit/repository/doc/html/spirit_repository/karma_components/nonterminal.html
==============================================================================
--- trunk/libs/spirit/repository/doc/html/spirit_repository/karma_components/nonterminal.html (original)
+++ trunk/libs/spirit/repository/doc/html/spirit_repository/karma_components/nonterminal.html 2010-07-19 16:15:52 EDT (Mon, 19 Jul 2010)
@@ -2,8 +2,8 @@
<head>
<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Karma Generator Non-terminals</title>
-<link rel="stylesheet" href="../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
+<link rel="stylesheet" href="../../../../../../../doc/src/boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
<link rel="home" href="../../index.html" title="Spirit Repository 0.1">
<link rel="up" href="../karma_components.html" title="Karma Components">
<link rel="prev" href="directives/karma_confix_generator.html" title="Karma Confix Generator">
@@ -13,16 +13,16 @@
<table cellpadding="2" width="100%"><tr>
<td valign="top"><img alt="Boost C++ Libraries" width="277" height="86" src="../../../../../../../boost.png"></td>
<td align="center">Home</td>
-<td align="center">Libraries</td>
+<td align="center">Libraries</td>
<td align="center">People</td>
<td align="center">FAQ</td>
<td align="center">More</td>
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="directives/karma_confix_generator.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../karma_components.html"><img src="../../../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../../index.html"><img src="../../../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="nonterminal/subrule.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
+<a accesskey="p" href="directives/karma_confix_generator.html"><img src="../../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../karma_components.html"><img src="../../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../../index.html"><img src="../../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="nonterminal/subrule.html"><img src="../../../../../../../doc/src/images/next.png" alt="Next"></a>
</div>
-<div class="section" title="Karma Generator Non-terminals">
+<div class="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="spirit_repository.karma_components.nonterminal"></a><a class="link" href="nonterminal.html" title="Karma Generator Non-terminals"> Karma
Generator Non-terminals</a>
@@ -40,7 +40,7 @@
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="directives/karma_confix_generator.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../karma_components.html"><img src="../../../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../../index.html"><img src="../../../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="nonterminal/subrule.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
+<a accesskey="p" href="directives/karma_confix_generator.html"><img src="../../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../karma_components.html"><img src="../../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../../index.html"><img src="../../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="nonterminal/subrule.html"><img src="../../../../../../../doc/src/images/next.png" alt="Next"></a>
</div>
</body>
</html>

Modified: trunk/libs/spirit/repository/doc/html/spirit_repository/karma_components/nonterminal/subrule.html
==============================================================================
--- trunk/libs/spirit/repository/doc/html/spirit_repository/karma_components/nonterminal/subrule.html (original)
+++ trunk/libs/spirit/repository/doc/html/spirit_repository/karma_components/nonterminal/subrule.html 2010-07-19 16:15:52 EDT (Mon, 19 Jul 2010)
@@ -2,8 +2,8 @@
<head>
<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Karma subrules</title>
-<link rel="stylesheet" href="../../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
+<link rel="stylesheet" href="../../../../../../../../doc/src/boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
<link rel="home" href="../../../index.html" title="Spirit Repository 0.1">
<link rel="up" href="../nonterminal.html" title="Karma Generator Non-terminals">
<link rel="prev" href="../nonterminal.html" title="Karma Generator Non-terminals">
@@ -12,22 +12,22 @@
<table cellpadding="2" width="100%"><tr>
<td valign="top"><img alt="Boost C++ Libraries" width="277" height="86" src="../../../../../../../../boost.png"></td>
<td align="center">Home</td>
-<td align="center">Libraries</td>
+<td align="center">Libraries</td>
<td align="center">People</td>
<td align="center">FAQ</td>
<td align="center">More</td>
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="../nonterminal.html"><img src="../../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../nonterminal.html"><img src="../../../../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../../../index.html"><img src="../../../../../../../../doc/html/images/home.png" alt="Home"></a>
+<a accesskey="p" href="../nonterminal.html"><img src="../../../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../nonterminal.html"><img src="../../../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../../../index.html"><img src="../../../../../../../../doc/src/images/home.png" alt="Home"></a>
</div>
-<div class="section" title="Karma subrules">
+<div class="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="spirit_repository.karma_components.nonterminal.subrule"></a><a class="link" href="subrule.html" title="Karma subrules">
 Karma subrules</a>
</h4></div></div></div>
<a name="spirit_repository.karma_components.nonterminal.subrule.description"></a><h6>
-<a name="id639090"></a>
+<a name="id774685"></a>
 <a class="link" href="subrule.html#spirit_repository.karma_components.nonterminal.subrule.description">Description</a>
 </h6>

@@ -49,20 +49,18 @@
 
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
- subrules can only be defined and used within the same generator expression.
- A subrule cannot be defined at one location, and then used in another
- location.
- </li>
+ subrules can only be defined and used within the same generator expression.
+ A subrule cannot be defined at one location, and then used in another
+ location.
+ </li>
<li class="listitem">
- subrules put a massive strain on the C++ compiler. They increase compile
- times and memory usage during compilation, and also increase the risk
- of hitting compiler limits and/or bugs.
- </li>
+ subrules put a massive strain on the C++ compiler. They increase compile
+ times and memory usage during compilation, and also increase the risk
+ of hitting compiler limits and/or bugs.
+ </li>
</ul></div>

- 
-
-
+

<pre class="programlisting">entry %= (
 ast_node %= int_ | binary_node | unary_node
@@ -73,8 +71,6 @@
);
</pre>

- 
-
 

 The example above can be found here: ../../example/karma/calc2_ast_dump_sr.cpp
@@ -89,21 +85,21 @@
 parts), whereas the rest can use rules and grammars.
 
<a name="spirit_repository.karma_components.nonterminal.subrule.header"></a><h6>
-<a name="id639352"></a>
+<a name="id775027"></a>
 <a class="link" href="subrule.html#spirit_repository.karma_components.nonterminal.subrule.header">Header</a>
 </h6>
<pre class="programlisting">// forwards to <boost/spirit/repository/home/karma/nonterminal/subrule.hpp>
#include <boost/spirit/repository/include/karma_subrule.hpp>
</pre>
<a name="spirit_repository.karma_components.nonterminal.subrule.synopsis__declaration_"></a><h6>
-<a name="id639428"></a>
+<a name="id775127"></a>
 <a class="link" href="subrule.html#spirit_repository.karma_components.nonterminal.subrule.synopsis__declaration_">Synopsis
 (declaration)</a>
 </h6>
<pre class="programlisting">subrule<ID, A1, A2> sr(name);
</pre>
<a name="spirit_repository.karma_components.nonterminal.subrule.parameters__declaration_"></a><h6>
-<a name="id639493"></a>
+<a name="id775212"></a>
 <a class="link" href="subrule.html#spirit_repository.karma_components.nonterminal.subrule.parameters__declaration_">Parameters
 (declaration)</a>
 </h6>
@@ -114,66 +110,66 @@
</colgroup>
<thead><tr>
<th>
- 
- Parameter
- 
+ 
+ Parameter
+ 
 </th>
<th>
- 
- Description
- 
+ 
+ Description
+ 
 </th>
</tr></thead>
<tbody>
<tr>
<td>
- 
- <code class="computeroutput">ID</code>
- 
+ 
+ <code class="computeroutput">ID</code>
+ 
 </td>
<td>
- 
- Required numeric argument. Gives the subrule a unique 'identification
- tag'.
- 
+ 
+ Required numeric argument. Gives the subrule a unique 'identification
+ tag'.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">A1</code>, <code class="computeroutput">A2</code>
- 
+ 
+ <code class="computeroutput">A1</code>, <code class="computeroutput">A2</code>
+ 
 </td>
<td>
- 
- Optional types, can be specified in any order. Can be one of 1.
- signature, 2. locals (see rules reference for more information
- on those parameters).
- 
- 
- Note that the delimiter type need not be specified in the parameters,
- unlike with grammars and rules. Subrules will automatically use
- the delimiter type which is in effect when they are invoked.
- 
+ 
+ Optional types, can be specified in any order. Can be one of
+ 1. signature, 2. locals (see rules reference for more information
+ on those parameters).
+ 
+ 
+ Note that the delimiter type need not be specified in the parameters,
+ unlike with grammars and rules. Subrules will automatically use
+ the delimiter type which is in effect when they are invoked.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">name</code>
- 
+ 
+ <code class="computeroutput">name</code>
+ 
 </td>
<td>
- 
- Optional string. Gives the subrule a name, useful for debugging
- and error handling.
- 
+ 
+ Optional string. Gives the subrule a name, useful for debugging
+ and error handling.
+ 
 </td>
</tr>
</tbody>
</table></div>
<a name="spirit_repository.karma_components.nonterminal.subrule.synopsis__usage_"></a><h6>
-<a name="id639622"></a>
+<a name="id775374"></a>
 <a class="link" href="subrule.html#spirit_repository.karma_components.nonterminal.subrule.synopsis__usage_">Synopsis
 (usage)</a>
 </h6>
@@ -202,7 +198,7 @@
)(a1, a2, ...) // Arguments to group, i.e. to start subrule srA
</pre>
<a name="spirit_repository.karma_components.nonterminal.subrule.parameters__usage_"></a><h6>
-<a name="id639858"></a>
+<a name="id775661"></a>
 <a class="link" href="subrule.html#spirit_repository.karma_components.nonterminal.subrule.parameters__usage_">Parameters
 (usage)</a>
 </h6>
@@ -213,120 +209,120 @@
</colgroup>
<thead><tr>
<th>
- 
- Parameter
- 
+ 
+ Parameter
+ 
 </th>
<th>
- 
- Description
- 
+ 
+ Description
+ 
 </th>
</tr></thead>
<tbody>
<tr>
<td>
- 
- <code class="computeroutput">sr1</code>, <code class="computeroutput">sr2</code>
- 
+ 
+ <code class="computeroutput">sr1</code>, <code class="computeroutput">sr2</code>
+ 
 </td>
<td>
- 
- Subrules with different IDs.
- 
+ 
+ Subrules with different IDs.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">expr1</code>, <code class="computeroutput">expr2</code>
- 
+ 
+ <code class="computeroutput">expr1</code>, <code class="computeroutput">expr2</code>
+ 
 </td>
<td>
- 
- Generator expressions. Can include <code class="computeroutput">sr1</code>
- and <code class="computeroutput">sr2</code>, as well
- as any other valid generator expressions.
- 
+ 
+ Generator expressions. Can include <code class="computeroutput">sr1</code>
+ and <code class="computeroutput">sr2</code>, as well
+ as any other valid generator expressions.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">srA</code>
- 
+ 
+ <code class="computeroutput">srA</code>
+ 
 </td>
<td>
- 
- Subrule with a synthesized attribute and inherited attributes.
- 
+ 
+ Subrule with a synthesized attribute and inherited attributes.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">srB</code>
- 
+ 
+ <code class="computeroutput">srB</code>
+ 
 </td>
<td>
- 
- Subrule with a synthesized attribute.
- 
+ 
+ Subrule with a synthesized attribute.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">srC</code>
- 
+ 
+ <code class="computeroutput">srC</code>
+ 
 </td>
<td>
- 
- Subrule with inherited attributes.
- 
+ 
+ Subrule with inherited attributes.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">exprA</code>, <code class="computeroutput">exprB</code>, <code class="computeroutput">exprC</code>
- 
+ 
+ <code class="computeroutput">exprA</code>, <code class="computeroutput">exprB</code>, <code class="computeroutput">exprC</code>
+ 
 </td>
<td>
- 
- Generator expressions.
- 
+ 
+ Generator expressions.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">a1</code>, <code class="computeroutput">a2</code>
- 
+ 
+ <code class="computeroutput">a1</code>, <code class="computeroutput">a2</code>
+ 
 </td>
<td>
- 
- Arguments passed to the subrule group. They are passed as inherited
- attributes to the group's start subrule, <code class="computeroutput">srA</code>.
- 
+ 
+ Arguments passed to the subrule group. They are passed as inherited
+ attributes to the group's start subrule, <code class="computeroutput">srA</code>.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">c1</code>, <code class="computeroutput">c2</code>
- 
+ 
+ <code class="computeroutput">c1</code>, <code class="computeroutput">c2</code>
+ 
 </td>
<td>
- 
- Arguments passed as inherited attributes to subrule <code class="computeroutput">srC</code>.
- 
+ 
+ Arguments passed as inherited attributes to subrule <code class="computeroutput">srC</code>.
+ 
 </td>
</tr>
</tbody>
</table></div>
<a name="spirit_repository.karma_components.nonterminal.subrule.groups"></a><h6>
-<a name="id640172"></a>
+<a name="id776039"></a>
 <a class="link" href="subrule.html#spirit_repository.karma_components.nonterminal.subrule.groups">Groups</a>
 </h6>

@@ -371,7 +367,7 @@
;
</pre>
<a name="spirit_repository.karma_components.nonterminal.subrule.attributes"></a><h6>
-<a name="id640566"></a>
+<a name="id776523"></a>
 <a class="link" href="subrule.html#spirit_repository.karma_components.nonterminal.subrule.attributes">Attributes</a>
 </h6>

@@ -380,27 +376,27 @@
 
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
- the type of its synthesized attribute is the one specified in the subrule's
- signature, if any. Otherwise it is <code class="computeroutput">unused_type</code>.
- </li>
+ the type of its synthesized attribute is the one specified in the subrule's
+ signature, if any. Otherwise it is <code class="computeroutput">unused_type</code>.
+ </li>
<li class="listitem">
- the types of its inherited attributes are the ones specified in the subrule's
- signature, if any. Otherwise the subrule has no inherited attributes.
- </li>
+ the types of its inherited attributes are the ones specified in the
+ subrule's signature, if any. Otherwise the subrule has no inherited
+ attributes.
+ </li>
<li class="listitem">
- an auto-subrule can be defined by assigning it with the <code class="computeroutput">%=</code> syntax. In this case, the subrule's
- synthesized attribute is automatically propagated to the RHS generator's
- attribute.
- </li>
+ an auto-subrule can be defined by assigning it with the <code class="computeroutput">%=</code> syntax. In this case, the subrule's
+ synthesized attribute is automatically propagated to the RHS generator's
+ attribute.
+ </li>
<li class="listitem">
- the Phoenix placeholders <code class="computeroutput">_val</code>,
- <code class="computeroutput">_r1</code>, <code class="computeroutput">_r2</code>,
- ... are available to refer to the subrule's synthesized and inherited
- attributes, if present.
- </li>
+ the Phoenix placeholders <code class="computeroutput">_val</code>,
+ <code class="computeroutput">_r1</code>, <code class="computeroutput">_r2</code>, ... are available to refer to
+ the subrule's synthesized and inherited attributes, if present.
+ </li>
</ul></div>
<a name="spirit_repository.karma_components.nonterminal.subrule.locals"></a><h6>
-<a name="id640639"></a>
+<a name="id776641"></a>
 <a class="link" href="subrule.html#spirit_repository.karma_components.nonterminal.subrule.locals">Locals</a>
 </h6>

@@ -410,16 +406,14 @@
 refer to the subrule's locals, if present.
 
<a name="spirit_repository.karma_components.nonterminal.subrule.example"></a><h6>
-<a name="id640675"></a>
+<a name="id776689"></a>
 <a class="link" href="subrule.html#spirit_repository.karma_components.nonterminal.subrule.example">Example</a>
 </h6>

 Some includes:
 

- 
-
-
+

<pre class="programlisting">#include <boost/spirit/include/karma.hpp>
#include <boost/spirit/repository/include/karma_subrule.hpp>
@@ -428,32 +422,24 @@
#include <boost/spirit/include/phoenix_fusion.hpp>
</pre>

- 
-
 

 Some using declarations:
 

- 
-
-
+

<pre class="programlisting">using namespace boost::spirit;
using namespace boost::spirit::ascii;
namespace repo = boost::spirit::repository;
</pre>

- 
-
 

 A grammar containing only one rule, defined with a group of 2 subrules:
 

- 
-
-
+

<pre class="programlisting">template <typename OutputIterator>
struct mini_xml_generator
@@ -478,8 +464,6 @@
};
</pre>

- 
-
 

 The definitions of the <code class="computeroutput">mini_xml</code>
@@ -488,7 +472,7 @@
 <a href="../../../../../example/karma/mini_xml_karma_sr.cpp" target="_top">../../example/karma/mini_xml_karma_sr.cpp</a>
 
<a name="spirit_repository.karma_components.nonterminal.subrule.performance"></a><h6>
-<a name="id642253"></a>
+<a name="id777754"></a>
 <a class="link" href="subrule.html#spirit_repository.karma_components.nonterminal.subrule.performance">Performance</a>
 </h6>

@@ -499,7 +483,7 @@
 subrules is very similar, so performance is very similar too).
 
<a name="spirit_repository.karma_components.nonterminal.subrule.notes"></a><h6>
-<a name="id642290"></a>
+<a name="id777801"></a>
 <a class="link" href="subrule.html#spirit_repository.karma_components.nonterminal.subrule.notes">Notes</a>
 </h6>

@@ -523,7 +507,7 @@
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="../nonterminal.html"><img src="../../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../nonterminal.html"><img src="../../../../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../../../index.html"><img src="../../../../../../../../doc/html/images/home.png" alt="Home"></a>
+<a accesskey="p" href="../nonterminal.html"><img src="../../../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../nonterminal.html"><img src="../../../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../../../index.html"><img src="../../../../../../../../doc/src/images/home.png" alt="Home"></a>
</div>
</body>
</html>

Modified: trunk/libs/spirit/repository/doc/html/spirit_repository/preface.html
==============================================================================
--- trunk/libs/spirit/repository/doc/html/spirit_repository/preface.html (original)
+++ trunk/libs/spirit/repository/doc/html/spirit_repository/preface.html 2010-07-19 16:15:52 EDT (Mon, 19 Jul 2010)
@@ -2,8 +2,8 @@
<head>
<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Preface</title>
-<link rel="stylesheet" href="../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
+<link rel="stylesheet" href="../../../../../../doc/src/boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
<link rel="home" href="../index.html" title="Spirit Repository 0.1">
<link rel="up" href="../index.html" title="Spirit Repository 0.1">
<link rel="prev" href="../index.html" title="Spirit Repository 0.1">
@@ -13,21 +13,21 @@
<table cellpadding="2" width="100%"><tr>
<td valign="top"><img alt="Boost C++ Libraries" width="277" height="86" src="../../../../../../boost.png"></td>
<td align="center">Home</td>
-<td align="center">Libraries</td>
+<td align="center">Libraries</td>
<td align="center">People</td>
<td align="center">FAQ</td>
<td align="center">More</td>
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="../index.html"><img src="../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="qi_components.html"><img src="../../../../../../doc/html/images/next.png" alt="Next"></a>
+<a accesskey="p" href="../index.html"><img src="../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="qi_components.html"><img src="../../../../../../doc/src/images/next.png" alt="Next"></a>
</div>
-<div class="section" title="Preface">
+<div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
<a name="spirit_repository.preface"></a><a class="link" href="preface.html" title="Preface">Preface</a>
</h2></div></div></div>
<a name="spirit_repository.preface.the_spirit_repository"></a><h4>
-<a name="id619472"></a>
+<a name="id759774"></a>
 <a class="link" href="preface.html#spirit_repository.preface.the_spirit_repository">The Spirit
 Repository</a>
 </h4>
@@ -77,7 +77,7 @@
 core library.
 
<a name="spirit_repository.preface.how_to_use_this_manual"></a><h4>
-<a name="id619560"></a>
+<a name="id759903"></a>
 <a class="link" href="preface.html#spirit_repository.preface.how_to_use_this_manual">How to use
 this manual</a>
 </h4>
@@ -86,7 +86,7 @@
 icons precede some text to indicate:
 
<div class="table">
-<a name="id619574"></a>Table 1. Icons
+<a name="id759921"></a>Table 1. Icons
<div class="table-contents"><table class="table" summary="Icons">
<colgroup>
<col>
@@ -95,108 +95,109 @@
</colgroup>
<thead><tr>
<th>
- 
- Icon
- 
- </th>
+ 
+ Icon
+ 
+ </th>
<th>
- 
- Name
- 
- </th>
+ 
+ Name
+ 
+ </th>
<th>
- 
- Meaning
- 
- </th>
+ 
+ Meaning
+ 
+ </th>
</tr></thead>
<tbody>
<tr>
<td>
- 
- <img src="../images/note.png" alt="note">
- 
- </td>
-<td>
- 
- Note
- 
- </td>
-<td>
- 
- Generally useful information (an aside that doesn't fit in the flow of
- the text)
- 
- </td>
+ 
+ <img src="../images/note.png" alt="note">
+ 
+ </td>
+<td>
+ 
+ Note
+ 
+ </td>
+<td>
+ 
+ Generally useful information (an aside that doesn't fit in the flow
+ of the text)
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <img src="../images/tip.png" alt="tip">
- 
- </td>
-<td>
- 
- Tip
- 
- </td>
-<td>
- 
- Suggestion on how to do something (especially something that not be obvious)
- 
- </td>
+ 
+ <img src="../images/tip.png" alt="tip">
+ 
+ </td>
+<td>
+ 
+ Tip
+ 
+ </td>
+<td>
+ 
+ Suggestion on how to do something (especially something that not
+ be obvious)
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <img src="../images/important.png" alt="important">
- 
- </td>
-<td>
- 
- Important
- 
- </td>
-<td>
- 
- Important note on something to take particular notice of
- 
- </td>
+ 
+ <img src="../images/important.png" alt="important">
+ 
+ </td>
+<td>
+ 
+ Important
+ 
+ </td>
+<td>
+ 
+ Important note on something to take particular notice of
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <img src="../images/caution.png" alt="caution">
- 
- </td>
-<td>
- 
- Caution
- 
- </td>
-<td>
- 
- Take special care with this - it may not be what you expect and may cause
- bad results
- 
- </td>
+ 
+ <img src="../images/caution.png" alt="caution">
+ 
+ </td>
+<td>
+ 
+ Caution
+ 
+ </td>
+<td>
+ 
+ Take special care with this - it may not be what you expect and may
+ cause bad results
+ 
+ </td>
</tr>
<tr>
<td>
- 
- <img src="../images/alert.png" alt="alert">
- 
- </td>
-<td>
- 
- Danger
- 
- </td>
-<td>
- 
- This is likely to cause serious trouble if ignored
- 
- </td>
+ 
+ <img src="../images/alert.png" alt="alert">
+ 
+ </td>
+<td>
+ 
+ Danger
+ 
+ </td>
+<td>
+ 
+ This is likely to cause serious trouble if ignored
+ 
+ </td>
</tr>
</tbody>
</table></div>
@@ -207,7 +208,7 @@
 Tools</a>.
 
<a name="spirit_repository.preface.support"></a><h4>
-<a name="id619815"></a>
+<a name="id760179"></a>
 <a class="link" href="preface.html#spirit_repository.preface.support">Support</a>
 </h4>

@@ -231,7 +232,7 @@
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="../index.html"><img src="../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="qi_components.html"><img src="../../../../../../doc/html/images/next.png" alt="Next"></a>
+<a accesskey="p" href="../index.html"><img src="../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="qi_components.html"><img src="../../../../../../doc/src/images/next.png" alt="Next"></a>
</div>
</body>
</html>

Modified: trunk/libs/spirit/repository/doc/html/spirit_repository/qi_components.html
==============================================================================
--- trunk/libs/spirit/repository/doc/html/spirit_repository/qi_components.html (original)
+++ trunk/libs/spirit/repository/doc/html/spirit_repository/qi_components.html 2010-07-19 16:15:52 EDT (Mon, 19 Jul 2010)
@@ -2,8 +2,8 @@
<head>
<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Qi Components</title>
-<link rel="stylesheet" href="../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
+<link rel="stylesheet" href="../../../../../../doc/src/boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
<link rel="home" href="../index.html" title="Spirit Repository 0.1">
<link rel="up" href="../index.html" title="Spirit Repository 0.1">
<link rel="prev" href="preface.html" title="Preface">
@@ -13,16 +13,16 @@
<table cellpadding="2" width="100%"><tr>
<td valign="top"><img alt="Boost C++ Libraries" width="277" height="86" src="../../../../../../boost.png"></td>
<td align="center">Home</td>
-<td align="center">Libraries</td>
+<td align="center">Libraries</td>
<td align="center">People</td>
<td align="center">FAQ</td>
<td align="center">More</td>
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="preface.html"><img src="../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="qi_components/primitive.html"><img src="../../../../../../doc/html/images/next.png" alt="Next"></a>
+<a accesskey="p" href="preface.html"><img src="../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="qi_components/primitive.html"><img src="../../../../../../doc/src/images/next.png" alt="Next"></a>
</div>
-<div class="section" title="Qi Components">
+<div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
<a name="spirit_repository.qi_components"></a><a class="link" href="qi_components.html" title="Qi Components">Qi Components</a>
</h2></div></div></div>
@@ -55,7 +55,7 @@
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="preface.html"><img src="../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="qi_components/primitive.html"><img src="../../../../../../doc/html/images/next.png" alt="Next"></a>
+<a accesskey="p" href="preface.html"><img src="../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="qi_components/primitive.html"><img src="../../../../../../doc/src/images/next.png" alt="Next"></a>
</div>
</body>
</html>

Modified: trunk/libs/spirit/repository/doc/html/spirit_repository/qi_components/directives.html
==============================================================================
--- trunk/libs/spirit/repository/doc/html/spirit_repository/qi_components/directives.html (original)
+++ trunk/libs/spirit/repository/doc/html/spirit_repository/qi_components/directives.html 2010-07-19 16:15:52 EDT (Mon, 19 Jul 2010)
@@ -2,8 +2,8 @@
<head>
<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Qi Parser Directives</title>
-<link rel="stylesheet" href="../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
+<link rel="stylesheet" href="../../../../../../../doc/src/boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
<link rel="home" href="../../index.html" title="Spirit Repository 0.1">
<link rel="up" href="../qi_components.html" title="Qi Components">
<link rel="prev" href="primitive/flush_multi_pass.html" title="Qi flush_multi_pass parser">
@@ -13,16 +13,16 @@
<table cellpadding="2" width="100%"><tr>
<td valign="top"><img alt="Boost C++ Libraries" width="277" height="86" src="../../../../../../../boost.png"></td>
<td align="center">Home</td>
-<td align="center">Libraries</td>
+<td align="center">Libraries</td>
<td align="center">People</td>
<td align="center">FAQ</td>
<td align="center">More</td>
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="primitive/flush_multi_pass.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../qi_components.html"><img src="../../../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../../index.html"><img src="../../../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="directives/confix.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
+<a accesskey="p" href="primitive/flush_multi_pass.html"><img src="../../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../qi_components.html"><img src="../../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../../index.html"><img src="../../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="directives/confix.html"><img src="../../../../../../../doc/src/images/next.png" alt="Next"></a>
</div>
-<div class="section" title="Qi Parser Directives">
+<div class="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="spirit_repository.qi_components.directives"></a><a class="link" href="directives.html" title="Qi Parser Directives"> Qi Parser
Directives</a>
@@ -44,7 +44,7 @@
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="primitive/flush_multi_pass.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../qi_components.html"><img src="../../../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../../index.html"><img src="../../../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="directives/confix.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
+<a accesskey="p" href="primitive/flush_multi_pass.html"><img src="../../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../qi_components.html"><img src="../../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../../index.html"><img src="../../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="directives/confix.html"><img src="../../../../../../../doc/src/images/next.png" alt="Next"></a>
</div>
</body>
</html>

Modified: trunk/libs/spirit/repository/doc/html/spirit_repository/qi_components/directives/confix.html
==============================================================================
--- trunk/libs/spirit/repository/doc/html/spirit_repository/qi_components/directives/confix.html (original)
+++ trunk/libs/spirit/repository/doc/html/spirit_repository/qi_components/directives/confix.html 2010-07-19 16:15:52 EDT (Mon, 19 Jul 2010)
@@ -2,8 +2,8 @@
<head>
<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Qi Confix Parser Directive</title>
-<link rel="stylesheet" href="../../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
+<link rel="stylesheet" href="../../../../../../../../doc/src/boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
<link rel="home" href="../../../index.html" title="Spirit Repository 0.1">
<link rel="up" href="../directives.html" title="Qi Parser Directives">
<link rel="prev" href="../directives.html" title="Qi Parser Directives">
@@ -13,22 +13,22 @@
<table cellpadding="2" width="100%"><tr>
<td valign="top"><img alt="Boost C++ Libraries" width="277" height="86" src="../../../../../../../../boost.png"></td>
<td align="center">Home</td>
-<td align="center">Libraries</td>
+<td align="center">Libraries</td>
<td align="center">People</td>
<td align="center">FAQ</td>
<td align="center">More</td>
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="../directives.html"><img src="../../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../directives.html"><img src="../../../../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../../../index.html"><img src="../../../../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="distinct.html"><img src="../../../../../../../../doc/html/images/next.png" alt="Next"></a>
+<a accesskey="p" href="../directives.html"><img src="../../../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../directives.html"><img src="../../../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../../../index.html"><img src="../../../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="distinct.html"><img src="../../../../../../../../doc/src/images/next.png" alt="Next"></a>
</div>
-<div class="section" title="Qi Confix Parser Directive">
+<div class="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="spirit_repository.qi_components.directives.confix"></a><a class="link" href="confix.html" title="Qi Confix Parser Directive">
 Qi Confix Parser Directive</a>
</h4></div></div></div>
<a name="spirit_repository.qi_components.directives.confix.description"></a><h6>
-<a name="id623313"></a>
+<a name="id761680"></a>
 <a class="link" href="confix.html#spirit_repository.qi_components.directives.confix.description">Description</a>
 </h6>

@@ -78,7 +78,7 @@
<pre class="programlisting">c_comment[*(char_ - "*/")] // C style comment
cpp_comment[*(char_ - eol)] // C++ style comment
</pre>
-<div class="note" title="Note"><table border="0" summary="Note">
+<div class="note"><table border="0" summary="Note">
<tr>
<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../../../images/note.png"></td>
<th align="left">Note</th>
@@ -88,27 +88,27 @@
 suffix)</code>
 parser in Spirit.Classic was equivalent to the sequence
 <code class="computeroutput">prefix >>
- (subject
+ *(subject
 - suffix) >> suffix, the Spirit.Qi </code>confix`
 directive will not perform this refactoring any more. This simplifies
 the code and makes things more explicit.
 </td></tr>
</table></div>
<a name="spirit_repository.qi_components.directives.confix.header"></a><h6>
-<a name="id624081"></a>
+<a name="id762520"></a>
 <a class="link" href="confix.html#spirit_repository.qi_components.directives.confix.header">Header</a>
 </h6>
<pre class="programlisting">// forwards to <boost/spirit/repository/home/qi/directive/confix.hpp>
#include <boost/spirit/repository/include/qi_confix.hpp>
</pre>
<a name="spirit_repository.qi_components.directives.confix.synopsis"></a><h6>
-<a name="id624159"></a>
+<a name="id762608"></a>
 <a class="link" href="confix.html#spirit_repository.qi_components.directives.confix.synopsis">Synopsis</a>
 </h6>
<pre class="programlisting">confix(prefix, suffix)[subject]
</pre>
<a name="spirit_repository.qi_components.directives.confix.parameters"></a><h6>
-<a name="id624212"></a>
+<a name="id762664"></a>
 <a class="link" href="confix.html#spirit_repository.qi_components.directives.confix.parameters">Parameters</a>
 </h6>
<div class="informaltable"><table class="table">
@@ -118,52 +118,52 @@
</colgroup>
<thead><tr>
<th>
- 
- Parameter
- 
+ 
+ Parameter
+ 
 </th>
<th>
- 
- Description
- 
+ 
+ Description
+ 
 </th>
</tr></thead>
<tbody>
<tr>
<td>
- 
- <code class="computeroutput">prefix</code>
- 
+ 
+ <code class="computeroutput">prefix</code>
+ 
 </td>
<td>
- 
- The parser for the opening (the prefix).
- 
+ 
+ The parser for the opening (the prefix).
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">suffix</code>
- 
+ 
+ <code class="computeroutput">suffix</code>
+ 
 </td>
<td>
- 
- The parser for the ending (the suffix).
- 
+ 
+ The parser for the ending (the suffix).
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">subject</code>
- 
+ 
+ <code class="computeroutput">subject</code>
+ 
 </td>
<td>
- 
- The parser for the input sequence between the <code class="computeroutput">prefix</code>
- and <code class="computeroutput">suffix</code> parts.
- 
+ 
+ The parser for the input sequence between the <code class="computeroutput">prefix</code>
+ and <code class="computeroutput">suffix</code> parts.
+ 
 </td>
</tr>
</tbody>
@@ -172,7 +172,7 @@
 All three parameters can be arbitrarily complex parsers themselves.
 
<a name="spirit_repository.qi_components.directives.confix.attribute"></a><h6>
-<a name="id624354"></a>
+<a name="id762814"></a>
 <a class="link" href="confix.html#spirit_repository.qi_components.directives.confix.attribute">Attribute</a>
 </h6>

@@ -184,7 +184,7 @@
 
<pre class="programlisting">a: A, p: P, s: S: --> confix(p, s)[a]: A
</pre>
-<div class="note" title="Note"><table border="0" summary="Note">
+<div class="note"><table border="0" summary="Note">
<tr>
<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../../../images/note.png"></td>
<th align="left">Note</th>
@@ -198,7 +198,7 @@
 </td></tr>
</table></div>
<a name="spirit_repository.qi_components.directives.confix.example"></a><h6>
-<a name="id624591"></a>
+<a name="id763077"></a>
 <a class="link" href="confix.html#spirit_repository.qi_components.directives.confix.example">Example</a>
 </h6>

@@ -208,7 +208,7 @@
 see confix.cpp)
 
<a name="spirit_repository.qi_components.directives.confix.prerequisites"></a><h6>
-<a name="id624626"></a>
+<a name="id763116"></a>
 <a class="link" href="confix.html#spirit_repository.qi_components.directives.confix.prerequisites">Prerequisites</a>
 </h6>

@@ -217,25 +217,19 @@
 for the new <code class="computeroutput">confix</code> directive.
 

- 
-
-
+

<pre class="programlisting">#include <boost/spirit/include/qi.hpp>
#include <boost/spirit/repository/include/qi_confix.hpp>
</pre>

- 
-
 

 In order to make the examples below more readable we import a number of
 elements into the current namespace:
 

- 
-
-
+

<pre class="programlisting">using boost::spirit::eol;
using boost::spirit::lexeme;
@@ -247,11 +241,9 @@
using boost::spirit::repository::confix;
</pre>

- 
-
 
<a name="spirit_repository.qi_components.directives.confix.parsing_different_comment_styles"></a><h6>
-<a name="id625044"></a>
+<a name="id763572"></a>
 <a class="link" href="confix.html#spirit_repository.qi_components.directives.confix.parsing_different_comment_styles">Parsing
 Different Comment Styles</a>
 </h6>
@@ -260,9 +252,7 @@
 a C++ comment:
 

- 
-
-
+

<pre class="programlisting">template <typename Iterator>
bool parse_cpp_comment(Iterator first, Iterator last, std::string& attr)
@@ -277,8 +267,6 @@
}
</pre>

- 
-
 

 This function will obviously parse input such as "<code class="computeroutput">//
@@ -286,9 +274,7 @@
 comment proves to be straightforward:
 

- 
-
-
+

<pre class="programlisting">template <typename Iterator>
bool parse_c_comment(Iterator first, Iterator last, std::string& attr)
@@ -303,15 +289,13 @@
}
</pre>

- 
-
 

 which again will be able to parse e.g. "<code class="computeroutput">/*
 This is a comment */ </code>".
 
<a name="spirit_repository.qi_components.directives.confix.parsing_tagged_data"></a><h6>
-<a name="id626988"></a>
+<a name="id764198"></a>
 <a class="link" href="confix.html#spirit_repository.qi_components.directives.confix.parsing_tagged_data">Parsing
 Tagged Data</a>
 </h6>
@@ -320,9 +304,7 @@
 is not very hard, either:
 

- 
-
-
+

<pre class="programlisting">template <typename Iterator>
bool parse_tagged(Iterator first, Iterator last, std::string& attr)
@@ -338,8 +320,6 @@
}
</pre>

- 
-
 
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
@@ -352,7 +332,7 @@
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="../directives.html"><img src="../../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../directives.html"><img src="../../../../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../../../index.html"><img src="../../../../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="distinct.html"><img src="../../../../../../../../doc/html/images/next.png" alt="Next"></a>
+<a accesskey="p" href="../directives.html"><img src="../../../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../directives.html"><img src="../../../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../../../index.html"><img src="../../../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="distinct.html"><img src="../../../../../../../../doc/src/images/next.png" alt="Next"></a>
</div>
</body>
</html>

Modified: trunk/libs/spirit/repository/doc/html/spirit_repository/qi_components/directives/distinct.html
==============================================================================
--- trunk/libs/spirit/repository/doc/html/spirit_repository/qi_components/directives/distinct.html (original)
+++ trunk/libs/spirit/repository/doc/html/spirit_repository/qi_components/directives/distinct.html 2010-07-19 16:15:52 EDT (Mon, 19 Jul 2010)
@@ -2,8 +2,8 @@
<head>
<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Qi Distinct Parser Directive</title>
-<link rel="stylesheet" href="../../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
+<link rel="stylesheet" href="../../../../../../../../doc/src/boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
<link rel="home" href="../../../index.html" title="Spirit Repository 0.1">
<link rel="up" href="../directives.html" title="Qi Parser Directives">
<link rel="prev" href="confix.html" title="Qi Confix Parser Directive">
@@ -13,22 +13,22 @@
<table cellpadding="2" width="100%"><tr>
<td valign="top"><img alt="Boost C++ Libraries" width="277" height="86" src="../../../../../../../../boost.png"></td>
<td align="center">Home</td>
-<td align="center">Libraries</td>
+<td align="center">Libraries</td>
<td align="center">People</td>
<td align="center">FAQ</td>
<td align="center">More</td>
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="confix.html"><img src="../../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../directives.html"><img src="../../../../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../../../index.html"><img src="../../../../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="../nonterminal.html"><img src="../../../../../../../../doc/html/images/next.png" alt="Next"></a>
+<a accesskey="p" href="confix.html"><img src="../../../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../directives.html"><img src="../../../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../../../index.html"><img src="../../../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="../nonterminal.html"><img src="../../../../../../../../doc/src/images/next.png" alt="Next"></a>
</div>
-<div class="section" title="Qi Distinct Parser Directive">
+<div class="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="spirit_repository.qi_components.directives.distinct"></a><a class="link" href="distinct.html" title="Qi Distinct Parser Directive">
 Qi Distinct Parser Directive</a>
</h4></div></div></div>
<a name="spirit_repository.qi_components.directives.distinct.description"></a><h6>
-<a name="id627341"></a>
+<a name="id764582"></a>
 <a class="link" href="distinct.html#spirit_repository.qi_components.directives.distinct.description">Description</a>
 </h6>

@@ -73,9 +73,7 @@
 see distinct.cpp):
 

- 
-
-
+

<pre class="programlisting">namespace spirit = boost::spirit;
namespace ascii = boost::spirit::ascii;
@@ -128,8 +126,6 @@
keyword_tag_type const keyword = distinct_spec(char_spec(keyword_spec));
</pre>

- 
-
 

 These definitions define a new Qi parser recognizing keywords! This allows
@@ -144,20 +140,20 @@
 above.
 
<a name="spirit_repository.qi_components.directives.distinct.header"></a><h6>
-<a name="id628578"></a>
+<a name="id765952"></a>
 <a class="link" href="distinct.html#spirit_repository.qi_components.directives.distinct.header">Header</a>
 </h6>
<pre class="programlisting">// forwards to <boost/spirit/repository/home/qi/directive/distinct.hpp>
#include <boost/spirit/repository/include/qi_distinct.hpp>
</pre>
<a name="spirit_repository.qi_components.directives.distinct.synopsis"></a><h6>
-<a name="id628656"></a>
+<a name="id766039"></a>
 <a class="link" href="distinct.html#spirit_repository.qi_components.directives.distinct.synopsis">Synopsis</a>
 </h6>
<pre class="programlisting">distinct(tail)[subject]
</pre>
<a name="spirit_repository.qi_components.directives.distinct.parameters"></a><h6>
-<a name="id628700"></a>
+<a name="id766087"></a>
 <a class="link" href="distinct.html#spirit_repository.qi_components.directives.distinct.parameters">Parameters</a>
 </h6>
<div class="informaltable"><table class="table">
@@ -167,41 +163,41 @@
</colgroup>
<thead><tr>
<th>
- 
- Parameter
- 
+ 
+ Parameter
+ 
 </th>
<th>
- 
- Description
- 
+ 
+ Description
+ 
 </th>
</tr></thead>
<tbody>
<tr>
<td>
- 
- <code class="computeroutput">tail</code>
- 
+ 
+ <code class="computeroutput">tail</code>
+ 
 </td>
<td>
- 
- The parser construct specifying what whould not follow the subject
- in order to match the overall expression.
- 
+ 
+ The parser construct specifying what whould not follow the subject
+ in order to match the overall expression.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">subject</code>
- 
+ 
+ <code class="computeroutput">subject</code>
+ 
 </td>
<td>
- 
- The parser construct to use to match the current input. The distinct
- directive makes sure that no unexpected partial matches occur.
- 
+ 
+ The parser construct to use to match the current input. The distinct
+ directive makes sure that no unexpected partial matches occur.
+ 
 </td>
</tr>
</tbody>
@@ -210,7 +206,7 @@
 All two parameters can be arbitrary complex parsers themselves.
 
<a name="spirit_repository.qi_components.directives.distinct.attribute"></a><h6>
-<a name="id628804"></a>
+<a name="id766199"></a>
 <a class="link" href="distinct.html#spirit_repository.qi_components.directives.distinct.attribute">Attribute</a>
 </h6>

@@ -224,7 +220,7 @@
<pre class="programlisting">a: A, b: B --> distinct(b)[a]: A
</pre>
<a name="spirit_repository.qi_components.directives.distinct.example"></a><h6>
-<a name="id629198"></a>
+<a name="id766328"></a>
 <a class="link" href="distinct.html#spirit_repository.qi_components.directives.distinct.example">Example</a>
 </h6>

@@ -232,7 +228,7 @@
 parser. distinct.cpp)
 
<a name="spirit_repository.qi_components.directives.distinct.prerequisites"></a><h6>
-<a name="id629230"></a>
+<a name="id766365"></a>
 <a class="link" href="distinct.html#spirit_repository.qi_components.directives.distinct.prerequisites">Prerequisites</a>
 </h6>

@@ -241,35 +237,27 @@
 for the new <code class="computeroutput">distinct</code> generator.
 

- 
-
-
+

<pre class="programlisting">#include <boost/spirit/include/qi.hpp>
#include <boost/spirit/repository/include/qi_distinct.hpp>
</pre>

- 
-
 

 To make all the code below more readable we introduce the following namespaces.
 

- 
-
-
+

<pre class="programlisting">using namespace boost::spirit;
using namespace boost::spirit::ascii;
using boost::spirit::repository::distinct;
</pre>

- 
-
 
<a name="spirit_repository.qi_components.directives.distinct.using_the_distinct_directive_to_match_keywords"></a><h6>
-<a name="id629474"></a>
+<a name="id766632"></a>
 <a class="link" href="distinct.html#spirit_repository.qi_components.directives.distinct.using_the_distinct_directive_to_match_keywords">Using
 The Distinct Directive to Match keywords</a>
 </h6>
@@ -281,9 +269,7 @@
 followed by an optional <code class="computeroutput">"--"</code>):
 

- 
-
-
+

<pre class="programlisting">{
 std::string str("description ident");
@@ -295,11 +281,9 @@
}
</pre>

- 
-
- 
+ 

-
+

<pre class="programlisting">{
 std::string str("description--ident");
@@ -311,17 +295,13 @@
}
</pre>

- 
-
 

 The last example shows that the <code class="computeroutput">distinct[]</code> parser component correctly refuses to
 match "description-ident":
 

- 
-
-
+

<pre class="programlisting">{
 std::string str("description-ident");
@@ -333,8 +313,6 @@
}
</pre>

- 
-
 
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
@@ -347,7 +325,7 @@
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="confix.html"><img src="../../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../directives.html"><img src="../../../../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../../../index.html"><img src="../../../../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="../nonterminal.html"><img src="../../../../../../../../doc/html/images/next.png" alt="Next"></a>
+<a accesskey="p" href="confix.html"><img src="../../../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../directives.html"><img src="../../../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../../../index.html"><img src="../../../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="../nonterminal.html"><img src="../../../../../../../../doc/src/images/next.png" alt="Next"></a>
</div>
</body>
</html>

Modified: trunk/libs/spirit/repository/doc/html/spirit_repository/qi_components/nonterminal.html
==============================================================================
--- trunk/libs/spirit/repository/doc/html/spirit_repository/qi_components/nonterminal.html (original)
+++ trunk/libs/spirit/repository/doc/html/spirit_repository/qi_components/nonterminal.html 2010-07-19 16:15:52 EDT (Mon, 19 Jul 2010)
@@ -2,8 +2,8 @@
<head>
<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Qi Parser Non-terminals</title>
-<link rel="stylesheet" href="../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
+<link rel="stylesheet" href="../../../../../../../doc/src/boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
<link rel="home" href="../../index.html" title="Spirit Repository 0.1">
<link rel="up" href="../qi_components.html" title="Qi Components">
<link rel="prev" href="directives/distinct.html" title="Qi Distinct Parser Directive">
@@ -13,16 +13,16 @@
<table cellpadding="2" width="100%"><tr>
<td valign="top"><img alt="Boost C++ Libraries" width="277" height="86" src="../../../../../../../boost.png"></td>
<td align="center">Home</td>
-<td align="center">Libraries</td>
+<td align="center">Libraries</td>
<td align="center">People</td>
<td align="center">FAQ</td>
<td align="center">More</td>
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="directives/distinct.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../qi_components.html"><img src="../../../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../../index.html"><img src="../../../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="nonterminal/subrule.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
+<a accesskey="p" href="directives/distinct.html"><img src="../../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../qi_components.html"><img src="../../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../../index.html"><img src="../../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="nonterminal/subrule.html"><img src="../../../../../../../doc/src/images/next.png" alt="Next"></a>
</div>
-<div class="section" title="Qi Parser Non-terminals">
+<div class="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="spirit_repository.qi_components.nonterminal"></a><a class="link" href="nonterminal.html" title="Qi Parser Non-terminals"> Qi Parser
Non-terminals</a>
@@ -40,7 +40,7 @@
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="directives/distinct.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../qi_components.html"><img src="../../../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../../index.html"><img src="../../../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="nonterminal/subrule.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
+<a accesskey="p" href="directives/distinct.html"><img src="../../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../qi_components.html"><img src="../../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../../index.html"><img src="../../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="nonterminal/subrule.html"><img src="../../../../../../../doc/src/images/next.png" alt="Next"></a>
</div>
</body>
</html>

Modified: trunk/libs/spirit/repository/doc/html/spirit_repository/qi_components/nonterminal/subrule.html
==============================================================================
--- trunk/libs/spirit/repository/doc/html/spirit_repository/qi_components/nonterminal/subrule.html (original)
+++ trunk/libs/spirit/repository/doc/html/spirit_repository/qi_components/nonterminal/subrule.html 2010-07-19 16:15:52 EDT (Mon, 19 Jul 2010)
@@ -2,8 +2,8 @@
<head>
<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Qi subrules</title>
-<link rel="stylesheet" href="../../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
+<link rel="stylesheet" href="../../../../../../../../doc/src/boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
<link rel="home" href="../../../index.html" title="Spirit Repository 0.1">
<link rel="up" href="../nonterminal.html" title="Qi Parser Non-terminals">
<link rel="prev" href="../nonterminal.html" title="Qi Parser Non-terminals">
@@ -13,22 +13,22 @@
<table cellpadding="2" width="100%"><tr>
<td valign="top"><img alt="Boost C++ Libraries" width="277" height="86" src="../../../../../../../../boost.png"></td>
<td align="center">Home</td>
-<td align="center">Libraries</td>
+<td align="center">Libraries</td>
<td align="center">People</td>
<td align="center">FAQ</td>
<td align="center">More</td>
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="../nonterminal.html"><img src="../../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../nonterminal.html"><img src="../../../../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../../../index.html"><img src="../../../../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="../../karma_components.html"><img src="../../../../../../../../doc/html/images/next.png" alt="Next"></a>
+<a accesskey="p" href="../nonterminal.html"><img src="../../../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../nonterminal.html"><img src="../../../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../../../index.html"><img src="../../../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="../../karma_components.html"><img src="../../../../../../../../doc/src/images/next.png" alt="Next"></a>
</div>
-<div class="section" title="Qi subrules">
+<div class="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="spirit_repository.qi_components.nonterminal.subrule"></a><a class="link" href="subrule.html" title="Qi subrules">
 Qi subrules</a>
</h4></div></div></div>
<a name="spirit_repository.qi_components.nonterminal.subrule.description"></a><h6>
-<a name="id630408"></a>
+<a name="id767651"></a>
 <a class="link" href="subrule.html#spirit_repository.qi_components.nonterminal.subrule.description">Description</a>
 </h6>

@@ -50,20 +50,18 @@
 
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
- subrules can only be defined and used within the same parser expression.
- A subrule cannot be defined at one location, and then used in another
- location.
- </li>
+ subrules can only be defined and used within the same parser expression.
+ A subrule cannot be defined at one location, and then used in another
+ location.
+ </li>
<li class="listitem">
- subrules put a massive strain on the C++ compiler. They increase compile
- times and memory usage during compilation, and also increase the risk
- of hitting compiler limits and/or bugs.
- </li>
+ subrules put a massive strain on the C++ compiler. They increase compile
+ times and memory usage during compilation, and also increase the risk
+ of hitting compiler limits and/or bugs.
+ </li>
</ul></div>

- 
-
-
+

<pre class="programlisting">entry = (
 expression =
@@ -86,8 +84,6 @@
);
</pre>

- 
-
 

 The example above can be found here: ../../example/qi/calc1_sr.cpp
@@ -101,21 +97,21 @@
 most performance-critical parts), whereas the rest can use rules and grammars.
 
<a name="spirit_repository.qi_components.nonterminal.subrule.header"></a><h6>
-<a name="id630796"></a>
+<a name="id768089"></a>
 <a class="link" href="subrule.html#spirit_repository.qi_components.nonterminal.subrule.header">Header</a>
 </h6>
<pre class="programlisting">// forwards to <boost/spirit/repository/home/qi/nonterminal/subrule.hpp>
#include <boost/spirit/repository/include/qi_subrule.hpp>
</pre>
<a name="spirit_repository.qi_components.nonterminal.subrule.synopsis__declaration_"></a><h6>
-<a name="id630872"></a>
+<a name="id768178"></a>
 <a class="link" href="subrule.html#spirit_repository.qi_components.nonterminal.subrule.synopsis__declaration_">Synopsis
 (declaration)</a>
 </h6>
<pre class="programlisting">subrule<ID, A1, A2> sr(name);
</pre>
<a name="spirit_repository.qi_components.nonterminal.subrule.parameters__declaration_"></a><h6>
-<a name="id630936"></a>
+<a name="id768255"></a>
 <a class="link" href="subrule.html#spirit_repository.qi_components.nonterminal.subrule.parameters__declaration_">Parameters
 (declaration)</a>
 </h6>
@@ -126,66 +122,66 @@
</colgroup>
<thead><tr>
<th>
- 
- Parameter
- 
+ 
+ Parameter
+ 
 </th>
<th>
- 
- Description
- 
+ 
+ Description
+ 
 </th>
</tr></thead>
<tbody>
<tr>
<td>
- 
- <code class="computeroutput">ID</code>
- 
+ 
+ <code class="computeroutput">ID</code>
+ 
 </td>
<td>
- 
- Required numeric argument. Gives the subrule a unique 'identification
- tag'.
- 
+ 
+ Required numeric argument. Gives the subrule a unique 'identification
+ tag'.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">A1</code>, <code class="computeroutput">A2</code>
- 
+ 
+ <code class="computeroutput">A1</code>, <code class="computeroutput">A2</code>
+ 
 </td>
<td>
- 
- Optional types, can be specified in any order. Can be one of 1.
- signature, 2. locals (see rules reference for more information
- on those parameters).
- 
- 
- Note that the skipper type need not be specified in the parameters,
- unlike with grammars and rules. Subrules will automatically use
- the skipper type which is in effect when they are invoked.
- 
+ 
+ Optional types, can be specified in any order. Can be one of
+ 1. signature, 2. locals (see rules reference for more information
+ on those parameters).
+ 
+ 
+ Note that the skipper type need not be specified in the parameters,
+ unlike with grammars and rules. Subrules will automatically use
+ the skipper type which is in effect when they are invoked.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">name</code>
- 
+ 
+ <code class="computeroutput">name</code>
+ 
 </td>
<td>
- 
- Optional string. Gives the subrule a name, useful for debugging
- and error handling.
- 
+ 
+ Optional string. Gives the subrule a name, useful for debugging
+ and error handling.
+ 
 </td>
</tr>
</tbody>
</table></div>
<a name="spirit_repository.qi_components.nonterminal.subrule.synopsis__usage_"></a><h6>
-<a name="id631066"></a>
+<a name="id768407"></a>
 <a class="link" href="subrule.html#spirit_repository.qi_components.nonterminal.subrule.synopsis__usage_">Synopsis
 (usage)</a>
 </h6>
@@ -214,7 +210,7 @@
)(a1, a2, ...) // Arguments to group, i.e. to start subrule srA
</pre>
<a name="spirit_repository.qi_components.nonterminal.subrule.parameters__usage_"></a><h6>
-<a name="id631301"></a>
+<a name="id768670"></a>
 <a class="link" href="subrule.html#spirit_repository.qi_components.nonterminal.subrule.parameters__usage_">Parameters
 (usage)</a>
 </h6>
@@ -225,120 +221,120 @@
</colgroup>
<thead><tr>
<th>
- 
- Parameter
- 
+ 
+ Parameter
+ 
 </th>
<th>
- 
- Description
- 
+ 
+ Description
+ 
 </th>
</tr></thead>
<tbody>
<tr>
<td>
- 
- <code class="computeroutput">sr1</code>, <code class="computeroutput">sr2</code>
- 
+ 
+ <code class="computeroutput">sr1</code>, <code class="computeroutput">sr2</code>
+ 
 </td>
<td>
- 
- Subrules with different IDs.
- 
+ 
+ Subrules with different IDs.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">expr1</code>, <code class="computeroutput">expr2</code>
- 
+ 
+ <code class="computeroutput">expr1</code>, <code class="computeroutput">expr2</code>
+ 
 </td>
<td>
- 
- Parser expressions. Can include <code class="computeroutput">sr1</code>
- and <code class="computeroutput">sr2</code>, as well
- as any other valid parser expressions.
- 
+ 
+ Parser expressions. Can include <code class="computeroutput">sr1</code>
+ and <code class="computeroutput">sr2</code>, as well
+ as any other valid parser expressions.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">srA</code>
- 
+ 
+ <code class="computeroutput">srA</code>
+ 
 </td>
<td>
- 
- Subrule with a synthesized attribute and inherited attributes.
- 
+ 
+ Subrule with a synthesized attribute and inherited attributes.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">srB</code>
- 
+ 
+ <code class="computeroutput">srB</code>
+ 
 </td>
<td>
- 
- Subrule with a synthesized attribute.
- 
+ 
+ Subrule with a synthesized attribute.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">srC</code>
- 
+ 
+ <code class="computeroutput">srC</code>
+ 
 </td>
<td>
- 
- Subrule with inherited attributes.
- 
+ 
+ Subrule with inherited attributes.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">exprA</code>, <code class="computeroutput">exprB</code>, <code class="computeroutput">exprC</code>
- 
+ 
+ <code class="computeroutput">exprA</code>, <code class="computeroutput">exprB</code>, <code class="computeroutput">exprC</code>
+ 
 </td>
<td>
- 
- Parser expressions.
- 
+ 
+ Parser expressions.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">a1</code>, <code class="computeroutput">a2</code>
- 
+ 
+ <code class="computeroutput">a1</code>, <code class="computeroutput">a2</code>
+ 
 </td>
<td>
- 
- Arguments passed to the subrule group. They are passed as inherited
- attributes to the group's start subrule, <code class="computeroutput">srA</code>.
- 
+ 
+ Arguments passed to the subrule group. They are passed as inherited
+ attributes to the group's start subrule, <code class="computeroutput">srA</code>.
+ 
 </td>
</tr>
<tr>
<td>
- 
- <code class="computeroutput">c1</code>, <code class="computeroutput">c2</code>
- 
+ 
+ <code class="computeroutput">c1</code>, <code class="computeroutput">c2</code>
+ 
 </td>
<td>
- 
- Arguments passed as inherited attributes to subrule <code class="computeroutput">srC</code>.
- 
+ 
+ Arguments passed as inherited attributes to subrule <code class="computeroutput">srC</code>.
+ 
 </td>
</tr>
</tbody>
</table></div>
<a name="spirit_repository.qi_components.nonterminal.subrule.groups"></a><h6>
-<a name="id632980"></a>
+<a name="id769280"></a>
 <a class="link" href="subrule.html#spirit_repository.qi_components.nonterminal.subrule.groups">Groups</a>
 </h6>

@@ -383,7 +379,7 @@
;
</pre>
<a name="spirit_repository.qi_components.nonterminal.subrule.attributes"></a><h6>
-<a name="id633381"></a>
+<a name="id769725"></a>
 <a class="link" href="subrule.html#spirit_repository.qi_components.nonterminal.subrule.attributes">Attributes</a>
 </h6>

@@ -392,26 +388,27 @@
 
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
- the type of its synthesized attribute is the one specified in the subrule's
- signature, if any. Otherwise it is <code class="computeroutput">unused_type</code>.
- </li>
+ the type of its synthesized attribute is the one specified in the subrule's
+ signature, if any. Otherwise it is <code class="computeroutput">unused_type</code>.
+ </li>
<li class="listitem">
- the types of its inherited attributes are the ones specified in the subrule's
- signature, if any. Otherwise the subrule has no inherited attributes.
- </li>
+ the types of its inherited attributes are the ones specified in the
+ subrule's signature, if any. Otherwise the subrule has no inherited
+ attributes.
+ </li>
<li class="listitem">
- an auto-subrule can be defined by assigning it with the <code class="computeroutput">%=</code> syntax. In this case, the RHS parser's
- attribute is automatically propagated to the subrule's synthesized attribute.
- </li>
+ an auto-subrule can be defined by assigning it with the <code class="computeroutput">%=</code> syntax. In this case, the RHS parser's
+ attribute is automatically propagated to the subrule's synthesized
+ attribute.
+ </li>
<li class="listitem">
- the Phoenix placeholders <code class="computeroutput">_val</code>,
- <code class="computeroutput">_r1</code>, <code class="computeroutput">_r2</code>,
- ... are available to refer to the subrule's synthesized and inherited
- attributes, if present.
- </li>
+ the Phoenix placeholders <code class="computeroutput">_val</code>,
+ <code class="computeroutput">_r1</code>, <code class="computeroutput">_r2</code>, ... are available to refer to
+ the subrule's synthesized and inherited attributes, if present.
+ </li>
</ul></div>
<a name="spirit_repository.qi_components.nonterminal.subrule.locals"></a><h6>
-<a name="id633457"></a>
+<a name="id769830"></a>
 <a class="link" href="subrule.html#spirit_repository.qi_components.nonterminal.subrule.locals">Locals</a>
 </h6>

@@ -421,16 +418,14 @@
 refer to the subrule's locals, if present.
 
<a name="spirit_repository.qi_components.nonterminal.subrule.example"></a><h6>
-<a name="id633493"></a>
+<a name="id769872"></a>
 <a class="link" href="subrule.html#spirit_repository.qi_components.nonterminal.subrule.example">Example</a>
 </h6>

 Some includes:
 

- 
-
-
+

<pre class="programlisting">#include <boost/spirit/include/qi.hpp>
#include <boost/spirit/repository/include/qi_subrule.hpp>
@@ -438,32 +433,24 @@
#include <boost/spirit/include/phoenix_operator.hpp>
</pre>

- 
-
 

 Some using declarations:
 

- 
-
-
+

<pre class="programlisting">namespace qi = boost::spirit::qi;
namespace repo = boost::spirit::repository;
namespace ascii = boost::spirit::ascii;
</pre>

- 
-
 

 A grammar containing only one rule, defined with a group of 5 subrules:
 

- 
-
-
+

<pre class="programlisting">template <typename Iterator>
struct mini_xml_grammar
@@ -511,8 +498,6 @@
};
</pre>

- 
-
 

 The definitions of the <code class="computeroutput">mini_xml</code>
@@ -521,7 +506,7 @@
 <a href="../../../../../example/qi/mini_xml2_sr.cpp" target="_top">../../example/qi/mini_xml2_sr.cpp</a>
 
<a name="spirit_repository.qi_components.nonterminal.subrule.performance"></a><h6>
-<a name="id634763"></a>
+<a name="id771325"></a>
 <a class="link" href="subrule.html#spirit_repository.qi_components.nonterminal.subrule.performance">Performance</a>
 </h6>

@@ -529,7 +514,7 @@
 examples to subrules, with various compilers.
 
<div class="table">
-<a name="id634779"></a>Table 2. Subrules performance
+<a name="id771345"></a>Table 2. Subrules performance
<div class="table-contents"><table class="table" summary="Subrules performance">
<colgroup>
<col>
@@ -540,220 +525,220 @@
</colgroup>
<thead><tr>
<th>
- 
- Example
- 
- </th>
+ 
+ Example
+ 
+ </th>
<th>
- 
- Compiler
- 
- </th>
+ 
+ Compiler
+ 
+ </th>
<th>
- 
- Speed (run-time)
- 
- </th>
+ 
+ Speed (run-time)
+ 
+ </th>
<th>
- 
- Time (compile-time)
- 
- </th>
+ 
+ Time (compile-time)
+ 
+ </th>
<th>
- 
- Memory (compile-time)
- 
- </th>
+ 
+ Memory (compile-time)
+ 
+ </th>
</tr></thead>
<tbody>
<tr>
<td>
- 
- calc1_sr
- 
- </td>
-<td>
- 
- gcc 4.4.1
- 
- </td>
-<td>
- 
- +6%
- 
- </td>
-<td>
- 
- n/a
- 
- </td>
-<td>
- 
- n/a
- 
- </td>
-</tr>
-<tr>
-<td>
- 
- calc1_sr
- 
- </td>
-<td>
- 
- Visual C++ 2008 (VC9)
- 
- </td>
-<td>
- 
- +5%
- 
- </td>
-<td>
- 
- n/a
- 
- </td>
-<td>
- 
- n/a
- 
- </td>
-</tr>
-<tr>
-<td>
- 
- mini_xml2_sr
- 
- </td>
-<td>
- 
- gcc 3.4.6
- 
- </td>
-<td>
- 
- -1%
- 
- </td>
-<td>
- 
- +54%
- 
- </td>
-<td>
- 
- +32%
- 
- </td>
-</tr>
-<tr>
-<td>
- 
- mini_xml2_sr
- 
- </td>
-<td>
- 
- gcc 4.1.2
- 
- </td>
-<td>
- 
- +5%
- 
- </td>
-<td>
- 
- +58%
- 
- </td>
-<td>
- 
- +25%
- 
- </td>
-</tr>
-<tr>
-<td>
- 
- mini_xml2_sr
- 
- </td>
-<td>
- 
- gcc 4.4.1
- 
- </td>
-<td>
- 
- +8%
- 
- </td>
-<td>
- 
- +20%
- 
- </td>
-<td>
- 
- +14%
- 
- </td>
-</tr>
-<tr>
-<td>
- 
- mini_xml2_sr
- 
- </td>
-<td>
- 
- Visual C++ 2005 (VC8) SP1
- 
- </td>
-<td>
- 
- +1%
- 
- </td>
-<td>
- 
- +33%
- 
- </td>
-<td>
- 
- +27%
- 
- </td>
-</tr>
-<tr>
-<td>
- 
- mini_xml2_sr
- 
- </td>
-<td>
- 
- Visual C++ 2008 (VC9)
- 
- </td>
-<td>
- 
- +9%
- 
- </td>
-<td>
- 
- +52%
- 
- </td>
-<td>
- 
- +40%
- 
- </td>
+ 
+ calc1_sr
+ 
+ </td>
+<td>
+ 
+ gcc 4.4.1
+ 
+ </td>
+<td>
+ 
+ +6%
+ 
+ </td>
+<td>
+ 
+ n/a
+ 
+ </td>
+<td>
+ 
+ n/a
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ calc1_sr
+ 
+ </td>
+<td>
+ 
+ Visual C++ 2008 (VC9)
+ 
+ </td>
+<td>
+ 
+ +5%
+ 
+ </td>
+<td>
+ 
+ n/a
+ 
+ </td>
+<td>
+ 
+ n/a
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ mini_xml2_sr
+ 
+ </td>
+<td>
+ 
+ gcc 3.4.6
+ 
+ </td>
+<td>
+ 
+ -1%
+ 
+ </td>
+<td>
+ 
+ +54%
+ 
+ </td>
+<td>
+ 
+ +32%
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ mini_xml2_sr
+ 
+ </td>
+<td>
+ 
+ gcc 4.1.2
+ 
+ </td>
+<td>
+ 
+ +5%
+ 
+ </td>
+<td>
+ 
+ +58%
+ 
+ </td>
+<td>
+ 
+ +25%
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ mini_xml2_sr
+ 
+ </td>
+<td>
+ 
+ gcc 4.4.1
+ 
+ </td>
+<td>
+ 
+ +8%
+ 
+ </td>
+<td>
+ 
+ +20%
+ 
+ </td>
+<td>
+ 
+ +14%
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ mini_xml2_sr
+ 
+ </td>
+<td>
+ 
+ Visual C++ 2005 (VC8) SP1
+ 
+ </td>
+<td>
+ 
+ +1%
+ 
+ </td>
+<td>
+ 
+ +33%
+ 
+ </td>
+<td>
+ 
+ +27%
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ mini_xml2_sr
+ 
+ </td>
+<td>
+ 
+ Visual C++ 2008 (VC9)
+ 
+ </td>
+<td>
+ 
+ +9%
+ 
+ </td>
+<td>
+ 
+ +52%
+ 
+ </td>
+<td>
+ 
+ +40%
+ 
+ </td>
</tr>
</tbody>
</table></div>
@@ -763,20 +748,20 @@
 
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
-Speed (run-time): speed-up of the parser
- resulting from the use of subrules (higher is better).
- </li>
+ Speed (run-time): speed-up of the
+ parser resulting from the use of subrules (higher is better).
+ </li>
<li class="listitem">
-Time (compile-time): increase in compile
- time (lower is better).
- </li>
+ Time (compile-time): increase in compile
+ time (lower is better).
+ </li>
<li class="listitem">
-Memory (compile-time): increase in compiler
- memory usage (lower is better).
- </li>
+ Memory (compile-time): increase in
+ compiler memory usage (lower is better).
+ </li>
</ul></div>
<a name="spirit_repository.qi_components.nonterminal.subrule.notes"></a><h6>
-<a name="id635118"></a>
+<a name="id771740"></a>
 <a class="link" href="subrule.html#spirit_repository.qi_components.nonterminal.subrule.notes">Notes</a>
 </h6>

@@ -800,7 +785,7 @@
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="../nonterminal.html"><img src="../../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../nonterminal.html"><img src="../../../../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../../../index.html"><img src="../../../../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="../../karma_components.html"><img src="../../../../../../../../doc/html/images/next.png" alt="Next"></a>
+<a accesskey="p" href="../nonterminal.html"><img src="../../../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../nonterminal.html"><img src="../../../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../../../index.html"><img src="../../../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="../../karma_components.html"><img src="../../../../../../../../doc/src/images/next.png" alt="Next"></a>
</div>
</body>
</html>

Modified: trunk/libs/spirit/repository/doc/html/spirit_repository/qi_components/primitive.html
==============================================================================
--- trunk/libs/spirit/repository/doc/html/spirit_repository/qi_components/primitive.html (original)
+++ trunk/libs/spirit/repository/doc/html/spirit_repository/qi_components/primitive.html 2010-07-19 16:15:52 EDT (Mon, 19 Jul 2010)
@@ -2,8 +2,8 @@
<head>
<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Qi Parser Primitives</title>
-<link rel="stylesheet" href="../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
+<link rel="stylesheet" href="../../../../../../../doc/src/boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
<link rel="home" href="../../index.html" title="Spirit Repository 0.1">
<link rel="up" href="../qi_components.html" title="Qi Components">
<link rel="prev" href="../qi_components.html" title="Qi Components">
@@ -13,16 +13,16 @@
<table cellpadding="2" width="100%"><tr>
<td valign="top"><img alt="Boost C++ Libraries" width="277" height="86" src="../../../../../../../boost.png"></td>
<td align="center">Home</td>
-<td align="center">Libraries</td>
+<td align="center">Libraries</td>
<td align="center">People</td>
<td align="center">FAQ</td>
<td align="center">More</td>
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="../qi_components.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../qi_components.html"><img src="../../../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../../index.html"><img src="../../../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="primitive/flush_multi_pass.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
+<a accesskey="p" href="../qi_components.html"><img src="../../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../qi_components.html"><img src="../../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../../index.html"><img src="../../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="primitive/flush_multi_pass.html"><img src="../../../../../../../doc/src/images/next.png" alt="Next"></a>
</div>
-<div class="section" title="Qi Parser Primitives">
+<div class="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="spirit_repository.qi_components.primitive"></a><a class="link" href="primitive.html" title="Qi Parser Primitives"> Qi Parser
Primitives</a>
@@ -40,7 +40,7 @@
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="../qi_components.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../qi_components.html"><img src="../../../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../../index.html"><img src="../../../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="primitive/flush_multi_pass.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
+<a accesskey="p" href="../qi_components.html"><img src="../../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../qi_components.html"><img src="../../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../../index.html"><img src="../../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="primitive/flush_multi_pass.html"><img src="../../../../../../../doc/src/images/next.png" alt="Next"></a>
</div>
</body>
</html>

Modified: trunk/libs/spirit/repository/doc/html/spirit_repository/qi_components/primitive/flush_multi_pass.html
==============================================================================
--- trunk/libs/spirit/repository/doc/html/spirit_repository/qi_components/primitive/flush_multi_pass.html (original)
+++ trunk/libs/spirit/repository/doc/html/spirit_repository/qi_components/primitive/flush_multi_pass.html 2010-07-19 16:15:52 EDT (Mon, 19 Jul 2010)
@@ -2,8 +2,8 @@
<head>
<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Qi flush_multi_pass parser</title>
-<link rel="stylesheet" href="../../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
+<link rel="stylesheet" href="../../../../../../../../doc/src/boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
<link rel="home" href="../../../index.html" title="Spirit Repository 0.1">
<link rel="up" href="../primitive.html" title="Qi Parser Primitives">
<link rel="prev" href="../primitive.html" title="Qi Parser Primitives">
@@ -13,22 +13,22 @@
<table cellpadding="2" width="100%"><tr>
<td valign="top"><img alt="Boost C++ Libraries" width="277" height="86" src="../../../../../../../../boost.png"></td>
<td align="center">Home</td>
-<td align="center">Libraries</td>
+<td align="center">Libraries</td>
<td align="center">People</td>
<td align="center">FAQ</td>
<td align="center">More</td>
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="../primitive.html"><img src="../../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../primitive.html"><img src="../../../../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../../../index.html"><img src="../../../../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="../directives.html"><img src="../../../../../../../../doc/html/images/next.png" alt="Next"></a>
+<a accesskey="p" href="../primitive.html"><img src="../../../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../primitive.html"><img src="../../../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../../../index.html"><img src="../../../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="../directives.html"><img src="../../../../../../../../doc/src/images/next.png" alt="Next"></a>
</div>
-<div class="section" title="Qi flush_multi_pass parser">
+<div class="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="spirit_repository.qi_components.primitive.flush_multi_pass"></a><a class="link" href="flush_multi_pass.html" title="Qi flush_multi_pass parser">
 Qi flush_multi_pass parser</a>
</h4></div></div></div>
<a name="spirit_repository.qi_components.primitive.flush_multi_pass.description"></a><h6>
-<a name="id619892"></a>
+<a name="id760277"></a>
 <a class="link" href="flush_multi_pass.html#spirit_repository.qi_components.primitive.flush_multi_pass.description">Description</a>
 </h6>

@@ -53,20 +53,20 @@
 <code class="computeroutput">eps</code>).
 
<a name="spirit_repository.qi_components.primitive.flush_multi_pass.header"></a><h6>
-<a name="id620000"></a>
+<a name="id760413"></a>
 <a class="link" href="flush_multi_pass.html#spirit_repository.qi_components.primitive.flush_multi_pass.header">Header</a>
 </h6>
<pre class="programlisting">// forwards to <boost/spirit/repository/home/qi/primitive/flush_multi_pass.hpp>
#include <boost/spirit/repository/include/qi_flush_multi_pass.hpp>
</pre>
<a name="spirit_repository.qi_components.primitive.flush_multi_pass.synopsis"></a><h6>
-<a name="id620073"></a>
+<a name="id760502"></a>
 <a class="link" href="flush_multi_pass.html#spirit_repository.qi_components.primitive.flush_multi_pass.synopsis">Synopsis</a>
 </h6>
<pre class="programlisting">flush_multi_pass
</pre>
<a name="spirit_repository.qi_components.primitive.flush_multi_pass.parameters"></a><h6>
-<a name="id620094"></a>
+<a name="id760531"></a>
 <a class="link" href="flush_multi_pass.html#spirit_repository.qi_components.primitive.flush_multi_pass.parameters">Parameters</a>
 </h6>

@@ -74,7 +74,7 @@
 not require any parameters.
 
<a name="spirit_repository.qi_components.primitive.flush_multi_pass.attribute"></a><h6>
-<a name="id620118"></a>
+<a name="id760563"></a>
 <a class="link" href="flush_multi_pass.html#spirit_repository.qi_components.primitive.flush_multi_pass.attribute">Attribute</a>
 </h6>

@@ -84,7 +84,7 @@
<pre class="programlisting">flush_multi_pass --> unused
</pre>
<a name="spirit_repository.qi_components.primitive.flush_multi_pass.example"></a><h6>
-<a name="id620168"></a>
+<a name="id760623"></a>
 <a class="link" href="flush_multi_pass.html#spirit_repository.qi_components.primitive.flush_multi_pass.example">Example</a>
 </h6>

@@ -96,7 +96,7 @@
 a function prototype (for the full example code see here: flush_multi_pass.cpp)
 
<a name="spirit_repository.qi_components.primitive.flush_multi_pass.prerequisites"></a><h6>
-<a name="id620200"></a>
+<a name="id760666"></a>
 <a class="link" href="flush_multi_pass.html#spirit_repository.qi_components.primitive.flush_multi_pass.prerequisites">Prerequisites</a>
 </h6>

@@ -106,34 +106,26 @@
 parser.
 

- 
-
-
+

<pre class="programlisting">#include <boost/spirit/include/qi.hpp>
#include <boost/spirit/repository/include/qi_flush_multi_pass.hpp>
</pre>

- 
-
 

 To make all the code below more readable we introduce the following namespaces.
 

- 
-
-
+

<pre class="programlisting">namespace spirit = boost::spirit;
using boost::spirit::repository::flush_multi_pass;
</pre>

- 
-
 
<a name="spirit_repository.qi_components.primitive.flush_multi_pass.clearing_the_internal_buffer"></a><h6>
-<a name="id620416"></a>
+<a name="id760902"></a>
 <a class="link" href="flush_multi_pass.html#spirit_repository.qi_components.primitive.flush_multi_pass.clearing_the_internal_buffer">Clearing
 the internal buffer</a>
 </h6>
@@ -147,9 +139,7 @@
 purpose.
 

- 
-
-
+

<pre class="programlisting">template <typename Iterator, typename Skipper>
struct preprocessor : spirit::qi::grammar<Iterator, Skipper>
@@ -188,10 +178,8 @@
};
</pre>

- 
-
 
-<div class="note" title="Note"><table border="0" summary="Note">
+<div class="note"><table border="0" summary="Note">
<tr>
<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../../../images/note.png"></td>
<th align="left">Note</th>
@@ -213,7 +201,7 @@
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="../primitive.html"><img src="../../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../primitive.html"><img src="../../../../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../../../index.html"><img src="../../../../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="../directives.html"><img src="../../../../../../../../doc/html/images/next.png" alt="Next"></a>
+<a accesskey="p" href="../primitive.html"><img src="../../../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../primitive.html"><img src="../../../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../../../index.html"><img src="../../../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="../directives.html"><img src="../../../../../../../../doc/src/images/next.png" alt="Next"></a>
</div>
</body>
</html>

Date view	Thread view	Subject view	Author view

Boost-Commit list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk