Boost logo

Boost-Commit :

Subject: [Boost-commit] svn:boost r54905 - in trunk/libs/spirit/doc: . html html/spirit html/spirit/abstracts html/spirit/karma html/spirit/karma/quick_reference html/spirit/karma/reference html/spirit/karma/reference/generator_concepts html/spirit/karma/tutorials html/spirit/lex html/spirit/lex/abstracts html/spirit/lex/abstracts/lexer_primitives html/spirit/lex/reference html/spirit/lex/reference/concepts html/spirit/lex/tutorials html/spirit/notes html/spirit/qi html/spirit/qi/quick_reference html/spirit/qi/reference html/spirit/qi/reference/parser_concepts html/spirit/qi/tutorials html/spirit/structure html/spirit/support lex qi support
From: hartmut.kaiser_at_[hidden]
Date: 2009-07-11 23:35:45


Author: hkaiser
Date: 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
New Revision: 54905
URL: http://svn.boost.org/trac/boost/changeset/54905

Log:
Spirit: doc update, mainly related to multi_pass
Added:
   trunk/libs/spirit/doc/html/spirit/support/
   trunk/libs/spirit/doc/html/spirit/support.html (contents, props changed)
   trunk/libs/spirit/doc/html/spirit/support/multi_pass.html (contents, props changed)
   trunk/libs/spirit/doc/support/
   trunk/libs/spirit/doc/support.qbk (contents, props changed)
   trunk/libs/spirit/doc/support/multi_pass.qbk (contents, props changed)
Text files modified:
   trunk/libs/spirit/doc/html/index.html | 22
   trunk/libs/spirit/doc/html/spirit/abstracts.html | 15
   trunk/libs/spirit/doc/html/spirit/abstracts/parsing_expression_grammar.html | 97 +-
   trunk/libs/spirit/doc/html/spirit/abstracts/syntax_diagram.html | 68
   trunk/libs/spirit/doc/html/spirit/acknowledgments.html | 117 +-
   trunk/libs/spirit/doc/html/spirit/faq.html | 45
   trunk/libs/spirit/doc/html/spirit/introduction.html | 295 +++--
   trunk/libs/spirit/doc/html/spirit/karma.html | 21
   trunk/libs/spirit/doc/html/spirit/karma/quick_reference.html | 21
   trunk/libs/spirit/doc/html/spirit/karma/quick_reference/common_notation.html | 88 -
   trunk/libs/spirit/doc/html/spirit/karma/quick_reference/compound_attribute_rules.html | 169 ++-
   trunk/libs/spirit/doc/html/spirit/karma/quick_reference/lazy_arguments.html | 24
   trunk/libs/spirit/doc/html/spirit/karma/quick_reference/non_terminals.html | 312 ++++--
   trunk/libs/spirit/doc/html/spirit/karma/quick_reference/phoenix.html | 40
   trunk/libs/spirit/doc/html/spirit/karma/quick_reference/predefined_primitive_generators.html | 1705 ++++++++++++++++++++++++---------------
   trunk/libs/spirit/doc/html/spirit/karma/quick_reference/semantic_actions.html | 25
   trunk/libs/spirit/doc/html/spirit/karma/reference.html | 20
   trunk/libs/spirit/doc/html/spirit/karma/reference/generator_concepts.html | 19
   trunk/libs/spirit/doc/html/spirit/karma/reference/generator_concepts/binarygenerator.html | 194 ++-
   trunk/libs/spirit/doc/html/spirit/karma/reference/generator_concepts/generator.html | 215 ++--
   trunk/libs/spirit/doc/html/spirit/karma/reference/generator_concepts/narygenerator.html | 152 +-
   trunk/libs/spirit/doc/html/spirit/karma/reference/generator_concepts/primitivegenerator.html | 78
   trunk/libs/spirit/doc/html/spirit/karma/reference/generator_concepts/unarygenerator.html | 146 +-
   trunk/libs/spirit/doc/html/spirit/karma/tutorials.html | 17
   trunk/libs/spirit/doc/html/spirit/karma/tutorials/complex___a_first_more_complex_generator.html | 35
   trunk/libs/spirit/doc/html/spirit/karma/tutorials/quick_start.html | 29
   trunk/libs/spirit/doc/html/spirit/karma/tutorials/semantic_actions.html | 72
   trunk/libs/spirit/doc/html/spirit/karma/tutorials/warming_up.html | 135 +-
   trunk/libs/spirit/doc/html/spirit/lex.html | 19
   trunk/libs/spirit/doc/html/spirit/lex/abstracts.html | 20
   trunk/libs/spirit/doc/html/spirit/lex/abstracts/lexer_attributes.html | 20
   trunk/libs/spirit/doc/html/spirit/lex/abstracts/lexer_parsing.html | 22
   trunk/libs/spirit/doc/html/spirit/lex/abstracts/lexer_primitives.html | 20
   trunk/libs/spirit/doc/html/spirit/lex/abstracts/lexer_primitives/lexer_primitives.html | 20
   trunk/libs/spirit/doc/html/spirit/lex/abstracts/lexer_primitives/lexer_token_definition.html | 21
   trunk/libs/spirit/doc/html/spirit/lex/abstracts/lexer_primitives/lexer_token_values.html | 142 +-
   trunk/libs/spirit/doc/html/spirit/lex/abstracts/lexer_semantic_actions.html | 448 ++++++----
   trunk/libs/spirit/doc/html/spirit/lex/abstracts/lexer_states.html | 45
   trunk/libs/spirit/doc/html/spirit/lex/abstracts/lexer_static_model.html | 59
   trunk/libs/spirit/doc/html/spirit/lex/abstracts/lexer_tokenizing.html | 83 -
   trunk/libs/spirit/doc/html/spirit/lex/lexer_introduction.html | 88 -
   trunk/libs/spirit/doc/html/spirit/lex/quick_reference.html | 19
   trunk/libs/spirit/doc/html/spirit/lex/reference.html | 21
   trunk/libs/spirit/doc/html/spirit/lex/reference/concepts.html | 19
   trunk/libs/spirit/doc/html/spirit/lex/reference/concepts/lexer.html | 679 +++++++++------
   trunk/libs/spirit/doc/html/spirit/lex/reference/concepts/token.html | 15
   trunk/libs/spirit/doc/html/spirit/lex/reference/concepts/tokendef.html | 15
   trunk/libs/spirit/doc/html/spirit/lex/reference/concepts/tokenset.html | 15
   trunk/libs/spirit/doc/html/spirit/lex/reference/lexer_class.html | 49
   trunk/libs/spirit/doc/html/spirit/lex/reference/token_class.html | 15
   trunk/libs/spirit/doc/html/spirit/lex/reference/tokendef_class.html | 15
   trunk/libs/spirit/doc/html/spirit/lex/reference/tokenset_class.html | 21
   trunk/libs/spirit/doc/html/spirit/lex/tutorials.html | 24
   trunk/libs/spirit/doc/html/spirit/lex/tutorials/lexer_quickstart1.html | 108 +-
   trunk/libs/spirit/doc/html/spirit/lex/tutorials/lexer_quickstart2.html | 125 +-
   trunk/libs/spirit/doc/html/spirit/lex/tutorials/lexer_quickstart3.html | 210 ++--
   trunk/libs/spirit/doc/html/spirit/lex/tutorials/lexer_tutorials.html | 53
   trunk/libs/spirit/doc/html/spirit/notes.html | 15
   trunk/libs/spirit/doc/html/spirit/notes/style_guide.html | 49
   trunk/libs/spirit/doc/html/spirit/preface.html | 223 ++--
   trunk/libs/spirit/doc/html/spirit/qi.html | 25
   trunk/libs/spirit/doc/html/spirit/qi/quick_reference.html | 18
   trunk/libs/spirit/doc/html/spirit/qi/quick_reference/common_notation.html | 86 -
   trunk/libs/spirit/doc/html/spirit/qi/quick_reference/compound_attribute_rules.html | 223 ++--
   trunk/libs/spirit/doc/html/spirit/qi/quick_reference/non_terminals.html | 313 ++++---
   trunk/libs/spirit/doc/html/spirit/qi/quick_reference/phoenix.html | 40
   trunk/libs/spirit/doc/html/spirit/qi/quick_reference/predefined_primitive_parsers.html | 1732 ++++++++++++++++++++++++---------------
   trunk/libs/spirit/doc/html/spirit/qi/quick_reference/semantic_actions.html | 25
   trunk/libs/spirit/doc/html/spirit/qi/reference.html | 19
   trunk/libs/spirit/doc/html/spirit/qi/reference/basics.html | 85 -
   trunk/libs/spirit/doc/html/spirit/qi/reference/parser_concepts.html | 15
   trunk/libs/spirit/doc/html/spirit/qi/reference/parser_concepts/binaryparser.html | 189 ++-
   trunk/libs/spirit/doc/html/spirit/qi/reference/parser_concepts/naryparser.html | 147 +-
   trunk/libs/spirit/doc/html/spirit/qi/reference/parser_concepts/parser.html | 227 ++--
   trunk/libs/spirit/doc/html/spirit/qi/reference/parser_concepts/primitiveparser.html | 77
   trunk/libs/spirit/doc/html/spirit/qi/reference/parser_concepts/unaryparser.html | 143 +-
   trunk/libs/spirit/doc/html/spirit/qi/tutorials.html | 17
   trunk/libs/spirit/doc/html/spirit/qi/tutorials/complex___our_first_complex_parser.html | 50
   trunk/libs/spirit/doc/html/spirit/qi/tutorials/employee___parsing_into_structs.html | 187 ++--
   trunk/libs/spirit/doc/html/spirit/qi/tutorials/mini_xml___asts_.html | 269 +++---
   trunk/libs/spirit/doc/html/spirit/qi/tutorials/mini_xml___error_handling.html | 185 ++-
   trunk/libs/spirit/doc/html/spirit/qi/tutorials/number_list___stuffing_numbers_into_a_std__vector.html | 33
   trunk/libs/spirit/doc/html/spirit/qi/tutorials/number_list_attribute___one_more__with_style.html | 44
   trunk/libs/spirit/doc/html/spirit/qi/tutorials/number_list_redux___list_syntax.html | 25
   trunk/libs/spirit/doc/html/spirit/qi/tutorials/quick_start.html | 23
   trunk/libs/spirit/doc/html/spirit/qi/tutorials/roman_numerals.html | 153 +-
   trunk/libs/spirit/doc/html/spirit/qi/tutorials/semantic_actions.html | 68
   trunk/libs/spirit/doc/html/spirit/qi/tutorials/sum___adding_numbers.html | 113 +-
   trunk/libs/spirit/doc/html/spirit/qi/tutorials/warming_up.html | 151 +-
   trunk/libs/spirit/doc/html/spirit/references.html | 447 ++++++---
   trunk/libs/spirit/doc/html/spirit/structure.html | 15
   trunk/libs/spirit/doc/html/spirit/structure/include.html | 75
   trunk/libs/spirit/doc/html/spirit/what_s_new.html | 232 ++--
   trunk/libs/spirit/doc/lex/lexer_tutorials.qbk | 2
   trunk/libs/spirit/doc/qi/string.qbk | 1
   trunk/libs/spirit/doc/spirit2.qbk | 1
   96 files changed, 6823 insertions(+), 5505 deletions(-)

Modified: trunk/libs/spirit/doc/html/index.html
==============================================================================
--- trunk/libs/spirit/doc/html/index.html (original)
+++ trunk/libs/spirit/doc/html/index.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -3,7 +3,7 @@
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <title>Spirit 2.1</title>
 <link rel="stylesheet" href="../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="index.html" title="Spirit 2.1">
 <link rel="next" href="spirit/preface.html" title="Preface">
 </head>
@@ -18,7 +18,7 @@
 </tr></table>
 <hr>
 <div class="spirit-nav"><a accesskey="n" href="spirit/preface.html"><img src="../../../../doc/html/images/next.png" alt="Next"></a></div>
-<div class="article" lang="en">
+<div class="article" title="Spirit 2.1">
 <div class="titlepage">
 <div>
 <div><h2 class="title">
@@ -33,12 +33,13 @@
 </div></div>
 <div><p class="copyright">Copyright © 2001-2009 Joel
       de Guzman, Hartmut Kaiser</p></div>
-<div><div class="legalnotice"><p>
+<div><div class="legalnotice" title="Legal Notice">
+<a name="id1017677"></a><p>
         Distributed under the Boost Software License, Version 1.0. (See accompanying
         file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)
- </p></div></div>
+ </p>
+</div></div>
 </div>
-<div></div>
 <hr>
 </div>
 <div class="toc">
@@ -95,7 +96,12 @@
 <dd><dl>
 <dt><span class="section">Parser Concepts</span></dt>
 <dt><span class="section">Basics</span></dt>
-<dt><span class="section">String</span></dt>
+<dt><span class="section">char_</span></dt>
+</dl></dd>
+<dt><span class="section">String</span></dt>
+<dd><dl>
+<dt><span class="section">lit/string</span></dt>
+<dt><span class="section">symbols</span></dt>
 </dl></dd>
 </dl></dd>
 <dt><span class="section"> Karma</span></dt>
@@ -165,6 +171,8 @@
 <dt><span class="section">TokenSet Class</span></dt>
 </dl></dd>
 </dl></dd>
+<dt><span class="section"> Supporting libraries</span></dt>
+<dd><dl><dt><span class="section"> The multi pass iterator</span></dt></dl></dd>
 <dt><span class="section"> Spirit FAQ</span></dt>
 <dt><span class="section">Notes</span></dt>
 <dd><dl><dt><span class="section">Style Guide</span></dt></dl></dd>
@@ -177,7 +185,7 @@
   </p>
 </div>
 <table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
-<td align="left"><p><small>Last revised: July 11, 2009 at 05:34:38 GMT</small></p></td>
+<td align="left"><p><small>Last revised: July 12, 2009 at 03:33:41 GMT</small></p></td>
 <td align="right"><div class="copyright-footer"></div></td>
 </tr></table>
 <hr>

Modified: trunk/libs/spirit/doc/html/spirit/abstracts.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/abstracts.html (original)
+++ trunk/libs/spirit/doc/html/spirit/abstracts.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -3,10 +3,10 @@
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <title>Abstracts</title>
 <link rel="stylesheet" href="../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../index.html" title="Spirit 2.1">
 <link rel="up" href="../index.html" title="Spirit 2.1">
-<link rel="previous" href="structure/include.html" title="Include">
+<link rel="prev" href="structure/include.html" title="Include">
 <link rel="next" href="abstracts/syntax_diagram.html" title="Syntax Diagram">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -22,13 +22,10 @@
 <div class="spirit-nav">
 <a accesskey="p" href="structure/include.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="abstracts/syntax_diagram.html"><img src="../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h2 class="title" style="clear: both">
-<a name="spirit.abstracts"></a>Abstracts
-</h2></div></div>
-<div></div>
-</div>
+<div class="section" title="Abstracts">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="spirit.abstracts"></a><a class="link" href="abstracts.html" title="Abstracts">Abstracts</a>
+</h2></div></div></div>
 <div class="toc"><dl>
 <dt><span class="section">Syntax Diagram</span></dt>
 <dt><span class="section"><a href="abstracts/parsing_expression_grammar.html">Parsing

Modified: trunk/libs/spirit/doc/html/spirit/abstracts/parsing_expression_grammar.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/abstracts/parsing_expression_grammar.html (original)
+++ trunk/libs/spirit/doc/html/spirit/abstracts/parsing_expression_grammar.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -1,14 +1,13 @@
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title>Parsing
- Expression Grammar</title>
+<title>Parsing Expression Grammar</title>
 <link rel="stylesheet" href="../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../index.html" title="Spirit 2.1">
 <link rel="up" href="../abstracts.html" title="Abstracts">
-<link rel="previous" href="syntax_diagram.html" title="Syntax Diagram">
-<link rel="next" href="../qi.html" title=" Qi">
+<link rel="prev" href="syntax_diagram.html" title="Syntax Diagram">
+<link rel="next" href="../qi.html" title="Qi">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
 <table cellpadding="2" width="100%"><tr>
@@ -23,15 +22,11 @@
 <div class="spirit-nav">
 <a accesskey="p" href="syntax_diagram.html"><img src="../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../abstracts.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.html"><img src="../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h3 class="title">
-<a name="spirit.abstracts.parsing_expression_grammar"></a><a href="parsing_expression_grammar.html" title="Parsing
- Expression Grammar">Parsing
+<div class="section" title="Parsing Expression Grammar">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="spirit.abstracts.parsing_expression_grammar"></a><a class="link" href="parsing_expression_grammar.html" title="Parsing Expression Grammar">Parsing
       Expression Grammar</a>
-</h3></div></div>
-<div></div>
-</div>
+</h3></div></div></div>
 <p>
         Parsing Expression Grammars (PEG) are a derivative of Extended Backus-Naur
         Form (EBNF) with a different interpretation, designed to represent a recursive
@@ -44,24 +39,24 @@
         PEGs have an exact interpretation. There is only one valid parse tree (see
         [Abstract Syntax Tree) for each PEG grammar.
       </p>
-<a name="spirit.abstracts.parsing_expression_grammar.sequences"></a><h4>
-<a name="id414821"></a>
- Sequences
- </h4>
+<a name="spirit.abstracts.parsing_expression_grammar.sequences"></a><h5>
+<a name="id1027282"></a>
+ <a class="link" href="parsing_expression_grammar.html#spirit.abstracts.parsing_expression_grammar.sequences">Sequences</a>
+ </h5>
 <p>
         Sequences are represented by juxtaposition like in EBNF:
       </p>
 <pre class="programlisting"><span class="identifier">a</span> <span class="identifier">b</span>
 </pre>
 <p>
- The PEG expression above states that, in order for this to succeed, <tt class="computeroutput"><span class="identifier">a</span></tt> must follow <tt class="computeroutput"><span class="identifier">b</span></tt>.
+ The PEG expression above states that, in order for this to succeed, <code class="computeroutput"><span class="identifier">a</span></code> must follow <code class="computeroutput"><span class="identifier">b</span></code>.
         Here's the syntax diagram:
       </p>
 <div class="blockquote"><blockquote class="blockquote">
 <p>
           </p>
 <p>
- <span class="inlinemediaobject"><img src="images/sequence.png" alt="sequence"></span>
+ <span class="inlinemediaobject"><img src="../../images/sequence.png" alt="sequence"></span>
           </p>
 <p>
         </p>
@@ -72,66 +67,66 @@
 <pre class="programlisting"><span class="char">'x'</span> <span class="identifier">digit</span>
 </pre>
 <p>
- which means the character <tt class="computeroutput"><span class="identifier">x</span></tt>
+ which means the character <code class="computeroutput"><span class="identifier">x</span></code>
         must be followed by a digit.
       </p>
-<div class="note"><table border="0" summary="Note">
+<div class="note" title="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>
 </tr>
-<tr><td colspan="2" align="left" valign="top"><p>
- In Spirit.Qi, we use the <tt class="computeroutput"><span class="special">&gt;&gt;</span></tt>
+<tr><td align="left" valign="top"><p>
+ In Spirit.Qi, we use the <code class="computeroutput"><span class="special">&gt;&gt;</span></code>
           for sequences since C++ does not allow juxtaposition
         </p></td></tr>
 </table></div>
-<a name="spirit.abstracts.parsing_expression_grammar.alternatives"></a><h4>
-<a name="id414970"></a>
- Alternatives
- </h4>
+<a name="spirit.abstracts.parsing_expression_grammar.alternatives"></a><h5>
+<a name="id1027399"></a>
+ <a class="link" href="parsing_expression_grammar.html#spirit.abstracts.parsing_expression_grammar.alternatives">Alternatives</a>
+ </h5>
 <p>
         Alternatives are represented in PEG using the slash:
       </p>
 <pre class="programlisting"><span class="identifier">a</span> <span class="special">/</span> <span class="identifier">b</span>
 </pre>
-<div class="note"><table border="0" summary="Note">
+<div class="note" title="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>
 </tr>
-<tr><td colspan="2" align="left" valign="top"><p>
- In Spirit.Qi, we use the <tt class="computeroutput"><span class="special">|</span></tt>
+<tr><td align="left" valign="top"><p>
+ In Spirit.Qi, we use the <code class="computeroutput"><span class="special">|</span></code>
           for alternatives just as in EBNF
         </p></td></tr>
 </table></div>
 <p>
         Alternatives allow for choices. The expression above reads: try to match
- <tt class="computeroutput"><span class="identifier">a</span></tt>. If <tt class="computeroutput"><span class="identifier">a</span></tt>
- succeeds, success, if not try to match <tt class="computeroutput"><span class="identifier">b</span></tt>.
+ <code class="computeroutput"><span class="identifier">a</span></code>. If <code class="computeroutput"><span class="identifier">a</span></code>
+ succeeds, success, if not try to match <code class="computeroutput"><span class="identifier">b</span></code>.
         This is a bit of a deviation from the usual EBNF interpretation where you
- simply match <tt class="computeroutput"><span class="identifier">a</span></tt> <span class="bold"><b>or</b></span> <tt class="computeroutput"><span class="identifier">b</span></tt>.
+ simply match <code class="computeroutput"><span class="identifier">a</span></code> <span class="bold"><strong>or</strong></span> <code class="computeroutput"><span class="identifier">b</span></code>.
         Here's the syntax diagram:
       </p>
 <div class="blockquote"><blockquote class="blockquote">
 <p>
           </p>
 <p>
- <span class="inlinemediaobject"><img src="images/alternative.png" alt="alternative"></span>
+ <span class="inlinemediaobject"><img src="../../images/alternative.png" alt="alternative"></span>
           </p>
 <p>
         </p>
 </blockquote></div>
 <p>
         PEGs allow for ambiguity in the alternatives. In the expression above, both
- <tt class="computeroutput"><span class="identifier">a</span></tt> or <tt class="computeroutput"><span class="identifier">b</span></tt>
+ <code class="computeroutput"><span class="identifier">a</span></code> or <code class="computeroutput"><span class="identifier">b</span></code>
         can both match an input string. However, only the first matching alternative
         is valid. As noted, there can only be one valid parse tree ($$$ explain more
         about this $$$).
       </p>
-<a name="spirit.abstracts.parsing_expression_grammar.loops"></a><h4>
-<a name="id415155"></a>
- Loops
- </h4>
+<a name="spirit.abstracts.parsing_expression_grammar.loops"></a><h5>
+<a name="id1027538"></a>
+ <a class="link" href="parsing_expression_grammar.html#spirit.abstracts.parsing_expression_grammar.loops">Loops</a>
+ </h5>
 <p>
         Again, like EBNF, PEG uses the regular-expression Kleene star and the plus
         loops:
@@ -139,12 +134,12 @@
 <pre class="programlisting"><span class="identifier">a</span><span class="special">*</span>
 <span class="identifier">a</span><span class="special">+</span>
 </pre>
-<div class="note"><table border="0" summary="Note">
+<div class="note" title="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>
 </tr>
-<tr><td colspan="2" align="left" valign="top"><p>
+<tr><td align="left" valign="top"><p>
           Spirit.Qi uses the prefix star and plus since there is no postfix star
           or plus in C++.
         </p></td></tr>
@@ -156,7 +151,7 @@
 <p>
           </p>
 <p>
- <span class="inlinemediaobject"><img src="images/kleene.png" alt="kleene"></span>
+ <span class="inlinemediaobject"><img src="../../images/kleene.png" alt="kleene"></span>
           </p>
 <p>
         </p>
@@ -165,14 +160,14 @@
 <p>
           </p>
 <p>
- <span class="inlinemediaobject"><img src="images/plus.png" alt="plus"></span>
+ <span class="inlinemediaobject"><img src="../../images/plus.png" alt="plus"></span>
           </p>
 <p>
         </p>
 </blockquote></div>
 <p>
- The first, called the Kleene star, matches zero or more of its subject <tt class="computeroutput"><span class="identifier">a</span></tt>. The second, plus, matches one ore more
- of its subject <tt class="computeroutput"><span class="identifier">a</span></tt>.
+ The first, called the Kleene star, matches zero or more of its subject <code class="computeroutput"><span class="identifier">a</span></code>. The second, plus, matches one ore more
+ of its subject <code class="computeroutput"><span class="identifier">a</span></code>.
       </p>
 <p>
         Unlike EBNF, PEGs have greedy loops. It will match as much as it can until
@@ -191,10 +186,10 @@
         a major gotcha. PEG provides a couple of other mechanisms to circumvent this.
         We will see more of these other mechanisms shortly.
       </p>
-<a name="spirit.abstracts.parsing_expression_grammar.difference"></a><h4>
-<a name="id415332"></a>
- Difference
- </h4>
+<a name="spirit.abstracts.parsing_expression_grammar.difference"></a><h5>
+<a name="id1027679"></a>
+ <a class="link" href="parsing_expression_grammar.html#spirit.abstracts.parsing_expression_grammar.difference">Difference</a>
+ </h5>
 <p>
         In certain cases, you may want to restrict a certain expression. You can
         think of a PEG expression as a match for a potentially infinite set of strings.
@@ -203,8 +198,8 @@
 <pre class="programlisting"><span class="identifier">a</span> <span class="special">-</span> <span class="identifier">b</span>
 </pre>
 <p>
- The expression reads: match <tt class="computeroutput"><span class="identifier">a</span></tt>
- but not <tt class="computeroutput"><span class="identifier">b</span></tt>.
+ The expression reads: match <code class="computeroutput"><span class="identifier">a</span></code>
+ but not <code class="computeroutput"><span class="identifier">b</span></code>.
       </p>
 </div>
 <table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>

Modified: trunk/libs/spirit/doc/html/spirit/abstracts/syntax_diagram.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/abstracts/syntax_diagram.html (original)
+++ trunk/libs/spirit/doc/html/spirit/abstracts/syntax_diagram.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -3,12 +3,11 @@
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <title>Syntax Diagram</title>
 <link rel="stylesheet" href="../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../index.html" title="Spirit 2.1">
 <link rel="up" href="../abstracts.html" title="Abstracts">
-<link rel="previous" href="../abstracts.html" title="Abstracts">
-<link rel="next" href="parsing_expression_grammar.html" title="Parsing
- Expression Grammar">
+<link rel="prev" href="../abstracts.html" title="Abstracts">
+<link rel="next" href="parsing_expression_grammar.html" title="Parsing Expression Grammar">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
 <table cellpadding="2" width="100%"><tr>
@@ -23,28 +22,25 @@
 <div class="spirit-nav">
 <a accesskey="p" href="../abstracts.html"><img src="../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../abstracts.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="parsing_expression_grammar.html"><img src="../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h3 class="title">
-<a name="spirit.abstracts.syntax_diagram"></a>Syntax Diagram
-</h3></div></div>
-<div></div>
-</div>
+<div class="section" title="Syntax Diagram">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="spirit.abstracts.syntax_diagram"></a><a class="link" href="syntax_diagram.html" title="Syntax Diagram">Syntax Diagram</a>
+</h3></div></div></div>
 <p>
         In the next section, we will deal with Parsing Expression Grammars (PEG),
         a variant of Extended Backus-Naur Form (EBNF) with a different interpretation.
         It is easier to understand PEG using Syntax Diagrams. Syntax diagrams represent
         a grammar graphically. It was used extensibly by Niklaus Wirth
- <sup>[<a name="id414322" href="#ftn.id414322">2</a>]</sup>
+ <sup>[<a name="id1026870" href="#ftn.id1026870" class="footnote">2</a>]</sup>
         in the "Pascal User Manual". Syntax Diagrams are easily understandable
         with programmers due to its similarity to flow charts. The isomorphism of
         the diagrams and functions make it ideal for representing [Recursive Descent
         parsers which are essentially mutually recursive functions.
       </p>
-<a name="spirit.abstracts.syntax_diagram.elements"></a><h4>
-<a name="id414345"></a>
- Elements
- </h4>
+<a name="spirit.abstracts.syntax_diagram.elements"></a><h5>
+<a name="id1026882"></a>
+ <a class="link" href="syntax_diagram.html#spirit.abstracts.syntax_diagram.elements">Elements</a>
+ </h5>
 <p>
         All diagrams have one entry and exit point. Arrows connect all possible paths
         through the grammar from the entry point to the exit point.
@@ -53,7 +49,7 @@
 <p>
           </p>
 <p>
- <span class="inlinemediaobject"><img src="images/start_stop.png" alt="start_stop"></span>
+ <span class="inlinemediaobject"><img src="../../images/start_stop.png" alt="start_stop"></span>
           </p>
 <p>
         </p>
@@ -66,7 +62,7 @@
 <p>
           </p>
 <p>
- <span class="inlinemediaobject"><img src="images/terminal.png" alt="terminal"></span>
+ <span class="inlinemediaobject"><img src="../../images/terminal.png" alt="terminal"></span>
           </p>
 <p>
         </p>
@@ -80,15 +76,15 @@
 <p>
           </p>
 <p>
- <span class="inlinemediaobject"><img src="images/non-terminal.png" alt="non-terminal"></span>
+ <span class="inlinemediaobject"><img src="../../images/non-terminal.png" alt="non-terminal"></span>
           </p>
 <p>
         </p>
 </blockquote></div>
-<a name="spirit.abstracts.syntax_diagram.constructs"></a><h4>
-<a name="id414464"></a>
- Constructs
- </h4>
+<a name="spirit.abstracts.syntax_diagram.constructs"></a><h5>
+<a name="id1026982"></a>
+ <a class="link" href="syntax_diagram.html#spirit.abstracts.syntax_diagram.constructs">Constructs</a>
+ </h5>
 <p>
         The most basic composition is the Sequence. B follows A:
       </p>
@@ -96,7 +92,7 @@
 <p>
           </p>
 <p>
- <span class="inlinemediaobject"><img src="images/sequence.png" alt="sequence"></span>
+ <span class="inlinemediaobject"><img src="../../images/sequence.png" alt="sequence"></span>
           </p>
 <p>
         </p>
@@ -111,7 +107,7 @@
 <p>
           </p>
 <p>
- <span class="inlinemediaobject"><img src="images/alternative.png" alt="alternative"></span>
+ <span class="inlinemediaobject"><img src="../../images/alternative.png" alt="alternative"></span>
           </p>
 <p>
         </p>
@@ -123,7 +119,7 @@
 <p>
           </p>
 <p>
- <span class="inlinemediaobject"><img src="images/optional.png" alt="optional"></span>
+ <span class="inlinemediaobject"><img src="../../images/optional.png" alt="optional"></span>
           </p>
 <p>
         </p>
@@ -135,7 +131,7 @@
 <p>
           </p>
 <p>
- <span class="inlinemediaobject"><img src="images/kleene.png" alt="kleene"></span>
+ <span class="inlinemediaobject"><img src="../../images/kleene.png" alt="kleene"></span>
           </p>
 <p>
         </p>
@@ -144,7 +140,7 @@
 <p>
           </p>
 <p>
- <span class="inlinemediaobject"><img src="images/plus.png" alt="plus"></span>
+ <span class="inlinemediaobject"><img src="../../images/plus.png" alt="plus"></span>
           </p>
 <p>
         </p>
@@ -156,10 +152,10 @@
         is a crucial difference between PEG and general Context Free Grammars (CFGs).
         This behavior is quite obvious with syntax diagrams as they resemble flow-charts.
       </p>
-<a name="spirit.abstracts.syntax_diagram.predicates"></a><h4>
-<a name="id414645"></a>
- Predicates
- </h4>
+<a name="spirit.abstracts.syntax_diagram.predicates"></a><h5>
+<a name="id1027142"></a>
+ <a class="link" href="syntax_diagram.html#spirit.abstracts.syntax_diagram.predicates">Predicates</a>
+ </h5>
 <p>
         Now, the following are Syntax Diagram versions of PEG predicates. These are
         not traditionally found in Syntax Diagrams. These are special extensions
@@ -172,7 +168,7 @@
 <p>
           </p>
 <p>
- <span class="inlinemediaobject"><img src="images/predicate.png" alt="predicate"></span>
+ <span class="inlinemediaobject"><img src="../../images/predicate.png" alt="predicate"></span>
           </p>
 <p>
         </p>
@@ -189,7 +185,7 @@
 <p>
           </p>
 <p>
- <span class="inlinemediaobject"><img src="images/and_predicate.png" alt="and_predicate"></span>
+ <span class="inlinemediaobject"><img src="../../images/and_predicate.png" alt="and_predicate"></span>
           </p>
 <p>
         </p>
@@ -198,7 +194,7 @@
 <p>
           </p>
 <p>
- <span class="inlinemediaobject"><img src="images/not_predicate.png" alt="not_predicate"></span>
+ <span class="inlinemediaobject"><img src="../../images/not_predicate.png" alt="not_predicate"></span>
           </p>
 <p>
         </p>
@@ -212,7 +208,7 @@
       </p>
 <div class="footnotes">
 <br><hr width="100" align="left">
-<div class="footnote"><p><sup>[<a name="ftn.id414322" href="#id414322">2</a>] </sup>
+<div class="footnote"><p><sup>[<a name="ftn.id1026870" href="#id1026870" class="para">2</a>] </sup>
             Niklaus Wirth: The Programming Language Pascal. (July 1973)
           </p></div>
 </div>

Modified: trunk/libs/spirit/doc/html/spirit/acknowledgments.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/acknowledgments.html (original)
+++ trunk/libs/spirit/doc/html/spirit/acknowledgments.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -3,10 +3,10 @@
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <title>Acknowledgments</title>
 <link rel="stylesheet" href="../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../index.html" title="Spirit 2.1">
 <link rel="up" href="../index.html" title="Spirit 2.1">
-<link rel="previous" href="notes/style_guide.html" title="Style Guide">
+<link rel="prev" href="notes/style_guide.html" title="Style Guide">
 <link rel="next" href="references.html" title="References">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -22,13 +22,10 @@
 <div class="spirit-nav">
 <a accesskey="p" href="notes/style_guide.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>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h2 class="title" style="clear: both">
-<a name="spirit.acknowledgments"></a>Acknowledgments
-</h2></div></div>
-<div></div>
-</div>
+<div class="section" title="Acknowledgments">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="spirit.acknowledgments"></a><a class="link" href="acknowledgments.html" title="Acknowledgments">Acknowledgments</a>
+</h2></div></div></div>
 <p>
       This version of Spirit is a complete rewrite of the <span class="emphasis"><em>classic</em></span>
       Spirit many people have been contributing to (see below). But there are a couple
@@ -36,52 +33,52 @@
       would like to express our special acknowledgement to:
     </p>
 <p>
- <span class="bold"><b>Eric Niebler</b></span> for writing Boost.Proto, without
+ <span class="bold"><strong>Eric Niebler</strong></span> for writing Boost.Proto, without
       which this rewrite wouldn't have been possible, and helping with examples,
       advices, and suggestions on how to use Boost.Proto in the best possible way.
     </p>
 <p>
- <span class="bold"><b>Ben Hanson</b></span> for providing us with an early
+ <span class="bold"><strong>Ben Hanson</strong></span> for providing us with an early
       version of his Lexertl library, which is proposed to be included into Boost
       (as Boost.Lexer), but at the time of this writing the Boost review for this
       library is still pending.
     </p>
 <p>
- <span class="bold"><b>FIXME</b></span>: Add more people
+ <span class="bold"><strong>FIXME</strong></span>: Add more people
     </p>
-<a name="spirit.acknowledgments.acknowledgements_from_the_spirit_v1__emphasis_classic__emphasis__documentation"></a><h3>
-<a name="id509007"></a>
- <a href="acknowledgments.html#spirit.acknowledgments.acknowledgements_from_the_spirit_v1__emphasis_classic__emphasis__documentation">Acknowledgements
+<a name="spirit.acknowledgments.acknowledgements_from_the_spirit_v1__emphasis_classic__emphasis__documentation"></a><h4>
+<a name="id1128526"></a>
+ <a class="link" href="acknowledgments.html#spirit.acknowledgments.acknowledgements_from_the_spirit_v1__emphasis_classic__emphasis__documentation">Acknowledgements
       from the Spirit V1 <span class="emphasis"><em>classic</em></span> Documentation</a>
- </h3>
+ </h4>
 <p>
       Special thanks for working on Spirit <span class="emphasis"><em>classic</em></span> to:
     </p>
 <p>
- <span class="bold"><b>Dan Nuffer</b></span> for his work on lexers, parse trees,
+ <span class="bold"><strong>Dan Nuffer</strong></span> for his work on lexers, parse trees,
       ASTs, XML parsers, the multi-pass iterator as well as administering Spirit's
       site, editing, maintaining the CVS and doing the releases plus a zillion of
       other chores that were almost taken for granted.
     </p>
 <p>
- <span class="bold"><b>Hartmut Kaiser</b></span> for his work on the C parser,
+ <span class="bold"><strong>Hartmut Kaiser</strong></span> for his work on the C parser,
       the work on the C/C++ preprocessor, utility parsers, the original port to Intel
       5.0, various work on Phoenix, porting to v1.5, the meta-parsers, the grouping-parsers,
       extensive testing and painstaking attention to details.
     </p>
 <p>
- <span class="bold"><b>Martin Wille</b></span> who improved grammar multi thread
+ <span class="bold"><strong>Martin Wille</strong></span> who improved grammar multi thread
       safety, contributed the eol_p parser, the dynamic parsers, documentation and
       for taking an active role in almost every aspect from brainstorming and design
       to coding. And, as always, helps keep the regression tests for g++ on Linux
       as green as ever :-).
     </p>
 <p>
- <span class="bold"><b>Martijn W. Van Der Lee</b></span> our Web site administrator
+ <span class="bold"><strong>Martijn W. Van Der Lee</strong></span> our Web site administrator
       and for contributing the RFC821 parser.
     </p>
 <p>
- <span class="bold"><b>Giovanni Bajo</b></span> for last minute tweaks of Spirit
+ <span class="bold"><strong>Giovanni Bajo</strong></span> for last minute tweaks of Spirit
       1.8.0 for CodeWarrior 8.3. Actually, I'm ashamed Giovanni was not in this list
       already. He's done a lot since Spirit 1.5, the first Boost.Spirit release.
       He's instrumental in the porting of the Spirit iterators stuff to the new Boost
@@ -89,107 +86,107 @@
       tests here and there.
     </p>
 <p>
- <span class="bold"><b>Juan Carlos Arevalo-Baeza (JCAB)*</b></span> for his
+ <span class="bold"><strong>Juan Carlos Arevalo-Baeza (JCAB)*</strong></span> for his
       work on the C++ parser, the position iterator, ports to v1.5 and keeping the
       mailing list discussions alive and kicking.
     </p>
 <p>
- <span class="bold"><b>Vaclav Vesely</b></span>, lots of stuff, the no_actions
+ <span class="bold"><strong>Vaclav Vesely</strong></span>, lots of stuff, the no_actions
       directive, various patches fixes, the distinct parsers, the lazy parser, some
       phoenix tweaks and add-ons (e.g. new_). Also, *Stefan Slapeta] and wife for
       editing Vaclav's distinct parser doc.
     </p>
 <p>
- <span class="bold"><b>Raghavendra Satish</b></span> for doing the original
+ <span class="bold"><strong>Raghavendra Satish</strong></span> for doing the original
       v1.3 port to VC++ and his work on Phoenix.
     </p>
 <p>
- <span class="bold"><b>Noah Stein</b></span> for following up and helping Ragav
+ <span class="bold"><strong>Noah Stein</strong></span> for following up and helping Ragav
       on the VC++ ports.
     </p>
 <p>
- <span class="bold"><b>Hakki Dogusan</b></span>, for his original v1.0 Pascal
+ <span class="bold"><strong>Hakki Dogusan</strong></span>, for his original v1.0 Pascal
       parser.
     </p>
 <p>
- <span class="bold"><b>John (EBo) David</b></span> for his work on the VM and
+ <span class="bold"><strong>John (EBo) David</strong></span> for his work on the VM and
       watching over my shoulder as I code giving the impression of distance eXtreme
       programming.
     </p>
 <p>
- <span class="bold"><b>Chris Uzdavinis</b></span> for feeding in comments and
+ <span class="bold"><strong>Chris Uzdavinis</strong></span> for feeding in comments and
       valuable suggestions as well as editing the documentation.
     </p>
 <p>
- <span class="bold"><b>Carsten Stoll</b></span>, for his work on dynamic parsers.
+ <span class="bold"><strong>Carsten Stoll</strong></span>, for his work on dynamic parsers.
     </p>
 <p>
- <span class="bold"><b>Andy Elvey</b></span> and his conifer parser.
+ <span class="bold"><strong>Andy Elvey</strong></span> and his conifer parser.
     </p>
 <p>
- <span class="bold"><b>Bruce Florman</b></span>, who did the original v1.0 port
+ <span class="bold"><strong>Bruce Florman</strong></span>, who did the original v1.0 port
       to VC++.
     </p>
 <p>
- <span class="bold"><b>Jeff Westfahl</b></span> for porting the loop parsers
+ <span class="bold"><strong>Jeff Westfahl</strong></span> for porting the loop parsers
       to v1.5 and contributing the file iterator.
     </p>
 <p>
- <span class="bold"><b>Peter Simons</b></span> for the RFC date parser example
+ <span class="bold"><strong>Peter Simons</strong></span> for the RFC date parser example
       and tutorial plus helping out with some nitty gritty details.
     </p>
 <p>
- <span class="bold"><b>Markus Schöpflin</b></span> for suggesting the end_p parser
+ <span class="bold"><strong>Markus Schöpflin</strong></span> for suggesting the end_p parser
       and lots of other nifty things and his active presence in the mailing list.
     </p>
 <p>
- <span class="bold"><b>Doug Gregor</b></span> for mentoring and his ability
+ <span class="bold"><strong>Doug Gregor</strong></span> for mentoring and his ability
       to see things that others don't.
     </p>
 <p>
- <span class="bold"><b>David Abrahams</b></span> for giving Joel a job that
+ <span class="bold"><strong>David Abrahams</strong></span> for giving Joel a job that
       allows him to still work on Spirit, plus countless advice and help on C++ and
       specifically template metaprogramming.
     </p>
 <p>
- <span class="bold"><b>Aleksey Gurtovoy</b></span> for his MPL library from
+ <span class="bold"><strong>Aleksey Gurtovoy</strong></span> for his MPL library from
       which we stole many metaprogramming tricks especially for less conforming compilers
       such as Borland and VC6/7.
     </p>
 <p>
- <span class="bold"><b>Gustavo Guerra</b></span> for his last minute review
+ <span class="bold"><strong>Gustavo Guerra</strong></span> for his last minute review
       of Spirit and constant feedback, plus patches here and there (e.g. proposing
       the new dot behavior of the real numerics parsers).
     </p>
 <p>
- <span class="bold"><b>Nicola Musatti</b></span>, <span class="bold"><b>Paul
- Snively</b></span>, <span class="bold"><b>Alisdair Meredith</b></span> and
- <span class="bold"><b>Hugo Duncan</b></span> for testing and sending in various
+ <span class="bold"><strong>Nicola Musatti</strong></span>, <span class="bold"><strong>Paul
+ Snively</strong></span>, <span class="bold"><strong>Alisdair Meredith</strong></span> and
+ <span class="bold"><strong>Hugo Duncan</strong></span> for testing and sending in various
       patches.
     </p>
 <p>
- <span class="bold"><b>Steve Rowe</b></span> for his splendid work on the TSTs
+ <span class="bold"><strong>Steve Rowe</strong></span> for his splendid work on the TSTs
       that will soon be taken into Spirit.
     </p>
 <p>
- <span class="bold"><b>Jonathan de Halleux</b></span> for his work on actors.
+ <span class="bold"><strong>Jonathan de Halleux</strong></span> for his work on actors.
     </p>
 <p>
- <span class="bold"><b>Angus Leeming</b></span> for last minute editing work
+ <span class="bold"><strong>Angus Leeming</strong></span> for last minute editing work
       on the 1.8.0 release documentation, his work on Phoenix and his active presence
       in the Spirit mailing list.
     </p>
 <p>
- <span class="bold"><b>Joao Abecasis</b></span> for his active presence in the
+ <span class="bold"><strong>Joao Abecasis</strong></span> for his active presence in the
       Spirit mailing list, providing user support, participating in the discussions
       and so on.
     </p>
 <p>
- <span class="bold"><b>Guillaume Melquiond</b></span> for a last minute patch
+ <span class="bold"><strong>Guillaume Melquiond</strong></span> for a last minute patch
       to multi_pass for 1.8.1.
     </p>
 <p>
- <span class="bold"><b>Peder Holt</b></span> for his porting work on Phoenix,
+ <span class="bold"><strong>Peder Holt</strong></span> for his porting work on Phoenix,
       Fusion and Spirit to VC6.
     </p>
 <p>
@@ -206,19 +203,19 @@
       in the review:
     </p>
 <p>
- <span class="bold"><b>John Maddock</b></span>, our review manager, <span class="bold"><b>Aleksey Gurtovoy</b></span>, <span class="bold"><b>Andre Hentz</b></span>,
- <span class="bold"><b>Beman Dawes</b></span>, <span class="bold"><b>Carl Daniel</b></span>,
- <span class="bold"><b>Christopher Currie</b></span>, <span class="bold"><b>Dan
- Gohman</b></span>, <span class="bold"><b>Dan Nuffer</b></span>, <span class="bold"><b>Daryle
- Walker</b></span>, <span class="bold"><b>David Abrahams</b></span>, <span class="bold"><b>David B. Held</b></span>, <span class="bold"><b>Dirk Gerrits</b></span>,
- <span class="bold"><b>Douglas Gregor</b></span>, <span class="bold"><b>Hartmut
- Kaiser</b></span>, <span class="bold"><b>Iain K.Hanson</b></span>, <span class="bold"><b>Juan Carlos Arevalo-Baeza</b></span>, <span class="bold"><b>Larry
- Evans</b></span>, <span class="bold"><b>Martin Wille</b></span>, <span class="bold"><b>Mattias Flodin</b></span>, <span class="bold"><b>Noah Stein</b></span>,
- <span class="bold"><b>Nuno Lucas</b></span>, <span class="bold"><b>Peter Dimov</b></span>,
- <span class="bold"><b>Peter Simons</b></span>, <span class="bold"><b>Petr Kocmid</b></span>,
- <span class="bold"><b>Ross Smith</b></span>, <span class="bold"><b>Scott Kirkwood</b></span>,
- <span class="bold"><b>Steve Cleary</b></span>, <span class="bold"><b>Thorsten
- Ottosen</b></span>, <span class="bold"><b>Tom Wenisch</b></span>, <span class="bold"><b>Vladimir Prus</b></span>
+ <span class="bold"><strong>John Maddock</strong></span>, our review manager, <span class="bold"><strong>Aleksey Gurtovoy</strong></span>, <span class="bold"><strong>Andre Hentz</strong></span>,
+ <span class="bold"><strong>Beman Dawes</strong></span>, <span class="bold"><strong>Carl Daniel</strong></span>,
+ <span class="bold"><strong>Christopher Currie</strong></span>, <span class="bold"><strong>Dan
+ Gohman</strong></span>, <span class="bold"><strong>Dan Nuffer</strong></span>, <span class="bold"><strong>Daryle
+ Walker</strong></span>, <span class="bold"><strong>David Abrahams</strong></span>, <span class="bold"><strong>David B. Held</strong></span>, <span class="bold"><strong>Dirk Gerrits</strong></span>,
+ <span class="bold"><strong>Douglas Gregor</strong></span>, <span class="bold"><strong>Hartmut
+ Kaiser</strong></span>, <span class="bold"><strong>Iain K.Hanson</strong></span>, <span class="bold"><strong>Juan Carlos Arevalo-Baeza</strong></span>, <span class="bold"><strong>Larry
+ Evans</strong></span>, <span class="bold"><strong>Martin Wille</strong></span>, <span class="bold"><strong>Mattias Flodin</strong></span>, <span class="bold"><strong>Noah Stein</strong></span>,
+ <span class="bold"><strong>Nuno Lucas</strong></span>, <span class="bold"><strong>Peter Dimov</strong></span>,
+ <span class="bold"><strong>Peter Simons</strong></span>, <span class="bold"><strong>Petr Kocmid</strong></span>,
+ <span class="bold"><strong>Ross Smith</strong></span>, <span class="bold"><strong>Scott Kirkwood</strong></span>,
+ <span class="bold"><strong>Steve Cleary</strong></span>, <span class="bold"><strong>Thorsten
+ Ottosen</strong></span>, <span class="bold"><strong>Tom Wenisch</strong></span>, <span class="bold"><strong>Vladimir Prus</strong></span>
     </p>
 <p>
       Finally thanks to SourceForge for hosting the Spirit project and Boost: a C++

Modified: trunk/libs/spirit/doc/html/spirit/faq.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/faq.html (original)
+++ trunk/libs/spirit/doc/html/spirit/faq.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -1,12 +1,12 @@
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title> Spirit FAQ</title>
+<title>Spirit FAQ</title>
 <link rel="stylesheet" href="../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../index.html" title="Spirit 2.1">
 <link rel="up" href="../index.html" title="Spirit 2.1">
-<link rel="previous" href="lex/reference/tokenset_class.html" title="TokenSet Class">
+<link rel="prev" href="support/multi_pass.html" title="The multi pass iterator">
 <link rel="next" href="notes.html" title="Notes">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -20,35 +20,32 @@
 </tr></table>
 <hr>
 <div class="spirit-nav">
-<a accesskey="p" href="lex/reference/tokenset_class.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="notes.html"><img src="../../../../../doc/html/images/next.png" alt="Next"></a>
+<a accesskey="p" href="support/multi_pass.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="notes.html"><img src="../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h2 class="title" style="clear: both">
-<a name="spirit.faq"></a> Spirit FAQ
-</h2></div></div>
-<div></div>
-</div>
-<a name="spirit.faq.i_m_getting_multiple_symbol_definition_errors_while_using_visual_c____anything_i_could_do_about_that_"></a><h3>
-<a name="id507182"></a>
- <a href="faq.html#spirit.faq.i_m_getting_multiple_symbol_definition_errors_while_using_visual_c____anything_i_could_do_about_that_">I'm
+<div class="section" title="Spirit FAQ">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="spirit.faq"></a><a class="link" href="faq.html" title="Spirit FAQ"> Spirit FAQ</a>
+</h2></div></div></div>
+<a name="spirit.faq.i_m_getting_multiple_symbol_definition_errors_while_using_visual_c____anything_i_could_do_about_that_"></a><h4>
+<a name="id1127270"></a>
+ <a class="link" href="faq.html#spirit.faq.i_m_getting_multiple_symbol_definition_errors_while_using_visual_c____anything_i_could_do_about_that_">I'm
       getting multiple symbol definition errors while using Visual C++. Anything
       I could do about that?</a>
- </h3>
+ </h4>
 <p>
- Do you see strange multiple symbol definition linker errors mentioning <tt class="computeroutput"><span class="identifier">boost</span><span class="special">::</span><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">failed</span></tt>
- and <tt class="computeroutput"><span class="identifier">boost</span><span class="special">::</span><span class="identifier">spirit</span><span class="special">::</span><span class="identifier">qi</span><span class="special">::</span><span class="identifier">rule</span></tt>?
+ Do you see strange multiple symbol definition linker errors mentioning <code class="computeroutput"><span class="identifier">boost</span><span class="special">::</span><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">failed</span></code>
+ and <code class="computeroutput"><span class="identifier">boost</span><span class="special">::</span><span class="identifier">spirit</span><span class="special">::</span><span class="identifier">qi</span><span class="special">::</span><span class="identifier">rule</span></code>?
       Then this FAQ entry might be for you.
     </p>
 <p>
       <a href="http://www.boost.org/libs/mpl/index.html" target="_top">Boost.Mpl</a> implements
- a macro <tt class="computeroutput"><span class="identifier">BOOST_MPL_ASSERT_MSG</span><span class="special">()</span></tt> which essentially is a more powerfull version
+ a macro <code class="computeroutput"><span class="identifier">BOOST_MPL_ASSERT_MSG</span><span class="special">()</span></code> which essentially is a more powerfull version
       of static_assert. Unfortunately under certain circumstances using this macro
       may lead to the aformentioned linker errors.
     </p>
 <p>
       <a href="http://spirit.sourceforge.net" target="_top">Spirit</a> allows you to define
- a preprocessor constant disabling the usage of <tt class="computeroutput"><span class="identifier">BOOST_MPL_ASSERT_MSG</span><span class="special">()</span></tt>, while switching to <tt class="computeroutput"><span class="identifier">BOOST_STATIC_ASSRT</span><span class="special">()</span></tt> instead. If you define BOOST_SPIRIT_DONT_USE_MPL_ASSERT_MSG=1
+ a preprocessor constant disabling the usage of <code class="computeroutput"><span class="identifier">BOOST_MPL_ASSERT_MSG</span><span class="special">()</span></code>, while switching to <code class="computeroutput"><span class="identifier">BOOST_STATIC_ASSRT</span><span class="special">()</span></code> instead. If you define BOOST_SPIRIT_DONT_USE_MPL_ASSERT_MSG=1
       (either by adding
     </p>
 <pre class="programlisting"><span class="special">-</span><span class="identifier">DBOOST_SPIRIT_DONT_USE_MPL_ASSERT_MSG</span><span class="special">=</span><span class="number">1</span>
@@ -66,12 +63,12 @@
       see while using this workaround are less verbose error messages generated from
       static_assert.
     </p>
-<a name="spirit.faq.i_m_very_confused_about_the_header_hell_in_my_boost_spirit_directory__what_s_all_this_about_"></a><h3>
-<a name="id507443"></a>
- <a href="faq.html#spirit.faq.i_m_very_confused_about_the_header_hell_in_my_boost_spirit_directory__what_s_all_this_about_">I'm
+<a name="spirit.faq.i_m_very_confused_about_the_header_hell_in_my_boost_spirit_directory__what_s_all_this_about_"></a><h4>
+<a name="id1127440"></a>
+ <a class="link" href="faq.html#spirit.faq.i_m_very_confused_about_the_header_hell_in_my_boost_spirit_directory__what_s_all_this_about_">I'm
       very confused about the header hell in my boost/spirit directory. What's all
       this about?</a>
- </h3>
+ </h4>
 <p>
       The boost/spirit directory currently holds two versions of the Spirit library:
       <span class="emphasis"><em>Spirit.Classic</em></span> (former V1.8.x) and SpiritV2. Both are
@@ -186,7 +183,7 @@
 </tr></table>
 <hr>
 <div class="spirit-nav">
-<a accesskey="p" href="lex/reference/tokenset_class.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="notes.html"><img src="../../../../../doc/html/images/next.png" alt="Next"></a>
+<a accesskey="p" href="support/multi_pass.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="notes.html"><img src="../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
 </body>
 </html>

Modified: trunk/libs/spirit/doc/html/spirit/introduction.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/introduction.html (original)
+++ trunk/libs/spirit/doc/html/spirit/introduction.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -3,10 +3,10 @@
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <title>Introduction</title>
 <link rel="stylesheet" href="../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../index.html" title="Spirit 2.1">
 <link rel="up" href="../index.html" title="Spirit 2.1">
-<link rel="previous" href="what_s_new.html" title="What's New">
+<link rel="prev" href="what_s_new.html" title="What's New">
 <link rel="next" href="structure.html" title="Structure">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -22,18 +22,15 @@
 <div class="spirit-nav">
 <a accesskey="p" href="what_s_new.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="structure.html"><img src="../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h2 class="title" style="clear: both">
-<a name="spirit.introduction"></a>Introduction
-</h2></div></div>
-<div></div>
-</div>
+<div class="section" title="Introduction">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="spirit.introduction"></a><a class="link" href="introduction.html" title="Introduction">Introduction</a>
+</h2></div></div></div>
 <p>
       Boost Spirit is an object-oriented, recursive-descent parser and output generation
       library for C++. It allows you to write grammars and format descriptions using
       a format similar to Extended Backus Naur Form (EBNF)
- <sup>[<a name="id410902" href="#ftn.id410902">1</a>]</sup>
+ <sup>[<a name="id1023075" href="#ftn.id1023075" class="footnote">1</a>]</sup>
       directly in C++. These inline grammar specifications can mix freely with other
       C++ code and, thanks to the generative power of C++ templates, are immediately
       executable. In retrospect, conventional compiler-compilers or parser-generators
@@ -45,14 +42,14 @@
       embedded languages (DSEL). In fact, Spirit exposes 3 different DSELs to the
       user:
     </p>
-<div class="itemizedlist"><ul type="disc">
-<li>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem">
         one for creating parser grammars,
       </li>
-<li>
+<li class="listitem">
         one for the specification of the required tokens to be used for parsing,
       </li>
-<li>
+<li class="listitem">
         and one for the description of the required output formats.
       </li>
 </ul></div>
@@ -70,28 +67,28 @@
       can directly be used to generate arbitrarily-formatted output.
     </p>
 <p>
- The figure below depicts the
+ The <a class="link" href="introduction.html#spirit.spiritstructure" title="Figure 1. The overall structure of the Boost Spirit library">figure</a> below depicts the
       overall structure of the Boost Spirit library. The library consists of 4 major
       parts:
     </p>
-<div class="itemizedlist"><ul type="disc">
-<li>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem">
 <span class="emphasis"><em>Spirit.Classic</em></span>: This is the almost-unchanged code base
         taken from the former Boost Spirit V1.8 distribution. It has been moved into
         the namespace boost::spirit::classic. A special compatibility layer has been
         added to ensure complete compatibility with existing code using Spirit V1.8.
       </li>
-<li>
+<li class="listitem">
 <span class="emphasis"><em>Spirit.Qi</em></span>: This is the parser library allowing you to
         build recursive descent parsers. The exposed domain-specific language can
         be used to describe the grammars to implement, and the rules for storing
         the parsed information.
       </li>
-<li>
+<li class="listitem">
 <span class="emphasis"><em>Spirit.Lex</em></span>: This is the library usable to create tokenizers
         (lexers). The domain-specific language exposed by <span class="emphasis"><em>Spirit.Lex</em></span>
 </li>
-<li>
+<li class="listitem">
 <span class="emphasis"><em>Spirit.Karma</em></span>: This is the generator library allowing
         you to create code for recursive descent, data type-driven output formatting.
         The exposed domain-specific language is almost equivalent to the parser description
@@ -103,10 +100,9 @@
       </p>
 <div class="figure">
 <a name="spirit.spiritstructure"></a><p class="title"><b>Figure 1. The overall structure of the Boost Spirit library</b></p>
-<span class="inlinemediaobject"><img src="./images/spiritstructure.png" alt="The
- overall structure of the Boost Spirit library"></span>
+<div class="figure-contents"><span class="inlinemediaobject"><img src=".././images/spiritstructure.png" alt="The overall structure of the Boost Spirit library"></span></div>
 </div>
-<p>
+<p><br class="figure-break">
     </p>
 <p>
       The separate sublibraries <span class="emphasis"><em>Spirit.Qi</em></span>, <span class="emphasis"><em>Spirit.Karma</em></span>
@@ -119,8 +115,7 @@
       the input for a parser generated by <span class="emphasis"><em>Spirit.Qi</em></span>.
     </p>
 <p>
- The <a href="introduction.html#spirit.spiritkarmaflow" title="Figure 2. The place of Spirit.Qi and Spirit.Karma
- in a data transformation flow of a typical application">figure</a> below shows the typical
+ The <a class="link" href="introduction.html#spirit.spiritkarmaflow" title="Figure 2. The place of Spirit.Qi and Spirit.Karma in a data transformation flow of a typical application">figure</a> below shows the typical
       data flow of some input being converted to some internal representation. After
       some (optional) transformation these data are converted back into some different,
       external representation. The picture highlights Spirit's place in this data
@@ -131,17 +126,15 @@
 <div class="figure">
 <a name="spirit.spiritkarmaflow"></a><p class="title"><b>Figure 2. The place of <span class="emphasis"><em>Spirit.Qi</em></span> and <span class="emphasis"><em>Spirit.Karma</em></span>
       in a data transformation flow of a typical application</b></p>
-<span class="inlinemediaobject"><img src="./images/spiritkarmaflow.png" alt="The
- place of Spirit.Qi and Spirit.Karma
- in a data transformation flow of a typical application"></span>
+<div class="figure-contents"><span class="inlinemediaobject"><img src=".././images/spiritkarmaflow.png" alt="The place of Spirit.Qi and Spirit.Karma in a data transformation flow of a typical application"></span></div>
 </div>
-<p>
+<p><br class="figure-break">
     </p>
-<a name="spirit.introduction.a_quick_overview_of_parsing_with__emphasis_spirit_qi__emphasis_"></a><h3>
-<a name="id411183"></a>
- <a href="introduction.html#spirit.introduction.a_quick_overview_of_parsing_with__emphasis_spirit_qi__emphasis_">A
+<a name="spirit.introduction.a_quick_overview_of_parsing_with__emphasis_spirit_qi__emphasis_"></a><h4>
+<a name="id1023288"></a>
+ <a class="link" href="introduction.html#spirit.introduction.a_quick_overview_of_parsing_with__emphasis_spirit_qi__emphasis_">A
       Quick Overview of Parsing with <span class="emphasis"><em>Spirit.Qi</em></span></a>
- </h3>
+ </h4>
 <p>
       <span class="emphasis"><em>Spirit.Qi</em></span> is Spirit's sublibrary dealing with generating
       parsers based on a given target grammar (essentially a format description of
@@ -166,14 +159,14 @@
 </pre>
 <p>
       Through the magic of expression templates, this is perfectly valid and executable
- C++ code. The production rule <tt class="computeroutput"><span class="identifier">expression</span></tt>
- is, in fact, an object that has a member function <tt class="computeroutput"><span class="identifier">parse</span></tt>
+ C++ code. The production rule <code class="computeroutput"><span class="identifier">expression</span></code>
+ is, in fact, an object that has a member function <code class="computeroutput"><span class="identifier">parse</span></code>
       that does the work given a source code written in the grammar that we have
       just declared. Yes, it's a calculator. We shall simplify for now by skipping
- the type declarations and the definition of the rule <tt class="computeroutput"><span class="identifier">integer</span></tt>
- invoked by <tt class="computeroutput"><span class="identifier">factor</span></tt>. Now, the
- production rule <tt class="computeroutput"><span class="identifier">expression</span></tt>
- in our grammar specification, traditionally called the <tt class="computeroutput"><span class="identifier">start</span></tt>
+ the type declarations and the definition of the rule <code class="computeroutput"><span class="identifier">integer</span></code>
+ invoked by <code class="computeroutput"><span class="identifier">factor</span></code>. Now, the
+ production rule <code class="computeroutput"><span class="identifier">expression</span></code>
+ in our grammar specification, traditionally called the <code class="computeroutput"><span class="identifier">start</span></code>
       symbol, can recognize inputs such as:
     </p>
 <pre class="programlisting"><span class="number">12345</span>
@@ -200,19 +193,19 @@
 <p>
       as seen in math syntax, for example, to mean multiplication or, in our case,
       as seen in EBNF syntax to mean sequencing (b should follow a). Spirit uses
- the shift <tt class="computeroutput"><span class="special">&gt;&gt;</span></tt> operator instead
- for this purpose. We take the <tt class="computeroutput"><span class="special">&gt;&gt;</span></tt>
+ the shift <code class="computeroutput"><span class="special">&gt;&gt;</span></code> operator instead
+ for this purpose. We take the <code class="computeroutput"><span class="special">&gt;&gt;</span></code>
       operator, with arrows pointing to the right, to mean "is followed by".
       Thus we write:
     </p>
 <pre class="programlisting"><span class="identifier">a</span> <span class="special">&gt;&gt;</span> <span class="identifier">b</span>
 </pre>
 <p>
- The alternative operator <tt class="computeroutput"><span class="special">|</span></tt> and
- the parentheses <tt class="computeroutput"><span class="special">()</span></tt> remain as is.
- The assignment operator <tt class="computeroutput"><span class="special">=</span></tt> is used
- in place of EBNF's <tt class="computeroutput"><span class="special">::=</span></tt>. Last but
- not least, the Kleene star <tt class="computeroutput"><span class="special">*</span></tt> which
+ The alternative operator <code class="computeroutput"><span class="special">|</span></code> and
+ the parentheses <code class="computeroutput"><span class="special">()</span></code> remain as is.
+ The assignment operator <code class="computeroutput"><span class="special">=</span></code> is used
+ in place of EBNF's <code class="computeroutput"><span class="special">::=</span></code>. Last but
+ not least, the Kleene star <code class="computeroutput"><span class="special">*</span></code> which
       used to be a postfix operator in EBNF becomes a prefix. Instead of:
     </p>
 <pre class="programlisting"><span class="identifier">a</span><span class="special">*</span> <span class="comment">//... in EBNF syntax,
@@ -223,15 +216,15 @@
 <pre class="programlisting"><span class="special">*</span><span class="identifier">a</span> <span class="comment">//... in Spirit.
 </span></pre>
 <p>
- since there are no postfix stars, <tt class="computeroutput"><span class="special">*</span></tt>,
+ since there are no postfix stars, <code class="computeroutput"><span class="special">*</span></code>,
       in C/C++. Finally, we terminate each rule with the ubiquitous semi-colon,
- <tt class="computeroutput"><span class="special">;</span></tt>.
+ <code class="computeroutput"><span class="special">;</span></code>.
     </p>
-<a name="spirit.introduction.a_quick_overview_of_output_generation_with__emphasis_spirit_karma__emphasis_"></a><h3>
-<a name="id412390"></a>
- <a href="introduction.html#spirit.introduction.a_quick_overview_of_output_generation_with__emphasis_spirit_karma__emphasis_">A
+<a name="spirit.introduction.a_quick_overview_of_output_generation_with__emphasis_spirit_karma__emphasis_"></a><h4>
+<a name="id1024241"></a>
+ <a class="link" href="introduction.html#spirit.introduction.a_quick_overview_of_output_generation_with__emphasis_spirit_karma__emphasis_">A
       Quick Overview of Output Generation with <span class="emphasis"><em>Spirit.Karma</em></span></a>
- </h3>
+ </h4>
 <p>
       Spirit not only allows you to describe the structure of the input. Starting
       with Version 2.0 it enables the specification of the output format for your
@@ -239,7 +232,7 @@
     </p>
 <p>
       Let's assume we need to generate a textual representation from a simple data
- structure such as a <tt class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">vector</span><span class="special">&lt;</span><span class="keyword">int</span><span class="special">&gt;</span></tt>. Conventional
+ structure such as a <code class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">vector</span><span class="special">&lt;</span><span class="keyword">int</span><span class="special">&gt;</span></code>. Conventional
       code probably would look like:
     </p>
 <pre class="programlisting"><span class="identifier">std</span><span class="special">::</span><span class="identifier">vector</span><span class="special">&lt;</span><span class="keyword">int</span><span class="special">&gt;</span> <span class="identifier">v</span> <span class="special">(</span><span class="identifier">initialize_and_fill</span><span class="special">());</span>
@@ -258,84 +251,114 @@
 </pre>
 <p>
       Here are some more examples of format descriptions for different output representations
- of the same <tt class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">vector</span><span class="special">&lt;</span><span class="keyword">int</span><span class="special">&gt;</span></tt>:
+ of the same <code class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">vector</span><span class="special">&lt;</span><span class="keyword">int</span><span class="special">&gt;</span></code>:
     </p>
 <div class="table">
-<a name="id412827"></a><p class="title"><b>Table 2. Different output formats for `std::vector&lt;int&gt;`</b></p>
-<table class="table" summary="Different output formats for `std::vector&lt;int&gt;`">
+<a name="id1024582"></a><p class="title"><b>Table 2. Different output formats for `std::vector&lt;int&gt;`</b></p>
+<div class="table-contents"><table class="table" summary="Different output formats for `std::vector&lt;int&gt;`">
 <colgroup>
 <col>
 <col>
 <col>
 </colgroup>
 <thead><tr>
-<th><p>
+<th>
+ <p>
             Format
- </p></th>
-<th><p>
+ </p>
+ </th>
+<th>
+ <p>
             Example
- </p></th>
-<th><p>
+ </p>
+ </th>
+<th>
+ <p>
             Description
- </p></th>
+ </p>
+ </th>
 </tr></thead>
 <tbody>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="char">'['</span> <span class="special">&lt;&lt;</span>
+<td>
+ <p>
+ <code class="computeroutput"><span class="char">'['</span> <span class="special">&lt;&lt;</span>
             <span class="special">*(</span><span class="identifier">int_</span>
- <span class="special">&lt;&lt;</span> <span class="char">','</span><span class="special">)</span> <span class="special">&lt;&lt;</span> <span class="char">']'</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="special">[</span><span class="number">1</span><span class="special">,</span><span class="number">8</span><span class="special">,</span><span class="number">10</span><span class="special">,]</span></tt>
- </p></td>
-<td><p>
+ <span class="special">&lt;&lt;</span> <span class="char">','</span><span class="special">)</span> <span class="special">&lt;&lt;</span> <span class="char">']'</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="special">[</span><span class="number">1</span><span class="special">,</span><span class="number">8</span><span class="special">,</span><span class="number">10</span><span class="special">,]</span></code>
+ </p>
+ </td>
+<td>
+ <p>
             Comma separated list of integers
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="special">*(</span><span class="char">'('</span>
+<td>
+ <p>
+ <code class="computeroutput"><span class="special">*(</span><span class="char">'('</span>
             <span class="special">&lt;&lt;</span> <span class="identifier">int_</span>
             <span class="special">&lt;&lt;</span> <span class="char">')'</span>
- <span class="special">&lt;&lt;</span> <span class="char">','</span><span class="special">)</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="special">(</span><span class="number">1</span><span class="special">),(</span><span class="number">8</span><span class="special">),(</span><span class="number">10</span><span class="special">),]</span></tt>
- </p></td>
-<td><p>
+ <span class="special">&lt;&lt;</span> <span class="char">','</span><span class="special">)</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="special">(</span><span class="number">1</span><span class="special">),(</span><span class="number">8</span><span class="special">),(</span><span class="number">10</span><span class="special">),]</span></code>
+ </p>
+ </td>
+<td>
+ <p>
             Comma separated list of integers in parenthesis
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="special">*</span><span class="identifier">hex</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="number">18</span><span class="identifier">a</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="special">*</span><span class="identifier">hex</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="number">18</span><span class="identifier">a</span></code>
+ </p>
+ </td>
+<td>
+ <p>
             A list of hexadecimal numbers
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="special">*(</span><span class="identifier">double_</span>
- <span class="special">&lt;&lt;</span> <span class="char">','</span><span class="special">)</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="number">1.0</span><span class="special">,</span><span class="number">8.0</span><span class="special">,</span><span class="number">10.0</span><span class="special">,</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="special">*(</span><span class="identifier">double_</span>
+ <span class="special">&lt;&lt;</span> <span class="char">','</span><span class="special">)</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="number">1.0</span><span class="special">,</span><span class="number">8.0</span><span class="special">,</span><span class="number">10.0</span><span class="special">,</span></code>
+ </p>
+ </td>
+<td>
+ <p>
             A list of floating point numbers
- </p></td>
+ </p>
+ </td>
 </tr>
 </tbody>
-</table>
+</table></div>
 </div>
-<p>
+<br class="table-break"><p>
       The syntax is similar to <span class="emphasis"><em>Qi</em></span> with the exception that we
- use the <tt class="computeroutput"><span class="special">&lt;&lt;</span></tt> operator for
+ use the <code class="computeroutput"><span class="special">&lt;&lt;</span></code> operator for
       output concatenation. This should be easy to understand as it follows the conventions
       used in the Standard's I/O streams.
     </p>
@@ -346,59 +369,77 @@
       next table gives some related examples.
     </p>
 <div class="table">
-<a name="id413273"></a><p class="title"><b>Table 3. Different data types usable with the output format
+<a name="id1026048"></a><p class="title"><b>Table 3. Different data types usable with the output format
     `*(int_ &lt;&lt; eol)`</b></p>
-<table class="table" summary="Different data types usable with the output format
+<div class="table-contents"><table class="table" summary="Different data types usable with the output format
     `*(int_ &lt;&lt; eol)`">
 <colgroup>
 <col>
 <col>
 </colgroup>
 <thead><tr>
-<th><p>
+<th>
+ <p>
             Data type
- </p></th>
+ </p>
+ </th>
 <td class="auto-generated"> </td>
 </tr></thead>
 <tbody>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="keyword">int</span> <span class="identifier">i</span><span class="special">[</span><span class="number">4</span><span class="special">]</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="keyword">int</span> <span class="identifier">i</span><span class="special">[</span><span class="number">4</span><span class="special">]</span></code>
+ </p>
+ </td>
+<td>
+ <p>
             C style arrays
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">vector</span><span class="special">&lt;</span><span class="keyword">int</span><span class="special">&gt;</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">vector</span><span class="special">&lt;</span><span class="keyword">int</span><span class="special">&gt;</span></code>
+ </p>
+ </td>
+<td>
+ <p>
             Standard vector
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">list</span><span class="special">&lt;</span><span class="keyword">int</span><span class="special">&gt;</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">list</span><span class="special">&lt;</span><span class="keyword">int</span><span class="special">&gt;</span></code>
+ </p>
+ </td>
+<td>
+ <p>
             Standard list
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">boost</span><span class="special">::</span><span class="identifier">array</span><span class="special">&lt;</span><span class="keyword">long</span><span class="special">,</span> <span class="number">20</span><span class="special">&gt;</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">boost</span><span class="special">::</span><span class="identifier">array</span><span class="special">&lt;</span><span class="keyword">long</span><span class="special">,</span> <span class="number">20</span><span class="special">&gt;</span></code>
+ </p>
+ </td>
+<td>
+ <p>
             Boost array
- </p></td>
+ </p>
+ </td>
 </tr>
 </tbody>
-</table>
+</table></div>
 </div>
-<div class="footnotes">
+<br class="table-break"><div class="footnotes">
 <br><hr width="100" align="left">
-<div class="footnote"><p><sup>[<a name="ftn.id410902" href="#id410902">1</a>] </sup>
+<div class="footnote"><p><sup>[<a name="ftn.id1023075" href="#id1023075" class="para">1</a>] </sup>
           <a href="http://www.cl.cam.ac.uk/%7Emgk25/iso-14977.pdf" target="_top">ISO-EBNF</a>
         </p></div>
 </div>

Modified: trunk/libs/spirit/doc/html/spirit/karma.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/karma.html (original)
+++ trunk/libs/spirit/doc/html/spirit/karma.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -1,12 +1,12 @@
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title> Karma</title>
+<title>Karma</title>
 <link rel="stylesheet" href="../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../index.html" title="Spirit 2.1">
 <link rel="up" href="../index.html" title="Spirit 2.1">
-<link rel="previous" href="qi/reference/string/symbols.html" title="symbols">
+<link rel="prev" href="qi/string/symbols.html" title="symbols">
 <link rel="next" href="karma/tutorials.html" title="Tutorials">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -20,15 +20,12 @@
 </tr></table>
 <hr>
 <div class="spirit-nav">
-<a accesskey="p" href="qi/reference/string/symbols.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/tutorials.html"><img src="../../../../../doc/html/images/next.png" alt="Next"></a>
-</div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h2 class="title" style="clear: both">
-<a name="spirit.karma"></a> Karma
-</h2></div></div>
-<div></div>
+<a accesskey="p" href="qi/string/symbols.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/tutorials.html"><img src="../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
+<div class="section" title="Karma">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="spirit.karma"></a><a class="link" href="karma.html" title="Karma"> Karma</a>
+</h2></div></div></div>
 <div class="toc"><dl>
 <dt><span class="section">Tutorials</span></dt>
 <dd><dl>
@@ -68,7 +65,7 @@
 </tr></table>
 <hr>
 <div class="spirit-nav">
-<a accesskey="p" href="qi/reference/string/symbols.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/tutorials.html"><img src="../../../../../doc/html/images/next.png" alt="Next"></a>
+<a accesskey="p" href="qi/string/symbols.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/tutorials.html"><img src="../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
 </body>
 </html>

Modified: trunk/libs/spirit/doc/html/spirit/karma/quick_reference.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/karma/quick_reference.html (original)
+++ trunk/libs/spirit/doc/html/spirit/karma/quick_reference.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -3,13 +3,11 @@
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <title>Quick Reference</title>
 <link rel="stylesheet" href="../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../index.html" title="Spirit 2.1">
-<link rel="up" href="../karma.html" title=" Karma">
-<link rel="previous" href="tutorials/complex___a_first_more_complex_generator.html" title="Complex
- - A first more complex generator">
-<link rel="next" href="quick_reference/common_notation.html" title="Common
- Notation">
+<link rel="up" href="../karma.html" title="Karma">
+<link rel="prev" href="tutorials/complex___a_first_more_complex_generator.html" title="Complex - A first more complex generator">
+<link rel="next" href="quick_reference/common_notation.html" title="Common Notation">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
 <table cellpadding="2" width="100%"><tr>
@@ -24,13 +22,10 @@
 <div class="spirit-nav">
 <a accesskey="p" href="tutorials/complex___a_first_more_complex_generator.html"><img src="../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../karma.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="quick_reference/common_notation.html"><img src="../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h3 class="title">
-<a name="spirit.karma.quick_reference"></a>Quick Reference
-</h3></div></div>
-<div></div>
-</div>
+<div class="section" title="Quick Reference">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="spirit.karma.quick_reference"></a><a class="link" href="quick_reference.html" title="Quick Reference">Quick Reference</a>
+</h3></div></div></div>
 <div class="toc"><dl>
 <dt><span class="section"><a href="quick_reference/common_notation.html">Common
         Notation</a></span></dt>

Modified: trunk/libs/spirit/doc/html/spirit/karma/quick_reference/common_notation.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/karma/quick_reference/common_notation.html (original)
+++ trunk/libs/spirit/doc/html/spirit/karma/quick_reference/common_notation.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -1,15 +1,13 @@
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title>Common
- Notation</title>
+<title>Common Notation</title>
 <link rel="stylesheet" href="../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../index.html" title="Spirit 2.1">
 <link rel="up" href="../quick_reference.html" title="Quick Reference">
-<link rel="previous" href="../quick_reference.html" title="Quick Reference">
-<link rel="next" href="predefined_primitive_generators.html" title="Predefined
- Primitive Generators">
+<link rel="prev" href="../quick_reference.html" title="Quick Reference">
+<link rel="next" href="predefined_primitive_generators.html" title="Predefined Primitive Generators">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
 <table cellpadding="2" width="100%"><tr>
@@ -24,109 +22,105 @@
 <div class="spirit-nav">
 <a accesskey="p" href="../quick_reference.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../quick_reference.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="predefined_primitive_generators.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h4 class="title">
-<a name="spirit.karma.quick_reference.common_notation"></a><a href="common_notation.html" title="Common
- Notation">Common
+<div class="section" title="Common Notation">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="spirit.karma.quick_reference.common_notation"></a><a class="link" href="common_notation.html" title="Common Notation">Common
         Notation</a>
-</h4></div></div>
-<div></div>
-</div>
-<div class="variablelist">
+</h4></div></div></div>
+<div class="variablelist" title="Notation">
 <p class="title"><b>Notation</b></p>
 <dl>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">G</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">G</span></code></span></dt>
 <dd><p>
               Generator type
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">g</span><span class="special">,</span> <span class="identifier">a</span><span class="special">,</span>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">g</span><span class="special">,</span> <span class="identifier">a</span><span class="special">,</span>
           <span class="identifier">b</span><span class="special">,</span>
- <span class="identifier">c</span></tt></span></dt>
+ <span class="identifier">c</span></code></span></dt>
 <dd><p>
               Generator objects
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">A</span><span class="special">,</span> <span class="identifier">B</span><span class="special">,</span>
- <span class="identifier">C</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">A</span><span class="special">,</span> <span class="identifier">B</span><span class="special">,</span>
+ <span class="identifier">C</span></code></span></dt>
 <dd><p>
               Attribute types of generators A, B and C
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">I</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">I</span></code></span></dt>
 <dd><p>
               The iterator type used for generation
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">Unused</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">Unused</span></code></span></dt>
 <dd><p>
- An <tt class="computeroutput"><span class="identifier">unused_type</span></tt>
+ An <code class="computeroutput"><span class="identifier">unused_type</span></code>
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">Context</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">Context</span></code></span></dt>
 <dd><p>
- The enclosing rule's <tt class="computeroutput"><span class="identifier">Context</span></tt>
+ The enclosing rule's <code class="computeroutput"><span class="identifier">Context</span></code>
               type
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">Attr</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">Attr</span></code></span></dt>
 <dd><p>
               An attribute type
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">b</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">b</span></code></span></dt>
 <dd><p>
               A boolean expression
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">fg</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">fg</span></code></span></dt>
 <dd><p>
- A (lazy generator) function with signature <tt class="computeroutput"><span class="identifier">G</span><span class="special">(</span><span class="identifier">Unused</span><span class="special">,</span> <span class="identifier">Context</span><span class="special">)</span></tt>
+ A (lazy generator) function with signature <code class="computeroutput"><span class="identifier">G</span><span class="special">(</span><span class="identifier">Unused</span><span class="special">,</span> <span class="identifier">Context</span><span class="special">)</span></code>
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">fa</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">fa</span></code></span></dt>
 <dd><p>
- A (semantic action) function with signature <tt class="computeroutput"><span class="keyword">void</span><span class="special">(</span><span class="identifier">Attr</span><span class="special">&amp;,</span> <span class="identifier">Context</span><span class="special">,</span> <span class="keyword">bool</span><span class="special">&amp;)</span></tt>. The third parameter is a boolean
+ A (semantic action) function with signature <code class="computeroutput"><span class="keyword">void</span><span class="special">(</span><span class="identifier">Attr</span><span class="special">&amp;,</span> <span class="identifier">Context</span><span class="special">,</span> <span class="keyword">bool</span><span class="special">&amp;)</span></code>. The third parameter is a boolean
               flag that can be set to false to force the generator to fail. Both
- <tt class="computeroutput"><span class="identifier">Context</span></tt> and the boolean
+ <code class="computeroutput"><span class="identifier">Context</span></code> and the boolean
               flag are optional.
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">outiter</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">outiter</span></code></span></dt>
 <dd><p>
               An output iterator to receive the generated output
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">Ch</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">Ch</span></code></span></dt>
 <dd><p>
               Character-class specific character type (See __char_class<span class="underline">types</span>_)
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">ch</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">ch</span></code></span></dt>
 <dd><p>
               Character-class specific character (See __char_class<span class="underline">types</span>_)
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">ch2</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">ch2</span></code></span></dt>
 <dd><p>
               Character-class specific character (See __char_class<span class="underline">types</span>_)
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">chset</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">chset</span></code></span></dt>
 <dd><p>
               Character-set specifier string (example: "a-z0-9")
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">str</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">str</span></code></span></dt>
 <dd><p>
               Character-class specific string (See __char_class<span class="underline">types</span>_)
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">Str</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">Str</span></code></span></dt>
 <dd><p>
- Attribute of <tt class="computeroutput"><span class="identifier">str</span></tt>:
- <tt class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">basic_string</span><span class="special">&lt;</span><span class="identifier">T</span><span class="special">&gt;</span></tt>
- where <tt class="computeroutput"><span class="identifier">T</span></tt> is the underlying
- character type of <tt class="computeroutput"><span class="identifier">str</span></tt>
+ Attribute of <code class="computeroutput"><span class="identifier">str</span></code>:
+ <code class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">basic_string</span><span class="special">&lt;</span><span class="identifier">T</span><span class="special">&gt;</span></code>
+ where <code class="computeroutput"><span class="identifier">T</span></code> is the underlying
+ character type of <code class="computeroutput"><span class="identifier">str</span></code>
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">tuple</span><span class="special">&lt;&gt;</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">tuple</span><span class="special">&lt;&gt;</span></code></span></dt>
 <dd><p>
               Used as a placeholder for a fusion sequence
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">vector</span><span class="special">&lt;&gt;</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">vector</span><span class="special">&lt;&gt;</span></code></span></dt>
 <dd><p>
               Used as a placeholder for an STL container
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">variant</span><span class="special">&lt;&gt;</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">variant</span><span class="special">&lt;&gt;</span></code></span></dt>
 <dd><p>
               Used as a placeholder for a boost::variant
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">optional</span><span class="special">&lt;&gt;</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">optional</span><span class="special">&lt;&gt;</span></code></span></dt>
 <dd><p>
               Used as a placeholder for a boost::optional
             </p></dd>

Modified: trunk/libs/spirit/doc/html/spirit/karma/quick_reference/compound_attribute_rules.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/karma/quick_reference/compound_attribute_rules.html (original)
+++ trunk/libs/spirit/doc/html/spirit/karma/quick_reference/compound_attribute_rules.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -1,14 +1,12 @@
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title>Compound
- Attribute Rules</title>
+<title>Compound Attribute Rules</title>
 <link rel="stylesheet" href="../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../index.html" title="Spirit 2.1">
 <link rel="up" href="../quick_reference.html" title="Quick Reference">
-<link rel="previous" href="predefined_primitive_generators.html" title="Predefined
- Primitive Generators">
+<link rel="prev" href="predefined_primitive_generators.html" title="Predefined Primitive Generators">
 <link rel="next" href="lazy_arguments.html" title="Lazy Arguments">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -24,50 +22,52 @@
 <div class="spirit-nav">
 <a accesskey="p" href="predefined_primitive_generators.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../quick_reference.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="lazy_arguments.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h4 class="title">
-<a name="spirit.karma.quick_reference.compound_attribute_rules"></a><a href="compound_attribute_rules.html" title="Compound
- Attribute Rules">Compound
+<div class="section" title="Compound Attribute Rules">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="spirit.karma.quick_reference.compound_attribute_rules"></a><a class="link" href="compound_attribute_rules.html" title="Compound Attribute Rules">Compound
         Attribute Rules</a>
-</h4></div></div>
-<div></div>
-</div>
+</h4></div></div></div>
 <p>
           The notation will be for instance:
         </p>
 <pre class="programlisting"><span class="identifier">a</span><span class="special">:</span> <span class="identifier">A</span><span class="special">,</span> <span class="identifier">b</span><span class="special">:</span> <span class="identifier">B</span> <span class="special">--&gt;</span> <span class="special">(</span><span class="identifier">a</span> <span class="special">&lt;&lt;</span> <span class="identifier">b</span><span class="special">):</span> <span class="identifier">tuple</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">,</span> <span class="identifier">B</span><span class="special">&gt;</span>
 </pre>
 <p>
- which reads as: given, <tt class="computeroutput"><span class="identifier">a</span></tt>
- and <tt class="computeroutput"><span class="identifier">b</span></tt> are generators, and
- <tt class="computeroutput"><span class="identifier">A</span></tt> is the type of the attribute
- of <tt class="computeroutput"><span class="identifier">a</span></tt>, and <tt class="computeroutput"><span class="identifier">B</span></tt> is the type of the attribute of <tt class="computeroutput"><span class="identifier">b</span></tt>, then the type of the attribute of
- <tt class="computeroutput"><span class="identifier">a</span> <span class="special">&lt;&lt;</span>
- <span class="identifier">b</span></tt> will be <tt class="computeroutput"><span class="identifier">tuple</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">,</span> <span class="identifier">B</span><span class="special">&gt;</span></tt>.
+ which reads as: given, <code class="computeroutput"><span class="identifier">a</span></code>
+ and <code class="computeroutput"><span class="identifier">b</span></code> are generators, and
+ <code class="computeroutput"><span class="identifier">A</span></code> is the type of the attribute
+ of <code class="computeroutput"><span class="identifier">a</span></code>, and <code class="computeroutput"><span class="identifier">B</span></code> is the type of the attribute of <code class="computeroutput"><span class="identifier">b</span></code>, then the type of the attribute of
+ <code class="computeroutput"><span class="identifier">a</span> <span class="special">&lt;&lt;</span>
+ <span class="identifier">b</span></code> will be <code class="computeroutput"><span class="identifier">tuple</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">,</span> <span class="identifier">B</span><span class="special">&gt;</span></code>.
         </p>
 <div class="table">
-<a name="id472176"></a><p class="title"><b>Table 5. Spirit.Karma compound generator attribute types</b></p>
-<table class="table" summary="Spirit.Karma compound generator attribute types">
+<a name="id1083158"></a><p class="title"><b>Table 5. Spirit.Karma compound generator attribute types</b></p>
+<div class="table-contents"><table class="table" summary="Spirit.Karma compound generator attribute types">
 <colgroup>
 <col>
 <col>
 </colgroup>
 <thead><tr>
-<th><p>
+<th>
+ <p>
                 Expression
- </p></th>
-<th><p>
+ </p>
+ </th>
+<th>
+ <p>
                 Attribute
- </p></th>
+ </p>
+ </th>
 </tr></thead>
 <tbody>
 <tr>
-<td><p>
- sequence (<tt class="computeroutput"><span class="special">&lt;&lt;</span></tt>)
- </p></td>
 <td>
-<p>
+ <p>
+ sequence (<code class="computeroutput"><span class="special">&lt;&lt;</span></code>)
+ </p>
+ </td>
+<td>
+ <p>
                 
 </p>
 <pre class="programlisting"><span class="identifier">a</span><span class="special">:</span> <span class="identifier">A</span><span class="special">,</span> <span class="identifier">b</span><span class="special">:</span> <span class="identifier">B</span> <span class="special">--&gt;</span> <span class="special">(</span><span class="identifier">a</span> <span class="special">&lt;&lt;</span> <span class="identifier">b</span><span class="special">):</span> <span class="identifier">tuple</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">,</span> <span class="identifier">B</span><span class="special">&gt;</span>
@@ -77,14 +77,16 @@
 <span class="identifier">a</span><span class="special">:</span> <span class="identifier">A</span><span class="special">,</span> <span class="identifier">b</span><span class="special">:</span> <span class="identifier">A</span> <span class="special">--&gt;</span> <span class="special">(</span><span class="identifier">a</span> <span class="special">&lt;&lt;</span> <span class="identifier">b</span><span class="special">):</span> <span class="identifier">vector</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">&gt;</span></pre>
 <p>
               </p>
-</td>
+ </td>
 </tr>
 <tr>
-<td><p>
- alternative (<tt class="computeroutput"><span class="special">|</span></tt>)
- </p></td>
 <td>
-<p>
+ <p>
+ alternative (<code class="computeroutput"><span class="special">|</span></code>)
+ </p>
+ </td>
+<td>
+ <p>
                 
 </p>
 <pre class="programlisting"><span class="identifier">a</span><span class="special">:</span> <span class="identifier">A</span><span class="special">,</span> <span class="identifier">b</span><span class="special">:</span> <span class="identifier">B</span> <span class="special">--&gt;</span> <span class="special">(</span><span class="identifier">a</span> <span class="special">|</span> <span class="identifier">b</span><span class="special">):</span> <span class="identifier">variant</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">,</span> <span class="identifier">B</span><span class="special">&gt;</span>
@@ -94,101 +96,120 @@
 <span class="identifier">a</span><span class="special">:</span> <span class="identifier">A</span><span class="special">,</span> <span class="identifier">b</span><span class="special">:</span> <span class="identifier">A</span> <span class="special">--&gt;</span> <span class="special">(</span><span class="identifier">a</span> <span class="special">|</span> <span class="identifier">b</span><span class="special">):</span> <span class="identifier">A</span></pre>
 <p>
               </p>
-</td>
+ </td>
 </tr>
 <tr>
-<td><p>
- kleene (<tt class="computeroutput"><span class="special">*</span></tt>)
- </p></td>
 <td>
-<p>
+ <p>
+ kleene (<code class="computeroutput"><span class="special">*</span></code>)
+ </p>
+ </td>
+<td>
+ <p>
                 
 </p>
 <pre class="programlisting"><span class="identifier">a</span><span class="special">:</span> <span class="identifier">A</span> <span class="special">--&gt;</span> <span class="special">*</span><span class="identifier">a</span><span class="special">:</span> <span class="identifier">vector</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">&gt;</span>
 <span class="identifier">a</span><span class="special">:</span> <span class="identifier">Unused</span> <span class="special">--&gt;</span> <span class="identifier">a</span><span class="special">:</span> <span class="identifier">Unused</span></pre>
 <p>
               </p>
-</td>
+ </td>
 </tr>
 <tr>
-<td><p>
- plus (<tt class="computeroutput"><span class="special">+</span></tt>)
- </p></td>
 <td>
-<p>
+ <p>
+ plus (<code class="computeroutput"><span class="special">+</span></code>)
+ </p>
+ </td>
+<td>
+ <p>
                 
 </p>
 <pre class="programlisting"><span class="identifier">a</span><span class="special">:</span> <span class="identifier">A</span> <span class="special">--&gt;</span> <span class="special">+</span><span class="identifier">a</span><span class="special">:</span> <span class="identifier">vector</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">&gt;</span>
 <span class="identifier">a</span><span class="special">:</span> <span class="identifier">Unused</span> <span class="special">--&gt;</span> <span class="identifier">a</span><span class="special">:</span> <span class="identifier">Unused</span></pre>
 <p>
               </p>
-</td>
+ </td>
 </tr>
 <tr>
-<td><p>
- list (<tt class="computeroutput"><span class="special">%</span></tt>)
- </p></td>
 <td>
-<p>
+ <p>
+ list (<code class="computeroutput"><span class="special">%</span></code>)
+ </p>
+ </td>
+<td>
+ <p>
                 
 </p>
 <pre class="programlisting"><span class="identifier">a</span><span class="special">:</span> <span class="identifier">A</span><span class="special">,</span> <span class="identifier">b</span><span class="special">:</span> <span class="identifier">B</span> <span class="special">--&gt;</span> <span class="special">(</span><span class="identifier">a</span> <span class="special">%</span> <span class="identifier">b</span><span class="special">):</span> <span class="identifier">vector</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">&gt;</span>
 <span class="identifier">a</span><span class="special">:</span> <span class="identifier">Unused</span><span class="special">,</span> <span class="identifier">b</span><span class="special">:</span> <span class="identifier">B</span> <span class="special">--&gt;</span> <span class="special">(</span><span class="identifier">a</span> <span class="special">%</span> <span class="identifier">b</span><span class="special">):</span> <span class="identifier">Unused</span></pre>
 <p>
               </p>
-</td>
+ </td>
 </tr>
 <tr>
-<td><p>
+<td>
+ <p>
                 repetition
- </p></td>
+ </p>
+ </td>
 <td>
-<p>
+ <p>
                 
 </p>
 <pre class="programlisting"><span class="identifier">a</span><span class="special">:</span> <span class="identifier">A</span> <span class="special">--&gt;</span> <span class="identifier">repeat</span><span class="special">(...,...)[</span><span class="identifier">a</span><span class="special">]:</span> <span class="identifier">vector</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">&gt;</span>
 <span class="identifier">a</span><span class="special">:</span> <span class="identifier">Unused</span> <span class="special">--&gt;</span> <span class="identifier">repeat</span><span class="special">(...,...)[</span><span class="identifier">a</span><span class="special">]:</span> <span class="identifier">Unused</span></pre>
 <p>
               </p>
-</td>
+ </td>
 </tr>
 <tr>
-<td><p>
- optional (<tt class="computeroutput"><span class="special">-</span></tt>)
- </p></td>
 <td>
-<p>
+ <p>
+ optional (<code class="computeroutput"><span class="special">-</span></code>)
+ </p>
+ </td>
+<td>
+ <p>
                 
 </p>
 <pre class="programlisting"><span class="identifier">a</span><span class="special">:</span> <span class="identifier">A</span> <span class="special">--&gt;</span> <span class="special">-</span><span class="identifier">a</span><span class="special">:</span> <span class="identifier">optional</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">&gt;</span>
 <span class="identifier">a</span><span class="special">:</span> <span class="identifier">Unused</span> <span class="special">--&gt;</span> <span class="special">-</span><span class="identifier">a</span><span class="special">:</span> <span class="identifier">Unused</span></pre>
 <p>
               </p>
-</td>
+ </td>
 </tr>
 <tr>
-<td><p>
- and predicate (<tt class="computeroutput"><span class="special">&amp;</span></tt>)
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">a</span><span class="special">:</span>
+<td>
+ <p>
+ and predicate (<code class="computeroutput"><span class="special">&amp;</span></code>)
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">a</span><span class="special">:</span>
                 <span class="identifier">A</span> <span class="special">--&gt;</span>
- <span class="special">&amp;</span><span class="identifier">a</span><span class="special">:</span> <span class="identifier">Unused</span></tt>
- </p></td>
+ <span class="special">&amp;</span><span class="identifier">a</span><span class="special">:</span> <span class="identifier">Unused</span></code>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- not predicate (<tt class="computeroutput"><span class="special">!</span></tt>)
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">a</span><span class="special">:</span>
+<td>
+ <p>
+ not predicate (<code class="computeroutput"><span class="special">!</span></code>)
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">a</span><span class="special">:</span>
                 <span class="identifier">A</span> <span class="special">--&gt;</span>
- <span class="special">!</span><span class="identifier">a</span><span class="special">:</span> <span class="identifier">Unused</span></tt>
- </p></td>
+ <span class="special">!</span><span class="identifier">a</span><span class="special">:</span> <span class="identifier">Unused</span></code>
+ </p>
+ </td>
 </tr>
 </tbody>
-</table>
+</table></div>
 </div>
+<br class="table-break">
 </div>
 <table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
 <td align="left"></td>

Modified: trunk/libs/spirit/doc/html/spirit/karma/quick_reference/lazy_arguments.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/karma/quick_reference/lazy_arguments.html (original)
+++ trunk/libs/spirit/doc/html/spirit/karma/quick_reference/lazy_arguments.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -3,11 +3,10 @@
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <title>Lazy Arguments</title>
 <link rel="stylesheet" href="../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../index.html" title="Spirit 2.1">
 <link rel="up" href="../quick_reference.html" title="Quick Reference">
-<link rel="previous" href="compound_attribute_rules.html" title="Compound
- Attribute Rules">
+<link rel="prev" href="compound_attribute_rules.html" title="Compound Attribute Rules">
 <link rel="next" href="non_terminals.html" title="Non-terminals">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -23,27 +22,24 @@
 <div class="spirit-nav">
 <a accesskey="p" href="compound_attribute_rules.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../quick_reference.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="non_terminals.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h4 class="title">
-<a name="spirit.karma.quick_reference.lazy_arguments"></a>Lazy Arguments
-</h4></div></div>
-<div></div>
-</div>
+<div class="section" title="Lazy Arguments">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="spirit.karma.quick_reference.lazy_arguments"></a><a class="link" href="lazy_arguments.html" title="Lazy Arguments">Lazy Arguments</a>
+</h4></div></div></div>
 <p>
           For all expressions of the form:
         </p>
 <pre class="programlisting"><span class="identifier">g</span><span class="special">(</span><span class="identifier">a1</span><span class="special">,</span> <span class="identifier">a2</span><span class="special">,...</span> <span class="identifier">aN</span><span class="special">)</span>
 </pre>
 <p>
- where <tt class="computeroutput"><span class="identifier">g</span></tt> is a generator,
+ where <code class="computeroutput"><span class="identifier">g</span></code> is a generator,
           each of the arguments (a1...aN) can either be an immediate value, or a
           lazy function with signature:
         </p>
 <pre class="programlisting"><span class="identifier">T</span><span class="special">(</span><span class="identifier">Unused</span><span class="special">,</span> <span class="identifier">Context</span><span class="special">)</span>
 </pre>
 <p>
- where <tt class="computeroutput"><span class="identifier">T</span></tt>, the function's
+ where <code class="computeroutput"><span class="identifier">T</span></code>, the function's
           return value, is compatible with the argument type expected. For example,
           this is a valid expression:
         </p>
@@ -57,8 +53,8 @@
 </span> <span class="comment">// of flag at generation time
 </span></pre>
 <p>
- since <tt class="computeroutput"><span class="identifier">phoenix</span><span class="special">::</span><span class="identifier">ref</span><span class="special">(</span><span class="identifier">f</span><span class="special">)</span></tt> is
- a function that returns a <tt class="computeroutput"><span class="keyword">bool</span></tt>.
+ since <code class="computeroutput"><span class="identifier">phoenix</span><span class="special">::</span><span class="identifier">ref</span><span class="special">(</span><span class="identifier">f</span><span class="special">)</span></code> is
+ a function that returns a <code class="computeroutput"><span class="keyword">bool</span></code>.
         </p>
 </div>
 <table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>

Modified: trunk/libs/spirit/doc/html/spirit/karma/quick_reference/non_terminals.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/karma/quick_reference/non_terminals.html (original)
+++ trunk/libs/spirit/doc/html/spirit/karma/quick_reference/non_terminals.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -3,12 +3,11 @@
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <title>Non-terminals</title>
 <link rel="stylesheet" href="../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../index.html" title="Spirit 2.1">
 <link rel="up" href="../quick_reference.html" title="Quick Reference">
-<link rel="previous" href="lazy_arguments.html" title="Lazy Arguments">
-<link rel="next" href="semantic_actions.html" title="Semantic
- Actions">
+<link rel="prev" href="lazy_arguments.html" title="Lazy Arguments">
+<link rel="next" href="semantic_actions.html" title="Semantic Actions">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
 <table cellpadding="2" width="100%"><tr>
@@ -23,61 +22,58 @@
 <div class="spirit-nav">
 <a accesskey="p" href="lazy_arguments.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../quick_reference.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="semantic_actions.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h4 class="title">
-<a name="spirit.karma.quick_reference.non_terminals"></a>Non-terminals
-</h4></div></div>
-<div></div>
-</div>
-<div class="variablelist">
+<div class="section" title="Non-terminals">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="spirit.karma.quick_reference.non_terminals"></a><a class="link" href="non_terminals.html" title="Non-terminals">Non-terminals</a>
+</h4></div></div></div>
+<div class="variablelist" title="Notation">
 <p class="title"><b>Notation</b></p>
 <dl>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">RT</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">RT</span></code></span></dt>
 <dd><p>
               Synthesized attribute. The rule or grammar's return type.
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">Arg1</span></tt>,
- <tt class="computeroutput"><span class="identifier">Arg2</span></tt>, <tt class="computeroutput"><span class="identifier">ArgN</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">Arg1</span></code>,
+ <code class="computeroutput"><span class="identifier">Arg2</span></code>, <code class="computeroutput"><span class="identifier">ArgN</span></code></span></dt>
 <dd><p>
               Inherited attributes. Zero or more or arguments.
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">L1</span></tt>,
- <tt class="computeroutput"><span class="identifier">L2</span></tt>, <tt class="computeroutput"><span class="identifier">LN</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">L1</span></code>,
+ <code class="computeroutput"><span class="identifier">L2</span></code>, <code class="computeroutput"><span class="identifier">LN</span></code></span></dt>
 <dd><p>
               Zero or more local variables.
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">r</span><span class="special">,</span> <span class="identifier">r2</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">r</span><span class="special">,</span> <span class="identifier">r2</span></code></span></dt>
 <dd><p>
               Rules
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">g</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">g</span></code></span></dt>
 <dd><p>
               A grammar
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">p</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">p</span></code></span></dt>
 <dd><p>
               A parser expression
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">my_grammar</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">my_grammar</span></code></span></dt>
 <dd><p>
               A user defined grammar
             </p></dd>
 </dl>
 </div>
-<div class="variablelist">
+<div class="variablelist" title="Terminology">
 <p class="title"><b>Terminology</b></p>
 <dl>
 <dt><span class="term">Signature</span></dt>
 <dd><p>
- <tt class="computeroutput"><span class="identifier">RT</span><span class="special">(</span><span class="identifier">Arg1</span><span class="special">,</span> <span class="identifier">Arg2</span> <span class="special">...</span>
- <span class="special">,</span><span class="identifier">ArgN</span><span class="special">)</span></tt>. The signature specifies the synthesized
+ <code class="computeroutput"><span class="identifier">RT</span><span class="special">(</span><span class="identifier">Arg1</span><span class="special">,</span> <span class="identifier">Arg2</span> <span class="special">...</span>
+ <span class="special">,</span><span class="identifier">ArgN</span><span class="special">)</span></code>. The signature specifies the synthesized
               (return value) and inherited (arguments) attributes.
             </p></dd>
 <dt><span class="term">Locals</span></dt>
 <dd><p>
- <tt class="computeroutput"><span class="identifier">locals</span><span class="special">&lt;</span><span class="identifier">L1</span><span class="special">,</span> <span class="identifier">L2</span> <span class="special">...,</span>
- <span class="identifier">LN</span><span class="special">&gt;</span></tt>.
+ <code class="computeroutput"><span class="identifier">locals</span><span class="special">&lt;</span><span class="identifier">L1</span><span class="special">,</span> <span class="identifier">L2</span> <span class="special">...,</span>
+ <span class="identifier">LN</span><span class="special">&gt;</span></code>.
               The local variables.
             </p></dd>
 <dt><span class="term">Delimiter</span></dt>
@@ -86,15 +82,15 @@
             </p></dd>
 </dl>
 </div>
-<div class="variablelist">
+<div class="variablelist" title="Template Arguments">
 <p class="title"><b>Template Arguments</b></p>
 <dl>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">Iterator</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">Iterator</span></code></span></dt>
 <dd><p>
               The iterator type you will use for parsing.
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">A1</span></tt>,
- <tt class="computeroutput"><span class="identifier">A2</span></tt>, <tt class="computeroutput"><span class="identifier">A3</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">A1</span></code>,
+ <code class="computeroutput"><span class="identifier">A2</span></code>, <code class="computeroutput"><span class="identifier">A3</span></code></span></dt>
 <dd><p>
               Can be one of 1)Signature 2)Locals 3)Skipper.
             </p></dd>
@@ -106,120 +102,164 @@
 <col>
 </colgroup>
 <thead><tr>
-<th><p>
+<th>
+ <p>
                   Expression
- </p></th>
-<th><p>
+ </p>
+ </th>
+<th>
+ <p>
                   Description
- </p></th>
+ </p>
+ </th>
 </tr></thead>
 <tbody>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">rule</span><span class="special">&lt;</span><span class="identifier">Iterator</span><span class="special">,</span>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">rule</span><span class="special">&lt;</span><span class="identifier">Iterator</span><span class="special">,</span>
                   <span class="identifier">A1</span><span class="special">,</span>
                   <span class="identifier">A2</span><span class="special">,</span>
                   <span class="identifier">A3</span><span class="special">&gt;</span>
- <span class="identifier">r</span><span class="special">(</span><span class="identifier">name</span><span class="special">);</span></tt>
- </p></td>
-<td><p>
- Rule declaration. <tt class="computeroutput"><span class="identifier">Iterator</span></tt>
- is required. <tt class="computeroutput"><span class="identifier">A1</span><span class="special">,</span> <span class="identifier">A2</span><span class="special">,</span> <span class="identifier">A3</span></tt>
- are optional and can be specified in any order. <tt class="computeroutput"><span class="identifier">name</span></tt>
+ <span class="identifier">r</span><span class="special">(</span><span class="identifier">name</span><span class="special">);</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Rule declaration. <code class="computeroutput"><span class="identifier">Iterator</span></code>
+ is required. <code class="computeroutput"><span class="identifier">A1</span><span class="special">,</span> <span class="identifier">A2</span><span class="special">,</span> <span class="identifier">A3</span></code>
+ are optional and can be specified in any order. <code class="computeroutput"><span class="identifier">name</span></code>
                   is an optional string that gives the rule its name, useful for
                   debugging and error handling.
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">rule</span><span class="special">&lt;</span><span class="identifier">Iterator</span><span class="special">,</span>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">rule</span><span class="special">&lt;</span><span class="identifier">Iterator</span><span class="special">,</span>
                   <span class="identifier">A1</span><span class="special">,</span>
                   <span class="identifier">A2</span><span class="special">,</span>
                   <span class="identifier">A3</span><span class="special">&gt;</span>
- <span class="identifier">r</span><span class="special">(</span><span class="identifier">r2</span><span class="special">);</span></tt>
- </p></td>
-<td><p>
- Copy construct rule <tt class="computeroutput"><span class="identifier">r</span></tt>
- from rule <tt class="computeroutput"><span class="identifier">r2</span></tt>.
- <tt class="computeroutput"><span class="identifier">boost</span><span class="special">::</span><span class="identifier">shared_ptr</span></tt> semantics.
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">r</span> <span class="special">=</span>
- <span class="identifier">r2</span><span class="special">;</span></tt>
- </p></td>
-<td><p>
- Assign rule <tt class="computeroutput"><span class="identifier">r2</span></tt>
- to <tt class="computeroutput"><span class="identifier">r</span></tt>. <tt class="computeroutput"><span class="identifier">boost</span><span class="special">::</span><span class="identifier">shared_ptr</span></tt> semantics.
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">r</span><span class="special">.</span><span class="identifier">alias</span><span class="special">()</span></tt>
- </p></td>
-<td><p>
- return an alias of <tt class="computeroutput"><span class="identifier">r</span></tt>.
- The alias is a parser that holds a reference to <tt class="computeroutput"><span class="identifier">r</span></tt>.
+ <span class="identifier">r</span><span class="special">(</span><span class="identifier">r2</span><span class="special">);</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Copy construct rule <code class="computeroutput"><span class="identifier">r</span></code>
+ from rule <code class="computeroutput"><span class="identifier">r2</span></code>.
+ <code class="computeroutput"><span class="identifier">boost</span><span class="special">::</span><span class="identifier">shared_ptr</span></code> semantics.
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">r</span> <span class="special">=</span>
+ <span class="identifier">r2</span><span class="special">;</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Assign rule <code class="computeroutput"><span class="identifier">r2</span></code>
+ to <code class="computeroutput"><span class="identifier">r</span></code>. <code class="computeroutput"><span class="identifier">boost</span><span class="special">::</span><span class="identifier">shared_ptr</span></code> semantics.
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">r</span><span class="special">.</span><span class="identifier">alias</span><span class="special">()</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ return an alias of <code class="computeroutput"><span class="identifier">r</span></code>.
+ The alias is a parser that holds a reference to <code class="computeroutput"><span class="identifier">r</span></code>.
                   Reference semantics.
- </p></td>
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">r</span><span class="special">.</span><span class="identifier">copy</span><span class="special">()</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Get a copy of <code class="computeroutput"><span class="identifier">r</span></code>.
+ <code class="computeroutput"><span class="identifier">boost</span><span class="special">::</span><span class="identifier">shared_ptr</span></code> semantics.
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">r</span><span class="special">.</span><span class="identifier">copy</span><span class="special">()</span></tt>
- </p></td>
-<td><p>
- Get a copy of <tt class="computeroutput"><span class="identifier">r</span></tt>.
- <tt class="computeroutput"><span class="identifier">boost</span><span class="special">::</span><span class="identifier">shared_ptr</span></tt> semantics.
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">r</span><span class="special">.</span><span class="identifier">name</span><span class="special">(</span><span class="identifier">name</span><span class="special">)</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">r</span><span class="special">.</span><span class="identifier">name</span><span class="special">(</span><span class="identifier">name</span><span class="special">)</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   Naming a rule
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">r</span><span class="special">.</span><span class="identifier">name</span><span class="special">()</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">r</span><span class="special">.</span><span class="identifier">name</span><span class="special">()</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   Getting the name of a rule
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
+<td>
+ <p>
                   debug(r)
- </p></td>
-<td><p>
- Debug rule <tt class="computeroutput"><span class="identifier">r</span></tt>
- </p></td>
+ </p>
+ </td>
+<td>
+ <p>
+ Debug rule <code class="computeroutput"><span class="identifier">r</span></code>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">r</span> <span class="special">=</span>
- <span class="identifier">g</span><span class="special">;</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">r</span> <span class="special">=</span>
+ <span class="identifier">g</span><span class="special">;</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   Rule definition
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">r</span> <span class="special">%=</span>
- <span class="identifier">g</span><span class="special">;</span></tt>
- </p></td>
-<td><p>
- Auto-rule definition. The attribute of <tt class="computeroutput"><span class="identifier">g</span></tt>
- should be compatible with the synthesized attribute of <tt class="computeroutput"><span class="identifier">r</span></tt>. When <tt class="computeroutput"><span class="identifier">g</span></tt>
- is successful, its attribute is automatically propagated to <tt class="computeroutput"><span class="identifier">r</span></tt>'s synthesized attribute.
- </p></td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">r</span> <span class="special">%=</span>
+ <span class="identifier">g</span><span class="special">;</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Auto-rule definition. The attribute of <code class="computeroutput"><span class="identifier">g</span></code>
+ should be compatible with the synthesized attribute of <code class="computeroutput"><span class="identifier">r</span></code>. When <code class="computeroutput"><span class="identifier">g</span></code>
+ is successful, its attribute is automatically propagated to <code class="computeroutput"><span class="identifier">r</span></code>'s synthesized attribute.
+ </p>
+ </td>
 </tr>
 <tr>
 <td>
-<p>
+ <p>
                   
 </p>
 <pre xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="table-programlisting"><span class="keyword">template</span> <span class="special">&lt;</span><span class="keyword">typename</span> <span class="identifier">Iterator</span><span class="special">&gt;</span>
@@ -237,36 +277,50 @@
 </pre>
 <p>
                 </p>
-</td>
-<td><p>
- Grammar definition. <tt class="computeroutput"><span class="identifier">name</span></tt>
+ </td>
+<td>
+ <p>
+ Grammar definition. <code class="computeroutput"><span class="identifier">name</span></code>
                   is an optional string that gives the grammar its name, useful for
                   debugging and error handling.
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
+<td>
+ <p>
                   my_grammar&lt;Iterator&gt; g
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
                   Instantiating a grammar
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">g</span><span class="special">.</span><span class="identifier">name</span><span class="special">(</span><span class="identifier">name</span><span class="special">)</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">g</span><span class="special">.</span><span class="identifier">name</span><span class="special">(</span><span class="identifier">name</span><span class="special">)</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   Naming a grammar
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">g</span><span class="special">.</span><span class="identifier">name</span><span class="special">()</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">g</span><span class="special">.</span><span class="identifier">name</span><span class="special">()</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   Getting the name of a grammar
- </p></td>
+ </p>
+ </td>
 </tr>
 </tbody>
 </table></div>

Modified: trunk/libs/spirit/doc/html/spirit/karma/quick_reference/phoenix.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/karma/quick_reference/phoenix.html (original)
+++ trunk/libs/spirit/doc/html/spirit/karma/quick_reference/phoenix.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -3,11 +3,10 @@
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <title>Phoenix</title>
 <link rel="stylesheet" href="../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../index.html" title="Spirit 2.1">
 <link rel="up" href="../quick_reference.html" title="Quick Reference">
-<link rel="previous" href="semantic_actions.html" title="Semantic
- Actions">
+<link rel="prev" href="semantic_actions.html" title="Semantic Actions">
 <link rel="next" href="../reference.html" title="Reference">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -23,13 +22,10 @@
 <div class="spirit-nav">
 <a accesskey="p" href="semantic_actions.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../quick_reference.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="../reference.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h4 class="title">
-<a name="spirit.karma.quick_reference.phoenix"></a>Phoenix
-</h4></div></div>
-<div></div>
-</div>
+<div class="section" title="Phoenix">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="spirit.karma.quick_reference.phoenix"></a><a class="link" href="phoenix.html" title="Phoenix">Phoenix</a>
+</h4></div></div></div>
 <p>
           <a href="../../../../../phoenix/doc/html/index.html" target="_top">Boost.Phoenix</a> makes
           it easier to attach semantic actions. You just inline your lambda expressions:
@@ -38,37 +34,37 @@
 </pre>
 <p>
           <span class="emphasis"><em>Spirit.Karma</em></span> provides some Boost.Phoenix
- placeholders to access important information from the <tt class="computeroutput"><span class="identifier">Attr</span></tt>
- and <tt class="computeroutput"><span class="identifier">Context</span></tt> that are otherwise
+ placeholders to access important information from the <code class="computeroutput"><span class="identifier">Attr</span></code>
+ and <code class="computeroutput"><span class="identifier">Context</span></code> that are otherwise
           fiddly to extract.
         </p>
-<div class="variablelist">
+<div class="variablelist" title="Spirit.Karma specific Phoenix placeholders">
 <p class="title"><b>Spirit.Karma specific Phoenix placeholders</b></p>
 <dl>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">_1</span><span class="special">,</span> <span class="identifier">_2</span><span class="special">...</span> <span class="special">,</span> <span class="identifier">_N</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">_1</span><span class="special">,</span> <span class="identifier">_2</span><span class="special">...</span> <span class="special">,</span> <span class="identifier">_N</span></code></span></dt>
 <dd><p>
- Nth attribute of <tt class="computeroutput"><span class="identifier">g</span></tt>
+ Nth attribute of <code class="computeroutput"><span class="identifier">g</span></code>
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">_val</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">_val</span></code></span></dt>
 <dd><p>
               The enclosing rule's synthesized attribute.
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">_r1</span><span class="special">,</span> <span class="identifier">_r2</span><span class="special">...</span> <span class="special">,</span> <span class="identifier">_rN</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">_r1</span><span class="special">,</span> <span class="identifier">_r2</span><span class="special">...</span> <span class="special">,</span> <span class="identifier">_rN</span></code></span></dt>
 <dd><p>
               The enclosing rule's Nth inherited attribute.
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">_a</span><span class="special">,</span> <span class="identifier">_b</span><span class="special">...</span> <span class="special">,</span> <span class="identifier">_j</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">_a</span><span class="special">,</span> <span class="identifier">_b</span><span class="special">...</span> <span class="special">,</span> <span class="identifier">_j</span></code></span></dt>
 <dd><p>
- The enclosing rule's local variables (<tt class="computeroutput"><span class="identifier">_a</span></tt>
+ The enclosing rule's local variables (<code class="computeroutput"><span class="identifier">_a</span></code>
               refers to the first).
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">_val</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">_val</span></code></span></dt>
 <dd><p>
               The enclosing rule's synthesized attribute.
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">_pass</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">_pass</span></code></span></dt>
 <dd><p>
- Assign <tt class="computeroutput"><span class="keyword">false</span></tt> to <tt class="computeroutput"><span class="identifier">_pass</span></tt> to force a generator failure.
+ Assign <code class="computeroutput"><span class="keyword">false</span></code> to <code class="computeroutput"><span class="identifier">_pass</span></code> to force a generator failure.
             </p></dd>
 </dl>
 </div>

Modified: trunk/libs/spirit/doc/html/spirit/karma/quick_reference/predefined_primitive_generators.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/karma/quick_reference/predefined_primitive_generators.html (original)
+++ trunk/libs/spirit/doc/html/spirit/karma/quick_reference/predefined_primitive_generators.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -1,16 +1,13 @@
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title>Predefined
- Primitive Generators</title>
+<title>Predefined Primitive Generators</title>
 <link rel="stylesheet" href="../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../index.html" title="Spirit 2.1">
 <link rel="up" href="../quick_reference.html" title="Quick Reference">
-<link rel="previous" href="common_notation.html" title="Common
- Notation">
-<link rel="next" href="compound_attribute_rules.html" title="Compound
- Attribute Rules">
+<link rel="prev" href="common_notation.html" title="Common Notation">
+<link rel="next" href="compound_attribute_rules.html" title="Compound Attribute Rules">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
 <table cellpadding="2" width="100%"><tr>
@@ -25,15 +22,11 @@
 <div class="spirit-nav">
 <a accesskey="p" href="common_notation.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../quick_reference.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="compound_attribute_rules.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h4 class="title">
-<a name="spirit.karma.quick_reference.predefined_primitive_generators"></a><a href="predefined_primitive_generators.html" title="Predefined
- Primitive Generators">Predefined
+<div class="section" title="Predefined Primitive Generators">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="spirit.karma.quick_reference.predefined_primitive_generators"></a><a class="link" href="predefined_primitive_generators.html" title="Predefined Primitive Generators">Predefined
         Primitive Generators</a>
-</h4></div></div>
-<div></div>
-</div>
+</h4></div></div></div>
 <div class="informaltable"><table class="table">
 <colgroup>
 <col>
@@ -41,781 +34,1177 @@
 <col>
 </colgroup>
 <thead><tr>
-<th><p>
+<th>
+ <p>
                   Expression
- </p></th>
-<th><p>
+ </p>
+ </th>
+<th>
+ <p>
                   Attribute
- </p></th>
-<th><p>
+ </p>
+ </th>
+<th>
+ <p>
                   Description
- </p></th>
+ </p>
+ </th>
 </tr></thead>
 <tbody>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">eol</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">Unused</span></tt>
- </p></td>
-<td><p>
- Generates the end of line (<tt class="computeroutput"><span class="special">\</span><span class="identifier">n</span></tt>)
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">eps</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">Unused</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">eol</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">Unused</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Generates the end of line (<code class="computeroutput"><span class="special">\</span><span class="identifier">n</span></code>)
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">eps</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">Unused</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   Generate an empty string
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">eps</span><span class="special">(</span><span class="identifier">b</span><span class="special">)</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">Unused</span></tt>
- </p></td>
-<td><p>
- If <tt class="computeroutput"><span class="identifier">b</span></tt> is true, generate
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">eps</span><span class="special">(</span><span class="identifier">b</span><span class="special">)</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">Unused</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ If <code class="computeroutput"><span class="identifier">b</span></code> is true, generate
                   an empty string
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">lazy</span><span class="special">(</span><span class="identifier">fg</span><span class="special">)</span></tt>
- </p></td>
-<td><p>
- Attribute of <tt class="computeroutput"><span class="identifier">G</span></tt>
- where <tt class="computeroutput"><span class="identifier">G</span></tt> is the
- return type of <tt class="computeroutput"><span class="identifier">fg</span></tt>
- </p></td>
-<td><p>
- Invoke <tt class="computeroutput"><span class="identifier">fg</span></tt> at generation
- time, returning a generator <tt class="computeroutput"><span class="identifier">g</span></tt>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">lazy</span><span class="special">(</span><span class="identifier">fg</span><span class="special">)</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Attribute of <code class="computeroutput"><span class="identifier">G</span></code>
+ where <code class="computeroutput"><span class="identifier">G</span></code> is the
+ return type of <code class="computeroutput"><span class="identifier">fg</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Invoke <code class="computeroutput"><span class="identifier">fg</span></code> at generation
+ time, returning a generator <code class="computeroutput"><span class="identifier">g</span></code>
                   which is then called to generate.
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">fg</span></tt>
- </p></td>
-<td><p>
- see <tt class="computeroutput"><span class="identifier">lazy</span><span class="special">(</span><span class="identifier">fg</span><span class="special">)</span></tt>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">fg</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ see <code class="computeroutput"><span class="identifier">lazy</span><span class="special">(</span><span class="identifier">fg</span><span class="special">)</span></code>
                   above
- </p></td>
-<td><p>
- Equivalent to <tt class="computeroutput"><span class="identifier">lazy</span><span class="special">[</span><span class="identifier">fg</span><span class="special">]</span></tt>
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">g</span><span class="special">[</span><span class="identifier">fa</span><span class="special">]</span></tt>
- </p></td>
-<td><p>
- Attribute of <tt class="computeroutput"><span class="identifier">g</span></tt>
- </p></td>
-<td><p>
- Call semantic action <tt class="computeroutput"><span class="identifier">fa</span></tt>
- (before executing <tt class="computeroutput"><span class="identifier">g</span></tt>).
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">byte_</span></tt>
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
+ Equivalent to <code class="computeroutput"><span class="identifier">lazy</span><span class="special">[</span><span class="identifier">fg</span><span class="special">]</span></code>
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">g</span><span class="special">[</span><span class="identifier">fa</span><span class="special">]</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Attribute of <code class="computeroutput"><span class="identifier">g</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Call semantic action <code class="computeroutput"><span class="identifier">fa</span></code>
+ (before executing <code class="computeroutput"><span class="identifier">g</span></code>).
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">byte_</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   8 bits native endian
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
                   Generates an 8 bit binary
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">word</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">word</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   16 bits native endian
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
                   Generates a 16 bit binary
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">big_word</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">big_word</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   16 bits big endian
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
                   Generates a 16 bit binary
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">little_word</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">little_word</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   16 bits little endian
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
                   Generates a 16 bit binary
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">dword</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">dword</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   32 bits native endian
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
                   Generates a 32 bit binary
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">big_dword</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">big_dword</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   32 bits big endian
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
                   Generates a 32 bit binary
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">little_dword</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">little_dword</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   32 bits little endian
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
                   Generates a 32 bit binary
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">qword</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">qword</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   64 bits native endian
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
                   Generates a 64 bit binary
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">big_qword</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">big_qword</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   64 bits big endian
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
                   Generates a 64 bit binary
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">little_qword</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">little_qword</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   64 bits little endian
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
                   Generates a 64 bit binary
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">char_</span><span class="special">(</span><span class="identifier">ch</span><span class="special">)</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">Ch</span></tt>
- </p></td>
-<td><p>
- Generates <tt class="computeroutput"><span class="identifier">ch</span></tt>
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">char_</span><span class="special">(</span><span class="string">"c"</span><span class="special">)</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">Ch</span></tt>
- </p></td>
-<td><p>
- Generates a single char string literal, <tt class="computeroutput"><span class="identifier">c</span></tt>
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">ch</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">Unused</span></tt>
- </p></td>
-<td><p>
- Generates <tt class="computeroutput"><span class="identifier">ch</span></tt>
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">str</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">Unused</span></tt>
- </p></td>
-<td><p>
- Generates <tt class="computeroutput"><span class="identifier">str</span></tt>
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">lit</span><span class="special">(</span><span class="identifier">ch</span><span class="special">)</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">Unused</span></tt>
- </p></td>
-<td><p>
- Generates <tt class="computeroutput"><span class="identifier">ch</span></tt>
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">lit</span><span class="special">(</span><span class="identifier">str</span><span class="special">)</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">Unused</span></tt>
- </p></td>
-<td><p>
- Generates <tt class="computeroutput"><span class="identifier">str</span></tt>
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">string</span><span class="special">(</span><span class="identifier">str</span><span class="special">)</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">Str</span></tt>
- </p></td>
-<td><p>
- Generates <tt class="computeroutput"><span class="identifier">str</span></tt>
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">lower</span><span class="special">[</span><span class="identifier">a</span><span class="special">]</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">A</span></tt>
- </p></td>
-<td><p>
- Generate <tt class="computeroutput"><span class="identifier">a</span></tt> as lower
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">char_</span><span class="special">(</span><span class="identifier">ch</span><span class="special">)</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">Ch</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Generates <code class="computeroutput"><span class="identifier">ch</span></code>
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">char_</span><span class="special">(</span><span class="string">"c"</span><span class="special">)</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">Ch</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Generates a single char string literal, <code class="computeroutput"><span class="identifier">c</span></code>
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">ch</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">Unused</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Generates <code class="computeroutput"><span class="identifier">ch</span></code>
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">str</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">Unused</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Generates <code class="computeroutput"><span class="identifier">str</span></code>
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">lit</span><span class="special">(</span><span class="identifier">ch</span><span class="special">)</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">Unused</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Generates <code class="computeroutput"><span class="identifier">ch</span></code>
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">lit</span><span class="special">(</span><span class="identifier">str</span><span class="special">)</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">Unused</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Generates <code class="computeroutput"><span class="identifier">str</span></code>
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">string</span><span class="special">(</span><span class="identifier">str</span><span class="special">)</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">Str</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Generates <code class="computeroutput"><span class="identifier">str</span></code>
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">lower</span><span class="special">[</span><span class="identifier">a</span><span class="special">]</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">A</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Generate <code class="computeroutput"><span class="identifier">a</span></code> as lower
                   case
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">upper</span><span class="special">[</span><span class="identifier">a</span><span class="special">]</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">A</span></tt>
- </p></td>
-<td><p>
- Generate <tt class="computeroutput"><span class="identifier">a</span></tt> as upper
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">upper</span><span class="special">[</span><span class="identifier">a</span><span class="special">]</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">A</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Generate <code class="computeroutput"><span class="identifier">a</span></code> as upper
                   case
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">left_align</span><span class="special">[</span><span class="identifier">a</span><span class="special">]</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">A</span></tt>
- </p></td>
-<td><p>
- Generate <tt class="computeroutput"><span class="identifier">a</span></tt> left
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">left_align</span><span class="special">[</span><span class="identifier">a</span><span class="special">]</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">A</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Generate <code class="computeroutput"><span class="identifier">a</span></code> left
                   aligned in column of width BOOST_KARMA_DEFAULT_FIELD_LENGTH
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">left_align</span><span class="special">(</span><span class="identifier">N</span><span class="special">)[</span><span class="identifier">a</span><span class="special">]</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">A</span></tt>
- </p></td>
-<td><p>
- Generate <tt class="computeroutput"><span class="identifier">a</span></tt> left
- aligned in column of width <tt class="computeroutput"><span class="identifier">N</span></tt>
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">left_align</span><span class="special">(</span><span class="identifier">N</span><span class="special">,</span>
- <span class="identifier">g</span><span class="special">)[</span><span class="identifier">a</span><span class="special">]</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">A</span></tt>
- </p></td>
-<td><p>
- Generate <tt class="computeroutput"><span class="identifier">a</span></tt> left
- aligned in column of width <tt class="computeroutput"><span class="identifier">N</span></tt>
- while using <tt class="computeroutput"><span class="identifier">g</span></tt> to
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">left_align</span><span class="special">(</span><span class="identifier">N</span><span class="special">)[</span><span class="identifier">a</span><span class="special">]</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">A</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Generate <code class="computeroutput"><span class="identifier">a</span></code> left
+ aligned in column of width <code class="computeroutput"><span class="identifier">N</span></code>
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">left_align</span><span class="special">(</span><span class="identifier">N</span><span class="special">,</span>
+ <span class="identifier">g</span><span class="special">)[</span><span class="identifier">a</span><span class="special">]</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">A</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Generate <code class="computeroutput"><span class="identifier">a</span></code> left
+ aligned in column of width <code class="computeroutput"><span class="identifier">N</span></code>
+ while using <code class="computeroutput"><span class="identifier">g</span></code> to
                   generate the necesssary padding
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">right_align</span><span class="special">[</span><span class="identifier">a</span><span class="special">]</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">A</span></tt>
- </p></td>
-<td><p>
- Generate <tt class="computeroutput"><span class="identifier">a</span></tt> right
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">right_align</span><span class="special">[</span><span class="identifier">a</span><span class="special">]</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">A</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Generate <code class="computeroutput"><span class="identifier">a</span></code> right
                   aligned in column of width BOOST_KARMA_DEFAULT_FIELD_LENGTH
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">right_align</span><span class="special">(</span><span class="identifier">N</span><span class="special">)[</span><span class="identifier">a</span><span class="special">]</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">A</span></tt>
- </p></td>
-<td><p>
- Generate <tt class="computeroutput"><span class="identifier">a</span></tt> right
- aligned in column of width <tt class="computeroutput"><span class="identifier">N</span></tt>
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">right_align</span><span class="special">(</span><span class="identifier">N</span><span class="special">,</span>
- <span class="identifier">g</span><span class="special">)[</span><span class="identifier">a</span><span class="special">]</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">A</span></tt>
- </p></td>
-<td><p>
- Generate <tt class="computeroutput"><span class="identifier">a</span></tt> right
- aligned in column of width <tt class="computeroutput"><span class="identifier">N</span></tt>
- while using <tt class="computeroutput"><span class="identifier">g</span></tt> to
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">right_align</span><span class="special">(</span><span class="identifier">N</span><span class="special">)[</span><span class="identifier">a</span><span class="special">]</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">A</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Generate <code class="computeroutput"><span class="identifier">a</span></code> right
+ aligned in column of width <code class="computeroutput"><span class="identifier">N</span></code>
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">right_align</span><span class="special">(</span><span class="identifier">N</span><span class="special">,</span>
+ <span class="identifier">g</span><span class="special">)[</span><span class="identifier">a</span><span class="special">]</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">A</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Generate <code class="computeroutput"><span class="identifier">a</span></code> right
+ aligned in column of width <code class="computeroutput"><span class="identifier">N</span></code>
+ while using <code class="computeroutput"><span class="identifier">g</span></code> to
                   generate the necesssary padding
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">center</span><span class="special">[</span><span class="identifier">a</span><span class="special">]</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">A</span></tt>
- </p></td>
-<td><p>
- Generate <tt class="computeroutput"><span class="identifier">a</span></tt> centered
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">center</span><span class="special">[</span><span class="identifier">a</span><span class="special">]</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">A</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Generate <code class="computeroutput"><span class="identifier">a</span></code> centered
                   in column of width BOOST_KARMA_DEFAULT_FIELD_LENGTH
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">center</span><span class="special">(</span><span class="identifier">N</span><span class="special">)[</span><span class="identifier">a</span><span class="special">]</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">A</span></tt>
- </p></td>
-<td><p>
- Generate <tt class="computeroutput"><span class="identifier">a</span></tt> centered
- in column of width <tt class="computeroutput"><span class="identifier">N</span></tt>
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">center</span><span class="special">(</span><span class="identifier">N</span><span class="special">,</span>
- <span class="identifier">g</span><span class="special">)[</span><span class="identifier">a</span><span class="special">]</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">A</span></tt>
- </p></td>
-<td><p>
- Generate <tt class="computeroutput"><span class="identifier">a</span></tt> centered
- in column of width <tt class="computeroutput"><span class="identifier">N</span></tt>
- while using <tt class="computeroutput"><span class="identifier">g</span></tt> to
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">center</span><span class="special">(</span><span class="identifier">N</span><span class="special">)[</span><span class="identifier">a</span><span class="special">]</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">A</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Generate <code class="computeroutput"><span class="identifier">a</span></code> centered
+ in column of width <code class="computeroutput"><span class="identifier">N</span></code>
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">center</span><span class="special">(</span><span class="identifier">N</span><span class="special">,</span>
+ <span class="identifier">g</span><span class="special">)[</span><span class="identifier">a</span><span class="special">]</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">A</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Generate <code class="computeroutput"><span class="identifier">a</span></code> centered
+ in column of width <code class="computeroutput"><span class="identifier">N</span></code>
+ while using <code class="computeroutput"><span class="identifier">g</span></code> to
                   generate the necesssary padding
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">maxwidth</span><span class="special">[</span><span class="identifier">a</span><span class="special">]</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">A</span></tt>
- </p></td>
-<td><p>
- Generate <tt class="computeroutput"><span class="identifier">a</span></tt> truncated
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">maxwidth</span><span class="special">[</span><span class="identifier">a</span><span class="special">]</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">A</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Generate <code class="computeroutput"><span class="identifier">a</span></code> truncated
                   to column of width BOOST_KARMA_DEFAULT_FIELD_MAXWIDTH
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">maxwidth</span><span class="special">(</span><span class="identifier">N</span><span class="special">)[</span><span class="identifier">a</span><span class="special">]</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">A</span></tt>
- </p></td>
-<td><p>
- Generate <tt class="computeroutput"><span class="identifier">a</span></tt> truncated
- to column of width <tt class="computeroutput"><span class="identifier">N</span></tt>
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">repeat</span><span class="special">[</span><span class="identifier">a</span><span class="special">]</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">vector</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">&gt;</span></tt>
- </p></td>
-<td><p>
- Repeat <tt class="computeroutput"><span class="identifier">a</span></tt> zero or
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">maxwidth</span><span class="special">(</span><span class="identifier">N</span><span class="special">)[</span><span class="identifier">a</span><span class="special">]</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">A</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Generate <code class="computeroutput"><span class="identifier">a</span></code> truncated
+ to column of width <code class="computeroutput"><span class="identifier">N</span></code>
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">repeat</span><span class="special">[</span><span class="identifier">a</span><span class="special">]</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">vector</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">&gt;</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Repeat <code class="computeroutput"><span class="identifier">a</span></code> zero or
                   more times
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">repeat</span><span class="special">(</span><span class="identifier">N</span><span class="special">)[</span><span class="identifier">a</span><span class="special">]</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">vector</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">&gt;</span></tt>
- </p></td>
-<td><p>
- Repeat <tt class="computeroutput"><span class="identifier">a</span></tt> <tt class="computeroutput"><span class="identifier">N</span></tt> times
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">repeat</span><span class="special">(</span><span class="identifier">N</span><span class="special">,</span>
- <span class="identifier">M</span><span class="special">)[</span><span class="identifier">a</span><span class="special">]</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">vector</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">&gt;</span></tt>
- </p></td>
-<td><p>
- Repeat <tt class="computeroutput"><span class="identifier">a</span></tt> <tt class="computeroutput"><span class="identifier">N</span></tt> to <tt class="computeroutput"><span class="identifier">M</span></tt>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">repeat</span><span class="special">(</span><span class="identifier">N</span><span class="special">)[</span><span class="identifier">a</span><span class="special">]</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">vector</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">&gt;</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Repeat <code class="computeroutput"><span class="identifier">a</span></code> <code class="computeroutput"><span class="identifier">N</span></code> times
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">repeat</span><span class="special">(</span><span class="identifier">N</span><span class="special">,</span>
+ <span class="identifier">M</span><span class="special">)[</span><span class="identifier">a</span><span class="special">]</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">vector</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">&gt;</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Repeat <code class="computeroutput"><span class="identifier">a</span></code> <code class="computeroutput"><span class="identifier">N</span></code> to <code class="computeroutput"><span class="identifier">M</span></code>
                   times
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">repeat</span><span class="special">(</span><span class="identifier">N</span><span class="special">,</span>
- <span class="identifier">inf</span><span class="special">)[</span><span class="identifier">a</span><span class="special">]</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">vector</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">&gt;</span></tt>
- </p></td>
-<td><p>
- Repeat <tt class="computeroutput"><span class="identifier">a</span></tt> <tt class="computeroutput"><span class="identifier">N</span></tt> or more times
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">verbatim</span><span class="special">[</span><span class="identifier">a</span><span class="special">]</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">A</span></tt>
- </p></td>
-<td><p>
- Disable delimited generation for <tt class="computeroutput"><span class="identifier">a</span></tt>
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">delimit</span><span class="special">[</span><span class="identifier">a</span><span class="special">]</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">A</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">repeat</span><span class="special">(</span><span class="identifier">N</span><span class="special">,</span>
+ <span class="identifier">inf</span><span class="special">)[</span><span class="identifier">a</span><span class="special">]</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">vector</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">&gt;</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Repeat <code class="computeroutput"><span class="identifier">a</span></code> <code class="computeroutput"><span class="identifier">N</span></code> or more times
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">verbatim</span><span class="special">[</span><span class="identifier">a</span><span class="special">]</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">A</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Disable delimited generation for <code class="computeroutput"><span class="identifier">a</span></code>
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">delimit</span><span class="special">[</span><span class="identifier">a</span><span class="special">]</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">A</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   Reestablish the delimiter that got inhibited by verbatim
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">delimit</span><span class="special">(</span><span class="identifier">g</span><span class="special">)[</span><span class="identifier">a</span><span class="special">]</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">A</span></tt>
- </p></td>
-<td><p>
- Use <tt class="computeroutput"><span class="identifier">g</span></tt> as a skipper
- for generating <tt class="computeroutput"><span class="identifier">a</span></tt>
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">float_</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="keyword">float</span></tt>
- </p></td>
-<td><p>
- Generate a floating point number from a <tt class="computeroutput"><span class="keyword">float</span></tt>
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">double_</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="keyword">double</span></tt>
- </p></td>
-<td><p>
- Generate a floating point number from a <tt class="computeroutput"><span class="keyword">double</span></tt>
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">long_double</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="keyword">long</span> <span class="keyword">double</span></tt>
- </p></td>
-<td><p>
- Generate a floating point number from a <tt class="computeroutput"><span class="keyword">long</span>
- <span class="keyword">double</span></tt>
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">bin</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="keyword">unsigned</span></tt>
- </p></td>
-<td><p>
- Generate a binary integer from an <tt class="computeroutput"><span class="keyword">unsigned</span></tt>
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">oct</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="keyword">unsigned</span></tt>
- </p></td>
-<td><p>
- Generate an octal integer from an <tt class="computeroutput"><span class="keyword">unsigned</span></tt>
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">hex</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="keyword">unsigned</span></tt>
- </p></td>
-<td><p>
- Generate a hexadecimal integer from an <tt class="computeroutput"><span class="keyword">unsigned</span></tt>
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">ushort_</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="keyword">unsigned</span> <span class="keyword">short</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">delimit</span><span class="special">(</span><span class="identifier">g</span><span class="special">)[</span><span class="identifier">a</span><span class="special">]</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">A</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Use <code class="computeroutput"><span class="identifier">g</span></code> as a skipper
+ for generating <code class="computeroutput"><span class="identifier">a</span></code>
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">float_</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="keyword">float</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Generate a floating point number from a <code class="computeroutput"><span class="keyword">float</span></code>
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">double_</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="keyword">double</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Generate a floating point number from a <code class="computeroutput"><span class="keyword">double</span></code>
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">long_double</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="keyword">long</span> <span class="keyword">double</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Generate a floating point number from a <code class="computeroutput"><span class="keyword">long</span>
+ <span class="keyword">double</span></code>
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">bin</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="keyword">unsigned</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Generate a binary integer from an <code class="computeroutput"><span class="keyword">unsigned</span></code>
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">oct</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="keyword">unsigned</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Generate an octal integer from an <code class="computeroutput"><span class="keyword">unsigned</span></code>
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">hex</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="keyword">unsigned</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Generate a hexadecimal integer from an <code class="computeroutput"><span class="keyword">unsigned</span></code>
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">ushort_</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="keyword">unsigned</span> <span class="keyword">short</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   Generate an unsigned short integer
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">ulong_</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="keyword">unsigned</span> <span class="keyword">long</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">ulong_</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="keyword">unsigned</span> <span class="keyword">long</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   Generate an unsigned long integer
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">uint_</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="keyword">unsigned</span> <span class="keyword">int</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">uint_</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="keyword">unsigned</span> <span class="keyword">int</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   Generate an unsigned int
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">ulong_long</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="keyword">unsigned</span> <span class="keyword">long</span>
- <span class="keyword">long</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">ulong_long</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="keyword">unsigned</span> <span class="keyword">long</span>
+ <span class="keyword">long</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   Generate an unsigned long long
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">short_</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="keyword">short</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">short_</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="keyword">short</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   Generate a short integer
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">long_</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="keyword">long</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">long_</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="keyword">long</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   Generate a long integer
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">int_</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="keyword">int</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">int_</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="keyword">int</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   Generate an int
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">long_long</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="keyword">long</span> <span class="keyword">long</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">long_long</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="keyword">long</span> <span class="keyword">long</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   Generate a long long
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="special">!</span><span class="identifier">a</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">Unused</span></tt>
- </p></td>
-<td><p>
- Not predicate. Ensure that <tt class="computeroutput"><span class="identifier">a</span></tt>
+<td>
+ <p>
+ <code class="computeroutput"><span class="special">!</span><span class="identifier">a</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">Unused</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Not predicate. Ensure that <code class="computeroutput"><span class="identifier">a</span></code>
                   does not succeed generating but don't create any output
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="special">&amp;</span><span class="identifier">a</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">Unused</span></tt>
- </p></td>
-<td><p>
- And predicate. Ensure that <tt class="computeroutput"><span class="identifier">a</span></tt>
+<td>
+ <p>
+ <code class="computeroutput"><span class="special">&amp;</span><span class="identifier">a</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">Unused</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ And predicate. Ensure that <code class="computeroutput"><span class="identifier">a</span></code>
                   does succeed generating but don't create any output
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="special">-</span><span class="identifier">a</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">optional</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">&gt;</span></tt>
- </p></td>
-<td><p>
- Optional. Generate <tt class="computeroutput"><span class="identifier">a</span></tt>
+<td>
+ <p>
+ <code class="computeroutput"><span class="special">-</span><span class="identifier">a</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">optional</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">&gt;</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Optional. Generate <code class="computeroutput"><span class="identifier">a</span></code>
                   zero or one time
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="special">*</span><span class="identifier">a</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">vector</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">&gt;</span></tt>
- </p></td>
-<td><p>
- Kleene. Generate <tt class="computeroutput"><span class="identifier">a</span></tt>
+<td>
+ <p>
+ <code class="computeroutput"><span class="special">*</span><span class="identifier">a</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">vector</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">&gt;</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Kleene. Generate <code class="computeroutput"><span class="identifier">a</span></code>
                   zero or more times
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="special">+</span><span class="identifier">a</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">vector</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">&gt;</span></tt>
- </p></td>
-<td><p>
- Plus. Generate <tt class="computeroutput"><span class="identifier">a</span></tt>
+<td>
+ <p>
+ <code class="computeroutput"><span class="special">+</span><span class="identifier">a</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">vector</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">&gt;</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Plus. Generate <code class="computeroutput"><span class="identifier">a</span></code>
                   one or more times
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">a</span> <span class="special">|</span>
- <span class="identifier">b</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">variant</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">,</span>
- <span class="identifier">B</span><span class="special">&gt;</span></tt>
- </p></td>
-<td><p>
- Alternative. Generate <tt class="computeroutput"><span class="identifier">a</span></tt>
- or <tt class="computeroutput"><span class="identifier">b</span></tt>
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">a</span> <span class="special">&lt;&lt;</span>
- <span class="identifier">b</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">tuple</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">,</span>
- <span class="identifier">B</span><span class="special">&gt;</span></tt>
- </p></td>
-<td><p>
- Sequence. Generate <tt class="computeroutput"><span class="identifier">a</span></tt>
- followed by <tt class="computeroutput"><span class="identifier">b</span></tt>
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">a</span> <span class="special">%</span>
- <span class="identifier">b</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">vector</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">&gt;</span></tt>
- </p></td>
-<td><p>
- List. Generate <tt class="computeroutput"><span class="identifier">a</span></tt>
- delimited <tt class="computeroutput"><span class="identifier">b</span></tt> one
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">a</span> <span class="special">|</span>
+ <span class="identifier">b</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">variant</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">,</span>
+ <span class="identifier">B</span><span class="special">&gt;</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Alternative. Generate <code class="computeroutput"><span class="identifier">a</span></code>
+ or <code class="computeroutput"><span class="identifier">b</span></code>
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">a</span> <span class="special">&lt;&lt;</span>
+ <span class="identifier">b</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">tuple</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">,</span>
+ <span class="identifier">B</span><span class="special">&gt;</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Sequence. Generate <code class="computeroutput"><span class="identifier">a</span></code>
+ followed by <code class="computeroutput"><span class="identifier">b</span></code>
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">a</span> <span class="special">%</span>
+ <span class="identifier">b</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">vector</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">&gt;</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ List. Generate <code class="computeroutput"><span class="identifier">a</span></code>
+ delimited <code class="computeroutput"><span class="identifier">b</span></code> one
                   or more times
- </p></td>
+ </p>
+ </td>
 </tr>
 </tbody>
 </table></div>

Modified: trunk/libs/spirit/doc/html/spirit/karma/quick_reference/semantic_actions.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/karma/quick_reference/semantic_actions.html (original)
+++ trunk/libs/spirit/doc/html/spirit/karma/quick_reference/semantic_actions.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -1,13 +1,12 @@
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title>Semantic
- Actions</title>
+<title>Semantic Actions</title>
 <link rel="stylesheet" href="../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../index.html" title="Spirit 2.1">
 <link rel="up" href="../quick_reference.html" title="Quick Reference">
-<link rel="previous" href="non_terminals.html" title="Non-terminals">
+<link rel="prev" href="non_terminals.html" title="Non-terminals">
 <link rel="next" href="phoenix.html" title="Phoenix">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -23,22 +22,18 @@
 <div class="spirit-nav">
 <a accesskey="p" href="non_terminals.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../quick_reference.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="phoenix.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h4 class="title">
-<a name="spirit.karma.quick_reference.semantic_actions"></a><a href="semantic_actions.html" title="Semantic
- Actions">Semantic
+<div class="section" title="Semantic Actions">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="spirit.karma.quick_reference.semantic_actions"></a><a class="link" href="semantic_actions.html" title="Semantic Actions">Semantic
         Actions</a>
-</h4></div></div>
-<div></div>
-</div>
+</h4></div></div></div>
 <p>
           Has the form:
         </p>
 <pre class="programlisting"><span class="identifier">g</span><span class="special">[</span><span class="identifier">f</span><span class="special">]</span>
 </pre>
 <p>
- where <tt class="computeroutput"><span class="identifier">f</span></tt> is a function with
+ where <code class="computeroutput"><span class="identifier">f</span></code> is a function with
           the signatures:
         </p>
 <pre class="programlisting"><span class="keyword">void</span> <span class="identifier">f</span><span class="special">(</span><span class="identifier">Attr</span><span class="special">&amp;);</span>
@@ -46,7 +41,7 @@
 <span class="keyword">void</span> <span class="identifier">f</span><span class="special">(</span><span class="identifier">Attr</span><span class="special">&amp;,</span> <span class="identifier">Context</span><span class="special">&amp;,</span> <span class="keyword">bool</span><span class="special">&amp;);</span>
 </pre>
 <p>
- You can use <tt class="computeroutput">Boost.Bind</tt>
+ You can use <code class="computeroutput">Boost.Bind</code>
           to bind member functions. For function objects, the allowed signatures
           are:
         </p>
@@ -55,7 +50,7 @@
 <span class="keyword">void</span> <span class="keyword">operator</span><span class="special">()(</span><span class="identifier">Attr</span><span class="special">&amp;,</span> <span class="identifier">Context</span><span class="special">&amp;,</span> <span class="keyword">bool</span><span class="special">&amp;)</span> <span class="keyword">const</span><span class="special">;</span>
 </pre>
 <p>
- The <tt class="computeroutput"><span class="identifier">unused_type</span></tt> is used
+ The <code class="computeroutput"><span class="identifier">unused_type</span></code> is used
           in the signatures above to signify 'don't care'.
         </p>
 </div>

Modified: trunk/libs/spirit/doc/html/spirit/karma/reference.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/karma/reference.html (original)
+++ trunk/libs/spirit/doc/html/spirit/karma/reference.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -3,12 +3,11 @@
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <title>Reference</title>
 <link rel="stylesheet" href="../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../index.html" title="Spirit 2.1">
-<link rel="up" href="../karma.html" title=" Karma">
-<link rel="previous" href="quick_reference/phoenix.html" title="Phoenix">
-<link rel="next" href="reference/generator_concepts.html" title="Generator
- Concepts">
+<link rel="up" href="../karma.html" title="Karma">
+<link rel="prev" href="quick_reference/phoenix.html" title="Phoenix">
+<link rel="next" href="reference/generator_concepts.html" title="Generator Concepts">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
 <table cellpadding="2" width="100%"><tr>
@@ -23,13 +22,10 @@
 <div class="spirit-nav">
 <a accesskey="p" href="quick_reference/phoenix.html"><img src="../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../karma.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="reference/generator_concepts.html"><img src="../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h3 class="title">
-<a name="spirit.karma.reference"></a>Reference
-</h3></div></div>
-<div></div>
-</div>
+<div class="section" title="Reference">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="spirit.karma.reference"></a><a class="link" href="reference.html" title="Reference">Reference</a>
+</h3></div></div></div>
 <div class="toc"><dl><dt><span class="section"><a href="reference/generator_concepts.html">Generator
         Concepts</a></span></dt></dl></div>
 </div>

Modified: trunk/libs/spirit/doc/html/spirit/karma/reference/generator_concepts.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/karma/reference/generator_concepts.html (original)
+++ trunk/libs/spirit/doc/html/spirit/karma/reference/generator_concepts.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -1,13 +1,12 @@
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title>Generator
- Concepts</title>
+<title>Generator Concepts</title>
 <link rel="stylesheet" href="../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../index.html" title="Spirit 2.1">
 <link rel="up" href="../reference.html" title="Reference">
-<link rel="previous" href="../reference.html" title="Reference">
+<link rel="prev" href="../reference.html" title="Reference">
 <link rel="next" href="generator_concepts/generator.html" title="Generator">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -23,15 +22,11 @@
 <div class="spirit-nav">
 <a accesskey="p" href="../reference.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../reference.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="generator_concepts/generator.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h4 class="title">
-<a name="spirit.karma.reference.generator_concepts"></a><a href="generator_concepts.html" title="Generator
- Concepts">Generator
+<div class="section" title="Generator Concepts">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="spirit.karma.reference.generator_concepts"></a><a class="link" href="generator_concepts.html" title="Generator Concepts">Generator
         Concepts</a>
-</h4></div></div>
-<div></div>
-</div>
+</h4></div></div></div>
 <div class="toc"><dl>
 <dt><span class="section">Generator</span></dt>
 <dt><span class="section">PrimitiveGenerator</span></dt>

Modified: trunk/libs/spirit/doc/html/spirit/karma/reference/generator_concepts/binarygenerator.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/karma/reference/generator_concepts/binarygenerator.html (original)
+++ trunk/libs/spirit/doc/html/spirit/karma/reference/generator_concepts/binarygenerator.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -3,11 +3,10 @@
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <title>BinaryGenerator</title>
 <link rel="stylesheet" href="../../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../../index.html" title="Spirit 2.1">
-<link rel="up" href="../generator_concepts.html" title="Generator
- Concepts">
-<link rel="previous" href="unarygenerator.html" title="UnaryGenerator">
+<link rel="up" href="../generator_concepts.html" title="Generator Concepts">
+<link rel="prev" href="unarygenerator.html" title="UnaryGenerator">
 <link rel="next" href="narygenerator.html" title="NaryGenerator">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -23,59 +22,56 @@
 <div class="spirit-nav">
 <a accesskey="p" href="unarygenerator.html"><img src="../../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../generator_concepts.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="narygenerator.html"><img src="../../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h5 class="title">
-<a name="spirit.karma.reference.generator_concepts.binarygenerator"></a>BinaryGenerator
-</h5></div></div>
-<div></div>
-</div>
+<div class="section" title="BinaryGenerator">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="spirit.karma.reference.generator_concepts.binarygenerator"></a><a class="link" href="binarygenerator.html" title="BinaryGenerator">BinaryGenerator</a>
+</h5></div></div></div>
 <a name="spirit.karma.reference.generator_concepts.binarygenerator.description"></a><h6>
-<a name="id479485"></a>
- Description
+<a name="id1090265"></a>
+ <a class="link" href="binarygenerator.html#spirit.karma.reference.generator_concepts.binarygenerator.description">Description</a>
           </h6>
 <p>
             <span class="emphasis"><em>BinaryGenerator</em></span> is a composite parser that has a
- two subjects, <tt class="computeroutput"><span class="identifier">left</span></tt> and
- <tt class="computeroutput"><span class="identifier">right</span></tt>. The BinaryGenerator
+ two subjects, <code class="computeroutput"><span class="identifier">left</span></code> and
+ <code class="computeroutput"><span class="identifier">right</span></code>. The BinaryGenerator
             allows its subjects to be treated in the same way as a single instance
- of a Generator following the Composite
+ of a <a class="link" href="generator.html" title="Generator"><code class="computeroutput"><span class="identifier">Generator</span></code></a> following the Composite
             Design Pattern.
           </p>
 <a name="spirit.karma.reference.generator_concepts.binarygenerator.refinement_of"></a><h6>
-<a name="id479566"></a>
- <a href="binarygenerator.html#spirit.karma.reference.generator_concepts.binarygenerator.refinement_of">Refinement
+<a name="id1090312"></a>
+ <a class="link" href="binarygenerator.html#spirit.karma.reference.generator_concepts.binarygenerator.refinement_of">Refinement
             of</a>
           </h6>
 <div class="blockquote"><blockquote class="blockquote">
 <p>
               </p>
 <p>
- Generator
+ <a class="link" href="generator.html" title="Generator"><code class="computeroutput"><span class="identifier">Generator</span></code></a>
               </p>
 <p>
             </p>
 </blockquote></div>
-<div class="variablelist">
+<div class="variablelist" title="Notation">
 <p class="title"><b>Notation</b></p>
 <dl>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">g</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">g</span></code></span></dt>
 <dd><p>
                 A BinaryGenerator.
               </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">G</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">G</span></code></span></dt>
 <dd><p>
                 A BinaryGenerator type.
               </p></dd>
 </dl>
 </div>
 <a name="spirit.karma.reference.generator_concepts.binarygenerator.valid_expressions"></a><h6>
-<a name="id479674"></a>
- <a href="binarygenerator.html#spirit.karma.reference.generator_concepts.binarygenerator.valid_expressions">Valid
+<a name="id1090389"></a>
+ <a class="link" href="binarygenerator.html#spirit.karma.reference.generator_concepts.binarygenerator.valid_expressions">Valid
             Expressions</a>
           </h6>
 <p>
- In addition to the requirements defined in Generator, for any BinaryGenerator
+ In addition to the requirements defined in <a class="link" href="generator.html" title="Generator"><code class="computeroutput"><span class="identifier">Generator</span></code></a>, for any BinaryGenerator
             the following must be met:
           </p>
 <div class="informaltable"><table class="table">
@@ -85,44 +81,62 @@
 <col>
 </colgroup>
 <thead><tr>
-<th><p>
+<th>
+ <p>
                     Expression
- </p></th>
-<th><p>
+ </p>
+ </th>
+<th>
+ <p>
                     Semantics
- </p></th>
-<th><p>
+ </p>
+ </th>
+<th>
+ <p>
                     Return type
- </p></th>
+ </p>
+ </th>
 </tr></thead>
 <tbody>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">g</span><span class="special">.</span><span class="identifier">left</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">g</span><span class="special">.</span><span class="identifier">left</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                     Left generator.
- </p></td>
-<td><p>
- Generator
- </p></td>
+ </p>
+ </td>
+<td>
+ <p>
+ <a class="link" href="generator.html" title="Generator"><code class="computeroutput"><span class="identifier">Generator</span></code></a>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">g</span><span class="special">.</span><span class="identifier">right</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">g</span><span class="special">.</span><span class="identifier">right</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                     Right generator.
- </p></td>
-<td><p>
- Generator
- </p></td>
+ </p>
+ </td>
+<td>
+ <p>
+ <a class="link" href="generator.html" title="Generator"><code class="computeroutput"><span class="identifier">Generator</span></code></a>
+ </p>
+ </td>
 </tr>
 </tbody>
 </table></div>
 <a name="spirit.karma.reference.generator_concepts.binarygenerator.type_expressions"></a><h6>
-<a name="id479896"></a>
- <a href="binarygenerator.html#spirit.karma.reference.generator_concepts.binarygenerator.type_expressions">Type
+<a name="id1090551"></a>
+ <a class="link" href="binarygenerator.html#spirit.karma.reference.generator_concepts.binarygenerator.type_expressions">Type
             Expressions</a>
           </h6>
 <div class="informaltable"><table class="table">
@@ -131,66 +145,82 @@
 <col>
 </colgroup>
 <thead><tr>
-<th><p>
+<th>
+ <p>
                     Expression
- </p></th>
-<th><p>
+ </p>
+ </th>
+<th>
+ <p>
                     Description
- </p></th>
+ </p>
+ </th>
 </tr></thead>
 <tbody>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">G</span><span class="special">::</span><span class="identifier">left_type</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">G</span><span class="special">::</span><span class="identifier">left_type</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                     The left parser type.
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">G</span><span class="special">::</span><span class="identifier">right_type</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">G</span><span class="special">::</span><span class="identifier">right_type</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                     The right parser type.
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">traits</span><span class="special">::</span><span class="identifier">is_binary_generator</span><span class="special">&lt;</span><span class="identifier">G</span><span class="special">&gt;::</span><span class="identifier">type</span></tt>
- </p></td>
-<td><p>
- Metafunction that evaluates to <tt class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">true_</span></tt>
- if a certain type, <tt class="computeroutput"><span class="identifier">G</span></tt>
- is a BinaryGenerator, <tt class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">false_</span></tt>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">traits</span><span class="special">::</span><span class="identifier">is_binary_generator</span><span class="special">&lt;</span><span class="identifier">G</span><span class="special">&gt;::</span><span class="identifier">type</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Metafunction that evaluates to <code class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">true_</span></code>
+ if a certain type, <code class="computeroutput"><span class="identifier">G</span></code>
+ is a BinaryGenerator, <code class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">false_</span></code>
                     otherwise (See <a href="http://www.boost.org/libs/mpl/doc/refmanual/integral-constant.html" target="_top">MPL
                     Boolean Constant</a>).
- </p></td>
+ </p>
+ </td>
 </tr>
 </tbody>
 </table></div>
 <a name="spirit.karma.reference.generator_concepts.binarygenerator.invariants"></a><h6>
-<a name="id480162"></a>
- Invariants
+<a name="id1090749"></a>
+ <a class="link" href="binarygenerator.html#spirit.karma.reference.generator_concepts.binarygenerator.invariants">Invariants</a>
           </h6>
 <p>
- For any BinaryGenerator, <tt class="computeroutput"><span class="identifier">G</span></tt>,
+ For any BinaryGenerator, <code class="computeroutput"><span class="identifier">G</span></code>,
             the following invariants always hold:
           </p>
-<div class="itemizedlist"><ul type="disc">
-<li>
-<tt class="computeroutput"><span class="identifier">traits</span><span class="special">::</span><span class="identifier">is_generator</span><span class="special">&lt;</span><span class="identifier">G</span><span class="special">::</span><span class="identifier">left_type</span><span class="special">&gt;::</span><span class="identifier">type</span></tt> evaluates to <tt class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">true_</span></tt>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem">
+<code class="computeroutput"><span class="identifier">traits</span><span class="special">::</span><span class="identifier">is_generator</span><span class="special">&lt;</span><span class="identifier">G</span><span class="special">::</span><span class="identifier">left_type</span><span class="special">&gt;::</span><span class="identifier">type</span></code> evaluates to <code class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">true_</span></code>
 </li>
-<li>
-<tt class="computeroutput"><span class="identifier">traits</span><span class="special">::</span><span class="identifier">is_generator</span><span class="special">&lt;</span><span class="identifier">G</span><span class="special">::</span><span class="identifier">right_type</span><span class="special">&gt;::</span><span class="identifier">type</span></tt> evaluates to <tt class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">true_</span></tt>
+<li class="listitem">
+<code class="computeroutput"><span class="identifier">traits</span><span class="special">::</span><span class="identifier">is_generator</span><span class="special">&lt;</span><span class="identifier">G</span><span class="special">::</span><span class="identifier">right_type</span><span class="special">&gt;::</span><span class="identifier">type</span></code> evaluates to <code class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">true_</span></code>
 </li>
 </ul></div>
 <a name="spirit.karma.reference.generator_concepts.binarygenerator.models"></a><h6>
-<a name="id480362"></a>
- Models
+<a name="id1090886"></a>
+ <a class="link" href="binarygenerator.html#spirit.karma.reference.generator_concepts.binarygenerator.models">Models</a>
           </h6>
 <p>
- <span class="bold"><b>FIXME</b></span> Add links to models of BinaryGenerator
+ <span class="bold"><strong>FIXME</strong></span> Add links to models of BinaryGenerator
             concept
           </p>
 </div>

Modified: trunk/libs/spirit/doc/html/spirit/karma/reference/generator_concepts/generator.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/karma/reference/generator_concepts/generator.html (original)
+++ trunk/libs/spirit/doc/html/spirit/karma/reference/generator_concepts/generator.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -3,12 +3,10 @@
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <title>Generator</title>
 <link rel="stylesheet" href="../../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../../index.html" title="Spirit 2.1">
-<link rel="up" href="../generator_concepts.html" title="Generator
- Concepts">
-<link rel="previous" href="../generator_concepts.html" title="Generator
- Concepts">
+<link rel="up" href="../generator_concepts.html" title="Generator Concepts">
+<link rel="prev" href="../generator_concepts.html" title="Generator Concepts">
 <link rel="next" href="primitivegenerator.html" title="PrimitiveGenerator">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -24,77 +22,74 @@
 <div class="spirit-nav">
 <a accesskey="p" href="../generator_concepts.html"><img src="../../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../generator_concepts.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="primitivegenerator.html"><img src="../../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h5 class="title">
-<a name="spirit.karma.reference.generator_concepts.generator"></a>Generator
-</h5></div></div>
-<div></div>
-</div>
+<div class="section" title="Generator">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="spirit.karma.reference.generator_concepts.generator"></a><a class="link" href="generator.html" title="Generator">Generator</a>
+</h5></div></div></div>
 <a name="spirit.karma.reference.generator_concepts.generator.description"></a><h6>
-<a name="id477159"></a>
- Description
+<a name="id1088512"></a>
+ <a class="link" href="generator.html#spirit.karma.reference.generator_concepts.generator.description">Description</a>
           </h6>
 <p>
             The <span class="emphasis"><em>Generator</em></span> is the most fundamental concept. A
- Generator has a member function, <tt class="computeroutput"><span class="identifier">generate</span></tt>,
- that accepts an <tt class="computeroutput"><span class="identifier">OutputIterator</span></tt>
+ Generator has a member function, <code class="computeroutput"><span class="identifier">generate</span></code>,
+ that accepts an <code class="computeroutput"><span class="identifier">OutputIterator</span></code>
             and returns bool as its result. The iterator receives the data being
- generated. The Generator's <tt class="computeroutput"><span class="identifier">generate</span></tt>
- member function returns <tt class="computeroutput"><span class="keyword">true</span></tt>
+ generated. The Generator's <code class="computeroutput"><span class="identifier">generate</span></code>
+ member function returns <code class="computeroutput"><span class="keyword">true</span></code>
             if the generator succeeds. Each Generator can represent a specific pattern
             or algorithm, or it can be a more complex generator formed as a composition
             of other Generator's.
           </p>
-<div class="variablelist">
+<div class="variablelist" title="Notation">
 <p class="title"><b>Notation</b></p>
 <dl>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">g</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">g</span></code></span></dt>
 <dd><p>
- A <tt class="computeroutput"><span class="identifier">Generator</span></tt>.
+ A <code class="computeroutput"><span class="identifier">Generator</span></code>.
               </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">G</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">G</span></code></span></dt>
 <dd><p>
- A <tt class="computeroutput"><span class="identifier">Generator</span></tt> type.
+ A <code class="computeroutput"><span class="identifier">Generator</span></code> type.
               </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">OutIter</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">OutIter</span></code></span></dt>
 <dd><p>
- An <tt class="computeroutput"><span class="identifier">OutputIterator</span></tt>
+ An <code class="computeroutput"><span class="identifier">OutputIterator</span></code>
                 type.
               </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">sink</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">sink</span></code></span></dt>
 <dd><p>
- An <tt class="computeroutput"><span class="identifier">OutputIterator</span></tt>
+ An <code class="computeroutput"><span class="identifier">OutputIterator</span></code>
                 instance.
               </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">Context</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">Context</span></code></span></dt>
 <dd><p>
                 The generator's Context type.
               </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">context</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">context</span></code></span></dt>
 <dd><p>
- The generator's Context, or <tt class="computeroutput"><span class="identifier">unused</span></tt>.
+ The generator's Context, or <code class="computeroutput"><span class="identifier">unused</span></code>.
               </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">delimit</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">delimit</span></code></span></dt>
 <dd><p>
- A delimiter Generator, or <tt class="computeroutput"><span class="identifier">unused</span></tt>.
+ A delimiter Generator, or <code class="computeroutput"><span class="identifier">unused</span></code>.
               </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">attr</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">attr</span></code></span></dt>
 <dd><p>
- A Compatible Attribute, or <tt class="computeroutput"><span class="identifier">unused</span></tt>.
+ A Compatible Attribute, or <code class="computeroutput"><span class="identifier">unused</span></code>.
               </p></dd>
 </dl>
 </div>
 <a name="spirit.karma.reference.generator_concepts.generator.valid_expressions"></a><h6>
-<a name="id477526"></a>
- <a href="generator.html#spirit.karma.reference.generator_concepts.generator.valid_expressions">Valid
+<a name="id1088766"></a>
+ <a class="link" href="generator.html#spirit.karma.reference.generator_concepts.generator.valid_expressions">Valid
             Expressions</a>
           </h6>
 <p>
- In the expressions below, the behavior of the generator, <tt class="computeroutput"><span class="identifier">g</span></tt>, as well as how <tt class="computeroutput"><span class="identifier">delimit</span></tt>
- and <tt class="computeroutput"><span class="identifier">attr</span></tt> are handled
- by <tt class="computeroutput"><span class="identifier">g</span></tt>, are left unspecified
- in the base <tt class="computeroutput"><span class="identifier">Generator</span></tt>
+ In the expressions below, the behavior of the generator, <code class="computeroutput"><span class="identifier">g</span></code>, as well as how <code class="computeroutput"><span class="identifier">delimit</span></code>
+ and <code class="computeroutput"><span class="identifier">attr</span></code> are handled
+ by <code class="computeroutput"><span class="identifier">g</span></code>, are left unspecified
+ in the base <code class="computeroutput"><span class="identifier">Generator</span></code>
             concept. These are specified in subsequent, more refined concepts and
             by the actual models therof.
           </p>
@@ -108,53 +103,69 @@
 <col>
 </colgroup>
 <thead><tr>
-<th><p>
+<th>
+ <p>
                     Expression
- </p></th>
-<th><p>
+ </p>
+ </th>
+<th>
+ <p>
                     Semantics
- </p></th>
-<th><p>
+ </p>
+ </th>
+<th>
+ <p>
                     Return type
- </p></th>
+ </p>
+ </th>
 </tr></thead>
 <tbody>
 <tr>
 <td>
-<p>
+ <p>
                     
 </p>
 <pre xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="table-programlisting"><span class="identifier">g</span><span class="special">.</span><span class="identifier">generate</span><span class="special">(</span><span class="identifier">sink</span><span class="special">,</span> <span class="identifier">context</span><span class="special">,</span> <span class="identifier">delimit</span><span class="special">,</span> <span class="identifier">attr</span><span class="special">)</span></pre>
 <p>
                   </p>
-</td>
-<td><p>
+ </td>
+<td>
+ <p>
                     Generate the output sequence by inserting the generated characters/tokens
- into <tt class="computeroutput"><span class="identifier">sink</span></tt>. Use
- the <tt class="computeroutput"><span class="identifier">delimit</span></tt> generator
- for delimiting. Return <tt class="computeroutput"><span class="keyword">true</span></tt>
- if successful, otherwise return <tt class="computeroutput"><span class="keyword">false</span></tt>.
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="keyword">bool</span></tt>
- </p></td>
+ into <code class="computeroutput"><span class="identifier">sink</span></code>. Use
+ the <code class="computeroutput"><span class="identifier">delimit</span></code> generator
+ for delimiting. Return <code class="computeroutput"><span class="keyword">true</span></code>
+ if successful, otherwise return <code class="computeroutput"><span class="keyword">false</span></code>.
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="keyword">bool</span></code>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">g</span><span class="special">.</span><span class="identifier">what</span><span class="special">(</span><span class="identifier">context</span><span class="special">)</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">g</span><span class="special">.</span><span class="identifier">what</span><span class="special">(</span><span class="identifier">context</span><span class="special">)</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                     Get information about a Generator.
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">info</span></tt>
- </p></td>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">info</span></code>
+ </p>
+ </td>
 </tr>
 </tbody>
 </table></div>
 <a name="spirit.karma.reference.generator_concepts.generator.type_expressions"></a><h6>
-<a name="id477895"></a>
- <a href="generator.html#spirit.karma.reference.generator_concepts.generator.type_expressions">Type
+<a name="id1089026"></a>
+ <a class="link" href="generator.html#spirit.karma.reference.generator_concepts.generator.type_expressions">Type
             Expressions</a>
           </h6>
 <div class="informaltable"><table class="table">
@@ -163,61 +174,73 @@
 <col>
 </colgroup>
 <thead><tr>
-<th><p>
+<th>
+ <p>
                     Expression
- </p></th>
-<th><p>
+ </p>
+ </th>
+<th>
+ <p>
                     Description
- </p></th>
+ </p>
+ </th>
 </tr></thead>
 <tbody>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">G</span><span class="special">::</span><span class="keyword">template</span> <span class="identifier">attribute</span><span class="special">&lt;</span><span class="identifier">Context</span><span class="special">&gt;::</span><span class="identifier">type</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">G</span><span class="special">::</span><span class="keyword">template</span> <span class="identifier">attribute</span><span class="special">&lt;</span><span class="identifier">Context</span><span class="special">&gt;::</span><span class="identifier">type</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                     The Generator's attribute.
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">traits</span><span class="special">::</span><span class="identifier">is_generator</span><span class="special">&lt;</span><span class="identifier">G</span><span class="special">&gt;::</span><span class="identifier">type</span></tt>
- </p></td>
-<td><p>
- Metafunction that evaluates to <tt class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">true_</span></tt>
- if a certain type, <tt class="computeroutput"><span class="identifier">G</span></tt>
- is a Generator, <tt class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">false_</span></tt>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">traits</span><span class="special">::</span><span class="identifier">is_generator</span><span class="special">&lt;</span><span class="identifier">G</span><span class="special">&gt;::</span><span class="identifier">type</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Metafunction that evaluates to <code class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">true_</span></code>
+ if a certain type, <code class="computeroutput"><span class="identifier">G</span></code>
+ is a Generator, <code class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">false_</span></code>
                     otherwise (See <a href="http://www.boost.org/libs/mpl/doc/refmanual/integral-constant.html" target="_top">MPL
                     Boolean Constant</a>).
- </p></td>
+ </p>
+ </td>
 </tr>
 </tbody>
 </table></div>
 <a name="spirit.karma.reference.generator_concepts.generator.postcondition"></a><h6>
-<a name="id478148"></a>
- Postcondition
+<a name="id1089210"></a>
+ <a class="link" href="generator.html#spirit.karma.reference.generator_concepts.generator.postcondition">Postcondition</a>
           </h6>
 <p>
- Upon return from <tt class="computeroutput"><span class="identifier">g</span><span class="special">.</span><span class="identifier">generate</span></tt> the following post conditions
+ Upon return from <code class="computeroutput"><span class="identifier">g</span><span class="special">.</span><span class="identifier">generate</span></code> the following post conditions
             should hold:
           </p>
-<div class="itemizedlist"><ul type="disc">
-<li>
- On successful generation, <tt class="computeroutput"><span class="identifier">sink</span></tt>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem">
+ On successful generation, <code class="computeroutput"><span class="identifier">sink</span></code>
               received the generated characters/tokens seqeunce.
             </li>
-<li>
- No pre-delimits: <tt class="computeroutput"><span class="identifier">delimit</span></tt>
+<li class="listitem">
+ No pre-delimits: <code class="computeroutput"><span class="identifier">delimit</span></code>
               characters/tokens will not be emitted in front of any other output.
             </li>
-<li>
- The attribute <tt class="computeroutput"><span class="identifier">attr</span></tt>
+<li class="listitem">
+ The attribute <code class="computeroutput"><span class="identifier">attr</span></code>
               has not been modified.
             </li>
 </ul></div>
 <a name="spirit.karma.reference.generator_concepts.generator.models"></a><h6>
-<a name="id478254"></a>
- Models
+<a name="id1089280"></a>
+ <a class="link" href="generator.html#spirit.karma.reference.generator_concepts.generator.models">Models</a>
           </h6>
 <p>
             All generators in <span class="emphasis"><em>Spirit.Karma</em></span> are models of the

Modified: trunk/libs/spirit/doc/html/spirit/karma/reference/generator_concepts/narygenerator.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/karma/reference/generator_concepts/narygenerator.html (original)
+++ trunk/libs/spirit/doc/html/spirit/karma/reference/generator_concepts/narygenerator.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -3,12 +3,11 @@
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <title>NaryGenerator</title>
 <link rel="stylesheet" href="../../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../../index.html" title="Spirit 2.1">
-<link rel="up" href="../generator_concepts.html" title="Generator
- Concepts">
-<link rel="previous" href="binarygenerator.html" title="BinaryGenerator">
-<link rel="next" href="../../../lex.html" title=" Spirit.Lex">
+<link rel="up" href="../generator_concepts.html" title="Generator Concepts">
+<link rel="prev" href="binarygenerator.html" title="BinaryGenerator">
+<link rel="next" href="../../../lex.html" title="Spirit.Lex">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
 <table cellpadding="2" width="100%"><tr>
@@ -23,57 +22,54 @@
 <div class="spirit-nav">
 <a accesskey="p" href="binarygenerator.html"><img src="../../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../generator_concepts.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="../../../lex.html"><img src="../../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h5 class="title">
-<a name="spirit.karma.reference.generator_concepts.narygenerator"></a>NaryGenerator
-</h5></div></div>
-<div></div>
-</div>
+<div class="section" title="NaryGenerator">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="spirit.karma.reference.generator_concepts.narygenerator"></a><a class="link" href="narygenerator.html" title="NaryGenerator">NaryGenerator</a>
+</h5></div></div></div>
 <a name="spirit.karma.reference.generator_concepts.narygenerator.description"></a><h6>
-<a name="id480419"></a>
- Description
+<a name="id1090918"></a>
+ <a class="link" href="narygenerator.html#spirit.karma.reference.generator_concepts.narygenerator.description">Description</a>
           </h6>
 <p>
             <span class="emphasis"><em>NaryGenerator</em></span> is a composite generator that has
             one or more subjects. The NaryGenerator allows its subjects to be treated
- in the same way as a single instance of a Generator following the Composite
+ in the same way as a single instance of a <a class="link" href="generator.html" title="Generator"><code class="computeroutput"><span class="identifier">Generator</span></code></a> following the Composite
             Design Pattern.
           </p>
 <a name="spirit.karma.reference.generator_concepts.narygenerator.refinement_of"></a><h6>
-<a name="id480474"></a>
- <a href="narygenerator.html#spirit.karma.reference.generator_concepts.narygenerator.refinement_of">Refinement
+<a name="id1090949"></a>
+ <a class="link" href="narygenerator.html#spirit.karma.reference.generator_concepts.narygenerator.refinement_of">Refinement
             of</a>
           </h6>
 <div class="blockquote"><blockquote class="blockquote">
 <p>
               </p>
 <p>
- Generator
+ <a class="link" href="generator.html" title="Generator"><code class="computeroutput"><span class="identifier">Generator</span></code></a>
               </p>
 <p>
             </p>
 </blockquote></div>
-<div class="variablelist">
+<div class="variablelist" title="Notation">
 <p class="title"><b>Notation</b></p>
 <dl>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">g</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">g</span></code></span></dt>
 <dd><p>
                 A NaryGenerator.
               </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">G</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">G</span></code></span></dt>
 <dd><p>
                 A NaryGenerator type.
               </p></dd>
 </dl>
 </div>
 <a name="spirit.karma.reference.generator_concepts.narygenerator.valid_expressions"></a><h6>
-<a name="id480582"></a>
- <a href="narygenerator.html#spirit.karma.reference.generator_concepts.narygenerator.valid_expressions">Valid
+<a name="id1091026"></a>
+ <a class="link" href="narygenerator.html#spirit.karma.reference.generator_concepts.narygenerator.valid_expressions">Valid
             Expressions</a>
           </h6>
 <p>
- In addition to the requirements defined in Generator, for any NaryGenerator
+ In addition to the requirements defined in <a class="link" href="generator.html" title="Generator"><code class="computeroutput"><span class="identifier">Generator</span></code></a>, for any NaryGenerator
             the following must be met:
           </p>
 <div class="informaltable"><table class="table">
@@ -83,32 +79,44 @@
 <col>
 </colgroup>
 <thead><tr>
-<th><p>
+<th>
+ <p>
                     Expression
- </p></th>
-<th><p>
+ </p>
+ </th>
+<th>
+ <p>
                     Semantics
- </p></th>
-<th><p>
+ </p>
+ </th>
+<th>
+ <p>
                     Return type
- </p></th>
+ </p>
+ </th>
 </tr></thead>
 <tbody><tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">g</span><span class="special">.</span><span class="identifier">elements</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">g</span><span class="special">.</span><span class="identifier">elements</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                     The tuple of elements.
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
                     A Fusion
- Sequence of Generator types.
- </p></td>
+ Sequence of <a class="link" href="generator.html" title="Generator"><code class="computeroutput"><span class="identifier">Generator</span></code></a> types.
+ </p>
+ </td>
 </tr></tbody>
 </table></div>
 <a name="spirit.karma.reference.generator_concepts.narygenerator.type_expressions"></a><h6>
-<a name="id480750"></a>
- <a href="narygenerator.html#spirit.karma.reference.generator_concepts.narygenerator.type_expressions">Type
+<a name="id1091146"></a>
+ <a class="link" href="narygenerator.html#spirit.karma.reference.generator_concepts.narygenerator.type_expressions">Type
             Expressions</a>
           </h6>
 <div class="informaltable"><table class="table">
@@ -117,54 +125,66 @@
 <col>
 </colgroup>
 <thead><tr>
-<th><p>
+<th>
+ <p>
                     Expression
- </p></th>
-<th><p>
+ </p>
+ </th>
+<th>
+ <p>
                     Description
- </p></th>
+ </p>
+ </th>
 </tr></thead>
 <tbody>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">g</span><span class="special">.</span><span class="identifier">elements_type</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">g</span><span class="special">.</span><span class="identifier">elements_type</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                     Elements tuple type.
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">traits</span><span class="special">::</span><span class="identifier">is_nary_generator</span><span class="special">&lt;</span><span class="identifier">G</span><span class="special">&gt;::</span><span class="identifier">type</span></tt>
- </p></td>
-<td><p>
- Metafunction that evaluates to <tt class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">true_</span></tt>
- if a certain type, <tt class="computeroutput"><span class="identifier">G</span></tt>
- is a NaryGenerator, <tt class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">false_</span></tt>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">traits</span><span class="special">::</span><span class="identifier">is_nary_generator</span><span class="special">&lt;</span><span class="identifier">G</span><span class="special">&gt;::</span><span class="identifier">type</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Metafunction that evaluates to <code class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">true_</span></code>
+ if a certain type, <code class="computeroutput"><span class="identifier">G</span></code>
+ is a NaryGenerator, <code class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">false_</span></code>
                     otherwise (See <a href="http://www.boost.org/libs/mpl/doc/refmanual/integral-constant.html" target="_top">MPL
                     Boolean Constant</a>).
- </p></td>
+ </p>
+ </td>
 </tr>
 </tbody>
 </table></div>
 <a name="spirit.karma.reference.generator_concepts.narygenerator.invariants"></a><h6>
-<a name="id480977"></a>
- Invariants
+<a name="id1091312"></a>
+ <a class="link" href="narygenerator.html#spirit.karma.reference.generator_concepts.narygenerator.invariants">Invariants</a>
           </h6>
 <p>
- For each element, <tt class="computeroutput"><span class="identifier">E</span></tt>,
- in any NaryGenerator, <tt class="computeroutput"><span class="identifier">G</span></tt>,
+ For each element, <code class="computeroutput"><span class="identifier">E</span></code>,
+ in any NaryGenerator, <code class="computeroutput"><span class="identifier">G</span></code>,
             the following invariant always holds:
           </p>
-<div class="itemizedlist"><ul type="disc"><li>
-<tt class="computeroutput"><span class="identifier">traits</span><span class="special">::</span><span class="identifier">is_generator</span><span class="special">&lt;</span><span class="identifier">E</span><span class="special">&gt;::</span><span class="identifier">type</span></tt> evaluates to <tt class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">true_</span></tt>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">
+<code class="computeroutput"><span class="identifier">traits</span><span class="special">::</span><span class="identifier">is_generator</span><span class="special">&lt;</span><span class="identifier">E</span><span class="special">&gt;::</span><span class="identifier">type</span></code> evaluates to <code class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">true_</span></code>
 </li></ul></div>
 <a name="spirit.karma.reference.generator_concepts.narygenerator.models"></a><h6>
-<a name="id481101"></a>
- Models
+<a name="id1091397"></a>
+ <a class="link" href="narygenerator.html#spirit.karma.reference.generator_concepts.narygenerator.models">Models</a>
           </h6>
 <p>
- <span class="bold"><b>FIXME</b></span> Add links to models of NaryGenerator
+ <span class="bold"><strong>FIXME</strong></span> Add links to models of NaryGenerator
             concept
           </p>
 </div>

Modified: trunk/libs/spirit/doc/html/spirit/karma/reference/generator_concepts/primitivegenerator.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/karma/reference/generator_concepts/primitivegenerator.html (original)
+++ trunk/libs/spirit/doc/html/spirit/karma/reference/generator_concepts/primitivegenerator.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -3,11 +3,10 @@
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <title>PrimitiveGenerator</title>
 <link rel="stylesheet" href="../../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../../index.html" title="Spirit 2.1">
-<link rel="up" href="../generator_concepts.html" title="Generator
- Concepts">
-<link rel="previous" href="generator.html" title="Generator">
+<link rel="up" href="../generator_concepts.html" title="Generator Concepts">
+<link rel="prev" href="generator.html" title="Generator">
 <link rel="next" href="unarygenerator.html" title="UnaryGenerator">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -23,51 +22,48 @@
 <div class="spirit-nav">
 <a accesskey="p" href="generator.html"><img src="../../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../generator_concepts.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="unarygenerator.html"><img src="../../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h5 class="title">
-<a name="spirit.karma.reference.generator_concepts.primitivegenerator"></a>PrimitiveGenerator
-</h5></div></div>
-<div></div>
-</div>
+<div class="section" title="PrimitiveGenerator">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="spirit.karma.reference.generator_concepts.primitivegenerator"></a><a class="link" href="primitivegenerator.html" title="PrimitiveGenerator">PrimitiveGenerator</a>
+</h5></div></div></div>
 <a name="spirit.karma.reference.generator_concepts.primitivegenerator.description"></a><h6>
-<a name="id478315"></a>
- Description
+<a name="id1089322"></a>
+ <a class="link" href="primitivegenerator.html#spirit.karma.reference.generator_concepts.primitivegenerator.description">Description</a>
           </h6>
 <p>
             <span class="emphasis"><em>PrimitiveGenerator</em></span> is the most basic building block
             that the client uses to build more complex generators.
           </p>
 <a name="spirit.karma.reference.generator_concepts.primitivegenerator.refinement_of"></a><h6>
-<a name="id478351"></a>
- <a href="primitivegenerator.html#spirit.karma.reference.generator_concepts.primitivegenerator.refinement_of">Refinement
+<a name="id1089342"></a>
+ <a class="link" href="primitivegenerator.html#spirit.karma.reference.generator_concepts.primitivegenerator.refinement_of">Refinement
             of</a>
           </h6>
 <div class="blockquote"><blockquote class="blockquote">
 <p>
               </p>
 <p>
- Generator
+ <a class="link" href="generator.html" title="Generator"><code class="computeroutput"><span class="identifier">Generator</span></code></a>
               </p>
 <p>
             </p>
 </blockquote></div>
 <a name="spirit.karma.reference.generator_concepts.primitivegenerator.post_delimit"></a><h6>
-<a name="id478407"></a>
- Post-delimit
+<a name="id1089376"></a>
+ <a class="link" href="primitivegenerator.html#spirit.karma.reference.generator_concepts.primitivegenerator.post_delimit">Post-delimit</a>
           </h6>
 <p>
- Before exiting the <tt class="computeroutput"><span class="identifier">generate</span></tt>
+ Before exiting the <code class="computeroutput"><span class="identifier">generate</span></code>
             member function, a PrimitiveGenerator is required to do a post-delimit.
             This will generate a single delimiting character/token sequence. Only
             PrimitiveGenerator's are required to perform this post-delimit. This
- is typically carried out through a call to <tt class="computeroutput"><span class="identifier">karma</span><span class="special">::</span><span class="identifier">delimit_out</span></tt>:
+ is typically carried out through a call to <code class="computeroutput"><span class="identifier">karma</span><span class="special">::</span><span class="identifier">delimit_out</span></code>:
           </p>
 <pre class="programlisting"><span class="identifier">karma</span><span class="special">::</span><span class="identifier">delimit_out</span><span class="special">(</span><span class="identifier">sink</span><span class="special">,</span> <span class="identifier">delimit</span><span class="special">);</span>
 </pre>
 <a name="spirit.karma.reference.generator_concepts.primitivegenerator.type_expressions"></a><h6>
-<a name="id478526"></a>
- <a href="primitivegenerator.html#spirit.karma.reference.generator_concepts.primitivegenerator.type_expressions">Type
+<a name="id1089449"></a>
+ <a class="link" href="primitivegenerator.html#spirit.karma.reference.generator_concepts.primitivegenerator.type_expressions">Type
             Expressions</a>
           </h6>
 <div class="informaltable"><table class="table">
@@ -76,32 +72,40 @@
 <col>
 </colgroup>
 <thead><tr>
-<th><p>
+<th>
+ <p>
                     Expression
- </p></th>
-<th><p>
+ </p>
+ </th>
+<th>
+ <p>
                     Description
- </p></th>
+ </p>
+ </th>
 </tr></thead>
 <tbody><tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">traits</span><span class="special">::</span><span class="identifier">is_primitive_generator</span><span class="special">&lt;</span><span class="identifier">G</span><span class="special">&gt;::</span><span class="identifier">type</span></tt>
- </p></td>
-<td><p>
- Metafunction that evaluates to <tt class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">true_</span></tt>
- if a certain type, <tt class="computeroutput"><span class="identifier">G</span></tt>,
- is a PrimitiveGenerator, <tt class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">false_</span></tt>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">traits</span><span class="special">::</span><span class="identifier">is_primitive_generator</span><span class="special">&lt;</span><span class="identifier">G</span><span class="special">&gt;::</span><span class="identifier">type</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Metafunction that evaluates to <code class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">true_</span></code>
+ if a certain type, <code class="computeroutput"><span class="identifier">G</span></code>,
+ is a PrimitiveGenerator, <code class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">false_</span></code>
                     otherwise (See <a href="http://www.boost.org/libs/mpl/doc/refmanual/integral-constant.html" target="_top">MPL
                     Boolean Constant</a>).
- </p></td>
+ </p>
+ </td>
 </tr></tbody>
 </table></div>
 <a name="spirit.karma.reference.generator_concepts.primitivegenerator.models"></a><h6>
-<a name="id478715"></a>
- Models
+<a name="id1089723"></a>
+ <a class="link" href="primitivegenerator.html#spirit.karma.reference.generator_concepts.primitivegenerator.models">Models</a>
           </h6>
 <p>
- <span class="bold"><b>FIXME</b></span> Add links to <span class="emphasis"><em>PrimitiveGenerator</em></span>
+ <span class="bold"><strong>FIXME</strong></span> Add links to <span class="emphasis"><em>PrimitiveGenerator</em></span>
             models here.
           </p>
 </div>

Modified: trunk/libs/spirit/doc/html/spirit/karma/reference/generator_concepts/unarygenerator.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/karma/reference/generator_concepts/unarygenerator.html (original)
+++ trunk/libs/spirit/doc/html/spirit/karma/reference/generator_concepts/unarygenerator.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -3,11 +3,10 @@
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <title>UnaryGenerator</title>
 <link rel="stylesheet" href="../../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../../index.html" title="Spirit 2.1">
-<link rel="up" href="../generator_concepts.html" title="Generator
- Concepts">
-<link rel="previous" href="primitivegenerator.html" title="PrimitiveGenerator">
+<link rel="up" href="../generator_concepts.html" title="Generator Concepts">
+<link rel="prev" href="primitivegenerator.html" title="PrimitiveGenerator">
 <link rel="next" href="binarygenerator.html" title="BinaryGenerator">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -23,16 +22,13 @@
 <div class="spirit-nav">
 <a accesskey="p" href="primitivegenerator.html"><img src="../../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../generator_concepts.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="binarygenerator.html"><img src="../../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h5 class="title">
-<a name="spirit.karma.reference.generator_concepts.unarygenerator"></a>UnaryGenerator
-</h5></div></div>
-<div></div>
-</div>
+<div class="section" title="UnaryGenerator">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="spirit.karma.reference.generator_concepts.unarygenerator"></a><a class="link" href="unarygenerator.html" title="UnaryGenerator">UnaryGenerator</a>
+</h5></div></div></div>
 <a name="spirit.karma.reference.generator_concepts.unarygenerator.description"></a><h6>
-<a name="id478775"></a>
- Description
+<a name="id1089764"></a>
+ <a class="link" href="unarygenerator.html#spirit.karma.reference.generator_concepts.unarygenerator.description">Description</a>
           </h6>
 <p>
             <span class="emphasis"><em>UnaryGenerator</em></span> is a composite generator that has
@@ -40,39 +36,39 @@
             following the Delegate Design Pattern.
           </p>
 <a name="spirit.karma.reference.generator_concepts.unarygenerator.refinement_of"></a><h6>
-<a name="id478811"></a>
- <a href="unarygenerator.html#spirit.karma.reference.generator_concepts.unarygenerator.refinement_of">Refinement
+<a name="id1089784"></a>
+ <a class="link" href="unarygenerator.html#spirit.karma.reference.generator_concepts.unarygenerator.refinement_of">Refinement
             of</a>
           </h6>
 <div class="blockquote"><blockquote class="blockquote">
 <p>
               </p>
 <p>
- Generator
+ <a class="link" href="generator.html" title="Generator"><code class="computeroutput"><span class="identifier">Generator</span></code></a>
               </p>
 <p>
             </p>
 </blockquote></div>
-<div class="variablelist">
+<div class="variablelist" title="Notation">
 <p class="title"><b>Notation</b></p>
 <dl>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">g</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">g</span></code></span></dt>
 <dd><p>
                 A UnaryGenerator.
               </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">G</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">G</span></code></span></dt>
 <dd><p>
                 A UnaryGenerator type.
               </p></dd>
 </dl>
 </div>
 <a name="spirit.karma.reference.generator_concepts.unarygenerator.valid_expressions"></a><h6>
-<a name="id478920"></a>
- <a href="unarygenerator.html#spirit.karma.reference.generator_concepts.unarygenerator.valid_expressions">Valid
+<a name="id1089861"></a>
+ <a class="link" href="unarygenerator.html#spirit.karma.reference.generator_concepts.unarygenerator.valid_expressions">Valid
             Expressions</a>
           </h6>
 <p>
- In addition to the requirements defined in Generator, for any UnaryGenerator
+ In addition to the requirements defined in <a class="link" href="generator.html" title="Generator"><code class="computeroutput"><span class="identifier">Generator</span></code></a>, for any UnaryGenerator
             the following must be met:
           </p>
 <div class="informaltable"><table class="table">
@@ -82,31 +78,43 @@
 <col>
 </colgroup>
 <thead><tr>
-<th><p>
+<th>
+ <p>
                     Expression
- </p></th>
-<th><p>
+ </p>
+ </th>
+<th>
+ <p>
                     Semantics
- </p></th>
-<th><p>
+ </p>
+ </th>
+<th>
+ <p>
                     Return type
- </p></th>
+ </p>
+ </th>
 </tr></thead>
 <tbody><tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">g</span><span class="special">.</span><span class="identifier">subject</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">g</span><span class="special">.</span><span class="identifier">subject</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                     Subject generator.
- </p></td>
-<td><p>
- Generator
- </p></td>
+ </p>
+ </td>
+<td>
+ <p>
+ <a class="link" href="generator.html" title="Generator"><code class="computeroutput"><span class="identifier">Generator</span></code></a>
+ </p>
+ </td>
 </tr></tbody>
 </table></div>
 <a name="spirit.karma.reference.generator_concepts.unarygenerator.type_expressions"></a><h6>
-<a name="id479079"></a>
- <a href="unarygenerator.html#spirit.karma.reference.generator_concepts.unarygenerator.type_expressions">Type
+<a name="id1089976"></a>
+ <a class="link" href="unarygenerator.html#spirit.karma.reference.generator_concepts.unarygenerator.type_expressions">Type
             Expressions</a>
           </h6>
 <div class="informaltable"><table class="table">
@@ -115,53 +123,65 @@
 <col>
 </colgroup>
 <thead><tr>
-<th><p>
+<th>
+ <p>
                     Expression
- </p></th>
-<th><p>
+ </p>
+ </th>
+<th>
+ <p>
                     Description
- </p></th>
+ </p>
+ </th>
 </tr></thead>
 <tbody>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">G</span><span class="special">::</span><span class="identifier">subject_type</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">G</span><span class="special">::</span><span class="identifier">subject_type</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                     The subject generator type.
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">traits</span><span class="special">::</span><span class="identifier">is_unary_generator</span><span class="special">&lt;</span><span class="identifier">G</span><span class="special">&gt;::</span><span class="identifier">type</span></tt>
- </p></td>
-<td><p>
- Metafunction that evaluates to <tt class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">true_</span></tt>
- if a certain type, <tt class="computeroutput"><span class="identifier">G</span></tt>
- is a UnaryGenerator, <tt class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">false_</span></tt>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">traits</span><span class="special">::</span><span class="identifier">is_unary_generator</span><span class="special">&lt;</span><span class="identifier">G</span><span class="special">&gt;::</span><span class="identifier">type</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Metafunction that evaluates to <code class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">true_</span></code>
+ if a certain type, <code class="computeroutput"><span class="identifier">G</span></code>
+ is a UnaryGenerator, <code class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">false_</span></code>
                     otherwise (See <a href="http://www.boost.org/libs/mpl/doc/refmanual/integral-constant.html" target="_top">MPL
                     Boolean Constant</a>).
- </p></td>
+ </p>
+ </td>
 </tr>
 </tbody>
 </table></div>
 <a name="spirit.karma.reference.generator_concepts.unarygenerator.invariants"></a><h6>
-<a name="id479305"></a>
- Invariants
+<a name="id1090141"></a>
+ <a class="link" href="unarygenerator.html#spirit.karma.reference.generator_concepts.unarygenerator.invariants">Invariants</a>
           </h6>
 <p>
- For any UnaryGenerator, <tt class="computeroutput"><span class="identifier">G</span></tt>,
+ For any UnaryGenerator, <code class="computeroutput"><span class="identifier">G</span></code>,
             the following invariant always holds:
           </p>
-<div class="itemizedlist"><ul type="disc"><li>
-<tt class="computeroutput"><span class="identifier">traits</span><span class="special">::</span><span class="identifier">is_generator</span><span class="special">&lt;</span><span class="identifier">G</span><span class="special">::</span><span class="identifier">subject_type</span><span class="special">&gt;::</span><span class="identifier">type</span></tt> evaluates to <tt class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">true_</span></tt>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">
+<code class="computeroutput"><span class="identifier">traits</span><span class="special">::</span><span class="identifier">is_generator</span><span class="special">&lt;</span><span class="identifier">G</span><span class="special">::</span><span class="identifier">subject_type</span><span class="special">&gt;::</span><span class="identifier">type</span></code> evaluates to <code class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">true_</span></code>
 </li></ul></div>
 <a name="spirit.karma.reference.generator_concepts.unarygenerator.models"></a><h6>
-<a name="id479428"></a>
- Models
+<a name="id1090226"></a>
+ <a class="link" href="unarygenerator.html#spirit.karma.reference.generator_concepts.unarygenerator.models">Models</a>
           </h6>
 <p>
- <span class="bold"><b>FIXME</b></span> Add links to models of UnaryGenerator
+ <span class="bold"><strong>FIXME</strong></span> Add links to models of UnaryGenerator
             concept
           </p>
 </div>

Modified: trunk/libs/spirit/doc/html/spirit/karma/tutorials.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/karma/tutorials.html (original)
+++ trunk/libs/spirit/doc/html/spirit/karma/tutorials.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -3,10 +3,10 @@
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <title>Tutorials</title>
 <link rel="stylesheet" href="../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../index.html" title="Spirit 2.1">
-<link rel="up" href="../karma.html" title=" Karma">
-<link rel="previous" href="../karma.html" title=" Karma">
+<link rel="up" href="../karma.html" title="Karma">
+<link rel="prev" href="../karma.html" title="Karma">
 <link rel="next" href="tutorials/quick_start.html" title="Quick Start">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -22,13 +22,10 @@
 <div class="spirit-nav">
 <a accesskey="p" href="../karma.html"><img src="../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../karma.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="tutorials/quick_start.html"><img src="../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h3 class="title">
-<a name="spirit.karma.tutorials"></a>Tutorials
-</h3></div></div>
-<div></div>
-</div>
+<div class="section" title="Tutorials">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="spirit.karma.tutorials"></a><a class="link" href="tutorials.html" title="Tutorials">Tutorials</a>
+</h3></div></div></div>
 <div class="toc"><dl>
 <dt><span class="section">Quick Start</span></dt>
 <dt><span class="section">Warming up</span></dt>

Modified: trunk/libs/spirit/doc/html/spirit/karma/tutorials/complex___a_first_more_complex_generator.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/karma/tutorials/complex___a_first_more_complex_generator.html (original)
+++ trunk/libs/spirit/doc/html/spirit/karma/tutorials/complex___a_first_more_complex_generator.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -1,13 +1,12 @@
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title>Complex
- - A first more complex generator</title>
+<title>Complex - A first more complex generator</title>
 <link rel="stylesheet" href="../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../index.html" title="Spirit 2.1">
 <link rel="up" href="../tutorials.html" title="Tutorials">
-<link rel="previous" href="semantic_actions.html" title="Semantic Actions">
+<link rel="prev" href="semantic_actions.html" title="Semantic Actions">
 <link rel="next" href="../quick_reference.html" title="Quick Reference">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -23,21 +22,17 @@
 <div class="spirit-nav">
 <a accesskey="p" href="semantic_actions.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../tutorials.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="../quick_reference.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h4 class="title">
-<a name="spirit.karma.tutorials.complex___a_first_more_complex_generator"></a><a href="complex___a_first_more_complex_generator.html" title="Complex
- - A first more complex generator">Complex
+<div class="section" title="Complex - A first more complex generator">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="spirit.karma.tutorials.complex___a_first_more_complex_generator"></a><a class="link" href="complex___a_first_more_complex_generator.html" title="Complex - A first more complex generator">Complex
         - A first more complex generator</a>
-</h4></div></div>
-<div></div>
-</div>
+</h4></div></div></div>
 <p>
           In this section we will develop a generator for complex numbers, allowing
- to represent a <tt class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">complex</span></tt> either as <tt class="computeroutput"><span class="string">"(real,
- imag)"</span></tt> (where <tt class="computeroutput"><span class="identifier">real</span></tt>
- and <tt class="computeroutput"><span class="identifier">imag</span></tt> are the real and
- imaginary parts of the complex number) or as a simple <tt class="computeroutput"><span class="identifier">real</span></tt>
+ to represent a <code class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">complex</span></code> either as <code class="computeroutput"><span class="string">"(real,
+ imag)"</span></code> (where <code class="computeroutput"><span class="identifier">real</span></code>
+ and <code class="computeroutput"><span class="identifier">imag</span></code> are the real and
+ imaginary parts of the complex number) or as a simple <code class="computeroutput"><span class="identifier">real</span></code>
           if the imaginary part happens ot be equal to zero. This example will highlight
           the power of <span class="emphasis"><em>Spirit.Karma</em></span> allowing to combine compile
           time definition of formatting rules with runtime based decisions which
@@ -56,7 +51,7 @@
           where the first alternative should be used for numbers having a non-zero
           imaginary part, while the second is for real numbers. Generally, alternatives
           are tried in the sequence of their definition as long as one of the expressions
- (as delimited by <tt class="computeroutput"><span class="char">'|'</span></tt>) succeeds.
+ (as delimited by <code class="computeroutput"><span class="char">'|'</span></code>) succeeds.
           If no generator expression succeeds the whole alternative fails.
         </p>
 <p>
@@ -66,7 +61,7 @@
           alternative will be chosen instead. The decision about whether to choose
           the first alternative has to be made at runtime as only then we actually
           know the value of the imaginary part of the complex number. <span class="emphasis"><em>Spirit.Karma</em></span>
- provides us with with a primitive generator <tt class="computeroutput"><span class="identifier">eps</span><span class="special">()</span></tt>, which is usable as a semantic predicate.
+ provides us with with a primitive generator <code class="computeroutput"><span class="identifier">eps</span><span class="special">()</span></code>, which is usable as a semantic predicate.
           It has the property to 'succeed' generating only if its argument is true
           (while it never generates any output on its own).
         </p>
@@ -114,7 +109,7 @@
 <p>
         </p>
 <p>
- The <tt class="computeroutput"><span class="identifier">double_</span></tt> generators
+ The <code class="computeroutput"><span class="identifier">double_</span></code> generators
           have this action attached:
         </p>
 <pre class="programlisting"><span class="identifier">_1</span> <span class="special">=</span> <span class="identifier">n</span>
@@ -124,7 +119,7 @@
           before the corresponding generator is invoked and they are expected to
           provide the generator with the data to be used. The semantic action above
           assigns the value to be generated (n) to the generator (actually, the attribute
- of <tt class="computeroutput"><span class="identifier">double_</span></tt>) . <tt class="computeroutput"><span class="identifier">_1</span></tt> is a Phoenix placeholder for the attribute
+ of <code class="computeroutput"><span class="identifier">double_</span></code>) . <code class="computeroutput"><span class="identifier">_1</span></code> is a Phoenix placeholder for the attribute
           of the generator the semantic action is attached to.
         </p>
 </div>

Modified: trunk/libs/spirit/doc/html/spirit/karma/tutorials/quick_start.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/karma/tutorials/quick_start.html (original)
+++ trunk/libs/spirit/doc/html/spirit/karma/tutorials/quick_start.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -3,10 +3,10 @@
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <title>Quick Start</title>
 <link rel="stylesheet" href="../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../index.html" title="Spirit 2.1">
 <link rel="up" href="../tutorials.html" title="Tutorials">
-<link rel="previous" href="../tutorials.html" title="Tutorials">
+<link rel="prev" href="../tutorials.html" title="Tutorials">
 <link rel="next" href="warming_up.html" title="Warming up">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -22,32 +22,29 @@
 <div class="spirit-nav">
 <a accesskey="p" href="../tutorials.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../tutorials.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="warming_up.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h4 class="title">
-<a name="spirit.karma.tutorials.quick_start"></a>Quick Start
-</h4></div></div>
-<div></div>
-</div>
-<a name="spirit.karma.tutorials.quick_start.spirit_karma___what_s_that_"></a><h5>
-<a name="id461961"></a>
- <a href="quick_start.html#spirit.karma.tutorials.quick_start.spirit_karma___what_s_that_">Spirit.Karma
+<div class="section" title="Quick Start">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="spirit.karma.tutorials.quick_start"></a><a class="link" href="quick_start.html" title="Quick Start">Quick Start</a>
+</h4></div></div></div>
+<a name="spirit.karma.tutorials.quick_start.spirit_karma___what_s_that_"></a><h6>
+<a name="id1072802"></a>
+ <a class="link" href="quick_start.html#spirit.karma.tutorials.quick_start.spirit_karma___what_s_that_">Spirit.Karma
           - what's that?</a>
- </h5>
+ </h6>
 <p>
           Throughout the description of <span class="emphasis"><em>Spirit.Karma</em></span> we will
           try to align ourselves very much with the documentation for <span class="emphasis"><em>Spirit.Qi</em></span>.
           The reasons are manyfold:
         </p>
-<div class="itemizedlist"><ul type="disc">
-<li>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem">
 <span class="emphasis"><em>Spirit.Karma</em></span> is the counterpart to <span class="emphasis"><em>Spirit.Qi</em></span>.
             Some people say it's the Yin to <span class="emphasis"><em>Spirit.Qi</em></span>'s Yang.
             <span class="emphasis"><em>Spirit.Karma</em></span> is to generating byte sequences from
             internal data structures as <span class="emphasis"><em>Spirit.Qi</em></span> parsing byte
             sequences into those (very same) internal data structures.
           </li>
-<li>
+<li class="listitem">
             Both libraries have an almost identical structure, very similar semantics,
             and are both built using identical tools. Both libraries implement a
             language casting the specifics of their domain (parsing and generating)

Modified: trunk/libs/spirit/doc/html/spirit/karma/tutorials/semantic_actions.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/karma/tutorials/semantic_actions.html (original)
+++ trunk/libs/spirit/doc/html/spirit/karma/tutorials/semantic_actions.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -3,12 +3,11 @@
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <title>Semantic Actions</title>
 <link rel="stylesheet" href="../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../index.html" title="Spirit 2.1">
 <link rel="up" href="../tutorials.html" title="Tutorials">
-<link rel="previous" href="warming_up.html" title="Warming up">
-<link rel="next" href="complex___a_first_more_complex_generator.html" title="Complex
- - A first more complex generator">
+<link rel="prev" href="warming_up.html" title="Warming up">
+<link rel="next" href="complex___a_first_more_complex_generator.html" title="Complex - A first more complex generator">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
 <table cellpadding="2" width="100%"><tr>
@@ -23,19 +22,16 @@
 <div class="spirit-nav">
 <a accesskey="p" href="warming_up.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../tutorials.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="complex___a_first_more_complex_generator.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h4 class="title">
-<a name="spirit.karma.tutorials.semantic_actions"></a>Semantic Actions
-</h4></div></div>
-<div></div>
-</div>
+<div class="section" title="Semantic Actions">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="spirit.karma.tutorials.semantic_actions"></a><a class="link" href="semantic_actions.html" title="Semantic Actions">Semantic Actions</a>
+</h4></div></div></div>
 <p>
           In the previous section we mentioned a very important difference between
           parsers and generators. While parsers may be used without 'producing' any
           data, generators alsways need data to generate the output from. We mentioned
           one way of passing data to the generator by supplying it as a parameter
- to one of the main API functions (for instance <tt class="computeroutput"><span class="identifier">generate</span><span class="special">()</span></tt> or <tt class="computeroutput"><span class="identifier">generate_delimited</span><span class="special">()</span></tt>). But sometimes this is not possible
+ to one of the main API functions (for instance <code class="computeroutput"><span class="identifier">generate</span><span class="special">()</span></code> or <code class="computeroutput"><span class="identifier">generate_delimited</span><span class="special">()</span></code>). But sometimes this is not possible
           or not desireable.
         </p>
 <p>
@@ -43,16 +39,16 @@
           in <span class="emphasis"><em>Spirit.Karma</em></span> as well. Semantic actions may be attached
           to any point in the grammar specification. These actions are C++ functions
           or function objects that are called whenever a part of the generator is
- about to be invoked. Say you have a generator <tt class="computeroutput"><span class="identifier">G</span></tt>,
- and a C++ function <tt class="computeroutput"><span class="identifier">F</span></tt>, you
- can make the generator call <tt class="computeroutput"><span class="identifier">F</span></tt>
- just before it gets invoked by attaching <tt class="computeroutput"><span class="identifier">F</span></tt>:
+ about to be invoked. Say you have a generator <code class="computeroutput"><span class="identifier">G</span></code>,
+ and a C++ function <code class="computeroutput"><span class="identifier">F</span></code>, you
+ can make the generator call <code class="computeroutput"><span class="identifier">F</span></code>
+ just before it gets invoked by attaching <code class="computeroutput"><span class="identifier">F</span></code>:
         </p>
 <pre class="programlisting"><span class="identifier">G</span><span class="special">[</span><span class="identifier">F</span><span class="special">]</span>
 </pre>
 <p>
- The expression above links <tt class="computeroutput"><span class="identifier">F</span></tt>
- to the generator, <tt class="computeroutput"><span class="identifier">G</span></tt>.
+ The expression above links <code class="computeroutput"><span class="identifier">F</span></code>
+ to the generator, <code class="computeroutput"><span class="identifier">G</span></code>.
         </p>
 <p>
           Semantic actions in <span class="emphasis"><em>Spirit.Qi</em></span> are invoked after a
@@ -63,16 +59,16 @@
         </p>
 <p>
           The function/function object signature depends on the type of the generator
- to which it is attached. The generator <tt class="computeroutput"><span class="identifier">double_</span></tt>
+ to which it is attached. The generator <code class="computeroutput"><span class="identifier">double_</span></code>
           expects the number to generate. Thus, if we were to attach a function
- <tt class="computeroutput"><span class="identifier">F</span></tt> to <tt class="computeroutput"><span class="identifier">double_</span></tt>,
- we need <tt class="computeroutput"><span class="identifier">F</span></tt> to be declared
+ <code class="computeroutput"><span class="identifier">F</span></code> to <code class="computeroutput"><span class="identifier">double_</span></code>,
+ we need <code class="computeroutput"><span class="identifier">F</span></code> to be declared
           as:
         </p>
 <pre class="programlisting"><span class="keyword">void</span> <span class="identifier">F</span><span class="special">(</span><span class="keyword">double</span><span class="special">&amp;</span> <span class="identifier">n</span><span class="special">);</span>
 </pre>
 <p>
- where the function is expected to initialize the parameter <tt class="computeroutput"><span class="identifier">n</span></tt> with the value to generate.
+ where the function is expected to initialize the parameter <code class="computeroutput"><span class="identifier">n</span></code> with the value to generate.
         </p>
 <p>
           There are actually 2 more arguments being passed (the generator context
@@ -84,22 +80,22 @@
 <p>
           We present various ways to attach semantic actions:
         </p>
-<div class="itemizedlist"><ul type="disc">
-<li>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem">
             Using plain function pointer
           </li>
-<li>
+<li class="listitem">
             Using simple function object
           </li>
-<li>
+<li class="listitem">
             Using Boost.Bind
             with a plain function
           </li>
-<li>
+<li class="listitem">
             Using Boost.Bind
             with a member function
           </li>
-<li>
+<li class="listitem">
             Using Boost.Lambda
 </li>
 </ul></div>
@@ -145,11 +141,11 @@
 <p>
         </p>
 <p>
- Take note that with function objects, we need to have an <tt class="computeroutput"><span class="keyword">operator</span><span class="special">()</span></tt>
+ Take note that with function objects, we need to have an <code class="computeroutput"><span class="keyword">operator</span><span class="special">()</span></code>
           with 3 arguments. Since we don't care about the other two, we can use
- <tt class="computeroutput"><span class="identifier">unused_type</span></tt> for these.
- We'll see more of <tt class="computeroutput"><span class="identifier">unused_type</span></tt>
- elsewhere. Get used to it. <tt class="computeroutput"><span class="identifier">unused_type</span></tt>
+ <code class="computeroutput"><span class="identifier">unused_type</span></code> for these.
+ We'll see more of <code class="computeroutput"><span class="identifier">unused_type</span></code>
+ elsewhere. Get used to it. <code class="computeroutput"><span class="identifier">unused_type</span></code>
           is a Spirit supplied support class.
         </p>
 <p>
@@ -175,8 +171,8 @@
 <p>
         </p>
 <p>
- What's new? Well <tt class="computeroutput"><span class="identifier">int_</span></tt> is
- the sibbling of <tt class="computeroutput"><span class="identifier">double_</span></tt>.
+ What's new? Well <code class="computeroutput"><span class="identifier">int_</span></code> is
+ the sibbling of <code class="computeroutput"><span class="identifier">double_</span></code>.
           I'm sure you can guess what this generator does.
         </p>
 <p>
@@ -250,10 +246,10 @@
 <p>
           The examples above can be found here: actions.cpp
         </p>
-<a name="spirit.karma.tutorials.semantic_actions.phoenix"></a><h5>
-<a name="id465044"></a>
- Phoenix
- </h5>
+<a name="spirit.karma.tutorials.semantic_actions.phoenix"></a><h6>
+<a name="id1076174"></a>
+ <a class="link" href="semantic_actions.html#spirit.karma.tutorials.semantic_actions.phoenix">Phoenix</a>
+ </h6>
 <p>
           <a href="../../../../../phoenix/doc/html/index.html" target="_top">Phoenix</a>, a companion
           library bundled with Spirit, is specifically suited for binding semantic

Modified: trunk/libs/spirit/doc/html/spirit/karma/tutorials/warming_up.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/karma/tutorials/warming_up.html (original)
+++ trunk/libs/spirit/doc/html/spirit/karma/tutorials/warming_up.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -3,10 +3,10 @@
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <title>Warming up</title>
 <link rel="stylesheet" href="../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../index.html" title="Spirit 2.1">
 <link rel="up" href="../tutorials.html" title="Tutorials">
-<link rel="previous" href="quick_start.html" title="Quick Start">
+<link rel="prev" href="quick_start.html" title="Quick Start">
 <link rel="next" href="semantic_actions.html" title="Semantic Actions">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -22,22 +22,19 @@
 <div class="spirit-nav">
 <a accesskey="p" href="quick_start.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../tutorials.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="semantic_actions.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h4 class="title">
-<a name="spirit.karma.tutorials.warming_up"></a>Warming up
-</h4></div></div>
-<div></div>
-</div>
+<div class="section" title="Warming up">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="spirit.karma.tutorials.warming_up"></a><a class="link" href="warming_up.html" title="Warming up">Warming up</a>
+</h4></div></div></div>
 <p>
           Learning how to use <span class="emphasis"><em>Spirit.Karma</em></span> is really simple.
           We will start from trivial examples, ramping up as we go.
         </p>
-<a name="spirit.karma.tutorials.warming_up.trivial_example__1_generating_a_number"></a><h5>
-<a name="id462147"></a>
- <a href="warming_up.html#spirit.karma.tutorials.warming_up.trivial_example__1_generating_a_number">Trivial
+<a name="spirit.karma.tutorials.warming_up.trivial_example__1_generating_a_number"></a><h6>
+<a name="id1072917"></a>
+ <a class="link" href="warming_up.html#spirit.karma.tutorials.warming_up.trivial_example__1_generating_a_number">Trivial
           Example #1 Generating a number</a>
- </h5>
+ </h6>
 <p>
           Let's create a generator that will output a floating-point number:
         </p>
@@ -51,13 +48,13 @@
           entities (as in this case, floating point numbers) are named identically
           in <span class="emphasis"><em>Spirit.Karma</em></span> and in <span class="emphasis"><em>Spirit.Qi</em></span>.
           Actually, both libraries are using the very same variable instance to refer
- to a floating point generator or parser: <tt class="computeroutput"><span class="identifier">double_</span></tt>.
+ to a floating point generator or parser: <code class="computeroutput"><span class="identifier">double_</span></code>.
         </p>
-<a name="spirit.karma.tutorials.warming_up.trivial_example__2_generating_two_numbers"></a><h5>
-<a name="id462232"></a>
- <a href="warming_up.html#spirit.karma.tutorials.warming_up.trivial_example__2_generating_two_numbers">Trivial
+<a name="spirit.karma.tutorials.warming_up.trivial_example__2_generating_two_numbers"></a><h6>
+<a name="id1072961"></a>
+ <a class="link" href="warming_up.html#spirit.karma.tutorials.warming_up.trivial_example__2_generating_two_numbers">Trivial
           Example #2 Generating two numbers</a>
- </h5>
+ </h6>
 <p>
           Now, let's create a generator that will output a line consisting of two
           floating-point numbers.
@@ -65,37 +62,37 @@
 <pre class="programlisting"><span class="identifier">double_</span> <span class="special">&lt;&lt;</span> <span class="identifier">double_</span>
 </pre>
 <p>
- Here you see the familiar floating-point numeric generator <tt class="computeroutput"><span class="identifier">double_</span></tt> used twice, once for each number.
- If you are used to see the <tt class="computeroutput"><span class="char">'&gt;&gt;'</span></tt>
+ Here you see the familiar floating-point numeric generator <code class="computeroutput"><span class="identifier">double_</span></code> used twice, once for each number.
+ If you are used to see the <code class="computeroutput"><span class="char">'&gt;&gt;'</span></code>
           operator for concatenating two parsers in <span class="emphasis"><em>Spirit.Qi</em></span>
- you might wonder, what's that <tt class="computeroutput"><span class="char">'&lt;&lt;'</span></tt>
+ you might wonder, what's that <code class="computeroutput"><span class="char">'&lt;&lt;'</span></code>
           operator doing in there? We decided to distinguish generating and parsing
           of sequences the same way as the std::stream libraries do: we use operator
- <tt class="computeroutput"><span class="char">'&gt;&gt;'</span></tt> for input (parsing),
- and operator <tt class="computeroutput"><span class="char">'&lt;&lt;'</span></tt> for output
+ <code class="computeroutput"><span class="char">'&gt;&gt;'</span></code> for input (parsing),
+ and operator <code class="computeroutput"><span class="char">'&lt;&lt;'</span></code> for output
           (generating). Other than that there is no significant difference. The above
           program creates a generator from two simpler generators, glueing them together
           with the sequence operator. The result is a generator that is a composition
           of smaller generators. Whitespace between numbers can implicitly be inserted
           depending on how the generator is invoked (see below).
         </p>
-<div class="note"><table border="0" summary="Note">
+<div class="note" title="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>
 </tr>
-<tr><td colspan="2" align="left" valign="top"><p>
+<tr><td align="left" valign="top"><p>
             When we combine generators, we end up with a "bigger" generator,
             but it's still a generator. Generators can get bigger and bigger, nesting
             more and more, but whenever you glue two generators together, you end
             up with one bigger generator. This is an important concept.
           </p></td></tr>
 </table></div>
-<a name="spirit.karma.tutorials.warming_up.trivial_example__3_generating_one_or_more_numbers"></a><h5>
-<a name="id462379"></a>
- <a href="warming_up.html#spirit.karma.tutorials.warming_up.trivial_example__3_generating_one_or_more_numbers">Trivial
+<a name="spirit.karma.tutorials.warming_up.trivial_example__3_generating_one_or_more_numbers"></a><h6>
+<a name="id1073046"></a>
+ <a class="link" href="warming_up.html#spirit.karma.tutorials.warming_up.trivial_example__3_generating_one_or_more_numbers">Trivial
           Example #3 Generating one or more numbers</a>
- </h5>
+ </h6>
 <p>
           Now, creating output for two numbers is not too interesting. Let's create
           a generator that will output zero or more floating-point numbers in a row.
@@ -103,7 +100,7 @@
 <pre class="programlisting"><span class="special">*</span><span class="identifier">double_</span>
 </pre>
 <p>
- This is like a regular-expression Kleene Star. We moved the <tt class="computeroutput"><span class="special">*</span></tt> to the front for the same reasons we did
+ This is like a regular-expression Kleene Star. We moved the <code class="computeroutput"><span class="special">*</span></code> to the front for the same reasons we did
           in <span class="emphasis"><em>Spirit.Qi</em></span>: we must work with the syntax rules of
           C++. But if you know regular expressions (and for sure you remember those
           syntax rules) it will start to look very familiar in a matter of a very
@@ -116,11 +113,11 @@
           As above, whitespace can be inserted implicitely in between the generated
           numbers, if needed.
         </p>
-<a name="spirit.karma.tutorials.warming_up.trivial_example__4_generating_a_comma_delimited_list_of_numbers"></a><h5>
-<a name="id462467"></a>
- <a href="warming_up.html#spirit.karma.tutorials.warming_up.trivial_example__4_generating_a_comma_delimited_list_of_numbers">Trivial
+<a name="spirit.karma.tutorials.warming_up.trivial_example__4_generating_a_comma_delimited_list_of_numbers"></a><h6>
+<a name="id1073094"></a>
+ <a class="link" href="warming_up.html#spirit.karma.tutorials.warming_up.trivial_example__4_generating_a_comma_delimited_list_of_numbers">Trivial
           Example #4 Generating a comma-delimited list of numbers</a>
- </h5>
+ </h6>
 <p>
           We follow the lead of <span class="emphasis"><em>Spirit.Qi</em></span>'s warming up section
           and will create a generator that produces a comma-delimited list of numbers.
@@ -128,8 +125,8 @@
 <pre class="programlisting"><span class="identifier">double_</span> <span class="special">&lt;&lt;</span> <span class="special">*(</span><span class="identifier">char_</span><span class="special">(</span><span class="char">','</span><span class="special">)</span> <span class="special">&lt;&lt;</span> <span class="identifier">double_</span><span class="special">)</span>
 </pre>
 <p>
- Notice <tt class="computeroutput"><span class="identifier">char_</span><span class="special">(</span><span class="char">','</span><span class="special">)</span></tt>. It is
- a literal character generator that simply generates the comma <tt class="computeroutput"><span class="char">','</span></tt>. In this case, the Kleene Star is modifying
+ Notice <code class="computeroutput"><span class="identifier">char_</span><span class="special">(</span><span class="char">','</span><span class="special">)</span></code>. It is
+ a literal character generator that simply generates the comma <code class="computeroutput"><span class="char">','</span></code>. In this case, the Kleene Star is modifying
           a more complex generator, namely, the one generated by the expression:
         </p>
 <pre class="programlisting"><span class="special">(</span><span class="identifier">char_</span><span class="special">(</span><span class="char">','</span><span class="special">)</span> <span class="special">&lt;&lt;</span> <span class="identifier">double_</span><span class="special">)</span>
@@ -139,27 +136,27 @@
           Star encloses the complete expression above, repeating the whole pattern
           in the generated output zero or more times.
         </p>
-<a name="spirit.karma.tutorials.warming_up.let_s_generate_"></a><h5>
-<a name="id462666"></a>
- <a href="warming_up.html#spirit.karma.tutorials.warming_up.let_s_generate_">Let's
+<a name="spirit.karma.tutorials.warming_up.let_s_generate_"></a><h6>
+<a name="id1073228"></a>
+ <a class="link" href="warming_up.html#spirit.karma.tutorials.warming_up.let_s_generate_">Let's
           Generate!</a>
- </h5>
+ </h6>
 <p>
           We're done with defining the generator. All what's left is to invoke the
- generator to do its work. For now, we will use the <tt class="computeroutput"><span class="identifier">generate_delimited</span></tt>
+ generator to do its work. For now, we will use the <code class="computeroutput"><span class="identifier">generate_delimited</span></code>
           function. One overload of this function accepts four arguments:
         </p>
-<div class="orderedlist"><ol type="1">
-<li>
+<div class="orderedlist"><ol class="orderedlist" type="1">
+<li class="listitem">
             An output iterator accepting the generated characters
           </li>
-<li>
+<li class="listitem">
             The generator expression
           </li>
-<li>
+<li class="listitem">
             Another generator called the delimiting generator
           </li>
-<li>
+<li class="listitem">
             The data to format and output
           </li>
 </ol></div>
@@ -173,22 +170,22 @@
           For generators this mode doesn't make any sense. What is output generation
           without generating any output? So we always will have to supply the data
           the output should be generated from. In our example we supply a vector
- of <tt class="computeroutput"><span class="keyword">double</span></tt> numbers as the last
- parameter to the function <tt class="computeroutput"><span class="identifier">generate_delimited</span></tt>
+ of <code class="computeroutput"><span class="keyword">double</span></code> numbers as the last
+ parameter to the function <code class="computeroutput"><span class="identifier">generate_delimited</span></code>
           (see code below).
         </p>
 <p>
           In this example, we wish to delimit the generated numbers by spaces. Another
- generator named <tt class="computeroutput"><span class="identifier">space</span></tt> is
+ generator named <code class="computeroutput"><span class="identifier">space</span></code> is
           included in Spirit's repertoire of predefined generators. It is a very
           trivial generator that simply produces spaces. It is the equivalent to
- writing <tt class="computeroutput"><span class="identifier">char_</span><span class="special">(</span><span class="char">' '</span><span class="special">)</span></tt>, or simply
- <tt class="computeroutput"><span class="char">' '</span></tt>. It has been implemented
- for similarity with the corresponding predefined <tt class="computeroutput"><span class="identifier">space</span></tt>
- parser. We will use <tt class="computeroutput"><span class="identifier">space</span></tt>
+ writing <code class="computeroutput"><span class="identifier">char_</span><span class="special">(</span><span class="char">' '</span><span class="special">)</span></code>, or simply
+ <code class="computeroutput"><span class="char">' '</span></code>. It has been implemented
+ for similarity with the corresponding predefined <code class="computeroutput"><span class="identifier">space</span></code>
+ parser. We will use <code class="computeroutput"><span class="identifier">space</span></code>
           as our delimiter. The delimiter is the one responsible for inserting characters
- in between generator elements such as the <tt class="computeroutput"><span class="identifier">double_</span></tt>
- and <tt class="computeroutput"><span class="identifier">char_</span></tt>.
+ in between generator elements such as the <code class="computeroutput"><span class="identifier">double_</span></code>
+ and <code class="computeroutput"><span class="identifier">char_</span></code>.
         </p>
 <p>
           Ok, so now let's generate (for the complete source code of this example
@@ -207,10 +204,10 @@
     <span class="keyword">using</span> <span class="identifier">ascii</span><span class="special">::</span><span class="identifier">space</span><span class="special">;</span>
 
     <span class="keyword">bool</span> <span class="identifier">r</span> <span class="special">=</span> <span class="identifier">generate_delimited</span><span class="special">(</span>
- <span class="identifier">sink</span><span class="special">,</span> <span class="callout_bug"><a name="spirit4co" href="warming_up.html#spirit4"><img src="../../../../../../../doc/src/images/callouts/1.png" alt="1" border="0"></a></span>
- <span class="identifier">double_</span> <span class="special">&lt;&lt;</span> <span class="special">*(</span><span class="char">','</span> <span class="special">&lt;&lt;</span> <span class="identifier">double_</span><span class="special">),</span> <span class="callout_bug"><a name="spirit5co" href="warming_up.html#spirit5"><img src="../../../../../../../doc/src/images/callouts/2.png" alt="2" border="0"></a></span>
- <span class="identifier">space</span><span class="special">,</span> <span class="callout_bug"><a name="spirit6co" href="warming_up.html#spirit6"><img src="../../../../../../../doc/src/images/callouts/3.png" alt="3" border="0"></a></span>
- <span class="identifier">v</span> <span class="callout_bug"><a name="spirit7co" href="warming_up.html#spirit7"><img src="../../../../../../../doc/src/images/callouts/4.png" alt="4" border="0"></a></span>
+ <span class="identifier">sink</span><span class="special">,</span> <span class="callout_bug"><a class="co" name="spirit4co" href="warming_up.html#spirit4"><img src="../../../../../../../doc/src/images/callouts/1.png" alt="1" border="0"></a></span>
+ <span class="identifier">double_</span> <span class="special">&lt;&lt;</span> <span class="special">*(</span><span class="char">','</span> <span class="special">&lt;&lt;</span> <span class="identifier">double_</span><span class="special">),</span> <span class="callout_bug"><a class="co" name="spirit5co" href="warming_up.html#spirit5"><img src="../../../../../../../doc/src/images/callouts/2.png" alt="2" border="0"></a></span>
+ <span class="identifier">space</span><span class="special">,</span> <span class="callout_bug"><a class="co" name="spirit6co" href="warming_up.html#spirit6"><img src="../../../../../../../doc/src/images/callouts/3.png" alt="3" border="0"></a></span>
+ <span class="identifier">v</span> <span class="callout_bug"><a class="co" name="spirit7co" href="warming_up.html#spirit7"><img src="../../../../../../../doc/src/images/callouts/4.png" alt="4" border="0"></a></span>
     <span class="special">);</span>
     <span class="keyword">return</span> <span class="identifier">r</span><span class="special">;</span>
 <span class="special">}</span>
@@ -223,23 +220,19 @@
             </p>
 <div class="calloutlist"><table border="0" summary="Callout list">
 <tr>
-<td width="5%" valign="top" align="left">
-<a name="spirit4"></a>1 </td>
+<td width="5%" valign="top" align="left"><p><a name="spirit4"></a>1 </p></td>
 <td valign="top" align="left"><p> destination: output iterator </p></td>
 </tr>
 <tr>
-<td width="5%" valign="top" align="left">
-<a name="spirit5"></a>2 </td>
+<td width="5%" valign="top" align="left"><p><a name="spirit5"></a>2 </p></td>
 <td valign="top" align="left"><p> the generator </p></td>
 </tr>
 <tr>
-<td width="5%" valign="top" align="left">
-<a name="spirit6"></a>3 </td>
+<td width="5%" valign="top" align="left"><p><a name="spirit6"></a>3 </p></td>
 <td valign="top" align="left"><p> the delimiter-generator </p></td>
 </tr>
 <tr>
-<td width="5%" valign="top" align="left">
-<a name="spirit7"></a>4 </td>
+<td width="5%" valign="top" align="left"><p><a name="spirit7"></a>4 </p></td>
 <td valign="top" align="left"><p> the
             data to output </p></td>
 </tr>
@@ -249,17 +242,17 @@
 <p>
         </p>
 <p>
- The generate function returns <tt class="computeroutput"><span class="keyword">true</span></tt>
- or <tt class="computeroutput"><span class="keyword">false</span></tt> depending on the
+ The generate function returns <code class="computeroutput"><span class="keyword">true</span></code>
+ or <code class="computeroutput"><span class="keyword">false</span></code> depending on the
           result of the output generation. As outlined in different places of this
           documentation, a generator may fail for different reasons. One of the possible
           reasons is an error in the underlying output iterator (memory exhausted
           or disk full, etc.)
         </p>
 <p>
- Note that we inlined the generator directly in the call to <tt class="computeroutput"><span class="identifier">generate_delimited</span></tt>. Upon calling generate,
+ Note that we inlined the generator directly in the call to <code class="computeroutput"><span class="identifier">generate_delimited</span></code>. Upon calling generate,
           the expression evaluates into a temporary, unnamed generator which is passed
- into the <tt class="computeroutput"><span class="identifier">generate_delimited</span><span class="special">()</span></tt> function, used, and then destroyed.
+ into the <code class="computeroutput"><span class="identifier">generate_delimited</span><span class="special">()</span></code> function, used, and then destroyed.
         </p>
 <p>
           Here, we chose to make the generate function generic by making it a template,

Modified: trunk/libs/spirit/doc/html/spirit/lex.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/lex.html (original)
+++ trunk/libs/spirit/doc/html/spirit/lex.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -1,13 +1,13 @@
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title> Spirit.Lex</title>
+<title>Spirit.Lex</title>
 <link rel="stylesheet" href="../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../index.html" title="Spirit 2.1">
 <link rel="up" href="../index.html" title="Spirit 2.1">
-<link rel="previous" href="karma/reference/generator_concepts/narygenerator.html" title="NaryGenerator">
-<link rel="next" href="lex/lexer_introduction.html" title=" Introduction to Spirit.Lex">
+<link rel="prev" href="karma/reference/generator_concepts/narygenerator.html" title="NaryGenerator">
+<link rel="next" href="lex/lexer_introduction.html" title="Introduction to Spirit.Lex">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
 <table cellpadding="2" width="100%"><tr>
@@ -22,13 +22,10 @@
 <div class="spirit-nav">
 <a accesskey="p" href="karma/reference/generator_concepts/narygenerator.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="lex/lexer_introduction.html"><img src="../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h2 class="title" style="clear: both">
-<a name="spirit.lex"></a> Spirit.Lex
-</h2></div></div>
-<div></div>
-</div>
+<div class="section" title="Spirit.Lex">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="spirit.lex"></a><a class="link" href="lex.html" title="Spirit.Lex"> <span class="emphasis"><em>Spirit.Lex</em></span></a>
+</h2></div></div></div>
 <div class="toc"><dl>
 <dt><span class="section"> Introduction to Spirit.Lex</span></dt>
 <dt><span class="section"><a href="lex/tutorials.html"> <span class="emphasis"><em>Spirit.Lex</em></span>

Modified: trunk/libs/spirit/doc/html/spirit/lex/abstracts.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/lex/abstracts.html (original)
+++ trunk/libs/spirit/doc/html/spirit/lex/abstracts.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -1,13 +1,12 @@
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title> Abstracts</title>
+<title>Abstracts</title>
 <link rel="stylesheet" href="../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../index.html" title="Spirit 2.1">
-<link rel="up" href="../lex.html" title=" Spirit.Lex">
-<link rel="previous" href="tutorials/lexer_quickstart3.html" title=" Quickstart
- 3 - Counting Words Using a Parser">
+<link rel="up" href="../lex.html" title="Spirit.Lex">
+<link rel="prev" href="tutorials/lexer_quickstart3.html" title="Quickstart 3 - Counting Words Using a Parser">
 <link rel="next" href="abstracts/lexer_primitives.html" title="Lexer Primitives">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -23,13 +22,10 @@
 <div class="spirit-nav">
 <a accesskey="p" href="tutorials/lexer_quickstart3.html"><img src="../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../lex.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="abstracts/lexer_primitives.html"><img src="../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h3 class="title">
-<a name="spirit.lex.abstracts"></a> Abstracts
-</h3></div></div>
-<div></div>
-</div>
+<div class="section" title="Abstracts">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="spirit.lex.abstracts"></a><a class="link" href="abstracts.html" title="Abstracts"> Abstracts</a>
+</h3></div></div></div>
 <div class="toc"><dl>
 <dt><span class="section">Lexer Primitives</span></dt>
 <dt><span class="section"><a href="abstracts/lexer_tokenizing.html"> Tokenizing

Modified: trunk/libs/spirit/doc/html/spirit/lex/abstracts/lexer_attributes.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/lex/abstracts/lexer_attributes.html (original)
+++ trunk/libs/spirit/doc/html/spirit/lex/abstracts/lexer_attributes.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -1,14 +1,13 @@
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title> Lexer Attributes</title>
+<title>Lexer Attributes</title>
 <link rel="stylesheet" href="../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../index.html" title="Spirit 2.1">
-<link rel="up" href="../abstracts.html" title=" Abstracts">
-<link rel="previous" href="lexer_parsing.html" title=" Parsing using
- a Lexer">
-<link rel="next" href="lexer_states.html" title=" Lexer States">
+<link rel="up" href="../abstracts.html" title="Abstracts">
+<link rel="prev" href="lexer_parsing.html" title="Parsing using a Lexer">
+<link rel="next" href="lexer_states.html" title="Lexer States">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
 <table cellpadding="2" width="100%"><tr>
@@ -23,12 +22,9 @@
 <div class="spirit-nav">
 <a accesskey="p" href="lexer_parsing.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../abstracts.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="lexer_states.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en"><div class="titlepage">
-<div><div><h4 class="title">
-<a name="spirit.lex.abstracts.lexer_attributes"></a> Lexer Attributes
-</h4></div></div>
-<div></div>
-</div></div>
+<div class="section" title="Lexer Attributes"><div class="titlepage"><div><div><h4 class="title">
+<a name="spirit.lex.abstracts.lexer_attributes"></a><a class="link" href="lexer_attributes.html" title="Lexer Attributes"> Lexer Attributes</a>
+</h4></div></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 © 2001-2009 Joel

Modified: trunk/libs/spirit/doc/html/spirit/lex/abstracts/lexer_parsing.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/lex/abstracts/lexer_parsing.html (original)
+++ trunk/libs/spirit/doc/html/spirit/lex/abstracts/lexer_parsing.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -1,15 +1,13 @@
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title> Parsing using
- a Lexer</title>
+<title>Parsing using a Lexer</title>
 <link rel="stylesheet" href="../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../index.html" title="Spirit 2.1">
-<link rel="up" href="../abstracts.html" title=" Abstracts">
-<link rel="previous" href="lexer_static_model.html" title=" The Static
- Lexer Model">
-<link rel="next" href="lexer_attributes.html" title=" Lexer Attributes">
+<link rel="up" href="../abstracts.html" title="Abstracts">
+<link rel="prev" href="lexer_static_model.html" title="The Static Lexer Model">
+<link rel="next" href="lexer_attributes.html" title="Lexer Attributes">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
 <table cellpadding="2" width="100%"><tr>
@@ -24,14 +22,10 @@
 <div class="spirit-nav">
 <a accesskey="p" href="lexer_static_model.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../abstracts.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="lexer_attributes.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en"><div class="titlepage">
-<div><div><h4 class="title">
-<a name="spirit.lex.abstracts.lexer_parsing"></a><a href="lexer_parsing.html" title=" Parsing using
- a Lexer"> Parsing using
+<div class="section" title="Parsing using a Lexer"><div class="titlepage"><div><div><h4 class="title">
+<a name="spirit.lex.abstracts.lexer_parsing"></a><a class="link" href="lexer_parsing.html" title="Parsing using a Lexer"> Parsing using
         a Lexer</a>
-</h4></div></div>
-<div></div>
-</div></div>
+</h4></div></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 © 2001-2009 Joel

Modified: trunk/libs/spirit/doc/html/spirit/lex/abstracts/lexer_primitives.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/lex/abstracts/lexer_primitives.html (original)
+++ trunk/libs/spirit/doc/html/spirit/lex/abstracts/lexer_primitives.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -3,12 +3,11 @@
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <title>Lexer Primitives</title>
 <link rel="stylesheet" href="../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../index.html" title="Spirit 2.1">
-<link rel="up" href="../abstracts.html" title=" Abstracts">
-<link rel="previous" href="../abstracts.html" title=" Abstracts">
-<link rel="next" href="lexer_primitives/lexer_primitives.html" title="
- Lexer Primitives">
+<link rel="up" href="../abstracts.html" title="Abstracts">
+<link rel="prev" href="../abstracts.html" title="Abstracts">
+<link rel="next" href="lexer_primitives/lexer_primitives.html" title="Lexer Primitives">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
 <table cellpadding="2" width="100%"><tr>
@@ -23,13 +22,10 @@
 <div class="spirit-nav">
 <a accesskey="p" href="../abstracts.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../abstracts.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="lexer_primitives/lexer_primitives.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h4 class="title">
-<a name="spirit.lex.abstracts.lexer_primitives"></a>Lexer Primitives
-</h4></div></div>
-<div></div>
-</div>
+<div class="section" title="Lexer Primitives">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="spirit.lex.abstracts.lexer_primitives"></a><a class="link" href="lexer_primitives.html" title="Lexer Primitives">Lexer Primitives</a>
+</h4></div></div></div>
 <div class="toc"><dl>
 <dt><span class="section"><a href="lexer_primitives/lexer_primitives.html">
           Lexer Primitives</a></span></dt>

Modified: trunk/libs/spirit/doc/html/spirit/lex/abstracts/lexer_primitives/lexer_primitives.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/lex/abstracts/lexer_primitives/lexer_primitives.html (original)
+++ trunk/libs/spirit/doc/html/spirit/lex/abstracts/lexer_primitives/lexer_primitives.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -1,15 +1,13 @@
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title>
- Lexer Primitives</title>
+<title>Lexer Primitives</title>
 <link rel="stylesheet" href="../../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../../index.html" title="Spirit 2.1">
 <link rel="up" href="../lexer_primitives.html" title="Lexer Primitives">
-<link rel="previous" href="../lexer_primitives.html" title="Lexer Primitives">
-<link rel="next" href="lexer_token_values.html" title="
- About Tokens and Token Values">
+<link rel="prev" href="../lexer_primitives.html" title="Lexer Primitives">
+<link rel="next" href="lexer_token_values.html" title="About Tokens and Token Values">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
 <table cellpadding="2" width="100%"><tr>
@@ -24,14 +22,10 @@
 <div class="spirit-nav">
 <a accesskey="p" href="../lexer_primitives.html"><img src="../../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../lexer_primitives.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="lexer_token_values.html"><img src="../../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en"><div class="titlepage">
-<div><div><h5 class="title">
-<a name="spirit.lex.abstracts.lexer_primitives.lexer_primitives"></a><a href="lexer_primitives.html" title="
- Lexer Primitives">
+<div class="section" title="Lexer Primitives"><div class="titlepage"><div><div><h5 class="title">
+<a name="spirit.lex.abstracts.lexer_primitives.lexer_primitives"></a><a class="link" href="lexer_primitives.html" title="Lexer Primitives">
           Lexer Primitives</a>
-</h5></div></div>
-<div></div>
-</div></div>
+</h5></div></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 © 2001-2009 Joel

Modified: trunk/libs/spirit/doc/html/spirit/lex/abstracts/lexer_primitives/lexer_token_definition.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/lex/abstracts/lexer_primitives/lexer_token_definition.html (original)
+++ trunk/libs/spirit/doc/html/spirit/lex/abstracts/lexer_primitives/lexer_token_definition.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -1,16 +1,13 @@
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title>
- Ways to define Tokens</title>
+<title>Ways to define Tokens</title>
 <link rel="stylesheet" href="../../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../../index.html" title="Spirit 2.1">
 <link rel="up" href="../lexer_primitives.html" title="Lexer Primitives">
-<link rel="previous" href="lexer_token_values.html" title="
- About Tokens and Token Values">
-<link rel="next" href="../lexer_tokenizing.html" title=" Tokenizing
- Input Data">
+<link rel="prev" href="lexer_token_values.html" title="About Tokens and Token Values">
+<link rel="next" href="../lexer_tokenizing.html" title="Tokenizing Input Data">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
 <table cellpadding="2" width="100%"><tr>
@@ -25,14 +22,10 @@
 <div class="spirit-nav">
 <a accesskey="p" href="lexer_token_values.html"><img src="../../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../lexer_primitives.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="../lexer_tokenizing.html"><img src="../../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en"><div class="titlepage">
-<div><div><h5 class="title">
-<a name="spirit.lex.abstracts.lexer_primitives.lexer_token_definition"></a><a href="lexer_token_definition.html" title="
- Ways to define Tokens">
+<div class="section" title="Ways to define Tokens"><div class="titlepage"><div><div><h5 class="title">
+<a name="spirit.lex.abstracts.lexer_primitives.lexer_token_definition"></a><a class="link" href="lexer_token_definition.html" title="Ways to define Tokens">
           Ways to define Tokens</a>
-</h5></div></div>
-<div></div>
-</div></div>
+</h5></div></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 © 2001-2009 Joel

Modified: trunk/libs/spirit/doc/html/spirit/lex/abstracts/lexer_primitives/lexer_token_values.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/lex/abstracts/lexer_primitives/lexer_token_values.html (original)
+++ trunk/libs/spirit/doc/html/spirit/lex/abstracts/lexer_primitives/lexer_token_values.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -1,16 +1,13 @@
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title>
- About Tokens and Token Values</title>
+<title>About Tokens and Token Values</title>
 <link rel="stylesheet" href="../../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../../index.html" title="Spirit 2.1">
 <link rel="up" href="../lexer_primitives.html" title="Lexer Primitives">
-<link rel="previous" href="lexer_primitives.html" title="
- Lexer Primitives">
-<link rel="next" href="lexer_token_definition.html" title="
- Ways to define Tokens">
+<link rel="prev" href="lexer_primitives.html" title="Lexer Primitives">
+<link rel="next" href="lexer_token_definition.html" title="Ways to define Tokens">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
 <table cellpadding="2" width="100%"><tr>
@@ -25,15 +22,11 @@
 <div class="spirit-nav">
 <a accesskey="p" href="lexer_primitives.html"><img src="../../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../lexer_primitives.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="lexer_token_definition.html"><img src="../../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h5 class="title">
-<a name="spirit.lex.abstracts.lexer_primitives.lexer_token_values"></a><a href="lexer_token_values.html" title="
- About Tokens and Token Values">
+<div class="section" title="About Tokens and Token Values">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="spirit.lex.abstracts.lexer_primitives.lexer_token_values"></a><a class="link" href="lexer_token_values.html" title="About Tokens and Token Values">
           About Tokens and Token Values</a>
-</h5></div></div>
-<div></div>
-</div>
+</h5></div></div></div>
 <p>
             As already discussed, lexical scanning is the process of analyzing the
             stream of input characters and separating it into strings called tokens,
@@ -49,45 +42,45 @@
             class to the user. The only real limitation posed on this token class
             is consequently, that it has to carry at least the token id of the token
             it represents. For more information about the interface a user defined
- token type has to expose please look at the <a href="../../reference/concepts/token.html" title="Token">Token
+ token type has to expose please look at the <a class="link" href="../../reference/concepts/token.html" title="Token">Token
             Reference</a> reference. The library provides a default token type
             based on the Lexertl
- library which should be sufficient in most use cases: the lexertl_token<>
+ library which should be sufficient in most use cases: the <a class="link" href="../../reference/token_class.html" title="Token Class"><code class="computeroutput"><span class="identifier">lexertl_token</span><span class="special">&lt;&gt;</span></code></a>
             type. This section focusses on the description of general features a
             token class may implement and how this integrates with the other parts
             of the <span class="emphasis"><em>Spirit.Lex</em></span> library.
           </p>
 <a name="spirit.lex.abstracts.lexer_primitives.lexer_token_values.the_anatomy_of_a_token"></a><h6>
-<a name="id493359"></a>
- <a href="lexer_token_values.html#spirit.lex.abstracts.lexer_primitives.lexer_token_values.the_anatomy_of_a_token">The
+<a name="id1105350"></a>
+ <a class="link" href="lexer_token_values.html#spirit.lex.abstracts.lexer_primitives.lexer_token_values.the_anatomy_of_a_token">The
             Anatomy of a Token</a>
           </h6>
 <p>
             It is very important to understand the difference between a token definition
- (represented by the token_def<>
- template) and a token itself (for instance represented by the lexertl_token<>
+ (represented by the <a class="link" href="../../reference/tokendef_class.html" title="TokenDef Class"><code class="computeroutput"><span class="identifier">token_def</span><span class="special">&lt;&gt;</span></code></a>
+ template) and a token itself (for instance represented by the <a class="link" href="../../reference/token_class.html" title="Token Class"><code class="computeroutput"><span class="identifier">lexertl_token</span><span class="special">&lt;&gt;</span></code></a>
             template).
           </p>
 <p>
             The token definition is used to describe the main features of a particular
             token type, especially:
           </p>
-<div class="itemizedlist"><ul type="disc">
-<li>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem">
               to simplify the definition of a token type using a regular expression
               pattern applied while matching this token type,
             </li>
-<li>
+<li class="listitem">
               to associate a token type with a particular lexer state,
             </li>
-<li>
+<li class="listitem">
               to optionally assign a token id to a token type,
             </li>
-<li>
+<li class="listitem">
               to optionally associate some code to execute whenever an instance of
               this token type has been matched,
             </li>
-<li>
+<li class="listitem">
               and to optionally specify the attribute type of the token value.
             </li>
 </ul></div>
@@ -101,47 +94,46 @@
             data structure contains at least the token id of the matched token type,
             allowing to identify the matched character sequence. Optionally, the
             token instance may contain a token value and/or the lexer state this
- token instance was matched in. The following figure
+ token instance was matched in. The following <a class="link" href="lexer_token_values.html#spirit.lex.tokenstructure" title="Figure 5. The structure of a token">figure</a>
             shows the schematic structure of a token.
           </p>
 <p>
             </p>
 <div class="figure">
 <a name="spirit.lex.tokenstructure"></a><p class="title"><b>Figure 5. The structure of a token</b></p>
-<span class="inlinemediaobject"><img src="./images/tokenstructure.png" alt="The
- structure of a token"></span>
+<div class="figure-contents"><span class="inlinemediaobject"><img src="../../../.././images/tokenstructure.png" alt="The structure of a token"></span></div>
 </div>
-<p>
+<p><br class="figure-break">
           </p>
 <p>
             The token value and the lexer state the token has been recogniyed in
             may be omitted for optimization reasons, avoiding the token to carry
             more data than actually required. This configuration can be achieved
- by supplying appropriate template parameters for the lexertl_token<>
+ by supplying appropriate template parameters for the <a class="link" href="../../reference/token_class.html" title="Token Class"><code class="computeroutput"><span class="identifier">lexertl_token</span><span class="special">&lt;&gt;</span></code></a>
             template while defining the token type.
           </p>
 <p>
             The lexer iterator returns the same token type for each of the different
             matched token definitions. To accomodate for the possibly different token
             <span class="emphasis"><em>value</em></span> types exposed by the various token types (token
- definitions), the general type of the token value is a boost.variant<>.
+ definitions), the general type of the token value is a boost.variant<>.
             As a minimum (for the default configuration) this token value variant
- will be configured to always hold a boost::iterator_range<>
+ will be configured to always hold a boost::iterator_range<>
             containing the pair of iterators pointing to the matched input sequence
             for this token instance.
           </p>
-<div class="note"><table border="0" summary="Note">
+<div class="note" title="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>
 </tr>
-<tr><td colspan="2" align="left" valign="top"><p>
+<tr><td align="left" valign="top"><p>
               If the lexical analyzer is used in conjunction with a <span class="emphasis"><em>Spirit.Qi</em></span>
- parser, the stored boost::iterator_range<>
+ parser, the stored boost::iterator_range<>
               token value will be converted to the requested token type (parser attribute)
               exactly once. This happens at the time of the first access to the token
               value requiring the corresponding type conversion. The converted token
- value will be stored in the boost.variant<>
+ value will be stored in the boost.variant<>
               replacing the initially stored iterator range. This avoids to convert
               the input sequence to the token value more than once, thus optimizing
               the integration of the lexer with <span class="emphasis"><em>Spirit.Qi</em></span>, even
@@ -149,7 +141,7 @@
             </p></td></tr>
 </table></div>
 <p>
- Here is the template prototype of the lexertl_token<>
+ Here is the template prototype of the <a class="link" href="../../reference/token_class.html" title="Token Class"><code class="computeroutput"><span class="identifier">lexertl_token</span><span class="special">&lt;&gt;</span></code></a>
             template:
           </p>
 <pre class="programlisting"><span class="keyword">template</span> <span class="special">&lt;</span>
@@ -159,28 +151,28 @@
 <span class="special">&gt;</span>
 <span class="keyword">struct</span> <span class="identifier">lexertl_token</span><span class="special">;</span>
 </pre>
-<div class="variablelist">
+<div class="variablelist" title="where:">
 <p class="title"><b>where:</b></p>
 <dl>
 <dt><span class="term">Iterator</span></dt>
 <dd><p>
                 This is the type of the iterator used to access the underlying input
- stream. It defaults to a plain <tt class="computeroutput"><span class="keyword">char</span>
- <span class="keyword">const</span><span class="special">*</span></tt>.
+ stream. It defaults to a plain <code class="computeroutput"><span class="keyword">char</span>
+ <span class="keyword">const</span><span class="special">*</span></code>.
               </p></dd>
 <dt><span class="term">AttributeTypes</span></dt>
 <dd><p>
                 This is either a mpl sequence containing all attribute types used
- for the token definitions or the type <tt class="computeroutput"><span class="identifier">omitted</span></tt>.
+ for the token definitions or the type <code class="computeroutput"><span class="identifier">omitted</span></code>.
                 If the mpl sequence is empty (which is the default), all token instances
- will store a <tt class="computeroutput"><span class="identifier">boost</span><span class="special">::</span><span class="identifier">iterator_range</span><span class="special">&lt;</span><span class="identifier">Iterator</span><span class="special">&gt;</span></tt> pointing to the start and the
- end of the matched section in the input stream. If the type is <tt class="computeroutput"><span class="identifier">omitted</span></tt>, the generated tokens will
+ will store a <code class="computeroutput"><span class="identifier">boost</span><span class="special">::</span><span class="identifier">iterator_range</span><span class="special">&lt;</span><span class="identifier">Iterator</span><span class="special">&gt;</span></code> pointing to the start and the
+ end of the matched section in the input stream. If the type is <code class="computeroutput"><span class="identifier">omitted</span></code>, the generated tokens will
                 contain no token value (attribute) at all.
               </p></dd>
 <dt><span class="term">HasState</span></dt>
 <dd><p>
- This is either <tt class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">true_</span></tt>
- or <tt class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">false_</span></tt>, allowing to control whether
+ This is either <code class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">true_</span></code>
+ or <code class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">false_</span></code>, allowing to control whether
                 the generated token instances will contain the lexer state they were
                 generated in. The default is mpl::true_, so all token instances will
                 contain the lexer state.
@@ -189,18 +181,18 @@
 </div>
 <p>
             Normally, during its construction, a token instance always holds the
- boost::iterator_range<>
- as its token value (except, if it has been defined using the <tt class="computeroutput"><span class="identifier">omitted</span></tt> token value type). This iterator
+ boost::iterator_range<>
+ as its token value (except, if it has been defined using the <code class="computeroutput"><span class="identifier">omitted</span></code> token value type). This iterator
             range then is converted in place to the requested token value type (attribute)
             when it is requested for the first time.
           </p>
 <a name="spirit.lex.abstracts.lexer_primitives.lexer_token_values.the_physiognomy_of_a_token_definition"></a><h6>
-<a name="id494167"></a>
- <a href="lexer_token_values.html#spirit.lex.abstracts.lexer_primitives.lexer_token_values.the_physiognomy_of_a_token_definition">The
+<a name="id1105876"></a>
+ <a class="link" href="lexer_token_values.html#spirit.lex.abstracts.lexer_primitives.lexer_token_values.the_physiognomy_of_a_token_definition">The
             Physiognomy of a Token Definition</a>
           </h6>
 <p>
- The token definitions (represented by the token_def<>
+ The token definitions (represented by the <a class="link" href="../../reference/tokendef_class.html" title="TokenDef Class"><code class="computeroutput"><span class="identifier">token_def</span><span class="special">&lt;&gt;</span></code></a>
             template) are normally used as part of the definition of the lexical
             analyzer. At the same time a token definition instance may be used as
             a parser component in <span class="emphasis"><em>Spirit.Qi</em></span>.
@@ -214,7 +206,7 @@
 <span class="special">&gt;</span>
 <span class="keyword">class</span> <span class="identifier">token_def</span><span class="special">;</span>
 </pre>
-<div class="variablelist">
+<div class="variablelist" title="where:">
 <p class="title"><b>where:</b></p>
 <dl>
 <dt><span class="term">Attribute</span></dt>
@@ -223,17 +215,17 @@
                 instances representing this token type. This attribute type is exposed
                 to the <span class="emphasis"><em>Spirit.Qi</em></span> library, whenever this token
                 definition is used as a parser component. The default attribute type
- is <tt class="computeroutput"><span class="identifier">unused_type</span></tt>, which
- means the token instance holds a boost::iterator_range<>
+ is <code class="computeroutput"><span class="identifier">unused_type</span></code>, which
+ means the token instance holds a boost::iterator_range<>
                 pointing to the start and the end of the matched section in the input
- stream. If the attribute is <tt class="computeroutput"><span class="identifier">omitted</span></tt>
+ stream. If the attribute is <code class="computeroutput"><span class="identifier">omitted</span></code>
                 the token instance will expose no token type at all. Any other type
                 will be used directly as the token value type.
               </p></dd>
 <dt><span class="term">Char</span></dt>
 <dd><p>
                 This is the value type of the iterator for the underlying input sequence.
- It defaults to <tt class="computeroutput"><span class="keyword">char</span></tt>.
+ It defaults to <code class="computeroutput"><span class="keyword">char</span></code>.
               </p></dd>
 </dl>
 </div>
@@ -241,36 +233,36 @@
             The semantics of the template parameters for the token type and the token
             definition type are very similar and interdependent. As a rule of thumb
             you can think of the token definition type as the means of specifying
- everything related to a single specific token type (such as <tt class="computeroutput"><span class="identifier">identifier</span></tt> or <tt class="computeroutput"><span class="identifier">integer</span></tt>).
+ everything related to a single specific token type (such as <code class="computeroutput"><span class="identifier">identifier</span></code> or <code class="computeroutput"><span class="identifier">integer</span></code>).
             On the other hand the token type is used to define the general proerties
             of all token instances generated by the <span class="emphasis"><em>Spirit.Lex</em></span>
             library.
           </p>
-<div class="important"><table border="0" summary="Important">
+<div class="important" title="Important"><table border="0" summary="Important">
 <tr>
 <td rowspan="2" align="center" valign="top" width="25"><img alt="[Important]" src="../../../../images/important.png"></td>
 <th align="left">Important</th>
 </tr>
-<tr><td colspan="2" align="left" valign="top">
+<tr><td align="left" valign="top">
 <p>
               If you don't list any token value types in the token type definition
- declaration (resulting in the usage of the default boost::iterator_range<>
+ declaration (resulting in the usage of the default boost::iterator_range<>
               token type) everything will compile and work just fine, just a bit
               less efficient. This is because the token value will be converted from
               the matched input sequence every time it is requested.
             </p>
 <p>
               But as soon as you specify at least one token value type while defining
- the token type you'll have to list all value types used for token_def<>
+ the token type you'll have to list all value types used for <a class="link" href="../../reference/tokendef_class.html" title="TokenDef Class"><code class="computeroutput"><span class="identifier">token_def</span><span class="special">&lt;&gt;</span></code></a>
               declarations in the token definition class, otherwise compilation errors
               will occur.
             </p>
 </td></tr>
 </table></div>
 <a name="spirit.lex.abstracts.lexer_primitives.lexer_token_values.examples_of_using__link_linkend__spirit_lex_reference_token_class___code__phrase_role__identifier__lexertl_token__phrase__phrase_role__special___lt__gt___phrase___code___link_"></a><h6>
-<a name="id494578"></a>
- <a href="lexer_token_values.html#spirit.lex.abstracts.lexer_primitives.lexer_token_values.examples_of_using__link_linkend__spirit_lex_reference_token_class___code__phrase_role__identifier__lexertl_token__phrase__phrase_role__special___lt__gt___phrase___code___link_">Examples
- of using lexertl_token<></a>
+<a name="id1106475"></a>
+ <a class="link" href="lexer_token_values.html#spirit.lex.abstracts.lexer_primitives.lexer_token_values.examples_of_using__link_linkend__spirit_lex_reference_token_class___code__phrase_role__identifier__lexertl_token__phrase__phrase_role__special___lt__gt___phrase___code___link_">Examples
+ of using <a class="link" href="../../reference/token_class.html" title="Token Class"><code class="computeroutput"><span class="identifier">lexertl_token</span><span class="special">&lt;&gt;</span></code></a></a>
           </h6>
 <p>
             Let's start with some examples. We refer to one of the <span class="emphasis"><em>Spirit.Lex</em></span>
@@ -279,13 +271,13 @@
 <p>
             The first code snippet shows an excerpt of the token definition class,
             the definition of a couple of token types. Some of the token types do
- not expose a special token value (<tt class="computeroutput"><span class="identifier">if_</span></tt>,
- <tt class="computeroutput"><span class="identifier">else_</span></tt>, and <tt class="computeroutput"><span class="identifier">while_</span></tt>). Their token value will always
+ not expose a special token value (<code class="computeroutput"><span class="identifier">if_</span></code>,
+ <code class="computeroutput"><span class="identifier">else_</span></code>, and <code class="computeroutput"><span class="identifier">while_</span></code>). Their token value will always
             hold the iterator range of the matched input sequence only. The token
- definitions for the <tt class="computeroutput"><span class="identifier">identifier</span></tt>
- and the integer <tt class="computeroutput"><span class="identifier">constant</span></tt>
- are specialized to expose an explicit token type each: <tt class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">string</span></tt> and <tt class="computeroutput"><span class="keyword">unsigned</span>
- <span class="keyword">int</span></tt>.
+ definitions for the <code class="computeroutput"><span class="identifier">identifier</span></code>
+ and the integer <code class="computeroutput"><span class="identifier">constant</span></code>
+ are specialized to expose an explicit token type each: <code class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">string</span></code> and <code class="computeroutput"><span class="keyword">unsigned</span>
+ <span class="keyword">int</span></code>.
           </p>
 <p>
             </p>
@@ -318,7 +310,7 @@
 <p>
             As the parsers generated by <span class="emphasis"><em>Spirit.Qi</em></span> are fully
             attributed, any <span class="emphasis"><em>Spirit.Qi</em></span> parser component needs
- to expose a certain type as its parser attribute. Naturally, the token_def<> exposes the token value
+ to expose a certain type as its parser attribute. Naturally, the <a class="link" href="../../reference/tokendef_class.html" title="TokenDef Class"><code class="computeroutput"><span class="identifier">token_def</span><span class="special">&lt;&gt;</span></code></a> exposes the token value
             type as its parser attribute, enabling a smooth integration with <span class="emphasis"><em>Spirit.Qi</em></span>.
           </p>
 <p>
@@ -354,9 +346,9 @@
 <p>
           </p>
 <p>
- To avoid the token to have a token value at all, the special tag <tt class="computeroutput"><span class="identifier">omitted</span></tt> can be used: <tt class="computeroutput"><span class="identifier">token_def</span><span class="special">&lt;</span><span class="identifier">omitted</span><span class="special">&gt;</span></tt>
- and <tt class="computeroutput"><span class="identifier">lexertl_token</span><span class="special">&lt;</span><span class="identifier">base_iterator_type</span><span class="special">,</span>
- <span class="identifier">omitted</span><span class="special">&gt;</span></tt>.
+ To avoid the token to have a token value at all, the special tag <code class="computeroutput"><span class="identifier">omitted</span></code> can be used: <code class="computeroutput"><span class="identifier">token_def</span><span class="special">&lt;</span><span class="identifier">omitted</span><span class="special">&gt;</span></code>
+ and <code class="computeroutput"><span class="identifier">lexertl_token</span><span class="special">&lt;</span><span class="identifier">base_iterator_type</span><span class="special">,</span>
+ <span class="identifier">omitted</span><span class="special">&gt;</span></code>.
           </p>
 </div>
 <table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>

Modified: trunk/libs/spirit/doc/html/spirit/lex/abstracts/lexer_semantic_actions.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/lex/abstracts/lexer_semantic_actions.html (original)
+++ trunk/libs/spirit/doc/html/spirit/lex/abstracts/lexer_semantic_actions.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -1,16 +1,13 @@
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title> Lexer
- Semantic Actions</title>
+<title>Lexer Semantic Actions</title>
 <link rel="stylesheet" href="../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../index.html" title="Spirit 2.1">
-<link rel="up" href="../abstracts.html" title=" Abstracts">
-<link rel="previous" href="lexer_tokenizing.html" title=" Tokenizing
- Input Data">
-<link rel="next" href="lexer_static_model.html" title=" The Static
- Lexer Model">
+<link rel="up" href="../abstracts.html" title="Abstracts">
+<link rel="prev" href="lexer_tokenizing.html" title="Tokenizing Input Data">
+<link rel="next" href="lexer_static_model.html" title="The Static Lexer Model">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
 <table cellpadding="2" width="100%"><tr>
@@ -25,15 +22,11 @@
 <div class="spirit-nav">
 <a accesskey="p" href="lexer_tokenizing.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../abstracts.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="lexer_static_model.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h4 class="title">
-<a name="spirit.lex.abstracts.lexer_semantic_actions"></a><a href="lexer_semantic_actions.html" title=" Lexer
- Semantic Actions"> Lexer
+<div class="section" title="Lexer Semantic Actions">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="spirit.lex.abstracts.lexer_semantic_actions"></a><a class="link" href="lexer_semantic_actions.html" title="Lexer Semantic Actions"> Lexer
         Semantic Actions</a>
-</h4></div></div>
-<div></div>
-</div>
+</h4></div></div></div>
 <p>
           The main task of a lexer normally is to recognize tokens in the input.
           Traditionally this has been complemented with the possibility to execute
@@ -43,57 +36,57 @@
           and generators (<span class="emphasis"><em>Spirit.Karma</em></span>). Lexer semantic actions
           may be attached to any token definition. These are C++ functions or function
           objects that are called whenever a token definition successfully recognizes
- a portion of the input. Say you have a token definition <tt class="computeroutput"><span class="identifier">D</span></tt>,
- and a C++ function <tt class="computeroutput"><span class="identifier">f</span></tt>, you
- can make the lexer call <tt class="computeroutput"><span class="identifier">f</span></tt>
- whenever it matches an input by attaching <tt class="computeroutput"><span class="identifier">f</span></tt>:
+ a portion of the input. Say you have a token definition <code class="computeroutput"><span class="identifier">D</span></code>,
+ and a C++ function <code class="computeroutput"><span class="identifier">f</span></code>, you
+ can make the lexer call <code class="computeroutput"><span class="identifier">f</span></code>
+ whenever it matches an input by attaching <code class="computeroutput"><span class="identifier">f</span></code>:
         </p>
 <pre class="programlisting"><span class="identifier">D</span><span class="special">[</span><span class="identifier">f</span><span class="special">]</span>
 </pre>
 <p>
- The expression above links <tt class="computeroutput"><span class="identifier">f</span></tt>
- to the token definition, <tt class="computeroutput"><span class="identifier">D</span></tt>.
- The required prototype of <tt class="computeroutput"><span class="identifier">f</span></tt>
+ The expression above links <code class="computeroutput"><span class="identifier">f</span></code>
+ to the token definition, <code class="computeroutput"><span class="identifier">D</span></code>.
+ The required prototype of <code class="computeroutput"><span class="identifier">f</span></code>
           is:
         </p>
 <pre class="programlisting"><span class="keyword">void</span> <span class="identifier">f</span> <span class="special">(</span><span class="identifier">Iterator</span><span class="special">&amp;</span> <span class="identifier">start</span><span class="special">,</span> <span class="identifier">Iterator</span><span class="special">&amp;</span> <span class="identifier">end</span><span class="special">,</span> <span class="identifier">pass_flag</span><span class="special">&amp;</span> <span class="identifier">matched</span><span class="special">,</span> <span class="identifier">Idtype</span><span class="special">&amp;</span> <span class="identifier">id</span><span class="special">,</span> <span class="identifier">Context</span><span class="special">&amp;</span> <span class="identifier">ctx</span><span class="special">);</span>
 </pre>
-<div class="variablelist">
+<div class="variablelist" title="where:">
 <p class="title"><b>where:</b></p>
 <dl>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">Iterator</span><span class="special">&amp;</span> <span class="identifier">start</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">Iterator</span><span class="special">&amp;</span> <span class="identifier">start</span></code></span></dt>
 <dd><p>
               This is a the iterator pointing to the begin of the matched range in
               the underlying input sequence. The type of the iterator is the same
- as specified while defining the type of the <tt class="computeroutput"><span class="identifier">lexertl_lexer</span><span class="special">&lt;...&gt;</span></tt> (its first template parameter).
+ as specified while defining the type of the <code class="computeroutput"><span class="identifier">lexertl_lexer</span><span class="special">&lt;...&gt;</span></code> (its first template parameter).
               The semantic action is allowed to change the value of this iterator
               influencing, the matched input sequence.
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">Iterator</span><span class="special">&amp;</span> <span class="identifier">end</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">Iterator</span><span class="special">&amp;</span> <span class="identifier">end</span></code></span></dt>
 <dd><p>
               This is a the iterator pointing to the end of the matched range in
               the underlying input sequence. The type of the iterator is the same
- as specified while defining the type of the <tt class="computeroutput"><span class="identifier">lexertl_lexer</span><span class="special">&lt;...&gt;</span></tt> (its first template parameter).
+ as specified while defining the type of the <code class="computeroutput"><span class="identifier">lexertl_lexer</span><span class="special">&lt;...&gt;</span></code> (its first template parameter).
               The semantic action is allowed to change the value of this iterator
               influencing, the matched input sequence.
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">pass_flag</span><span class="special">&amp;</span> <span class="identifier">matched</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">pass_flag</span><span class="special">&amp;</span> <span class="identifier">matched</span></code></span></dt>
 <dd><p>
- This value is pre/initialized to <tt class="computeroutput"><span class="identifier">pass_normal</span></tt>.
- If the semantic action sets it to <tt class="computeroutput"><span class="identifier">pass_fail</span></tt>
+ This value is pre/initialized to <code class="computeroutput"><span class="identifier">pass_normal</span></code>.
+ If the semantic action sets it to <code class="computeroutput"><span class="identifier">pass_fail</span></code>
               the behaves as if the token has not been matched in the first place.
- If the semantic action sets this to <tt class="computeroutput"><span class="identifier">pass_ignore</span></tt>
+ If the semantic action sets this to <code class="computeroutput"><span class="identifier">pass_ignore</span></code>
               the lexer ignores the current token and tries to match a next token
               from the input.
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">Idtype</span><span class="special">&amp;</span> <span class="identifier">id</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">Idtype</span><span class="special">&amp;</span> <span class="identifier">id</span></code></span></dt>
 <dd><p>
               This is the token id of the type Idtype (most of the time this will
- be a <tt class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">size_t</span></tt>) for the matched token. The
+ be a <code class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">size_t</span></code>) for the matched token. The
               semantic action is allowed to change the value of this token id, influencing
               the if of the created token.
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">Context</span><span class="special">&amp;</span> <span class="identifier">ctx</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">Context</span><span class="special">&amp;</span> <span class="identifier">ctx</span></code></span></dt>
 <dd><p>
               This is a reference to a lexer specific, unspecified type, providing
               the context for the current lexer state. It can be used to access different
@@ -111,14 +104,14 @@
 <span class="keyword">void</span> <span class="identifier">f</span> <span class="special">(</span><span class="identifier">Iterator</span><span class="special">&amp;</span> <span class="identifier">start</span><span class="special">,</span> <span class="identifier">Iterator</span><span class="special">&amp;</span> <span class="identifier">end</span><span class="special">);</span>
 <span class="keyword">void</span> <span class="identifier">f</span> <span class="special">();</span>
 </pre>
-<a name="spirit.lex.abstracts.lexer_semantic_actions.the_context_of_a_lexer_semantic_action"></a><h5>
-<a name="id499297"></a>
- <a href="lexer_semantic_actions.html#spirit.lex.abstracts.lexer_semantic_actions.the_context_of_a_lexer_semantic_action">The
+<a name="spirit.lex.abstracts.lexer_semantic_actions.the_context_of_a_lexer_semantic_action"></a><h6>
+<a name="id1111512"></a>
+ <a class="link" href="lexer_semantic_actions.html#spirit.lex.abstracts.lexer_semantic_actions.the_context_of_a_lexer_semantic_action">The
           context of a lexer semantic action</a>
- </h5>
+ </h6>
 <p>
           The last parameter passed to any lexer semantic action is a reference to
- an unspecified type (see the <tt class="computeroutput"><span class="identifier">Context</span></tt>
+ an unspecified type (see the <code class="computeroutput"><span class="identifier">Context</span></code>
           type in the table above). This type is unspecified because it depends on
           the token type returned by the lexer. It is implemented in the internals
           of the iterator type exposed by the lexer. Nevertheless, any context type
@@ -127,103 +120,131 @@
           of the available functionality.
         </p>
 <div class="table">
-<a name="id499340"></a><p class="title"><b>Table 6. Functions exposed by any context passed to a lexer
+<a name="id1111533"></a><p class="title"><b>Table 6. Functions exposed by any context passed to a lexer
         semantic action</b></p>
-<table class="table" summary="Functions exposed by any context passed to a lexer
+<div class="table-contents"><table class="table" summary="Functions exposed by any context passed to a lexer
         semantic action">
 <colgroup>
 <col>
 <col>
 </colgroup>
 <thead><tr>
-<th><p>
+<th>
+ <p>
                 Name
- </p></th>
-<th><p>
+ </p>
+ </th>
+<th>
+ <p>
                 Description
- </p></th>
+ </p>
+ </th>
 </tr></thead>
 <tbody>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">Iterator</span> <span class="keyword">const</span><span class="special">&amp;</span> <span class="identifier">get_eoi</span><span class="special">()</span> <span class="keyword">const</span></tt>
- </p></td>
-<td><p>
- The function <tt class="computeroutput"><span class="identifier">get_eoi</span><span class="special">()</span></tt> may be used by to access the end
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">Iterator</span> <span class="keyword">const</span><span class="special">&amp;</span> <span class="identifier">get_eoi</span><span class="special">()</span> <span class="keyword">const</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ The function <code class="computeroutput"><span class="identifier">get_eoi</span><span class="special">()</span></code> may be used by to access the end
                 iterator of the input stream the lexer has been initialized with
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="keyword">void</span> <span class="identifier">more</span><span class="special">()</span></tt>
- </p></td>
-<td><p>
- The function <tt class="computeroutput"><span class="identifier">more</span><span class="special">()</span></tt> tells the lexer that the next time
+<td>
+ <p>
+ <code class="computeroutput"><span class="keyword">void</span> <span class="identifier">more</span><span class="special">()</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ The function <code class="computeroutput"><span class="identifier">more</span><span class="special">()</span></code> tells the lexer that the next time
                 it matches a rule, the corresponding token should be appended onto
                 the current token value rather than replacing it.
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">Iterator</span> <span class="keyword">const</span><span class="special">&amp;</span> <span class="identifier">less</span><span class="special">(</span><span class="identifier">Iterator</span>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">Iterator</span> <span class="keyword">const</span><span class="special">&amp;</span> <span class="identifier">less</span><span class="special">(</span><span class="identifier">Iterator</span>
                 <span class="keyword">const</span><span class="special">&amp;</span>
                 <span class="identifier">it</span><span class="special">,</span>
- <span class="keyword">int</span> <span class="identifier">n</span><span class="special">)</span></tt>
- </p></td>
-<td><p>
- The function <tt class="computeroutput"><span class="identifier">less</span><span class="special">()</span></tt> returns an iterator positioned
+ <span class="keyword">int</span> <span class="identifier">n</span><span class="special">)</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ The function <code class="computeroutput"><span class="identifier">less</span><span class="special">()</span></code> returns an iterator positioned
                 to the nth input character beyond the current token start iterator
- (i.e. by passing the return value to the parameter <tt class="computeroutput"><span class="identifier">end</span></tt> it is possible to return all
+ (i.e. by passing the return value to the parameter <code class="computeroutput"><span class="identifier">end</span></code> it is possible to return all
                 but the first n characters of the current token back to the input
                 stream.
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="keyword">bool</span> <span class="identifier">lookahead</span><span class="special">(</span><span class="identifier">std</span><span class="special">::</span><span class="identifier">size_t</span>
- <span class="identifier">id</span><span class="special">)</span></tt>
- </p></td>
-<td><p>
- The function <tt class="computeroutput"><span class="identifier">lookahead</span><span class="special">()</span></tt> can be for instance used to implement
+<td>
+ <p>
+ <code class="computeroutput"><span class="keyword">bool</span> <span class="identifier">lookahead</span><span class="special">(</span><span class="identifier">std</span><span class="special">::</span><span class="identifier">size_t</span>
+ <span class="identifier">id</span><span class="special">)</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ The function <code class="computeroutput"><span class="identifier">lookahead</span><span class="special">()</span></code> can be for instance used to implement
                 lookahead for lexer engines not supporting constructs like flex'
- <tt class="computeroutput"><span class="identifier">a</span><span class="special">/</span><span class="identifier">b</span></tt> (match <tt class="computeroutput"><span class="identifier">a</span></tt>,
- but only when followed by <tt class="computeroutput"><span class="identifier">b</span></tt>).
+ <code class="computeroutput"><span class="identifier">a</span><span class="special">/</span><span class="identifier">b</span></code> (match <code class="computeroutput"><span class="identifier">a</span></code>,
+ but only when followed by <code class="computeroutput"><span class="identifier">b</span></code>).
                 It invokes the lexer on the input following the current token without
                 actually moving forward in the input stream. The function returns
                 whether the lexer was able to match a token with the given token-id
- <tt class="computeroutput"><span class="identifier">id</span></tt>.
- </p></td>
+ <code class="computeroutput"><span class="identifier">id</span></code>.
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">size_t</span> <span class="identifier">get_state</span><span class="special">()</span> <span class="keyword">const</span></tt>
- and <tt class="computeroutput"><span class="keyword">void</span> <span class="identifier">set_state</span><span class="special">(</span><span class="identifier">std</span><span class="special">::</span><span class="identifier">size_t</span>
- <span class="identifier">state</span><span class="special">)</span></tt>
- </p></td>
-<td><p>
- The functions <tt class="computeroutput"><span class="identifier">get_state</span><span class="special">()</span></tt> and <tt class="computeroutput"><span class="identifier">set_state</span><span class="special">()</span></tt> may be used to introspect and change
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">size_t</span> <span class="identifier">get_state</span><span class="special">()</span> <span class="keyword">const</span></code>
+ and <code class="computeroutput"><span class="keyword">void</span> <span class="identifier">set_state</span><span class="special">(</span><span class="identifier">std</span><span class="special">::</span><span class="identifier">size_t</span>
+ <span class="identifier">state</span><span class="special">)</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ The functions <code class="computeroutput"><span class="identifier">get_state</span><span class="special">()</span></code> and <code class="computeroutput"><span class="identifier">set_state</span><span class="special">()</span></code> may be used to introspect and change
                 the current lexer state.
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">token_value_type</span> <span class="identifier">get_value</span><span class="special">()</span>
- <span class="keyword">const</span></tt> and <tt class="computeroutput"><span class="keyword">void</span>
- <span class="identifier">set_value</span><span class="special">(</span><span class="identifier">Value</span> <span class="keyword">const</span><span class="special">&amp;)</span></tt>
- </p></td>
-<td><p>
- The functions <tt class="computeroutput"><span class="identifier">get_value</span><span class="special">()</span></tt> and <tt class="computeroutput"><span class="identifier">set_value</span><span class="special">()</span></tt> may be used to introspect and change
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">token_value_type</span> <span class="identifier">get_value</span><span class="special">()</span>
+ <span class="keyword">const</span></code> and <code class="computeroutput"><span class="keyword">void</span>
+ <span class="identifier">set_value</span><span class="special">(</span><span class="identifier">Value</span> <span class="keyword">const</span><span class="special">&amp;)</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ The functions <code class="computeroutput"><span class="identifier">get_value</span><span class="special">()</span></code> and <code class="computeroutput"><span class="identifier">set_value</span><span class="special">()</span></code> may be used to introspect and change
                 the current token value.
- </p></td>
+ </p>
+ </td>
 </tr>
 </tbody>
-</table>
+</table></div>
 </div>
-<a name="spirit.lex.abstracts.lexer_semantic_actions.lexer_semantic_actions_using_phoenix"></a><h5>
-<a name="id500064"></a>
- <a href="lexer_semantic_actions.html#spirit.lex.abstracts.lexer_semantic_actions.lexer_semantic_actions_using_phoenix">Lexer
+<br class="table-break"><a name="spirit.lex.abstracts.lexer_semantic_actions.lexer_semantic_actions_using_phoenix"></a><h6>
+<a name="id1112051"></a>
+ <a class="link" href="lexer_semantic_actions.html#spirit.lex.abstracts.lexer_semantic_actions.lexer_semantic_actions_using_phoenix">Lexer
           Semantic Actions Using Phoenix</a>
- </h5>
+ </h6>
 <p>
           Even if it is possible to write your own function object implementations
           (i.e. using Boost.Lambda or Boost.Bind), the preferred way of defining
@@ -232,98 +253,130 @@
           predefined Spirit placeholders:
         </p>
 <div class="table">
-<a name="id500105"></a><p class="title"><b>Table 7. Predefined Phoenix placeholders for lexer semantic
+<a name="id1112074"></a><p class="title"><b>Table 7. Predefined Phoenix placeholders for lexer semantic
         actions</b></p>
-<table class="table" summary="Predefined Phoenix placeholders for lexer semantic
+<div class="table-contents"><table class="table" summary="Predefined Phoenix placeholders for lexer semantic
         actions">
 <colgroup>
 <col>
 <col>
 </colgroup>
 <thead><tr>
-<th><p>
+<th>
+ <p>
                 Placeholder
- </p></th>
-<th><p>
+ </p>
+ </th>
+<th>
+ <p>
                 Description
- </p></th>
+ </p>
+ </th>
 </tr></thead>
 <tbody>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">_start</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">_start</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                 Refers to the iterator pointing to the begin of the matched input
                 sequence. Any modifications to this iterator value will be reflected
                 in the generated token.
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">_end</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">_end</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                 Refers to the iterator pointing past the end of the matched input
                 sequence. Any modifications to this iterator value will be reflected
                 in the generated token.
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">_pass</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">_pass</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                 References the value signaling the outcome of the semantic action.
- This is pre-initialized to <tt class="computeroutput"><span class="identifier">lex</span><span class="special">::</span><span class="identifier">pass_flags</span><span class="special">::</span><span class="identifier">pass_normal</span></tt>.
- If this is set to <tt class="computeroutput"><span class="identifier">lex</span><span class="special">::</span><span class="identifier">pass_flags</span><span class="special">::</span><span class="identifier">pass_fail</span></tt>,
+ This is pre-initialized to <code class="computeroutput"><span class="identifier">lex</span><span class="special">::</span><span class="identifier">pass_flags</span><span class="special">::</span><span class="identifier">pass_normal</span></code>.
+ If this is set to <code class="computeroutput"><span class="identifier">lex</span><span class="special">::</span><span class="identifier">pass_flags</span><span class="special">::</span><span class="identifier">pass_fail</span></code>,
                 the lexer will behave as if no token has been matched, if is set
- to <tt class="computeroutput"><span class="identifier">lex</span><span class="special">::</span><span class="identifier">pass_flags</span><span class="special">::</span><span class="identifier">pass_ignore</span></tt>, the lexer will ignore
+ to <code class="computeroutput"><span class="identifier">lex</span><span class="special">::</span><span class="identifier">pass_flags</span><span class="special">::</span><span class="identifier">pass_ignore</span></code>, the lexer will ignore
                 the current match and proceed trying to match tokens from the input.
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">_tokenid</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">_tokenid</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                 Refers to the token id of the token to be generated. Any modifications
                 to this value will be reflected in the generated token.
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">_val</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">_val</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                 Refers to the value the next token will be initialized from. Any
                 modifications to this value will be reflected in the generated token.
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">_state</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">_state</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                 Refers to the lexer state the input has been match in. Any modifications
                 to this value will be reflected in the lexer itself (the next match
                 will start in the new state). The currently generated token is not
                 affected by changes to this variable.
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">_eoi</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">_eoi</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                 References the end iterator of the overall lexer input. This value
                 cannot be changed.
- </p></td>
+ </p>
+ </td>
 </tr>
 </tbody>
-</table>
+</table></div>
 </div>
-<p>
+<br class="table-break"><p>
           The context object passed as the last parameter to any lexer semantic action
           is not directly accessible while using Boost.Phoenix
           expressions. We rather provide predefine Phoenix functions allowing to
@@ -331,9 +384,9 @@
           table lists the available support functions and describes their functionality:
         </p>
 <div class="table">
-<a name="id500485"></a><p class="title"><b>Table 8. Support functions usable from Phoenix expressions
+<a name="id1112448"></a><p class="title"><b>Table 8. Support functions usable from Phoenix expressions
         inside lexer semantic actions</b></p>
-<table class="table" summary="Support functions usable from Phoenix expressions
+<div class="table-contents"><table class="table" summary="Support functions usable from Phoenix expressions
         inside lexer semantic actions">
 <colgroup>
 <col>
@@ -341,69 +394,94 @@
 <col>
 </colgroup>
 <thead><tr>
-<th><p>
+<th>
+ <p>
                 Plain function
- </p></th>
-<th><p>
+ </p>
+ </th>
+<th>
+ <p>
                 Phoenix function
- </p></th>
-<th><p>
+ </p>
+ </th>
+<th>
+ <p>
                 Description
- </p></th>
+ </p>
+ </th>
 </tr></thead>
 <tbody>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">ctx</span><span class="special">.</span><span class="identifier">more</span><span class="special">()</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">more</span><span class="special">()</span></tt>
- </p></td>
-<td><p>
- The function <tt class="computeroutput"><span class="identifier">more</span><span class="special">()</span></tt> tells the lexer that the next time
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">ctx</span><span class="special">.</span><span class="identifier">more</span><span class="special">()</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">more</span><span class="special">()</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ The function <code class="computeroutput"><span class="identifier">more</span><span class="special">()</span></code> tells the lexer that the next time
                 it matches a rule, the corresponding token should be appended onto
                 the current token value rather than replacing it.
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">ctx</span><span class="special">.</span><span class="identifier">less</span><span class="special">()</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">less</span><span class="special">(</span><span class="identifier">n</span><span class="special">)</span></tt>
- </p></td>
-<td><p>
- The function <tt class="computeroutput"><span class="identifier">less</span><span class="special">()</span></tt> takes a single integer parameter
- <tt class="computeroutput"><span class="identifier">n</span></tt> and returns an
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">ctx</span><span class="special">.</span><span class="identifier">less</span><span class="special">()</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">less</span><span class="special">(</span><span class="identifier">n</span><span class="special">)</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ The function <code class="computeroutput"><span class="identifier">less</span><span class="special">()</span></code> takes a single integer parameter
+ <code class="computeroutput"><span class="identifier">n</span></code> and returns an
                 iterator positioned to the nth input character beyond the current
                 token start iterator (i.e. by assigning the return value to the placeholder
- <tt class="computeroutput"><span class="identifier">_end</span></tt> it is possible
- to return all but the first <tt class="computeroutput"><span class="identifier">n</span></tt>
+ <code class="computeroutput"><span class="identifier">_end</span></code> it is possible
+ to return all but the first <code class="computeroutput"><span class="identifier">n</span></code>
                 characters of the current token back to the input stream.
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">ctx</span><span class="special">.</span><span class="identifier">lookahead</span><span class="special">()</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">lookahead</span><span class="special">(</span><span class="identifier">std</span><span class="special">::</span><span class="identifier">size_t</span><span class="special">)</span></tt>
- or <tt class="computeroutput"><span class="identifier">lookahead</span><span class="special">(</span><span class="identifier">token_def</span><span class="special">)</span></tt>
- </p></td>
-<td><p>
- The function <tt class="computeroutput"><span class="identifier">lookahead</span><span class="special">()</span></tt> takes a single parameter specifying
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">ctx</span><span class="special">.</span><span class="identifier">lookahead</span><span class="special">()</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">lookahead</span><span class="special">(</span><span class="identifier">std</span><span class="special">::</span><span class="identifier">size_t</span><span class="special">)</span></code>
+ or <code class="computeroutput"><span class="identifier">lookahead</span><span class="special">(</span><span class="identifier">token_def</span><span class="special">)</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ The function <code class="computeroutput"><span class="identifier">lookahead</span><span class="special">()</span></code> takes a single parameter specifying
                 the token to match in the input. The function can be used for instance
                 to implement lookahead for lexer engines not supporting constructs
- like flex' <tt class="computeroutput"><span class="identifier">a</span><span class="special">/</span><span class="identifier">b</span></tt> (match <tt class="computeroutput"><span class="identifier">a</span></tt>,
- but only when followed by <tt class="computeroutput"><span class="identifier">b</span></tt>).
+ like flex' <code class="computeroutput"><span class="identifier">a</span><span class="special">/</span><span class="identifier">b</span></code> (match <code class="computeroutput"><span class="identifier">a</span></code>,
+ but only when followed by <code class="computeroutput"><span class="identifier">b</span></code>).
                 It invokes the lexer on the input following the current token without
                 actually moving forward in the input stream. The function returns
                 whether the lexer was able to match the specified token.
- </p></td>
+ </p>
+ </td>
 </tr>
 </tbody>
-</table>
+</table></div>
 </div>
+<br class="table-break">
 </div>
 <table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
 <td align="left"></td>

Modified: trunk/libs/spirit/doc/html/spirit/lex/abstracts/lexer_states.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/lex/abstracts/lexer_states.html (original)
+++ trunk/libs/spirit/doc/html/spirit/lex/abstracts/lexer_states.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -1,13 +1,13 @@
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title> Lexer States</title>
+<title>Lexer States</title>
 <link rel="stylesheet" href="../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../index.html" title="Spirit 2.1">
-<link rel="up" href="../abstracts.html" title=" Abstracts">
-<link rel="previous" href="lexer_attributes.html" title=" Lexer Attributes">
-<link rel="next" href="../quick_reference.html" title=" Quick Reference">
+<link rel="up" href="../abstracts.html" title="Abstracts">
+<link rel="prev" href="lexer_attributes.html" title="Lexer Attributes">
+<link rel="next" href="../quick_reference.html" title="Quick Reference">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
 <table cellpadding="2" width="100%"><tr>
@@ -22,28 +22,25 @@
 <div class="spirit-nav">
 <a accesskey="p" href="lexer_attributes.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../abstracts.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="../quick_reference.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h4 class="title">
-<a name="spirit.lex.abstracts.lexer_states"></a> Lexer States
-</h4></div></div>
-<div></div>
-</div>
-<a name="spirit.lex.abstracts.lexer_states.controlling_the_lexer_state_from_lexer_semantic_actions"></a><h5>
-<a name="id504388"></a>
- <a href="lexer_states.html#spirit.lex.abstracts.lexer_states.controlling_the_lexer_state_from_lexer_semantic_actions">Controlling
+<div class="section" title="Lexer States">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="spirit.lex.abstracts.lexer_states"></a><a class="link" href="lexer_states.html" title="Lexer States"> Lexer States</a>
+</h4></div></div></div>
+<a name="spirit.lex.abstracts.lexer_states.controlling_the_lexer_state_from_lexer_semantic_actions"></a><h6>
+<a name="id1115485"></a>
+ <a class="link" href="lexer_states.html#spirit.lex.abstracts.lexer_states.controlling_the_lexer_state_from_lexer_semantic_actions">Controlling
           the Lexer State from Lexer Semantic Actions</a>
- </h5>
-<a name="spirit.lex.abstracts.lexer_states.controlling_the_lexer_state_from_parser_semantic_actions"></a><h5>
-<a name="id504415"></a>
- <a href="lexer_states.html#spirit.lex.abstracts.lexer_states.controlling_the_lexer_state_from_parser_semantic_actions">Controlling
+ </h6>
+<a name="spirit.lex.abstracts.lexer_states.controlling_the_lexer_state_from_parser_semantic_actions"></a><h6>
+<a name="id1115499"></a>
+ <a class="link" href="lexer_states.html#spirit.lex.abstracts.lexer_states.controlling_the_lexer_state_from_parser_semantic_actions">Controlling
           the Lexer State from Parser Semantic Actions</a>
- </h5>
-<a name="spirit.lex.abstracts.lexer_states.using_a_lexer_state_for_the_skip_parser"></a><h5>
-<a name="id504444"></a>
- <a href="lexer_states.html#spirit.lex.abstracts.lexer_states.using_a_lexer_state_for_the_skip_parser">Using
+ </h6>
+<a name="spirit.lex.abstracts.lexer_states.using_a_lexer_state_for_the_skip_parser"></a><h6>
+<a name="id1115512"></a>
+ <a class="link" href="lexer_states.html#spirit.lex.abstracts.lexer_states.using_a_lexer_state_for_the_skip_parser">Using
           a Lexer State for the Skip Parser</a>
- </h5>
+ </h6>
 </div>
 <table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
 <td align="left"></td>

Modified: trunk/libs/spirit/doc/html/spirit/lex/abstracts/lexer_static_model.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/lex/abstracts/lexer_static_model.html (original)
+++ trunk/libs/spirit/doc/html/spirit/lex/abstracts/lexer_static_model.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -1,16 +1,13 @@
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title> The Static
- Lexer Model</title>
+<title>The Static Lexer Model</title>
 <link rel="stylesheet" href="../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../index.html" title="Spirit 2.1">
-<link rel="up" href="../abstracts.html" title=" Abstracts">
-<link rel="previous" href="lexer_semantic_actions.html" title=" Lexer
- Semantic Actions">
-<link rel="next" href="lexer_parsing.html" title=" Parsing using
- a Lexer">
+<link rel="up" href="../abstracts.html" title="Abstracts">
+<link rel="prev" href="lexer_semantic_actions.html" title="Lexer Semantic Actions">
+<link rel="next" href="lexer_parsing.html" title="Parsing using a Lexer">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
 <table cellpadding="2" width="100%"><tr>
@@ -25,15 +22,11 @@
 <div class="spirit-nav">
 <a accesskey="p" href="lexer_semantic_actions.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../abstracts.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="lexer_parsing.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h4 class="title">
-<a name="spirit.lex.abstracts.lexer_static_model"></a><a href="lexer_static_model.html" title=" The Static
- Lexer Model"> The <span class="emphasis"><em>Static</em></span>
+<div class="section" title="The Static Lexer Model">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="spirit.lex.abstracts.lexer_static_model"></a><a class="link" href="lexer_static_model.html" title="The Static Lexer Model"> The <span class="emphasis"><em>Static</em></span>
         Lexer Model</a>
-</h4></div></div>
-<div></div>
-</div>
+</h4></div></div></div>
 <p>
           The documentation of <span class="emphasis"><em>Spirit.Lex</em></span> so far mostly was
           about describing the features of the <span class="emphasis"><em>dynamic</em></span> model,
@@ -57,12 +50,12 @@
           Assuming you already built a dynamic lexer for your problem, there are
           two more steps needed to create a static lexical analyzer using <span class="emphasis"><em>Spirit.Lex</em></span>:
         </p>
-<div class="orderedlist"><ol type="1">
-<li>
+<div class="orderedlist"><ol class="orderedlist" type="1">
+<li class="listitem">
             generating the C++ code for the static analyzer (including the tokenization
             function and corresponding tables), and
           </li>
-<li>
+<li class="listitem">
             modifying the dynamic lexical anlyzer to use the generated code.
           </li>
 </ol></div>
@@ -132,8 +125,8 @@
 <p>
           The only thing changing between the three different use cases is the template
           parameter used to instantiate a concrete token definition. Fot the dynamic
- model and the code generator you probably will use the lexertl_lexer<>
- template, where for the static model you will use the lexertl_static_lexer<>
+ model and the code generator you probably will use the <a class="link" href="../reference/lexer_class.html#spirit.lex.reference.lexer_class.the_lexertl_lexer_class_implementing_the_dynamic_model"><code class="computeroutput"><span class="identifier">lexertl_lexer</span><span class="special">&lt;&gt;</span></code></a>
+ template, where for the static model you will use the <a class="link" href="../reference/lexer_class.html#spirit.lex.reference.lexer_class.the_lexertl_static_lexer_class_implementing_the_static_model"><code class="computeroutput"><span class="identifier">lexertl_static_lexer</span><span class="special">&lt;&gt;</span></code></a>
           type as the template parameter.
         </p>
 <p>
@@ -182,17 +175,17 @@
           </p>
 <p>
         </p>
-<a name="spirit.lex.abstracts.lexer_static_model.generating_the_static_analyzer"></a><h5>
-<a name="id502529"></a>
- <a href="lexer_static_model.html#spirit.lex.abstracts.lexer_static_model.generating_the_static_analyzer">Generating
+<a name="spirit.lex.abstracts.lexer_static_model.generating_the_static_analyzer"></a><h6>
+<a name="id1113898"></a>
+ <a class="link" href="lexer_static_model.html#spirit.lex.abstracts.lexer_static_model.generating_the_static_analyzer">Generating
           the Static Analyzer</a>
- </h5>
+ </h6>
 <p>
           The first additional step to perform in order to create a static lexical
           analyzer is to create a small standalone program for creating the lexer
           tables and the corresponding tokenization function. For this purpose the
           <span class="emphasis"><em>Spirit.Lex</em></span> library exposes a special API - the function
- generate_static().
+ <a class="link" href="../../../"><code class="computeroutput"><span class="identifier">generate_static</span><span class="special">()</span></code></a>.
           It implements the whole code generator, no further code is needed. All
           what it takes to invoke this function is to supply a token definition instance,
           an output stream to use to generate the code to, and an optional string
@@ -231,20 +224,20 @@
           a file for later inclusion into the static lexical analzyer as shown in
           the next topic (the full generated code can be viewed here).
         </p>
-<a name="spirit.lex.abstracts.lexer_static_model.modifying_the_dynamic_analyzer"></a><h5>
-<a name="id502993"></a>
- <a href="lexer_static_model.html#spirit.lex.abstracts.lexer_static_model.modifying_the_dynamic_analyzer">Modifying
+<a name="spirit.lex.abstracts.lexer_static_model.modifying_the_dynamic_analyzer"></a><h6>
+<a name="id1114226"></a>
+ <a class="link" href="lexer_static_model.html#spirit.lex.abstracts.lexer_static_model.modifying_the_dynamic_analyzer">Modifying
           the Dynamic Analyzer</a>
- </h5>
+ </h6>
 <p>
           The second required step to convert an existing dynamic lexer into a static
           one is to change your main program at two places. First, you need to change
           the type of the used lexer (that is the template parameter used while instantiating
           your token definition class). While in the dynamic model we have been using
- the lexertl_lexer<>
- template, we now need to change that to the lexertl_static_lexer<>
+ the <a class="link" href="../reference/lexer_class.html#spirit.lex.reference.lexer_class.the_lexertl_lexer_class_implementing_the_dynamic_model"><code class="computeroutput"><span class="identifier">lexertl_lexer</span><span class="special">&lt;&gt;</span></code></a>
+ template, we now need to change that to the <a class="link" href="../reference/lexer_class.html#spirit.lex.reference.lexer_class.the_lexertl_static_lexer_class_implementing_the_static_model"><code class="computeroutput"><span class="identifier">lexertl_static_lexer</span><span class="special">&lt;&gt;</span></code></a>
           type. The second change is tightly related to the first one and involves
- correcting the corresponding <tt class="computeroutput"><span class="preprocessor">#include</span></tt>
+ correcting the corresponding <code class="computeroutput"><span class="preprocessor">#include</span></code>
           statement to:
         </p>
 <p>

Modified: trunk/libs/spirit/doc/html/spirit/lex/abstracts/lexer_tokenizing.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/lex/abstracts/lexer_tokenizing.html (original)
+++ trunk/libs/spirit/doc/html/spirit/lex/abstracts/lexer_tokenizing.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -1,16 +1,13 @@
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title> Tokenizing
- Input Data</title>
+<title>Tokenizing Input Data</title>
 <link rel="stylesheet" href="../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../index.html" title="Spirit 2.1">
-<link rel="up" href="../abstracts.html" title=" Abstracts">
-<link rel="previous" href="lexer_primitives/lexer_token_definition.html" title="
- Ways to define Tokens">
-<link rel="next" href="lexer_semantic_actions.html" title=" Lexer
- Semantic Actions">
+<link rel="up" href="../abstracts.html" title="Abstracts">
+<link rel="prev" href="lexer_primitives/lexer_token_definition.html" title="Ways to define Tokens">
+<link rel="next" href="lexer_semantic_actions.html" title="Lexer Semantic Actions">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
 <table cellpadding="2" width="100%"><tr>
@@ -25,28 +22,23 @@
 <div class="spirit-nav">
 <a accesskey="p" href="lexer_primitives/lexer_token_definition.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../abstracts.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="lexer_semantic_actions.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h4 class="title">
-<a name="spirit.lex.abstracts.lexer_tokenizing"></a><a href="lexer_tokenizing.html" title=" Tokenizing
- Input Data"> Tokenizing
+<div class="section" title="Tokenizing Input Data">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="spirit.lex.abstracts.lexer_tokenizing"></a><a class="link" href="lexer_tokenizing.html" title="Tokenizing Input Data"> Tokenizing
         Input Data</a>
-</h4></div></div>
-<div></div>
-</div>
-<a name="spirit.lex.abstracts.lexer_tokenizing.the_tokenize_function"></a><h5>
-<a name="id495386"></a>
- <a href="lexer_tokenizing.html#spirit.lex.abstracts.lexer_tokenizing.the_tokenize_function">The
+</h4></div></div></div>
+<a name="spirit.lex.abstracts.lexer_tokenizing.the_tokenize_function"></a><h6>
+<a name="id1107002"></a>
+ <a class="link" href="lexer_tokenizing.html#spirit.lex.abstracts.lexer_tokenizing.the_tokenize_function">The
           tokenize function</a>
- </h5>
+ </h6>
 <p>
- The <tt class="computeroutput"><span class="identifier">tokenize</span><span class="special">()</span></tt>
+ The <code class="computeroutput"><span class="identifier">tokenize</span><span class="special">()</span></code>
           function is a helper function simplifying the usage of a lexer in a standalone
           fashion. Consider you have a standalone lexer where all the required functionality
           is implemented inside of lexer semantic actions. A good example for this
           is the word_count_lexer
- described in more detail in the section <a href="../tutorials/lexer_quickstart2.html" title=" Quickstart
- 2 - A better word counter using Spirit.Lex">Lex
+ described in more detail in the section <a class="link" href="../tutorials/lexer_quickstart2.html" title="Quickstart 2 - A better word counter using Spirit.Lex">Lex
           Quickstart 2 - A better word counter using <span class="emphasis"><em>Spirit.Lex</em></span></a>.
           As a reminder, here is the token definition class:
         </p>
@@ -87,7 +79,7 @@
 <p>
           The construct used to tokenize the given input, while discarding all generated
           tokens is a common application of the lexer. For this reason <span class="emphasis"><em>Spirit.Lex</em></span>
- exposes an API function <tt class="computeroutput"><span class="identifier">tokenize</span><span class="special">()</span></tt> minimizing the code required:
+ exposes an API function <code class="computeroutput"><span class="identifier">tokenize</span><span class="special">()</span></code> minimizing the code required:
         </p>
 <pre class="programlisting"><span class="comment">// Read input from the given file
 </span><span class="identifier">std</span><span class="special">::</span><span class="identifier">string</span> <span class="identifier">str</span> <span class="special">(</span><span class="identifier">read_from_file</span><span class="special">(</span><span class="number">1</span> <span class="special">==</span> <span class="identifier">argc</span> <span class="special">?</span> <span class="string">"word_count.input"</span> <span class="special">:</span> <span class="identifier">argv</span><span class="special">[</span><span class="number">1</span><span class="special">]));</span>
@@ -100,15 +92,14 @@
 </pre>
 <p>
           This code is completely equivalent to the more verbose version as shown
- in the section <a href="../tutorials/lexer_quickstart2.html" title=" Quickstart
- 2 - A better word counter using Spirit.Lex">Lex
+ in the section <a class="link" href="../tutorials/lexer_quickstart2.html" title="Quickstart 2 - A better word counter using Spirit.Lex">Lex
           Quickstart 2 - A better word counter using <span class="emphasis"><em>Spirit.Lex</em></span></a>.
- The function <tt class="computeroutput"><span class="identifier">tokenize</span><span class="special">()</span></tt>
+ The function <code class="computeroutput"><span class="identifier">tokenize</span><span class="special">()</span></code>
           will return either if the end of the input has been reached (in this case
- the return value will be <tt class="computeroutput"><span class="keyword">true</span></tt>),
+ the return value will be <code class="computeroutput"><span class="keyword">true</span></code>),
           or if the lexer couldn't match any of the token definitions in the input
- (in this case the return value will be <tt class="computeroutput"><span class="keyword">false</span></tt>
- and the iterator <tt class="computeroutput"><span class="identifier">first</span></tt>
+ (in this case the return value will be <code class="computeroutput"><span class="keyword">false</span></code>
+ and the iterator <code class="computeroutput"><span class="identifier">first</span></code>
           will point to the first not matched character in the input sequence).
         </p>
 <p>
@@ -118,7 +109,7 @@
 <span class="keyword">bool</span> <span class="identifier">tokenize</span><span class="special">(</span><span class="identifier">Iterator</span><span class="special">&amp;</span> <span class="identifier">first</span><span class="special">,</span> <span class="identifier">Iterator</span> <span class="identifier">last</span><span class="special">,</span> <span class="identifier">Lexer</span> <span class="keyword">const</span><span class="special">&amp;</span> <span class="identifier">lex</span>
   <span class="special">,</span> <span class="keyword">typename</span> <span class="identifier">Lexer</span><span class="special">::</span><span class="identifier">char_type</span> <span class="keyword">const</span><span class="special">*</span> <span class="identifier">initial_state</span> <span class="special">=</span> <span class="number">0</span><span class="special">);</span>
 </pre>
-<div class="variablelist">
+<div class="variablelist" title="where:">
 <p class="title"><b>where:</b></p>
 <dl>
 <dt><span class="term">Iterator&amp; first</span></dt>
@@ -143,7 +134,7 @@
 </dl>
 </div>
 <p>
- A second overload of the <tt class="computeroutput"><span class="identifier">tokenize</span><span class="special">()</span></tt> function allows to specify any arbitrary
+ A second overload of the <code class="computeroutput"><span class="identifier">tokenize</span><span class="special">()</span></code> function allows to specify any arbitrary
           function or function object to be called for each of the generated tokens.
           For some applications this is very useful, as it might avoid having lexer
           semantic actions. For an example of how to use this function, please have
@@ -152,10 +143,10 @@
 <p>
           </p>
 <p>
- The main function simply loads the given file into memory (as a <tt class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">string</span></tt>), instantiates an instance of
- the token definition template using the correct iterator type (<tt class="computeroutput"><span class="identifier">word_count_tokens</span><span class="special">&lt;</span><span class="keyword">char</span> <span class="keyword">const</span><span class="special">*&gt;</span></tt>), and finally calls <tt class="computeroutput"><span class="identifier">lex</span><span class="special">::</span><span class="identifier">tokenize</span></tt>, passing an instance of the
- counter function object. The return value of <tt class="computeroutput"><span class="identifier">lex</span><span class="special">::</span><span class="identifier">tokenize</span><span class="special">()</span></tt> will be <tt class="computeroutput"><span class="keyword">true</span></tt>
- if the whole input sequence has been successfully tokenized, and <tt class="computeroutput"><span class="keyword">false</span></tt> otherwise.
+ The main function simply loads the given file into memory (as a <code class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">string</span></code>), instantiates an instance of
+ the token definition template using the correct iterator type (<code class="computeroutput"><span class="identifier">word_count_tokens</span><span class="special">&lt;</span><span class="keyword">char</span> <span class="keyword">const</span><span class="special">*&gt;</span></code>), and finally calls <code class="computeroutput"><span class="identifier">lex</span><span class="special">::</span><span class="identifier">tokenize</span></code>, passing an instance of the
+ counter function object. The return value of <code class="computeroutput"><span class="identifier">lex</span><span class="special">::</span><span class="identifier">tokenize</span><span class="special">()</span></code> will be <code class="computeroutput"><span class="keyword">true</span></code>
+ if the whole input sequence has been successfully tokenized, and <code class="computeroutput"><span class="keyword">false</span></code> otherwise.
           </p>
 <p>
           </p>
@@ -198,13 +189,13 @@
 <p>
         </p>
 <p>
- Here is the prototype of this <tt class="computeroutput"><span class="identifier">tokenize</span><span class="special">()</span></tt> function overload:
+ Here is the prototype of this <code class="computeroutput"><span class="identifier">tokenize</span><span class="special">()</span></code> function overload:
         </p>
 <pre class="programlisting"><span class="keyword">template</span> <span class="special">&lt;</span><span class="keyword">typename</span> <span class="identifier">Iterator</span><span class="special">,</span> <span class="keyword">typename</span> <span class="identifier">Lexer</span><span class="special">,</span> <span class="keyword">typename</span> <span class="identifier">F</span><span class="special">&gt;</span>
 <span class="keyword">bool</span> <span class="identifier">tokenize</span><span class="special">(</span><span class="identifier">Iterator</span><span class="special">&amp;</span> <span class="identifier">first</span><span class="special">,</span> <span class="identifier">Iterator</span> <span class="identifier">last</span><span class="special">,</span> <span class="identifier">Lexer</span> <span class="keyword">const</span><span class="special">&amp;</span> <span class="identifier">lex</span><span class="special">,</span> <span class="identifier">F</span> <span class="identifier">f</span>
   <span class="special">,</span> <span class="keyword">typename</span> <span class="identifier">Lexer</span><span class="special">::</span><span class="identifier">char_type</span> <span class="keyword">const</span><span class="special">*</span> <span class="identifier">initial_state</span> <span class="special">=</span> <span class="number">0</span><span class="special">);</span>
 </pre>
-<div class="variablelist">
+<div class="variablelist" title="where:">
 <p class="title"><b>where:</b></p>
 <dl>
 <dt><span class="term">Iterator&amp; first</span></dt>
@@ -224,10 +215,10 @@
 <dt><span class="term">F f</span></dt>
 <dd><p>
               A function or function object to be called for each matched token.
- This function is expected to have the prototype: <tt class="computeroutput"><span class="keyword">bool</span>
- <span class="identifier">f</span><span class="special">(</span><span class="identifier">Lexer</span><span class="special">::</span><span class="identifier">token_type</span><span class="special">);</span></tt>
- and should return <tt class="computeroutput"><span class="keyword">false</span></tt>
- if the supplied token instance is invald (the <tt class="computeroutput"><span class="identifier">tokenize</span><span class="special">()</span></tt> function will return immediatly).
+ This function is expected to have the prototype: <code class="computeroutput"><span class="keyword">bool</span>
+ <span class="identifier">f</span><span class="special">(</span><span class="identifier">Lexer</span><span class="special">::</span><span class="identifier">token_type</span><span class="special">);</span></code>
+ and should return <code class="computeroutput"><span class="keyword">false</span></code>
+ if the supplied token instance is invald (the <code class="computeroutput"><span class="identifier">tokenize</span><span class="special">()</span></code> function will return immediatly).
             </p></dd>
 <dt><span class="term">Lexer::char_type const* initial_state</span></dt>
 <dd><p>
@@ -236,11 +227,11 @@
             </p></dd>
 </dl>
 </div>
-<a name="spirit.lex.abstracts.lexer_tokenizing.the_generate_static_function"></a><h5>
-<a name="id498391"></a>
- <a href="lexer_tokenizing.html#spirit.lex.abstracts.lexer_tokenizing.the_generate_static_function">The
+<a name="spirit.lex.abstracts.lexer_tokenizing.the_generate_static_function"></a><h6>
+<a name="id1110891"></a>
+ <a class="link" href="lexer_tokenizing.html#spirit.lex.abstracts.lexer_tokenizing.the_generate_static_function">The
           generate_static function</a>
- </h5>
+ </h6>
 </div>
 <table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
 <td align="left"></td>

Modified: trunk/libs/spirit/doc/html/spirit/lex/lexer_introduction.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/lex/lexer_introduction.html (original)
+++ trunk/libs/spirit/doc/html/spirit/lex/lexer_introduction.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -1,14 +1,13 @@
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title> Introduction to Spirit.Lex</title>
+<title>Introduction to Spirit.Lex</title>
 <link rel="stylesheet" href="../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../index.html" title="Spirit 2.1">
-<link rel="up" href="../lex.html" title=" Spirit.Lex">
-<link rel="previous" href="../lex.html" title=" Spirit.Lex">
-<link rel="next" href="tutorials.html" title=" Spirit.Lex
- Tutorials">
+<link rel="up" href="../lex.html" title="Spirit.Lex">
+<link rel="prev" href="../lex.html" title="Spirit.Lex">
+<link rel="next" href="tutorials.html" title="Spirit.Lex Tutorials">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
 <table cellpadding="2" width="100%"><tr>
@@ -23,13 +22,10 @@
 <div class="spirit-nav">
 <a accesskey="p" href="../lex.html"><img src="../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../lex.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="tutorials.html"><img src="../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h3 class="title">
-<a name="spirit.lex.lexer_introduction"></a> Introduction to Spirit.Lex
-</h3></div></div>
-<div></div>
-</div>
+<div class="section" title="Introduction to Spirit.Lex">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="spirit.lex.lexer_introduction"></a><a class="link" href="lexer_introduction.html" title="Introduction to Spirit.Lex"> Introduction to <span class="emphasis"><em>Spirit.Lex</em></span></a>
+</h3></div></div></div>
 <p>
         Lexical scanning is the process of analyzing the stream of input characters
         and separating it into strings called tokens, separated by whitespace. Most
@@ -41,29 +37,29 @@
         set of patterns describing the different tokens you want to recognize in
         the input. To make this a bit more formal, here are some definitions:
       </p>
-<div class="itemizedlist"><ul type="disc">
-<li>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem">
           A token is a sequence of consecutive characters having a collective meaning.
           Tokens may have attributes specific to the token type, carrying additional
           information about the matched character sequence.
         </li>
-<li>
+<li class="listitem">
           A pattern is a rule expressed as a regular expression and describing how
- a particular token can be formed. For example, <tt class="literal">[A-Za-z][A-Za-z_0-9]*</tt>
+ a particular token can be formed. For example, <code class="literal">[A-Za-z][A-Za-z_0-9]*</code>
           is a pattern for a rule matching C++ identifiers.
         </li>
-<li>
+<li class="listitem">
           Characters between tokens are called whitespace; these include spaces,
           tabs, newlines, and formfeeds. Many people also count comments as whitespace,
           though since some tools such as lint look at comments, this conflation
           is not perfect.
         </li>
 </ul></div>
-<a name="spirit.lex.lexer_introduction.why_use_a_separate_lexer_"></a><h4>
-<a name="id481242"></a>
- <a href="lexer_introduction.html#spirit.lex.lexer_introduction.why_use_a_separate_lexer_">Why
+<a name="spirit.lex.lexer_introduction.why_use_a_separate_lexer_"></a><h5>
+<a name="id1091476"></a>
+ <a class="link" href="lexer_introduction.html#spirit.lex.lexer_introduction.why_use_a_separate_lexer_">Why
         Use a Separate Lexer?</a>
- </h4>
+ </h5>
 <p>
         Typically, lexical scanning is done in a separate module from the parser,
         feeding the parser with a stream of input tokens only. Theoretically it is
@@ -79,17 +75,17 @@
         to be very useful in practical applications. In 1956, Noam Chomsky defined
         the "Chomsky Hierarchy" of grammars:
       </p>
-<div class="itemizedlist"><ul type="disc">
-<li>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem">
           Type 0: Unrestricted grammars (e.g., natural languages)
         </li>
-<li>
+<li class="listitem">
           Type 1: Context-Sensitive grammars
         </li>
-<li>
+<li class="listitem">
           Type 2: Context-Free grammars
         </li>
-<li>
+<li class="listitem">
           Type 3: Regular grammars
         </li>
 </ul></div>
@@ -158,11 +154,11 @@
         it is even possible to use the provided functionality to build more complex
         grammar recognizers.
       </p>
-<a name="spirit.lex.lexer_introduction.advantages_of_using__emphasis_spirit_lex__emphasis_"></a><h4>
-<a name="id481591"></a>
- <a href="lexer_introduction.html#spirit.lex.lexer_introduction.advantages_of_using__emphasis_spirit_lex__emphasis_">Advantages
+<a name="spirit.lex.lexer_introduction.advantages_of_using__emphasis_spirit_lex__emphasis_"></a><h5>
+<a name="id1091685"></a>
+ <a class="link" href="lexer_introduction.html#spirit.lex.lexer_introduction.advantages_of_using__emphasis_spirit_lex__emphasis_">Advantages
         of using <span class="emphasis"><em>Spirit.Lex</em></span></a>
- </h4>
+ </h5>
 <p>
         The advantage of using <span class="emphasis"><em>Spirit.Lex</em></span> to create the lexical
         analyzer over using more traditional tools such as Flex
@@ -175,18 +171,18 @@
         gives you the vast majority of features you could get from a similar Flex program without the need
         to leave C++ as a host language:
       </p>
-<div class="itemizedlist"><ul type="disc">
-<li>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem">
           The definition of tokens is done using regular expressions (patterns)
         </li>
-<li>
+<li class="listitem">
           The token definitions can refer to special substitution strings (pattern
           macros) simplifying pattern definitions
         </li>
-<li>
+<li class="listitem">
           The generated lexical scanner may have multiple start states
         </li>
-<li>
+<li class="listitem">
           It is possible to attach code to any of the token definitions; this code
           gets executed whenever the corresponding token pattern has been matched
         </li>
@@ -195,8 +191,7 @@
         Even if it is possible to use <span class="emphasis"><em>Spirit.Lex</em></span> to generate
         C++ code representing the lexical analyzer (we will refer to that as the
         <span class="emphasis"><em>static</em></span> model, described in more detail in the section
- <a href="abstracts/lexer_static_model.html" title=" The Static
- Lexer Model">The <span class="emphasis"><em>Static</em></span>
+ <a class="link" href="abstracts/lexer_static_model.html" title="The Static Lexer Model">The <span class="emphasis"><em>Static</em></span>
         Model</a>) - a model very similar to the way Flex
         operates - we will mainly focus on the opposite, the <span class="emphasis"><em>dynamic</em></span>
         model. You can directly integrate the token definitions into your C++ program,
@@ -207,14 +202,13 @@
         But it is very flexible and allows you to speed up the development of your
         application.
       </p>
-<a name="spirit.lex.lexer_introduction.the_library_structure_of__emphasis_spirit_lex__emphasis_"></a><h4>
-<a name="id481762"></a>
- <a href="lexer_introduction.html#spirit.lex.lexer_introduction.the_library_structure_of__emphasis_spirit_lex__emphasis_">The
+<a name="spirit.lex.lexer_introduction.the_library_structure_of__emphasis_spirit_lex__emphasis_"></a><h5>
+<a name="id1093792"></a>
+ <a class="link" href="lexer_introduction.html#spirit.lex.lexer_introduction.the_library_structure_of__emphasis_spirit_lex__emphasis_">The
         Library Structure of <span class="emphasis"><em>Spirit.Lex</em></span></a>
- </h4>
+ </h5>
 <p>
- The <a href="lexer_introduction.html#spirit.lexerflow" title="Figure 3. The Library structure and Common Flow of Information while
- using Spirit.Lex in an application">figure</a> below shows a high level
+ The <a class="link" href="lexer_introduction.html#spirit.lexerflow" title="Figure 3. The Library structure and Common Flow of Information while using Spirit.Lex in an application">figure</a> below shows a high level
         overview of how the <span class="emphasis"><em>Spirit.Lex</em></span> library might be used
         in an application. <span class="emphasis"><em>Spirit.Lex</em></span> allows to create lexical
         analyzers based on patterns. These patterns are regular expression based
@@ -232,11 +226,9 @@
 <div class="figure">
 <a name="spirit.lexerflow"></a><p class="title"><b>Figure 3. The Library structure and Common Flow of Information while
         using <span class="emphasis"><em>Spirit.Lex</em></span> in an application</b></p>
-<span class="inlinemediaobject"><img src="./images/lexerflow.png" alt="The
- Library structure and Common Flow of Information while using Spirit.Lex
- in an application"></span>
+<div class="figure-contents"><span class="inlinemediaobject"><img src="../.././images/lexerflow.png" alt="The Library structure and Common Flow of Information while using Spirit.Lex in an application"></span></div>
 </div>
-<p>
+<p><br class="figure-break">
       </p>
 </div>
 <table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>

Modified: trunk/libs/spirit/doc/html/spirit/lex/quick_reference.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/lex/quick_reference.html (original)
+++ trunk/libs/spirit/doc/html/spirit/lex/quick_reference.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -1,13 +1,13 @@
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title> Quick Reference</title>
+<title>Quick Reference</title>
 <link rel="stylesheet" href="../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../index.html" title="Spirit 2.1">
-<link rel="up" href="../lex.html" title=" Spirit.Lex">
-<link rel="previous" href="abstracts/lexer_states.html" title=" Lexer States">
-<link rel="next" href="reference.html" title=" Reference">
+<link rel="up" href="../lex.html" title="Spirit.Lex">
+<link rel="prev" href="abstracts/lexer_states.html" title="Lexer States">
+<link rel="next" href="reference.html" title="Reference">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
 <table cellpadding="2" width="100%"><tr>
@@ -22,12 +22,9 @@
 <div class="spirit-nav">
 <a accesskey="p" href="abstracts/lexer_states.html"><img src="../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../lex.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="reference.html"><img src="../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en"><div class="titlepage">
-<div><div><h3 class="title">
-<a name="spirit.lex.quick_reference"></a> Quick Reference
-</h3></div></div>
-<div></div>
-</div></div>
+<div class="section" title="Quick Reference"><div class="titlepage"><div><div><h3 class="title">
+<a name="spirit.lex.quick_reference"></a><a class="link" href="quick_reference.html" title="Quick Reference"> Quick Reference</a>
+</h3></div></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 © 2001-2009 Joel

Modified: trunk/libs/spirit/doc/html/spirit/lex/reference.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/lex/reference.html (original)
+++ trunk/libs/spirit/doc/html/spirit/lex/reference.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -1,13 +1,13 @@
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title> Reference</title>
+<title>Reference</title>
 <link rel="stylesheet" href="../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../index.html" title="Spirit 2.1">
-<link rel="up" href="../lex.html" title=" Spirit.Lex">
-<link rel="previous" href="quick_reference.html" title=" Quick Reference">
-<link rel="next" href="reference/concepts.html" title=" Concepts">
+<link rel="up" href="../lex.html" title="Spirit.Lex">
+<link rel="prev" href="quick_reference.html" title="Quick Reference">
+<link rel="next" href="reference/concepts.html" title="Concepts">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
 <table cellpadding="2" width="100%"><tr>
@@ -22,13 +22,10 @@
 <div class="spirit-nav">
 <a accesskey="p" href="quick_reference.html"><img src="../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../lex.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="reference/concepts.html"><img src="../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h3 class="title">
-<a name="spirit.lex.reference"></a> Reference
-</h3></div></div>
-<div></div>
-</div>
+<div class="section" title="Reference">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="spirit.lex.reference"></a><a class="link" href="reference.html" title="Reference"> Reference</a>
+</h3></div></div></div>
 <div class="toc"><dl>
 <dt><span class="section"> Concepts</span></dt>
 <dt><span class="section">Lexer Class</span></dt>

Modified: trunk/libs/spirit/doc/html/spirit/lex/reference/concepts.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/lex/reference/concepts.html (original)
+++ trunk/libs/spirit/doc/html/spirit/lex/reference/concepts.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -1,12 +1,12 @@
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title> Concepts</title>
+<title>Concepts</title>
 <link rel="stylesheet" href="../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../index.html" title="Spirit 2.1">
-<link rel="up" href="../reference.html" title=" Reference">
-<link rel="previous" href="../reference.html" title=" Reference">
+<link rel="up" href="../reference.html" title="Reference">
+<link rel="prev" href="../reference.html" title="Reference">
 <link rel="next" href="concepts/lexer.html" title="Lexer">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -22,13 +22,10 @@
 <div class="spirit-nav">
 <a accesskey="p" href="../reference.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../reference.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="concepts/lexer.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h4 class="title">
-<a name="spirit.lex.reference.concepts"></a> Concepts
-</h4></div></div>
-<div></div>
-</div>
+<div class="section" title="Concepts">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="spirit.lex.reference.concepts"></a><a class="link" href="concepts.html" title="Concepts"> Concepts</a>
+</h4></div></div></div>
 <div class="toc"><dl>
 <dt><span class="section">Lexer</span></dt>
 <dt><span class="section">Token</span></dt>

Modified: trunk/libs/spirit/doc/html/spirit/lex/reference/concepts/lexer.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/lex/reference/concepts/lexer.html (original)
+++ trunk/libs/spirit/doc/html/spirit/lex/reference/concepts/lexer.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -3,10 +3,10 @@
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <title>Lexer</title>
 <link rel="stylesheet" href="../../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../../index.html" title="Spirit 2.1">
-<link rel="up" href="../concepts.html" title=" Concepts">
-<link rel="previous" href="../concepts.html" title=" Concepts">
+<link rel="up" href="../concepts.html" title="Concepts">
+<link rel="prev" href="../concepts.html" title="Concepts">
 <link rel="next" href="token.html" title="Token">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -22,375 +22,516 @@
 <div class="spirit-nav">
 <a accesskey="p" href="../concepts.html"><img src="../../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../concepts.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="token.html"><img src="../../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h5 class="title">
-<a name="spirit.lex.reference.concepts.lexer"></a>Lexer
-</h5></div></div>
-<div></div>
-</div>
+<div class="section" title="Lexer">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="spirit.lex.reference.concepts.lexer"></a><a class="link" href="lexer.html" title="Lexer">Lexer</a>
+</h5></div></div></div>
 <div class="table">
-<a name="id504537"></a><p class="title"><b>Table 9. Regular expressions support</b></p>
-<table class="table" summary="Regular expressions support">
+<a name="id1115563"></a><p class="title"><b>Table 9. Regular expressions support</b></p>
+<div class="table-contents"><table class="table" summary="Regular expressions support">
 <colgroup>
 <col>
 <col>
 </colgroup>
 <thead><tr>
-<th><p>
+<th>
+ <p>
                   Expression
- </p></th>
-<th><p>
+ </p>
+ </th>
+<th>
+ <p>
                   Meaning
- </p></th>
+ </p>
+ </th>
 </tr></thead>
 <tbody>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">x</span></tt>
- </p></td>
-<td><p>
- Match any character <tt class="computeroutput"><span class="identifier">x</span></tt>
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="special">.</span></tt>
- </p></td>
-<td><p>
- Match any except newline (or optionally <span class="bold"><b>any</b></span>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">x</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Match any character <code class="computeroutput"><span class="identifier">x</span></code>
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="special">.</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Match any except newline (or optionally <span class="bold"><strong>any</strong></span>
                   character)
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="special">[</span><span class="identifier">xyz</span><span class="special">]</span></tt>
- </p></td>
-<td><p>
- A character class; in this case matches <tt class="computeroutput"><span class="identifier">x</span></tt>,
- <tt class="computeroutput"><span class="identifier">y</span></tt> or <tt class="computeroutput"><span class="identifier">z</span></tt>
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="special">[</span><span class="identifier">abj</span><span class="special">-</span><span class="identifier">oZ</span><span class="special">]</span></tt>
- </p></td>
-<td><p>
- A character class with a range in it; matches <tt class="computeroutput"><span class="identifier">a</span></tt>,
- <tt class="computeroutput"><span class="identifier">b</span></tt> any letter from
- <tt class="computeroutput"><span class="identifier">j</span></tt> through <tt class="computeroutput"><span class="identifier">o</span></tt> or a <tt class="computeroutput"><span class="identifier">Z</span></tt>
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="special">[^</span><span class="identifier">A</span><span class="special">-</span><span class="identifier">Z</span><span class="special">]</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="special">[</span><span class="identifier">xyz</span><span class="special">]</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ A character class; in this case matches <code class="computeroutput"><span class="identifier">x</span></code>,
+ <code class="computeroutput"><span class="identifier">y</span></code> or <code class="computeroutput"><span class="identifier">z</span></code>
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="special">[</span><span class="identifier">abj</span><span class="special">-</span><span class="identifier">oZ</span><span class="special">]</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ A character class with a range in it; matches <code class="computeroutput"><span class="identifier">a</span></code>,
+ <code class="computeroutput"><span class="identifier">b</span></code> any letter from
+ <code class="computeroutput"><span class="identifier">j</span></code> through <code class="computeroutput"><span class="identifier">o</span></code> or a <code class="computeroutput"><span class="identifier">Z</span></code>
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="special">[^</span><span class="identifier">A</span><span class="special">-</span><span class="identifier">Z</span><span class="special">]</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   A negated character class i.e. any character but those in the class.
                   In this case, any character except an uppercase letter
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">r</span><span class="special">*</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">r</span><span class="special">*</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   Zero or more r's (greedy), where r is any regular expression
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">r</span><span class="special">*?</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">r</span><span class="special">*?</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   Zero or more r's (abstemious), where r is any regular expression
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">r</span><span class="special">+</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">r</span><span class="special">+</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   One or more r's (greedy)
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">r</span><span class="special">+?</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">r</span><span class="special">+?</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   One or more r's (abstemious)
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">r</span><span class="special">?</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">r</span><span class="special">?</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   Zero or one r's (greedy), i.e. optional
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">r</span><span class="special">??</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">r</span><span class="special">??</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   Zero or one r's (abstemious), i.e. optional
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">r</span><span class="special">{</span><span class="number">2</span><span class="special">,</span><span class="number">5</span><span class="special">}</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">r</span><span class="special">{</span><span class="number">2</span><span class="special">,</span><span class="number">5</span><span class="special">}</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   Anywhere between two and five r's (greedy)
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">r</span><span class="special">{</span><span class="number">2</span><span class="special">,</span><span class="number">5</span><span class="special">}?</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">r</span><span class="special">{</span><span class="number">2</span><span class="special">,</span><span class="number">5</span><span class="special">}?</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   Anywhere between two and five r's (abstemious)
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">r</span><span class="special">{</span><span class="number">2</span><span class="special">,}</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">r</span><span class="special">{</span><span class="number">2</span><span class="special">,}</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   Two or more r's (greedy)
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">r</span><span class="special">{</span><span class="number">2</span><span class="special">,}?</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">r</span><span class="special">{</span><span class="number">2</span><span class="special">,}?</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   Two or more r's (abstemious)
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">r</span><span class="special">{</span><span class="number">4</span><span class="special">}</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">r</span><span class="special">{</span><span class="number">4</span><span class="special">}</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   Exactly four r's
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="special">{</span><span class="identifier">NAME</span><span class="special">}</span></tt>
- </p></td>
-<td><p>
- The macro <tt class="computeroutput"><span class="identifier">NAME</span></tt>
+<td>
+ <p>
+ <code class="computeroutput"><span class="special">{</span><span class="identifier">NAME</span><span class="special">}</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ The macro <code class="computeroutput"><span class="identifier">NAME</span></code>
                   (see below)
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="string">"[xyz]\"foo"</span></tt>
- </p></td>
-<td><p>
- The literal string <tt class="computeroutput"><span class="special">[</span><span class="identifier">xyz</span><span class="special">]\</span><span class="error">"</span><span class="identifier">foo</span></tt>
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="special">\</span><span class="identifier">X</span></tt>
- </p></td>
-<td><p>
- If X is <tt class="computeroutput"><span class="identifier">a</span></tt>, <tt class="computeroutput"><span class="identifier">b</span></tt>, <tt class="computeroutput"><span class="identifier">e</span></tt>,
- <tt class="computeroutput"><span class="identifier">n</span></tt>, <tt class="computeroutput"><span class="identifier">r</span></tt>, <tt class="computeroutput"><span class="identifier">f</span></tt>,
- <tt class="computeroutput"><span class="identifier">t</span></tt>, <tt class="computeroutput"><span class="identifier">v</span></tt> then the ANSI-C interpretation
- of <tt class="computeroutput"><span class="special">\</span><span class="identifier">x</span></tt>.
- Otherwise a literal <tt class="computeroutput"><span class="identifier">X</span></tt>
- (used to escape operators such as <tt class="computeroutput"><span class="special">*</span></tt>)
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="special">\</span><span class="number">0</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="string">"[xyz]\"foo"</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ The literal string <code class="computeroutput"><span class="special">[</span><span class="identifier">xyz</span><span class="special">]\</span><span class="error">"</span><span class="identifier">foo</span></code>
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="special">\</span><span class="identifier">X</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ If X is <code class="computeroutput"><span class="identifier">a</span></code>, <code class="computeroutput"><span class="identifier">b</span></code>, <code class="computeroutput"><span class="identifier">e</span></code>,
+ <code class="computeroutput"><span class="identifier">n</span></code>, <code class="computeroutput"><span class="identifier">r</span></code>, <code class="computeroutput"><span class="identifier">f</span></code>,
+ <code class="computeroutput"><span class="identifier">t</span></code>, <code class="computeroutput"><span class="identifier">v</span></code> then the ANSI-C interpretation
+ of <code class="computeroutput"><span class="special">\</span><span class="identifier">x</span></code>.
+ Otherwise a literal <code class="computeroutput"><span class="identifier">X</span></code>
+ (used to escape operators such as <code class="computeroutput"><span class="special">*</span></code>)
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="special">\</span><span class="number">0</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   A NUL character (ASCII code 0)
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="special">\</span><span class="number">123</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="special">\</span><span class="number">123</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   The character with octal value 123
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="special">\</span><span class="identifier">x2a</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="special">\</span><span class="identifier">x2a</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   The character with hexadecimal value 2a
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="special">\</span><span class="identifier">cX</span></tt>
- </p></td>
-<td><p>
- A named control character <tt class="computeroutput"><span class="identifier">X</span></tt>.
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="special">\</span><span class="identifier">d</span></tt>
- </p></td>
-<td><p>
- A shortcut for <tt class="computeroutput"><span class="special">[</span><span class="number">0</span><span class="special">-</span><span class="number">9</span><span class="special">]</span></tt>
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="special">\</span><span class="identifier">D</span></tt>
- </p></td>
-<td><p>
- A shortcut for <tt class="computeroutput"><span class="special">[^</span><span class="number">0</span><span class="special">-</span><span class="number">9</span><span class="special">]</span></tt>
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="special">\</span><span class="identifier">s</span></tt>
- </p></td>
-<td><p>
- A shortcut for <tt class="computeroutput"><span class="special">[\</span><span class="identifier">x20</span><span class="special">\</span><span class="identifier">t</span><span class="special">\</span><span class="identifier">n</span><span class="special">\</span><span class="identifier">r</span><span class="special">\</span><span class="identifier">f</span><span class="special">\</span><span class="identifier">v</span><span class="special">]</span></tt>
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="special">\</span><span class="identifier">S</span></tt>
- </p></td>
-<td><p>
- A shortcut for <tt class="computeroutput"><span class="special">[^\</span><span class="identifier">x20</span><span class="special">\</span><span class="identifier">t</span><span class="special">\</span><span class="identifier">n</span><span class="special">\</span><span class="identifier">r</span><span class="special">\</span><span class="identifier">f</span><span class="special">\</span><span class="identifier">v</span><span class="special">]</span></tt>
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="special">\</span><span class="identifier">w</span></tt>
- </p></td>
-<td><p>
- A shortcut for <tt class="computeroutput"><span class="special">[</span><span class="identifier">a</span><span class="special">-</span><span class="identifier">zA</span><span class="special">-</span><span class="identifier">Z0</span><span class="special">-</span><span class="number">9</span><span class="identifier">_</span><span class="special">]</span></tt>
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="special">\</span><span class="identifier">W</span></tt>
- </p></td>
-<td><p>
- A shortcut for <tt class="computeroutput"><span class="special">[^</span><span class="identifier">a</span><span class="special">-</span><span class="identifier">zA</span><span class="special">-</span><span class="identifier">Z0</span><span class="special">-</span><span class="number">9</span><span class="identifier">_</span><span class="special">]</span></tt>
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="special">(</span><span class="identifier">r</span><span class="special">)</span></tt>
- </p></td>
-<td><p>
- Match an <tt class="computeroutput"><span class="identifier">r</span></tt>; parenthesis
+<td>
+ <p>
+ <code class="computeroutput"><span class="special">\</span><span class="identifier">cX</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ A named control character <code class="computeroutput"><span class="identifier">X</span></code>.
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="special">\</span><span class="identifier">d</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ A shortcut for <code class="computeroutput"><span class="special">[</span><span class="number">0</span><span class="special">-</span><span class="number">9</span><span class="special">]</span></code>
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="special">\</span><span class="identifier">D</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ A shortcut for <code class="computeroutput"><span class="special">[^</span><span class="number">0</span><span class="special">-</span><span class="number">9</span><span class="special">]</span></code>
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="special">\</span><span class="identifier">s</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ A shortcut for <code class="computeroutput"><span class="special">[\</span><span class="identifier">x20</span><span class="special">\</span><span class="identifier">t</span><span class="special">\</span><span class="identifier">n</span><span class="special">\</span><span class="identifier">r</span><span class="special">\</span><span class="identifier">f</span><span class="special">\</span><span class="identifier">v</span><span class="special">]</span></code>
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="special">\</span><span class="identifier">S</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ A shortcut for <code class="computeroutput"><span class="special">[^\</span><span class="identifier">x20</span><span class="special">\</span><span class="identifier">t</span><span class="special">\</span><span class="identifier">n</span><span class="special">\</span><span class="identifier">r</span><span class="special">\</span><span class="identifier">f</span><span class="special">\</span><span class="identifier">v</span><span class="special">]</span></code>
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="special">\</span><span class="identifier">w</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ A shortcut for <code class="computeroutput"><span class="special">[</span><span class="identifier">a</span><span class="special">-</span><span class="identifier">zA</span><span class="special">-</span><span class="identifier">Z0</span><span class="special">-</span><span class="number">9</span><span class="identifier">_</span><span class="special">]</span></code>
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="special">\</span><span class="identifier">W</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ A shortcut for <code class="computeroutput"><span class="special">[^</span><span class="identifier">a</span><span class="special">-</span><span class="identifier">zA</span><span class="special">-</span><span class="identifier">Z0</span><span class="special">-</span><span class="number">9</span><span class="identifier">_</span><span class="special">]</span></code>
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="special">(</span><span class="identifier">r</span><span class="special">)</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Match an <code class="computeroutput"><span class="identifier">r</span></code>; parenthesis
                   are used to override precedence (see below)
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="special">(?</span><span class="identifier">r</span><span class="special">-</span><span class="identifier">s</span><span class="special">:</span><span class="identifier">pattern</span><span class="special">)</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="special">(?</span><span class="identifier">r</span><span class="special">-</span><span class="identifier">s</span><span class="special">:</span><span class="identifier">pattern</span><span class="special">)</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   apply option 'r' and omit option 's' while interpreting pattern.
                   Options may be zero or more of the characters 'i' or 's'. 'i' means
                   case-insensitive. '-i' means case-sensitive. 's' alters the meaning
                   of the '.' syntax to match any single character whatsoever. '-s'
- alters the meaning of '.' to match any character except '<tt class="computeroutput"><span class="special">\</span><span class="identifier">n</span></tt>'.
- </p></td>
+ alters the meaning of '.' to match any character except '<code class="computeroutput"><span class="special">\</span><span class="identifier">n</span></code>'.
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">rs</span></tt>
- </p></td>
-<td><p>
- The regular expression <tt class="computeroutput"><span class="identifier">r</span></tt>
- followed by the regular expression <tt class="computeroutput"><span class="identifier">s</span></tt>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">rs</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ The regular expression <code class="computeroutput"><span class="identifier">r</span></code>
+ followed by the regular expression <code class="computeroutput"><span class="identifier">s</span></code>
                   (a sequence)
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">r</span><span class="special">|</span><span class="identifier">s</span></tt>
- </p></td>
-<td><p>
- Either an <tt class="computeroutput"><span class="identifier">r</span></tt> or
- and <tt class="computeroutput"><span class="identifier">s</span></tt>
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="special">^</span><span class="identifier">r</span></tt>
- </p></td>
-<td><p>
- An <tt class="computeroutput"><span class="identifier">r</span></tt> but only at
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">r</span><span class="special">|</span><span class="identifier">s</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Either an <code class="computeroutput"><span class="identifier">r</span></code> or
+ and <code class="computeroutput"><span class="identifier">s</span></code>
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="special">^</span><span class="identifier">r</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ An <code class="computeroutput"><span class="identifier">r</span></code> but only at
                   the beginning of a line (i.e. when just starting to scan, or right
                   after a newline has been scanned)
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">r</span></tt>$
- </p></td>
-<td><p>
- An <tt class="computeroutput"><span class="identifier">r</span></tt> but only at
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">r</span></code>$
+ </p>
+ </td>
+<td>
+ <p>
+ An <code class="computeroutput"><span class="identifier">r</span></code> but only at
                   the end of a line (i.e. just before a newline)
- </p></td>
+ </p>
+ </td>
 </tr>
 </tbody>
-</table>
+</table></div>
 </div>
-<div class="note"><table border="0" summary="Note">
+<br class="table-break"><div class="note" title="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>
 </tr>
-<tr><td colspan="2" align="left" valign="top"><p>
+<tr><td align="left" valign="top"><p>
               POSIX character classes are not currently supported, due to performance
               issues when creating them in wide character mode.
             </p></td></tr>
 </table></div>
 <a name="spirit.lex.reference.concepts.lexer.regular_expression_precedence"></a><h6>
-<a name="id506627"></a>
- <a href="lexer.html#spirit.lex.reference.concepts.lexer.regular_expression_precedence">Regular
+<a name="id1118787"></a>
+ <a class="link" href="lexer.html#spirit.lex.reference.concepts.lexer.regular_expression_precedence">Regular
             Expression Precedence</a>
           </h6>
-<div class="itemizedlist"><ul type="disc">
-<li>
-<tt class="computeroutput"><span class="identifier">rs</span></tt> has highest precedence
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem">
+<code class="computeroutput"><span class="identifier">rs</span></code> has highest precedence
             </li>
-<li>
-<tt class="computeroutput"><span class="identifier">r</span><span class="special">*</span></tt>
- has next highest (<tt class="computeroutput"><span class="special">+</span></tt>,
- <tt class="computeroutput"><span class="special">?</span></tt>, <tt class="computeroutput"><span class="special">{</span><span class="identifier">n</span><span class="special">,</span><span class="identifier">m</span><span class="special">}</span></tt>
- have the same precedence as <tt class="computeroutput"><span class="special">*</span></tt>)
+<li class="listitem">
+<code class="computeroutput"><span class="identifier">r</span><span class="special">*</span></code>
+ has next highest (<code class="computeroutput"><span class="special">+</span></code>,
+ <code class="computeroutput"><span class="special">?</span></code>, <code class="computeroutput"><span class="special">{</span><span class="identifier">n</span><span class="special">,</span><span class="identifier">m</span><span class="special">}</span></code>
+ have the same precedence as <code class="computeroutput"><span class="special">*</span></code>)
             </li>
-<li>
-<tt class="computeroutput"><span class="identifier">r</span><span class="special">|</span><span class="identifier">s</span></tt> has the lowest precedence
+<li class="listitem">
+<code class="computeroutput"><span class="identifier">r</span><span class="special">|</span><span class="identifier">s</span></code> has the lowest precedence
             </li>
 </ul></div>
 <a name="spirit.lex.reference.concepts.lexer.macros"></a><h6>
-<a name="id506784"></a>
- Macros
+<a name="id1118891"></a>
+ <a class="link" href="lexer.html#spirit.lex.reference.concepts.lexer.macros">Macros</a>
           </h6>
 <p>
             Regular expressions can be given a name and referred to in rules using
- the syntax <tt class="computeroutput"><span class="special">{</span><span class="identifier">NAME</span><span class="special">}</span></tt> where <tt class="computeroutput"><span class="identifier">NAME</span></tt>
+ the syntax <code class="computeroutput"><span class="special">{</span><span class="identifier">NAME</span><span class="special">}</span></code> where <code class="computeroutput"><span class="identifier">NAME</span></code>
             is the name you have given to the macro. A macro name can be at most
- 30 characters long and must start with a <tt class="computeroutput"><span class="identifier">_</span></tt>
- or a letter. Subsequent characters can be <tt class="computeroutput"><span class="identifier">_</span></tt>,
- <tt class="computeroutput"><span class="special">-</span></tt>, a letter or a decimal
- digit. Use the <tt class="computeroutput"><span class="identifier">rules</span><span class="special">::</span><span class="identifier">add_macro</span><span class="special">()</span></tt> method to define a macro.
+ 30 characters long and must start with a <code class="computeroutput"><span class="identifier">_</span></code>
+ or a letter. Subsequent characters can be <code class="computeroutput"><span class="identifier">_</span></code>,
+ <code class="computeroutput"><span class="special">-</span></code>, a letter or a decimal
+ digit. Use the <code class="computeroutput"><span class="identifier">rules</span><span class="special">::</span><span class="identifier">add_macro</span><span class="special">()</span></code> method to define a macro.
           </p>
 </div>
 <table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>

Modified: trunk/libs/spirit/doc/html/spirit/lex/reference/concepts/token.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/lex/reference/concepts/token.html (original)
+++ trunk/libs/spirit/doc/html/spirit/lex/reference/concepts/token.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -3,10 +3,10 @@
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <title>Token</title>
 <link rel="stylesheet" href="../../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../../index.html" title="Spirit 2.1">
-<link rel="up" href="../concepts.html" title=" Concepts">
-<link rel="previous" href="lexer.html" title="Lexer">
+<link rel="up" href="../concepts.html" title="Concepts">
+<link rel="prev" href="lexer.html" title="Lexer">
 <link rel="next" href="tokendef.html" title="TokenDef">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -22,12 +22,9 @@
 <div class="spirit-nav">
 <a accesskey="p" href="lexer.html"><img src="../../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../concepts.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="tokendef.html"><img src="../../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en"><div class="titlepage">
-<div><div><h5 class="title">
-<a name="spirit.lex.reference.concepts.token"></a>Token
-</h5></div></div>
-<div></div>
-</div></div>
+<div class="section" title="Token"><div class="titlepage"><div><div><h5 class="title">
+<a name="spirit.lex.reference.concepts.token"></a><a class="link" href="token.html" title="Token">Token</a>
+</h5></div></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 © 2001-2009 Joel

Modified: trunk/libs/spirit/doc/html/spirit/lex/reference/concepts/tokendef.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/lex/reference/concepts/tokendef.html (original)
+++ trunk/libs/spirit/doc/html/spirit/lex/reference/concepts/tokendef.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -3,10 +3,10 @@
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <title>TokenDef</title>
 <link rel="stylesheet" href="../../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../../index.html" title="Spirit 2.1">
-<link rel="up" href="../concepts.html" title=" Concepts">
-<link rel="previous" href="token.html" title="Token">
+<link rel="up" href="../concepts.html" title="Concepts">
+<link rel="prev" href="token.html" title="Token">
 <link rel="next" href="tokenset.html" title="TokenSet">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -22,12 +22,9 @@
 <div class="spirit-nav">
 <a accesskey="p" href="token.html"><img src="../../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../concepts.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="tokenset.html"><img src="../../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en"><div class="titlepage">
-<div><div><h5 class="title">
-<a name="spirit.lex.reference.concepts.tokendef"></a>TokenDef
-</h5></div></div>
-<div></div>
-</div></div>
+<div class="section" title="TokenDef"><div class="titlepage"><div><div><h5 class="title">
+<a name="spirit.lex.reference.concepts.tokendef"></a><a class="link" href="tokendef.html" title="TokenDef">TokenDef</a>
+</h5></div></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 © 2001-2009 Joel

Modified: trunk/libs/spirit/doc/html/spirit/lex/reference/concepts/tokenset.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/lex/reference/concepts/tokenset.html (original)
+++ trunk/libs/spirit/doc/html/spirit/lex/reference/concepts/tokenset.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -3,10 +3,10 @@
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <title>TokenSet</title>
 <link rel="stylesheet" href="../../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../../index.html" title="Spirit 2.1">
-<link rel="up" href="../concepts.html" title=" Concepts">
-<link rel="previous" href="tokendef.html" title="TokenDef">
+<link rel="up" href="../concepts.html" title="Concepts">
+<link rel="prev" href="tokendef.html" title="TokenDef">
 <link rel="next" href="../lexer_class.html" title="Lexer Class">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -22,12 +22,9 @@
 <div class="spirit-nav">
 <a accesskey="p" href="tokendef.html"><img src="../../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../concepts.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="../lexer_class.html"><img src="../../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en"><div class="titlepage">
-<div><div><h5 class="title">
-<a name="spirit.lex.reference.concepts.tokenset"></a>TokenSet
-</h5></div></div>
-<div></div>
-</div></div>
+<div class="section" title="TokenSet"><div class="titlepage"><div><div><h5 class="title">
+<a name="spirit.lex.reference.concepts.tokenset"></a><a class="link" href="tokenset.html" title="TokenSet">TokenSet</a>
+</h5></div></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 © 2001-2009 Joel

Modified: trunk/libs/spirit/doc/html/spirit/lex/reference/lexer_class.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/lex/reference/lexer_class.html (original)
+++ trunk/libs/spirit/doc/html/spirit/lex/reference/lexer_class.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -3,10 +3,10 @@
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <title>Lexer Class</title>
 <link rel="stylesheet" href="../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../index.html" title="Spirit 2.1">
-<link rel="up" href="../reference.html" title=" Reference">
-<link rel="previous" href="concepts/tokenset.html" title="TokenSet">
+<link rel="up" href="../reference.html" title="Reference">
+<link rel="prev" href="concepts/tokenset.html" title="TokenSet">
 <link rel="next" href="token_class.html" title="Token Class">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -22,33 +22,30 @@
 <div class="spirit-nav">
 <a accesskey="p" href="concepts/tokenset.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../reference.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="token_class.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h4 class="title">
-<a name="spirit.lex.reference.lexer_class"></a>Lexer Class
-</h4></div></div>
-<div></div>
-</div>
-<a name="spirit.lex.reference.lexer_class.the_lexertl_lexer_class_implementing_the_dynamic_model"></a><h5>
-<a name="id506991"></a>
- <a href="lexer_class.html#spirit.lex.reference.lexer_class.the_lexertl_lexer_class_implementing_the_dynamic_model">The
+<div class="section" title="Lexer Class">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="spirit.lex.reference.lexer_class"></a><a class="link" href="lexer_class.html" title="Lexer Class">Lexer Class</a>
+</h4></div></div></div>
+<a name="spirit.lex.reference.lexer_class.the_lexertl_lexer_class_implementing_the_dynamic_model"></a><h6>
+<a name="id1119013"></a>
+ <a class="link" href="lexer_class.html#spirit.lex.reference.lexer_class.the_lexertl_lexer_class_implementing_the_dynamic_model">The
           lexertl_lexer Class Implementing the Dynamic Model</a>
- </h5>
-<a name="spirit.lex.reference.lexer_class.the_lexertl_actor_lexer_class_implementing_the_dynamic_model"></a><h5>
-<a name="id507018"></a>
- <a href="lexer_class.html#spirit.lex.reference.lexer_class.the_lexertl_actor_lexer_class_implementing_the_dynamic_model">The
+ </h6>
+<a name="spirit.lex.reference.lexer_class.the_lexertl_actor_lexer_class_implementing_the_dynamic_model"></a><h6>
+<a name="id1119026"></a>
+ <a class="link" href="lexer_class.html#spirit.lex.reference.lexer_class.the_lexertl_actor_lexer_class_implementing_the_dynamic_model">The
           lexertl_actor_lexer Class Implementing the Dynamic Model</a>
- </h5>
-<a name="spirit.lex.reference.lexer_class.the_lexertl_static_lexer_class_implementing_the_static_model"></a><h5>
-<a name="id507046"></a>
- <a href="lexer_class.html#spirit.lex.reference.lexer_class.the_lexertl_static_lexer_class_implementing_the_static_model">The
+ </h6>
+<a name="spirit.lex.reference.lexer_class.the_lexertl_static_lexer_class_implementing_the_static_model"></a><h6>
+<a name="id1119039"></a>
+ <a class="link" href="lexer_class.html#spirit.lex.reference.lexer_class.the_lexertl_static_lexer_class_implementing_the_static_model">The
           lexertl_static_lexer Class Implementing the Static Model</a>
- </h5>
-<a name="spirit.lex.reference.lexer_class.the_lexertl_static_actor_lexer_class_implementing_the_static_model"></a><h5>
-<a name="id507075"></a>
- <a href="lexer_class.html#spirit.lex.reference.lexer_class.the_lexertl_static_actor_lexer_class_implementing_the_static_model">The
+ </h6>
+<a name="spirit.lex.reference.lexer_class.the_lexertl_static_actor_lexer_class_implementing_the_static_model"></a><h6>
+<a name="id1119053"></a>
+ <a class="link" href="lexer_class.html#spirit.lex.reference.lexer_class.the_lexertl_static_actor_lexer_class_implementing_the_static_model">The
           lexertl_static_actor_lexer Class Implementing the Static Model</a>
- </h5>
+ </h6>
 </div>
 <table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
 <td align="left"></td>

Modified: trunk/libs/spirit/doc/html/spirit/lex/reference/token_class.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/lex/reference/token_class.html (original)
+++ trunk/libs/spirit/doc/html/spirit/lex/reference/token_class.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -3,10 +3,10 @@
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <title>Token Class</title>
 <link rel="stylesheet" href="../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../index.html" title="Spirit 2.1">
-<link rel="up" href="../reference.html" title=" Reference">
-<link rel="previous" href="lexer_class.html" title="Lexer Class">
+<link rel="up" href="../reference.html" title="Reference">
+<link rel="prev" href="lexer_class.html" title="Lexer Class">
 <link rel="next" href="tokendef_class.html" title="TokenDef Class">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -22,12 +22,9 @@
 <div class="spirit-nav">
 <a accesskey="p" href="lexer_class.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../reference.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="tokendef_class.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en"><div class="titlepage">
-<div><div><h4 class="title">
-<a name="spirit.lex.reference.token_class"></a>Token Class
-</h4></div></div>
-<div></div>
-</div></div>
+<div class="section" title="Token Class"><div class="titlepage"><div><div><h4 class="title">
+<a name="spirit.lex.reference.token_class"></a><a class="link" href="token_class.html" title="Token Class">Token Class</a>
+</h4></div></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 © 2001-2009 Joel

Modified: trunk/libs/spirit/doc/html/spirit/lex/reference/tokendef_class.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/lex/reference/tokendef_class.html (original)
+++ trunk/libs/spirit/doc/html/spirit/lex/reference/tokendef_class.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -3,10 +3,10 @@
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <title>TokenDef Class</title>
 <link rel="stylesheet" href="../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../index.html" title="Spirit 2.1">
-<link rel="up" href="../reference.html" title=" Reference">
-<link rel="previous" href="token_class.html" title="Token Class">
+<link rel="up" href="../reference.html" title="Reference">
+<link rel="prev" href="token_class.html" title="Token Class">
 <link rel="next" href="tokenset_class.html" title="TokenSet Class">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -22,12 +22,9 @@
 <div class="spirit-nav">
 <a accesskey="p" href="token_class.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../reference.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="tokenset_class.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en"><div class="titlepage">
-<div><div><h4 class="title">
-<a name="spirit.lex.reference.tokendef_class"></a>TokenDef Class
-</h4></div></div>
-<div></div>
-</div></div>
+<div class="section" title="TokenDef Class"><div class="titlepage"><div><div><h4 class="title">
+<a name="spirit.lex.reference.tokendef_class"></a><a class="link" href="tokendef_class.html" title="TokenDef Class">TokenDef Class</a>
+</h4></div></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 © 2001-2009 Joel

Modified: trunk/libs/spirit/doc/html/spirit/lex/reference/tokenset_class.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/lex/reference/tokenset_class.html (original)
+++ trunk/libs/spirit/doc/html/spirit/lex/reference/tokenset_class.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -3,11 +3,11 @@
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <title>TokenSet Class</title>
 <link rel="stylesheet" href="../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../index.html" title="Spirit 2.1">
-<link rel="up" href="../reference.html" title=" Reference">
-<link rel="previous" href="tokendef_class.html" title="TokenDef Class">
-<link rel="next" href="../../faq.html" title=" Spirit FAQ">
+<link rel="up" href="../reference.html" title="Reference">
+<link rel="prev" href="tokendef_class.html" title="TokenDef Class">
+<link rel="next" href="../../support.html" title="Supporting libraries">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
 <table cellpadding="2" width="100%"><tr>
@@ -20,14 +20,11 @@
 </tr></table>
 <hr>
 <div class="spirit-nav">
-<a accesskey="p" href="tokendef_class.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../reference.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="../../faq.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
+<a accesskey="p" href="tokendef_class.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../reference.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="../../support.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en"><div class="titlepage">
-<div><div><h4 class="title">
-<a name="spirit.lex.reference.tokenset_class"></a>TokenSet Class
-</h4></div></div>
-<div></div>
-</div></div>
+<div class="section" title="TokenSet Class"><div class="titlepage"><div><div><h4 class="title">
+<a name="spirit.lex.reference.tokenset_class"></a><a class="link" href="tokenset_class.html" title="TokenSet Class">TokenSet Class</a>
+</h4></div></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 © 2001-2009 Joel
@@ -39,7 +36,7 @@
 </tr></table>
 <hr>
 <div class="spirit-nav">
-<a accesskey="p" href="tokendef_class.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../reference.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="../../faq.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
+<a accesskey="p" href="tokendef_class.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../reference.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="../../support.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
 </body>
 </html>

Modified: trunk/libs/spirit/doc/html/spirit/lex/tutorials.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/lex/tutorials.html (original)
+++ trunk/libs/spirit/doc/html/spirit/lex/tutorials.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -1,15 +1,13 @@
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title> Spirit.Lex
- Tutorials</title>
+<title>Spirit.Lex Tutorials</title>
 <link rel="stylesheet" href="../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../index.html" title="Spirit 2.1">
-<link rel="up" href="../lex.html" title=" Spirit.Lex">
-<link rel="previous" href="lexer_introduction.html" title=" Introduction to Spirit.Lex">
-<link rel="next" href="tutorials/lexer_tutorials.html" title=" Spirit.Lex
- Tutorials Overview">
+<link rel="up" href="../lex.html" title="Spirit.Lex">
+<link rel="prev" href="lexer_introduction.html" title="Introduction to Spirit.Lex">
+<link rel="next" href="tutorials/lexer_tutorials.html" title="Spirit.Lex Tutorials Overview">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
 <table cellpadding="2" width="100%"><tr>
@@ -24,15 +22,11 @@
 <div class="spirit-nav">
 <a accesskey="p" href="lexer_introduction.html"><img src="../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../lex.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="tutorials/lexer_tutorials.html"><img src="../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h3 class="title">
-<a name="spirit.lex.tutorials"></a><a href="tutorials.html" title=" Spirit.Lex
- Tutorials"> <span class="emphasis"><em>Spirit.Lex</em></span>
+<div class="section" title="Spirit.Lex Tutorials">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="spirit.lex.tutorials"></a><a class="link" href="tutorials.html" title="Spirit.Lex Tutorials"> <span class="emphasis"><em>Spirit.Lex</em></span>
       Tutorials</a>
-</h3></div></div>
-<div></div>
-</div>
+</h3></div></div></div>
 <div class="toc"><dl>
 <dt><span class="section"><a href="tutorials/lexer_tutorials.html"> <span class="emphasis"><em>Spirit.Lex</em></span>
         Tutorials Overview</a></span></dt>

Modified: trunk/libs/spirit/doc/html/spirit/lex/tutorials/lexer_quickstart1.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/lex/tutorials/lexer_quickstart1.html (original)
+++ trunk/libs/spirit/doc/html/spirit/lex/tutorials/lexer_quickstart1.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -1,17 +1,13 @@
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title> Quickstart
- 1 - A word counter using Spirit.Lex</title>
+<title>Quickstart 1 - A word counter using Spirit.Lex</title>
 <link rel="stylesheet" href="../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../index.html" title="Spirit 2.1">
-<link rel="up" href="../tutorials.html" title=" Spirit.Lex
- Tutorials">
-<link rel="previous" href="lexer_tutorials.html" title=" Spirit.Lex
- Tutorials Overview">
-<link rel="next" href="lexer_quickstart2.html" title=" Quickstart
- 2 - A better word counter using Spirit.Lex">
+<link rel="up" href="../tutorials.html" title="Spirit.Lex Tutorials">
+<link rel="prev" href="lexer_tutorials.html" title="Spirit.Lex Tutorials Overview">
+<link rel="next" href="lexer_quickstart2.html" title="Quickstart 2 - A better word counter using Spirit.Lex">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
 <table cellpadding="2" width="100%"><tr>
@@ -26,15 +22,11 @@
 <div class="spirit-nav">
 <a accesskey="p" href="lexer_tutorials.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../tutorials.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="lexer_quickstart2.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h4 class="title">
-<a name="spirit.lex.tutorials.lexer_quickstart1"></a><a href="lexer_quickstart1.html" title=" Quickstart
- 1 - A word counter using Spirit.Lex"> Quickstart
+<div class="section" title="Quickstart 1 - A word counter using Spirit.Lex">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="spirit.lex.tutorials.lexer_quickstart1"></a><a class="link" href="lexer_quickstart1.html" title="Quickstart 1 - A word counter using Spirit.Lex"> Quickstart
         1 - A word counter using <span class="emphasis"><em>Spirit.Lex</em></span></a>
-</h4></div></div>
-<div></div>
-</div>
+</h4></div></div></div>
 <p>
           <span class="emphasis"><em>Spirit.Lex</em></span> is very modular, which follows the general
           building principle of the Spirit
@@ -43,20 +35,20 @@
           but nevertheless can be used separately to build standalone lexical analyzers.
           The first quick start example describes a standalone application: counting
           characters, words, and lines in a file, very similar to what the well known
- Unix command <tt class="computeroutput"><span class="identifier">wc</span></tt> is doing
+ Unix command <code class="computeroutput"><span class="identifier">wc</span></code> is doing
           (for the full example code see here: word_count_functor.cpp).
         </p>
-<a name="spirit.lex.tutorials.lexer_quickstart1.prerequisites"></a><h5>
-<a name="id482228"></a>
- Prerequisites
- </h5>
+<a name="spirit.lex.tutorials.lexer_quickstart1.prerequisites"></a><h6>
+<a name="id1094061"></a>
+ <a class="link" href="lexer_quickstart1.html#spirit.lex.tutorials.lexer_quickstart1.prerequisites">Prerequisites</a>
+ </h6>
 <p>
- The only required <tt class="computeroutput"><span class="preprocessor">#include</span></tt>
+ The only required <code class="computeroutput"><span class="preprocessor">#include</span></code>
           specific to <span class="emphasis"><em>Spirit.Lex</em></span> follows. It is a wrapper for
           all necessary definitions to use <span class="emphasis"><em>Spirit.Lex</em></span> in a standalone
           fashion, and on top of the Lexertl
- library. Additionally we <tt class="computeroutput"><span class="preprocessor">#include</span></tt>
- two of the Boost headers to define <tt class="computeroutput"><span class="identifier">boost</span><span class="special">::</span><span class="identifier">bind</span><span class="special">()</span></tt> and <tt class="computeroutput"><span class="identifier">boost</span><span class="special">::</span><span class="identifier">ref</span><span class="special">()</span></tt>.
+ library. Additionally we <code class="computeroutput"><span class="preprocessor">#include</span></code>
+ two of the Boost headers to define <code class="computeroutput"><span class="identifier">boost</span><span class="special">::</span><span class="identifier">bind</span><span class="special">()</span></code> and <code class="computeroutput"><span class="identifier">boost</span><span class="special">::</span><span class="identifier">ref</span><span class="special">()</span></code>.
         </p>
 <p>
           </p>
@@ -85,11 +77,11 @@
           </p>
 <p>
         </p>
-<a name="spirit.lex.tutorials.lexer_quickstart1.defining_tokens"></a><h5>
-<a name="id482575"></a>
- <a href="lexer_quickstart1.html#spirit.lex.tutorials.lexer_quickstart1.defining_tokens">Defining
+<a name="spirit.lex.tutorials.lexer_quickstart1.defining_tokens"></a><h6>
+<a name="id1094306"></a>
+ <a class="link" href="lexer_quickstart1.html#spirit.lex.tutorials.lexer_quickstart1.defining_tokens">Defining
           Tokens</a>
- </h5>
+ </h6>
 <p>
           The most important step while creating a lexer using <span class="emphasis"><em>Spirit.Lex</em></span>
           is to define the tokens to be recognized in the input sequence. This is
@@ -102,16 +94,16 @@
 <p>
           </p>
 <p>
- The template <tt class="computeroutput"><span class="identifier">word_count_tokens</span></tt>
- defines three different tokens: <tt class="computeroutput"><span class="identifier">ID_WORD</span></tt>,
- <tt class="computeroutput"><span class="identifier">ID_EOL</span></tt>, and <tt class="computeroutput"><span class="identifier">ID_CHAR</span></tt>, representing a word (anything
+ The template <code class="computeroutput"><span class="identifier">word_count_tokens</span></code>
+ defines three different tokens: <code class="computeroutput"><span class="identifier">ID_WORD</span></code>,
+ <code class="computeroutput"><span class="identifier">ID_EOL</span></code>, and <code class="computeroutput"><span class="identifier">ID_CHAR</span></code>, representing a word (anything
             except a whitespace or a newline), a newline character, and any other
- character (<tt class="computeroutput"><span class="identifier">ID_WORD</span></tt>,
- <tt class="computeroutput"><span class="identifier">ID_EOL</span></tt>, and <tt class="computeroutput"><span class="identifier">ID_CHAR</span></tt> are enum values representing
+ character (<code class="computeroutput"><span class="identifier">ID_WORD</span></code>,
+ <code class="computeroutput"><span class="identifier">ID_EOL</span></code>, and <code class="computeroutput"><span class="identifier">ID_CHAR</span></code> are enum values representing
             the token ids, but could be anything else convertible to an integer as
             well). The direct base class of any token definition class needs to be
- the template <tt class="computeroutput"><span class="identifier">lexer_def</span><span class="special">&lt;&gt;</span></tt>, where the corresponding template
- parameter (here: <tt class="computeroutput"><span class="identifier">lexertl_lexer</span><span class="special">&lt;</span><span class="identifier">BaseIterator</span><span class="special">&gt;</span></tt>) defines which underlying lexer engine
+ the template <code class="computeroutput"><span class="identifier">lexer_def</span><span class="special">&lt;&gt;</span></code>, where the corresponding template
+ parameter (here: <code class="computeroutput"><span class="identifier">lexertl_lexer</span><span class="special">&lt;</span><span class="identifier">BaseIterator</span><span class="special">&gt;</span></code>) defines which underlying lexer engine
             has to be used to provide the required state machine functionality. In
             this example we use the Lexertl based lexer engine as the underlying
             lexer type.
@@ -140,18 +132,18 @@
           </p>
 <p>
         </p>
-<a name="spirit.lex.tutorials.lexer_quickstart1.doing_the_useful_work"></a><h5>
-<a name="id483024"></a>
- <a href="lexer_quickstart1.html#spirit.lex.tutorials.lexer_quickstart1.doing_the_useful_work">Doing
+<a name="spirit.lex.tutorials.lexer_quickstart1.doing_the_useful_work"></a><h6>
+<a name="id1094614"></a>
+ <a class="link" href="lexer_quickstart1.html#spirit.lex.tutorials.lexer_quickstart1.doing_the_useful_work">Doing
           the Useful Work</a>
- </h5>
+ </h6>
 <p>
           We will use a setup, where we want the <span class="emphasis"><em>Spirit.Lex</em></span>
           library to invoke a given function after any of of the generated tokens
           is recognized. For this reason we need to implement a functor taking at
           least the generated token as an argument and returning a boolean value
           allowing to stop the tokenization process. The default token type used
- in this example carries a token value of the type <tt class="computeroutput"><span class="identifier">iterator_range</span><span class="special">&lt;</span><span class="identifier">BaseIterator</span><span class="special">&gt;</span></tt> pointing to the matched range in the
+ in this example carries a token value of the type <code class="computeroutput"><span class="identifier">iterator_range</span><span class="special">&lt;</span><span class="identifier">BaseIterator</span><span class="special">&gt;</span></code> pointing to the matched range in the
           underlying input sequence.
         </p>
 <p>
@@ -198,25 +190,25 @@
         </p>
 <p>
           All what's left is to write some boilerplate code helping to tie together
- the pieces described so far. To simplify this example we call the <tt class="computeroutput"><span class="identifier">lex</span><span class="special">::</span><span class="identifier">tokenize</span><span class="special">()</span></tt>
+ the pieces described so far. To simplify this example we call the <code class="computeroutput"><span class="identifier">lex</span><span class="special">::</span><span class="identifier">tokenize</span><span class="special">()</span></code>
           function implemented in <span class="emphasis"><em>Spirit.Lex</em></span> (for a more detailed
- description of this function see here: <span class="bold"><b>FIXME</b></span>),
+ description of this function see here: <span class="bold"><strong>FIXME</strong></span>),
           even if we could have written a loop to iterate over the lexer iterators
- [<tt class="computeroutput"><span class="identifier">first</span></tt>, <tt class="computeroutput"><span class="identifier">last</span></tt>)
+ [<code class="computeroutput"><span class="identifier">first</span></code>, <code class="computeroutput"><span class="identifier">last</span></code>)
           as well.
         </p>
-<a name="spirit.lex.tutorials.lexer_quickstart1.pulling_everything_together"></a><h5>
-<a name="id483721"></a>
- <a href="lexer_quickstart1.html#spirit.lex.tutorials.lexer_quickstart1.pulling_everything_together">Pulling
+<a name="spirit.lex.tutorials.lexer_quickstart1.pulling_everything_together"></a><h6>
+<a name="id1095113"></a>
+ <a class="link" href="lexer_quickstart1.html#spirit.lex.tutorials.lexer_quickstart1.pulling_everything_together">Pulling
           Everything Together</a>
- </h5>
+ </h6>
 <p>
           </p>
 <p>
- The main function simply loads the given file into memory (as a <tt class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">string</span></tt>), instantiates an instance of
- the token definition template using the correct iterator type (<tt class="computeroutput"><span class="identifier">word_count_tokens</span><span class="special">&lt;</span><span class="keyword">char</span> <span class="keyword">const</span><span class="special">*&gt;</span></tt>), and finally calls <tt class="computeroutput"><span class="identifier">lex</span><span class="special">::</span><span class="identifier">tokenize</span></tt>, passing an instance of the
- counter function object. The return value of <tt class="computeroutput"><span class="identifier">lex</span><span class="special">::</span><span class="identifier">tokenize</span><span class="special">()</span></tt> will be <tt class="computeroutput"><span class="keyword">true</span></tt>
- if the whole input sequence has been successfully tokenized, and <tt class="computeroutput"><span class="keyword">false</span></tt> otherwise.
+ The main function simply loads the given file into memory (as a <code class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">string</span></code>), instantiates an instance of
+ the token definition template using the correct iterator type (<code class="computeroutput"><span class="identifier">word_count_tokens</span><span class="special">&lt;</span><span class="keyword">char</span> <span class="keyword">const</span><span class="special">*&gt;</span></code>), and finally calls <code class="computeroutput"><span class="identifier">lex</span><span class="special">::</span><span class="identifier">tokenize</span></code>, passing an instance of the
+ counter function object. The return value of <code class="computeroutput"><span class="identifier">lex</span><span class="special">::</span><span class="identifier">tokenize</span><span class="special">()</span></code> will be <code class="computeroutput"><span class="keyword">true</span></code>
+ if the whole input sequence has been successfully tokenized, and <code class="computeroutput"><span class="keyword">false</span></code> otherwise.
           </p>
 <p>
           </p>
@@ -258,23 +250,23 @@
           </p>
 <p>
         </p>
-<a name="spirit.lex.tutorials.lexer_quickstart1.comparing__emphasis_spirit_lex__emphasis__with__ulink_url__http___flex_sourceforge_net___flex__ulink_"></a><h5>
-<a name="id484851"></a>
- <a href="lexer_quickstart1.html#spirit.lex.tutorials.lexer_quickstart1.comparing__emphasis_spirit_lex__emphasis__with__ulink_url__http___flex_sourceforge_net___flex__ulink_">Comparing
+<a name="spirit.lex.tutorials.lexer_quickstart1.comparing__emphasis_spirit_lex__emphasis__with__ulink_url__http___flex_sourceforge_net___flex__ulink_"></a><h6>
+<a name="id1095940"></a>
+ <a class="link" href="lexer_quickstart1.html#spirit.lex.tutorials.lexer_quickstart1.comparing__emphasis_spirit_lex__emphasis__with__ulink_url__http___flex_sourceforge_net___flex__ulink_">Comparing
           <span class="emphasis"><em>Spirit.Lex</em></span> with Flex</a>
- </h5>
+ </h6>
 <p>
           This example was deliberately chosen to be as much as possible similar
           to the equivalent Flex
           program (see below), which isn't too different from what has to be written
           when using <span class="emphasis"><em>Spirit.Lex</em></span>.
         </p>
-<div class="note"><table border="0" summary="Note">
+<div class="note" title="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>
 </tr>
-<tr><td colspan="2" align="left" valign="top"><p>
+<tr><td align="left" valign="top"><p>
             Interestingly enough, performance comparisons of lexical analyzers written
             using <span class="emphasis"><em>Spirit.Lex</em></span> with equivalent programs generated
             by Flex show that both

Modified: trunk/libs/spirit/doc/html/spirit/lex/tutorials/lexer_quickstart2.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/lex/tutorials/lexer_quickstart2.html (original)
+++ trunk/libs/spirit/doc/html/spirit/lex/tutorials/lexer_quickstart2.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -1,17 +1,13 @@
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title> Quickstart
- 2 - A better word counter using Spirit.Lex</title>
+<title>Quickstart 2 - A better word counter using Spirit.Lex</title>
 <link rel="stylesheet" href="../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../index.html" title="Spirit 2.1">
-<link rel="up" href="../tutorials.html" title=" Spirit.Lex
- Tutorials">
-<link rel="previous" href="lexer_quickstart1.html" title=" Quickstart
- 1 - A word counter using Spirit.Lex">
-<link rel="next" href="lexer_quickstart3.html" title=" Quickstart
- 3 - Counting Words Using a Parser">
+<link rel="up" href="../tutorials.html" title="Spirit.Lex Tutorials">
+<link rel="prev" href="lexer_quickstart1.html" title="Quickstart 1 - A word counter using Spirit.Lex">
+<link rel="next" href="lexer_quickstart3.html" title="Quickstart 3 - Counting Words Using a Parser">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
 <table cellpadding="2" width="100%"><tr>
@@ -26,19 +22,14 @@
 <div class="spirit-nav">
 <a accesskey="p" href="lexer_quickstart1.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../tutorials.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="lexer_quickstart3.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h4 class="title">
-<a name="spirit.lex.tutorials.lexer_quickstart2"></a><a href="lexer_quickstart2.html" title=" Quickstart
- 2 - A better word counter using Spirit.Lex"> Quickstart
+<div class="section" title="Quickstart 2 - A better word counter using Spirit.Lex">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="spirit.lex.tutorials.lexer_quickstart2"></a><a class="link" href="lexer_quickstart2.html" title="Quickstart 2 - A better word counter using Spirit.Lex"> Quickstart
         2 - A better word counter using <span class="emphasis"><em>Spirit.Lex</em></span></a>
-</h4></div></div>
-<div></div>
-</div>
+</h4></div></div></div>
 <p>
           People knowing Flex will
- probably complain about the example from the section <a href="lexer_quickstart1.html" title=" Quickstart
- 1 - A word counter using Spirit.Lex">Lex
+ probably complain about the example from the section <a class="link" href="lexer_quickstart1.html" title="Quickstart 1 - A word counter using Spirit.Lex">Lex
           Quickstart 1 - A word counter using <span class="emphasis"><em>Spirit.Lex</em></span></a>
           as being overly complex and not being written to leverage the possibilities
           provided by this tool. In particular the previous example did not directly
@@ -48,12 +39,12 @@
           to count text elements only it introduces other new concepts and configuration
           options along the lines (for the full example code see here: word_count_lexer.cpp).
         </p>
-<a name="spirit.lex.tutorials.lexer_quickstart2.prerequisites"></a><h5>
-<a name="id485908"></a>
- Prerequisites
- </h5>
+<a name="spirit.lex.tutorials.lexer_quickstart2.prerequisites"></a><h6>
+<a name="id1098002"></a>
+ <a class="link" href="lexer_quickstart2.html#spirit.lex.tutorials.lexer_quickstart2.prerequisites">Prerequisites</a>
+ </h6>
 <p>
- In addition to the only required <tt class="computeroutput"><span class="preprocessor">#include</span></tt>
+ In addition to the only required <code class="computeroutput"><span class="preprocessor">#include</span></code>
           specific to <span class="emphasis"><em>Spirit.Lex</em></span> this example needs to include
           a couple of header files from the Boost.Phoenix
           library. This example shows how to attach functors to token definitions,
@@ -122,18 +113,18 @@
           </p>
 <p>
         </p>
-<a name="spirit.lex.tutorials.lexer_quickstart2.semantic_actions_in__emphasis_spirit_lex__emphasis_"></a><h5>
-<a name="id486797"></a>
- <a href="lexer_quickstart2.html#spirit.lex.tutorials.lexer_quickstart2.semantic_actions_in__emphasis_spirit_lex__emphasis_">Semantic
+<a name="spirit.lex.tutorials.lexer_quickstart2.semantic_actions_in__emphasis_spirit_lex__emphasis_"></a><h6>
+<a name="id1098652"></a>
+ <a class="link" href="lexer_quickstart2.html#spirit.lex.tutorials.lexer_quickstart2.semantic_actions_in__emphasis_spirit_lex__emphasis_">Semantic
           Actions in <span class="emphasis"><em>Spirit.Lex</em></span></a>
- </h5>
+ </h6>
 <p>
           <span class="emphasis"><em>Spirit.Lex</em></span> uses a very similar way of associating
           actions with the token definitions (which should look familiar to anybody
           knowlegdeable with Spirit
- as well): specifying the operations to execute inside of a pair of <tt class="computeroutput"><span class="special">[]</span></tt> brackets. In order to be able to attach
+ as well): specifying the operations to execute inside of a pair of <code class="computeroutput"><span class="special">[]</span></code> brackets. In order to be able to attach
           semantic actions to token definitions for each of them there is defined
- an instance of a <tt class="computeroutput"><span class="identifier">token_def</span><span class="special">&lt;&gt;</span></tt>.
+ an instance of a <code class="computeroutput"><span class="identifier">token_def</span><span class="special">&lt;&gt;</span></code>.
         </p>
 <p>
           </p>
@@ -170,7 +161,7 @@
 <p>
         </p>
 <p>
- The semantics of the shown code is as follows. The code inside the <tt class="computeroutput"><span class="special">[]</span></tt> brackets will be executed whenever the
+ The semantics of the shown code is as follows. The code inside the <code class="computeroutput"><span class="special">[]</span></code> brackets will be executed whenever the
           corresponding token has been matched by the lexical analyzer. This is very
           similar to Flex, where
           the action code associated with a token definition gets executed after
@@ -178,24 +169,22 @@
           objects constructed using Boost.Phoenix,
           but it is possible to insert any C++ function or function object as long
           as it exposes the proper interface. For more details on please refer to
- the section <a href="../abstracts/lexer_semantic_actions.html" title=" Lexer
- Semantic Actions">Lexer
+ the section <a class="link" href="../abstracts/lexer_semantic_actions.html" title="Lexer Semantic Actions">Lexer
           Semantic Actions</a>.
         </p>
-<a name="spirit.lex.tutorials.lexer_quickstart2.associating_token_definitions_with_the_lexer"></a><h5>
-<a name="id487654"></a>
- <a href="lexer_quickstart2.html#spirit.lex.tutorials.lexer_quickstart2.associating_token_definitions_with_the_lexer">Associating
+<a name="spirit.lex.tutorials.lexer_quickstart2.associating_token_definitions_with_the_lexer"></a><h6>
+<a name="id1099270"></a>
+ <a class="link" href="lexer_quickstart2.html#spirit.lex.tutorials.lexer_quickstart2.associating_token_definitions_with_the_lexer">Associating
           Token Definitions with the Lexer</a>
- </h5>
+ </h6>
 <p>
- If you compare this code to the code from <a href="lexer_quickstart1.html" title=" Quickstart
- 1 - A word counter using Spirit.Lex">Lex
+ If you compare this code to the code from <a class="link" href="lexer_quickstart1.html" title="Quickstart 1 - A word counter using Spirit.Lex">Lex
           Quickstart 1 - A word counter using <span class="emphasis"><em>Spirit.Lex</em></span></a>
           with regard to the way how token definitions are associated with the lexer,
           you will notice a different syntax being used here. In the previous example
- we have been using the <tt class="computeroutput"><span class="identifier">self</span><span class="special">.</span><span class="identifier">add</span><span class="special">()</span></tt> style of the API, while we here directly
- assign the token definitions to <tt class="computeroutput"><span class="identifier">self</span></tt>,
- combining the different token definitions using the <tt class="computeroutput"><span class="special">|</span></tt>
+ we have been using the <code class="computeroutput"><span class="identifier">self</span><span class="special">.</span><span class="identifier">add</span><span class="special">()</span></code> style of the API, while we here directly
+ assign the token definitions to <code class="computeroutput"><span class="identifier">self</span></code>,
+ combining the different token definitions using the <code class="computeroutput"><span class="special">|</span></code>
           operator. Here is the code snippet again:
         </p>
 <pre class="programlisting"><span class="identifier">self</span> <span class="special">=</span> <span class="identifier">word</span> <span class="special">[++</span><span class="identifier">ref</span><span class="special">(</span><span class="identifier">w</span><span class="special">),</span> <span class="identifier">ref</span><span class="special">(</span><span class="identifier">c</span><span class="special">)</span> <span class="special">+=</span> <span class="identifier">distance</span><span class="special">(</span><span class="identifier">_1</span><span class="special">)]</span>
@@ -206,10 +195,10 @@
 <p>
           This way we have a very powerful and natural way of building the lexical
           analyzer. If translated into English this may be read as: The lexical analyer
- will recognize ('<tt class="computeroutput"><span class="special">=</span></tt>') tokens
- as defined by any of ('<tt class="computeroutput"><span class="special">|</span></tt>')
- the token definitions <tt class="computeroutput"><span class="identifier">word</span></tt>,
- <tt class="computeroutput"><span class="identifier">eol</span></tt>, and <tt class="computeroutput"><span class="identifier">any</span></tt>.
+ will recognize ('<code class="computeroutput"><span class="special">=</span></code>') tokens
+ as defined by any of ('<code class="computeroutput"><span class="special">|</span></code>')
+ the token definitions <code class="computeroutput"><span class="identifier">word</span></code>,
+ <code class="computeroutput"><span class="identifier">eol</span></code>, and <code class="computeroutput"><span class="identifier">any</span></code>.
         </p>
 <p>
           A second difference to the previous example is that we do not explicitly
@@ -217,13 +206,13 @@
           to trigger some useful work has freed us from the need to define those.
           To ensure every token gets assigned a id the <span class="emphasis"><em>Spirit.Lex</em></span>
           library internally assigns unique numbers to the token definitions, starting
- with the constant defined by <tt class="computeroutput"><span class="identifier">boost</span><span class="special">::</span><span class="identifier">spirit</span><span class="special">::</span><span class="identifier">lex</span><span class="special">::</span><span class="identifier">min_token_id</span></tt>.
+ with the constant defined by <code class="computeroutput"><span class="identifier">boost</span><span class="special">::</span><span class="identifier">spirit</span><span class="special">::</span><span class="identifier">lex</span><span class="special">::</span><span class="identifier">min_token_id</span></code>.
         </p>
-<a name="spirit.lex.tutorials.lexer_quickstart2.pulling_everything_together"></a><h5>
-<a name="id488080"></a>
- <a href="lexer_quickstart2.html#spirit.lex.tutorials.lexer_quickstart2.pulling_everything_together">Pulling
+<a name="spirit.lex.tutorials.lexer_quickstart2.pulling_everything_together"></a><h6>
+<a name="id1099644"></a>
+ <a class="link" href="lexer_quickstart2.html#spirit.lex.tutorials.lexer_quickstart2.pulling_everything_together">Pulling
           everything together</a>
- </h5>
+ </h6>
 <p>
           In order to execute the code defined above we still need to instantiate
           an instance of the lexer type, feed it from some input sequence and create
@@ -238,20 +227,20 @@
 <pre class="programlisting"><span class="keyword">int</span> <span class="identifier">main</span><span class="special">(</span><span class="keyword">int</span> <span class="identifier">argc</span><span class="special">,</span> <span class="keyword">char</span><span class="special">*</span> <span class="identifier">argv</span><span class="special">[])</span>
 <span class="special">{</span>
 
-<span class="callout_bug"><a name="spirit8co" href="lexer_quickstart2.html#spirit8"><img src="../../../../../../../doc/src/images/callouts/1.png" alt="1" border="0"></a></span> <span class="keyword">typedef</span> <span class="identifier">lexertl</span><span class="special">::</span><span class="identifier">token</span><span class="special">&lt;</span><span class="keyword">char</span> <span class="keyword">const</span><span class="special">*,</span> <span class="identifier">omitted</span><span class="special">,</span> <span class="identifier">boost</span><span class="special">::</span><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">false_</span><span class="special">&gt;</span> <span class="identifier">token_type</span><span class="special">;</span>
+<span class="callout_bug"><a class="co" name="spirit8co" href="lexer_quickstart2.html#spirit8"><img src="../../../../../../../doc/src/images/callouts/1.png" alt="1" border="0"></a></span> <span class="keyword">typedef</span> <span class="identifier">lexertl</span><span class="special">::</span><span class="identifier">token</span><span class="special">&lt;</span><span class="keyword">char</span> <span class="keyword">const</span><span class="special">*,</span> <span class="identifier">omitted</span><span class="special">,</span> <span class="identifier">boost</span><span class="special">::</span><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">false_</span><span class="special">&gt;</span> <span class="identifier">token_type</span><span class="special">;</span>
 
-<span class="callout_bug"><a name="spirit9co" href="lexer_quickstart2.html#spirit9"><img src="../../../../../../../doc/src/images/callouts/2.png" alt="2" border="0"></a></span> <span class="keyword">typedef</span> <span class="identifier">lexertl</span><span class="special">::</span><span class="identifier">actor_lexer</span><span class="special">&lt;</span><span class="identifier">token_type</span><span class="special">&gt;</span> <span class="identifier">lexer_type</span><span class="special">;</span>
+<span class="callout_bug"><a class="co" name="spirit9co" href="lexer_quickstart2.html#spirit9"><img src="../../../../../../../doc/src/images/callouts/2.png" alt="2" border="0"></a></span> <span class="keyword">typedef</span> <span class="identifier">lexertl</span><span class="special">::</span><span class="identifier">actor_lexer</span><span class="special">&lt;</span><span class="identifier">token_type</span><span class="special">&gt;</span> <span class="identifier">lexer_type</span><span class="special">;</span>
 
-<span class="callout_bug"><a name="spirit10co" href="lexer_quickstart2.html#spirit10"><img src="../../../../../../../doc/src/images/callouts/3.png" alt="3" border="0"></a></span> <span class="identifier">word_count_tokens</span><span class="special">&lt;</span><span class="identifier">lexer_type</span><span class="special">&gt;</span> <span class="identifier">word_count_lexer</span><span class="special">;</span>
+<span class="callout_bug"><a class="co" name="spirit10co" href="lexer_quickstart2.html#spirit10"><img src="../../../../../../../doc/src/images/callouts/3.png" alt="3" border="0"></a></span> <span class="identifier">word_count_tokens</span><span class="special">&lt;</span><span class="identifier">lexer_type</span><span class="special">&gt;</span> <span class="identifier">word_count_lexer</span><span class="special">;</span>
 
-<span class="callout_bug"><a name="spirit11co" href="lexer_quickstart2.html#spirit11"><img src="../../../../../../../doc/src/images/callouts/4.png" alt="4" border="0"></a></span> <span class="identifier">std</span><span class="special">::</span><span class="identifier">string</span> <span class="identifier">str</span> <span class="special">(</span><span class="identifier">read_from_file</span><span class="special">(</span><span class="number">1</span> <span class="special">==</span> <span class="identifier">argc</span> <span class="special">?</span> <span class="string">"word_count.input"</span> <span class="special">:</span> <span class="identifier">argv</span><span class="special">[</span><span class="number">1</span><span class="special">]));</span>
+<span class="callout_bug"><a class="co" name="spirit11co" href="lexer_quickstart2.html#spirit11"><img src="../../../../../../../doc/src/images/callouts/4.png" alt="4" border="0"></a></span> <span class="identifier">std</span><span class="special">::</span><span class="identifier">string</span> <span class="identifier">str</span> <span class="special">(</span><span class="identifier">read_from_file</span><span class="special">(</span><span class="number">1</span> <span class="special">==</span> <span class="identifier">argc</span> <span class="special">?</span> <span class="string">"word_count.input"</span> <span class="special">:</span> <span class="identifier">argv</span><span class="special">[</span><span class="number">1</span><span class="special">]));</span>
     <span class="keyword">char</span> <span class="keyword">const</span><span class="special">*</span> <span class="identifier">first</span> <span class="special">=</span> <span class="identifier">str</span><span class="special">.</span><span class="identifier">c_str</span><span class="special">();</span>
     <span class="keyword">char</span> <span class="keyword">const</span><span class="special">*</span> <span class="identifier">last</span> <span class="special">=</span> <span class="special">&amp;</span><span class="identifier">first</span><span class="special">[</span><span class="identifier">str</span><span class="special">.</span><span class="identifier">size</span><span class="special">()];</span>
 
-<span class="callout_bug"><a name="spirit12co" href="lexer_quickstart2.html#spirit12"><img src="../../../../../../../doc/src/images/callouts/5.png" alt="5" border="0"></a></span> <span class="identifier">lexer_type</span><span class="special">::</span><span class="identifier">iterator_type</span> <span class="identifier">iter</span> <span class="special">=</span> <span class="identifier">word_count_lexer</span><span class="special">.</span><span class="identifier">begin</span><span class="special">(</span><span class="identifier">first</span><span class="special">,</span> <span class="identifier">last</span><span class="special">);</span>
+<span class="callout_bug"><a class="co" name="spirit12co" href="lexer_quickstart2.html#spirit12"><img src="../../../../../../../doc/src/images/callouts/5.png" alt="5" border="0"></a></span> <span class="identifier">lexer_type</span><span class="special">::</span><span class="identifier">iterator_type</span> <span class="identifier">iter</span> <span class="special">=</span> <span class="identifier">word_count_lexer</span><span class="special">.</span><span class="identifier">begin</span><span class="special">(</span><span class="identifier">first</span><span class="special">,</span> <span class="identifier">last</span><span class="special">);</span>
     <span class="identifier">lexer_type</span><span class="special">::</span><span class="identifier">iterator_type</span> <span class="identifier">end</span> <span class="special">=</span> <span class="identifier">word_count_lexer</span><span class="special">.</span><span class="identifier">end</span><span class="special">();</span>
 
-<span class="callout_bug"><a name="spirit13co" href="lexer_quickstart2.html#spirit13"><img src="../../../../../../../doc/src/images/callouts/6.png" alt="6" border="0"></a></span> <span class="keyword">while</span> <span class="special">(</span><span class="identifier">iter</span> <span class="special">!=</span> <span class="identifier">end</span> <span class="special">&amp;&amp;</span> <span class="identifier">token_is_valid</span><span class="special">(*</span><span class="identifier">iter</span><span class="special">))</span>
+<span class="callout_bug"><a class="co" name="spirit13co" href="lexer_quickstart2.html#spirit13"><img src="../../../../../../../doc/src/images/callouts/6.png" alt="6" border="0"></a></span> <span class="keyword">while</span> <span class="special">(</span><span class="identifier">iter</span> <span class="special">!=</span> <span class="identifier">end</span> <span class="special">&amp;&amp;</span> <span class="identifier">token_is_valid</span><span class="special">(*</span><span class="identifier">iter</span><span class="special">))</span>
         <span class="special">++</span><span class="identifier">iter</span><span class="special">;</span>
 
     <span class="keyword">if</span> <span class="special">(</span><span class="identifier">iter</span> <span class="special">==</span> <span class="identifier">end</span><span class="special">)</span> <span class="special">{</span>
@@ -276,44 +265,38 @@
             </p>
 <div class="calloutlist"><table border="0" summary="Callout list">
 <tr>
-<td width="5%" valign="top" align="left">
-<a name="spirit8"></a>1 </td>
-<td valign="top" align="left"><p> Specifying <tt class="computeroutput"><span class="identifier">omitted</span></tt> as
+<td width="5%" valign="top" align="left"><p><a name="spirit8"></a>1 </p></td>
+<td valign="top" align="left"><p> Specifying <code class="computeroutput"><span class="identifier">omitted</span></code> as
             the token attribute type generates a token class not holding any token
             attribute at all (not even the iterator range of the matched input sequence),
             therefore optimizing the token, the lexer, and possibly the parser implementation
- as much as possible. Specifying <tt class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">false_</span></tt>
+ as much as possible. Specifying <code class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">false_</span></code>
             as the 3rd template parameter generates a token type and an iterator,
             both holding no lexer state, allowing for even more aggressive optimizations.
             As a result the token instances contain the token ids as the only data
             member. </p></td>
 </tr>
 <tr>
-<td width="5%" valign="top" align="left">
-<a name="spirit9"></a>2 </td>
+<td width="5%" valign="top" align="left"><p><a name="spirit9"></a>2 </p></td>
 <td valign="top" align="left"><p> This defines the lexer type to use </p></td>
 </tr>
 <tr>
-<td width="5%" valign="top" align="left">
-<a name="spirit10"></a>3 </td>
+<td width="5%" valign="top" align="left"><p><a name="spirit10"></a>3 </p></td>
 <td valign="top" align="left"><p> Create the lexer object instance
             needed to invoke the lexical analysis </p></td>
 </tr>
 <tr>
-<td width="5%" valign="top" align="left">
-<a name="spirit11"></a>4 </td>
+<td width="5%" valign="top" align="left"><p><a name="spirit11"></a>4 </p></td>
 <td valign="top" align="left"><p> Read input from the given file,
             tokenize all the input, while discarding all generated tokens </p></td>
 </tr>
 <tr>
-<td width="5%" valign="top" align="left">
-<a name="spirit12"></a>5 </td>
+<td width="5%" valign="top" align="left"><p><a name="spirit12"></a>5 </p></td>
 <td valign="top" align="left"><p> Create
             a pair of iterators returning the sequence of generated tokens </p></td>
 </tr>
 <tr>
-<td width="5%" valign="top" align="left">
-<a name="spirit13"></a>6 </td>
+<td width="5%" valign="top" align="left"><p><a name="spirit13"></a>6 </p></td>
 <td valign="top" align="left"><p> Here we
             simply iterate over all tokens, making sure to break the loop if an invalid
             token gets returned from the lexer </p></td>

Modified: trunk/libs/spirit/doc/html/spirit/lex/tutorials/lexer_quickstart3.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/lex/tutorials/lexer_quickstart3.html (original)
+++ trunk/libs/spirit/doc/html/spirit/lex/tutorials/lexer_quickstart3.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -1,16 +1,13 @@
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title> Quickstart
- 3 - Counting Words Using a Parser</title>
+<title>Quickstart 3 - Counting Words Using a Parser</title>
 <link rel="stylesheet" href="../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../index.html" title="Spirit 2.1">
-<link rel="up" href="../tutorials.html" title=" Spirit.Lex
- Tutorials">
-<link rel="previous" href="lexer_quickstart2.html" title=" Quickstart
- 2 - A better word counter using Spirit.Lex">
-<link rel="next" href="../abstracts.html" title=" Abstracts">
+<link rel="up" href="../tutorials.html" title="Spirit.Lex Tutorials">
+<link rel="prev" href="lexer_quickstart2.html" title="Quickstart 2 - A better word counter using Spirit.Lex">
+<link rel="next" href="../abstracts.html" title="Abstracts">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
 <table cellpadding="2" width="100%"><tr>
@@ -25,15 +22,11 @@
 <div class="spirit-nav">
 <a accesskey="p" href="lexer_quickstart2.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../tutorials.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="../abstracts.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h4 class="title">
-<a name="spirit.lex.tutorials.lexer_quickstart3"></a><a href="lexer_quickstart3.html" title=" Quickstart
- 3 - Counting Words Using a Parser"> Quickstart
+<div class="section" title="Quickstart 3 - Counting Words Using a Parser">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="spirit.lex.tutorials.lexer_quickstart3"></a><a class="link" href="lexer_quickstart3.html" title="Quickstart 3 - Counting Words Using a Parser"> Quickstart
         3 - Counting Words Using a Parser</a>
-</h4></div></div>
-<div></div>
-</div>
+</h4></div></div></div>
 <p>
           The whole purpose of integrating <span class="emphasis"><em>Spirit.Lex</em></span> as part
           of the Spirit library
@@ -46,8 +39,7 @@
           usage of possibly different lexical analyzer libraries. The utilization
           of iterators seemed to be the right choice from this standpoint as well,
           mainly because these can be used as an abstraction layer hiding implementation
- specifics of the used lexer library. The <a href="lexer_quickstart3.html#spirit.lex.flowcontrol" title="Figure 4. The common flow control implemented while parsing
- combined with lexical analysis">picture</a>
+ specifics of the used lexer library. The <a class="link" href="lexer_quickstart3.html#spirit.lex.flowcontrol" title="Figure 4. The common flow control implemented while parsing combined with lexical analysis">picture</a>
           below shows the common flow control implemented while parsing combined
           with lexical analysis.
         </p>
@@ -56,16 +48,15 @@
 <div class="figure">
 <a name="spirit.lex.flowcontrol"></a><p class="title"><b>Figure 4. The common flow control implemented while parsing
           combined with lexical analysis</b></p>
-<span class="inlinemediaobject"><img src="./images/flowofcontrol.png" alt="The common flow
- control implemented while parsing combined with lexical analysis"></span>
+<div class="figure-contents"><span class="inlinemediaobject"><img src="../../.././images/flowofcontrol.png" alt="The common flow control implemented while parsing combined with lexical analysis"></span></div>
 </div>
-<p>
+<p><br class="figure-break">
         </p>
 <p>
           Another problem related to the integration of the lexical analyzer with
           the parser was to find a way how the defined tokens syntactically could
           be blended with the grammar definition syntax of Spirit.
- For tokens defined as instances of the <tt class="computeroutput"><span class="identifier">token_def</span><span class="special">&lt;&gt;</span></tt> class the most natural way of integration
+ For tokens defined as instances of the <code class="computeroutput"><span class="identifier">token_def</span><span class="special">&lt;&gt;</span></code> class the most natural way of integration
           was to allow to directly use these as parser components. Semantically these
           parser components succeed matching their input whenever the corresponding
           token type has been matched by the lexer. This quick start example will
@@ -73,14 +64,14 @@
           the numbers inside of semantic actions of a parser (for the full example
           code see here: word_count.cpp).
         </p>
-<a name="spirit.lex.tutorials.lexer_quickstart3.prerequisites"></a><h5>
-<a name="id489505"></a>
- Prerequisites
- </h5>
+<a name="spirit.lex.tutorials.lexer_quickstart3.prerequisites"></a><h6>
+<a name="id1100618"></a>
+ <a class="link" href="lexer_quickstart3.html#spirit.lex.tutorials.lexer_quickstart3.prerequisites">Prerequisites</a>
+ </h6>
 <p>
           This example uses two of the Spirit
           library components: <span class="emphasis"><em>Spirit.Lex</em></span> and <span class="emphasis"><em>Spirit.Qi</em></span>,
- consequently we have to <tt class="computeroutput"><span class="preprocessor">#include</span></tt>
+ consequently we have to <code class="computeroutput"><span class="preprocessor">#include</span></code>
           the corresponding header files. Again, we need to include a couple of header
           files from the Boost.Phoenix
           library. This example shows how to attach functors to parser components,
@@ -123,22 +114,20 @@
           </p>
 <p>
         </p>
-<a name="spirit.lex.tutorials.lexer_quickstart3.defining_tokens"></a><h5>
-<a name="id490110"></a>
- <a href="lexer_quickstart3.html#spirit.lex.tutorials.lexer_quickstart3.defining_tokens">Defining
+<a name="spirit.lex.tutorials.lexer_quickstart3.defining_tokens"></a><h6>
+<a name="id1101049"></a>
+ <a class="link" href="lexer_quickstart3.html#spirit.lex.tutorials.lexer_quickstart3.defining_tokens">Defining
           Tokens</a>
- </h5>
+ </h6>
 <p>
- If compared to the two previous quick start examples (<a href="lexer_quickstart1.html" title=" Quickstart
- 1 - A word counter using Spirit.Lex">Lex
+ If compared to the two previous quick start examples (<a class="link" href="lexer_quickstart1.html" title="Quickstart 1 - A word counter using Spirit.Lex">Lex
           Quickstart 1 - A word counter using <span class="emphasis"><em>Spirit.Lex</em></span></a>
- and <a href="lexer_quickstart2.html" title=" Quickstart
- 2 - A better word counter using Spirit.Lex">Lex Quickstart
+ and <a class="link" href="lexer_quickstart2.html" title="Quickstart 2 - A better word counter using Spirit.Lex">Lex Quickstart
           2 - A better word counter using <span class="emphasis"><em>Spirit.Lex</em></span></a>)
           the token definition class for this example does not reveal any surprises.
           However, it uses lexer token definition macros to simplify the composition
           of the regular expressions, which will be described in more detail in the
- section <span class="bold"><b>FIXME</b></span>. Generally, any token definition
+ section <span class="bold"><strong>FIXME</strong></span>. Generally, any token definition
           is usable without modification either for a standalone lexical analyzer
           or in conjunction with a parser.
         </p>
@@ -178,29 +167,29 @@
           </p>
 <p>
         </p>
-<a name="spirit.lex.tutorials.lexer_quickstart3.using_token_definition_instances_as_parsers"></a><h5>
-<a name="id490585"></a>
- <a href="lexer_quickstart3.html#spirit.lex.tutorials.lexer_quickstart3.using_token_definition_instances_as_parsers">Using
+<a name="spirit.lex.tutorials.lexer_quickstart3.using_token_definition_instances_as_parsers"></a><h6>
+<a name="id1101386"></a>
+ <a class="link" href="lexer_quickstart3.html#spirit.lex.tutorials.lexer_quickstart3.using_token_definition_instances_as_parsers">Using
           Token Definition Instances as Parsers</a>
- </h5>
+ </h6>
 <p>
           While the integration of lexer and parser in the control flow is achieved
           by using special iterators wrapping the lexical analyzer, we still nead
           a means of expressing in the grammar what tokens to match and where. The
           token definition class above uses three different ways of defining a token:
         </p>
-<div class="itemizedlist"><ul type="disc">
-<li>
- Using an instance of a <tt class="computeroutput"><span class="identifier">token_def</span><span class="special">&lt;&gt;</span></tt>, which is handy whenever you
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem">
+ Using an instance of a <code class="computeroutput"><span class="identifier">token_def</span><span class="special">&lt;&gt;</span></code>, which is handy whenever you
             need to specify a token attribute (for more information about lexer related
- attributes please look here: <a href="../abstracts/lexer_attributes.html" title=" Lexer Attributes">Lexer
+ attributes please look here: <a class="link" href="../abstracts/lexer_attributes.html" title="Lexer Attributes">Lexer
             Attributes</a>).
           </li>
-<li>
+<li class="listitem">
             Using a single character as the token, in this case the character represents
             itself as a token, where the token id is the ASCII character value.
           </li>
-<li>
+<li class="listitem">
             Using a regular expression represented as a string, where the token id
             needs to be specified explicitly to make the token accessible from the
             grammar level.
@@ -218,47 +207,63 @@
 <col>
 </colgroup>
 <thead><tr>
-<th><p>
+<th>
+ <p>
                   Token definition
- </p></th>
-<th><p>
+ </p>
+ </th>
+<th>
+ <p>
                   Parser integration
- </p></th>
+ </p>
+ </th>
 </tr></thead>
 <tbody>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">token_def</span><span class="special">&lt;&gt;</span></tt>
- </p></td>
-<td><p>
- The <tt class="computeroutput"><span class="identifier">token_def</span><span class="special">&lt;&gt;</span></tt>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">token_def</span><span class="special">&lt;&gt;</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ The <code class="computeroutput"><span class="identifier">token_def</span><span class="special">&lt;&gt;</span></code>
                   instance is directly usable as a parser component. Parsing of this
                   component will succeed if the regular expression used to define
                   this has been matched successfully.
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
+<td>
+ <p>
                   single character
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
                   The single character is directly usable in the grammar, under certain
- circumstances it needs to be wrapped by a <tt class="computeroutput"><span class="identifier">char_</span><span class="special">()</span></tt> parser component, though. Parsing
+ circumstances it needs to be wrapped by a <code class="computeroutput"><span class="identifier">char_</span><span class="special">()</span></code> parser component, though. Parsing
                   of this component will succeed if the single character has been
                   matched.
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
+<td>
+ <p>
                   explicit token id
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
                   To use an explicit token id in a <span class="emphasis"><em>Spirit.Qi</em></span>
- grammar you are required to wrap it with the special <tt class="computeroutput"><span class="identifier">token</span><span class="special">()</span></tt>
+ grammar you are required to wrap it with the special <code class="computeroutput"><span class="identifier">token</span><span class="special">()</span></code>
                   parser component. Parsing of this component will succeed if the
                   current token has the same token id as specified in the expression
- <tt class="computeroutput"><span class="identifier">token</span><span class="special">(&lt;</span><span class="identifier">id</span><span class="special">&gt;)</span></tt>.
- </p></td>
+ <code class="computeroutput"><span class="identifier">token</span><span class="special">(&lt;</span><span class="identifier">id</span><span class="special">&gt;)</span></code>.
+ </p>
+ </td>
 </tr>
 </tbody>
 </table></div>
@@ -298,54 +303,53 @@
 <p>
         </p>
 <p>
- As already described (see: Attributes),
+ As already described (see: <a class="link" href="../../../">Attributes</a>),
           the <span class="emphasis"><em>Spirit.Qi</em></span> parser library builds upon a set of
           of fully attributed parser components. Consequently, all the token definitions
           do support the this attribute model as well. The most natural way of implementing
           this was to use the token values as the attributes exposed by the parser
           component corresponding to the token definition (you can read more about
- this topic here: <a href="../abstracts/lexer_primitives/lexer_token_values.html" title="
- About Tokens and Token Values">About
+ this topic here: <a class="link" href="../abstracts/lexer_primitives/lexer_token_values.html" title="About Tokens and Token Values">About
           Tokens and Token Values</a>). The example above takes advantage of the
- full integration of the token values as the <tt class="computeroutput"><span class="identifier">token_def</span><span class="special">&lt;&gt;</span></tt>'s parser attributes: the <tt class="computeroutput"><span class="identifier">word</span></tt> token definition is declared as
- a <tt class="computeroutput"><span class="identifier">token_def</span><span class="special">&lt;</span><span class="identifier">std</span><span class="special">::</span><span class="identifier">string</span><span class="special">&gt;</span></tt>,
- making every instance of a <tt class="computeroutput"><span class="identifier">word</span></tt>
+ full integration of the token values as the <code class="computeroutput"><span class="identifier">token_def</span><span class="special">&lt;&gt;</span></code>'s parser attributes: the <code class="computeroutput"><span class="identifier">word</span></code> token definition is declared as
+ a <code class="computeroutput"><span class="identifier">token_def</span><span class="special">&lt;</span><span class="identifier">std</span><span class="special">::</span><span class="identifier">string</span><span class="special">&gt;</span></code>,
+ making every instance of a <code class="computeroutput"><span class="identifier">word</span></code>
           token carry the string representation of the matched input sequence as
- its value. The semantic action attached to <tt class="computeroutput"><span class="identifier">tok</span><span class="special">.</span><span class="identifier">word</span></tt>
- receives this string (represented by the <tt class="computeroutput"><span class="identifier">_1</span></tt>
+ its value. The semantic action attached to <code class="computeroutput"><span class="identifier">tok</span><span class="special">.</span><span class="identifier">word</span></code>
+ receives this string (represented by the <code class="computeroutput"><span class="identifier">_1</span></code>
           placeholder) and uses it to calculate the number of matched characters:
- <tt class="computeroutput"><span class="identifier">ref</span><span class="special">(</span><span class="identifier">c</span><span class="special">)</span> <span class="special">+=</span>
- <span class="identifier">size</span><span class="special">(</span><span class="identifier">_1</span><span class="special">)</span></tt>.
+ <code class="computeroutput"><span class="identifier">ref</span><span class="special">(</span><span class="identifier">c</span><span class="special">)</span> <span class="special">+=</span>
+ <span class="identifier">size</span><span class="special">(</span><span class="identifier">_1</span><span class="special">)</span></code>.
         </p>
-<div class="important"><table border="0" summary="Important">
+<div class="important" title="Important"><table border="0" summary="Important">
 <tr>
 <td rowspan="2" align="center" valign="top" width="25"><img alt="[Important]" src="../../../images/important.png"></td>
 <th align="left">Important</th>
 </tr>
-<tr><td colspan="2" align="left" valign="top"><p>
- All placeholders (<tt class="computeroutput"><span class="identifier">_1</span></tt>,
- <tt class="computeroutput"><span class="identifier">_2</span></tt>, etc.) used in <span class="emphasis"><em>parser</em></span>
+<tr><td align="left" valign="top"><p>
+ All placeholders (<code class="computeroutput"><span class="identifier">_1</span></code>,
+ <code class="computeroutput"><span class="identifier">_2</span></code>, etc.) used in <span class="emphasis"><em>parser</em></span>
             semantic actions in conjunction with functors created based on Boost.Phoenix need to
- be imported from the <tt class="computeroutput"><span class="keyword">namespace</span>
- <span class="identifier">boost</span><span class="special">::</span><span class="identifier">spirit</span><span class="special">::</span><span class="identifier">arg_names</span></tt> (and <span class="bold"><b>not</b></span>
- <tt class="computeroutput"><span class="keyword">namespace</span> <span class="identifier">boost</span><span class="special">::</span><span class="identifier">phoenix</span><span class="special">::</span><span class="identifier">arg_names</span></tt>,
+ be imported from the <code class="computeroutput"><span class="keyword">namespace</span>
+ <span class="identifier">boost</span><span class="special">::</span><span class="identifier">spirit</span><span class="special">::</span><span class="identifier">arg_names</span></code> (and <span class="bold"><strong>not</strong></span>
+ <code class="computeroutput"><span class="keyword">namespace</span> <span class="identifier">boost</span><span class="special">::</span><span class="identifier">phoenix</span><span class="special">::</span><span class="identifier">arg_names</span></code>,
             which is different from using placeholders in <span class="emphasis"><em>Spirit.Lex</em></span>).
             Using the wrong placeholders leads to subtle compilation errors which
             are difficult to backtrack to their cause.
           </p></td></tr>
 </table></div>
-<a name="spirit.lex.tutorials.lexer_quickstart3.pulling_everything_together"></a><h5>
-<a name="id491919"></a>
- <a href="lexer_quickstart3.html#spirit.lex.tutorials.lexer_quickstart3.pulling_everything_together">Pulling
+<a name="spirit.lex.tutorials.lexer_quickstart3.pulling_everything_together"></a><h6>
+<a name="id1104365"></a>
+ <a class="link" href="lexer_quickstart3.html#spirit.lex.tutorials.lexer_quickstart3.pulling_everything_together">Pulling
           Everything Together</a>
- </h5>
+ </h6>
 <p>
           The main function needs to implement a bit more logic now as we have to
           initialize and start not only the lexical analysis but the parsing process
- as well. The three type definitions (<tt class="computeroutput"><span class="keyword">typedef</span></tt>
+ as well. The three type definitions (<code class="computeroutput"><span class="keyword">typedef</span></code>
           statements) simplify the creation of the lexical analyzer and the grammar.
           After reading the contents of the given file into memory it calls the function
- tokenize_and_parse()
+ <a class="link" href="../../../"><code class="computeroutput"><span class="identifier">tokenize_and_parse</span><span class="special">()</span></code></a>
           to initialize the lexical analysis and parsing processes.
         </p>
 <p>
@@ -355,13 +359,13 @@
 </p>
 <pre class="programlisting"><span class="keyword">int</span> <span class="identifier">main</span><span class="special">(</span><span class="keyword">int</span> <span class="identifier">argc</span><span class="special">,</span> <span class="keyword">char</span><span class="special">*</span> <span class="identifier">argv</span><span class="special">[])</span>
 <span class="special">{</span>
-<span class="callout_bug"><a name="spirit14co" href="lexer_quickstart3.html#spirit14"><img src="../../../../../../../doc/src/images/callouts/1.png" alt="1" border="0"></a></span> <span class="keyword">typedef</span> <span class="identifier">lexertl</span><span class="special">::</span><span class="identifier">token</span><span class="special">&lt;</span>
+<span class="callout_bug"><a class="co" name="spirit14co" href="lexer_quickstart3.html#spirit14"><img src="../../../../../../../doc/src/images/callouts/1.png" alt="1" border="0"></a></span> <span class="keyword">typedef</span> <span class="identifier">lexertl</span><span class="special">::</span><span class="identifier">token</span><span class="special">&lt;</span>
         <span class="keyword">char</span> <span class="keyword">const</span><span class="special">*,</span> <span class="identifier">boost</span><span class="special">::</span><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">vector</span><span class="special">&lt;</span><span class="identifier">std</span><span class="special">::</span><span class="identifier">string</span><span class="special">&gt;</span>
     <span class="special">&gt;</span> <span class="identifier">token_type</span><span class="special">;</span>
 
-<span class="callout_bug"><a name="spirit15co" href="lexer_quickstart3.html#spirit15"><img src="../../../../../../../doc/src/images/callouts/2.png" alt="2" border="0"></a></span> <span class="keyword">typedef</span> <span class="identifier">lexertl</span><span class="special">::</span><span class="identifier">lexer</span><span class="special">&lt;</span><span class="identifier">token_type</span><span class="special">&gt;</span> <span class="identifier">lexer_type</span><span class="special">;</span>
+<span class="callout_bug"><a class="co" name="spirit15co" href="lexer_quickstart3.html#spirit15"><img src="../../../../../../../doc/src/images/callouts/2.png" alt="2" border="0"></a></span> <span class="keyword">typedef</span> <span class="identifier">lexertl</span><span class="special">::</span><span class="identifier">lexer</span><span class="special">&lt;</span><span class="identifier">token_type</span><span class="special">&gt;</span> <span class="identifier">lexer_type</span><span class="special">;</span>
 
-<span class="callout_bug"><a name="spirit16co" href="lexer_quickstart3.html#spirit16"><img src="../../../../../../../doc/src/images/callouts/3.png" alt="3" border="0"></a></span> <span class="keyword">typedef</span> <span class="identifier">word_count_tokens</span><span class="special">&lt;</span><span class="identifier">lexer_type</span><span class="special">&gt;::</span><span class="identifier">iterator_type</span> <span class="identifier">iterator_type</span><span class="special">;</span>
+<span class="callout_bug"><a class="co" name="spirit16co" href="lexer_quickstart3.html#spirit16"><img src="../../../../../../../doc/src/images/callouts/3.png" alt="3" border="0"></a></span> <span class="keyword">typedef</span> <span class="identifier">word_count_tokens</span><span class="special">&lt;</span><span class="identifier">lexer_type</span><span class="special">&gt;::</span><span class="identifier">iterator_type</span> <span class="identifier">iterator_type</span><span class="special">;</span>
 
     <span class="comment">// now we use the types defined above to create the lexer and grammar
 </span> <span class="comment">// object instances needed to invoke the parsing process
@@ -373,7 +377,7 @@
     <span class="keyword">char</span> <span class="keyword">const</span><span class="special">*</span> <span class="identifier">first</span> <span class="special">=</span> <span class="identifier">str</span><span class="special">.</span><span class="identifier">c_str</span><span class="special">();</span>
     <span class="keyword">char</span> <span class="keyword">const</span><span class="special">*</span> <span class="identifier">last</span> <span class="special">=</span> <span class="special">&amp;</span><span class="identifier">first</span><span class="special">[</span><span class="identifier">str</span><span class="special">.</span><span class="identifier">size</span><span class="special">()];</span>
 
-<span class="callout_bug"><a name="spirit17co" href="lexer_quickstart3.html#spirit17"><img src="../../../../../../../doc/src/images/callouts/4.png" alt="4" border="0"></a></span> <span class="keyword">bool</span> <span class="identifier">r</span> <span class="special">=</span> <span class="identifier">tokenize_and_parse</span><span class="special">(</span><span class="identifier">first</span><span class="special">,</span> <span class="identifier">last</span><span class="special">,</span> <span class="identifier">word_count</span><span class="special">,</span> <span class="identifier">g</span><span class="special">);</span>
+<span class="callout_bug"><a class="co" name="spirit17co" href="lexer_quickstart3.html#spirit17"><img src="../../../../../../../doc/src/images/callouts/4.png" alt="4" border="0"></a></span> <span class="keyword">bool</span> <span class="identifier">r</span> <span class="special">=</span> <span class="identifier">tokenize_and_parse</span><span class="special">(</span><span class="identifier">first</span><span class="special">,</span> <span class="identifier">last</span><span class="special">,</span> <span class="identifier">word_count</span><span class="special">,</span> <span class="identifier">g</span><span class="special">);</span>
 
     <span class="keyword">if</span> <span class="special">(</span><span class="identifier">r</span><span class="special">)</span> <span class="special">{</span>
         <span class="identifier">std</span><span class="special">::</span><span class="identifier">cout</span> <span class="special">&lt;&lt;</span> <span class="string">"lines: "</span> <span class="special">&lt;&lt;</span> <span class="identifier">g</span><span class="special">.</span><span class="identifier">l</span> <span class="special">&lt;&lt;</span> <span class="string">", words: "</span> <span class="special">&lt;&lt;</span> <span class="identifier">g</span><span class="special">.</span><span class="identifier">w</span>
@@ -395,29 +399,25 @@
             </p>
 <div class="calloutlist"><table border="0" summary="Callout list">
 <tr>
-<td width="5%" valign="top" align="left">
-<a name="spirit14"></a>1 </td>
-<td valign="top" align="left"><p> Define the token type to be used: <tt class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">string</span></tt>
+<td width="5%" valign="top" align="left"><p><a name="spirit14"></a>1 </p></td>
+<td valign="top" align="left"><p> Define the token type to be used: <code class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">string</span></code>
             is available as the type of the token attribute </p></td>
 </tr>
 <tr>
-<td width="5%" valign="top" align="left">
-<a name="spirit15"></a>2 </td>
+<td width="5%" valign="top" align="left"><p><a name="spirit15"></a>2 </p></td>
 <td valign="top" align="left"><p> Define the lexer type
             to use implementing the state machine </p></td>
 </tr>
 <tr>
-<td width="5%" valign="top" align="left">
-<a name="spirit16"></a>3 </td>
+<td width="5%" valign="top" align="left"><p><a name="spirit16"></a>3 </p></td>
 <td valign="top" align="left"><p> Define the iterator type exposed
             by the lexer type </p></td>
 </tr>
 <tr>
-<td width="5%" valign="top" align="left">
-<a name="spirit17"></a>4 </td>
+<td width="5%" valign="top" align="left"><p><a name="spirit17"></a>4 </p></td>
 <td valign="top" align="left"><p> Parsing is done based on the the token stream, not
- the character stream read from the input. The function <tt class="computeroutput"><span class="identifier">tokenize_and_parse</span><span class="special">()</span></tt>
- wraps the passed iterator range <tt class="computeroutput"><span class="special">[</span><span class="identifier">first</span><span class="special">,</span> <span class="identifier">last</span><span class="special">)</span></tt>
+ the character stream read from the input. The function <code class="computeroutput"><span class="identifier">tokenize_and_parse</span><span class="special">()</span></code>
+ wraps the passed iterator range <code class="computeroutput"><span class="special">[</span><span class="identifier">first</span><span class="special">,</span> <span class="identifier">last</span><span class="special">)</span></code>
             by the lexical analyzer and uses its exposed iterators to parse the toke
             stream. </p></td>
 </tr>

Modified: trunk/libs/spirit/doc/html/spirit/lex/tutorials/lexer_tutorials.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/lex/tutorials/lexer_tutorials.html (original)
+++ trunk/libs/spirit/doc/html/spirit/lex/tutorials/lexer_tutorials.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -1,17 +1,13 @@
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title> Spirit.Lex
- Tutorials Overview</title>
+<title>Spirit.Lex Tutorials Overview</title>
 <link rel="stylesheet" href="../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../index.html" title="Spirit 2.1">
-<link rel="up" href="../tutorials.html" title=" Spirit.Lex
- Tutorials">
-<link rel="previous" href="../tutorials.html" title=" Spirit.Lex
- Tutorials">
-<link rel="next" href="lexer_quickstart1.html" title=" Quickstart
- 1 - A word counter using Spirit.Lex">
+<link rel="up" href="../tutorials.html" title="Spirit.Lex Tutorials">
+<link rel="prev" href="../tutorials.html" title="Spirit.Lex Tutorials">
+<link rel="next" href="lexer_quickstart1.html" title="Quickstart 1 - A word counter using Spirit.Lex">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
 <table cellpadding="2" width="100%"><tr>
@@ -26,15 +22,11 @@
 <div class="spirit-nav">
 <a accesskey="p" href="../tutorials.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../tutorials.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="lexer_quickstart1.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h4 class="title">
-<a name="spirit.lex.tutorials.lexer_tutorials"></a><a href="lexer_tutorials.html" title=" Spirit.Lex
- Tutorials Overview"> <span class="emphasis"><em>Spirit.Lex</em></span>
+<div class="section" title="Spirit.Lex Tutorials Overview">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="spirit.lex.tutorials.lexer_tutorials"></a><a class="link" href="lexer_tutorials.html" title="Spirit.Lex Tutorials Overview"> <span class="emphasis"><em>Spirit.Lex</em></span>
         Tutorials Overview</a>
-</h4></div></div>
-<div></div>
-</div>
+</h4></div></div></div>
 <p>
           The <span class="emphasis"><em>Spirit.Lex</em></span> library implements several components
           on top of possibly different lexer generator libraries. It exposes a pair
@@ -53,12 +45,12 @@
           generator library, all what needs to be implemented is a set of wrapper
           objects exposing a well defined interface as described in this documentation.
         </p>
-<div class="note"><table border="0" summary="Note">
+<div class="note" title="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>
 </tr>
-<tr><td colspan="2" align="left" valign="top"><p>
+<tr><td align="left" valign="top"><p>
             For the sake of clarity all examples in this documentation assume <span class="emphasis"><em>Spirit.Lex</em></span>
             to be used on top of Lexertl.
           </p></td></tr>
@@ -71,23 +63,23 @@
           Here is a (non-complete) list of features you can tweak to adjust the generated
           lexer instance to the actual needs:
         </p>
-<div class="itemizedlist"><ul type="disc">
-<li>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem">
             Select and customize the token type to be generated by the lexer instance.
           </li>
-<li>
+<li class="listitem">
             Select and customize the token value types the generated token instances
             will be able to hold.
           </li>
-<li>
+<li class="listitem">
             Select the iterator type of the underlying input stream, which will be
             used as the source for the character stream to tokenize.
           </li>
-<li>
+<li class="listitem">
             Customize the iterator type returned by the lexer to enable debug support,
             special handling of certain input sequences, etc.
           </li>
-<li>
+<li class="listitem">
             Select the <span class="emphasis"><em>dynamic</em></span> or the <span class="emphasis"><em>static</em></span>
             runtime model for the lexical analyzer.
           </li>
@@ -100,19 +92,16 @@
 <p>
           The series of tutorial examples of this section will guide you through
           some common use cases helping to understand the big picture. The first
- two quick start examples (<a href="lexer_quickstart1.html" title=" Quickstart
- 1 - A word counter using Spirit.Lex">Lex
+ two quick start examples (<a class="link" href="lexer_quickstart1.html" title="Quickstart 1 - A word counter using Spirit.Lex">Lex
           Quickstart 1 - A word counter using <span class="emphasis"><em>Spirit.Lex</em></span></a>
- and <a href="lexer_quickstart2.html" title=" Quickstart
- 2 - A better word counter using Spirit.Lex">Lex Quickstart
+ and <a class="link" href="lexer_quickstart2.html" title="Quickstart 2 - A better word counter using Spirit.Lex">Lex Quickstart
           2 - A better word counter using <span class="emphasis"><em>Spirit.Lex</em></span></a>)
           introduce the <span class="emphasis"><em>Spirit.Lex</em></span> library while building two
           standalone applications, not being connected to or depending on any other
           part of Spirit. The
- section <a href="lexer_quickstart3.html" title=" Quickstart
- 3 - Counting Words Using a Parser">Lex Quickstart
+ section <a class="link" href="lexer_quickstart3.html" title="Quickstart 3 - Counting Words Using a Parser">Lex Quickstart
           3 - Counting Words Using a Parser</a> demonstrates how to use a lexer
- in conjunction with a parser (where certainly the parser is built using
+ in conjunction with a parser (where obviously the parser is built using
           <span class="emphasis"><em>Spirit.Qi</em></span>).
         </p>
 </div>

Modified: trunk/libs/spirit/doc/html/spirit/notes.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/notes.html (original)
+++ trunk/libs/spirit/doc/html/spirit/notes.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -3,10 +3,10 @@
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <title>Notes</title>
 <link rel="stylesheet" href="../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../index.html" title="Spirit 2.1">
 <link rel="up" href="../index.html" title="Spirit 2.1">
-<link rel="previous" href="faq.html" title=" Spirit FAQ">
+<link rel="prev" href="faq.html" title="Spirit FAQ">
 <link rel="next" href="notes/style_guide.html" title="Style Guide">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -22,13 +22,10 @@
 <div class="spirit-nav">
 <a accesskey="p" href="faq.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="notes/style_guide.html"><img src="../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h2 class="title" style="clear: both">
-<a name="spirit.notes"></a>Notes
-</h2></div></div>
-<div></div>
-</div>
+<div class="section" title="Notes">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="spirit.notes"></a><a class="link" href="notes.html" title="Notes">Notes</a>
+</h2></div></div></div>
 <div class="toc"><dl><dt><span class="section">Style Guide</span></dt></dl></div>
 </div>
 <table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>

Modified: trunk/libs/spirit/doc/html/spirit/notes/style_guide.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/notes/style_guide.html (original)
+++ trunk/libs/spirit/doc/html/spirit/notes/style_guide.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -3,10 +3,10 @@
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <title>Style Guide</title>
 <link rel="stylesheet" href="../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../index.html" title="Spirit 2.1">
 <link rel="up" href="../notes.html" title="Notes">
-<link rel="previous" href="../notes.html" title="Notes">
+<link rel="prev" href="../notes.html" title="Notes">
 <link rel="next" href="../acknowledgments.html" title="Acknowledgments">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -22,13 +22,10 @@
 <div class="spirit-nav">
 <a accesskey="p" href="../notes.html"><img src="../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../notes.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="../acknowledgments.html"><img src="../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h3 class="title">
-<a name="spirit.notes.style_guide"></a>Style Guide
-</h3></div></div>
-<div></div>
-</div>
+<div class="section" title="Style Guide">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="spirit.notes.style_guide"></a><a class="link" href="style_guide.html" title="Style Guide">Style Guide</a>
+</h3></div></div></div>
 <p>
         At some point, especially when there are lots of semantic actions attached
         to various points, the grammar tends to be quite difficult to follow. In
@@ -41,22 +38,22 @@
         Requirements and Guidelines</a> and is the combined work of Joel de Guzman,
         Chris Uzdavinis, and Hartmut Kaiser.
       </p>
-<div class="itemizedlist"><ul type="disc">
-<li>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem">
           Rule names use std C++ (Boost) convention. The rule name may be very long.
         </li>
-<li>
+<li class="listitem">
           The '=' is neatly indented 4 spaces below. Like in Boost, use spaces instead
           of tabs.
         </li>
-<li>
+<li class="listitem">
           Breaking the operands into separate lines puts the semantic actions neatly
           to the right.
         </li>
-<li>
+<li class="listitem">
           Semicolon at the last line terminates the rule.
         </li>
-<li>
+<li class="listitem">
           The adjacent parts of a sequence should be indented accordingly to have
           all, what belongs to one level, at one indentation level.
         </li>
@@ -69,20 +66,20 @@
         <span class="special">&gt;&gt;</span> <span class="identifier">etc</span>
     <span class="special">;</span>
 </pre>
-<div class="itemizedlist"><ul type="disc">
-<li>
- Prefer literals in the grammar instead of identifiers. e.g. <tt class="computeroutput"><span class="string">"program"</span></tt> instead of <tt class="computeroutput"><span class="identifier">PROGRAM</span></tt>, <tt class="computeroutput"><span class="char">'&gt;='</span></tt>
- instead of <tt class="computeroutput"><span class="identifier">GTE</span></tt> and <tt class="computeroutput"><span class="char">'.'</span></tt> instead of <tt class="computeroutput"><span class="identifier">DOT</span></tt>.
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem">
+ Prefer literals in the grammar instead of identifiers. e.g. <code class="computeroutput"><span class="string">"program"</span></code> instead of <code class="computeroutput"><span class="identifier">PROGRAM</span></code>, <code class="computeroutput"><span class="char">'&gt;='</span></code>
+ instead of <code class="computeroutput"><span class="identifier">GTE</span></code> and <code class="computeroutput"><span class="char">'.'</span></code> instead of <code class="computeroutput"><span class="identifier">DOT</span></code>.
           This makes it much easier to read. If this isn't possible (for instance
           where the used tokens must be identified through integers) capitalized
           identifiers should be used instead.
         </li>
-<li>
- Breaking the operands may not be needed for short expressions. e.g. <tt class="computeroutput"><span class="special">*(</span><span class="char">','</span> <span class="special">&gt;&gt;</span>
- <span class="identifier">file_identifier</span><span class="special">)</span></tt>
+<li class="listitem">
+ Breaking the operands may not be needed for short expressions. e.g. <code class="computeroutput"><span class="special">*(</span><span class="char">','</span> <span class="special">&gt;&gt;</span>
+ <span class="identifier">file_identifier</span><span class="special">)</span></code>
           as long as the line does not exceed 80 characters.
         </li>
-<li>
+<li class="listitem">
           If a sequence fits on one line, put spaces inside the parentheses to clearly
           separate them from the rules.
         </li>
@@ -97,7 +94,7 @@
         <span class="special">&gt;&gt;</span> <span class="char">';'</span>
     <span class="special">;</span>
 </pre>
-<div class="itemizedlist"><ul type="disc"><li>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">
           Nesting directives: If a rule does not fit on one line (80 characters)
           it should be continued on the next line intended by one level. The brackets
           of directives, semantic expressions (using Phoenix or LL lambda expressions)
@@ -113,9 +110,9 @@
         <span class="special">]</span>
    <span class="special">;</span>
 </pre>
-<div class="itemizedlist"><ul type="disc"><li>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">
           Nesting unary operators (e.g.Kleene star): Unary rule operators (Kleene
- star, <tt class="computeroutput"><span class="char">'!'</span></tt>, <tt class="computeroutput"><span class="char">'+'</span></tt>
+ star, <code class="computeroutput"><span class="char">'!'</span></code>, <code class="computeroutput"><span class="char">'+'</span></code>
           etc.) should be moved out one space before the corresponding indentation
           level, if this rule has a body or a sequence after it, which does not fit
           on on line. This makes the formatting more consistent and moves the rule

Modified: trunk/libs/spirit/doc/html/spirit/preface.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/preface.html (original)
+++ trunk/libs/spirit/doc/html/spirit/preface.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -3,10 +3,10 @@
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <title>Preface</title>
 <link rel="stylesheet" href="../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../index.html" title="Spirit 2.1">
 <link rel="up" href="../index.html" title="Spirit 2.1">
-<link rel="previous" href="../index.html" title="Spirit 2.1">
+<link rel="prev" href="../index.html" title="Spirit 2.1">
 <link rel="next" href="what_s_new.html" title="What's New">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -22,35 +22,32 @@
 <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="what_s_new.html"><img src="../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h2 class="title" style="clear: both">
-<a name="spirit.preface"></a>Preface
-</h2></div></div>
-<div></div>
-</div>
+<div class="section" title="Preface">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="spirit.preface"></a><a class="link" href="preface.html" title="Preface">Preface</a>
+</h2></div></div></div>
 <div class="blockquote"><blockquote class="blockquote">
 <p>
         </p>
 <p>
- <span class="emphasis"><em>&#8220;<span class="quote">Examples of designs that meet most of the criteria for
+ <span class="emphasis"><em><span class="quote">&#8220;<span class="quote">Examples of designs that meet most of the criteria for
           "goodness" (easy to understand, flexible, efficient) are a recursive-descent
           parser, which is traditional procedural code. Another example is the STL,
           which is a generic library of containers and algorithms depending crucially
- on both traditional procedural code and on parametric polymorphism.</span>&#8221;</em></span>
- <span class="bold"><b>--Bjarne Stroustrup</b></span>
+ on both traditional procedural code and on parametric polymorphism.</span>&#8221;</span></em></span>
+ <span class="bold"><strong>--Bjarne Stroustrup</strong></span>
         </p>
 <p>
       </p>
 </blockquote></div>
-<a name="spirit.preface.history"></a><h3>
-<a name="id355315"></a>
- History
- </h3>
-<a name="spirit.preface._emphasis_80s__emphasis_"></a><h3>
-<a name="id355328"></a>
- 80s
- </h3>
+<a name="spirit.preface.history"></a><h4>
+<a name="id1017731"></a>
+ <a class="link" href="preface.html#spirit.preface.history">History</a>
+ </h4>
+<a name="spirit.preface._emphasis_80s__emphasis_"></a><h4>
+<a name="id1017744"></a>
+ <a class="link" href="preface.html#spirit.preface._emphasis_80s__emphasis_"><span class="emphasis"><em>80s</em></span></a>
+ </h4>
 <p>
       In the mid-80s, Joel wrote his first calculator in Pascal. It was an unforgettable
       coding experience. He was amazed at how a mutually recursive set of functions
@@ -61,10 +58,10 @@
       a grammar using Pascal-like syntax diagrams and then a corresponding recursive-descent
       parser. This worked very well.
     </p>
-<a name="spirit.preface._emphasis_90s__emphasis_"></a><h3>
-<a name="id353707"></a>
- 90s
- </h3>
+<a name="spirit.preface._emphasis_90s__emphasis_"></a><h4>
+<a name="id1017762"></a>
+ <a class="link" href="preface.html#spirit.preface._emphasis_90s__emphasis_"><span class="emphasis"><em>90s</em></span></a>
+ </h4>
 <p>
       The arrival of the Internet and the World Wide Web magnified this thousand-fold.
       At one point Joel had to write an HTML parser for a Web browser project. He
@@ -99,11 +96,11 @@
       objects and linking semantic actions on the fly. A very early text can be found
       here: pre-Spirit.
     </p>
-<a name="spirit.preface._emphasis_2001_to_2006__emphasis_"></a><h3>
-<a name="id353793"></a>
- <a href="preface.html#spirit.preface._emphasis_2001_to_2006__emphasis_"><span class="emphasis"><em>2001
+<a name="spirit.preface._emphasis_2001_to_2006__emphasis_"></a><h4>
+<a name="id1017804"></a>
+ <a class="link" href="preface.html#spirit.preface._emphasis_2001_to_2006__emphasis_"><span class="emphasis"><em>2001
       to 2006</em></span></a>
- </h3>
+ </h4>
 <p>
       Version 1.0 to 1.8 was a complete rewrite of the original Spirit parser using
       expression templates and static polymorphism, inspired by the works of Todd
@@ -129,13 +126,13 @@
       of domains. The Boost Libraries have become widely known as an industry standard
       for design and implementation quality, robustness, and reusability.
     </p>
-<a name="spirit.preface._emphasis_2007__emphasis_"></a><h3>
-<a name="id353842"></a>
- 2007
- </h3>
+<a name="spirit.preface._emphasis_2007__emphasis_"></a><h4>
+<a name="id1017839"></a>
+ <a class="link" href="preface.html#spirit.preface._emphasis_2007__emphasis_"><span class="emphasis"><em>2007</em></span></a>
+ </h4>
 <p>
       Over the years, especially after Spirit was accepted into Boost, Spirit has
- served its purpose quite admirably. The focus of what we'll now call <span class="bold"><b><span class="emphasis"><em>Classic-Spirit</em></span></b></span> (versions prior
+ served its purpose quite admirably. The focus of what we'll now call <span class="bold"><strong><span class="emphasis"><em>Classic-Spirit</em></span></strong></span> (versions prior
       to 2.0) was on transduction parsing where the input string is merely translated
       to an output string. A lot of parsers are of the transduction type. When the
       time came to add attributes to the parser library, it was done in a rather
@@ -166,10 +163,10 @@
       its modularity and extensibility. Instead of giving you a sledgehammer, it
       gives you the right ingredients to create a sledgehammer easily.
     </p>
-<a name="spirit.preface.new_ideas__spirit_v2"></a><h3>
-<a name="id355493"></a>
- New Ideas: Spirit V2
- </h3>
+<a name="spirit.preface.new_ideas__spirit_v2"></a><h4>
+<a name="id1017915"></a>
+ <a class="link" href="preface.html#spirit.preface.new_ideas__spirit_v2">New Ideas: Spirit V2</a>
+ </h4>
 <p>
       Just before the development of Spirit V2 began, Hartmut came across the StringTemplate library which is
       a part of the ANTLR parser framework. It is a Java template engine (with ports
@@ -204,27 +201,27 @@
       parser grammars. Again, Spirit's modular structure allowed us to reuse the
       same underlying component library as for the parser and generator libraries.
     </p>
-<a name="spirit.preface.how_to_use_this_manual"></a><h3>
-<a name="id355575"></a>
- How to use this manual
- </h3>
+<a name="spirit.preface.how_to_use_this_manual"></a><h4>
+<a name="id1017965"></a>
+ <a class="link" href="preface.html#spirit.preface.how_to_use_this_manual">How to use this manual</a>
+ </h4>
 <p>
- Each major section (there are 3: Qi, Karma, and Lex)
+ Each major section (there are 3: <a class="link" href="qi.html" title="Qi">Qi</a>, <a class="link" href="karma.html" title="Karma">Karma</a>, and <a class="link" href="lex.html" title="Spirit.Lex">Lex</a>)
       is roughly divided into 3 parts:
     </p>
-<div class="orderedlist"><ol type="1">
-<li>
+<div class="orderedlist"><ol class="orderedlist" type="1">
+<li class="listitem">
         Tutorials: A step by step guide with heavily annotated code. These are meant
         to get the user acquainted with the library as quickly as possible. The objective
         is to build the confidence of the user in using the library through abundant
         examples and detailed instructions. Examples speak volumes and we have volumes
         of examples!
       </li>
-<li>
+<li class="listitem">
         Abstracts: A high level summary of key topics. The objective is to give the
         user a high level view of the library, the key concepts, background and theories.
       </li>
-<li>
+<li class="listitem">
         Reference: Detailed formal technical reference. We start with a quick reference
         -- an easy to use table that maps into the reference proper. The reference
         proper starts with C++ Concepts
@@ -236,94 +233,130 @@
       icons precede some text to indicate:
     </p>
 <div class="table">
-<a name="id355647"></a><p class="title"><b>Table 1. Icons</b></p>
-<table class="table" summary="Icons">
+<a name="id1018018"></a><p class="title"><b>Table 1. Icons</b></p>
+<div class="table-contents"><table class="table" summary="Icons">
 <colgroup>
 <col>
 <col>
 <col>
 </colgroup>
 <thead><tr>
-<th><p>
+<th>
+ <p>
             Icon
- </p></th>
-<th><p>
+ </p>
+ </th>
+<th>
+ <p>
             Name
- </p></th>
-<th><p>
+ </p>
+ </th>
+<th>
+ <p>
             Meaning
- </p></th>
+ </p>
+ </th>
 </tr></thead>
 <tbody>
 <tr>
-<td><p>
- <span class="inlinemediaobject"><img src="images/note.png" alt="note"></span>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <span class="inlinemediaobject"><img src="../images/note.png" alt="note"></span>
+ </p>
+ </td>
+<td>
+ <p>
             Note
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
             Generally useful information (an aside that doesn't fit in the flow of
             the text)
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <span class="inlinemediaobject"><img src="images/tip.png" alt="tip"></span>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <span class="inlinemediaobject"><img src="../images/tip.png" alt="tip"></span>
+ </p>
+ </td>
+<td>
+ <p>
             Tip
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
             Suggestion on how to do something (especially something that not be obvious)
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <span class="inlinemediaobject"><img src="images/important.png" alt="important"></span>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <span class="inlinemediaobject"><img src="../images/important.png" alt="important"></span>
+ </p>
+ </td>
+<td>
+ <p>
             Important
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
             Important note on something to take particular notice of
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <span class="inlinemediaobject"><img src="images/caution.png" alt="caution"></span>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <span class="inlinemediaobject"><img src="../images/caution.png" alt="caution"></span>
+ </p>
+ </td>
+<td>
+ <p>
             Caution
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
             Take special care with this - it may not be what you expect and may cause
             bad results
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <span class="inlinemediaobject"><img src="images/alert.png" alt="alert"></span>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <span class="inlinemediaobject"><img src="../images/alert.png" alt="alert"></span>
+ </p>
+ </td>
+<td>
+ <p>
             Danger
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
             This is likely to cause serious trouble if ignored
- </p></td>
+ </p>
+ </td>
 </tr>
 </tbody>
-</table>
+</table></div>
 </div>
-<p>
+<br class="table-break"><p>
       This documentation is automatically generated by Boost QuickBook documentation
       tool. QuickBook can be found in the <a href="http://www.boost.org/tools/index.html" target="_top">Boost
       Tools</a>.
     </p>
-<a name="spirit.preface.support"></a><h3>
-<a name="id353382"></a>
- Support
- </h3>
+<a name="spirit.preface.support"></a><h4>
+<a name="id1018259"></a>
+ <a class="link" href="preface.html#spirit.preface.support">Support</a>
+ </h4>
 <p>
       Please direct all questions to Spirit's mailing list. You can subscribe to
       the <a href="http://www.nabble.com/The-Spirit-Parser-Library-f3430.html" target="_top">Spirit

Modified: trunk/libs/spirit/doc/html/spirit/qi.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/qi.html (original)
+++ trunk/libs/spirit/doc/html/spirit/qi.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -1,13 +1,12 @@
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title> Qi</title>
+<title>Qi</title>
 <link rel="stylesheet" href="../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../index.html" title="Spirit 2.1">
 <link rel="up" href="../index.html" title="Spirit 2.1">
-<link rel="previous" href="abstracts/parsing_expression_grammar.html" title="Parsing
- Expression Grammar">
+<link rel="prev" href="abstracts/parsing_expression_grammar.html" title="Parsing Expression Grammar">
 <link rel="next" href="qi/tutorials.html" title="Tutorials">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -23,13 +22,10 @@
 <div class="spirit-nav">
 <a accesskey="p" href="abstracts/parsing_expression_grammar.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/tutorials.html"><img src="../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h2 class="title" style="clear: both">
-<a name="spirit.qi"></a> Qi
-</h2></div></div>
-<div></div>
-</div>
+<div class="section" title="Qi">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="spirit.qi"></a><a class="link" href="qi.html" title="Qi"> Qi</a>
+</h2></div></div></div>
 <div class="toc"><dl>
 <dt><span class="section">Tutorials</span></dt>
 <dd><dl>
@@ -69,7 +65,12 @@
 <dd><dl>
 <dt><span class="section">Parser Concepts</span></dt>
 <dt><span class="section">Basics</span></dt>
-<dt><span class="section">String</span></dt>
+<dt><span class="section">char_</span></dt>
+</dl></dd>
+<dt><span class="section">String</span></dt>
+<dd><dl>
+<dt><span class="section">lit/string</span></dt>
+<dt><span class="section">symbols</span></dt>
 </dl></dd>
 </dl></div>
 </div>

Modified: trunk/libs/spirit/doc/html/spirit/qi/quick_reference.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/qi/quick_reference.html (original)
+++ trunk/libs/spirit/doc/html/spirit/qi/quick_reference.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -3,11 +3,10 @@
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <title>Quick Reference</title>
 <link rel="stylesheet" href="../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../index.html" title="Spirit 2.1">
-<link rel="up" href="../qi.html" title=" Qi">
-<link rel="previous" href="tutorials/mini_xml___error_handling.html" title="Mini
- XML - Error Handling">
+<link rel="up" href="../qi.html" title="Qi">
+<link rel="prev" href="tutorials/mini_xml___error_handling.html" title="Mini XML - Error Handling">
 <link rel="next" href="quick_reference/common_notation.html" title="Common Notation">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -23,13 +22,10 @@
 <div class="spirit-nav">
 <a accesskey="p" href="tutorials/mini_xml___error_handling.html"><img src="../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../qi.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="quick_reference/common_notation.html"><img src="../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h3 class="title">
-<a name="spirit.qi.quick_reference"></a>Quick Reference
-</h3></div></div>
-<div></div>
-</div>
+<div class="section" title="Quick Reference">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="spirit.qi.quick_reference"></a><a class="link" href="quick_reference.html" title="Quick Reference">Quick Reference</a>
+</h3></div></div></div>
 <div class="toc"><dl>
 <dt><span class="section">Common Notation</span></dt>
 <dt><span class="section"><a href="quick_reference/predefined_primitive_parsers.html">Predefined

Modified: trunk/libs/spirit/doc/html/spirit/qi/quick_reference/common_notation.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/qi/quick_reference/common_notation.html (original)
+++ trunk/libs/spirit/doc/html/spirit/qi/quick_reference/common_notation.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -3,12 +3,11 @@
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <title>Common Notation</title>
 <link rel="stylesheet" href="../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../index.html" title="Spirit 2.1">
 <link rel="up" href="../quick_reference.html" title="Quick Reference">
-<link rel="previous" href="../quick_reference.html" title="Quick Reference">
-<link rel="next" href="predefined_primitive_parsers.html" title="Predefined
- Primitive Parsers">
+<link rel="prev" href="../quick_reference.html" title="Quick Reference">
+<link rel="next" href="predefined_primitive_parsers.html" title="Predefined Primitive Parsers">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
 <table cellpadding="2" width="100%"><tr>
@@ -23,110 +22,107 @@
 <div class="spirit-nav">
 <a accesskey="p" href="../quick_reference.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../quick_reference.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="predefined_primitive_parsers.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h4 class="title">
-<a name="spirit.qi.quick_reference.common_notation"></a>Common Notation
-</h4></div></div>
-<div></div>
-</div>
-<div class="variablelist">
+<div class="section" title="Common Notation">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="spirit.qi.quick_reference.common_notation"></a><a class="link" href="common_notation.html" title="Common Notation">Common Notation</a>
+</h4></div></div></div>
+<div class="variablelist" title="Notation">
 <p class="title"><b>Notation</b></p>
 <dl>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">P</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">P</span></code></span></dt>
 <dd><p>
               Parser type
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">p</span><span class="special">,</span> <span class="identifier">a</span><span class="special">,</span>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">p</span><span class="special">,</span> <span class="identifier">a</span><span class="special">,</span>
           <span class="identifier">b</span><span class="special">,</span>
- <span class="identifier">c</span></tt></span></dt>
+ <span class="identifier">c</span></code></span></dt>
 <dd><p>
               Parser objects
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">A</span><span class="special">,</span> <span class="identifier">B</span><span class="special">,</span>
- <span class="identifier">C</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">A</span><span class="special">,</span> <span class="identifier">B</span><span class="special">,</span>
+ <span class="identifier">C</span></code></span></dt>
 <dd><p>
               Attribute types of parsers A, B and C
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">I</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">I</span></code></span></dt>
 <dd><p>
               The iterator type used for parsing
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">Unused</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">Unused</span></code></span></dt>
 <dd><p>
- An <tt class="computeroutput"><span class="identifier">unused_type</span></tt>
+ An <code class="computeroutput"><span class="identifier">unused_type</span></code>
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">Context</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">Context</span></code></span></dt>
 <dd><p>
- The enclosing rule's <tt class="computeroutput"><span class="identifier">Context</span></tt>
+ The enclosing rule's <code class="computeroutput"><span class="identifier">Context</span></code>
               type
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">Attr</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">Attr</span></code></span></dt>
 <dd><p>
               An attribute type
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">b</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">b</span></code></span></dt>
 <dd><p>
               A boolean expression
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">fp</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">fp</span></code></span></dt>
 <dd><p>
- A (lazy parser) function with signature <tt class="computeroutput"><span class="identifier">P</span><span class="special">(</span><span class="identifier">Unused</span><span class="special">,</span> <span class="identifier">Context</span><span class="special">)</span></tt>
+ A (lazy parser) function with signature <code class="computeroutput"><span class="identifier">P</span><span class="special">(</span><span class="identifier">Unused</span><span class="special">,</span> <span class="identifier">Context</span><span class="special">)</span></code>
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">fa</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">fa</span></code></span></dt>
 <dd><p>
- A (semantic action) function with signature <tt class="computeroutput"><span class="keyword">void</span><span class="special">(</span><span class="identifier">Attr</span><span class="special">,</span> <span class="identifier">Context</span><span class="special">,</span> <span class="keyword">bool</span><span class="special">&amp;)</span></tt>. The third parameter is a boolean
- flag that can be set to false to force the parse to fail. Both <tt class="computeroutput"><span class="identifier">Context</span></tt> and the boolean flag are
+ A (semantic action) function with signature <code class="computeroutput"><span class="keyword">void</span><span class="special">(</span><span class="identifier">Attr</span><span class="special">,</span> <span class="identifier">Context</span><span class="special">,</span> <span class="keyword">bool</span><span class="special">&amp;)</span></code>. The third parameter is a boolean
+ flag that can be set to false to force the parse to fail. Both <code class="computeroutput"><span class="identifier">Context</span></code> and the boolean flag are
               optional.
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">first</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">first</span></code></span></dt>
 <dd><p>
               An iterator pointing to the start of input
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">last</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">last</span></code></span></dt>
 <dd><p>
               An iterator pointing to the end of input
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">Ch</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">Ch</span></code></span></dt>
 <dd><p>
               Character-class specific character type (See __char_class<span class="underline">types</span>_)
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">ch</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">ch</span></code></span></dt>
 <dd><p>
               Character-class specific character (See __char_class<span class="underline">types</span>_)
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">ch2</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">ch2</span></code></span></dt>
 <dd><p>
               Character-class specific character (See __char_class<span class="underline">types</span>_)
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">chset</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">chset</span></code></span></dt>
 <dd><p>
               Character-set specifier string (example: "a-z0-9")
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">str</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">str</span></code></span></dt>
 <dd><p>
               Character-class specific string (See __char_class<span class="underline">types</span>_)
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">Str</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">Str</span></code></span></dt>
 <dd><p>
- Attribute of <tt class="computeroutput"><span class="identifier">str</span></tt>:
- <tt class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">basic_string</span><span class="special">&lt;</span><span class="identifier">T</span><span class="special">&gt;</span></tt>
- where <tt class="computeroutput"><span class="identifier">T</span></tt> is the underlying
- character type of <tt class="computeroutput"><span class="identifier">str</span></tt>
+ Attribute of <code class="computeroutput"><span class="identifier">str</span></code>:
+ <code class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">basic_string</span><span class="special">&lt;</span><span class="identifier">T</span><span class="special">&gt;</span></code>
+ where <code class="computeroutput"><span class="identifier">T</span></code> is the underlying
+ character type of <code class="computeroutput"><span class="identifier">str</span></code>
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">tuple</span><span class="special">&lt;&gt;</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">tuple</span><span class="special">&lt;&gt;</span></code></span></dt>
 <dd><p>
               Used as a placeholder for a fusion sequence
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">vector</span><span class="special">&lt;&gt;</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">vector</span><span class="special">&lt;&gt;</span></code></span></dt>
 <dd><p>
               Used as a placeholder for an STL container
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">variant</span><span class="special">&lt;&gt;</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">variant</span><span class="special">&lt;&gt;</span></code></span></dt>
 <dd><p>
               Used as a placeholder for a boost::variant
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">optional</span><span class="special">&lt;&gt;</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">optional</span><span class="special">&lt;&gt;</span></code></span></dt>
 <dd><p>
               Used as a placeholder for a boost::optional
             </p></dd>

Modified: trunk/libs/spirit/doc/html/spirit/qi/quick_reference/compound_attribute_rules.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/qi/quick_reference/compound_attribute_rules.html (original)
+++ trunk/libs/spirit/doc/html/spirit/qi/quick_reference/compound_attribute_rules.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -1,14 +1,12 @@
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title>Compound
- Attribute Rules</title>
+<title>Compound Attribute Rules</title>
 <link rel="stylesheet" href="../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../index.html" title="Spirit 2.1">
 <link rel="up" href="../quick_reference.html" title="Quick Reference">
-<link rel="previous" href="predefined_primitive_parsers.html" title="Predefined
- Primitive Parsers">
+<link rel="prev" href="predefined_primitive_parsers.html" title="Predefined Primitive Parsers">
 <link rel="next" href="non_terminals.html" title="Non-terminals">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -24,50 +22,52 @@
 <div class="spirit-nav">
 <a accesskey="p" href="predefined_primitive_parsers.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../quick_reference.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="non_terminals.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h4 class="title">
-<a name="spirit.qi.quick_reference.compound_attribute_rules"></a><a href="compound_attribute_rules.html" title="Compound
- Attribute Rules">Compound
+<div class="section" title="Compound Attribute Rules">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="spirit.qi.quick_reference.compound_attribute_rules"></a><a class="link" href="compound_attribute_rules.html" title="Compound Attribute Rules">Compound
         Attribute Rules</a>
-</h4></div></div>
-<div></div>
-</div>
+</h4></div></div></div>
 <p>
           The notation will be for instance:
         </p>
 <pre class="programlisting"><span class="identifier">a</span><span class="special">:</span> <span class="identifier">A</span><span class="special">,</span> <span class="identifier">b</span><span class="special">:</span> <span class="identifier">B</span> <span class="special">--&gt;</span> <span class="special">(</span><span class="identifier">a</span> <span class="special">&gt;&gt;</span> <span class="identifier">b</span><span class="special">):</span> <span class="identifier">tuple</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">,</span> <span class="identifier">B</span><span class="special">&gt;</span>
 </pre>
 <p>
- which reads as: given, <tt class="computeroutput"><span class="identifier">a</span></tt>
- and <tt class="computeroutput"><span class="identifier">b</span></tt> are parsers/generators,
- and <tt class="computeroutput"><span class="identifier">A</span></tt> is the type of the
- attribute of <tt class="computeroutput"><span class="identifier">a</span></tt>, and <tt class="computeroutput"><span class="identifier">B</span></tt> is the type of the attribute of <tt class="computeroutput"><span class="identifier">b</span></tt>, then the type of the attribute of
- <tt class="computeroutput"><span class="identifier">a</span> <span class="special">&gt;&gt;</span>
- <span class="identifier">b</span></tt> will be <tt class="computeroutput"><span class="identifier">tuple</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">,</span> <span class="identifier">B</span><span class="special">&gt;</span></tt>.
+ which reads as: given, <code class="computeroutput"><span class="identifier">a</span></code>
+ and <code class="computeroutput"><span class="identifier">b</span></code> are parsers/generators,
+ and <code class="computeroutput"><span class="identifier">A</span></code> is the type of the
+ attribute of <code class="computeroutput"><span class="identifier">a</span></code>, and <code class="computeroutput"><span class="identifier">B</span></code> is the type of the attribute of <code class="computeroutput"><span class="identifier">b</span></code>, then the type of the attribute of
+ <code class="computeroutput"><span class="identifier">a</span> <span class="special">&gt;&gt;</span>
+ <span class="identifier">b</span></code> will be <code class="computeroutput"><span class="identifier">tuple</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">,</span> <span class="identifier">B</span><span class="special">&gt;</span></code>.
         </p>
 <div class="table">
-<a name="id444381"></a><p class="title"><b>Table 4. compound parser attribute types</b></p>
-<table class="table" summary="compound parser attribute types">
+<a name="id1056330"></a><p class="title"><b>Table 4. compound parser attribute types</b></p>
+<div class="table-contents"><table class="table" summary="compound parser attribute types">
 <colgroup>
 <col>
 <col>
 </colgroup>
 <thead><tr>
-<th><p>
+<th>
+ <p>
                 Expression
- </p></th>
-<th><p>
+ </p>
+ </th>
+<th>
+ <p>
                 Attribute
- </p></th>
+ </p>
+ </th>
 </tr></thead>
 <tbody>
 <tr>
-<td><p>
- sequence (<tt class="computeroutput"><span class="special">&gt;&gt;</span></tt>)
- </p></td>
 <td>
-<p>
+ <p>
+ sequence (<code class="computeroutput"><span class="special">&gt;&gt;</span></code>)
+ </p>
+ </td>
+<td>
+ <p>
                 
 </p>
 <pre class="programlisting"><span class="identifier">a</span><span class="special">:</span> <span class="identifier">A</span><span class="special">,</span> <span class="identifier">b</span><span class="special">:</span> <span class="identifier">B</span> <span class="special">--&gt;</span> <span class="special">(</span><span class="identifier">a</span> <span class="special">&gt;&gt;</span> <span class="identifier">b</span><span class="special">):</span> <span class="identifier">tuple</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">,</span> <span class="identifier">B</span><span class="special">&gt;</span>
@@ -77,14 +77,16 @@
 <span class="identifier">a</span><span class="special">:</span> <span class="identifier">A</span><span class="special">,</span> <span class="identifier">b</span><span class="special">:</span> <span class="identifier">A</span> <span class="special">--&gt;</span> <span class="special">(</span><span class="identifier">a</span> <span class="special">&gt;&gt;</span> <span class="identifier">b</span><span class="special">):</span> <span class="identifier">vector</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">&gt;</span></pre>
 <p>
               </p>
-</td>
+ </td>
 </tr>
 <tr>
-<td><p>
- expect (<tt class="computeroutput"><span class="special">&gt;</span></tt>)
- </p></td>
 <td>
-<p>
+ <p>
+ expect (<code class="computeroutput"><span class="special">&gt;</span></code>)
+ </p>
+ </td>
+<td>
+ <p>
                 
 </p>
 <pre class="programlisting"><span class="identifier">a</span><span class="special">:</span> <span class="identifier">A</span><span class="special">,</span> <span class="identifier">b</span><span class="special">:</span> <span class="identifier">B</span> <span class="special">--&gt;</span> <span class="special">(</span><span class="identifier">a</span> <span class="special">&gt;</span> <span class="identifier">b</span><span class="special">):</span> <span class="identifier">tuple</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">,</span> <span class="identifier">B</span><span class="special">&gt;</span>
@@ -94,14 +96,16 @@
 <span class="identifier">a</span><span class="special">:</span> <span class="identifier">A</span><span class="special">,</span> <span class="identifier">b</span><span class="special">:</span> <span class="identifier">A</span> <span class="special">--&gt;</span> <span class="special">(</span><span class="identifier">a</span> <span class="special">&gt;</span> <span class="identifier">b</span><span class="special">):</span> <span class="identifier">vector</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">&gt;</span></pre>
 <p>
               </p>
-</td>
+ </td>
 </tr>
 <tr>
-<td><p>
- alternative (<tt class="computeroutput"><span class="special">|</span></tt>)
- </p></td>
 <td>
-<p>
+ <p>
+ alternative (<code class="computeroutput"><span class="special">|</span></code>)
+ </p>
+ </td>
+<td>
+ <p>
                 
 </p>
 <pre class="programlisting"><span class="identifier">a</span><span class="special">:</span> <span class="identifier">A</span><span class="special">,</span> <span class="identifier">b</span><span class="special">:</span> <span class="identifier">B</span> <span class="special">--&gt;</span> <span class="special">(</span><span class="identifier">a</span> <span class="special">|</span> <span class="identifier">b</span><span class="special">):</span> <span class="identifier">variant</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">,</span> <span class="identifier">B</span><span class="special">&gt;</span>
@@ -111,83 +115,97 @@
 <span class="identifier">a</span><span class="special">:</span> <span class="identifier">A</span><span class="special">,</span> <span class="identifier">b</span><span class="special">:</span> <span class="identifier">A</span> <span class="special">--&gt;</span> <span class="special">(</span><span class="identifier">a</span> <span class="special">|</span> <span class="identifier">b</span><span class="special">):</span> <span class="identifier">A</span></pre>
 <p>
               </p>
-</td>
+ </td>
 </tr>
 <tr>
-<td><p>
- difference (<tt class="computeroutput"><span class="special">-</span></tt>)
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">a</span><span class="special">:</span>
+<td>
+ <p>
+ difference (<code class="computeroutput"><span class="special">-</span></code>)
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">a</span><span class="special">:</span>
                 <span class="identifier">A</span><span class="special">,</span>
                 <span class="identifier">b</span><span class="special">:</span>
                 <span class="identifier">B</span> <span class="special">--&gt;</span>
                 <span class="special">(</span><span class="identifier">a</span>
- <span class="special">-</span> <span class="identifier">b</span><span class="special">):</span> <span class="identifier">A</span></tt>
- </p></td>
+ <span class="special">-</span> <span class="identifier">b</span><span class="special">):</span> <span class="identifier">A</span></code>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- kleene (<tt class="computeroutput"><span class="special">*</span></tt>)
- </p></td>
 <td>
-<p>
+ <p>
+ kleene (<code class="computeroutput"><span class="special">*</span></code>)
+ </p>
+ </td>
+<td>
+ <p>
                 
 </p>
 <pre class="programlisting"><span class="identifier">a</span><span class="special">:</span> <span class="identifier">A</span> <span class="special">--&gt;</span> <span class="special">*</span><span class="identifier">a</span><span class="special">:</span> <span class="identifier">vector</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">&gt;</span>
 <span class="identifier">a</span><span class="special">:</span> <span class="identifier">Unused</span> <span class="special">--&gt;</span> <span class="identifier">a</span><span class="special">:</span> <span class="identifier">Unused</span></pre>
 <p>
               </p>
-</td>
+ </td>
 </tr>
 <tr>
-<td><p>
- plus (<tt class="computeroutput"><span class="special">+</span></tt>)
- </p></td>
 <td>
-<p>
+ <p>
+ plus (<code class="computeroutput"><span class="special">+</span></code>)
+ </p>
+ </td>
+<td>
+ <p>
                 
 </p>
 <pre class="programlisting"><span class="identifier">a</span><span class="special">:</span> <span class="identifier">A</span> <span class="special">--&gt;</span> <span class="special">+</span><span class="identifier">a</span><span class="special">:</span> <span class="identifier">vector</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">&gt;</span>
 <span class="identifier">a</span><span class="special">:</span> <span class="identifier">Unused</span> <span class="special">--&gt;</span> <span class="identifier">a</span><span class="special">:</span> <span class="identifier">Unused</span></pre>
 <p>
               </p>
-</td>
+ </td>
 </tr>
 <tr>
-<td><p>
- list (<tt class="computeroutput"><span class="special">%</span></tt>)
- </p></td>
 <td>
-<p>
+ <p>
+ list (<code class="computeroutput"><span class="special">%</span></code>)
+ </p>
+ </td>
+<td>
+ <p>
                 
 </p>
 <pre class="programlisting"><span class="identifier">a</span><span class="special">:</span> <span class="identifier">A</span><span class="special">,</span> <span class="identifier">b</span><span class="special">:</span> <span class="identifier">B</span> <span class="special">--&gt;</span> <span class="special">(</span><span class="identifier">a</span> <span class="special">%</span> <span class="identifier">b</span><span class="special">):</span> <span class="identifier">vector</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">&gt;</span>
 <span class="identifier">a</span><span class="special">:</span> <span class="identifier">Unused</span><span class="special">,</span> <span class="identifier">b</span><span class="special">:</span> <span class="identifier">B</span> <span class="special">--&gt;</span> <span class="special">(</span><span class="identifier">a</span> <span class="special">%</span> <span class="identifier">b</span><span class="special">):</span> <span class="identifier">Unused</span></pre>
 <p>
               </p>
-</td>
+ </td>
 </tr>
 <tr>
-<td><p>
+<td>
+ <p>
                 repetition
- </p></td>
+ </p>
+ </td>
 <td>
-<p>
+ <p>
                 
 </p>
 <pre class="programlisting"><span class="identifier">a</span><span class="special">:</span> <span class="identifier">A</span> <span class="special">--&gt;</span> <span class="identifier">repeat</span><span class="special">(...,...)[</span><span class="identifier">a</span><span class="special">]:</span> <span class="identifier">vector</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">&gt;</span>
 <span class="identifier">a</span><span class="special">:</span> <span class="identifier">Unused</span> <span class="special">--&gt;</span> <span class="identifier">repeat</span><span class="special">(...,...)[</span><span class="identifier">a</span><span class="special">]:</span> <span class="identifier">Unused</span></pre>
 <p>
               </p>
-</td>
+ </td>
 </tr>
 <tr>
-<td><p>
- sequential or (<tt class="computeroutput"><span class="special">||</span></tt>)
- </p></td>
 <td>
-<p>
+ <p>
+ sequential or (<code class="computeroutput"><span class="special">||</span></code>)
+ </p>
+ </td>
+<td>
+ <p>
                 
 </p>
 <pre class="programlisting"><span class="identifier">a</span><span class="special">:</span> <span class="identifier">A</span><span class="special">,</span> <span class="identifier">b</span><span class="special">:</span> <span class="identifier">B</span> <span class="special">--&gt;</span> <span class="special">(</span><span class="identifier">a</span> <span class="special">||</span> <span class="identifier">b</span><span class="special">):</span> <span class="identifier">tuple</span><span class="special">&lt;</span><span class="identifier">optional</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">&gt;,</span> <span class="identifier">optional</span><span class="special">&lt;</span><span class="identifier">B</span><span class="special">&gt;</span> <span class="special">&gt;</span>
@@ -196,48 +214,60 @@
 <span class="identifier">a</span><span class="special">:</span> <span class="identifier">Unused</span><span class="special">,</span> <span class="identifier">b</span><span class="special">:</span> <span class="identifier">Unused</span> <span class="special">--&gt;</span> <span class="special">(</span><span class="identifier">a</span> <span class="special">||</span> <span class="identifier">b</span><span class="special">):</span> <span class="identifier">Unused</span></pre>
 <p>
               </p>
-</td>
+ </td>
 </tr>
 <tr>
-<td><p>
- optional (<tt class="computeroutput"><span class="special">-</span></tt>)
- </p></td>
 <td>
-<p>
+ <p>
+ optional (<code class="computeroutput"><span class="special">-</span></code>)
+ </p>
+ </td>
+<td>
+ <p>
                 
 </p>
 <pre class="programlisting"><span class="identifier">a</span><span class="special">:</span> <span class="identifier">A</span> <span class="special">--&gt;</span> <span class="special">-</span><span class="identifier">a</span><span class="special">:</span> <span class="identifier">optional</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">&gt;</span>
 <span class="identifier">a</span><span class="special">:</span> <span class="identifier">Unused</span> <span class="special">--&gt;</span> <span class="special">-</span><span class="identifier">a</span><span class="special">:</span> <span class="identifier">Unused</span></pre>
 <p>
               </p>
-</td>
+ </td>
 </tr>
 <tr>
-<td><p>
- and predicate (<tt class="computeroutput"><span class="special">&amp;</span></tt>)
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">a</span><span class="special">:</span>
+<td>
+ <p>
+ and predicate (<code class="computeroutput"><span class="special">&amp;</span></code>)
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">a</span><span class="special">:</span>
                 <span class="identifier">A</span> <span class="special">--&gt;</span>
- <span class="special">&amp;</span><span class="identifier">a</span><span class="special">:</span> <span class="identifier">Unused</span></tt>
- </p></td>
+ <span class="special">&amp;</span><span class="identifier">a</span><span class="special">:</span> <span class="identifier">Unused</span></code>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- not predicate (<tt class="computeroutput"><span class="special">!</span></tt>)
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">a</span><span class="special">:</span>
+<td>
+ <p>
+ not predicate (<code class="computeroutput"><span class="special">!</span></code>)
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">a</span><span class="special">:</span>
                 <span class="identifier">A</span> <span class="special">--&gt;</span>
- <span class="special">!</span><span class="identifier">a</span><span class="special">:</span> <span class="identifier">Unused</span></tt>
- </p></td>
+ <span class="special">!</span><span class="identifier">a</span><span class="special">:</span> <span class="identifier">Unused</span></code>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- permutation (<tt class="computeroutput"><span class="special">^</span></tt>)
- </p></td>
 <td>
-<p>
+ <p>
+ permutation (<code class="computeroutput"><span class="special">^</span></code>)
+ </p>
+ </td>
+<td>
+ <p>
                 
 </p>
 <pre class="programlisting"><span class="identifier">a</span><span class="special">:</span> <span class="identifier">A</span><span class="special">,</span> <span class="identifier">b</span><span class="special">:</span> <span class="identifier">B</span> <span class="special">--&gt;</span> <span class="special">(</span><span class="identifier">a</span> <span class="special">^</span> <span class="identifier">b</span><span class="special">):</span> <span class="identifier">tuple</span><span class="special">&lt;</span><span class="identifier">optional</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">&gt;,</span> <span class="identifier">optional</span><span class="special">&lt;</span><span class="identifier">B</span><span class="special">&gt;</span> <span class="special">&gt;</span>
@@ -246,11 +276,12 @@
 <span class="identifier">a</span><span class="special">:</span> <span class="identifier">Unused</span><span class="special">,</span> <span class="identifier">b</span><span class="special">:</span> <span class="identifier">Unused</span> <span class="special">--&gt;</span> <span class="special">(</span><span class="identifier">a</span> <span class="special">^</span> <span class="identifier">b</span><span class="special">):</span> <span class="identifier">Unused</span></pre>
 <p>
               </p>
-</td>
+ </td>
 </tr>
 </tbody>
-</table>
+</table></div>
 </div>
+<br class="table-break">
 </div>
 <table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
 <td align="left"></td>

Modified: trunk/libs/spirit/doc/html/spirit/qi/quick_reference/non_terminals.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/qi/quick_reference/non_terminals.html (original)
+++ trunk/libs/spirit/doc/html/spirit/qi/quick_reference/non_terminals.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -3,13 +3,11 @@
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <title>Non-terminals</title>
 <link rel="stylesheet" href="../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../index.html" title="Spirit 2.1">
 <link rel="up" href="../quick_reference.html" title="Quick Reference">
-<link rel="previous" href="compound_attribute_rules.html" title="Compound
- Attribute Rules">
-<link rel="next" href="semantic_actions.html" title="Semantic
- Actions">
+<link rel="prev" href="compound_attribute_rules.html" title="Compound Attribute Rules">
+<link rel="next" href="semantic_actions.html" title="Semantic Actions">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
 <table cellpadding="2" width="100%"><tr>
@@ -24,61 +22,58 @@
 <div class="spirit-nav">
 <a accesskey="p" href="compound_attribute_rules.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../quick_reference.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="semantic_actions.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h4 class="title">
-<a name="spirit.qi.quick_reference.non_terminals"></a>Non-terminals
-</h4></div></div>
-<div></div>
-</div>
-<div class="variablelist">
+<div class="section" title="Non-terminals">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="spirit.qi.quick_reference.non_terminals"></a><a class="link" href="non_terminals.html" title="Non-terminals">Non-terminals</a>
+</h4></div></div></div>
+<div class="variablelist" title="Notation">
 <p class="title"><b>Notation</b></p>
 <dl>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">RT</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">RT</span></code></span></dt>
 <dd><p>
               Synthesized attribute. The rule or grammar's return type.
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">Arg1</span></tt>,
- <tt class="computeroutput"><span class="identifier">Arg2</span></tt>, <tt class="computeroutput"><span class="identifier">ArgN</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">Arg1</span></code>,
+ <code class="computeroutput"><span class="identifier">Arg2</span></code>, <code class="computeroutput"><span class="identifier">ArgN</span></code></span></dt>
 <dd><p>
               Inherited attributes. Zero or more or arguments.
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">L1</span></tt>,
- <tt class="computeroutput"><span class="identifier">L2</span></tt>, <tt class="computeroutput"><span class="identifier">LN</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">L1</span></code>,
+ <code class="computeroutput"><span class="identifier">L2</span></code>, <code class="computeroutput"><span class="identifier">LN</span></code></span></dt>
 <dd><p>
               Zero or more local variables.
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">r</span><span class="special">,</span> <span class="identifier">r2</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">r</span><span class="special">,</span> <span class="identifier">r2</span></code></span></dt>
 <dd><p>
               Rules
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">g</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">g</span></code></span></dt>
 <dd><p>
               A grammar
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">p</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">p</span></code></span></dt>
 <dd><p>
               A parser expression
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">my_grammar</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">my_grammar</span></code></span></dt>
 <dd><p>
               A user defined grammar
             </p></dd>
 </dl>
 </div>
-<div class="variablelist">
+<div class="variablelist" title="Terminology">
 <p class="title"><b>Terminology</b></p>
 <dl>
 <dt><span class="term">Signature</span></dt>
 <dd><p>
- <tt class="computeroutput"><span class="identifier">RT</span><span class="special">(</span><span class="identifier">Arg1</span><span class="special">,</span> <span class="identifier">Arg2</span> <span class="special">...</span>
- <span class="special">,</span><span class="identifier">ArgN</span><span class="special">)</span></tt>. The signature specifies the synthesized
+ <code class="computeroutput"><span class="identifier">RT</span><span class="special">(</span><span class="identifier">Arg1</span><span class="special">,</span> <span class="identifier">Arg2</span> <span class="special">...</span>
+ <span class="special">,</span><span class="identifier">ArgN</span><span class="special">)</span></code>. The signature specifies the synthesized
               (return value) and inherited (arguments) attributes.
             </p></dd>
 <dt><span class="term">Locals</span></dt>
 <dd><p>
- <tt class="computeroutput"><span class="identifier">locals</span><span class="special">&lt;</span><span class="identifier">L1</span><span class="special">,</span> <span class="identifier">L2</span> <span class="special">...,</span>
- <span class="identifier">LN</span><span class="special">&gt;</span></tt>.
+ <code class="computeroutput"><span class="identifier">locals</span><span class="special">&lt;</span><span class="identifier">L1</span><span class="special">,</span> <span class="identifier">L2</span> <span class="special">...,</span>
+ <span class="identifier">LN</span><span class="special">&gt;</span></code>.
               The local variables.
             </p></dd>
 <dt><span class="term">Skipper</span></dt>
@@ -87,15 +82,15 @@
             </p></dd>
 </dl>
 </div>
-<div class="variablelist">
+<div class="variablelist" title="Template Arguments">
 <p class="title"><b>Template Arguments</b></p>
 <dl>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">Iterator</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">Iterator</span></code></span></dt>
 <dd><p>
               The iterator type you will use for parsing.
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">A1</span></tt>,
- <tt class="computeroutput"><span class="identifier">A2</span></tt>, <tt class="computeroutput"><span class="identifier">A3</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">A1</span></code>,
+ <code class="computeroutput"><span class="identifier">A2</span></code>, <code class="computeroutput"><span class="identifier">A3</span></code></span></dt>
 <dd><p>
               Can be one of 1)Signature 2)Locals 3)Skipper.
             </p></dd>
@@ -107,120 +102,164 @@
 <col>
 </colgroup>
 <thead><tr>
-<th><p>
+<th>
+ <p>
                   Expression
- </p></th>
-<th><p>
+ </p>
+ </th>
+<th>
+ <p>
                   Description
- </p></th>
+ </p>
+ </th>
 </tr></thead>
 <tbody>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">rule</span><span class="special">&lt;</span><span class="identifier">Iterator</span><span class="special">,</span>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">rule</span><span class="special">&lt;</span><span class="identifier">Iterator</span><span class="special">,</span>
                   <span class="identifier">A1</span><span class="special">,</span>
                   <span class="identifier">A2</span><span class="special">,</span>
                   <span class="identifier">A3</span><span class="special">&gt;</span>
- <span class="identifier">r</span><span class="special">(</span><span class="identifier">name</span><span class="special">);</span></tt>
- </p></td>
-<td><p>
- Rule declaration. <tt class="computeroutput"><span class="identifier">Iterator</span></tt>
- is required. <tt class="computeroutput"><span class="identifier">A1</span><span class="special">,</span> <span class="identifier">A2</span><span class="special">,</span> <span class="identifier">A3</span></tt>
- are optional and can be specified in any order. <tt class="computeroutput"><span class="identifier">name</span></tt>
+ <span class="identifier">r</span><span class="special">(</span><span class="identifier">name</span><span class="special">);</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Rule declaration. <code class="computeroutput"><span class="identifier">Iterator</span></code>
+ is required. <code class="computeroutput"><span class="identifier">A1</span><span class="special">,</span> <span class="identifier">A2</span><span class="special">,</span> <span class="identifier">A3</span></code>
+ are optional and can be specified in any order. <code class="computeroutput"><span class="identifier">name</span></code>
                   is an optional string that gives the rule its name, useful for
                   debugging and error handling.
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">rule</span><span class="special">&lt;</span><span class="identifier">Iterator</span><span class="special">,</span>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">rule</span><span class="special">&lt;</span><span class="identifier">Iterator</span><span class="special">,</span>
                   <span class="identifier">A1</span><span class="special">,</span>
                   <span class="identifier">A2</span><span class="special">,</span>
                   <span class="identifier">A3</span><span class="special">&gt;</span>
- <span class="identifier">r</span><span class="special">(</span><span class="identifier">r2</span><span class="special">);</span></tt>
- </p></td>
-<td><p>
- Copy construct rule <tt class="computeroutput"><span class="identifier">r</span></tt>
- from rule <tt class="computeroutput"><span class="identifier">r2</span></tt>.
- <tt class="computeroutput"><span class="identifier">boost</span><span class="special">::</span><span class="identifier">shared_ptr</span></tt> semantics.
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">r</span> <span class="special">=</span>
- <span class="identifier">r2</span><span class="special">;</span></tt>
- </p></td>
-<td><p>
- Assign rule <tt class="computeroutput"><span class="identifier">r2</span></tt>
- to <tt class="computeroutput"><span class="identifier">r</span></tt>. <tt class="computeroutput"><span class="identifier">boost</span><span class="special">::</span><span class="identifier">shared_ptr</span></tt> semantics.
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">r</span><span class="special">.</span><span class="identifier">alias</span><span class="special">()</span></tt>
- </p></td>
-<td><p>
- return an alias of <tt class="computeroutput"><span class="identifier">r</span></tt>.
- The alias is a parser that holds a reference to <tt class="computeroutput"><span class="identifier">r</span></tt>.
+ <span class="identifier">r</span><span class="special">(</span><span class="identifier">r2</span><span class="special">);</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Copy construct rule <code class="computeroutput"><span class="identifier">r</span></code>
+ from rule <code class="computeroutput"><span class="identifier">r2</span></code>.
+ <code class="computeroutput"><span class="identifier">boost</span><span class="special">::</span><span class="identifier">shared_ptr</span></code> semantics.
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">r</span> <span class="special">=</span>
+ <span class="identifier">r2</span><span class="special">;</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Assign rule <code class="computeroutput"><span class="identifier">r2</span></code>
+ to <code class="computeroutput"><span class="identifier">r</span></code>. <code class="computeroutput"><span class="identifier">boost</span><span class="special">::</span><span class="identifier">shared_ptr</span></code> semantics.
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">r</span><span class="special">.</span><span class="identifier">alias</span><span class="special">()</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ return an alias of <code class="computeroutput"><span class="identifier">r</span></code>.
+ The alias is a parser that holds a reference to <code class="computeroutput"><span class="identifier">r</span></code>.
                   Reference semantics.
- </p></td>
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">r</span><span class="special">.</span><span class="identifier">copy</span><span class="special">()</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Get a copy of <code class="computeroutput"><span class="identifier">r</span></code>.
+ <code class="computeroutput"><span class="identifier">boost</span><span class="special">::</span><span class="identifier">shared_ptr</span></code> semantics.
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">r</span><span class="special">.</span><span class="identifier">copy</span><span class="special">()</span></tt>
- </p></td>
-<td><p>
- Get a copy of <tt class="computeroutput"><span class="identifier">r</span></tt>.
- <tt class="computeroutput"><span class="identifier">boost</span><span class="special">::</span><span class="identifier">shared_ptr</span></tt> semantics.
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">r</span><span class="special">.</span><span class="identifier">name</span><span class="special">(</span><span class="identifier">name</span><span class="special">)</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">r</span><span class="special">.</span><span class="identifier">name</span><span class="special">(</span><span class="identifier">name</span><span class="special">)</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   Naming a rule
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">r</span><span class="special">.</span><span class="identifier">name</span><span class="special">()</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">r</span><span class="special">.</span><span class="identifier">name</span><span class="special">()</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   Getting the name of a rule
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
+<td>
+ <p>
                   debug(r)
- </p></td>
-<td><p>
- Debug rule <tt class="computeroutput"><span class="identifier">r</span></tt>
- </p></td>
+ </p>
+ </td>
+<td>
+ <p>
+ Debug rule <code class="computeroutput"><span class="identifier">r</span></code>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">r</span> <span class="special">=</span>
- <span class="identifier">p</span><span class="special">;</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">r</span> <span class="special">=</span>
+ <span class="identifier">p</span><span class="special">;</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   Rule definition
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">r</span> <span class="special">%=</span>
- <span class="identifier">p</span><span class="special">;</span></tt>
- </p></td>
-<td><p>
- Auto-rule definition. The attribute of <tt class="computeroutput"><span class="identifier">p</span></tt>
- should be compatible with the synthesized attribute of <tt class="computeroutput"><span class="identifier">r</span></tt>. When <tt class="computeroutput"><span class="identifier">p</span></tt>
- is successful, its attribute is automatically propagated to <tt class="computeroutput"><span class="identifier">r</span></tt>'s synthesized attribute.
- </p></td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">r</span> <span class="special">%=</span>
+ <span class="identifier">p</span><span class="special">;</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Auto-rule definition. The attribute of <code class="computeroutput"><span class="identifier">p</span></code>
+ should be compatible with the synthesized attribute of <code class="computeroutput"><span class="identifier">r</span></code>. When <code class="computeroutput"><span class="identifier">p</span></code>
+ is successful, its attribute is automatically propagated to <code class="computeroutput"><span class="identifier">r</span></code>'s synthesized attribute.
+ </p>
+ </td>
 </tr>
 <tr>
 <td>
-<p>
+ <p>
                   
 </p>
 <pre xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="table-programlisting"><span class="keyword">template</span> <span class="special">&lt;</span><span class="keyword">typename</span> <span class="identifier">Iterator</span><span class="special">&gt;</span>
@@ -238,36 +277,50 @@
 </pre>
 <p>
                 </p>
-</td>
-<td><p>
- Grammar definition. <tt class="computeroutput"><span class="identifier">name</span></tt>
+ </td>
+<td>
+ <p>
+ Grammar definition. <code class="computeroutput"><span class="identifier">name</span></code>
                   is an optional string that gives the grammar its name, useful for
                   debugging and error handling.
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
+<td>
+ <p>
                   my_grammar&lt;Iterator&gt; g
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
                   Instantiating a grammar
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">g</span><span class="special">.</span><span class="identifier">name</span><span class="special">(</span><span class="identifier">name</span><span class="special">)</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">g</span><span class="special">.</span><span class="identifier">name</span><span class="special">(</span><span class="identifier">name</span><span class="special">)</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   Naming a grammar
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">g</span><span class="special">.</span><span class="identifier">name</span><span class="special">()</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">g</span><span class="special">.</span><span class="identifier">name</span><span class="special">()</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   Getting the name of a grammar
- </p></td>
+ </p>
+ </td>
 </tr>
 </tbody>
 </table></div>

Modified: trunk/libs/spirit/doc/html/spirit/qi/quick_reference/phoenix.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/qi/quick_reference/phoenix.html (original)
+++ trunk/libs/spirit/doc/html/spirit/qi/quick_reference/phoenix.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -3,11 +3,10 @@
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <title>Phoenix</title>
 <link rel="stylesheet" href="../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../index.html" title="Spirit 2.1">
 <link rel="up" href="../quick_reference.html" title="Quick Reference">
-<link rel="previous" href="semantic_actions.html" title="Semantic
- Actions">
+<link rel="prev" href="semantic_actions.html" title="Semantic Actions">
 <link rel="next" href="../reference.html" title="Reference">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -23,13 +22,10 @@
 <div class="spirit-nav">
 <a accesskey="p" href="semantic_actions.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../quick_reference.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="../reference.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h4 class="title">
-<a name="spirit.qi.quick_reference.phoenix"></a>Phoenix
-</h4></div></div>
-<div></div>
-</div>
+<div class="section" title="Phoenix">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="spirit.qi.quick_reference.phoenix"></a><a class="link" href="phoenix.html" title="Phoenix">Phoenix</a>
+</h4></div></div></div>
 <p>
           <a href="../../../../../phoenix/doc/html/index.html" target="_top">Boost.Phoenix</a> makes
           it easier to attach semantic actions. You just inline your lambda expressions:
@@ -38,37 +34,37 @@
 </pre>
 <p>
           Spirit.Qi provides some Boost.Phoenix
- placeholders to important information from the <tt class="computeroutput"><span class="identifier">Attr</span></tt>
- and <tt class="computeroutput"><span class="identifier">Context</span></tt> that are otherwise
+ placeholders to important information from the <code class="computeroutput"><span class="identifier">Attr</span></code>
+ and <code class="computeroutput"><span class="identifier">Context</span></code> that are otherwise
           fiddly to extract.
         </p>
-<div class="variablelist">
+<div class="variablelist" title="Spirit.Qi specific Phoenix placeholders">
 <p class="title"><b>Spirit.Qi specific Phoenix placeholders</b></p>
 <dl>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">_1</span><span class="special">,</span> <span class="identifier">_2</span><span class="special">...</span> <span class="special">,</span> <span class="identifier">_N</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">_1</span><span class="special">,</span> <span class="identifier">_2</span><span class="special">...</span> <span class="special">,</span> <span class="identifier">_N</span></code></span></dt>
 <dd><p>
- Nth attribute of <tt class="computeroutput"><span class="identifier">p</span></tt>
+ Nth attribute of <code class="computeroutput"><span class="identifier">p</span></code>
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">_val</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">_val</span></code></span></dt>
 <dd><p>
               The enclosing rule's synthesized attribute.
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">_r1</span><span class="special">,</span> <span class="identifier">_r2</span><span class="special">...</span> <span class="special">,</span> <span class="identifier">_rN</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">_r1</span><span class="special">,</span> <span class="identifier">_r2</span><span class="special">...</span> <span class="special">,</span> <span class="identifier">_rN</span></code></span></dt>
 <dd><p>
               The enclosing rule's Nth inherited attribute.
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">_a</span><span class="special">,</span> <span class="identifier">_b</span><span class="special">...</span> <span class="special">,</span> <span class="identifier">_j</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">_a</span><span class="special">,</span> <span class="identifier">_b</span><span class="special">...</span> <span class="special">,</span> <span class="identifier">_j</span></code></span></dt>
 <dd><p>
- The enclosing rule's local variables (<tt class="computeroutput"><span class="identifier">_a</span></tt>
+ The enclosing rule's local variables (<code class="computeroutput"><span class="identifier">_a</span></code>
               refers to the first).
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">_val</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">_val</span></code></span></dt>
 <dd><p>
               The enclosing rule's synthesized attribute.
             </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">_pass</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">_pass</span></code></span></dt>
 <dd><p>
- Assign <tt class="computeroutput"><span class="keyword">false</span></tt> to <tt class="computeroutput"><span class="identifier">_pass</span></tt> to force a parser failure.
+ Assign <code class="computeroutput"><span class="keyword">false</span></code> to <code class="computeroutput"><span class="identifier">_pass</span></code> to force a parser failure.
             </p></dd>
 </dl>
 </div>

Modified: trunk/libs/spirit/doc/html/spirit/qi/quick_reference/predefined_primitive_parsers.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/qi/quick_reference/predefined_primitive_parsers.html (original)
+++ trunk/libs/spirit/doc/html/spirit/qi/quick_reference/predefined_primitive_parsers.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -1,15 +1,13 @@
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title>Predefined
- Primitive Parsers</title>
+<title>Predefined Primitive Parsers</title>
 <link rel="stylesheet" href="../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../index.html" title="Spirit 2.1">
 <link rel="up" href="../quick_reference.html" title="Quick Reference">
-<link rel="previous" href="common_notation.html" title="Common Notation">
-<link rel="next" href="compound_attribute_rules.html" title="Compound
- Attribute Rules">
+<link rel="prev" href="common_notation.html" title="Common Notation">
+<link rel="next" href="compound_attribute_rules.html" title="Compound Attribute Rules">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
 <table cellpadding="2" width="100%"><tr>
@@ -24,15 +22,11 @@
 <div class="spirit-nav">
 <a accesskey="p" href="common_notation.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../quick_reference.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="compound_attribute_rules.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h4 class="title">
-<a name="spirit.qi.quick_reference.predefined_primitive_parsers"></a><a href="predefined_primitive_parsers.html" title="Predefined
- Primitive Parsers">Predefined
+<div class="section" title="Predefined Primitive Parsers">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="spirit.qi.quick_reference.predefined_primitive_parsers"></a><a class="link" href="predefined_primitive_parsers.html" title="Predefined Primitive Parsers">Predefined
         Primitive Parsers</a>
-</h4></div></div>
-<div></div>
-</div>
+</h4></div></div></div>
 <div class="informaltable"><table class="table">
 <colgroup>
 <col>
@@ -40,342 +34,516 @@
 <col>
 </colgroup>
 <thead><tr>
-<th><p>
+<th>
+ <p>
                   Expression
- </p></th>
-<th><p>
+ </p>
+ </th>
+<th>
+ <p>
                   Attribute
- </p></th>
-<th><p>
+ </p>
+ </th>
+<th>
+ <p>
                   Description
- </p></th>
+ </p>
+ </th>
 </tr></thead>
 <tbody>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">eol</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">Unused</span></tt>
- </p></td>
-<td><p>
- Matches the end of line (<tt class="computeroutput"><span class="special">\</span><span class="identifier">r</span></tt> or <tt class="computeroutput"><span class="special">\</span><span class="identifier">n</span></tt> or <tt class="computeroutput"><span class="special">\</span><span class="identifier">r</span><span class="special">\</span><span class="identifier">n</span></tt>)
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">eoi</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">Unused</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">eol</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">Unused</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Matches the end of line (<code class="computeroutput"><span class="special">\</span><span class="identifier">r</span></code> or <code class="computeroutput"><span class="special">\</span><span class="identifier">n</span></code> or <code class="computeroutput"><span class="special">\</span><span class="identifier">r</span><span class="special">\</span><span class="identifier">n</span></code>)
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">eoi</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">Unused</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   Matches the end of input (first == last)
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">eps</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">Unused</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">eps</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">Unused</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   Match an empty string
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">eps</span><span class="special">(</span><span class="identifier">b</span><span class="special">)</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">Unused</span></tt>
- </p></td>
-<td><p>
- If <tt class="computeroutput"><span class="identifier">b</span></tt> is true, match
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">eps</span><span class="special">(</span><span class="identifier">b</span><span class="special">)</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">Unused</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ If <code class="computeroutput"><span class="identifier">b</span></code> is true, match
                   an empty string
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">lazy</span><span class="special">(</span><span class="identifier">fp</span><span class="special">)</span></tt>
- </p></td>
-<td><p>
- Attribute of <tt class="computeroutput"><span class="identifier">P</span></tt>
- where <tt class="computeroutput"><span class="identifier">P</span></tt> is the
- return type of <tt class="computeroutput"><span class="identifier">fp</span></tt>
- </p></td>
-<td><p>
- Invoke <tt class="computeroutput"><span class="identifier">fp</span></tt> at parse
- time, returning a parser <tt class="computeroutput"><span class="identifier">p</span></tt>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">lazy</span><span class="special">(</span><span class="identifier">fp</span><span class="special">)</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Attribute of <code class="computeroutput"><span class="identifier">P</span></code>
+ where <code class="computeroutput"><span class="identifier">P</span></code> is the
+ return type of <code class="computeroutput"><span class="identifier">fp</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Invoke <code class="computeroutput"><span class="identifier">fp</span></code> at parse
+ time, returning a parser <code class="computeroutput"><span class="identifier">p</span></code>
                   which is then called to parse.
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">fp</span></tt>
- </p></td>
-<td><p>
- see <tt class="computeroutput"><span class="identifier">lazy</span><span class="special">(</span><span class="identifier">fp</span><span class="special">)</span></tt>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">fp</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ see <code class="computeroutput"><span class="identifier">lazy</span><span class="special">(</span><span class="identifier">fp</span><span class="special">)</span></code>
                   above
- </p></td>
-<td><p>
- Equivalent to <tt class="computeroutput"><span class="identifier">lazy</span><span class="special">[</span><span class="identifier">fp</span><span class="special">]</span></tt>
- </p></td>
+ </p>
+ </td>
+<td>
+ <p>
+ Equivalent to <code class="computeroutput"><span class="identifier">lazy</span><span class="special">[</span><span class="identifier">fp</span><span class="special">]</span></code>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">p</span><span class="special">[</span><span class="identifier">fa</span><span class="special">]</span></tt>
- </p></td>
-<td><p>
- Attribute of <tt class="computeroutput"><span class="identifier">p</span></tt>
- </p></td>
-<td><p>
- Call semantic action, <tt class="computeroutput"><span class="identifier">fa</span></tt>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">p</span><span class="special">[</span><span class="identifier">fa</span><span class="special">]</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Attribute of <code class="computeroutput"><span class="identifier">p</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Call semantic action, <code class="computeroutput"><span class="identifier">fa</span></code>
                   if p succeeds.
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">byte_</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">byte_</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   8 bits native endian
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
                   Matches an 8 bit binary
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">word</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">word</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   16 bits native endian
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
                   Matches a 16 bit binary
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">big_word</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">big_word</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   16 bits big endian
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
                   Matches a 16 bit binary
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">little_word</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">little_word</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   16 bits little endian
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
                   Matches a 16 bit binary
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">dword</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">dword</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   32 bits native endian
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
                   Matches a 32 bit binary
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">big_dword</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">big_dword</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   32 bits big endian
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
                   Matches a 32 bit binary
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">little_dword</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">little_dword</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   32 bits little endian
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
                   Matches a 32 bit binary
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">qword</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">qword</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   64 bits native endian
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
                   Matches a 64 bit binary
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">big_qword</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">big_qword</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   64 bits big endian
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
                   Matches a 64 bit binary
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">little_qword</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">little_qword</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   64 bits little endian
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
                   Matches a 64 bit binary
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">char_</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">Ch</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">char_</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">Ch</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   Matches any character
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">char_</span><span class="special">(</span><span class="identifier">ch</span><span class="special">)</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">Ch</span></tt>
- </p></td>
-<td><p>
- Matches <tt class="computeroutput"><span class="identifier">ch</span></tt>
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">char_</span><span class="special">(</span><span class="string">"c"</span><span class="special">)</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">Ch</span></tt>
- </p></td>
-<td><p>
- Matches a single char string literal, <tt class="computeroutput"><span class="identifier">c</span></tt>
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">char_</span><span class="special">(</span><span class="identifier">ch</span><span class="special">,</span>
- <span class="identifier">ch2</span><span class="special">)</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">Ch</span></tt>
- </p></td>
-<td><p>
- Matches a range of chars from <tt class="computeroutput"><span class="identifier">ch</span></tt>
- to <tt class="computeroutput"><span class="identifier">ch2</span></tt> (inclusive)
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">char_</span><span class="special">(</span><span class="identifier">chset</span><span class="special">)</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">Ch</span></tt>
- </p></td>
-<td><p>
- Matches a character set <tt class="computeroutput"><span class="identifier">chset</span></tt>
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">ch</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">Unused</span></tt>
- </p></td>
-<td><p>
- Matches <tt class="computeroutput"><span class="identifier">ch</span></tt>
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">str</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">Unused</span></tt>
- </p></td>
-<td><p>
- Matches <tt class="computeroutput"><span class="identifier">str</span></tt>
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">lit</span><span class="special">(</span><span class="identifier">ch</span><span class="special">)</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">Unused</span></tt>
- </p></td>
-<td><p>
- Matches <tt class="computeroutput"><span class="identifier">ch</span></tt>
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">lit</span><span class="special">(</span><span class="identifier">str</span><span class="special">)</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">Unused</span></tt>
- </p></td>
-<td><p>
- Matches <tt class="computeroutput"><span class="identifier">str</span></tt>
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">string</span><span class="special">(</span><span class="identifier">str</span><span class="special">)</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">Str</span></tt>
- </p></td>
-<td><p>
- Matches <tt class="computeroutput"><span class="identifier">str</span></tt>
- </p></td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">char_</span><span class="special">(</span><span class="identifier">ch</span><span class="special">)</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">Ch</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Matches <code class="computeroutput"><span class="identifier">ch</span></code>
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">char_</span><span class="special">(</span><span class="string">"c"</span><span class="special">)</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">Ch</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Matches a single char string literal, <code class="computeroutput"><span class="identifier">c</span></code>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">symbols</span><span class="special">&lt;</span><span class="identifier">Ch</span><span class="special">,</span>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">char_</span><span class="special">(</span><span class="identifier">ch</span><span class="special">,</span>
+ <span class="identifier">ch2</span><span class="special">)</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">Ch</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Matches a range of chars from <code class="computeroutput"><span class="identifier">ch</span></code>
+ to <code class="computeroutput"><span class="identifier">ch2</span></code> (inclusive)
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">char_</span><span class="special">(</span><span class="identifier">chset</span><span class="special">)</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">Ch</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Matches a character set <code class="computeroutput"><span class="identifier">chset</span></code>
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">ch</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">Unused</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Matches <code class="computeroutput"><span class="identifier">ch</span></code>
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">str</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">Unused</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Matches <code class="computeroutput"><span class="identifier">str</span></code>
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">lit</span><span class="special">(</span><span class="identifier">ch</span><span class="special">)</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">Unused</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Matches <code class="computeroutput"><span class="identifier">ch</span></code>
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">lit</span><span class="special">(</span><span class="identifier">str</span><span class="special">)</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">Unused</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Matches <code class="computeroutput"><span class="identifier">str</span></code>
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">string</span><span class="special">(</span><span class="identifier">str</span><span class="special">)</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">Str</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Matches <code class="computeroutput"><span class="identifier">str</span></code>
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">symbols</span><span class="special">&lt;</span><span class="identifier">Ch</span><span class="special">,</span>
                   <span class="identifier">T</span><span class="special">&gt;</span>
- <span class="identifier">sym</span><span class="special">;</span></tt>
- </p></td>
-<td><p>
+ <span class="identifier">sym</span><span class="special">;</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   N/A
- </p></td>
-<td><p>
- Declare a symbol table, <tt class="computeroutput"><span class="identifier">sym</span></tt>.
- <tt class="computeroutput"><span class="identifier">Ch</span></tt> is the underlying
- char type of the symbol table keys. <tt class="computeroutput"><span class="identifier">T</span></tt>
+ </p>
+ </td>
+<td>
+ <p>
+ Declare a symbol table, <code class="computeroutput"><span class="identifier">sym</span></code>.
+ <code class="computeroutput"><span class="identifier">Ch</span></code> is the underlying
+ char type of the symbol table keys. <code class="computeroutput"><span class="identifier">T</span></code>
                   is the data type associated with each key.
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
 <td>
-<p>
+ <p>
                   
 </p>
 <pre xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="table-programlisting"><span class="identifier">sym</span><span class="special">.</span><span class="identifier">add</span>
@@ -386,461 +554,687 @@
 </pre>
 <p>
                 </p>
-</td>
-<td><p>
+ </td>
+<td>
+ <p>
                   N/A
- </p></td>
-<td><p>
- Add symbols into a symbol table, <tt class="computeroutput"><span class="identifier">sym</span></tt>.
- val1 and val2 are optional data of type <tt class="computeroutput"><span class="identifier">T</span></tt>,
+ </p>
+ </td>
+<td>
+ <p>
+ Add symbols into a symbol table, <code class="computeroutput"><span class="identifier">sym</span></code>.
+ val1 and val2 are optional data of type <code class="computeroutput"><span class="identifier">T</span></code>,
                   the data type associated with each key.
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">sym</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">T</span></tt>
- </p></td>
-<td><p>
- Matches entries in the symbol table, <tt class="computeroutput"><span class="identifier">sym</span></tt>.
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">sym</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">T</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Matches entries in the symbol table, <code class="computeroutput"><span class="identifier">sym</span></code>.
                   If successful, returns the data associated with the key
- </p></td>
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">lexeme</span><span class="special">[</span><span class="identifier">a</span><span class="special">]</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">A</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Disable skip parsing for <code class="computeroutput"><span class="identifier">a</span></code>
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">nocase</span><span class="special">[</span><span class="identifier">a</span><span class="special">]</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">A</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Inhibits case-sensitivity for <code class="computeroutput"><span class="identifier">a</span></code>
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">omit</span><span class="special">[</span><span class="identifier">a</span><span class="special">]</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">Unused</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Ignores the attribute type of <code class="computeroutput"><span class="identifier">a</span></code>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">lexeme</span><span class="special">[</span><span class="identifier">a</span><span class="special">]</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">A</span></tt>
- </p></td>
-<td><p>
- Disable skip parsing for <tt class="computeroutput"><span class="identifier">a</span></tt>
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">nocase</span><span class="special">[</span><span class="identifier">a</span><span class="special">]</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">A</span></tt>
- </p></td>
-<td><p>
- Inhibits case-sensitivity for <tt class="computeroutput"><span class="identifier">a</span></tt>
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">omit</span><span class="special">[</span><span class="identifier">a</span><span class="special">]</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">Unused</span></tt>
- </p></td>
-<td><p>
- Ignores the attribute type of <tt class="computeroutput"><span class="identifier">a</span></tt>
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">raw</span><span class="special">[</span><span class="identifier">a</span><span class="special">]</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">boost</span><span class="special">::</span><span class="identifier">iterator_range</span><span class="special">&lt;</span><span class="identifier">I</span><span class="special">&gt;</span></tt>
- </p></td>
-<td><p>
- Presents the transduction of <tt class="computeroutput"><span class="identifier">a</span></tt>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">raw</span><span class="special">[</span><span class="identifier">a</span><span class="special">]</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">boost</span><span class="special">::</span><span class="identifier">iterator_range</span><span class="special">&lt;</span><span class="identifier">I</span><span class="special">&gt;</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Presents the transduction of <code class="computeroutput"><span class="identifier">a</span></code>
                   as an iterator range
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">repeat</span><span class="special">[</span><span class="identifier">a</span><span class="special">]</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">vector</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">&gt;</span></tt>
- </p></td>
-<td><p>
- Repeat <tt class="computeroutput"><span class="identifier">a</span></tt> zero or
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">repeat</span><span class="special">[</span><span class="identifier">a</span><span class="special">]</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">vector</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">&gt;</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Repeat <code class="computeroutput"><span class="identifier">a</span></code> zero or
                   more times
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">repeat</span><span class="special">(</span><span class="identifier">N</span><span class="special">)[</span><span class="identifier">a</span><span class="special">]</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">vector</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">&gt;</span></tt>
- </p></td>
-<td><p>
- Repeat <tt class="computeroutput"><span class="identifier">a</span></tt> <tt class="computeroutput"><span class="identifier">N</span></tt> times
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">repeat</span><span class="special">(</span><span class="identifier">N</span><span class="special">,</span>
- <span class="identifier">M</span><span class="special">)[</span><span class="identifier">a</span><span class="special">]</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">vector</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">&gt;</span></tt>
- </p></td>
-<td><p>
- Repeat <tt class="computeroutput"><span class="identifier">a</span></tt> <tt class="computeroutput"><span class="identifier">N</span></tt> to <tt class="computeroutput"><span class="identifier">M</span></tt>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">repeat</span><span class="special">(</span><span class="identifier">N</span><span class="special">)[</span><span class="identifier">a</span><span class="special">]</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">vector</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">&gt;</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Repeat <code class="computeroutput"><span class="identifier">a</span></code> <code class="computeroutput"><span class="identifier">N</span></code> times
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">repeat</span><span class="special">(</span><span class="identifier">N</span><span class="special">,</span>
+ <span class="identifier">M</span><span class="special">)[</span><span class="identifier">a</span><span class="special">]</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">vector</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">&gt;</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Repeat <code class="computeroutput"><span class="identifier">a</span></code> <code class="computeroutput"><span class="identifier">N</span></code> to <code class="computeroutput"><span class="identifier">M</span></code>
                   times
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">repeat</span><span class="special">(</span><span class="identifier">N</span><span class="special">,</span>
- <span class="identifier">inf</span><span class="special">)[</span><span class="identifier">a</span><span class="special">]</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">vector</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">&gt;</span></tt>
- </p></td>
-<td><p>
- Repeat <tt class="computeroutput"><span class="identifier">a</span></tt> <tt class="computeroutput"><span class="identifier">N</span></tt> or more times
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">skip</span><span class="special">[</span><span class="identifier">a</span><span class="special">]</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">A</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">repeat</span><span class="special">(</span><span class="identifier">N</span><span class="special">,</span>
+ <span class="identifier">inf</span><span class="special">)[</span><span class="identifier">a</span><span class="special">]</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">vector</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">&gt;</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Repeat <code class="computeroutput"><span class="identifier">a</span></code> <code class="computeroutput"><span class="identifier">N</span></code> or more times
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">skip</span><span class="special">[</span><span class="identifier">a</span><span class="special">]</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">A</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   Reestablish the skipper that got inhibited by lexeme
- </p></td>
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">skip</span><span class="special">(</span><span class="identifier">p</span><span class="special">)[</span><span class="identifier">a</span><span class="special">]</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">A</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Use <code class="computeroutput"><span class="identifier">p</span></code> as a skipper
+ for parsing <code class="computeroutput"><span class="identifier">a</span></code>
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">float_</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="keyword">float</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Parse a floating point number into a <code class="computeroutput"><span class="keyword">float</span></code>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">skip</span><span class="special">(</span><span class="identifier">p</span><span class="special">)[</span><span class="identifier">a</span><span class="special">]</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">A</span></tt>
- </p></td>
-<td><p>
- Use <tt class="computeroutput"><span class="identifier">p</span></tt> as a skipper
- for parsing <tt class="computeroutput"><span class="identifier">a</span></tt>
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">float_</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="keyword">float</span></tt>
- </p></td>
-<td><p>
- Parse a floating point number into a <tt class="computeroutput"><span class="keyword">float</span></tt>
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">double_</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="keyword">double</span></tt>
- </p></td>
-<td><p>
- Parse a floating point number into a <tt class="computeroutput"><span class="keyword">double</span></tt>
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">long_double</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="keyword">long</span> <span class="keyword">double</span></tt>
- </p></td>
-<td><p>
- Parse a floating point number into a <tt class="computeroutput"><span class="keyword">long</span>
- <span class="keyword">double</span></tt>
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">bin</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="keyword">unsigned</span></tt>
- </p></td>
-<td><p>
- Parse a binary integer into an <tt class="computeroutput"><span class="keyword">unsigned</span></tt>
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">oct</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="keyword">unsigned</span></tt>
- </p></td>
-<td><p>
- Parse an octal integer into an <tt class="computeroutput"><span class="keyword">unsigned</span></tt>
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">hex</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="keyword">unsigned</span></tt>
- </p></td>
-<td><p>
- Parse a hexadecimal integer into an <tt class="computeroutput"><span class="keyword">unsigned</span></tt>
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">ushort_</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="keyword">unsigned</span> <span class="keyword">short</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">double_</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="keyword">double</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Parse a floating point number into a <code class="computeroutput"><span class="keyword">double</span></code>
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">long_double</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="keyword">long</span> <span class="keyword">double</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Parse a floating point number into a <code class="computeroutput"><span class="keyword">long</span>
+ <span class="keyword">double</span></code>
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">bin</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="keyword">unsigned</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Parse a binary integer into an <code class="computeroutput"><span class="keyword">unsigned</span></code>
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">oct</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="keyword">unsigned</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Parse an octal integer into an <code class="computeroutput"><span class="keyword">unsigned</span></code>
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">hex</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="keyword">unsigned</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Parse a hexadecimal integer into an <code class="computeroutput"><span class="keyword">unsigned</span></code>
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">ushort_</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="keyword">unsigned</span> <span class="keyword">short</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   Parse an unsigned short integer
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">ulong_</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="keyword">unsigned</span> <span class="keyword">long</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">ulong_</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="keyword">unsigned</span> <span class="keyword">long</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   Parse an unsigned long integer
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">uint_</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="keyword">unsigned</span> <span class="keyword">int</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">uint_</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="keyword">unsigned</span> <span class="keyword">int</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   Parse an unsigned int
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">ulong_long</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="keyword">unsigned</span> <span class="keyword">long</span>
- <span class="keyword">long</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">ulong_long</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="keyword">unsigned</span> <span class="keyword">long</span>
+ <span class="keyword">long</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   Parse an unsigned long long
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">short_</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="keyword">short</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">short_</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="keyword">short</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   Parse a short integer
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">long_</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="keyword">long</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">long_</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="keyword">long</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   Parse a long integer
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">int_</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="keyword">int</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">int_</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="keyword">int</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   Parse an int
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">long_long</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="keyword">long</span> <span class="keyword">long</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">long_long</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="keyword">long</span> <span class="keyword">long</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                   Parse a long long
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="special">!</span><span class="identifier">a</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">Unused</span></tt>
- </p></td>
-<td><p>
- Not predicate. Ensure that <tt class="computeroutput"><span class="identifier">a</span></tt>
+<td>
+ <p>
+ <code class="computeroutput"><span class="special">!</span><span class="identifier">a</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">Unused</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Not predicate. Ensure that <code class="computeroutput"><span class="identifier">a</span></code>
                   does not match but don't move the iterator position
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="special">&amp;</span><span class="identifier">a</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">Unused</span></tt>
- </p></td>
-<td><p>
- And predicate. Ensure that <tt class="computeroutput"><span class="identifier">a</span></tt>
+<td>
+ <p>
+ <code class="computeroutput"><span class="special">&amp;</span><span class="identifier">a</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">Unused</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ And predicate. Ensure that <code class="computeroutput"><span class="identifier">a</span></code>
                   matches but don't move the iterator position
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="special">-</span><span class="identifier">a</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">optional</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">&gt;</span></tt>
- </p></td>
-<td><p>
- Optional. Parse <tt class="computeroutput"><span class="identifier">a</span></tt>
+<td>
+ <p>
+ <code class="computeroutput"><span class="special">-</span><span class="identifier">a</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">optional</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">&gt;</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Optional. Parse <code class="computeroutput"><span class="identifier">a</span></code>
                   zero or one time
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="special">*</span><span class="identifier">a</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">vector</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">&gt;</span></tt>
- </p></td>
-<td><p>
- Kleene. Parse <tt class="computeroutput"><span class="identifier">a</span></tt>
+<td>
+ <p>
+ <code class="computeroutput"><span class="special">*</span><span class="identifier">a</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">vector</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">&gt;</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Kleene. Parse <code class="computeroutput"><span class="identifier">a</span></code>
                   zero or more times
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="special">+</span><span class="identifier">a</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">vector</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">&gt;</span></tt>
- </p></td>
-<td><p>
- Plus. Parse <tt class="computeroutput"><span class="identifier">a</span></tt> one
+<td>
+ <p>
+ <code class="computeroutput"><span class="special">+</span><span class="identifier">a</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">vector</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">&gt;</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Plus. Parse <code class="computeroutput"><span class="identifier">a</span></code> one
                   or more times
- </p></td>
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">a</span> <span class="special">|</span>
+ <span class="identifier">b</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">variant</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">,</span>
+ <span class="identifier">B</span><span class="special">&gt;</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Alternative. Parse <code class="computeroutput"><span class="identifier">a</span></code>
+ or <code class="computeroutput"><span class="identifier">b</span></code>
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">a</span> <span class="special">&gt;&gt;</span>
+ <span class="identifier">b</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">tuple</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">,</span>
+ <span class="identifier">B</span><span class="special">&gt;</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Sequence. Parse <code class="computeroutput"><span class="identifier">a</span></code>
+ followed by <code class="computeroutput"><span class="identifier">b</span></code>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">a</span> <span class="special">|</span>
- <span class="identifier">b</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">variant</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">,</span>
- <span class="identifier">B</span><span class="special">&gt;</span></tt>
- </p></td>
-<td><p>
- Alternative. Parse <tt class="computeroutput"><span class="identifier">a</span></tt>
- or <tt class="computeroutput"><span class="identifier">b</span></tt>
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">a</span> <span class="special">&gt;&gt;</span>
- <span class="identifier">b</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">tuple</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">,</span>
- <span class="identifier">B</span><span class="special">&gt;</span></tt>
- </p></td>
-<td><p>
- Sequence. Parse <tt class="computeroutput"><span class="identifier">a</span></tt>
- followed by <tt class="computeroutput"><span class="identifier">b</span></tt>
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">a</span> <span class="special">&gt;</span>
- <span class="identifier">b</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">tuple</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">,</span>
- <span class="identifier">B</span><span class="special">&gt;</span></tt>
- </p></td>
-<td><p>
- Expect. Parse <tt class="computeroutput"><span class="identifier">a</span></tt>
- followed by <tt class="computeroutput"><span class="identifier">b</span></tt>.
- <tt class="computeroutput"><span class="identifier">b</span></tt> is expected to
- match when <tt class="computeroutput"><span class="identifier">a</span></tt> matches,
- otherwise, an <tt class="computeroutput"><span class="identifier">expectation_failure</span></tt>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">a</span> <span class="special">&gt;</span>
+ <span class="identifier">b</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">tuple</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">,</span>
+ <span class="identifier">B</span><span class="special">&gt;</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Expect. Parse <code class="computeroutput"><span class="identifier">a</span></code>
+ followed by <code class="computeroutput"><span class="identifier">b</span></code>.
+ <code class="computeroutput"><span class="identifier">b</span></code> is expected to
+ match when <code class="computeroutput"><span class="identifier">a</span></code> matches,
+ otherwise, an <code class="computeroutput"><span class="identifier">expectation_failure</span></code>
                   is thrown.
- </p></td>
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">a</span> <span class="special">-</span>
+ <span class="identifier">b</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">A</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Difference. Parse <code class="computeroutput"><span class="identifier">a</span></code>
+ but not <code class="computeroutput"><span class="identifier">b</span></code>
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">a</span> <span class="special">||</span>
+ <span class="identifier">b</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">tuple</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">,</span>
+ <span class="identifier">B</span><span class="special">&gt;</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Sequential Or. Parse <code class="computeroutput"><span class="identifier">a</span></code>
+ or <code class="computeroutput"><span class="identifier">b</span></code> or <code class="computeroutput"><span class="identifier">a</span></code> followed by <code class="computeroutput"><span class="identifier">b</span></code>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">a</span> <span class="special">-</span>
- <span class="identifier">b</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">A</span></tt>
- </p></td>
-<td><p>
- Difference. Parse <tt class="computeroutput"><span class="identifier">a</span></tt>
- but not <tt class="computeroutput"><span class="identifier">b</span></tt>
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">a</span> <span class="special">||</span>
- <span class="identifier">b</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">tuple</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">,</span>
- <span class="identifier">B</span><span class="special">&gt;</span></tt>
- </p></td>
-<td><p>
- Sequential Or. Parse <tt class="computeroutput"><span class="identifier">a</span></tt>
- or <tt class="computeroutput"><span class="identifier">b</span></tt> or <tt class="computeroutput"><span class="identifier">a</span></tt> followed by <tt class="computeroutput"><span class="identifier">b</span></tt>
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">a</span> <span class="special">%</span>
- <span class="identifier">b</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">vector</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">&gt;</span></tt>
- </p></td>
-<td><p>
- List. Parse <tt class="computeroutput"><span class="identifier">a</span></tt> delimited
- <tt class="computeroutput"><span class="identifier">b</span></tt> one or more times
- </p></td>
-</tr>
-<tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">a</span> <span class="special">^</span>
- <span class="identifier">b</span></tt>
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">tuple</span><span class="special">&lt;</span></tt>
- <tt class="computeroutput"><span class="identifier">optional</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">&gt;,</span></tt>
- <tt class="computeroutput"><span class="identifier">optional</span><span class="special">&lt;</span><span class="identifier">B</span><span class="special">&gt;</span>
- <span class="special">&gt;</span></tt>
- </p></td>
-<td><p>
- Permutation. Parse <tt class="computeroutput"><span class="identifier">a</span></tt>
- and <tt class="computeroutput"><span class="identifier">b</span></tt> in any order
- </p></td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">a</span> <span class="special">%</span>
+ <span class="identifier">b</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">vector</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">&gt;</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ List. Parse <code class="computeroutput"><span class="identifier">a</span></code> delimited
+ <code class="computeroutput"><span class="identifier">b</span></code> one or more times
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">a</span> <span class="special">^</span>
+ <span class="identifier">b</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">tuple</span><span class="special">&lt;</span></code>
+ <code class="computeroutput"><span class="identifier">optional</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">&gt;,</span></code>
+ <code class="computeroutput"><span class="identifier">optional</span><span class="special">&lt;</span><span class="identifier">B</span><span class="special">&gt;</span>
+ <span class="special">&gt;</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Permutation. Parse <code class="computeroutput"><span class="identifier">a</span></code>
+ and <code class="computeroutput"><span class="identifier">b</span></code> in any order
+ </p>
+ </td>
 </tr>
 </tbody>
 </table></div>

Modified: trunk/libs/spirit/doc/html/spirit/qi/quick_reference/semantic_actions.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/qi/quick_reference/semantic_actions.html (original)
+++ trunk/libs/spirit/doc/html/spirit/qi/quick_reference/semantic_actions.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -1,13 +1,12 @@
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title>Semantic
- Actions</title>
+<title>Semantic Actions</title>
 <link rel="stylesheet" href="../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../index.html" title="Spirit 2.1">
 <link rel="up" href="../quick_reference.html" title="Quick Reference">
-<link rel="previous" href="non_terminals.html" title="Non-terminals">
+<link rel="prev" href="non_terminals.html" title="Non-terminals">
 <link rel="next" href="phoenix.html" title="Phoenix">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -23,22 +22,18 @@
 <div class="spirit-nav">
 <a accesskey="p" href="non_terminals.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../quick_reference.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="phoenix.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h4 class="title">
-<a name="spirit.qi.quick_reference.semantic_actions"></a><a href="semantic_actions.html" title="Semantic
- Actions">Semantic
+<div class="section" title="Semantic Actions">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="spirit.qi.quick_reference.semantic_actions"></a><a class="link" href="semantic_actions.html" title="Semantic Actions">Semantic
         Actions</a>
-</h4></div></div>
-<div></div>
-</div>
+</h4></div></div></div>
 <p>
           Has the form:
         </p>
 <pre class="programlisting"><span class="identifier">p</span><span class="special">[</span><span class="identifier">f</span><span class="special">]</span>
 </pre>
 <p>
- where <tt class="computeroutput"><span class="identifier">f</span></tt> is a function with
+ where <code class="computeroutput"><span class="identifier">f</span></code> is a function with
           the signatures:
         </p>
 <pre class="programlisting"><span class="keyword">void</span> <span class="identifier">f</span><span class="special">(</span><span class="identifier">Attr</span> <span class="keyword">const</span><span class="special">&amp;);</span>
@@ -46,7 +41,7 @@
 <span class="keyword">void</span> <span class="identifier">f</span><span class="special">(</span><span class="identifier">Attr</span> <span class="keyword">const</span><span class="special">&amp;,</span> <span class="identifier">Context</span><span class="special">&amp;,</span> <span class="keyword">bool</span><span class="special">&amp;);</span>
 </pre>
 <p>
- You can use <tt class="computeroutput">Boost.Bind</tt>
+ You can use <code class="computeroutput">Boost.Bind</code>
           to bind member functions. For function objects, the allowed signatures
           are:
         </p>
@@ -55,7 +50,7 @@
 <span class="keyword">void</span> <span class="keyword">operator</span><span class="special">()(</span><span class="identifier">Attr</span> <span class="keyword">const</span><span class="special">&amp;,</span> <span class="identifier">Context</span><span class="special">&amp;,</span> <span class="keyword">bool</span><span class="special">&amp;)</span> <span class="keyword">const</span><span class="special">;</span>
 </pre>
 <p>
- The <tt class="computeroutput"><span class="identifier">unused_type</span></tt> is used
+ The <code class="computeroutput"><span class="identifier">unused_type</span></code> is used
           in the signatures above to signify 'don't care'.
         </p>
 </div>

Modified: trunk/libs/spirit/doc/html/spirit/qi/reference.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/qi/reference.html (original)
+++ trunk/libs/spirit/doc/html/spirit/qi/reference.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -3,10 +3,10 @@
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <title>Reference</title>
 <link rel="stylesheet" href="../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../index.html" title="Spirit 2.1">
-<link rel="up" href="../qi.html" title=" Qi">
-<link rel="previous" href="quick_reference/phoenix.html" title="Phoenix">
+<link rel="up" href="../qi.html" title="Qi">
+<link rel="prev" href="quick_reference/phoenix.html" title="Phoenix">
 <link rel="next" href="reference/parser_concepts.html" title="Parser Concepts">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -22,17 +22,14 @@
 <div class="spirit-nav">
 <a accesskey="p" href="quick_reference/phoenix.html"><img src="../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../qi.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="reference/parser_concepts.html"><img src="../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h3 class="title">
-<a name="spirit.qi.reference"></a>Reference
-</h3></div></div>
-<div></div>
-</div>
+<div class="section" title="Reference">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="spirit.qi.reference"></a><a class="link" href="reference.html" title="Reference">Reference</a>
+</h3></div></div></div>
 <div class="toc"><dl>
 <dt><span class="section">Parser Concepts</span></dt>
 <dt><span class="section">Basics</span></dt>
-<dt><span class="section">String</span></dt>
+<dt><span class="section">char_</span></dt>
 </dl></div>
 </div>
 <table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>

Modified: trunk/libs/spirit/doc/html/spirit/qi/reference/basics.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/qi/reference/basics.html (original)
+++ trunk/libs/spirit/doc/html/spirit/qi/reference/basics.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -3,11 +3,11 @@
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <title>Basics</title>
 <link rel="stylesheet" href="../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../index.html" title="Spirit 2.1">
 <link rel="up" href="../reference.html" title="Reference">
-<link rel="previous" href="parser_concepts/naryparser.html" title="NaryParser">
-<link rel="next" href="string.html" title="String">
+<link rel="prev" href="parser_concepts/naryparser.html" title="NaryParser">
+<link rel="next" href="char_.html" title="char_">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
 <table cellpadding="2" width="100%"><tr>
@@ -20,19 +20,16 @@
 </tr></table>
 <hr>
 <div class="spirit-nav">
-<a accesskey="p" href="parser_concepts/naryparser.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../reference.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="string.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
+<a accesskey="p" href="parser_concepts/naryparser.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../reference.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="char_.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h4 class="title">
-<a name="spirit.qi.reference.basics"></a>Basics
-</h4></div></div>
-<div></div>
-</div>
-<a name="spirit.qi.reference.basics.lazy_argument"></a><h5>
-<a name="id454623"></a>
- Lazy Argument
- </h5>
+<div class="section" title="Basics">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="spirit.qi.reference.basics"></a><a class="link" href="basics.html" title="Basics">Basics</a>
+</h4></div></div></div>
+<a name="spirit.qi.reference.basics.lazy_argument"></a><h6>
+<a name="id1065642"></a>
+ <a class="link" href="basics.html#spirit.qi.reference.basics.lazy_argument">Lazy Argument</a>
+ </h6>
 <p>
           Some parsers (e.g. primitives and non-terminals) may take in additional
           attributes. Such parsers take the form:
@@ -40,39 +37,39 @@
 <pre class="programlisting"><span class="identifier">p</span><span class="special">(</span><span class="identifier">a1</span><span class="special">,</span> <span class="identifier">a2</span><span class="special">,...</span> <span class="identifier">aN</span><span class="special">)</span>
 </pre>
 <p>
- where <tt class="computeroutput"><span class="identifier">p</span></tt> is a parser. Each
+ where <code class="computeroutput"><span class="identifier">p</span></code> is a parser. Each
           of the arguments (a1...aN) can either be an immediate value, or a function,
- <tt class="computeroutput"><span class="identifier">f</span></tt>, with signature:
+ <code class="computeroutput"><span class="identifier">f</span></code>, with signature:
         </p>
 <pre class="programlisting"><span class="identifier">T</span> <span class="identifier">f</span><span class="special">(</span><span class="identifier">Unused</span><span class="special">,</span> <span class="identifier">Context</span><span class="special">)</span>
 </pre>
 <p>
- where <tt class="computeroutput"><span class="identifier">T</span></tt>, the function's
- return value, is compatible with the argument type expected and <tt class="computeroutput"><span class="identifier">Context</span></tt> is the parser's Context type
- (The first argument is <tt class="computeroutput"><span class="identifier">unused</span></tt>
- to make the <tt class="computeroutput"><span class="identifier">Context</span></tt> the
+ where <code class="computeroutput"><span class="identifier">T</span></code>, the function's
+ return value, is compatible with the argument type expected and <code class="computeroutput"><span class="identifier">Context</span></code> is the parser's Context type
+ (The first argument is <code class="computeroutput"><span class="identifier">unused</span></code>
+ to make the <code class="computeroutput"><span class="identifier">Context</span></code> the
           second argument. This is done for uniformity with Semantic Actions).
         </p>
-<a name="spirit.qi.reference.basics.character_encoding_namespace"></a><h5>
-<a name="id454832"></a>
- <a href="basics.html#spirit.qi.reference.basics.character_encoding_namespace">Character
+<a name="spirit.qi.reference.basics.character_encoding_namespace"></a><h6>
+<a name="id1065779"></a>
+ <a class="link" href="basics.html#spirit.qi.reference.basics.character_encoding_namespace">Character
           Encoding Namespace</a>
- </h5>
+ </h6>
 <p>
- Some parsers need to know which character set a <tt class="computeroutput"><span class="keyword">char</span></tt>
- or <tt class="computeroutput"><span class="keyword">wchar_t</span></tt> is operating on.
- For example, the <tt class="computeroutput"><span class="identifier">alnum</span></tt>
+ Some parsers need to know which character set a <code class="computeroutput"><span class="keyword">char</span></code>
+ or <code class="computeroutput"><span class="keyword">wchar_t</span></code> is operating on.
+ For example, the <code class="computeroutput"><span class="identifier">alnum</span></code>
           parser works differently with ISO8859.1 and ASCII encodings. Where necessary,
           Spirit encodes (tags) the parser with the character set.
         </p>
 <p>
           We have a namespace for each character set Spirit will be supporting. That
- includes <tt class="computeroutput"><span class="identifier">ascii</span></tt>, <tt class="computeroutput"><span class="identifier">iso8859_1</span></tt>, <tt class="computeroutput"><span class="identifier">standard</span></tt>
- and <tt class="computeroutput"><span class="identifier">standard_wide</span></tt> (and
- in the future, <tt class="computeroutput"><span class="identifier">unicode</span></tt>).
+ includes <code class="computeroutput"><span class="identifier">ascii</span></code>, <code class="computeroutput"><span class="identifier">iso8859_1</span></code>, <code class="computeroutput"><span class="identifier">standard</span></code>
+ and <code class="computeroutput"><span class="identifier">standard_wide</span></code> (and
+ in the future, <code class="computeroutput"><span class="identifier">unicode</span></code>).
           In each of the character encoding namespaces, we place tagged versions
- of parsers such as <tt class="computeroutput"><span class="identifier">alnum</span></tt>,
- <tt class="computeroutput"><span class="identifier">space</span></tt> etc.
+ of parsers such as <code class="computeroutput"><span class="identifier">alnum</span></code>,
+ <code class="computeroutput"><span class="identifier">space</span></code> etc.
         </p>
 <p>
           Example:
@@ -82,17 +79,17 @@
 <p>
           Namespaces:
         </p>
-<div class="itemizedlist"><ul type="disc">
-<li>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem">
             boost::spirit::ascii
           </li>
-<li>
+<li class="listitem">
             boost::spirit::iso8859_1
           </li>
-<li>
+<li class="listitem">
             boost::spirit::standard
           </li>
-<li>
+<li class="listitem">
             boost::spirit::standard_wide
           </li>
 </ul></div>
@@ -100,17 +97,17 @@
           For ease of use, the components in this namespaces are also brought into
           the qi sub-namespaces with the same names:
         </p>
-<div class="itemizedlist"><ul type="disc">
-<li>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem">
             boost::spirit::qi::ascii
           </li>
-<li>
+<li class="listitem">
             boost::spirit::qi::iso8859_1
           </li>
-<li>
+<li class="listitem">
             boost::spirit::qi::standard
           </li>
-<li>
+<li class="listitem">
             boost::spirit::qi::standard_wide
           </li>
 </ul></div>
@@ -126,7 +123,7 @@
 </tr></table>
 <hr>
 <div class="spirit-nav">
-<a accesskey="p" href="parser_concepts/naryparser.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../reference.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="string.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
+<a accesskey="p" href="parser_concepts/naryparser.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../reference.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="char_.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
 </body>
 </html>

Modified: trunk/libs/spirit/doc/html/spirit/qi/reference/parser_concepts.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/qi/reference/parser_concepts.html (original)
+++ trunk/libs/spirit/doc/html/spirit/qi/reference/parser_concepts.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -3,10 +3,10 @@
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <title>Parser Concepts</title>
 <link rel="stylesheet" href="../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../index.html" title="Spirit 2.1">
 <link rel="up" href="../reference.html" title="Reference">
-<link rel="previous" href="../reference.html" title="Reference">
+<link rel="prev" href="../reference.html" title="Reference">
 <link rel="next" href="parser_concepts/parser.html" title="Parser">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -22,13 +22,10 @@
 <div class="spirit-nav">
 <a accesskey="p" href="../reference.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../reference.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="parser_concepts/parser.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h4 class="title">
-<a name="spirit.qi.reference.parser_concepts"></a>Parser Concepts
-</h4></div></div>
-<div></div>
-</div>
+<div class="section" title="Parser Concepts">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="spirit.qi.reference.parser_concepts"></a><a class="link" href="parser_concepts.html" title="Parser Concepts">Parser Concepts</a>
+</h4></div></div></div>
 <div class="toc"><dl>
 <dt><span class="section">Parser</span></dt>
 <dt><span class="section">PrimitiveParser</span></dt>

Modified: trunk/libs/spirit/doc/html/spirit/qi/reference/parser_concepts/binaryparser.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/qi/reference/parser_concepts/binaryparser.html (original)
+++ trunk/libs/spirit/doc/html/spirit/qi/reference/parser_concepts/binaryparser.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -3,10 +3,10 @@
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <title>BinaryParser</title>
 <link rel="stylesheet" href="../../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../../index.html" title="Spirit 2.1">
 <link rel="up" href="../parser_concepts.html" title="Parser Concepts">
-<link rel="previous" href="unaryparser.html" title="UnaryParser">
+<link rel="prev" href="unaryparser.html" title="UnaryParser">
 <link rel="next" href="naryparser.html" title="NaryParser">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -22,57 +22,54 @@
 <div class="spirit-nav">
 <a accesskey="p" href="unaryparser.html"><img src="../../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../parser_concepts.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="naryparser.html"><img src="../../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h5 class="title">
-<a name="spirit.qi.reference.parser_concepts.binaryparser"></a>BinaryParser
-</h5></div></div>
-<div></div>
-</div>
+<div class="section" title="BinaryParser">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="spirit.qi.reference.parser_concepts.binaryparser"></a><a class="link" href="binaryparser.html" title="BinaryParser">BinaryParser</a>
+</h5></div></div></div>
 <a name="spirit.qi.reference.parser_concepts.binaryparser.description"></a><h6>
-<a name="id452966"></a>
- Description
+<a name="id1064312"></a>
+ <a class="link" href="binaryparser.html#spirit.qi.reference.parser_concepts.binaryparser.description">Description</a>
           </h6>
 <p>
             <span class="emphasis"><em>BinaryParser</em></span> is a composite parser that has a two
- subjects, <tt class="computeroutput"><span class="identifier">left</span></tt> and <tt class="computeroutput"><span class="identifier">right</span></tt>. The BinaryParser allows its
- subjects to be treated in the same way as a single instance of a Parser
+ subjects, <code class="computeroutput"><span class="identifier">left</span></code> and <code class="computeroutput"><span class="identifier">right</span></code>. The BinaryParser allows its
+ subjects to be treated in the same way as a single instance of a <a class="link" href="parser.html" title="Parser"><code class="computeroutput"><span class="identifier">Parser</span></code></a>
             following the Composite Design Pattern.
           </p>
 <a name="spirit.qi.reference.parser_concepts.binaryparser.refinement_of"></a><h6>
-<a name="id453044"></a>
- <a href="binaryparser.html#spirit.qi.reference.parser_concepts.binaryparser.refinement_of">Refinement
+<a name="id1064364"></a>
+ <a class="link" href="binaryparser.html#spirit.qi.reference.parser_concepts.binaryparser.refinement_of">Refinement
             of</a>
           </h6>
 <div class="blockquote"><blockquote class="blockquote">
 <p>
               </p>
 <p>
- Parser
+ <a class="link" href="parser.html" title="Parser"><code class="computeroutput"><span class="identifier">Parser</span></code></a>
               </p>
 <p>
             </p>
 </blockquote></div>
-<div class="variablelist">
+<div class="variablelist" title="Notation">
 <p class="title"><b>Notation</b></p>
 <dl>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">p</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">p</span></code></span></dt>
 <dd><p>
                 A BinaryParser.
               </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">P</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">P</span></code></span></dt>
 <dd><p>
                 A BinaryParser type.
               </p></dd>
 </dl>
 </div>
 <a name="spirit.qi.reference.parser_concepts.binaryparser.valid_expressions"></a><h6>
-<a name="id453152"></a>
- <a href="binaryparser.html#spirit.qi.reference.parser_concepts.binaryparser.valid_expressions">Valid
+<a name="id1064443"></a>
+ <a class="link" href="binaryparser.html#spirit.qi.reference.parser_concepts.binaryparser.valid_expressions">Valid
             Expressions</a>
           </h6>
 <p>
- In addition to the requirements defined in Parser, for any BinaryParser
+ In addition to the requirements defined in <a class="link" href="parser.html" title="Parser"><code class="computeroutput"><span class="identifier">Parser</span></code></a>, for any BinaryParser
             the following must be met:
           </p>
 <div class="informaltable"><table class="table">
@@ -82,44 +79,62 @@
 <col>
 </colgroup>
 <thead><tr>
-<th><p>
+<th>
+ <p>
                     Expression
- </p></th>
-<th><p>
+ </p>
+ </th>
+<th>
+ <p>
                     Semantics
- </p></th>
-<th><p>
+ </p>
+ </th>
+<th>
+ <p>
                     Return type
- </p></th>
+ </p>
+ </th>
 </tr></thead>
 <tbody>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">p</span><span class="special">.</span><span class="identifier">left</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">p</span><span class="special">.</span><span class="identifier">left</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                     Left parser.
- </p></td>
-<td><p>
- Parser
- </p></td>
+ </p>
+ </td>
+<td>
+ <p>
+ <a class="link" href="parser.html" title="Parser"><code class="computeroutput"><span class="identifier">Parser</span></code></a>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">p</span><span class="special">.</span><span class="identifier">right</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">p</span><span class="special">.</span><span class="identifier">right</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                     Right parser.
- </p></td>
-<td><p>
- Parser
- </p></td>
+ </p>
+ </td>
+<td>
+ <p>
+ <a class="link" href="parser.html" title="Parser"><code class="computeroutput"><span class="identifier">Parser</span></code></a>
+ </p>
+ </td>
 </tr>
 </tbody>
 </table></div>
 <a name="spirit.qi.reference.parser_concepts.binaryparser.type_expressions"></a><h6>
-<a name="id453372"></a>
- <a href="binaryparser.html#spirit.qi.reference.parser_concepts.binaryparser.type_expressions">Type
+<a name="id1064604"></a>
+ <a class="link" href="binaryparser.html#spirit.qi.reference.parser_concepts.binaryparser.type_expressions">Type
             Expressions</a>
           </h6>
 <div class="informaltable"><table class="table">
@@ -128,66 +143,82 @@
 <col>
 </colgroup>
 <thead><tr>
-<th><p>
+<th>
+ <p>
                     Expression
- </p></th>
-<th><p>
+ </p>
+ </th>
+<th>
+ <p>
                     Description
- </p></th>
+ </p>
+ </th>
 </tr></thead>
 <tbody>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">P</span><span class="special">::</span><span class="identifier">left_type</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">P</span><span class="special">::</span><span class="identifier">left_type</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                     The left parser type.
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">P</span><span class="special">::</span><span class="identifier">right_type</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">P</span><span class="special">::</span><span class="identifier">right_type</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                     The right parser type.
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">traits</span><span class="special">::</span><span class="identifier">is_binary_parser</span><span class="special">&lt;</span><span class="identifier">P</span><span class="special">&gt;::</span><span class="identifier">type</span></tt>
- </p></td>
-<td><p>
- Metafunction that evaluates to <tt class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">true_</span></tt>
- if a certain type, <tt class="computeroutput"><span class="identifier">P</span></tt>
- is a BinaryParser, <tt class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">false_</span></tt>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">traits</span><span class="special">::</span><span class="identifier">is_binary_parser</span><span class="special">&lt;</span><span class="identifier">P</span><span class="special">&gt;::</span><span class="identifier">type</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Metafunction that evaluates to <code class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">true_</span></code>
+ if a certain type, <code class="computeroutput"><span class="identifier">P</span></code>
+ is a BinaryParser, <code class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">false_</span></code>
                     otherwise (See <a href="http://www.boost.org/libs/mpl/doc/refmanual/integral-constant.html" target="_top">MPL
                     Boolean Constant</a>).
- </p></td>
+ </p>
+ </td>
 </tr>
 </tbody>
 </table></div>
 <a name="spirit.qi.reference.parser_concepts.binaryparser.invariants"></a><h6>
-<a name="id453636"></a>
- Invariants
+<a name="id1064804"></a>
+ <a class="link" href="binaryparser.html#spirit.qi.reference.parser_concepts.binaryparser.invariants">Invariants</a>
           </h6>
 <p>
- For any BinaryParser, <tt class="computeroutput"><span class="identifier">P</span></tt>,
+ For any BinaryParser, <code class="computeroutput"><span class="identifier">P</span></code>,
             the following invariants always hold:
           </p>
-<div class="itemizedlist"><ul type="disc">
-<li>
-<tt class="computeroutput"><span class="identifier">traits</span><span class="special">::</span><span class="identifier">is_parser</span><span class="special">&lt;</span><span class="identifier">P</span><span class="special">::</span><span class="identifier">left_type</span><span class="special">&gt;::</span><span class="identifier">type</span></tt> evaluates to <tt class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">true_</span></tt>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem">
+<code class="computeroutput"><span class="identifier">traits</span><span class="special">::</span><span class="identifier">is_parser</span><span class="special">&lt;</span><span class="identifier">P</span><span class="special">::</span><span class="identifier">left_type</span><span class="special">&gt;::</span><span class="identifier">type</span></code> evaluates to <code class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">true_</span></code>
 </li>
-<li>
-<tt class="computeroutput"><span class="identifier">traits</span><span class="special">::</span><span class="identifier">is_parser</span><span class="special">&lt;</span><span class="identifier">P</span><span class="special">::</span><span class="identifier">right_type</span><span class="special">&gt;::</span><span class="identifier">type</span></tt> evaluates to <tt class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">true_</span></tt>
+<li class="listitem">
+<code class="computeroutput"><span class="identifier">traits</span><span class="special">::</span><span class="identifier">is_parser</span><span class="special">&lt;</span><span class="identifier">P</span><span class="special">::</span><span class="identifier">right_type</span><span class="special">&gt;::</span><span class="identifier">type</span></code> evaluates to <code class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">true_</span></code>
 </li>
 </ul></div>
 <a name="spirit.qi.reference.parser_concepts.binaryparser.models"></a><h6>
-<a name="id453836"></a>
- Models
+<a name="id1064944"></a>
+ <a class="link" href="binaryparser.html#spirit.qi.reference.parser_concepts.binaryparser.models">Models</a>
           </h6>
 <p>
- <span class="bold"><b>FIXME</b></span> Add links to models of BinaryParser
+ <span class="bold"><strong>FIXME</strong></span> Add links to models of BinaryParser
             concept
           </p>
 </div>

Modified: trunk/libs/spirit/doc/html/spirit/qi/reference/parser_concepts/naryparser.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/qi/reference/parser_concepts/naryparser.html (original)
+++ trunk/libs/spirit/doc/html/spirit/qi/reference/parser_concepts/naryparser.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -3,10 +3,10 @@
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <title>NaryParser</title>
 <link rel="stylesheet" href="../../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../../index.html" title="Spirit 2.1">
 <link rel="up" href="../parser_concepts.html" title="Parser Concepts">
-<link rel="previous" href="binaryparser.html" title="BinaryParser">
+<link rel="prev" href="binaryparser.html" title="BinaryParser">
 <link rel="next" href="../basics.html" title="Basics">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -22,57 +22,54 @@
 <div class="spirit-nav">
 <a accesskey="p" href="binaryparser.html"><img src="../../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../parser_concepts.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>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h5 class="title">
-<a name="spirit.qi.reference.parser_concepts.naryparser"></a>NaryParser
-</h5></div></div>
-<div></div>
-</div>
+<div class="section" title="NaryParser">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="spirit.qi.reference.parser_concepts.naryparser"></a><a class="link" href="naryparser.html" title="NaryParser">NaryParser</a>
+</h5></div></div></div>
 <a name="spirit.qi.reference.parser_concepts.naryparser.description"></a><h6>
-<a name="id453892"></a>
- Description
+<a name="id1064978"></a>
+ <a class="link" href="naryparser.html#spirit.qi.reference.parser_concepts.naryparser.description">Description</a>
           </h6>
 <p>
             <span class="emphasis"><em>NaryParser</em></span> is a composite parser that has one or
             more subjects. The NaryParser allows its subjects to be treated in the
- same way as a single instance of a Parser following the Composite
+ same way as a single instance of a <a class="link" href="parser.html" title="Parser"><code class="computeroutput"><span class="identifier">Parser</span></code></a> following the Composite
             Design Pattern.
           </p>
 <a name="spirit.qi.reference.parser_concepts.naryparser.refinement_of"></a><h6>
-<a name="id453946"></a>
- <a href="naryparser.html#spirit.qi.reference.parser_concepts.naryparser.refinement_of">Refinement
+<a name="id1065014"></a>
+ <a class="link" href="naryparser.html#spirit.qi.reference.parser_concepts.naryparser.refinement_of">Refinement
             of</a>
           </h6>
 <div class="blockquote"><blockquote class="blockquote">
 <p>
               </p>
 <p>
- Parser
+ <a class="link" href="parser.html" title="Parser"><code class="computeroutput"><span class="identifier">Parser</span></code></a>
               </p>
 <p>
             </p>
 </blockquote></div>
-<div class="variablelist">
+<div class="variablelist" title="Notation">
 <p class="title"><b>Notation</b></p>
 <dl>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">p</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">p</span></code></span></dt>
 <dd><p>
                 A NaryParser.
               </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">P</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">P</span></code></span></dt>
 <dd><p>
                 A NaryParser type.
               </p></dd>
 </dl>
 </div>
 <a name="spirit.qi.reference.parser_concepts.naryparser.valid_expressions"></a><h6>
-<a name="id454053"></a>
- <a href="naryparser.html#spirit.qi.reference.parser_concepts.naryparser.valid_expressions">Valid
+<a name="id1065094"></a>
+ <a class="link" href="naryparser.html#spirit.qi.reference.parser_concepts.naryparser.valid_expressions">Valid
             Expressions</a>
           </h6>
 <p>
- In addition to the requirements defined in Parser, for any NaryParser the
+ In addition to the requirements defined in <a class="link" href="parser.html" title="Parser"><code class="computeroutput"><span class="identifier">Parser</span></code></a>, for any NaryParser the
             following must be met:
           </p>
 <div class="informaltable"><table class="table">
@@ -82,32 +79,44 @@
 <col>
 </colgroup>
 <thead><tr>
-<th><p>
+<th>
+ <p>
                     Expression
- </p></th>
-<th><p>
+ </p>
+ </th>
+<th>
+ <p>
                     Semantics
- </p></th>
-<th><p>
+ </p>
+ </th>
+<th>
+ <p>
                     Return type
- </p></th>
+ </p>
+ </th>
 </tr></thead>
 <tbody><tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">p</span><span class="special">.</span><span class="identifier">elements</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">p</span><span class="special">.</span><span class="identifier">elements</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                     The tuple of elements.
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
                     A Fusion
- Sequence of Parser types.
- </p></td>
+ Sequence of <a class="link" href="parser.html" title="Parser"><code class="computeroutput"><span class="identifier">Parser</span></code></a> types.
+ </p>
+ </td>
 </tr></tbody>
 </table></div>
 <a name="spirit.qi.reference.parser_concepts.naryparser.type_expressions"></a><h6>
-<a name="id454218"></a>
- <a href="naryparser.html#spirit.qi.reference.parser_concepts.naryparser.type_expressions">Type
+<a name="id1065216"></a>
+ <a class="link" href="naryparser.html#spirit.qi.reference.parser_concepts.naryparser.type_expressions">Type
             Expressions</a>
           </h6>
 <div class="informaltable"><table class="table">
@@ -116,54 +125,66 @@
 <col>
 </colgroup>
 <thead><tr>
-<th><p>
+<th>
+ <p>
                     Expression
- </p></th>
-<th><p>
+ </p>
+ </th>
+<th>
+ <p>
                     Description
- </p></th>
+ </p>
+ </th>
 </tr></thead>
 <tbody>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">p</span><span class="special">.</span><span class="identifier">elements_type</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">p</span><span class="special">.</span><span class="identifier">elements_type</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                     Elements tuple type.
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">traits</span><span class="special">::</span><span class="identifier">is_nary_parser</span><span class="special">&lt;</span><span class="identifier">P</span><span class="special">&gt;::</span><span class="identifier">type</span></tt>
- </p></td>
-<td><p>
- Metafunction that evaluates to <tt class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">true_</span></tt>
- if a certain type, <tt class="computeroutput"><span class="identifier">P</span></tt>
- is a NaryParser, <tt class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">false_</span></tt>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">traits</span><span class="special">::</span><span class="identifier">is_nary_parser</span><span class="special">&lt;</span><span class="identifier">P</span><span class="special">&gt;::</span><span class="identifier">type</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Metafunction that evaluates to <code class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">true_</span></code>
+ if a certain type, <code class="computeroutput"><span class="identifier">P</span></code>
+ is a NaryParser, <code class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">false_</span></code>
                     otherwise (See <a href="http://www.boost.org/libs/mpl/doc/refmanual/integral-constant.html" target="_top">MPL
                     Boolean Constant</a>).
- </p></td>
+ </p>
+ </td>
 </tr>
 </tbody>
 </table></div>
 <a name="spirit.qi.reference.parser_concepts.naryparser.invariants"></a><h6>
-<a name="id454443"></a>
- Invariants
+<a name="id1065386"></a>
+ <a class="link" href="naryparser.html#spirit.qi.reference.parser_concepts.naryparser.invariants">Invariants</a>
           </h6>
 <p>
- For each element, <tt class="computeroutput"><span class="identifier">E</span></tt>,
- in any NaryParser, <tt class="computeroutput"><span class="identifier">P</span></tt>,
+ For each element, <code class="computeroutput"><span class="identifier">E</span></code>,
+ in any NaryParser, <code class="computeroutput"><span class="identifier">P</span></code>,
             the following invariant always holds:
           </p>
-<div class="itemizedlist"><ul type="disc"><li>
-<tt class="computeroutput"><span class="identifier">traits</span><span class="special">::</span><span class="identifier">is_parser</span><span class="special">&lt;</span><span class="identifier">E</span><span class="special">&gt;::</span><span class="identifier">type</span></tt> evaluates to <tt class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">true_</span></tt>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">
+<code class="computeroutput"><span class="identifier">traits</span><span class="special">::</span><span class="identifier">is_parser</span><span class="special">&lt;</span><span class="identifier">E</span><span class="special">&gt;::</span><span class="identifier">type</span></code> evaluates to <code class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">true_</span></code>
 </li></ul></div>
 <a name="spirit.qi.reference.parser_concepts.naryparser.models"></a><h6>
-<a name="id454569"></a>
- Models
+<a name="id1065609"></a>
+ <a class="link" href="naryparser.html#spirit.qi.reference.parser_concepts.naryparser.models">Models</a>
           </h6>
 <p>
- <span class="bold"><b>FIXME</b></span> Add links to models of NaryParser
+ <span class="bold"><strong>FIXME</strong></span> Add links to models of NaryParser
             concept
           </p>
 </div>

Modified: trunk/libs/spirit/doc/html/spirit/qi/reference/parser_concepts/parser.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/qi/reference/parser_concepts/parser.html (original)
+++ trunk/libs/spirit/doc/html/spirit/qi/reference/parser_concepts/parser.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -3,10 +3,10 @@
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <title>Parser</title>
 <link rel="stylesheet" href="../../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../../index.html" title="Spirit 2.1">
 <link rel="up" href="../parser_concepts.html" title="Parser Concepts">
-<link rel="previous" href="../parser_concepts.html" title="Parser Concepts">
+<link rel="prev" href="../parser_concepts.html" title="Parser Concepts">
 <link rel="next" href="primitiveparser.html" title="PrimitiveParser">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -22,77 +22,74 @@
 <div class="spirit-nav">
 <a accesskey="p" href="../parser_concepts.html"><img src="../../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../parser_concepts.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="primitiveparser.html"><img src="../../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h5 class="title">
-<a name="spirit.qi.reference.parser_concepts.parser"></a>Parser
-</h5></div></div>
-<div></div>
-</div>
+<div class="section" title="Parser">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="spirit.qi.reference.parser_concepts.parser"></a><a class="link" href="parser.html" title="Parser">Parser</a>
+</h5></div></div></div>
 <a name="spirit.qi.reference.parser_concepts.parser.description"></a><h6>
-<a name="id450528"></a>
- Description
+<a name="id1062040"></a>
+ <a class="link" href="parser.html#spirit.qi.reference.parser_concepts.parser.description">Description</a>
           </h6>
 <p>
             The <span class="emphasis"><em>Parser</em></span> is the most fundamental concept. A Parser
- has a member function, <tt class="computeroutput"><span class="identifier">parse</span></tt>,
- that accepts a first-last <tt class="computeroutput"><span class="identifier">ForwardIterator</span></tt>
+ has a member function, <code class="computeroutput"><span class="identifier">parse</span></code>,
+ that accepts a first-last <code class="computeroutput"><span class="identifier">ForwardIterator</span></code>
             pair and returns bool as its result. The iterators delimit the data being
- parsed. The Parser's <tt class="computeroutput"><span class="identifier">parse</span></tt>
- member function returns <tt class="computeroutput"><span class="keyword">true</span></tt>
+ parsed. The Parser's <code class="computeroutput"><span class="identifier">parse</span></code>
+ member function returns <code class="computeroutput"><span class="keyword">true</span></code>
             if the parse succeeds, in which case the first iterator is advanced accordingly.
             Each Parser can represent a specific pattern or algorithm, or it can
             be a more complex parser formed as a composition of other Parsers.
           </p>
-<div class="variablelist">
+<div class="variablelist" title="Notation">
 <p class="title"><b>Notation</b></p>
 <dl>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">p</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">p</span></code></span></dt>
 <dd><p>
- A <tt class="computeroutput"><span class="identifier">Parser</span></tt>.
+ A <code class="computeroutput"><span class="identifier">Parser</span></code>.
               </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">P</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">P</span></code></span></dt>
 <dd><p>
- A <tt class="computeroutput"><span class="identifier">Parser</span></tt> type.
+ A <code class="computeroutput"><span class="identifier">Parser</span></code> type.
               </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">Iter</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">Iter</span></code></span></dt>
 <dd><p>
- a <tt class="computeroutput"><span class="identifier">ForwardIterator</span></tt>
+ a <code class="computeroutput"><span class="identifier">ForwardIterator</span></code>
                 type.
               </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">f</span></tt>,
- <tt class="computeroutput"><span class="identifier">l</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">f</span></code>,
+ <code class="computeroutput"><span class="identifier">l</span></code></span></dt>
 <dd><p>
- <tt class="computeroutput"><span class="identifier">ForwardIterator</span></tt>.
+ <code class="computeroutput"><span class="identifier">ForwardIterator</span></code>.
                 first/last iterator pair.
               </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">Context</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">Context</span></code></span></dt>
 <dd><p>
                 The parser's Context type.
               </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">context</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">context</span></code></span></dt>
 <dd><p>
- The parser's Context, or <tt class="computeroutput"><span class="identifier">unused</span></tt>.
+ The parser's Context, or <code class="computeroutput"><span class="identifier">unused</span></code>.
               </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">skip</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">skip</span></code></span></dt>
 <dd><p>
- A skip Parser, or <tt class="computeroutput"><span class="identifier">unused</span></tt>.
+ A skip Parser, or <code class="computeroutput"><span class="identifier">unused</span></code>.
               </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">attr</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">attr</span></code></span></dt>
 <dd><p>
- A Compatible Attribute, or <tt class="computeroutput"><span class="identifier">unused</span></tt>.
+ A Compatible Attribute, or <code class="computeroutput"><span class="identifier">unused</span></code>.
               </p></dd>
 </dl>
 </div>
 <a name="spirit.qi.reference.parser_concepts.parser.valid_expressions"></a><h6>
-<a name="id450902"></a>
- <a href="parser.html#spirit.qi.reference.parser_concepts.parser.valid_expressions">Valid
+<a name="id1062303"></a>
+ <a class="link" href="parser.html#spirit.qi.reference.parser_concepts.parser.valid_expressions">Valid
             Expressions</a>
           </h6>
 <p>
- In the expressions below, the behavior of the parser, <tt class="computeroutput"><span class="identifier">p</span></tt>,
- how <tt class="computeroutput"><span class="identifier">skip</span></tt> and <tt class="computeroutput"><span class="identifier">attr</span></tt> are handled by <tt class="computeroutput"><span class="identifier">p</span></tt>,
- are left unspecified in the base <tt class="computeroutput"><span class="identifier">Parser</span></tt>
+ In the expressions below, the behavior of the parser, <code class="computeroutput"><span class="identifier">p</span></code>,
+ how <code class="computeroutput"><span class="identifier">skip</span></code> and <code class="computeroutput"><span class="identifier">attr</span></code> are handled by <code class="computeroutput"><span class="identifier">p</span></code>,
+ are left unspecified in the base <code class="computeroutput"><span class="identifier">Parser</span></code>
             concept. These are specified in subsequent, more refined concepts and
             by the actual models therof.
           </p>
@@ -106,51 +103,67 @@
 <col>
 </colgroup>
 <thead><tr>
-<th><p>
+<th>
+ <p>
                     Expression
- </p></th>
-<th><p>
+ </p>
+ </th>
+<th>
+ <p>
                     Semantics
- </p></th>
-<th><p>
+ </p>
+ </th>
+<th>
+ <p>
                     Return type
- </p></th>
+ </p>
+ </th>
 </tr></thead>
 <tbody>
 <tr>
 <td>
-<p>
+ <p>
                     
 </p>
 <pre xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="table-programlisting"><span class="identifier">p</span><span class="special">.</span><span class="identifier">parse</span><span class="special">(</span><span class="identifier">f</span><span class="special">,</span> <span class="identifier">l</span><span class="special">,</span> <span class="identifier">context</span><span class="special">,</span> <span class="identifier">skip</span><span class="special">,</span> <span class="identifier">attr</span><span class="special">)</span></pre>
 <p>
                   </p>
-</td>
-<td><p>
- Match the input sequence starting from <tt class="computeroutput"><span class="identifier">f</span></tt>.
- Return <tt class="computeroutput"><span class="keyword">true</span></tt> if successful,
- otherwise return <tt class="computeroutput"><span class="keyword">false</span></tt>.
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="keyword">bool</span></tt>
- </p></td>
+ </td>
+<td>
+ <p>
+ Match the input sequence starting from <code class="computeroutput"><span class="identifier">f</span></code>.
+ Return <code class="computeroutput"><span class="keyword">true</span></code> if successful,
+ otherwise return <code class="computeroutput"><span class="keyword">false</span></code>.
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="keyword">bool</span></code>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">p</span><span class="special">.</span><span class="identifier">what</span><span class="special">(</span><span class="identifier">context</span><span class="special">)</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">p</span><span class="special">.</span><span class="identifier">what</span><span class="special">(</span><span class="identifier">context</span><span class="special">)</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                     Get information about a Parser.
- </p></td>
-<td><p>
- <tt class="computeroutput"><span class="identifier">info</span></tt>
- </p></td>
+ </p>
+ </td>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">info</span></code>
+ </p>
+ </td>
 </tr>
 </tbody>
 </table></div>
 <a name="spirit.qi.reference.parser_concepts.parser.type_expressions"></a><h6>
-<a name="id451266"></a>
- <a href="parser.html#spirit.qi.reference.parser_concepts.parser.type_expressions">Type
+<a name="id1062571"></a>
+ <a class="link" href="parser.html#spirit.qi.reference.parser_concepts.parser.type_expressions">Type
             Expressions</a>
           </h6>
 <div class="informaltable"><table class="table">
@@ -159,73 +172,85 @@
 <col>
 </colgroup>
 <thead><tr>
-<th><p>
+<th>
+ <p>
                     Expression
- </p></th>
-<th><p>
+ </p>
+ </th>
+<th>
+ <p>
                     Description
- </p></th>
+ </p>
+ </th>
 </tr></thead>
 <tbody>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">P</span><span class="special">::</span><span class="keyword">template</span> <span class="identifier">attribute</span><span class="special">&lt;</span><span class="identifier">Context</span><span class="special">,</span> <span class="identifier">Iter</span><span class="special">&gt;::</span><span class="identifier">type</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">P</span><span class="special">::</span><span class="keyword">template</span> <span class="identifier">attribute</span><span class="special">&lt;</span><span class="identifier">Context</span><span class="special">,</span> <span class="identifier">Iter</span><span class="special">&gt;::</span><span class="identifier">type</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                     The Parser's expected attribute.
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">traits</span><span class="special">::</span><span class="identifier">is_parser</span><span class="special">&lt;</span><span class="identifier">P</span><span class="special">&gt;::</span><span class="identifier">type</span></tt>
- </p></td>
-<td><p>
- Metafunction that evaluates to <tt class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">true_</span></tt>
- if a certain type, <tt class="computeroutput"><span class="identifier">P</span></tt>
- is a Parser, <tt class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">false_</span></tt>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">traits</span><span class="special">::</span><span class="identifier">is_parser</span><span class="special">&lt;</span><span class="identifier">P</span><span class="special">&gt;::</span><span class="identifier">type</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Metafunction that evaluates to <code class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">true_</span></code>
+ if a certain type, <code class="computeroutput"><span class="identifier">P</span></code>
+ is a Parser, <code class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">false_</span></code>
                     otherwise (See <a href="http://www.boost.org/libs/mpl/doc/refmanual/integral-constant.html" target="_top">MPL
                     Boolean Constant</a>).
- </p></td>
+ </p>
+ </td>
 </tr>
 </tbody>
 </table></div>
 <a name="spirit.qi.reference.parser_concepts.parser.postcondition"></a><h6>
-<a name="id451531"></a>
- Postcondition
+<a name="id1063319"></a>
+ <a class="link" href="parser.html#spirit.qi.reference.parser_concepts.parser.postcondition">Postcondition</a>
           </h6>
 <p>
- Upon return from <tt class="computeroutput"><span class="identifier">p</span><span class="special">.</span><span class="identifier">parse</span></tt> the following post conditions
+ Upon return from <code class="computeroutput"><span class="identifier">p</span><span class="special">.</span><span class="identifier">parse</span></code> the following post conditions
             should hold:
           </p>
-<div class="itemizedlist"><ul type="disc">
-<li>
- On a successful match, <tt class="computeroutput"><span class="identifier">f</span></tt>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem">
+ On a successful match, <code class="computeroutput"><span class="identifier">f</span></code>
               is positioned one past the first non-matching character/token.
             </li>
-<li>
- On a failed match, if a <tt class="computeroutput"><span class="identifier">skip</span></tt>
- parser is <tt class="computeroutput"><span class="identifier">unused</span></tt>,
- <tt class="computeroutput"><span class="identifier">f</span></tt> is restored to its
+<li class="listitem">
+ On a failed match, if a <code class="computeroutput"><span class="identifier">skip</span></code>
+ parser is <code class="computeroutput"><span class="identifier">unused</span></code>,
+ <code class="computeroutput"><span class="identifier">f</span></code> is restored to its
               original position prior to entry.
             </li>
-<li>
- On a failed match, if a <tt class="computeroutput"><span class="identifier">skip</span></tt>
- parser is not <tt class="computeroutput"><span class="identifier">unused</span></tt>,
- <tt class="computeroutput"><span class="identifier">f</span></tt> is positioned one
- past the first character/token not matching <tt class="computeroutput"><span class="identifier">skip</span></tt>.
+<li class="listitem">
+ On a failed match, if a <code class="computeroutput"><span class="identifier">skip</span></code>
+ parser is not <code class="computeroutput"><span class="identifier">unused</span></code>,
+ <code class="computeroutput"><span class="identifier">f</span></code> is positioned one
+ past the first character/token not matching <code class="computeroutput"><span class="identifier">skip</span></code>.
             </li>
-<li>
- On a failed match, <tt class="computeroutput"><span class="identifier">attr</span></tt>
+<li class="listitem">
+ On a failed match, <code class="computeroutput"><span class="identifier">attr</span></code>
               is left untouched.
             </li>
-<li>
- No post-skips: trailing <tt class="computeroutput"><span class="identifier">skip</span></tt>
+<li class="listitem">
+ No post-skips: trailing <code class="computeroutput"><span class="identifier">skip</span></code>
               characters/tokens will not be skipped.
             </li>
 </ul></div>
 <a name="spirit.qi.reference.parser_concepts.parser.models"></a><h6>
-<a name="id451733"></a>
- Models
+<a name="id1063446"></a>
+ <a class="link" href="parser.html#spirit.qi.reference.parser_concepts.parser.models">Models</a>
           </h6>
 <p>
             All parsers in Spirit.Qi are models of the <span class="emphasis"><em>Parser</em></span>

Modified: trunk/libs/spirit/doc/html/spirit/qi/reference/parser_concepts/primitiveparser.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/qi/reference/parser_concepts/primitiveparser.html (original)
+++ trunk/libs/spirit/doc/html/spirit/qi/reference/parser_concepts/primitiveparser.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -3,10 +3,10 @@
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <title>PrimitiveParser</title>
 <link rel="stylesheet" href="../../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../../index.html" title="Spirit 2.1">
 <link rel="up" href="../parser_concepts.html" title="Parser Concepts">
-<link rel="previous" href="parser.html" title="Parser">
+<link rel="prev" href="parser.html" title="Parser">
 <link rel="next" href="unaryparser.html" title="UnaryParser">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -22,52 +22,49 @@
 <div class="spirit-nav">
 <a accesskey="p" href="parser.html"><img src="../../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../parser_concepts.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="unaryparser.html"><img src="../../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h5 class="title">
-<a name="spirit.qi.reference.parser_concepts.primitiveparser"></a>PrimitiveParser
-</h5></div></div>
-<div></div>
-</div>
+<div class="section" title="PrimitiveParser">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="spirit.qi.reference.parser_concepts.primitiveparser"></a><a class="link" href="primitiveparser.html" title="PrimitiveParser">PrimitiveParser</a>
+</h5></div></div></div>
 <a name="spirit.qi.reference.parser_concepts.primitiveparser.description"></a><h6>
-<a name="id451788"></a>
- Description
+<a name="id1063481"></a>
+ <a class="link" href="primitiveparser.html#spirit.qi.reference.parser_concepts.primitiveparser.description">Description</a>
           </h6>
 <p>
             <span class="emphasis"><em>PrimitiveParser</em></span> is the most basic building block
             that the client uses to build more complex parsers.
           </p>
 <a name="spirit.qi.reference.parser_concepts.primitiveparser.refinement_of"></a><h6>
-<a name="id451824"></a>
- <a href="primitiveparser.html#spirit.qi.reference.parser_concepts.primitiveparser.refinement_of">Refinement
+<a name="id1063504"></a>
+ <a class="link" href="primitiveparser.html#spirit.qi.reference.parser_concepts.primitiveparser.refinement_of">Refinement
             of</a>
           </h6>
 <div class="blockquote"><blockquote class="blockquote">
 <p>
               </p>
 <p>
- Parser
+ <a class="link" href="parser.html" title="Parser"><code class="computeroutput"><span class="identifier">Parser</span></code></a>
               </p>
 <p>
             </p>
 </blockquote></div>
 <a name="spirit.qi.reference.parser_concepts.primitiveparser.pre_skip"></a><h6>
-<a name="id451878"></a>
- Pre-skip
+<a name="id1063540"></a>
+ <a class="link" href="primitiveparser.html#spirit.qi.reference.parser_concepts.primitiveparser.pre_skip">Pre-skip</a>
           </h6>
 <p>
- Upon entry to the <tt class="computeroutput"><span class="identifier">parse</span></tt>
+ Upon entry to the <code class="computeroutput"><span class="identifier">parse</span></code>
             member function, a PrimitiveParser is required to do a pre-skip. Leading
- <tt class="computeroutput"><span class="identifier">skip</span></tt> characters/tokens
+ <code class="computeroutput"><span class="identifier">skip</span></code> characters/tokens
             will be skipped prior to parsing. Only PrimitiveParsers are required
             to perform this pre-skip. This is typically carried out through a call
- to <tt class="computeroutput"><span class="identifier">qi</span><span class="special">::</span><span class="identifier">skip_over</span></tt>:
+ to <code class="computeroutput"><span class="identifier">qi</span><span class="special">::</span><span class="identifier">skip_over</span></code>:
           </p>
 <pre class="programlisting"><span class="identifier">qi</span><span class="special">::</span><span class="identifier">skip_over</span><span class="special">(</span><span class="identifier">f</span><span class="special">,</span> <span class="identifier">l</span><span class="special">,</span> <span class="identifier">skip</span><span class="special">);</span>
 </pre>
 <a name="spirit.qi.reference.parser_concepts.primitiveparser.type_expressions"></a><h6>
-<a name="id452017"></a>
- <a href="primitiveparser.html#spirit.qi.reference.parser_concepts.primitiveparser.type_expressions">Type
+<a name="id1063631"></a>
+ <a class="link" href="primitiveparser.html#spirit.qi.reference.parser_concepts.primitiveparser.type_expressions">Type
             Expressions</a>
           </h6>
 <div class="informaltable"><table class="table">
@@ -76,32 +73,40 @@
 <col>
 </colgroup>
 <thead><tr>
-<th><p>
+<th>
+ <p>
                     Expression
- </p></th>
-<th><p>
+ </p>
+ </th>
+<th>
+ <p>
                     Description
- </p></th>
+ </p>
+ </th>
 </tr></thead>
 <tbody><tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">traits</span><span class="special">::</span><span class="identifier">is_primitive_parser</span><span class="special">&lt;</span><span class="identifier">P</span><span class="special">&gt;::</span><span class="identifier">type</span></tt>
- </p></td>
-<td><p>
- Metafunction that evaluates to <tt class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">true_</span></tt>
- if a certain type, <tt class="computeroutput"><span class="identifier">P</span></tt>,
- is a PrimitiveParser, <tt class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">false_</span></tt>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">traits</span><span class="special">::</span><span class="identifier">is_primitive_parser</span><span class="special">&lt;</span><span class="identifier">P</span><span class="special">&gt;::</span><span class="identifier">type</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Metafunction that evaluates to <code class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">true_</span></code>
+ if a certain type, <code class="computeroutput"><span class="identifier">P</span></code>,
+ is a PrimitiveParser, <code class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">false_</span></code>
                     otherwise (See <a href="http://www.boost.org/libs/mpl/doc/refmanual/integral-constant.html" target="_top">MPL
                     Boolean Constant</a>).
- </p></td>
+ </p>
+ </td>
 </tr></tbody>
 </table></div>
 <a name="spirit.qi.reference.parser_concepts.primitiveparser.models"></a><h6>
-<a name="id452203"></a>
- Models
+<a name="id1063766"></a>
+ <a class="link" href="primitiveparser.html#spirit.qi.reference.parser_concepts.primitiveparser.models">Models</a>
           </h6>
 <p>
- <span class="bold"><b>FIXME</b></span> Add links to <span class="emphasis"><em>PrimitiveParser</em></span>
+ <span class="bold"><strong>FIXME</strong></span> Add links to <span class="emphasis"><em>PrimitiveParser</em></span>
             models here.
           </p>
 </div>

Modified: trunk/libs/spirit/doc/html/spirit/qi/reference/parser_concepts/unaryparser.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/qi/reference/parser_concepts/unaryparser.html (original)
+++ trunk/libs/spirit/doc/html/spirit/qi/reference/parser_concepts/unaryparser.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -3,10 +3,10 @@
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <title>UnaryParser</title>
 <link rel="stylesheet" href="../../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../../index.html" title="Spirit 2.1">
 <link rel="up" href="../parser_concepts.html" title="Parser Concepts">
-<link rel="previous" href="primitiveparser.html" title="PrimitiveParser">
+<link rel="prev" href="primitiveparser.html" title="PrimitiveParser">
 <link rel="next" href="binaryparser.html" title="BinaryParser">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -22,16 +22,13 @@
 <div class="spirit-nav">
 <a accesskey="p" href="primitiveparser.html"><img src="../../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../parser_concepts.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="binaryparser.html"><img src="../../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h5 class="title">
-<a name="spirit.qi.reference.parser_concepts.unaryparser"></a>UnaryParser
-</h5></div></div>
-<div></div>
-</div>
+<div class="section" title="UnaryParser">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="spirit.qi.reference.parser_concepts.unaryparser"></a><a class="link" href="unaryparser.html" title="UnaryParser">UnaryParser</a>
+</h5></div></div></div>
 <a name="spirit.qi.reference.parser_concepts.unaryparser.description"></a><h6>
-<a name="id452262"></a>
- Description
+<a name="id1063807"></a>
+ <a class="link" href="unaryparser.html#spirit.qi.reference.parser_concepts.unaryparser.description">Description</a>
           </h6>
 <p>
             <span class="emphasis"><em>UnaryParser</em></span> is a composite parser that has a single
@@ -39,39 +36,39 @@
             the Delegate Design Pattern.
           </p>
 <a name="spirit.qi.reference.parser_concepts.unaryparser.refinement_of"></a><h6>
-<a name="id452298"></a>
- <a href="unaryparser.html#spirit.qi.reference.parser_concepts.unaryparser.refinement_of">Refinement
+<a name="id1063832"></a>
+ <a class="link" href="unaryparser.html#spirit.qi.reference.parser_concepts.unaryparser.refinement_of">Refinement
             of</a>
           </h6>
 <div class="blockquote"><blockquote class="blockquote">
 <p>
               </p>
 <p>
- Parser
+ <a class="link" href="parser.html" title="Parser"><code class="computeroutput"><span class="identifier">Parser</span></code></a>
               </p>
 <p>
             </p>
 </blockquote></div>
-<div class="variablelist">
+<div class="variablelist" title="Notation">
 <p class="title"><b>Notation</b></p>
 <dl>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">p</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">p</span></code></span></dt>
 <dd><p>
                 A UnaryParser.
               </p></dd>
-<dt><span class="term"><tt class="computeroutput"><span class="identifier">P</span></tt></span></dt>
+<dt><span class="term"><code class="computeroutput"><span class="identifier">P</span></code></span></dt>
 <dd><p>
                 A UnaryParser type.
               </p></dd>
 </dl>
 </div>
 <a name="spirit.qi.reference.parser_concepts.unaryparser.valid_expressions"></a><h6>
-<a name="id452407"></a>
- <a href="unaryparser.html#spirit.qi.reference.parser_concepts.unaryparser.valid_expressions">Valid
+<a name="id1063912"></a>
+ <a class="link" href="unaryparser.html#spirit.qi.reference.parser_concepts.unaryparser.valid_expressions">Valid
             Expressions</a>
           </h6>
 <p>
- In addition to the requirements defined in Parser, for any UnaryParser
+ In addition to the requirements defined in <a class="link" href="parser.html" title="Parser"><code class="computeroutput"><span class="identifier">Parser</span></code></a>, for any UnaryParser
             the following must be met:
           </p>
 <div class="informaltable"><table class="table">
@@ -81,31 +78,43 @@
 <col>
 </colgroup>
 <thead><tr>
-<th><p>
+<th>
+ <p>
                     Expression
- </p></th>
-<th><p>
+ </p>
+ </th>
+<th>
+ <p>
                     Semantics
- </p></th>
-<th><p>
+ </p>
+ </th>
+<th>
+ <p>
                     Return type
- </p></th>
+ </p>
+ </th>
 </tr></thead>
 <tbody><tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">p</span><span class="special">.</span><span class="identifier">subject</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">p</span><span class="special">.</span><span class="identifier">subject</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                     Subject parser.
- </p></td>
-<td><p>
- Parser
- </p></td>
+ </p>
+ </td>
+<td>
+ <p>
+ <a class="link" href="parser.html" title="Parser"><code class="computeroutput"><span class="identifier">Parser</span></code></a>
+ </p>
+ </td>
 </tr></tbody>
 </table></div>
 <a name="spirit.qi.reference.parser_concepts.unaryparser.type_expressions"></a><h6>
-<a name="id452562"></a>
- <a href="unaryparser.html#spirit.qi.reference.parser_concepts.unaryparser.type_expressions">Type
+<a name="id1064026"></a>
+ <a class="link" href="unaryparser.html#spirit.qi.reference.parser_concepts.unaryparser.type_expressions">Type
             Expressions</a>
           </h6>
 <div class="informaltable"><table class="table">
@@ -114,53 +123,65 @@
 <col>
 </colgroup>
 <thead><tr>
-<th><p>
+<th>
+ <p>
                     Expression
- </p></th>
-<th><p>
+ </p>
+ </th>
+<th>
+ <p>
                     Description
- </p></th>
+ </p>
+ </th>
 </tr></thead>
 <tbody>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">P</span><span class="special">::</span><span class="identifier">subject_type</span></tt>
- </p></td>
-<td><p>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">P</span><span class="special">::</span><span class="identifier">subject_type</span></code>
+ </p>
+ </td>
+<td>
+ <p>
                     The subject parser type.
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
- <tt class="computeroutput"><span class="identifier">traits</span><span class="special">::</span><span class="identifier">is_unary_parser</span><span class="special">&lt;</span><span class="identifier">P</span><span class="special">&gt;::</span><span class="identifier">type</span></tt>
- </p></td>
-<td><p>
- Metafunction that evaluates to <tt class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">true_</span></tt>
- if a certain type, <tt class="computeroutput"><span class="identifier">P</span></tt>
- is a UnaryParser, <tt class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">false_</span></tt>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">traits</span><span class="special">::</span><span class="identifier">is_unary_parser</span><span class="special">&lt;</span><span class="identifier">P</span><span class="special">&gt;::</span><span class="identifier">type</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Metafunction that evaluates to <code class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">true_</span></code>
+ if a certain type, <code class="computeroutput"><span class="identifier">P</span></code>
+ is a UnaryParser, <code class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">false_</span></code>
                     otherwise (See <a href="http://www.boost.org/libs/mpl/doc/refmanual/integral-constant.html" target="_top">MPL
                     Boolean Constant</a>).
- </p></td>
+ </p>
+ </td>
 </tr>
 </tbody>
 </table></div>
 <a name="spirit.qi.reference.parser_concepts.unaryparser.invariants"></a><h6>
-<a name="id452786"></a>
- Invariants
+<a name="id1064192"></a>
+ <a class="link" href="unaryparser.html#spirit.qi.reference.parser_concepts.unaryparser.invariants">Invariants</a>
           </h6>
 <p>
- For any UnaryParser, <tt class="computeroutput"><span class="identifier">P</span></tt>,
+ For any UnaryParser, <code class="computeroutput"><span class="identifier">P</span></code>,
             the following invariant always holds:
           </p>
-<div class="itemizedlist"><ul type="disc"><li>
-<tt class="computeroutput"><span class="identifier">traits</span><span class="special">::</span><span class="identifier">is_parser</span><span class="special">&lt;</span><span class="identifier">P</span><span class="special">::</span><span class="identifier">subject_type</span><span class="special">&gt;::</span><span class="identifier">type</span></tt> evaluates to <tt class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">true_</span></tt>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">
+<code class="computeroutput"><span class="identifier">traits</span><span class="special">::</span><span class="identifier">is_parser</span><span class="special">&lt;</span><span class="identifier">P</span><span class="special">::</span><span class="identifier">subject_type</span><span class="special">&gt;::</span><span class="identifier">type</span></code> evaluates to <code class="computeroutput"><span class="identifier">mpl</span><span class="special">::</span><span class="identifier">true_</span></code>
 </li></ul></div>
 <a name="spirit.qi.reference.parser_concepts.unaryparser.models"></a><h6>
-<a name="id452910"></a>
- Models
+<a name="id1064278"></a>
+ <a class="link" href="unaryparser.html#spirit.qi.reference.parser_concepts.unaryparser.models">Models</a>
           </h6>
 <p>
- <span class="bold"><b>FIXME</b></span> Add links to models of UnaryParser
+ <span class="bold"><strong>FIXME</strong></span> Add links to models of UnaryParser
             concept
           </p>
 </div>

Modified: trunk/libs/spirit/doc/html/spirit/qi/tutorials.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/qi/tutorials.html (original)
+++ trunk/libs/spirit/doc/html/spirit/qi/tutorials.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -3,10 +3,10 @@
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <title>Tutorials</title>
 <link rel="stylesheet" href="../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../index.html" title="Spirit 2.1">
-<link rel="up" href="../qi.html" title=" Qi">
-<link rel="previous" href="../qi.html" title=" Qi">
+<link rel="up" href="../qi.html" title="Qi">
+<link rel="prev" href="../qi.html" title="Qi">
 <link rel="next" href="tutorials/quick_start.html" title="Quick Start">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -22,13 +22,10 @@
 <div class="spirit-nav">
 <a accesskey="p" href="../qi.html"><img src="../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../qi.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="tutorials/quick_start.html"><img src="../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h3 class="title">
-<a name="spirit.qi.tutorials"></a>Tutorials
-</h3></div></div>
-<div></div>
-</div>
+<div class="section" title="Tutorials">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="spirit.qi.tutorials"></a><a class="link" href="tutorials.html" title="Tutorials">Tutorials</a>
+</h3></div></div></div>
 <div class="toc"><dl>
 <dt><span class="section">Quick Start</span></dt>
 <dt><span class="section">Warming up</span></dt>

Modified: trunk/libs/spirit/doc/html/spirit/qi/tutorials/complex___our_first_complex_parser.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/qi/tutorials/complex___our_first_complex_parser.html (original)
+++ trunk/libs/spirit/doc/html/spirit/qi/tutorials/complex___our_first_complex_parser.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -1,15 +1,13 @@
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title>Complex
- - Our first complex parser</title>
+<title>Complex - Our first complex parser</title>
 <link rel="stylesheet" href="../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../index.html" title="Spirit 2.1">
 <link rel="up" href="../tutorials.html" title="Tutorials">
-<link rel="previous" href="semantic_actions.html" title="Semantic Actions">
-<link rel="next" href="sum___adding_numbers.html" title="Sum - adding
- numbers">
+<link rel="prev" href="semantic_actions.html" title="Semantic Actions">
+<link rel="next" href="sum___adding_numbers.html" title="Sum - adding numbers">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
 <table cellpadding="2" width="100%"><tr>
@@ -24,15 +22,11 @@
 <div class="spirit-nav">
 <a accesskey="p" href="semantic_actions.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../tutorials.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="sum___adding_numbers.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h4 class="title">
-<a name="spirit.qi.tutorials.complex___our_first_complex_parser"></a><a href="complex___our_first_complex_parser.html" title="Complex
- - Our first complex parser">Complex
+<div class="section" title="Complex - Our first complex parser">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="spirit.qi.tutorials.complex___our_first_complex_parser"></a><a class="link" href="complex___our_first_complex_parser.html" title="Complex - Our first complex parser">Complex
         - Our first complex parser</a>
-</h4></div></div>
-<div></div>
-</div>
+</h4></div></div></div>
 <p>
           Well, not really a complex parser, but a parser that parses complex numbers.
           This time, we're using Phoenix
@@ -47,26 +41,26 @@
 <p>
           What's new? Well, we have:
         </p>
-<div class="orderedlist"><ol type="1">
-<li>
- Alternates: e.g. <tt class="computeroutput"><span class="identifier">a</span> <span class="special">|</span>
- <span class="identifier">b</span></tt>. Try <tt class="computeroutput"><span class="identifier">a</span></tt>
- first. If it succeeds, good. If not, try the next alternative, <tt class="computeroutput"><span class="identifier">b</span></tt>.
+<div class="orderedlist"><ol class="orderedlist" type="1">
+<li class="listitem">
+ Alternates: e.g. <code class="computeroutput"><span class="identifier">a</span> <span class="special">|</span>
+ <span class="identifier">b</span></code>. Try <code class="computeroutput"><span class="identifier">a</span></code>
+ first. If it succeeds, good. If not, try the next alternative, <code class="computeroutput"><span class="identifier">b</span></code>.
           </li>
-<li>
+<li class="listitem">
             Optionals: e.g. -p. Match the parser p zero or one time.
           </li>
 </ol></div>
 <p>
           The complex parser presented above reads as:
         </p>
-<div class="itemizedlist"><ul type="disc">
-<li>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem">
             One or two real number in parantheses, separated by comma (the second
             number is optional)
           </li>
-<li>
-<span class="bold"><b>OR</b></span> a single real number.
+<li class="listitem">
+<span class="bold"><strong>OR</strong></span> a single real number.
           </li>
 </ul></div>
 <p>
@@ -124,15 +118,15 @@
           The full cpp file for this example can be found here: ../../example/qi/complex_number.cpp
         </p>
 <p>
- The <tt class="computeroutput"><span class="identifier">double_</span></tt> parser attaches
+ The <code class="computeroutput"><span class="identifier">double_</span></code> parser attaches
           this action:
         </p>
 <pre class="programlisting"><span class="identifier">ref</span><span class="special">(</span><span class="identifier">n</span><span class="special">)</span> <span class="special">=</span> <span class="identifier">_1</span>
 </pre>
 <p>
- This assigns the parsed result (actually, the attribute of <tt class="computeroutput"><span class="identifier">double_</span></tt>) to n. <tt class="computeroutput"><span class="identifier">ref</span><span class="special">(</span><span class="identifier">n</span><span class="special">)</span></tt>
- tells Phoenix that <tt class="computeroutput"><span class="identifier">n</span></tt> is
- a mutable reference. <tt class="computeroutput"><span class="identifier">_1</span></tt>
+ This assigns the parsed result (actually, the attribute of <code class="computeroutput"><span class="identifier">double_</span></code>) to n. <code class="computeroutput"><span class="identifier">ref</span><span class="special">(</span><span class="identifier">n</span><span class="special">)</span></code>
+ tells Phoenix that <code class="computeroutput"><span class="identifier">n</span></code> is
+ a mutable reference. <code class="computeroutput"><span class="identifier">_1</span></code>
           is a Phoenix placeholder for the parsed result attribute.
         </p>
 </div>

Modified: trunk/libs/spirit/doc/html/spirit/qi/tutorials/employee___parsing_into_structs.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/qi/tutorials/employee___parsing_into_structs.html (original)
+++ trunk/libs/spirit/doc/html/spirit/qi/tutorials/employee___parsing_into_structs.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -1,13 +1,12 @@
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title>Employee
- - Parsing into structs</title>
+<title>Employee - Parsing into structs</title>
 <link rel="stylesheet" href="../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../index.html" title="Spirit 2.1">
 <link rel="up" href="../tutorials.html" title="Tutorials">
-<link rel="previous" href="roman_numerals.html" title="Roman Numerals">
+<link rel="prev" href="roman_numerals.html" title="Roman Numerals">
 <link rel="next" href="mini_xml___asts_.html" title="Mini XML - ASTs!">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -23,15 +22,11 @@
 <div class="spirit-nav">
 <a accesskey="p" href="roman_numerals.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../tutorials.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="mini_xml___asts_.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h4 class="title">
-<a name="spirit.qi.tutorials.employee___parsing_into_structs"></a><a href="employee___parsing_into_structs.html" title="Employee
- - Parsing into structs">Employee
+<div class="section" title="Employee - Parsing into structs">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="spirit.qi.tutorials.employee___parsing_into_structs"></a><a class="link" href="employee___parsing_into_structs.html" title="Employee - Parsing into structs">Employee
         - Parsing into structs</a>
-</h4></div></div>
-<div></div>
-</div>
+</h4></div></div></div>
 <p>
           It's a common question in the <a href="http://www.nabble.com/The-Spirit-Parser-Library-f3430.html" target="_top">Spirit
           General List</a>: how do I parse and place the results into a C++ struct?
@@ -40,17 +35,17 @@
           attributed, makes it even easier. The next example demonstrates some features
           of Spirit2 that makes this easy. In the process, you'll learn about:
         </p>
-<div class="itemizedlist"><ul type="disc">
-<li>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem">
             More about attributes
           </li>
-<li>
+<li class="listitem">
             Auto rules
           </li>
-<li>
+<li class="listitem">
             Some more built-in parsers
           </li>
-<li>
+<li class="listitem">
             Directives
           </li>
 </ul></div>
@@ -158,15 +153,15 @@
 <span class="keyword">struct</span> <span class="identifier">employee_parser</span> <span class="special">:</span> <span class="identifier">grammar</span><span class="special">&lt;</span><span class="identifier">Iterator</span><span class="special">,</span> <span class="identifier">employee</span><span class="special">(),</span> <span class="identifier">space_type</span><span class="special">&gt;</span>
 </pre>
 <p>
- <tt class="computeroutput"><span class="identifier">employee_parser</span></tt> is a grammar.
+ <code class="computeroutput"><span class="identifier">employee_parser</span></code> is a grammar.
           Like before, we make it a template so that we can reuse it for different
           iterator types. The grammar's signature is:
         </p>
 <pre class="programlisting"><span class="identifier">employee</span><span class="special">()</span>
 </pre>
 <p>
- meaning, the parser generates employee structs. <tt class="computeroutput"><span class="identifier">employee_parser</span></tt>
- skips white spaces using <tt class="computeroutput"><span class="identifier">space_type</span></tt>
+ meaning, the parser generates employee structs. <code class="computeroutput"><span class="identifier">employee_parser</span></code>
+ skips white spaces using <code class="computeroutput"><span class="identifier">space_type</span></code>
           as its skip parser.
         </p>
 <pre class="programlisting"><span class="identifier">employee_parser</span><span class="special">()</span> <span class="special">:</span> <span class="identifier">employee_parser</span><span class="special">::</span><span class="identifier">base_type</span><span class="special">(</span><span class="identifier">start</span><span class="special">)</span>
@@ -178,19 +173,19 @@
 <span class="identifier">rule</span><span class="special">&lt;</span><span class="identifier">Iterator</span><span class="special">,</span> <span class="identifier">employee</span><span class="special">(),</span> <span class="identifier">space_type</span><span class="special">&gt;</span> <span class="identifier">start</span><span class="special">;</span>
 </pre>
 <p>
- Declares two rules: <tt class="computeroutput"><span class="identifier">quoted_string</span></tt>
- and <tt class="computeroutput"><span class="identifier">start</span></tt>. <tt class="computeroutput"><span class="identifier">start</span></tt> has the same template parameters
- as the grammar itself. <tt class="computeroutput"><span class="identifier">quoted_string</span></tt>
- has a <tt class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">string</span></tt> attribute.
- </p>
-<a name="spirit.qi.tutorials.employee___parsing_into_structs.lexeme"></a><h5>
-<a name="id428652"></a>
- Lexeme
- </h5>
+ Declares two rules: <code class="computeroutput"><span class="identifier">quoted_string</span></code>
+ and <code class="computeroutput"><span class="identifier">start</span></code>. <code class="computeroutput"><span class="identifier">start</span></code> has the same template parameters
+ as the grammar itself. <code class="computeroutput"><span class="identifier">quoted_string</span></code>
+ has a <code class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">string</span></code> attribute.
+ </p>
+<a name="spirit.qi.tutorials.employee___parsing_into_structs.lexeme"></a><h6>
+<a name="id1041155"></a>
+ <a class="link" href="employee___parsing_into_structs.html#spirit.qi.tutorials.employee___parsing_into_structs.lexeme">Lexeme</a>
+ </h6>
 <pre class="programlisting"><span class="identifier">lexeme</span><span class="special">[</span><span class="char">'"'</span> <span class="special">&gt;&gt;</span> <span class="special">+(</span><span class="identifier">char_</span> <span class="special">-</span> <span class="char">'"'</span><span class="special">)</span> <span class="special">&gt;&gt;</span> <span class="char">'"'</span><span class="special">];</span>
 </pre>
 <p>
- <tt class="computeroutput"><span class="identifier">lexeme</span></tt> inhibits space skipping
+ <code class="computeroutput"><span class="identifier">lexeme</span></code> inhibits space skipping
           from the open brace to the closing brace. The expression parses quoted
           strings.
         </p>
@@ -200,35 +195,35 @@
           parses one or more chars, except the double quote. It stops when it sees
           a double quote.
         </p>
-<a name="spirit.qi.tutorials.employee___parsing_into_structs.difference"></a><h5>
-<a name="id428808"></a>
- Difference
- </h5>
+<a name="spirit.qi.tutorials.employee___parsing_into_structs.difference"></a><h6>
+<a name="id1041268"></a>
+ <a class="link" href="employee___parsing_into_structs.html#spirit.qi.tutorials.employee___parsing_into_structs.difference">Difference</a>
+ </h6>
 <p>
           The expression:
         </p>
 <pre class="programlisting"><span class="identifier">a</span> <span class="special">-</span> <span class="identifier">b</span>
 </pre>
 <p>
- parses <tt class="computeroutput"><span class="identifier">a</span></tt> but not <tt class="computeroutput"><span class="identifier">b</span></tt>. Its attribute is just <tt class="computeroutput"><span class="identifier">A</span></tt>, the attribute of <tt class="computeroutput"><span class="identifier">a</span></tt>.
- <tt class="computeroutput"><span class="identifier">b</span></tt>'s attribute is ignored.
+ parses <code class="computeroutput"><span class="identifier">a</span></code> but not <code class="computeroutput"><span class="identifier">b</span></code>. Its attribute is just <code class="computeroutput"><span class="identifier">A</span></code>, the attribute of <code class="computeroutput"><span class="identifier">a</span></code>.
+ <code class="computeroutput"><span class="identifier">b</span></code>'s attribute is ignored.
           Hence, the attribute of:
         </p>
 <pre class="programlisting"><span class="identifier">char_</span> <span class="special">-</span> <span class="char">'"'</span>
 </pre>
 <p>
- is just <tt class="computeroutput"><span class="keyword">char</span></tt>.
+ is just <code class="computeroutput"><span class="keyword">char</span></code>.
         </p>
-<a name="spirit.qi.tutorials.employee___parsing_into_structs.plus"></a><h5>
-<a name="id428966"></a>
- Plus
- </h5>
+<a name="spirit.qi.tutorials.employee___parsing_into_structs.plus"></a><h6>
+<a name="id1041376"></a>
+ <a class="link" href="employee___parsing_into_structs.html#spirit.qi.tutorials.employee___parsing_into_structs.plus">Plus</a>
+ </h6>
 <pre class="programlisting"><span class="special">+</span><span class="identifier">a</span>
 </pre>
 <p>
           is the close kin of the kleene star we got so used to in our tutorial.
- Like it's kin, the kleene star, its attribute is a <tt class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">vector</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">&gt;</span></tt> where <tt class="computeroutput"><span class="identifier">A</span></tt>
- is the attribute of <tt class="computeroutput"><span class="identifier">a</span></tt>.
+ Like it's kin, the kleene star, its attribute is a <code class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">vector</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">&gt;</span></code> where <code class="computeroutput"><span class="identifier">A</span></code>
+ is the attribute of <code class="computeroutput"><span class="identifier">a</span></code>.
           So, putting all these together, the attribute of
         </p>
 <pre class="programlisting"><span class="special">+(</span><span class="identifier">char_</span> <span class="special">-</span> <span class="char">'"'</span><span class="special">)</span>
@@ -238,11 +233,11 @@
         </p>
 <pre class="programlisting"><span class="identifier">std</span><span class="special">::</span><span class="identifier">vector</span><span class="special">&lt;</span><span class="keyword">char</span><span class="special">&gt;</span>
 </pre>
-<a name="spirit.qi.tutorials.employee___parsing_into_structs.sequence_attribute"></a><h5>
-<a name="id429153"></a>
- <a href="employee___parsing_into_structs.html#spirit.qi.tutorials.employee___parsing_into_structs.sequence_attribute">Sequence
+<a name="spirit.qi.tutorials.employee___parsing_into_structs.sequence_attribute"></a><h6>
+<a name="id1041502"></a>
+ <a class="link" href="employee___parsing_into_structs.html#spirit.qi.tutorials.employee___parsing_into_structs.sequence_attribute">Sequence
           Attribute</a>
- </h5>
+ </h6>
 <p>
           Now what's the attribute of
         </p>
@@ -262,45 +257,45 @@
 <pre class="programlisting"><span class="identifier">fusion</span><span class="special">::</span><span class="identifier">vector</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">,</span> <span class="identifier">B</span><span class="special">,</span> <span class="identifier">C</span><span class="special">&gt;</span>
 </pre>
 <p>
- where <tt class="computeroutput"><span class="identifier">A</span></tt> is the attribute
- of <tt class="computeroutput"><span class="identifier">a</span></tt>, <tt class="computeroutput"><span class="identifier">B</span></tt>
- is the attribute of <tt class="computeroutput"><span class="identifier">b</span></tt> and
- <tt class="computeroutput"><span class="identifier">C</span></tt> is the attribute of
- <tt class="computeroutput"><span class="identifier">c</span></tt>. What is <tt class="computeroutput"><span class="identifier">fusion</span><span class="special">::</span><span class="identifier">vector</span></tt>? - a tuple.
+ where <code class="computeroutput"><span class="identifier">A</span></code> is the attribute
+ of <code class="computeroutput"><span class="identifier">a</span></code>, <code class="computeroutput"><span class="identifier">B</span></code>
+ is the attribute of <code class="computeroutput"><span class="identifier">b</span></code> and
+ <code class="computeroutput"><span class="identifier">C</span></code> is the attribute of
+ <code class="computeroutput"><span class="identifier">c</span></code>. What is <code class="computeroutput"><span class="identifier">fusion</span><span class="special">::</span><span class="identifier">vector</span></code>? - a tuple.
         </p>
-<div class="note"><table border="0" summary="Note">
+<div class="note" title="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>
 </tr>
-<tr><td colspan="2" align="left" valign="top"><p>
+<tr><td align="left" valign="top"><p>
             If you don't know what I am talking about, see: <a href="http://tinyurl.com/6xun4j" target="_top">Fusion
             Vector</a>. It might be a good idea to have a look into Fusion
             at this point. You'll definitely see more of it in the coming pages.
           </p></td></tr>
 </table></div>
-<a name="spirit.qi.tutorials.employee___parsing_into_structs.attribute_collapsing"></a><h5>
-<a name="id429475"></a>
- <a href="employee___parsing_into_structs.html#spirit.qi.tutorials.employee___parsing_into_structs.attribute_collapsing">Attribute
+<a name="spirit.qi.tutorials.employee___parsing_into_structs.attribute_collapsing"></a><h6>
+<a name="id1041724"></a>
+ <a class="link" href="employee___parsing_into_structs.html#spirit.qi.tutorials.employee___parsing_into_structs.attribute_collapsing">Attribute
           Collapsing</a>
- </h5>
+ </h6>
 <p>
           Some parsers, especially those very little literal parsers you see, like
- <tt class="computeroutput"><span class="char">'"'</span></tt>, do not have attributes.
+ <code class="computeroutput"><span class="char">'"'</span></code>, do not have attributes.
         </p>
 <p>
           Nodes without attributes are disregarded. In a sequence, like above, all
- nodes with no attributes are filtered out of the <tt class="computeroutput"><span class="identifier">fusion</span><span class="special">:</span><span class="identifier">vector</span></tt>.
- So, since <tt class="computeroutput"><span class="char">'"'</span></tt> has no attribute,
- and <tt class="computeroutput"><span class="special">+(</span><span class="identifier">char_</span>
- <span class="special">-</span> <span class="char">'"'</span><span class="special">)</span></tt> has a <tt class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">vector</span><span class="special">&lt;</span><span class="keyword">char</span><span class="special">&gt;</span></tt> attribute, the whole expression's attribute
+ nodes with no attributes are filtered out of the <code class="computeroutput"><span class="identifier">fusion</span><span class="special">:</span><span class="identifier">vector</span></code>.
+ So, since <code class="computeroutput"><span class="char">'"'</span></code> has no attribute,
+ and <code class="computeroutput"><span class="special">+(</span><span class="identifier">char_</span>
+ <span class="special">-</span> <span class="char">'"'</span><span class="special">)</span></code> has a <code class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">vector</span><span class="special">&lt;</span><span class="keyword">char</span><span class="special">&gt;</span></code> attribute, the whole expression's attribute
           should have been:
         </p>
 <pre class="programlisting"><span class="identifier">fusion</span><span class="special">::</span><span class="identifier">vector</span><span class="special">&lt;</span><span class="identifier">std</span><span class="special">::</span><span class="identifier">vector</span><span class="special">&lt;</span><span class="keyword">char</span><span class="special">&gt;</span> <span class="special">&gt;</span>
 </pre>
 <p>
           But wait, there's one more collapsing rule: If after the attribute is a
- single element <tt class="computeroutput"><span class="identifier">fusion</span><span class="special">::</span><span class="identifier">vector</span></tt>, The element is stripped naked
+ single element <code class="computeroutput"><span class="identifier">fusion</span><span class="special">::</span><span class="identifier">vector</span></code>, The element is stripped naked
           from its container. So, to make a long story short, the attribute of the
           expression:
         </p>
@@ -311,11 +306,11 @@
         </p>
 <pre class="programlisting"><span class="identifier">std</span><span class="special">::</span><span class="identifier">vector</span><span class="special">&lt;</span><span class="keyword">char</span><span class="special">&gt;</span>
 </pre>
-<a name="spirit.qi.tutorials.employee___parsing_into_structs.auto_rules"></a><h5>
-<a name="id429824"></a>
- <a href="employee___parsing_into_structs.html#spirit.qi.tutorials.employee___parsing_into_structs.auto_rules">Auto
+<a name="spirit.qi.tutorials.employee___parsing_into_structs.auto_rules"></a><h6>
+<a name="id1041963"></a>
+ <a class="link" href="employee___parsing_into_structs.html#spirit.qi.tutorials.employee___parsing_into_structs.auto_rules">Auto
           Rules</a>
- </h5>
+ </h6>
 <p>
           It is typical to see rules like:
         </p>
@@ -329,11 +324,11 @@
 <pre class="programlisting"><span class="identifier">r</span> <span class="special">%=</span> <span class="identifier">p</span><span class="special">;</span>
 </pre>
 <p>
- The attribute of <tt class="computeroutput"><span class="identifier">p</span></tt> automatically
- uses the attribute of <tt class="computeroutput"><span class="identifier">r</span></tt>.
+ The attribute of <code class="computeroutput"><span class="identifier">p</span></code> automatically
+ uses the attribute of <code class="computeroutput"><span class="identifier">r</span></code>.
         </p>
 <p>
- So, going back to our <tt class="computeroutput"><span class="identifier">quoted_string</span></tt>
+ So, going back to our <code class="computeroutput"><span class="identifier">quoted_string</span></code>
           rule:
         </p>
 <pre class="programlisting"><span class="identifier">quoted_string</span> <span class="special">%=</span> <span class="identifier">lexeme</span><span class="special">[</span><span class="char">'"'</span> <span class="special">&gt;&gt;</span> <span class="special">+(</span><span class="identifier">char_</span> <span class="special">-</span> <span class="char">'"'</span><span class="special">)</span> <span class="special">&gt;&gt;</span> <span class="char">'"'</span><span class="special">];</span>
@@ -344,15 +339,15 @@
 <pre class="programlisting"><span class="identifier">quoted_string</span> <span class="special">=</span> <span class="identifier">lexeme</span><span class="special">[</span><span class="char">'"'</span> <span class="special">&gt;&gt;</span> <span class="special">+(</span><span class="identifier">char_</span> <span class="special">-</span> <span class="char">'"'</span><span class="special">)</span> <span class="special">&gt;&gt;</span> <span class="char">'"'</span><span class="special">][</span><span class="identifier">val_</span> <span class="special">=</span> <span class="identifier">_1</span><span class="special">];</span>
 </pre>
 <p>
- The attribute of the <tt class="computeroutput"><span class="identifier">quoted_string</span></tt>
- rule: <tt class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">string</span></tt> <span class="bold"><b>is compatible</b></span>
- with the attribute of the RHS: <tt class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">vector</span><span class="special">&lt;</span><span class="keyword">char</span><span class="special">&gt;</span></tt>. The RHS extracts the parsed attribute
+ The attribute of the <code class="computeroutput"><span class="identifier">quoted_string</span></code>
+ rule: <code class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">string</span></code> <span class="bold"><strong>is compatible</strong></span>
+ with the attribute of the RHS: <code class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">vector</span><span class="special">&lt;</span><span class="keyword">char</span><span class="special">&gt;</span></code>. The RHS extracts the parsed attribute
           directly into the rule's attribute, in-situ.
         </p>
-<a name="spirit.qi.tutorials.employee___parsing_into_structs.finally"></a><h5>
-<a name="id430268"></a>
- Finally
- </h5>
+<a name="spirit.qi.tutorials.employee___parsing_into_structs.finally"></a><h6>
+<a name="id1042282"></a>
+ <a class="link" href="employee___parsing_into_structs.html#spirit.qi.tutorials.employee___parsing_into_structs.finally">Finally</a>
+ </h6>
 <p>
           We're down to one rule, the start rule:
         </p>
@@ -374,28 +369,28 @@
 <p>
           These nodes do not have an attribute:
         </p>
-<div class="itemizedlist"><ul type="disc">
-<li><tt class="computeroutput"><span class="identifier">lit</span><span class="special">(</span><span class="string">"employee"</span><span class="special">)</span></tt></li>
-<li><tt class="computeroutput"><span class="char">'{'</span></tt></li>
-<li><tt class="computeroutput"><span class="char">'}'</span></tt></li>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem"><code class="computeroutput"><span class="identifier">lit</span><span class="special">(</span><span class="string">"employee"</span><span class="special">)</span></code></li>
+<li class="listitem"><code class="computeroutput"><span class="char">'{'</span></code></li>
+<li class="listitem"><code class="computeroutput"><span class="char">'}'</span></code></li>
 </ul></div>
-<div class="note"><table border="0" summary="Note">
+<div class="note" title="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>
 </tr>
-<tr><td colspan="2" align="left" valign="top"><p>
- In case you are wondering, <tt class="computeroutput"><span class="identifier">lit</span><span class="special">(</span><span class="string">"employee"</span><span class="special">)</span></tt> is the same as "employee".
- We had to wrap it inside <tt class="computeroutput"><span class="identifier">lit</span></tt>
- because immediately after it is <tt class="computeroutput"><span class="special">&gt;&gt;</span>
- <span class="char">'{'</span></tt>. You can't right-shift a <tt class="computeroutput"><span class="keyword">char</span><span class="special">[]</span></tt>
- and a <tt class="computeroutput"><span class="keyword">char</span></tt> - you know, C++
+<tr><td align="left" valign="top"><p>
+ In case you are wondering, <code class="computeroutput"><span class="identifier">lit</span><span class="special">(</span><span class="string">"employee"</span><span class="special">)</span></code> is the same as "employee".
+ We had to wrap it inside <code class="computeroutput"><span class="identifier">lit</span></code>
+ because immediately after it is <code class="computeroutput"><span class="special">&gt;&gt;</span>
+ <span class="char">'{'</span></code>. You can't right-shift a <code class="computeroutput"><span class="keyword">char</span><span class="special">[]</span></code>
+ and a <code class="computeroutput"><span class="keyword">char</span></code> - you know, C++
             syntax rules.
           </p></td></tr>
 </table></div>
 <p>
- Recall that the attribute of <tt class="computeroutput"><span class="identifier">start</span></tt>
- is the <tt class="computeroutput"><span class="identifier">employee</span></tt> struct:
+ Recall that the attribute of <code class="computeroutput"><span class="identifier">start</span></code>
+ is the <code class="computeroutput"><span class="identifier">employee</span></code> struct:
         </p>
 <p>
           </p>
@@ -415,11 +410,11 @@
 <p>
         </p>
 <p>
- Now everything is clear, right? The <tt class="computeroutput"><span class="keyword">struct</span>
- <span class="identifier">employee</span></tt> <span class="bold"><b>IS</b></span>
- compatible with <tt class="computeroutput"><span class="identifier">fusion</span><span class="special">::</span><span class="identifier">vector</span><span class="special">&lt;</span><span class="keyword">int</span><span class="special">,</span> <span class="identifier">std</span><span class="special">::</span><span class="identifier">string</span><span class="special">,</span> <span class="identifier">std</span><span class="special">::</span><span class="identifier">string</span><span class="special">,</span> <span class="keyword">double</span><span class="special">&gt;</span></tt>. So, the RHS of <tt class="computeroutput"><span class="identifier">start</span></tt>
- uses start's attribute (a <tt class="computeroutput"><span class="keyword">struct</span>
- <span class="identifier">employee</span></tt>) in-situ when it does
+ Now everything is clear, right? The <code class="computeroutput"><span class="keyword">struct</span>
+ <span class="identifier">employee</span></code> <span class="bold"><strong>IS</strong></span>
+ compatible with <code class="computeroutput"><span class="identifier">fusion</span><span class="special">::</span><span class="identifier">vector</span><span class="special">&lt;</span><span class="keyword">int</span><span class="special">,</span> <span class="identifier">std</span><span class="special">::</span><span class="identifier">string</span><span class="special">,</span> <span class="identifier">std</span><span class="special">::</span><span class="identifier">string</span><span class="special">,</span> <span class="keyword">double</span><span class="special">&gt;</span></code>. So, the RHS of <code class="computeroutput"><span class="identifier">start</span></code>
+ uses start's attribute (a <code class="computeroutput"><span class="keyword">struct</span>
+ <span class="identifier">employee</span></code>) in-situ when it does
           its work.
         </p>
 </div>

Modified: trunk/libs/spirit/doc/html/spirit/qi/tutorials/mini_xml___asts_.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/qi/tutorials/mini_xml___asts_.html (original)
+++ trunk/libs/spirit/doc/html/spirit/qi/tutorials/mini_xml___asts_.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -3,13 +3,11 @@
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <title>Mini XML - ASTs!</title>
 <link rel="stylesheet" href="../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../index.html" title="Spirit 2.1">
 <link rel="up" href="../tutorials.html" title="Tutorials">
-<link rel="previous" href="employee___parsing_into_structs.html" title="Employee
- - Parsing into structs">
-<link rel="next" href="mini_xml___error_handling.html" title="Mini
- XML - Error Handling">
+<link rel="prev" href="employee___parsing_into_structs.html" title="Employee - Parsing into structs">
+<link rel="next" href="mini_xml___error_handling.html" title="Mini XML - Error Handling">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
 <table cellpadding="2" width="100%"><tr>
@@ -24,19 +22,16 @@
 <div class="spirit-nav">
 <a accesskey="p" href="employee___parsing_into_structs.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../tutorials.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="mini_xml___error_handling.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h4 class="title">
-<a name="spirit.qi.tutorials.mini_xml___asts_"></a>Mini XML - ASTs!
-</h4></div></div>
-<div></div>
-</div>
+<div class="section" title="Mini XML - ASTs!">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="spirit.qi.tutorials.mini_xml___asts_"></a><a class="link" href="mini_xml___asts_.html" title="Mini XML - ASTs!">Mini XML - ASTs!</a>
+</h4></div></div></div>
 <p>
           Stop and think about it... We've come very close to generating an AST in
           our last example. We parsed a single structure and generated an in-memory
- representation of it in the form of a struct: the <tt class="computeroutput"><span class="keyword">struct</span>
- <span class="identifier">employee</span></tt>. If we changed the implementation
- to parse one or more employees, the result would be a <tt class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">vector</span><span class="special">&lt;</span><span class="identifier">employee</span><span class="special">&gt;</span></tt>. We can go on and add more hierarchy:
+ representation of it in the form of a struct: the <code class="computeroutput"><span class="keyword">struct</span>
+ <span class="identifier">employee</span></code>. If we changed the implementation
+ to parse one or more employees, the result would be a <code class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">vector</span><span class="special">&lt;</span><span class="identifier">employee</span><span class="special">&gt;</span></code>. We can go on and add more hierarchy:
           teams, departments, corporations. Then we'll have an AST representation
           of it all.
         </p>
@@ -48,20 +43,20 @@
 <p>
           Along the way, we'll see new features:
         </p>
-<div class="itemizedlist"><ul type="disc">
-<li>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem">
             Inherited attributes
           </li>
-<li>
+<li class="listitem">
             Variant attributes
           </li>
-<li>
+<li class="listitem">
             Local Variables
           </li>
-<li>
+<li class="listitem">
             Not Predicate
           </li>
-<li>
+<li class="listitem">
             Lazy Lit
           </li>
 </ul></div>
@@ -73,10 +68,10 @@
           There are a couple of sample toy-xml files in: ../../example/qi/mini_xml_samples
           for testing purposes. "4.toyxml" has an error in it.
         </p>
-<a name="spirit.qi.tutorials.mini_xml___asts_.first_cut"></a><h5>
-<a name="id431175"></a>
- First Cut
- </h5>
+<a name="spirit.qi.tutorials.mini_xml___asts_.first_cut"></a><h6>
+<a name="id1043272"></a>
+ <a class="link" href="mini_xml___asts_.html#spirit.qi.tutorials.mini_xml___asts_.first_cut">First Cut</a>
+ </h6>
 <p>
           Without further delay, here's the first version of the XML grammar:
         </p>
@@ -134,7 +129,7 @@
 <p>
         </p>
 <p>
- Going bottom up, let's examine the <tt class="computeroutput"><span class="identifier">text</span></tt>
+ Going bottom up, let's examine the <code class="computeroutput"><span class="identifier">text</span></code>
           rule:
         </p>
 <pre class="programlisting"><span class="identifier">rule</span><span class="special">&lt;</span><span class="identifier">Iterator</span><span class="special">,</span> <span class="identifier">std</span><span class="special">::</span><span class="identifier">string</span><span class="special">(),</span> <span class="identifier">space_type</span><span class="special">&gt;</span> <span class="identifier">text</span><span class="special">;</span>
@@ -146,13 +141,13 @@
 </pre>
 <p>
           The semantic action collects the chars and appends them (via +=) to the
- <tt class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">string</span></tt> attribute of the rule (represented
- by the placeholder <tt class="computeroutput"><span class="identifier">_val</span></tt>).
+ <code class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">string</span></code> attribute of the rule (represented
+ by the placeholder <code class="computeroutput"><span class="identifier">_val</span></code>).
         </p>
-<a name="spirit.qi.tutorials.mini_xml___asts_.alternates"></a><h5>
-<a name="id432776"></a>
- Alternates
- </h5>
+<a name="spirit.qi.tutorials.mini_xml___asts_.alternates"></a><h6>
+<a name="id1044453"></a>
+ <a class="link" href="mini_xml___asts_.html#spirit.qi.tutorials.mini_xml___asts_.alternates">Alternates</a>
+ </h6>
 <pre class="programlisting"><span class="identifier">rule</span><span class="special">&lt;</span><span class="identifier">Iterator</span><span class="special">,</span> <span class="identifier">mini_xml_node</span><span class="special">(),</span> <span class="identifier">space_type</span><span class="special">&gt;</span> <span class="identifier">node</span><span class="special">;</span>
 </pre>
 <p>
@@ -161,15 +156,15 @@
 <pre class="programlisting"><span class="identifier">node</span> <span class="special">=</span> <span class="special">(</span><span class="identifier">xml</span> <span class="special">|</span> <span class="identifier">text</span><span class="special">)</span> <span class="special">[</span><span class="identifier">_val</span> <span class="special">=</span> <span class="identifier">_1</span><span class="special">];</span>
 </pre>
 <p>
- We'll see what a <tt class="computeroutput"><span class="identifier">mini_xml_node</span></tt>
+ We'll see what a <code class="computeroutput"><span class="identifier">mini_xml_node</span></code>
           structure later. Looking at the rule definition, we see some alternation
- goiing on here. An xml <tt class="computeroutput"><span class="identifier">node</span></tt>
- is either an <tt class="computeroutput"><span class="identifier">xml</span></tt> OR <tt class="computeroutput"><span class="identifier">text</span></tt>. Hmmm... hold on to that thought...
+ goiing on here. An xml <code class="computeroutput"><span class="identifier">node</span></code>
+ is either an <code class="computeroutput"><span class="identifier">xml</span></code> OR <code class="computeroutput"><span class="identifier">text</span></code>. Hmmm... hold on to that thought...
         </p>
 <pre class="programlisting"><span class="identifier">rule</span><span class="special">&lt;</span><span class="identifier">Iterator</span><span class="special">,</span> <span class="identifier">std</span><span class="special">::</span><span class="identifier">string</span><span class="special">(),</span> <span class="identifier">space_type</span><span class="special">&gt;</span> <span class="identifier">start_tag</span><span class="special">;</span>
 </pre>
 <p>
- Again, with an attribute of <tt class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">string</span></tt>.
+ Again, with an attribute of <code class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">string</span></code>.
           Then, it's definition:
         </p>
 <pre class="programlisting"><span class="identifier">start_tag</span> <span class="special">=</span>
@@ -179,46 +174,46 @@
     <span class="special">&gt;&gt;</span> <span class="char">'&gt;'</span>
 <span class="special">;</span>
 </pre>
-<a name="spirit.qi.tutorials.mini_xml___asts_.not_predicate"></a><h5>
-<a name="id433236"></a>
- <a href="mini_xml___asts_.html#spirit.qi.tutorials.mini_xml___asts_.not_predicate">Not
+<a name="spirit.qi.tutorials.mini_xml___asts_.not_predicate"></a><h6>
+<a name="id1044780"></a>
+ <a class="link" href="mini_xml___asts_.html#spirit.qi.tutorials.mini_xml___asts_.not_predicate">Not
           Predicate</a>
- </h5>
+ </h6>
 <p>
- <tt class="computeroutput"><span class="identifier">start_tag</span></tt> is similar to
- the <tt class="computeroutput"><span class="identifier">text</span></tt> rule apart from
- the added <tt class="computeroutput"><span class="char">'&lt;'</span></tt> and <tt class="computeroutput"><span class="char">'&gt;'</span></tt>. But wait, to make sure that the <tt class="computeroutput"><span class="identifier">start_tag</span></tt> does not parse <tt class="computeroutput"><span class="identifier">end_tag</span></tt>s too, we add: <tt class="computeroutput"><span class="special">!</span><span class="identifier">char_</span><span class="special">(</span><span class="char">'/'</span><span class="special">)</span></tt>. This
+ <code class="computeroutput"><span class="identifier">start_tag</span></code> is similar to
+ the <code class="computeroutput"><span class="identifier">text</span></code> rule apart from
+ the added <code class="computeroutput"><span class="char">'&lt;'</span></code> and <code class="computeroutput"><span class="char">'&gt;'</span></code>. But wait, to make sure that the <code class="computeroutput"><span class="identifier">start_tag</span></code> does not parse <code class="computeroutput"><span class="identifier">end_tag</span></code>s too, we add: <code class="computeroutput"><span class="special">!</span><span class="identifier">char_</span><span class="special">(</span><span class="char">'/'</span><span class="special">)</span></code>. This
           is a "Not Predicate":
         </p>
 <pre class="programlisting"><span class="special">!</span><span class="identifier">p</span>
 </pre>
 <p>
- It will try the parser, <tt class="computeroutput"><span class="identifier">p</span></tt>.
+ It will try the parser, <code class="computeroutput"><span class="identifier">p</span></code>.
           If it is successful, fail, otherwise, pass. In other words, it negates
- the result of <tt class="computeroutput"><span class="identifier">p</span></tt>. Like the
- <tt class="computeroutput"><span class="identifier">eps</span></tt>, it does not consume
+ the result of <code class="computeroutput"><span class="identifier">p</span></code>. Like the
+ <code class="computeroutput"><span class="identifier">eps</span></code>, it does not consume
           any input though. It will always rewind the iterator position to where
           it was upon entry. So, the expression:
         </p>
 <pre class="programlisting"><span class="special">!</span><span class="identifier">char_</span><span class="special">(</span><span class="char">'/'</span><span class="special">)</span>
 </pre>
 <p>
- basically says: we should not have a <tt class="computeroutput"><span class="char">'/'</span></tt>
+ basically says: we should not have a <code class="computeroutput"><span class="char">'/'</span></code>
           at this point.
         </p>
-<a name="spirit.qi.tutorials.mini_xml___asts_.inherited_attribute"></a><h5>
-<a name="id433477"></a>
- <a href="mini_xml___asts_.html#spirit.qi.tutorials.mini_xml___asts_.inherited_attribute">Inherited
+<a name="spirit.qi.tutorials.mini_xml___asts_.inherited_attribute"></a><h6>
+<a name="id1044935"></a>
+ <a class="link" href="mini_xml___asts_.html#spirit.qi.tutorials.mini_xml___asts_.inherited_attribute">Inherited
           Attribute</a>
- </h5>
+ </h6>
 <p>
- The <tt class="computeroutput"><span class="identifier">end_tag</span></tt>:
+ The <code class="computeroutput"><span class="identifier">end_tag</span></code>:
         </p>
 <pre class="programlisting"><span class="identifier">rule</span><span class="special">&lt;</span><span class="identifier">Iterator</span><span class="special">,</span> <span class="keyword">void</span><span class="special">(</span><span class="identifier">std</span><span class="special">::</span><span class="identifier">string</span><span class="special">),</span> <span class="identifier">space_type</span><span class="special">&gt;</span> <span class="identifier">end_tag</span><span class="special">;</span>
 </pre>
 <p>
- Ohh! Now we see an inherited attribute there: <tt class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">string</span></tt>.
- The <tt class="computeroutput"><span class="identifier">end_tag</span></tt> does not have
+ Ohh! Now we see an inherited attribute there: <code class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">string</span></code>.
+ The <code class="computeroutput"><span class="identifier">end_tag</span></code> does not have
           a synthesized attribute. Let's see its definition:
         </p>
 <pre class="programlisting"><span class="identifier">end_tag</span> <span class="special">=</span>
@@ -228,28 +223,28 @@
 <span class="special">;</span>
 </pre>
 <p>
- <tt class="computeroutput"><span class="identifier">_r1</span></tt> is yet another Phoenix placeholder for
- the 1st inherited attribute (we have only one, use <tt class="computeroutput"><span class="identifier">_r2</span></tt>,
- <tt class="computeroutput"><span class="identifier">_r3</span></tt>, etc. if you have more).
- </p>
-<a name="spirit.qi.tutorials.mini_xml___asts_.a_lazy_lit"></a><h5>
-<a name="id433756"></a>
- <a href="mini_xml___asts_.html#spirit.qi.tutorials.mini_xml___asts_.a_lazy_lit">A Lazy
+ <code class="computeroutput"><span class="identifier">_r1</span></code> is yet another Phoenix placeholder for
+ the 1st inherited attribute (we have only one, use <code class="computeroutput"><span class="identifier">_r2</span></code>,
+ <code class="computeroutput"><span class="identifier">_r3</span></code>, etc. if you have more).
+ </p>
+<a name="spirit.qi.tutorials.mini_xml___asts_.a_lazy_lit"></a><h6>
+<a name="id1045130"></a>
+ <a class="link" href="mini_xml___asts_.html#spirit.qi.tutorials.mini_xml___asts_.a_lazy_lit">A Lazy
           Lit</a>
- </h5>
+ </h6>
 <p>
- Check out how we used <tt class="computeroutput"><span class="identifier">lit</span></tt>
+ Check out how we used <code class="computeroutput"><span class="identifier">lit</span></code>
           here, this time, not with a literal string, but with the value of the 1st
- inherited attribute, which is specified as <tt class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">string</span></tt>
+ inherited attribute, which is specified as <code class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">string</span></code>
           in our rule declaration.
         </p>
 <p>
- Finally, our <tt class="computeroutput"><span class="identifier">xml</span></tt> rule:
+ Finally, our <code class="computeroutput"><span class="identifier">xml</span></code> rule:
         </p>
 <pre class="programlisting"><span class="identifier">rule</span><span class="special">&lt;</span><span class="identifier">Iterator</span><span class="special">,</span> <span class="identifier">mini_xml</span><span class="special">(),</span> <span class="identifier">space_type</span><span class="special">&gt;</span> <span class="identifier">xml</span><span class="special">;</span>
 </pre>
 <p>
- <tt class="computeroutput"><span class="identifier">mini_xml</span></tt> is our attribute
+ <code class="computeroutput"><span class="identifier">mini_xml</span></code> is our attribute
           here. We'll see later what it is. Let's see its definition:
         </p>
 <pre class="programlisting"><span class="identifier">xml</span> <span class="special">=</span>
@@ -260,37 +255,37 @@
 </pre>
 <p>
           Those who know Fusion
- now will notice <tt class="computeroutput"><span class="identifier">at_c</span><span class="special">&lt;</span><span class="number">0</span><span class="special">&gt;</span></tt> and
- <tt class="computeroutput"><span class="identifier">at_c</span><span class="special">&lt;</span><span class="number">1</span><span class="special">&gt;</span></tt>. This
- gives us a hint that <tt class="computeroutput"><span class="identifier">mini_xml</span></tt>
- is a sort of a tuple - a fusion sequence. <tt class="computeroutput"><span class="identifier">at_c</span><span class="special">&lt;</span><span class="identifier">N</span><span class="special">&gt;</span></tt> here is a lazy version of the tuple
+ now will notice <code class="computeroutput"><span class="identifier">at_c</span><span class="special">&lt;</span><span class="number">0</span><span class="special">&gt;</span></code> and
+ <code class="computeroutput"><span class="identifier">at_c</span><span class="special">&lt;</span><span class="number">1</span><span class="special">&gt;</span></code>. This
+ gives us a hint that <code class="computeroutput"><span class="identifier">mini_xml</span></code>
+ is a sort of a tuple - a fusion sequence. <code class="computeroutput"><span class="identifier">at_c</span><span class="special">&lt;</span><span class="identifier">N</span><span class="special">&gt;</span></code> here is a lazy version of the tuple
           accessors, provided by Phoenix.
         </p>
-<a name="spirit.qi.tutorials.mini_xml___asts_.how_it_all_works"></a><h5>
-<a name="id434236"></a>
- <a href="mini_xml___asts_.html#spirit.qi.tutorials.mini_xml___asts_.how_it_all_works">How
+<a name="spirit.qi.tutorials.mini_xml___asts_.how_it_all_works"></a><h6>
+<a name="id1046558"></a>
+ <a class="link" href="mini_xml___asts_.html#spirit.qi.tutorials.mini_xml___asts_.how_it_all_works">How
           it all works</a>
- </h5>
+ </h6>
 <p>
           So, what's happening?
         </p>
-<div class="orderedlist"><ol type="1">
-<li>
- Upon parsing <tt class="computeroutput"><span class="identifier">start_tag</span></tt>,
- the parsed start-tag string is placed in <tt class="computeroutput"><span class="identifier">at_c</span><span class="special">&lt;</span><span class="number">0</span><span class="special">&gt;(</span><span class="identifier">_val</span><span class="special">)</span></tt>.
- </li>
-<li>
- Then we parse zero or more <tt class="computeroutput"><span class="identifier">node</span></tt>s.
- At each step, we <tt class="computeroutput"><span class="identifier">push_back</span></tt>
- the result into <tt class="computeroutput"><span class="identifier">at_c</span><span class="special">&lt;</span><span class="number">1</span><span class="special">&gt;(</span><span class="identifier">_val</span><span class="special">)</span></tt>.
- </li>
-<li>
- Finally, we parse the <tt class="computeroutput"><span class="identifier">end_tag</span></tt>
- giving it an inherited attribute: <tt class="computeroutput"><span class="identifier">at_c</span><span class="special">&lt;</span><span class="number">0</span><span class="special">&gt;(</span><span class="identifier">_val</span><span class="special">)</span></tt>.
- This is the string we obtained from the <tt class="computeroutput"><span class="identifier">start_tag</span></tt>.
- Investigate <tt class="computeroutput"><span class="identifier">end_tag</span></tt> above.
+<div class="orderedlist"><ol class="orderedlist" type="1">
+<li class="listitem">
+ Upon parsing <code class="computeroutput"><span class="identifier">start_tag</span></code>,
+ the parsed start-tag string is placed in <code class="computeroutput"><span class="identifier">at_c</span><span class="special">&lt;</span><span class="number">0</span><span class="special">&gt;(</span><span class="identifier">_val</span><span class="special">)</span></code>.
+ </li>
+<li class="listitem">
+ Then we parse zero or more <code class="computeroutput"><span class="identifier">node</span></code>s.
+ At each step, we <code class="computeroutput"><span class="identifier">push_back</span></code>
+ the result into <code class="computeroutput"><span class="identifier">at_c</span><span class="special">&lt;</span><span class="number">1</span><span class="special">&gt;(</span><span class="identifier">_val</span><span class="special">)</span></code>.
+ </li>
+<li class="listitem">
+ Finally, we parse the <code class="computeroutput"><span class="identifier">end_tag</span></code>
+ giving it an inherited attribute: <code class="computeroutput"><span class="identifier">at_c</span><span class="special">&lt;</span><span class="number">0</span><span class="special">&gt;(</span><span class="identifier">_val</span><span class="special">)</span></code>.
+ This is the string we obtained from the <code class="computeroutput"><span class="identifier">start_tag</span></code>.
+ Investigate <code class="computeroutput"><span class="identifier">end_tag</span></code> above.
             It will fail to parse if it gets something different from what we got
- from the <tt class="computeroutput"><span class="identifier">start_tag</span></tt>. This
+ from the <code class="computeroutput"><span class="identifier">start_tag</span></code>. This
             ensures that our tags are balanced.
           </li>
 </ol></div>
@@ -309,15 +304,15 @@
 <span class="special">;</span>
 </pre>
 <p>
- passing in <tt class="computeroutput"><span class="identifier">at_c</span><span class="special">&lt;</span><span class="number">0</span><span class="special">&gt;(</span><span class="identifier">_val</span><span class="special">)</span></tt>, the string from start tag. This is referred
- to in the <tt class="computeroutput"><span class="identifier">end_tag</span></tt> body
- as <tt class="computeroutput"><span class="identifier">_r1</span></tt>.
- </p>
-<a name="spirit.qi.tutorials.mini_xml___asts_.the_structures"></a><h5>
-<a name="id434679"></a>
- <a href="mini_xml___asts_.html#spirit.qi.tutorials.mini_xml___asts_.the_structures">The
+ passing in <code class="computeroutput"><span class="identifier">at_c</span><span class="special">&lt;</span><span class="number">0</span><span class="special">&gt;(</span><span class="identifier">_val</span><span class="special">)</span></code>, the string from start tag. This is referred
+ to in the <code class="computeroutput"><span class="identifier">end_tag</span></code> body
+ as <code class="computeroutput"><span class="identifier">_r1</span></code>.
+ </p>
+<a name="spirit.qi.tutorials.mini_xml___asts_.the_structures"></a><h6>
+<a name="id1046854"></a>
+ <a class="link" href="mini_xml___asts_.html#spirit.qi.tutorials.mini_xml___asts_.the_structures">The
           Structures</a>
- </h5>
+ </h6>
 <p>
           Let's see our structures. It will definitely be hierarchical: xml is hierarchical.
           It will also be recursive: xml is recursive.
@@ -346,17 +341,17 @@
           </p>
 <p>
         </p>
-<a name="spirit.qi.tutorials.mini_xml___asts_.of_alternates_and_variants"></a><h5>
-<a name="id434947"></a>
- <a href="mini_xml___asts_.html#spirit.qi.tutorials.mini_xml___asts_.of_alternates_and_variants">Of
+<a name="spirit.qi.tutorials.mini_xml___asts_.of_alternates_and_variants"></a><h6>
+<a name="id1047050"></a>
+ <a class="link" href="mini_xml___asts_.html#spirit.qi.tutorials.mini_xml___asts_.of_alternates_and_variants">Of
           Alternates and Variants</a>
- </h5>
+ </h6>
 <p>
- So that's how a <tt class="computeroutput"><span class="identifier">mini_xml_node</span></tt>
- looks like. We had a hint that it is either a <tt class="computeroutput"><span class="identifier">string</span></tt>
- or a <tt class="computeroutput"><span class="identifier">mini_xml</span></tt>. For this,
- we use boost.variant<>.
- <tt class="computeroutput"><span class="identifier">boost</span><span class="special">::</span><span class="identifier">recursive_wrapper</span></tt> wraps <tt class="computeroutput"><span class="identifier">mini_xml</span></tt>, making it a recursive data
+ So that's how a <code class="computeroutput"><span class="identifier">mini_xml_node</span></code>
+ looks like. We had a hint that it is either a <code class="computeroutput"><span class="identifier">string</span></code>
+ or a <code class="computeroutput"><span class="identifier">mini_xml</span></code>. For this,
+ we use boost.variant<>.
+ <code class="computeroutput"><span class="identifier">boost</span><span class="special">::</span><span class="identifier">recursive_wrapper</span></code> wraps <code class="computeroutput"><span class="identifier">mini_xml</span></code>, making it a recursive data
           structure.
         </p>
 <p>
@@ -370,16 +365,16 @@
 <pre class="programlisting"><span class="identifier">boost</span><span class="special">::</span><span class="identifier">variant</span><span class="special">&lt;</span><span class="identifier">A</span><span class="special">,</span> <span class="identifier">B</span><span class="special">&gt;</span>
 </pre>
 <p>
- where <tt class="computeroutput"><span class="identifier">A</span></tt> is the attribute
- of <tt class="computeroutput"><span class="identifier">a</span></tt> and <tt class="computeroutput"><span class="identifier">B</span></tt> is the attribute of <tt class="computeroutput"><span class="identifier">b</span></tt>.
+ where <code class="computeroutput"><span class="identifier">A</span></code> is the attribute
+ of <code class="computeroutput"><span class="identifier">a</span></code> and <code class="computeroutput"><span class="identifier">B</span></code> is the attribute of <code class="computeroutput"><span class="identifier">b</span></code>.
         </p>
-<a name="spirit.qi.tutorials.mini_xml___asts_.adapting_structs_again"></a><h5>
-<a name="id435213"></a>
- <a href="mini_xml___asts_.html#spirit.qi.tutorials.mini_xml___asts_.adapting_structs_again">Adapting
+<a name="spirit.qi.tutorials.mini_xml___asts_.adapting_structs_again"></a><h6>
+<a name="id1047230"></a>
+ <a class="link" href="mini_xml___asts_.html#spirit.qi.tutorials.mini_xml___asts_.adapting_structs_again">Adapting
           structs again</a>
- </h5>
+ </h6>
 <p>
- <tt class="computeroutput"><span class="identifier">mini_xml</span></tt> is no brainier.
+ <code class="computeroutput"><span class="identifier">mini_xml</span></code> is no brainier.
           It is a plain ol' struct. But as we've seen in our employee example, we
           can adapt that to be a Fusion
           sequence:
@@ -399,11 +394,11 @@
           </p>
 <p>
         </p>
-<a name="spirit.qi.tutorials.mini_xml___asts_.one_more_take"></a><h5>
-<a name="id435411"></a>
- <a href="mini_xml___asts_.html#spirit.qi.tutorials.mini_xml___asts_.one_more_take">One
+<a name="spirit.qi.tutorials.mini_xml___asts_.one_more_take"></a><h6>
+<a name="id1047370"></a>
+ <a class="link" href="mini_xml___asts_.html#spirit.qi.tutorials.mini_xml___asts_.one_more_take">One
           More Take</a>
- </h5>
+ </h6>
 <p>
           Here's another version. The AST structure remains the same, but this time,
           you'll see that we make use of auto-rules making the grammar semantic-action-
@@ -466,19 +461,19 @@
           the first xml parser example. The rules are almost the same, except that,
           we got rid of semantic actions and used auto-rules (see the employee example
           if you missed that). There are a couple of new stuff, though. It's all
- in the <tt class="computeroutput"><span class="identifier">xml</span></tt> rule:
+ in the <code class="computeroutput"><span class="identifier">xml</span></code> rule:
         </p>
-<a name="spirit.qi.tutorials.mini_xml___asts_.local_variables"></a><h5>
-<a name="id436656"></a>
- <a href="mini_xml___asts_.html#spirit.qi.tutorials.mini_xml___asts_.local_variables">Local
+<a name="spirit.qi.tutorials.mini_xml___asts_.local_variables"></a><h6>
+<a name="id1048286"></a>
+ <a class="link" href="mini_xml___asts_.html#spirit.qi.tutorials.mini_xml___asts_.local_variables">Local
           Variables</a>
- </h5>
+ </h6>
 <pre class="programlisting"><span class="identifier">rule</span><span class="special">&lt;</span><span class="identifier">Iterator</span><span class="special">,</span> <span class="identifier">mini_xml</span><span class="special">(),</span> <span class="identifier">locals</span><span class="special">&lt;</span><span class="identifier">std</span><span class="special">::</span><span class="identifier">string</span><span class="special">&gt;,</span> <span class="identifier">space_type</span><span class="special">&gt;</span> <span class="identifier">xml</span><span class="special">;</span>
 </pre>
 <p>
- Wow, we have four template parameters now. What's that <tt class="computeroutput"><span class="identifier">locals</span></tt>
- guy doing there? Well, it declares that the rule <tt class="computeroutput"><span class="identifier">xml</span></tt>
- will have one local variable: a <tt class="computeroutput"><span class="identifier">string</span></tt>.
+ Wow, we have four template parameters now. What's that <code class="computeroutput"><span class="identifier">locals</span></code>
+ guy doing there? Well, it declares that the rule <code class="computeroutput"><span class="identifier">xml</span></code>
+ will have one local variable: a <code class="computeroutput"><span class="identifier">string</span></code>.
           Let's see how this is used in action:
         </p>
 <pre class="programlisting"><span class="identifier">xml</span> <span class="special">%=</span>
@@ -487,25 +482,25 @@
     <span class="special">&gt;&gt;</span> <span class="identifier">end_tag</span><span class="special">(</span><span class="identifier">_a</span><span class="special">)</span>
 <span class="special">;</span>
 </pre>
-<div class="orderedlist"><ol type="1">
-<li>
- Upon parsing <tt class="computeroutput"><span class="identifier">start_tag</span></tt>,
+<div class="orderedlist"><ol class="orderedlist" type="1">
+<li class="listitem">
+ Upon parsing <code class="computeroutput"><span class="identifier">start_tag</span></code>,
             the parsed start-tag string is placed in the local variable specified
             by (yet another) Phoenix
- placeholder: <tt class="computeroutput"><span class="identifier">_a</span></tt>. We have
- only one local variable. If we had more, these are designated by <tt class="computeroutput"><span class="identifier">_b</span></tt>..<tt class="computeroutput"><span class="identifier">_z</span></tt>.
+ placeholder: <code class="computeroutput"><span class="identifier">_a</span></code>. We have
+ only one local variable. If we had more, these are designated by <code class="computeroutput"><span class="identifier">_b</span></code>..<code class="computeroutput"><span class="identifier">_z</span></code>.
           </li>
-<li>
- Then we parse zero or more <tt class="computeroutput"><span class="identifier">node</span></tt>s.
+<li class="listitem">
+ Then we parse zero or more <code class="computeroutput"><span class="identifier">node</span></code>s.
           </li>
-<li>
- Finally, we parse the <tt class="computeroutput"><span class="identifier">end_tag</span></tt>
- giving it an inherited attribute: <tt class="computeroutput"><span class="identifier">_a</span></tt>,
+<li class="listitem">
+ Finally, we parse the <code class="computeroutput"><span class="identifier">end_tag</span></code>
+ giving it an inherited attribute: <code class="computeroutput"><span class="identifier">_a</span></code>,
             our local variable.
           </li>
 </ol></div>
 <p>
- There are no actions involved in stuffing data into our <tt class="computeroutput"><span class="identifier">xml</span></tt>
+ There are no actions involved in stuffing data into our <code class="computeroutput"><span class="identifier">xml</span></code>
           attribute. It's all taken cared of thatnks to the auto-rule.
         </p>
 </div>

Modified: trunk/libs/spirit/doc/html/spirit/qi/tutorials/mini_xml___error_handling.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/qi/tutorials/mini_xml___error_handling.html (original)
+++ trunk/libs/spirit/doc/html/spirit/qi/tutorials/mini_xml___error_handling.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -1,13 +1,12 @@
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title>Mini
- XML - Error Handling</title>
+<title>Mini XML - Error Handling</title>
 <link rel="stylesheet" href="../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../index.html" title="Spirit 2.1">
 <link rel="up" href="../tutorials.html" title="Tutorials">
-<link rel="previous" href="mini_xml___asts_.html" title="Mini XML - ASTs!">
+<link rel="prev" href="mini_xml___asts_.html" title="Mini XML - ASTs!">
 <link rel="next" href="../quick_reference.html" title="Quick Reference">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -23,15 +22,11 @@
 <div class="spirit-nav">
 <a accesskey="p" href="mini_xml___asts_.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../tutorials.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="../quick_reference.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h4 class="title">
-<a name="spirit.qi.tutorials.mini_xml___error_handling"></a><a href="mini_xml___error_handling.html" title="Mini
- XML - Error Handling">Mini
+<div class="section" title="Mini XML - Error Handling">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="spirit.qi.tutorials.mini_xml___error_handling"></a><a class="link" href="mini_xml___error_handling.html" title="Mini XML - Error Handling">Mini
         XML - Error Handling</a>
-</h4></div></div>
-<div></div>
-</div>
+</h4></div></div></div>
 <p>
           A parser will not be complete without error handling. Spirit2 provides
           some facilities to make it easy to adapt a grammar for error handling.
@@ -48,11 +43,11 @@
 <p>
           What's new?
         </p>
-<a name="spirit.qi.tutorials.mini_xml___error_handling.readable_names"></a><h5>
-<a name="id437109"></a>
- <a href="mini_xml___error_handling.html#spirit.qi.tutorials.mini_xml___error_handling.readable_names">Readable
+<a name="spirit.qi.tutorials.mini_xml___error_handling.readable_names"></a><h6>
+<a name="id1049690"></a>
+ <a class="link" href="mini_xml___error_handling.html#spirit.qi.tutorials.mini_xml___error_handling.readable_names">Readable
           Names</a>
- </h5>
+ </h6>
 <p>
           First, when we call the base class, we give the grammar a name:
         </p>
@@ -67,13 +62,13 @@
 <span class="identifier">start_tag</span><span class="special">.</span><span class="identifier">name</span><span class="special">(</span><span class="string">"start_tag"</span><span class="special">);</span>
 <span class="identifier">end_tag</span><span class="special">.</span><span class="identifier">name</span><span class="special">(</span><span class="string">"end_tag"</span><span class="special">);</span>
 </pre>
-<a name="spirit.qi.tutorials.mini_xml___error_handling.on_error"></a><h5>
-<a name="id437360"></a>
- <a href="mini_xml___error_handling.html#spirit.qi.tutorials.mini_xml___error_handling.on_error">On
+<a name="spirit.qi.tutorials.mini_xml___error_handling.on_error"></a><h6>
+<a name="id1049870"></a>
+ <a class="link" href="mini_xml___error_handling.html#spirit.qi.tutorials.mini_xml___error_handling.on_error">On
           Error</a>
- </h5>
+ </h6>
 <p>
- <tt class="computeroutput"><span class="identifier">on_error</span></tt> declares our error
+ <code class="computeroutput"><span class="identifier">on_error</span></code> declares our error
           handler:
         </p>
 <pre class="programlisting"><span class="identifier">on_error</span><span class="special">&lt;</span><span class="identifier">Action</span><span class="special">&gt;(</span><span class="identifier">rule</span><span class="special">,</span> <span class="identifier">handler</span><span class="special">)</span>
@@ -95,8 +90,8 @@
 <span class="special">);</span>
 </pre>
 <p>
- we choose to <tt class="computeroutput"><span class="identifier">fail</span></tt> in our
- example for the <tt class="computeroutput"><span class="identifier">Action</span></tt>:
+ we choose to <code class="computeroutput"><span class="identifier">fail</span></code> in our
+ example for the <code class="computeroutput"><span class="identifier">Action</span></code>:
           Quit and fail. Return a no_match (false). It can be one of:
         </p>
 <div class="informaltable"><table class="table">
@@ -105,55 +100,75 @@
 <col>
 </colgroup>
 <thead><tr>
-<th><p>
- <tt class="computeroutput"><span class="identifier">Action</span></tt>
- </p></th>
-<th><p>
+<th>
+ <p>
+ <code class="computeroutput"><span class="identifier">Action</span></code>
+ </p>
+ </th>
+<th>
+ <p>
                   Description
- </p></th>
+ </p>
+ </th>
 </tr></thead>
 <tbody>
 <tr>
-<td><p>
+<td>
+ <p>
                   fail
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
                   Quit and fail. Return a no_match.
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
+<td>
+ <p>
                   retry
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
                   Attempt error recovery, possibly moving the iterator position.
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
+<td>
+ <p>
                   accept
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
                   Force success, moving the iterator position appropriately.
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
+<td>
+ <p>
                   rethrow
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
                   Rethrows the error.
- </p></td>
+ </p>
+ </td>
 </tr>
 </tbody>
 </table></div>
 <p>
- <tt class="computeroutput"><span class="identifier">rule</span></tt> is the rule we attach
- the handler to. In our case, we are attaching to the <tt class="computeroutput"><span class="identifier">xml</span></tt>
+ <code class="computeroutput"><span class="identifier">rule</span></code> is the rule we attach
+ the handler to. In our case, we are attaching to the <code class="computeroutput"><span class="identifier">xml</span></code>
           rule.
         </p>
 <p>
- <tt class="computeroutput"><span class="identifier">handler</span></tt> is the actual error
+ <code class="computeroutput"><span class="identifier">handler</span></code> is the actual error
           handling function. It expects 4 arguments:
         </p>
 <div class="informaltable"><table class="table">
@@ -162,57 +177,77 @@
 <col>
 </colgroup>
 <thead><tr>
-<th><p>
+<th>
+ <p>
                   Arg
- </p></th>
-<th><p>
+ </p>
+ </th>
+<th>
+ <p>
                   Description
- </p></th>
+ </p>
+ </th>
 </tr></thead>
 <tbody>
 <tr>
-<td><p>
+<td>
+ <p>
                   first
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
                   The position of the iterator when the rule with the handler was
                   entered.
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
+<td>
+ <p>
                   last
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
                   The end of input.
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
+<td>
+ <p>
                   error-pos
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
                   The actual position of the iterator where the error occurred.
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
+<td>
+ <p>
                   what
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
                   What failed: a string decribing the failure.
- </p></td>
+ </p>
+ </td>
 </tr>
 </tbody>
 </table></div>
-<a name="spirit.qi.tutorials.mini_xml___error_handling.expectation_points"></a><h5>
-<a name="id438030"></a>
- <a href="mini_xml___error_handling.html#spirit.qi.tutorials.mini_xml___error_handling.expectation_points">Expectation
+<a name="spirit.qi.tutorials.mini_xml___error_handling.expectation_points"></a><h6>
+<a name="id1050378"></a>
+ <a class="link" href="mini_xml___error_handling.html#spirit.qi.tutorials.mini_xml___error_handling.expectation_points">Expectation
           Points</a>
- </h5>
+ </h6>
 <p>
           You might not have noticed it, but some of our expressions changed from
- using the <tt class="computeroutput"><span class="special">&gt;&gt;</span></tt> to <tt class="computeroutput"><span class="special">&gt;</span></tt>. Look, for example:
+ using the <code class="computeroutput"><span class="special">&gt;&gt;</span></code> to <code class="computeroutput"><span class="special">&gt;</span></code>. Look, for example:
         </p>
 <pre class="programlisting"><span class="identifier">end_tag</span> <span class="special">=</span>
         <span class="string">"&lt;/"</span>
@@ -223,10 +258,10 @@
 <p>
           What is it? It's the <span class="emphasis"><em>expectation</em></span> operator. You will
           have some "deterministic points" in the grammar. Those are the
- places where backtracking <span class="bold"><b>cannot</b></span> occur.
- For our example above, when you get a <tt class="computeroutput"><span class="string">"&lt;/"</span></tt>,
+ places where backtracking <span class="bold"><strong>cannot</strong></span> occur.
+ For our example above, when you get a <code class="computeroutput"><span class="string">"&lt;/"</span></code>,
           you definitely must see a valid end-tag label next. It should be the one
- you got from the start-tag. After that, you definitely must have a <tt class="computeroutput"><span class="char">'&gt;'</span></tt> next. Otherwise, there is no point in
+ you got from the start-tag. After that, you definitely must have a <code class="computeroutput"><span class="char">'&gt;'</span></code> next. Otherwise, there is no point in
           proceeding forward and trying other branches, regardless where they are.
           The input is definitely erroneous. When this happens, an expectation_failure
           exception is thrown. Somewhere outward, the error handler will catch the

Modified: trunk/libs/spirit/doc/html/spirit/qi/tutorials/number_list___stuffing_numbers_into_a_std__vector.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/qi/tutorials/number_list___stuffing_numbers_into_a_std__vector.html (original)
+++ trunk/libs/spirit/doc/html/spirit/qi/tutorials/number_list___stuffing_numbers_into_a_std__vector.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -1,16 +1,13 @@
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title>Number
- List - stuffing numbers into a std::vector</title>
+<title>Number List - stuffing numbers into a std::vector</title>
 <link rel="stylesheet" href="../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../index.html" title="Spirit 2.1">
 <link rel="up" href="../tutorials.html" title="Tutorials">
-<link rel="previous" href="sum___adding_numbers.html" title="Sum - adding
- numbers">
-<link rel="next" href="number_list_redux___list_syntax.html" title="Number
- List Redux - list syntax">
+<link rel="prev" href="sum___adding_numbers.html" title="Sum - adding numbers">
+<link rel="next" href="number_list_redux___list_syntax.html" title="Number List Redux - list syntax">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
 <table cellpadding="2" width="100%"><tr>
@@ -25,15 +22,11 @@
 <div class="spirit-nav">
 <a accesskey="p" href="sum___adding_numbers.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../tutorials.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="number_list_redux___list_syntax.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h4 class="title">
-<a name="spirit.qi.tutorials.number_list___stuffing_numbers_into_a_std__vector"></a><a href="number_list___stuffing_numbers_into_a_std__vector.html" title="Number
- List - stuffing numbers into a std::vector">Number
+<div class="section" title="Number List - stuffing numbers into a std::vector">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="spirit.qi.tutorials.number_list___stuffing_numbers_into_a_std__vector"></a><a class="link" href="number_list___stuffing_numbers_into_a_std__vector.html" title="Number List - stuffing numbers into a std::vector">Number
         List - stuffing numbers into a std::vector</a>
-</h4></div></div>
-<div></div>
-</div>
+</h4></div></div></div>
 <p>
           This sample demontrates a parser for a comma separated list of numbers.
           The numbers are inserted in a vector using phoenix.
@@ -79,18 +72,18 @@
         </p>
 <p>
           This, again, is the same parser as before. This time, instead of summing
- up the numbers, we stuff them in a <tt class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">vector</span></tt>.
- <tt class="computeroutput"><span class="identifier">push_back</span></tt> is supplied by
+ up the numbers, we stuff them in a <code class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">vector</span></code>.
+ <code class="computeroutput"><span class="identifier">push_back</span></code> is supplied by
           <a href="../../../../../phoenix/doc/html/index.html" target="_top">Phoenix</a>. The expression:
         </p>
 <pre class="programlisting"><span class="identifier">push_back</span><span class="special">(</span><span class="identifier">ref</span><span class="special">(</span><span class="identifier">v</span><span class="special">),</span> <span class="identifier">_1</span><span class="special">)</span>
 </pre>
 <p>
- appends the parsed number. Like before, <tt class="computeroutput"><span class="identifier">_1</span></tt>
+ appends the parsed number. Like before, <code class="computeroutput"><span class="identifier">_1</span></code>
           is a Phoenix placeholder
- for the parsed result attribute. Also, like before, <tt class="computeroutput"><span class="identifier">ref</span><span class="special">(</span><span class="identifier">v</span><span class="special">)</span></tt>
+ for the parsed result attribute. Also, like before, <code class="computeroutput"><span class="identifier">ref</span><span class="special">(</span><span class="identifier">v</span><span class="special">)</span></code>
           tells Phoenix that
- <tt class="computeroutput"><span class="identifier">v</span></tt>, the <tt class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">vector</span></tt>,
+ <code class="computeroutput"><span class="identifier">v</span></code>, the <code class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">vector</span></code>,
           is a mutable reference.
         </p>
 </div>

Modified: trunk/libs/spirit/doc/html/spirit/qi/tutorials/number_list_attribute___one_more__with_style.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/qi/tutorials/number_list_attribute___one_more__with_style.html (original)
+++ trunk/libs/spirit/doc/html/spirit/qi/tutorials/number_list_attribute___one_more__with_style.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -1,14 +1,12 @@
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title>Number
- List Attribute - one more, with style</title>
+<title>Number List Attribute - one more, with style</title>
 <link rel="stylesheet" href="../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../index.html" title="Spirit 2.1">
 <link rel="up" href="../tutorials.html" title="Tutorials">
-<link rel="previous" href="number_list_redux___list_syntax.html" title="Number
- List Redux - list syntax">
+<link rel="prev" href="number_list_redux___list_syntax.html" title="Number List Redux - list syntax">
 <link rel="next" href="roman_numerals.html" title="Roman Numerals">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -24,18 +22,14 @@
 <div class="spirit-nav">
 <a accesskey="p" href="number_list_redux___list_syntax.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../tutorials.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="roman_numerals.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h4 class="title">
-<a name="spirit.qi.tutorials.number_list_attribute___one_more__with_style"></a><a href="number_list_attribute___one_more__with_style.html" title="Number
- List Attribute - one more, with style">Number
+<div class="section" title="Number List Attribute - one more, with style">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="spirit.qi.tutorials.number_list_attribute___one_more__with_style"></a><a class="link" href="number_list_attribute___one_more__with_style.html" title="Number List Attribute - one more, with style">Number
         List Attribute - one more, with style</a>
-</h4></div></div>
-<div></div>
-</div>
+</h4></div></div></div>
 <p>
- You've seen that the <tt class="computeroutput"><span class="identifier">double_</span></tt>
- parser has a <tt class="computeroutput"><span class="keyword">double</span></tt> attribute.
+ You've seen that the <code class="computeroutput"><span class="identifier">double_</span></code>
+ parser has a <code class="computeroutput"><span class="keyword">double</span></code> attribute.
           All parsers have an attribute, even complex parsers, those that are composed
           from primitives using operators, like the list parser, also have an attribute.
           It so happens that the the attribute of a list parser:
@@ -43,7 +37,7 @@
 <pre class="programlisting"><span class="identifier">p</span> <span class="special">%</span> <span class="identifier">d</span>
 </pre>
 <p>
- is a <tt class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">vector</span></tt> of the attribute of <tt class="computeroutput"><span class="identifier">p</span></tt>. So, for our parser:
+ is a <code class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">vector</span></code> of the attribute of <code class="computeroutput"><span class="identifier">p</span></code>. So, for our parser:
         </p>
 <pre class="programlisting"><span class="identifier">double_</span> <span class="special">%</span> <span class="char">','</span>
 </pre>
@@ -53,25 +47,25 @@
 <pre class="programlisting"><span class="identifier">std</span><span class="special">::</span><span class="identifier">vector</span><span class="special">&lt;</span><span class="keyword">double</span><span class="special">&gt;</span>
 </pre>
 <p>
- So, what does this give us? Well, we can simply pass in a <tt class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">vector</span><span class="special">&lt;</span><span class="keyword">double</span><span class="special">&gt;</span></tt>
+ So, what does this give us? Well, we can simply pass in a <code class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">vector</span><span class="special">&lt;</span><span class="keyword">double</span><span class="special">&gt;</span></code>
           to our number list parser and it will happily churn out our result in our
- vector. For that to happen, we'll use a variation of the <tt class="computeroutput"><span class="identifier">phrase_parse</span></tt> with an additional argument:
+ vector. For that to happen, we'll use a variation of the <code class="computeroutput"><span class="identifier">phrase_parse</span></code> with an additional argument:
           the parser's attribute:
         </p>
-<div class="orderedlist"><ol type="1">
-<li>
+<div class="orderedlist"><ol class="orderedlist" type="1">
+<li class="listitem">
             An iterator pointing to the start of the input
           </li>
-<li>
+<li class="listitem">
             An iterator pointing to one past the end of the input
           </li>
-<li>
+<li class="listitem">
             The parser object
           </li>
-<li>
+<li class="listitem">
             The parser's attribute
           </li>
-<li>
+<li class="listitem">
             Another parser called the skip parser
           </li>
 </ol></div>
@@ -115,7 +109,7 @@
           The full cpp file for this example can be found here: ../../example/qi/num_list4.cpp
         </p>
 <p>
- <span class="bold"><b>Hey, no more actions!!!</b></span> Now we're entering
+ <span class="bold"><strong>Hey, no more actions!!!</strong></span> Now we're entering
           the realm of attribute grammars. Cool eh?
         </p>
 </div>

Modified: trunk/libs/spirit/doc/html/spirit/qi/tutorials/number_list_redux___list_syntax.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/qi/tutorials/number_list_redux___list_syntax.html (original)
+++ trunk/libs/spirit/doc/html/spirit/qi/tutorials/number_list_redux___list_syntax.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -1,16 +1,13 @@
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title>Number
- List Redux - list syntax</title>
+<title>Number List Redux - list syntax</title>
 <link rel="stylesheet" href="../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../index.html" title="Spirit 2.1">
 <link rel="up" href="../tutorials.html" title="Tutorials">
-<link rel="previous" href="number_list___stuffing_numbers_into_a_std__vector.html" title="Number
- List - stuffing numbers into a std::vector">
-<link rel="next" href="number_list_attribute___one_more__with_style.html" title="Number
- List Attribute - one more, with style">
+<link rel="prev" href="number_list___stuffing_numbers_into_a_std__vector.html" title="Number List - stuffing numbers into a std::vector">
+<link rel="next" href="number_list_attribute___one_more__with_style.html" title="Number List Attribute - one more, with style">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
 <table cellpadding="2" width="100%"><tr>
@@ -25,15 +22,11 @@
 <div class="spirit-nav">
 <a accesskey="p" href="number_list___stuffing_numbers_into_a_std__vector.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../tutorials.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="number_list_attribute___one_more__with_style.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h4 class="title">
-<a name="spirit.qi.tutorials.number_list_redux___list_syntax"></a><a href="number_list_redux___list_syntax.html" title="Number
- List Redux - list syntax">Number
+<div class="section" title="Number List Redux - list syntax">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="spirit.qi.tutorials.number_list_redux___list_syntax"></a><a class="link" href="number_list_redux___list_syntax.html" title="Number List Redux - list syntax">Number
         List Redux - list syntax</a>
-</h4></div></div>
-<div></div>
-</div>
+</h4></div></div></div>
 <p>
           So far, we've been using the syntax:
         </p>
@@ -47,7 +40,7 @@
 <pre class="programlisting"><span class="identifier">double_</span> <span class="special">%</span> <span class="char">','</span>
 </pre>
 <p>
- read as: a list of doubles separated by <tt class="computeroutput"><span class="char">','</span></tt>.
+ read as: a list of doubles separated by <code class="computeroutput"><span class="char">','</span></code>.
         </p>
 <p>
           This sample, again a variation of our previous example, demonstrates just

Modified: trunk/libs/spirit/doc/html/spirit/qi/tutorials/quick_start.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/qi/tutorials/quick_start.html (original)
+++ trunk/libs/spirit/doc/html/spirit/qi/tutorials/quick_start.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -3,10 +3,10 @@
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <title>Quick Start</title>
 <link rel="stylesheet" href="../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../index.html" title="Spirit 2.1">
 <link rel="up" href="../tutorials.html" title="Tutorials">
-<link rel="previous" href="../tutorials.html" title="Tutorials">
+<link rel="prev" href="../tutorials.html" title="Tutorials">
 <link rel="next" href="warming_up.html" title="Warming up">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -22,18 +22,15 @@
 <div class="spirit-nav">
 <a accesskey="p" href="../tutorials.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../tutorials.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="warming_up.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h4 class="title">
-<a name="spirit.qi.tutorials.quick_start"></a>Quick Start
-</h4></div></div>
-<div></div>
-</div>
-<a name="spirit.qi.tutorials.quick_start.why_would_you_want_to_use_spirit_qi_"></a><h5>
-<a name="id415449"></a>
- <a href="quick_start.html#spirit.qi.tutorials.quick_start.why_would_you_want_to_use_spirit_qi_">Why
+<div class="section" title="Quick Start">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="spirit.qi.tutorials.quick_start"></a><a class="link" href="quick_start.html" title="Quick Start">Quick Start</a>
+</h4></div></div></div>
+<a name="spirit.qi.tutorials.quick_start.why_would_you_want_to_use_spirit_qi_"></a><h6>
+<a name="id1027763"></a>
+ <a class="link" href="quick_start.html#spirit.qi.tutorials.quick_start.why_would_you_want_to_use_spirit_qi_">Why
           would you want to use Spirit.Qi?</a>
- </h5>
+ </h6>
 <p>
           Spirit.Qi is designed to be a practical parsing tool. The ability to generate
           a fully-working parser from a formal EBNF specification inlined in C++

Modified: trunk/libs/spirit/doc/html/spirit/qi/tutorials/roman_numerals.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/qi/tutorials/roman_numerals.html (original)
+++ trunk/libs/spirit/doc/html/spirit/qi/tutorials/roman_numerals.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -3,13 +3,11 @@
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <title>Roman Numerals</title>
 <link rel="stylesheet" href="../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../index.html" title="Spirit 2.1">
 <link rel="up" href="../tutorials.html" title="Tutorials">
-<link rel="previous" href="number_list_attribute___one_more__with_style.html" title="Number
- List Attribute - one more, with style">
-<link rel="next" href="employee___parsing_into_structs.html" title="Employee
- - Parsing into structs">
+<link rel="prev" href="number_list_attribute___one_more__with_style.html" title="Number List Attribute - one more, with style">
+<link rel="next" href="employee___parsing_into_structs.html" title="Employee - Parsing into structs">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
 <table cellpadding="2" width="100%"><tr>
@@ -24,35 +22,32 @@
 <div class="spirit-nav">
 <a accesskey="p" href="number_list_attribute___one_more__with_style.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../tutorials.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="employee___parsing_into_structs.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h4 class="title">
-<a name="spirit.qi.tutorials.roman_numerals"></a>Roman Numerals
-</h4></div></div>
-<div></div>
-</div>
+<div class="section" title="Roman Numerals">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="spirit.qi.tutorials.roman_numerals"></a><a class="link" href="roman_numerals.html" title="Roman Numerals">Roman Numerals</a>
+</h4></div></div></div>
 <p>
           This example demonstrates:
         </p>
-<div class="itemizedlist"><ul type="disc">
-<li>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem">
             symbol table
           </li>
-<li>
+<li class="listitem">
             rule
           </li>
-<li>
+<li class="listitem">
             grammar
           </li>
 </ul></div>
-<a name="spirit.qi.tutorials.roman_numerals.symbol_table"></a><h5>
-<a name="id423448"></a>
- <a href="roman_numerals.html#spirit.qi.tutorials.roman_numerals.symbol_table">Symbol
+<a name="spirit.qi.tutorials.roman_numerals.symbol_table"></a><h6>
+<a name="id1035090"></a>
+ <a class="link" href="roman_numerals.html#spirit.qi.tutorials.roman_numerals.symbol_table">Symbol
           Table</a>
- </h5>
+ </h6>
 <p>
           The symbol table holds a dictionary of symbols where each symbol is a sequence
- of characters (a <tt class="computeroutput"><span class="keyword">char</span></tt>, <tt class="computeroutput"><span class="keyword">wchar_t</span></tt>, <tt class="computeroutput"><span class="keyword">int</span></tt>,
+ of characters (a <code class="computeroutput"><span class="keyword">char</span></code>, <code class="computeroutput"><span class="keyword">wchar_t</span></code>, <code class="computeroutput"><span class="keyword">int</span></code>,
           enumeration etc.) . The template class, parameterized by the character
           type, can work efficiently with 8, 16, 32 and even 64 bit characters. Mutable
           data of type T is associated with each symbol.
@@ -173,19 +168,19 @@
 <p>
         </p>
 <p>
- Now we can use <tt class="computeroutput"><span class="identifier">hundreds</span></tt>,
- <tt class="computeroutput"><span class="identifier">tens</span></tt> and <tt class="computeroutput"><span class="identifier">ones</span></tt> anywhere in our parser expressions.
+ Now we can use <code class="computeroutput"><span class="identifier">hundreds</span></code>,
+ <code class="computeroutput"><span class="identifier">tens</span></code> and <code class="computeroutput"><span class="identifier">ones</span></code> anywhere in our parser expressions.
           They are all parsers.
         </p>
-<a name="spirit.qi.tutorials.roman_numerals.rules"></a><h5>
-<a name="id424779"></a>
- Rules
- </h5>
+<a name="spirit.qi.tutorials.roman_numerals.rules"></a><h6>
+<a name="id1037115"></a>
+ <a class="link" href="roman_numerals.html#spirit.qi.tutorials.roman_numerals.rules">Rules</a>
+ </h6>
 <p>
           Up until now, we've been inlining our parser expressions, passing them
- directly to the <tt class="computeroutput"><span class="identifier">phrase_parse</span></tt>
+ directly to the <code class="computeroutput"><span class="identifier">phrase_parse</span></code>
           function. The expression evaluates into a temporary, unnamed parser which
- is passed into the <tt class="computeroutput"><span class="identifier">phrase_parse</span></tt>
+ is passed into the <code class="computeroutput"><span class="identifier">phrase_parse</span></code>
           function, used, and then destroyed. This is fine for small parsers. When
           the expressions get complicated, you'd want to break the expressions into
           smaller easier to understand pieces, name them, and refer to them from
@@ -199,8 +194,8 @@
 </pre>
 <p>
           At the very least, the rule needs to know the iterator type it will be
- working on. This rule cannot be used with <tt class="computeroutput"><span class="identifier">phrase_parse</span></tt>.
- It can only be used with the <tt class="computeroutput"><span class="identifier">parse</span></tt>
+ working on. This rule cannot be used with <code class="computeroutput"><span class="identifier">phrase_parse</span></code>.
+ It can only be used with the <code class="computeroutput"><span class="identifier">parse</span></code>
           function -- a version that does not do white space skipping (does not have
           the skipper argument). If you want to have it skip white spaces, you need
           to pass in the type skip parser, as in the next form:
@@ -213,8 +208,8 @@
 <pre class="programlisting"><span class="identifier">rule</span><span class="special">&lt;</span><span class="identifier">std</span><span class="special">::</span><span class="identifier">string</span><span class="special">::</span><span class="identifier">iterator</span><span class="special">,</span> <span class="identifier">space_type</span><span class="special">&gt;</span> <span class="identifier">r</span><span class="special">;</span>
 </pre>
 <p>
- This type of rule can be used for both <tt class="computeroutput"><span class="identifier">phrase_parse</span></tt>
- and <tt class="computeroutput"><span class="identifier">parse</span></tt>.
+ This type of rule can be used for both <code class="computeroutput"><span class="identifier">phrase_parse</span></code>
+ and <code class="computeroutput"><span class="identifier">parse</span></code>.
         </p>
 <p>
           For our next example, there's one more rule form you should know about:
@@ -226,19 +221,19 @@
         </p>
 <pre class="programlisting"><span class="identifier">rule</span><span class="special">&lt;</span><span class="identifier">Iterator</span><span class="special">,</span> <span class="identifier">Signature</span><span class="special">,</span> <span class="identifier">Skipper</span><span class="special">&gt;</span> <span class="identifier">r</span><span class="special">;</span>
 </pre>
-<div class="tip"><table border="0" summary="Tip">
+<div class="tip" title="Tip"><table border="0" summary="Tip">
 <tr>
 <td rowspan="2" align="center" valign="top" width="25"><img alt="[Tip]" src="../../../images/tip.png"></td>
 <th align="left">Tip</th>
 </tr>
-<tr><td colspan="2" align="left" valign="top"><p>
+<tr><td align="left" valign="top"><p>
             All rule template arguments after Iterator can be supplied in any order.
           </p></td></tr>
 </table></div>
 <p>
           The Signature specifies the attributes of the rule. You've seen that our
- parsers can have an attribute. Recall that the <tt class="computeroutput"><span class="identifier">double_</span></tt>
- parser has an attribute of <tt class="computeroutput"><span class="keyword">double</span></tt>.
+ parsers can have an attribute. Recall that the <code class="computeroutput"><span class="identifier">double_</span></code>
+ parser has an attribute of <code class="computeroutput"><span class="keyword">double</span></code>.
           To be precise, these are <span class="emphasis"><em>synthesized</em></span> attributes. The
           parser "synthesizes" the attribute value. Think of them as function
           return values.
@@ -257,27 +252,27 @@
         </p>
 <pre class="programlisting"><span class="identifier">r</span> <span class="special">=</span> <span class="identifier">double_</span> <span class="special">&gt;&gt;</span> <span class="special">*(</span><span class="char">','</span> <span class="special">&gt;&gt;</span> <span class="identifier">double_</span><span class="special">);</span>
 </pre>
-<a name="spirit.qi.tutorials.roman_numerals.grammars"></a><h5>
-<a name="id425363"></a>
- Grammars
- </h5>
+<a name="spirit.qi.tutorials.roman_numerals.grammars"></a><h6>
+<a name="id1037508"></a>
+ <a class="link" href="roman_numerals.html#spirit.qi.tutorials.roman_numerals.grammars">Grammars</a>
+ </h6>
 <p>
           A grammar encapsulates one or more rules. It has the same template parameters
           as the rule. You declare a grammar by:
         </p>
-<div class="orderedlist"><ol type="1">
-<li>
- deriving a struct (or class) from the <tt class="computeroutput"><span class="identifier">grammar</span></tt>
+<div class="orderedlist"><ol class="orderedlist" type="1">
+<li class="listitem">
+ deriving a struct (or class) from the <code class="computeroutput"><span class="identifier">grammar</span></code>
             class template
           </li>
-<li>
+<li class="listitem">
             declare one or more rules as member variables
           </li>
-<li>
+<li class="listitem">
             initialize the base grammar class by giving it the start rule (its the
             first rule that gets called when the grammar starts parsing)
           </li>
-<li>
+<li class="listitem">
             initialize your rules in your constructor
           </li>
 </ol></div>
@@ -320,52 +315,52 @@
 <p>
           Things to take notice of:
         </p>
-<div class="itemizedlist"><ul type="disc">
-<li>
- The grammar and start rule signature is <tt class="computeroutput"><span class="keyword">unsigned</span><span class="special">()</span></tt>. It has a synthesized attribute (return
- value) of type <tt class="computeroutput"><span class="keyword">unsigned</span></tt>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem">
+ The grammar and start rule signature is <code class="computeroutput"><span class="keyword">unsigned</span><span class="special">()</span></code>. It has a synthesized attribute (return
+ value) of type <code class="computeroutput"><span class="keyword">unsigned</span></code>
             with no inherited attributes (arguments).
           </li>
-<li>
+<li class="listitem">
             We did not specify a skip-parser. We don't want to skip in between the
             numerals.
           </li>
-<li>
-<tt class="computeroutput"><span class="identifier">roman</span><span class="special">::</span><span class="identifier">base_type</span></tt> is a typedef for <tt class="computeroutput"><span class="identifier">grammar</span><span class="special">&lt;</span><span class="identifier">Iterator</span><span class="special">,</span>
- <span class="keyword">unsigned</span><span class="special">()&gt;</span></tt>.
- If <tt class="computeroutput"><span class="identifier">roman</span></tt> was not a template,
+<li class="listitem">
+<code class="computeroutput"><span class="identifier">roman</span><span class="special">::</span><span class="identifier">base_type</span></code> is a typedef for <code class="computeroutput"><span class="identifier">grammar</span><span class="special">&lt;</span><span class="identifier">Iterator</span><span class="special">,</span>
+ <span class="keyword">unsigned</span><span class="special">()&gt;</span></code>.
+ If <code class="computeroutput"><span class="identifier">roman</span></code> was not a template,
             you can simply write: base_type(start)
           </li>
-<li>
+<li class="listitem">
             But it's best to make your grammar templates, so that they can be reused
             for different iterator types.
           </li>
-<li>
-<tt class="computeroutput"><span class="identifier">_val</span></tt> is another Phoenix placeholder representing
+<li class="listitem">
+<code class="computeroutput"><span class="identifier">_val</span></code> is another Phoenix placeholder representing
             the rule's synthesized attribute.
           </li>
-<li>
-<tt class="computeroutput"><span class="identifier">eps</span></tt> is a special spirit
+<li class="listitem">
+<code class="computeroutput"><span class="identifier">eps</span></code> is a special spirit
             parser that consumes no input but is always successful. We use it to
- initialize <tt class="computeroutput"><span class="identifier">_val</span></tt>, the
+ initialize <code class="computeroutput"><span class="identifier">_val</span></code>, the
             rule's synthesized attribute, to zero before anything else. The actual
- parser starts at <tt class="computeroutput"><span class="special">+</span><span class="identifier">char_</span><span class="special">(</span><span class="char">'M'</span><span class="special">)</span></tt>,
- parsing roman thousands. Using <tt class="computeroutput"><span class="identifier">eps</span></tt>
+ parser starts at <code class="computeroutput"><span class="special">+</span><span class="identifier">char_</span><span class="special">(</span><span class="char">'M'</span><span class="special">)</span></code>,
+ parsing roman thousands. Using <code class="computeroutput"><span class="identifier">eps</span></code>
             this way is good for doing pre and post initializations.
           </li>
-<li>
- The expression <tt class="computeroutput"><span class="identifier">a</span> <span class="special">||</span>
- <span class="identifier">b</span></tt> reads: match a or b and in
- sequence. That is, if both <tt class="computeroutput"><span class="identifier">a</span></tt>
- and <tt class="computeroutput"><span class="identifier">b</span></tt> match, it must
- be in sequence; this is equivalent to <tt class="computeroutput"><span class="identifier">a</span>
- <span class="special">&gt;&gt;</span> <span class="special">-</span><span class="identifier">b</span> <span class="special">|</span> <span class="identifier">b</span></tt>, but more efficient.
+<li class="listitem">
+ The expression <code class="computeroutput"><span class="identifier">a</span> <span class="special">||</span>
+ <span class="identifier">b</span></code> reads: match a or b and in
+ sequence. That is, if both <code class="computeroutput"><span class="identifier">a</span></code>
+ and <code class="computeroutput"><span class="identifier">b</span></code> match, it must
+ be in sequence; this is equivalent to <code class="computeroutput"><span class="identifier">a</span>
+ <span class="special">&gt;&gt;</span> <span class="special">-</span><span class="identifier">b</span> <span class="special">|</span> <span class="identifier">b</span></code>, but more efficient.
           </li>
 </ul></div>
-<a name="spirit.qi.tutorials.roman_numerals.let_s_parse_"></a><h5>
-<a name="id426379"></a>
- Let's Parse!
- </h5>
+<a name="spirit.qi.tutorials.roman_numerals.let_s_parse_"></a><h6>
+<a name="id1038235"></a>
+ <a class="link" href="roman_numerals.html#spirit.qi.tutorials.roman_numerals.let_s_parse_">Let's Parse!</a>
+ </h6>
 <p>
           </p>
 <p>
@@ -394,12 +389,12 @@
 <p>
         </p>
 <p>
- <tt class="computeroutput"><span class="identifier">roman_parser</span></tt> is an object
- of type <tt class="computeroutput"><span class="identifier">roman</span></tt> -our roman
+ <code class="computeroutput"><span class="identifier">roman_parser</span></code> is an object
+ of type <code class="computeroutput"><span class="identifier">roman</span></code> -our roman
           numeral parser. This time around, we are using the no-skipping version
           of the parse functions. We do not want to skip any spaces! We are also
- passing in an attribute, <tt class="computeroutput"><span class="keyword">unsigned</span>
- <span class="identifier">result</span></tt>, which will receive the
+ passing in an attribute, <code class="computeroutput"><span class="keyword">unsigned</span>
+ <span class="identifier">result</span></code>, which will receive the
           parsed value.
         </p>
 <p>

Modified: trunk/libs/spirit/doc/html/spirit/qi/tutorials/semantic_actions.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/qi/tutorials/semantic_actions.html (original)
+++ trunk/libs/spirit/doc/html/spirit/qi/tutorials/semantic_actions.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -3,12 +3,11 @@
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <title>Semantic Actions</title>
 <link rel="stylesheet" href="../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../index.html" title="Spirit 2.1">
 <link rel="up" href="../tutorials.html" title="Tutorials">
-<link rel="previous" href="warming_up.html" title="Warming up">
-<link rel="next" href="complex___our_first_complex_parser.html" title="Complex
- - Our first complex parser">
+<link rel="prev" href="warming_up.html" title="Warming up">
+<link rel="next" href="complex___our_first_complex_parser.html" title="Complex - Our first complex parser">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
 <table cellpadding="2" width="100%"><tr>
@@ -23,13 +22,10 @@
 <div class="spirit-nav">
 <a accesskey="p" href="warming_up.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../tutorials.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="complex___our_first_complex_parser.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h4 class="title">
-<a name="spirit.qi.tutorials.semantic_actions"></a>Semantic Actions
-</h4></div></div>
-<div></div>
-</div>
+<div class="section" title="Semantic Actions">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="spirit.qi.tutorials.semantic_actions"></a><a class="link" href="semantic_actions.html" title="Semantic Actions">Semantic Actions</a>
+</h4></div></div></div>
 <p>
           Our parser above is really nothing but a recognizer. It answers the question
           "did the input match our grammar?", but it does not do anything
@@ -41,22 +37,22 @@
           Enter Semantic actions. Semantic actions may be attached to any point in
           the grammar specification. These actions are C++ functions or function
           objects that are called whenever a part of the parser successfully recognizes
- a portion of the input. Say you have a parser <tt class="computeroutput"><span class="identifier">P</span></tt>,
- and a C++ function <tt class="computeroutput"><span class="identifier">F</span></tt>, you
- can make the parser call <tt class="computeroutput"><span class="identifier">F</span></tt>
- whenever it matches an input by attaching <tt class="computeroutput"><span class="identifier">F</span></tt>:
+ a portion of the input. Say you have a parser <code class="computeroutput"><span class="identifier">P</span></code>,
+ and a C++ function <code class="computeroutput"><span class="identifier">F</span></code>, you
+ can make the parser call <code class="computeroutput"><span class="identifier">F</span></code>
+ whenever it matches an input by attaching <code class="computeroutput"><span class="identifier">F</span></code>:
         </p>
 <pre class="programlisting"><span class="identifier">P</span><span class="special">[</span><span class="identifier">F</span><span class="special">]</span>
 </pre>
 <p>
- The expression above links <tt class="computeroutput"><span class="identifier">F</span></tt>
- to the parser, <tt class="computeroutput"><span class="identifier">P</span></tt>.
+ The expression above links <code class="computeroutput"><span class="identifier">F</span></code>
+ to the parser, <code class="computeroutput"><span class="identifier">P</span></code>.
         </p>
 <p>
           The function/function object signature depends on the type of the parser
- to which it is attached. The parser <tt class="computeroutput"><span class="identifier">double_</span></tt>
- passes the parsed number. Thus, if we were to attach a function <tt class="computeroutput"><span class="identifier">F</span></tt> to <tt class="computeroutput"><span class="identifier">double_</span></tt>,
- we need <tt class="computeroutput"><span class="identifier">F</span></tt> to be declared
+ to which it is attached. The parser <code class="computeroutput"><span class="identifier">double_</span></code>
+ passes the parsed number. Thus, if we were to attach a function <code class="computeroutput"><span class="identifier">F</span></code> to <code class="computeroutput"><span class="identifier">double_</span></code>,
+ we need <code class="computeroutput"><span class="identifier">F</span></code> to be declared
           as:
         </p>
 <pre class="programlisting"><span class="keyword">void</span> <span class="identifier">F</span><span class="special">(</span><span class="keyword">double</span> <span class="identifier">n</span><span class="special">);</span>
@@ -71,22 +67,22 @@
 <p>
           Presented are various ways to attach semantic actions:
         </p>
-<div class="itemizedlist"><ul type="disc">
-<li>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem">
             Using plain function pointer
           </li>
-<li>
+<li class="listitem">
             Using simple function object
           </li>
-<li>
+<li class="listitem">
             Using Boost.Bind
             with a plain function
           </li>
-<li>
+<li class="listitem">
             Using Boost.Bind
             with a member function
           </li>
-<li>
+<li class="listitem">
             Using Boost.Lambda
 </li>
 </ul></div>
@@ -132,11 +128,11 @@
 <p>
         </p>
 <p>
- Take note that with function objects, we need to have an <tt class="computeroutput"><span class="keyword">operator</span><span class="special">()</span></tt>
+ Take note that with function objects, we need to have an <code class="computeroutput"><span class="keyword">operator</span><span class="special">()</span></code>
           with 3 arguments. Since we don't care about the other two, we can use
- <tt class="computeroutput"><span class="identifier">unused_type</span></tt> for these.
- We'll see more of <tt class="computeroutput"><span class="identifier">unused_type</span></tt>
- elsewhere. Get used to it. <tt class="computeroutput"><span class="identifier">unused_type</span></tt>
+ <code class="computeroutput"><span class="identifier">unused_type</span></code> for these.
+ We'll see more of <code class="computeroutput"><span class="identifier">unused_type</span></code>
+ elsewhere. Get used to it. <code class="computeroutput"><span class="identifier">unused_type</span></code>
           is a Spirit supplied support class.
         </p>
 <p>
@@ -162,8 +158,8 @@
 <p>
         </p>
 <p>
- What's new? Well <tt class="computeroutput"><span class="identifier">int_</span></tt> is
- the sibbling of <tt class="computeroutput"><span class="identifier">double_</span></tt>.
+ What's new? Well <code class="computeroutput"><span class="identifier">int_</span></code> is
+ the sibbling of <code class="computeroutput"><span class="identifier">double_</span></code>.
           I'm sure you can guess what this parser does.
         </p>
 <p>
@@ -236,10 +232,10 @@
 <p>
           The examples above can be found here: ../../example/qi/actions.cpp
         </p>
-<a name="spirit.qi.tutorials.semantic_actions.phoenix"></a><h5>
-<a name="id418403"></a>
- Phoenix
- </h5>
+<a name="spirit.qi.tutorials.semantic_actions.phoenix"></a><h6>
+<a name="id1029965"></a>
+ <a class="link" href="semantic_actions.html#spirit.qi.tutorials.semantic_actions.phoenix">Phoenix</a>
+ </h6>
 <p>
           <a href="../../../../../phoenix/doc/html/index.html" target="_top">Phoenix</a>, a companion
           library bundled with Spirit, is specifically suited for binding semantic

Modified: trunk/libs/spirit/doc/html/spirit/qi/tutorials/sum___adding_numbers.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/qi/tutorials/sum___adding_numbers.html (original)
+++ trunk/libs/spirit/doc/html/spirit/qi/tutorials/sum___adding_numbers.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -1,16 +1,13 @@
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title>Sum - adding
- numbers</title>
+<title>Sum - adding numbers</title>
 <link rel="stylesheet" href="../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../index.html" title="Spirit 2.1">
 <link rel="up" href="../tutorials.html" title="Tutorials">
-<link rel="previous" href="complex___our_first_complex_parser.html" title="Complex
- - Our first complex parser">
-<link rel="next" href="number_list___stuffing_numbers_into_a_std__vector.html" title="Number
- List - stuffing numbers into a std::vector">
+<link rel="prev" href="complex___our_first_complex_parser.html" title="Complex - Our first complex parser">
+<link rel="next" href="number_list___stuffing_numbers_into_a_std__vector.html" title="Number List - stuffing numbers into a std::vector">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
 <table cellpadding="2" width="100%"><tr>
@@ -25,15 +22,11 @@
 <div class="spirit-nav">
 <a accesskey="p" href="complex___our_first_complex_parser.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../tutorials.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="number_list___stuffing_numbers_into_a_std__vector.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h4 class="title">
-<a name="spirit.qi.tutorials.sum___adding_numbers"></a><a href="sum___adding_numbers.html" title="Sum - adding
- numbers">Sum - adding
+<div class="section" title="Sum - adding numbers">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="spirit.qi.tutorials.sum___adding_numbers"></a><a class="link" href="sum___adding_numbers.html" title="Sum - adding numbers">Sum - adding
         numbers</a>
-</h4></div></div>
-<div></div>
-</div>
+</h4></div></div></div>
 <p>
           Here's a parser that sums a comma-separated list of numbers.
         </p>
@@ -83,64 +76,88 @@
 <col>
 </colgroup>
 <thead><tr>
-<th><p>
+<th>
+ <p>
                   Namespace
- </p></th>
-<th><p>
+ </p>
+ </th>
+<th>
+ <p>
                   Description
- </p></th>
+ </p>
+ </th>
 </tr></thead>
 <tbody>
 <tr>
-<td><p>
+<td>
+ <p>
                   boost::phoenix
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
                   All of phoenix
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
+<td>
+ <p>
                   boost::spirit
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
                   All of spirit
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
+<td>
+ <p>
                   boost::spirit::qi
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
                   All of spirit.qi
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
+<td>
+ <p>
                   boost::spirit::ascii
- </p></td>
-<td><p>
- ASCII version of <tt class="computeroutput"><span class="identifier">char_</span></tt>
+ </p>
+ </td>
+<td>
+ <p>
+ ASCII version of <code class="computeroutput"><span class="identifier">char_</span></code>
                   and all char related parsers. Other encodings are also provided
                   (e.g. also an ISO8859.1)
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
+<td>
+ <p>
                   boost::spirit::arg_names
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
                   Special phoenix placeholders for spirit
- </p></td>
+ </p>
+ </td>
 </tr>
 </tbody>
 </table></div>
-<div class="note"><table border="0" summary="Note">
+<div class="note" title="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>
 </tr>
-<tr><td colspan="2" align="left" valign="top"><p>
+<tr><td align="left" valign="top"><p>
             If you feel uneasy with using whole namespaces, feel free to qualify
             your code, use namespace aliases, etc. For the purpose of this tutorial,
             we will be presenting unqualified names for both Spirit and Phoenix.
@@ -192,25 +209,25 @@
           the sum of all the parsed numbers.
         </p>
 <p>
- The first <tt class="computeroutput"><span class="identifier">double_</span></tt> parser
+ The first <code class="computeroutput"><span class="identifier">double_</span></code> parser
           attaches this action:
         </p>
 <pre class="programlisting"><span class="identifier">ref</span><span class="special">(</span><span class="identifier">n</span><span class="special">)</span> <span class="special">=</span> <span class="identifier">_1</span>
 </pre>
 <p>
- This assigns the parsed result (actually, the attribute of <tt class="computeroutput"><span class="identifier">double_</span></tt>) to <tt class="computeroutput"><span class="identifier">n</span></tt>.
- <tt class="computeroutput"><span class="identifier">ref</span><span class="special">(</span><span class="identifier">n</span><span class="special">)</span></tt> tells
- Phoenix that <tt class="computeroutput"><span class="identifier">n</span></tt> is a mutable reference. <tt class="computeroutput"><span class="identifier">_1</span></tt> is a Phoenix
+ This assigns the parsed result (actually, the attribute of <code class="computeroutput"><span class="identifier">double_</span></code>) to <code class="computeroutput"><span class="identifier">n</span></code>.
+ <code class="computeroutput"><span class="identifier">ref</span><span class="special">(</span><span class="identifier">n</span><span class="special">)</span></code> tells
+ Phoenix that <code class="computeroutput"><span class="identifier">n</span></code> is a mutable reference. <code class="computeroutput"><span class="identifier">_1</span></code> is a Phoenix
           placeholder for the parsed result attribute.
         </p>
 <p>
- The second <tt class="computeroutput"><span class="identifier">double_</span></tt> parser
+ The second <code class="computeroutput"><span class="identifier">double_</span></code> parser
           attaches this action:
         </p>
 <pre class="programlisting"><span class="identifier">ref</span><span class="special">(</span><span class="identifier">n</span><span class="special">)</span> <span class="special">+=</span> <span class="identifier">_1</span>
 </pre>
 <p>
- So, subsequent numbers add into <tt class="computeroutput"><span class="identifier">n</span></tt>.
+ So, subsequent numbers add into <code class="computeroutput"><span class="identifier">n</span></code>.
         </p>
 <p>
           That wasn't too bad, was it :-) ?

Modified: trunk/libs/spirit/doc/html/spirit/qi/tutorials/warming_up.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/qi/tutorials/warming_up.html (original)
+++ trunk/libs/spirit/doc/html/spirit/qi/tutorials/warming_up.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -3,10 +3,10 @@
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <title>Warming up</title>
 <link rel="stylesheet" href="../../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../../index.html" title="Spirit 2.1">
 <link rel="up" href="../tutorials.html" title="Tutorials">
-<link rel="previous" href="quick_start.html" title="Quick Start">
+<link rel="prev" href="quick_start.html" title="Quick Start">
 <link rel="next" href="semantic_actions.html" title="Semantic Actions">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -22,22 +22,19 @@
 <div class="spirit-nav">
 <a accesskey="p" href="quick_start.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../tutorials.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="semantic_actions.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h4 class="title">
-<a name="spirit.qi.tutorials.warming_up"></a>Warming up
-</h4></div></div>
-<div></div>
-</div>
+<div class="section" title="Warming up">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="spirit.qi.tutorials.warming_up"></a><a class="link" href="warming_up.html" title="Warming up">Warming up</a>
+</h4></div></div></div>
 <p>
           We'll start by showing examples of parser expressions to give you a feel
           on how to build parsers from the simplest parser, building up as we go.
         </p>
-<a name="spirit.qi.tutorials.warming_up.trivial_example__1_parsing_a_number"></a><h5>
-<a name="id415540"></a>
- <a href="warming_up.html#spirit.qi.tutorials.warming_up.trivial_example__1_parsing_a_number">Trivial
+<a name="spirit.qi.tutorials.warming_up.trivial_example__1_parsing_a_number"></a><h6>
+<a name="id1027808"></a>
+ <a class="link" href="warming_up.html#spirit.qi.tutorials.warming_up.trivial_example__1_parsing_a_number">Trivial
           Example #1 Parsing a number</a>
- </h5>
+ </h6>
 <p>
           Create a parser that will parse a floating-point number.
         </p>
@@ -48,11 +45,11 @@
           a Spirit floating point parser (a built-in parser). Spirit has many pre-defined
           parsers and consistent naming conventions help you keep from going insane!
         </p>
-<a name="spirit.qi.tutorials.warming_up.trivial_example__2_parsing_two_numbers"></a><h5>
-<a name="id415585"></a>
- <a href="warming_up.html#spirit.qi.tutorials.warming_up.trivial_example__2_parsing_two_numbers">Trivial
+<a name="spirit.qi.tutorials.warming_up.trivial_example__2_parsing_two_numbers"></a><h6>
+<a name="id1027837"></a>
+ <a class="link" href="warming_up.html#spirit.qi.tutorials.warming_up.trivial_example__2_parsing_two_numbers">Trivial
           Example #2 Parsing two numbers</a>
- </h5>
+ </h6>
 <p>
           Create a parser that will accept a line consisting of two floating-point
           numbers.
@@ -60,8 +57,8 @@
 <pre class="programlisting"><span class="identifier">double_</span> <span class="special">&gt;&gt;</span> <span class="identifier">double_</span>
 </pre>
 <p>
- Here you see the familiar floating-point numeric parser <tt class="computeroutput"><span class="identifier">double_</span></tt>
- used twice, once for each number. What's that <tt class="computeroutput"><span class="special">&gt;&gt;</span></tt>
+ Here you see the familiar floating-point numeric parser <code class="computeroutput"><span class="identifier">double_</span></code>
+ used twice, once for each number. What's that <code class="computeroutput"><span class="special">&gt;&gt;</span></code>
           operator doing in there? Well, they had to be separated by something, and
           this was chosen as the "followed by" sequence operator. The above
           program creates a parser from two simpler parsers, glueing them together
@@ -69,23 +66,23 @@
           of smaller parsers. Whitespace between numbers can implicitly be consumed
           depending on how the parser is invoked (see below).
         </p>
-<div class="note"><table border="0" summary="Note">
+<div class="note" title="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>
 </tr>
-<tr><td colspan="2" align="left" valign="top"><p>
+<tr><td align="left" valign="top"><p>
             When we combine parsers, we end up with a "bigger" parser,
             but it's still a parser. Parsers can get bigger and bigger, nesting more
             and more, but whenever you glue two parsers together, you end up with
             one bigger parser. This is an important concept.
           </p></td></tr>
 </table></div>
-<a name="spirit.qi.tutorials.warming_up.trivial_example__3_parsing_one_or_more_numbers"></a><h5>
-<a name="id415673"></a>
- <a href="warming_up.html#spirit.qi.tutorials.warming_up.trivial_example__3_parsing_one_or_more_numbers">Trivial
+<a name="spirit.qi.tutorials.warming_up.trivial_example__3_parsing_one_or_more_numbers"></a><h6>
+<a name="id1027898"></a>
+ <a class="link" href="warming_up.html#spirit.qi.tutorials.warming_up.trivial_example__3_parsing_one_or_more_numbers">Trivial
           Example #3 Parsing one or more numbers</a>
- </h5>
+ </h6>
 <p>
           Create a parser that will accept zero or more floating-point numbers.
         </p>
@@ -93,7 +90,7 @@
 </pre>
 <p>
           This is like a regular-expression Kleene Star, though the syntax might
- look a bit odd for a C++ programmer not used to seeing the <tt class="computeroutput"><span class="special">*</span></tt> operator overloaded like this. Actually,
+ look a bit odd for a C++ programmer not used to seeing the <code class="computeroutput"><span class="special">*</span></code> operator overloaded like this. Actually,
           if you know regular expressions it may look odd too since the star is before
           the expression it modifies. C'est la vie. Blame it on the fact that we
           must work with the syntax rules of C++.
@@ -105,11 +102,11 @@
           Kleene Star is also known as a Kleene Closure, but we call it the Star
           in most places.
         </p>
-<a name="spirit.qi.tutorials.warming_up.trivial_example__4_parsing_a_comma_delimited_list_of_numbers"></a><h5>
-<a name="id415750"></a>
- <a href="warming_up.html#spirit.qi.tutorials.warming_up.trivial_example__4_parsing_a_comma_delimited_list_of_numbers">Trivial
+<a name="spirit.qi.tutorials.warming_up.trivial_example__4_parsing_a_comma_delimited_list_of_numbers"></a><h6>
+<a name="id1027943"></a>
+ <a class="link" href="warming_up.html#spirit.qi.tutorials.warming_up.trivial_example__4_parsing_a_comma_delimited_list_of_numbers">Trivial
           Example #4 Parsing a comma-delimited list of numbers</a>
- </h5>
+ </h6>
 <p>
           This example will create a parser that accepts a comma-delimited list of
           numbers.
@@ -117,8 +114,8 @@
 <pre class="programlisting"><span class="identifier">double_</span> <span class="special">&gt;&gt;</span> <span class="special">*(</span><span class="identifier">char_</span><span class="special">(</span><span class="char">','</span><span class="special">)</span> <span class="special">&gt;&gt;</span> <span class="identifier">double_</span><span class="special">)</span>
 </pre>
 <p>
- Notice <tt class="computeroutput"><span class="identifier">char_</span><span class="special">(</span><span class="char">','</span><span class="special">)</span></tt>. It is
- a literal character parser that can recognize the comma <tt class="computeroutput"><span class="char">','</span></tt>.
+ Notice <code class="computeroutput"><span class="identifier">char_</span><span class="special">(</span><span class="char">','</span><span class="special">)</span></code>. It is
+ a literal character parser that can recognize the comma <code class="computeroutput"><span class="char">','</span></code>.
           In this case, the Kleene Star is modifying a more complex parser, namely,
           the one generated by the expression:
         </p>
@@ -128,38 +125,38 @@
           Note that this is a case where the parentheses are necessary. The Kleene
           star encloses the complete expression above.
         </p>
-<a name="spirit.qi.tutorials.warming_up.let_s_parse_"></a><h5>
-<a name="id415926"></a>
- Let's Parse!
- </h5>
+<a name="spirit.qi.tutorials.warming_up.let_s_parse_"></a><h6>
+<a name="id1028086"></a>
+ <a class="link" href="warming_up.html#spirit.qi.tutorials.warming_up.let_s_parse_">Let's Parse!</a>
+ </h6>
 <p>
           We're done with defining the parser. So the next step is now invoking this
           parser to do its work. There are a couple of ways to do this. For now,
- we will use the <tt class="computeroutput"><span class="identifier">phrase_parse</span></tt>
+ we will use the <code class="computeroutput"><span class="identifier">phrase_parse</span></code>
           function. One overload of this function accepts four arguments:
         </p>
-<div class="orderedlist"><ol type="1">
-<li>
+<div class="orderedlist"><ol class="orderedlist" type="1">
+<li class="listitem">
             An iterator pointing to the start of the input
           </li>
-<li>
+<li class="listitem">
             An iterator pointing to one past the end of the input
           </li>
-<li>
+<li class="listitem">
             The parser object
           </li>
-<li>
+<li class="listitem">
             Another parser called the skip parser
           </li>
 </ol></div>
 <p>
           In our example, we wish to skip spaces and tabs. Another parser named
- <tt class="computeroutput"><span class="identifier">space</span></tt> is included in Spirit's
+ <code class="computeroutput"><span class="identifier">space</span></code> is included in Spirit's
           repertoire of predefined parsers. It is a very simple parser that simply
- recognizes whitespace. We will use <tt class="computeroutput"><span class="identifier">space</span></tt>
+ recognizes whitespace. We will use <code class="computeroutput"><span class="identifier">space</span></code>
           as our skip parser. The skip parser is the one responsible for skipping
- characters in between parser elements such as the <tt class="computeroutput"><span class="identifier">double_</span></tt>
- and <tt class="computeroutput"><span class="identifier">char_</span></tt>.
+ characters in between parser elements such as the <code class="computeroutput"><span class="identifier">double_</span></code>
+ and <code class="computeroutput"><span class="identifier">char_</span></code>.
         </p>
 <p>
           Ok, so now let's parse!
@@ -177,10 +174,10 @@
     <span class="keyword">using</span> <span class="identifier">ascii</span><span class="special">::</span><span class="identifier">space</span><span class="special">;</span>
 
     <span class="keyword">bool</span> <span class="identifier">r</span> <span class="special">=</span> <span class="identifier">phrase_parse</span><span class="special">(</span>
- <span class="identifier">first</span><span class="special">,</span> <span class="callout_bug"><a name="spirit0co" href="warming_up.html#spirit0"><img src="../../../../../../../doc/src/images/callouts/1.png" alt="1" border="0"></a></span>
- <span class="identifier">last</span><span class="special">,</span> <span class="callout_bug"><a name="spirit1co" href="warming_up.html#spirit1"><img src="../../../../../../../doc/src/images/callouts/2.png" alt="2" border="0"></a></span>
- <span class="identifier">double_</span> <span class="special">&gt;&gt;</span> <span class="special">*(</span><span class="char">','</span> <span class="special">&gt;&gt;</span> <span class="identifier">double_</span><span class="special">),</span> <span class="callout_bug"><a name="spirit2co" href="warming_up.html#spirit2"><img src="../../../../../../../doc/src/images/callouts/3.png" alt="3" border="0"></a></span>
- <span class="identifier">space</span> <span class="callout_bug"><a name="spirit3co" href="warming_up.html#spirit3"><img src="../../../../../../../doc/src/images/callouts/4.png" alt="4" border="0"></a></span>
+ <span class="identifier">first</span><span class="special">,</span> <span class="callout_bug"><a class="co" name="spirit0co" href="warming_up.html#spirit0"><img src="../../../../../../../doc/src/images/callouts/1.png" alt="1" border="0"></a></span>
+ <span class="identifier">last</span><span class="special">,</span> <span class="callout_bug"><a class="co" name="spirit1co" href="warming_up.html#spirit1"><img src="../../../../../../../doc/src/images/callouts/2.png" alt="2" border="0"></a></span>
+ <span class="identifier">double_</span> <span class="special">&gt;&gt;</span> <span class="special">*(</span><span class="char">','</span> <span class="special">&gt;&gt;</span> <span class="identifier">double_</span><span class="special">),</span> <span class="callout_bug"><a class="co" name="spirit2co" href="warming_up.html#spirit2"><img src="../../../../../../../doc/src/images/callouts/3.png" alt="3" border="0"></a></span>
+ <span class="identifier">space</span> <span class="callout_bug"><a class="co" name="spirit3co" href="warming_up.html#spirit3"><img src="../../../../../../../doc/src/images/callouts/4.png" alt="4" border="0"></a></span>
     <span class="special">);</span>
     <span class="keyword">if</span> <span class="special">(</span><span class="identifier">first</span> <span class="special">!=</span> <span class="identifier">last</span><span class="special">)</span> <span class="comment">// fail if we did not get a full match
 </span> <span class="keyword">return</span> <span class="keyword">false</span><span class="special">;</span>
@@ -195,23 +192,19 @@
             </p>
 <div class="calloutlist"><table border="0" summary="Callout list">
 <tr>
-<td width="5%" valign="top" align="left">
-<a name="spirit0"></a>1 </td>
+<td width="5%" valign="top" align="left"><p><a name="spirit0"></a>1 </p></td>
 <td valign="top" align="left"><p> start iterator </p></td>
 </tr>
 <tr>
-<td width="5%" valign="top" align="left">
-<a name="spirit1"></a>2 </td>
+<td width="5%" valign="top" align="left"><p><a name="spirit1"></a>2 </p></td>
 <td valign="top" align="left"><p> end iterator </p></td>
 </tr>
 <tr>
-<td width="5%" valign="top" align="left">
-<a name="spirit2"></a>3 </td>
+<td width="5%" valign="top" align="left"><p><a name="spirit2"></a>3 </p></td>
 <td valign="top" align="left"><p> the parser </p></td>
 </tr>
 <tr>
-<td width="5%" valign="top" align="left">
-<a name="spirit3"></a>4 </td>
+<td width="5%" valign="top" align="left"><p><a name="spirit3"></a>4 </p></td>
 <td valign="top" align="left"><p> the skip-parser </p></td>
 </tr>
 </table></div>
@@ -220,8 +213,8 @@
 <p>
         </p>
 <p>
- The parse function returns <tt class="computeroutput"><span class="keyword">true</span></tt>
- or <tt class="computeroutput"><span class="keyword">false</span></tt> depending on the
+ The parse function returns <code class="computeroutput"><span class="keyword">true</span></code>
+ or <code class="computeroutput"><span class="keyword">false</span></code> depending on the
           result of the parse. The first iterator is passed by reference. On a successful
           parse, this iterator is repositioned to the rightmost position consumed
           by the parser. If this becomes equal to str.end(), then we have a full
@@ -241,39 +234,39 @@
 <p>
           You can find the full cpp file here: ../../example/qi/num_list1.cpp
         </p>
-<div class="note"><table border="0" summary="Note">
+<div class="note" title="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>
 </tr>
-<tr><td colspan="2" align="left" valign="top">
+<tr><td align="left" valign="top">
 <p>
- <tt class="computeroutput"><span class="keyword">char</span></tt> and <tt class="computeroutput"><span class="keyword">wchar_t</span></tt>
+ <code class="computeroutput"><span class="keyword">char</span></code> and <code class="computeroutput"><span class="keyword">wchar_t</span></code>
             operands
           </p>
 <p>
- The careful reader may notice that the parser expression has <tt class="computeroutput"><span class="char">','</span></tt> instead of <tt class="computeroutput"><span class="identifier">char_</span><span class="special">(</span><span class="char">','</span><span class="special">)</span></tt>
+ The careful reader may notice that the parser expression has <code class="computeroutput"><span class="char">','</span></code> instead of <code class="computeroutput"><span class="identifier">char_</span><span class="special">(</span><span class="char">','</span><span class="special">)</span></code>
             as the previous examples did. This is ok due to C++ syntax rules of conversion.
- There are <tt class="computeroutput"><span class="special">&gt;&gt;</span></tt> operators
- that are overloaded to accept a <tt class="computeroutput"><span class="keyword">char</span></tt>
- or <tt class="computeroutput"><span class="keyword">wchar_t</span></tt> argument on its
+ There are <code class="computeroutput"><span class="special">&gt;&gt;</span></code> operators
+ that are overloaded to accept a <code class="computeroutput"><span class="keyword">char</span></code>
+ or <code class="computeroutput"><span class="keyword">wchar_t</span></code> argument on its
             left or right (but not both). An operator may be overloaded if at least
- one of its parameters is a user-defined type. In this case, the <tt class="computeroutput"><span class="identifier">double_</span></tt> is the 2nd argument to <tt class="computeroutput"><span class="keyword">operator</span><span class="special">&gt;&gt;</span></tt>,
- and so the proper overload of <tt class="computeroutput"><span class="special">&gt;&gt;</span></tt>
- is used, converting <tt class="computeroutput"><span class="char">','</span></tt> into
+ one of its parameters is a user-defined type. In this case, the <code class="computeroutput"><span class="identifier">double_</span></code> is the 2nd argument to <code class="computeroutput"><span class="keyword">operator</span><span class="special">&gt;&gt;</span></code>,
+ and so the proper overload of <code class="computeroutput"><span class="special">&gt;&gt;</span></code>
+ is used, converting <code class="computeroutput"><span class="char">','</span></code> into
             a character literal parser.
           </p>
 <p>
- The problem with omiting the <tt class="computeroutput"><span class="identifier">char_</span></tt>
- should be obvious: <tt class="computeroutput"><span class="char">'a'</span> <span class="special">&gt;&gt;</span>
- <span class="char">'b'</span></tt> is not a spirit parser, it is
+ The problem with omiting the <code class="computeroutput"><span class="identifier">char_</span></code>
+ should be obvious: <code class="computeroutput"><span class="char">'a'</span> <span class="special">&gt;&gt;</span>
+ <span class="char">'b'</span></code> is not a spirit parser, it is
             a numeric expression, right-shifting the ASCII (or another encoding)
- value of <tt class="computeroutput"><span class="char">'a'</span></tt> by the ASCII value
- of <tt class="computeroutput"><span class="char">'b'</span></tt>. However, both <tt class="computeroutput"><span class="identifier">char_</span><span class="special">(</span><span class="char">'a'</span><span class="special">)</span> <span class="special">&gt;&gt;</span>
- <span class="char">'b'</span></tt> and <tt class="computeroutput"><span class="char">'a'</span>
- <span class="special">&gt;&gt;</span> <span class="identifier">char_</span><span class="special">(</span><span class="char">'b'</span><span class="special">)</span></tt>
- are Spirit sequence parsers for the letter <tt class="computeroutput"><span class="char">'a'</span></tt>
- followed by <tt class="computeroutput"><span class="char">'b'</span></tt>. You'll get
+ value of <code class="computeroutput"><span class="char">'a'</span></code> by the ASCII value
+ of <code class="computeroutput"><span class="char">'b'</span></code>. However, both <code class="computeroutput"><span class="identifier">char_</span><span class="special">(</span><span class="char">'a'</span><span class="special">)</span> <span class="special">&gt;&gt;</span>
+ <span class="char">'b'</span></code> and <code class="computeroutput"><span class="char">'a'</span>
+ <span class="special">&gt;&gt;</span> <span class="identifier">char_</span><span class="special">(</span><span class="char">'b'</span><span class="special">)</span></code>
+ are Spirit sequence parsers for the letter <code class="computeroutput"><span class="char">'a'</span></code>
+ followed by <code class="computeroutput"><span class="char">'b'</span></code>. You'll get
             used to it, sooner or later.
           </p>
 </td></tr>

Modified: trunk/libs/spirit/doc/html/spirit/references.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/references.html (original)
+++ trunk/libs/spirit/doc/html/spirit/references.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -3,10 +3,10 @@
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <title>References</title>
 <link rel="stylesheet" href="../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../index.html" title="Spirit 2.1">
 <link rel="up" href="../index.html" title="Spirit 2.1">
-<link rel="previous" href="acknowledgments.html" title="Acknowledgments">
+<link rel="prev" href="acknowledgments.html" title="Acknowledgments">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
 <table cellpadding="2" width="100%"><tr>
@@ -21,13 +21,10 @@
 <div class="spirit-nav">
 <a accesskey="p" href="acknowledgments.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>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h2 class="title" style="clear: both">
-<a name="spirit.references"></a>References
-</h2></div></div>
-<div></div>
-</div>
+<div class="section" title="References">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="spirit.references"></a><a class="link" href="references.html" title="References">References</a>
+</h2></div></div></div>
 <div class="informaltable"><table class="table">
 <colgroup>
 <col>
@@ -35,300 +32,444 @@
 <col>
 </colgroup>
 <thead><tr>
-<th><p>
- </p></th>
-<th><p>
+<th>
+ <p>
+ </p>
+ </th>
+<th>
+ <p>
               Authors
- </p></th>
-<th><p>
+ </p>
+ </th>
+<th>
+ <p>
               Title, Publisher/link, Date Published
- </p></th>
+ </p>
+ </th>
 </tr></thead>
 <tbody>
 <tr>
-<td><p>
+<td>
+ <p>
               1.
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
               Todd Veldhuizen
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
               <a href="http://www.extreme.indiana.edu/%7Etveldhui/papers/Expression-Templates/exprtmpl.html" target="_top">"Expression
               Templates"</a>. C++ Report, June 1995.
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
+<td>
+ <p>
               2.
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
               Peter Naur (ed.)
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
               <a href="http://www.masswerk.at/algol60/report.htm" target="_top">"Report
               on the Algorithmic Language ALGOL 60"</a>. CACM, May 1960.
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
+<td>
+ <p>
               3.
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
               ISO/IEC
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
               <a href="http://www.cl.cam.ac.uk/%7Emgk25/iso-14977.pdf" target="_top">"ISO-EBNF"</a>,
               ISO/IEC 14977: 1996(E).
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
+<td>
+ <p>
               4.
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
               Richard J.Botting, Ph.D.
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
               <a href="http://www.csci.csusb.edu/dick/maths/intro_ebnf.html" target="_top">"XBNF"</a>
               (citing Leu-Weiner, 1973). California State University, San Bernardino,
               1998.
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
+<td>
+ <p>
               5.
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
               James Coplien.
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
               "Curiously Recurring Template Pattern". C++ Report, Feb.
               1995.
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
+<td>
+ <p>
               6.
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
               Thierry Geraud and Alexandre Duret-Lutz
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
               <a href="http://www.coldewey.com/europlop2000/papers/geraud%2Bduret.zip" target="_top">Generic
               Programming Redesign of Patterns</a> Proceedings of the 5th European
               Conference on Pattern Languages of Programs(EuroPLoP'2000) Irsee, Germany,
               July 2000.
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
+<td>
+ <p>
               7.
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
               Geoffrey Furnish
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
               <a href="http://www.adtmag.com/joop/carticle.aspx?ID=627" target="_top">"Disambiguated
               Glommable Expression Templates Reintroduced"</a> C++ Report,
               May 2000
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
+<td>
+ <p>
               8.
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
               Erich Gamma, Richard Helm, Ralph Jhonson, and John Vlissides
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
               Design Patterns, Elements of Reusable Object-Oriented Software. Addison-Wesley,
               1995.
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
+<td>
+ <p>
               9.
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
               Alfred V. Aho, Revi Sethi, Feffrey D. Ulman
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
               Compilers, Principles, Techniques and Tools Addison-Wesley, June 1987.
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
+<td>
+ <p>
               10.
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
               Dick Grune and Ceriel Jacobs
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
               <a href="http://www.cs.vu.nl/%7Edick/PTAPG.html" target="_top">Parsing Techniques:
               A Practical Guide.</a> Ellis Horwood Ltd.: West Sussex, England,
               1990. (electronic copy, 1998).
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
+<td>
+ <p>
               11.
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
               T. J. Parr, H. G. Dietz, and W. E. Cohen
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
               <a href="http://citeseer.ist.psu.edu/6885.html" target="_top">PCCTS Reference
               Manual (Version 1.00)</a>. School of Electrical Engineering, Purdue
               University, West Lafayette, August 1991.
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
+<td>
+ <p>
               12.
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
               Adrian Johnstone and Elizabeth Scott.
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
               <a href="ftp://ftp.cs.rhul.ac.uk/pub/rdp" target="_top">RDP, A Recursive Descent
               Compiler Compiler</a>. Technical Report CSD TR 97 25, Dept. of
               Computer Science, Egham, Surrey, England, Dec. 20, 1997.
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
+<td>
+ <p>
               13.
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
               Adrian Johnstone
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
               <a href="http://www.cs.rhul.ac.uk/research/languages/projects/lookahead_backtrack.shtml" target="_top">Languages
               and Architectures, Parser generators with backtrack or extended lookahead
               capability</a> Department of Computer Science, Royal Holloway,
               University of London, Egham, Surrey, England
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
+<td>
+ <p>
               14.
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
               Damian Conway
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
               <a href="http://www.csse.monash.edu.au/%7Edamian/papers/#Embedded_Input_Parsing_for_C" target="_top">Parsing
               with C++ Classes</a>. ACM SIGPLAN Notices, 29:1, 1994.
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
+<td>
+ <p>
               15.
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
               Joel de Guzman
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
               <a href="http://spirit.sourceforge.net/distrib/spirit_1_8_5/libs/spirit/index.html" target="_top">"Spirit
               Version 1.8"</a>, 1998-2003.
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
+<td>
+ <p>
               16.
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
               S. Doaitse Swierstra and Luc Duponcheel
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
               <a href="http://citeseer.ist.psu.edu/448665.html" target="_top">Deterministic,
               Error-Correcting Combinator Parsers</a> Dept. of Computer Science,
               Utrecht University P.O.Box 80.089, 3508 TB Utrecht, The Netherland
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
+<td>
+ <p>
               17.
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
               Bjarne Stroustrup
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
               <a href="http://www.research.att.com/%7Ebs/whitespace98.pdf" target="_top">Generalizing
               Overloading for C++2000</a> Overload, Issue 25. April 1, 1998.
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
+<td>
+ <p>
               18.
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
               Dr. John Maddock
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
               <a href="http://www.boost.org/libs/regex/index.html" target="_top">Regex++ Documentation</a>
               http://www.boost.org/libs/regex/index.htm
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
+<td>
+ <p>
               19.
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
               Anonymous Edited by Graham Hutton
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
               <a href="http://www.cs.nott.ac.uk/~gmh//faq.html" target="_top">Frequently Asked
               Questions for comp.lang.functional</a>. Edited by Graham Hutton,
               University of Nottingham.
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
+<td>
+ <p>
               20.
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
               Hewlett-Packard
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
               <a href="http://www.sgi.com/tech/stl/" target="_top">Standard Template Library
               Programmer's Guide.</a>, Hewlett-Packard Company, 1994
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
+<td>
+ <p>
               21.
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
               Boost Libraries
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
               <a href="http://boost.org/libs/libraries.htm" target="_top">Boost Libraries Documentation</a>.
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
+<td>
+ <p>
               22.
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
               Brian McNamara and Yannis Smaragdakis
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
               <a href="http://www.cc.gatech.edu/~yannis/fc++/" target="_top">FC++:Functional
               Programming in C++</a>.
- </p></td>
+ </p>
+ </td>
 </tr>
 <tr>
-<td><p>
+<td>
+ <p>
               23.
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
               Todd Veldhuizen
- </p></td>
-<td><p>
+ </p>
+ </td>
+<td>
+ <p>
               <a href="ftp://ftp.cs.indiana.edu/pub/techreports/TR542.pdf" target="_top">Techniques
               for Scientic C++.</a>
- </p></td>
+ </p>
+ </td>
 </tr>
 </tbody>
 </table></div>

Modified: trunk/libs/spirit/doc/html/spirit/structure.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/structure.html (original)
+++ trunk/libs/spirit/doc/html/spirit/structure.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -3,10 +3,10 @@
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <title>Structure</title>
 <link rel="stylesheet" href="../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../index.html" title="Spirit 2.1">
 <link rel="up" href="../index.html" title="Spirit 2.1">
-<link rel="previous" href="introduction.html" title="Introduction">
+<link rel="prev" href="introduction.html" title="Introduction">
 <link rel="next" href="structure/include.html" title="Include">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -22,13 +22,10 @@
 <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="structure/include.html"><img src="../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h2 class="title" style="clear: both">
-<a name="spirit.structure"></a>Structure
-</h2></div></div>
-<div></div>
-</div>
+<div class="section" title="Structure">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="spirit.structure"></a><a class="link" href="structure.html" title="Structure">Structure</a>
+</h2></div></div></div>
 <div class="toc"><dl><dt><span class="section">Include</span></dt></dl></div>
 </div>
 <table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>

Modified: trunk/libs/spirit/doc/html/spirit/structure/include.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/structure/include.html (original)
+++ trunk/libs/spirit/doc/html/spirit/structure/include.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -3,10 +3,10 @@
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <title>Include</title>
 <link rel="stylesheet" href="../../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../../index.html" title="Spirit 2.1">
 <link rel="up" href="../structure.html" title="Structure">
-<link rel="previous" href="../structure.html" title="Structure">
+<link rel="prev" href="../structure.html" title="Structure">
 <link rel="next" href="../abstracts.html" title="Abstracts">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -22,13 +22,10 @@
 <div class="spirit-nav">
 <a accesskey="p" href="../structure.html"><img src="../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../structure.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="../abstracts.html"><img src="../../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h3 class="title">
-<a name="spirit.structure.include"></a>Include
-</h3></div></div>
-<div></div>
-</div>
+<div class="section" title="Include">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="spirit.structure.include"></a><a class="link" href="include.html" title="Include">Include</a>
+</h3></div></div></div>
 <p>
         Spirit is a header file only library. There are no libraries to link to.
         This section documents the structure of the Spirit headers.
@@ -37,23 +34,23 @@
         Spirit contains five sub-libraries plus a 'support' module where common support
         classes are placed:
       </p>
-<div class="itemizedlist"><ul type="disc">
-<li>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem">
           Classic
         </li>
-<li>
+<li class="listitem">
           Qi
         </li>
-<li>
+<li class="listitem">
           Karma
         </li>
-<li>
+<li class="listitem">
           Lex
         </li>
-<li>
+<li class="listitem">
           Phoenix
         </li>
-<li>
+<li class="listitem">
           Support
         </li>
 </ul></div>
@@ -109,26 +106,26 @@
         is a special flat directory that contains all the spirit headers. To accomodate
         the flat structure, the headers are prefixed with the sub-library name:
       </p>
-<div class="itemizedlist"><ul type="disc">
-<li>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem">
           classic_
         </li>
-<li>
+<li class="listitem">
           karma_
         </li>
-<li>
+<li class="listitem">
           lex_
         </li>
-<li>
+<li class="listitem">
           phoenix1_
         </li>
-<li>
+<li class="listitem">
           phoenix_
         </li>
-<li>
+<li class="listitem">
           qi_
         </li>
-<li>
+<li class="listitem">
           support_
         </li>
 </ul></div>
@@ -139,26 +136,26 @@
 <p>
         If you want to simply include the main sub-library name, then you can include:
       </p>
-<div class="itemizedlist"><ul type="disc">
-<li>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem">
           &lt;boost/spirit/include/classic.hpp&gt;
         </li>
-<li>
+<li class="listitem">
           &lt;boost/spirit/include/karma.hpp&gt;
         </li>
-<li>
+<li class="listitem">
           &lt;boost/spirit/include/lex.hpp&gt;
         </li>
-<li>
+<li class="listitem">
           &lt;boost/spirit/include/phoenix1.hpp&gt;
         </li>
-<li>
+<li class="listitem">
           &lt;boost/spirit/include/phoenix.hpp&gt;
         </li>
-<li>
+<li class="listitem">
           &lt;boost/spirit/include/qi.hpp&gt;
         </li>
-<li>
+<li class="listitem">
           &lt;boost/spirit/include/support.hpp&gt;
         </li>
 </ul></div>
@@ -177,23 +174,23 @@
 <p>
         As usual, these directories have their corresponding include files:
       </p>
-<div class="itemizedlist"><ul type="disc">
-<li>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem">
           &lt;boost/spirit/home/classic.hpp&gt;
         </li>
-<li>
+<li class="listitem">
           &lt;boost/spirit/home/karma.hpp&gt;
         </li>
-<li>
+<li class="listitem">
           &lt;boost/spirit/home/lex.hpp&gt;
         </li>
-<li>
+<li class="listitem">
           &lt;boost/spirit/home/phoenix.hpp&gt;
         </li>
-<li>
+<li class="listitem">
           &lt;boost/spirit/home/qi.hpp&gt;
         </li>
-<li>
+<li class="listitem">
           &lt;boost/spirit/home/support.hpp&gt;
         </li>
 </ul></div>

Added: trunk/libs/spirit/doc/html/spirit/support.html
==============================================================================
--- (empty file)
+++ trunk/libs/spirit/doc/html/spirit/support.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -0,0 +1,45 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>Supporting libraries</title>
+<link rel="stylesheet" href="../../../../../doc/html/boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
+<link rel="home" href="../index.html" title="Spirit 2.1">
+<link rel="up" href="../index.html" title="Spirit 2.1">
+<link rel="prev" href="lex/reference/tokenset_class.html" title="TokenSet Class">
+<link rel="next" href="support/multi_pass.html" title="The multi pass iterator">
+</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">People</td>
+<td align="center">FAQ</td>
+<td align="center">More</td>
+</tr></table>
+<hr>
+<div class="spirit-nav">
+<a accesskey="p" href="lex/reference/tokenset_class.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="support/multi_pass.html"><img src="../../../../../doc/html/images/next.png" alt="Next"></a>
+</div>
+<div class="section" title="Supporting libraries">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="spirit.support"></a><a class="link" href="support.html" title="Supporting libraries"> Supporting libraries</a>
+</h2></div></div></div>
+<div class="toc"><dl><dt><span class="section"> The multi pass iterator</span></dt></dl></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 © 2001-2009 Joel
+ de Guzman, Hartmut Kaiser<p>
+ Distributed under the Boost Software License, Version 1.0. (See accompanying
+ file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)
+ </p>
+</div></td>
+</tr></table>
+<hr>
+<div class="spirit-nav">
+<a accesskey="p" href="lex/reference/tokenset_class.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="support/multi_pass.html"><img src="../../../../../doc/html/images/next.png" alt="Next"></a>
+</div>
+</body>
+</html>

Added: trunk/libs/spirit/doc/html/spirit/support/multi_pass.html
==============================================================================
--- (empty file)
+++ trunk/libs/spirit/doc/html/spirit/support/multi_pass.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -0,0 +1,1086 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>The multi pass iterator</title>
+<link rel="stylesheet" href="../../../../../../doc/html/boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
+<link rel="home" href="../../index.html" title="Spirit 2.1">
+<link rel="up" href="../support.html" title="Supporting libraries">
+<link rel="prev" href="../support.html" title="Supporting libraries">
+<link rel="next" href="../faq.html" title="Spirit FAQ">
+</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">People</td>
+<td align="center">FAQ</td>
+<td align="center">More</td>
+</tr></table>
+<hr>
+<div class="spirit-nav">
+<a accesskey="p" href="../support.html"><img src="../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../support.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="../faq.html"><img src="../../../../../../doc/html/images/next.png" alt="Next"></a>
+</div>
+<div class="section" title="The multi pass iterator">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="spirit.support.multi_pass"></a><a class="link" href="multi_pass.html" title="The multi pass iterator"> The multi pass iterator</a>
+</h3></div></div></div>
+<p>
+ Backtracking in <span class="emphasis"><em>Spirit.Qi</em></span> requires the use of the following
+ types of iterator: forward, bidirectional, or random access. Because of backtracking,
+ input iterators cannot be used. Therefore, the standard library classes
+ <code class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">istreambuf_iterator</span></code> and <code class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">istream_iterator</span></code>,
+ that fall under the category of input iterators, cannot be used. Another
+ input iterator that is of interest is one that wraps a lexer, such as LEX.
+ </p>
+<div class="note" title="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>
+</tr>
+<tr><td align="left" valign="top"><p>
+ In general, <span class="emphasis"><em>Spirit.Qi</em></span> generates recursive descent
+ parser which require backtracking parsers by design. For this reason we
+ need to provide at least forward iterators to any of <span class="emphasis"><em>Spirit.Qi</em></span>'s
+ API functions. This is not an absolute requirement though. In the future,
+ we shall see more deterministic parsers that require no more than 1 character
+ (token) of lookahead. Such parsers allow us to use input iterators such
+ as the <code class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">istream_iterator</span></code> as is.
+ </p></td></tr>
+</table></div>
+<p>
+ Backtracking can be implemented only if we are allowed to save an iterator
+ position, i.e. making a copy of the current iterator. Unfortunately, with
+ an input iterator, there is no way to do so, and thus input iterators will
+ not work with backtracking in <span class="emphasis"><em>Spirit.Qi</em></span>. One solution
+ to this problem is to simply load all the data to be parsed into a container,
+ such as a vector or deque, and then pass the begin and end of the container
+ to <span class="emphasis"><em>Spirit.Qi</em></span>. This method can be too memory intensive
+ for certain applications, which is why the <code class="computeroutput"><span class="identifier">multi_pass</span></code>
+ iterator was created.
+ </p>
+<a name="spirit.support.multi_pass.using_the_multi_pass"></a><h5>
+<a name="id1119204"></a>
+ <a class="link" href="multi_pass.html#spirit.support.multi_pass.using_the_multi_pass">Using the
+ multi_pass</a>
+ </h5>
+<p>
+ The <code class="computeroutput"><span class="identifier">multi_pass</span></code> iterator will
+ convert any input iterator into a forward iterator suitable for use with
+ <span class="emphasis"><em>Spirit.Qi</em></span>. <code class="computeroutput"><span class="identifier">multi_pass</span></code>
+ will buffer data when needed and will discard the buffer when its contents
+ is not needed anymore. This happens either if only one copy of the iterator
+ exists or if no backtracking can occur.
+ </p>
+<p>
+ A grammar must be designed with care if the <code class="computeroutput"><span class="identifier">multi_pass</span></code>
+ iterator is used. Any rule that may need to backtrack, such as one that contains
+ an alternative, will cause data to be buffered. The rules that are optimal
+ to use are sequence and repetition. Sequences of the form <code class="computeroutput"><span class="identifier">a</span>
+ <span class="special">&gt;&gt;</span> <span class="identifier">b</span></code>
+ will not buffer data at all. Any rule that repeats, such as kleene_star (<code class="computeroutput"><span class="special">*</span><span class="identifier">a</span></code>) or
+ positive such as (<code class="computeroutput"><span class="special">+</span><span class="identifier">a</span></code>),
+ will only buffer the data for the current repetition.
+ </p>
+<p>
+ In typical grammars, ambiguity and therefore lookahead is often localized.
+ In fact, many well designed languages are fully deterministic and require
+ no lookahead at all. Peeking at the first character from the input will immediately
+ determine the alternative branch to take. Yet, even with highly ambiguous
+ grammars, alternatives are often of the form <code class="computeroutput"><span class="special">*(</span><span class="identifier">a</span> <span class="special">|</span> <span class="identifier">b</span>
+ <span class="special">|</span> <span class="identifier">c</span> <span class="special">|</span> <span class="identifier">d</span><span class="special">)</span></code>.
+ The input iterator moves on and is never stuck at the beginning. Let's look
+ at a Pascal snippet for example:
+ </p>
+<pre class="programlisting"><span class="identifier">program</span> <span class="special">=</span>
+ <span class="identifier">programHeading</span> <span class="special">&gt;&gt;</span> <span class="identifier">block</span> <span class="special">&gt;&gt;</span> <span class="char">'.'</span>
+ <span class="special">;</span>
+
+<span class="identifier">block</span> <span class="special">=</span>
+ <span class="special">*(</span> <span class="identifier">labelDeclarationPart</span>
+ <span class="special">|</span> <span class="identifier">constantDefinitionPart</span>
+ <span class="special">|</span> <span class="identifier">typeDefinitionPart</span>
+ <span class="special">|</span> <span class="identifier">variableDeclarationPart</span>
+ <span class="special">|</span> <span class="identifier">procedureAndFunctionDeclarationPart</span>
+ <span class="special">)</span>
+ <span class="special">&gt;&gt;</span> <span class="identifier">statementPart</span>
+ <span class="special">;</span>
+</pre>
+<p>
+ Notice the alternatives inside the Kleene star in the rule block . The rule
+ gobbles the input in a linear manner and throws away the past history with
+ each iteration. As this is fully deterministic LL(1) grammar, each failed
+ alternative only has to peek 1 character (token). The alternative that consumes
+ more than 1 character (token) is definitely a winner. After which, the Kleene
+ star moves on to the next.
+ </p>
+<p>
+ Now, after the lecture on the features to be careful with when using <code class="computeroutput"><span class="identifier">multi_pass</span></code>, you may think that <code class="computeroutput"><span class="identifier">multi_pass</span></code> is way too restrictive to use.
+ That's not the case. If your grammar is deterministic, you can make use of
+ the <code class="computeroutput"><span class="identifier">flush_multi_pass</span></code> pseudo
+ parser in your grammar to ensure that data is not buffered when unnecessary
+ (<code class="computeroutput"><span class="identifier">flush_multi_pass</span></code> is available
+ from the <span class="emphasis"><em>Spirit.Qi</em></span> parser repository).
+ </p>
+<p>
+ Here we present a minimal example showing a minimal use case. The <code class="computeroutput"><span class="identifier">multi_pass</span></code> iterator is highly configurable,
+ but the default policies have been chosen so that its easily usable with
+ input iterators such as <code class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">istreambuf_iterator</span></code>.
+ For the complete source code of this example please refer to multi_pass.cpp.
+ </p>
+<p>
+ </p>
+<p>
+
+</p>
+<pre class="programlisting"><span class="keyword">int</span> <span class="identifier">main</span><span class="special">()</span>
+<span class="special">{</span>
+ <span class="keyword">namespace</span> <span class="identifier">spirit</span> <span class="special">=</span> <span class="identifier">boost</span><span class="special">::</span><span class="identifier">spirit</span><span class="special">;</span>
+ <span class="keyword">using</span> <span class="identifier">spirit</span><span class="special">::</span><span class="identifier">ascii</span><span class="special">::</span><span class="identifier">space</span><span class="special">;</span>
+ <span class="keyword">using</span> <span class="identifier">spirit</span><span class="special">::</span><span class="identifier">ascii</span><span class="special">::</span><span class="identifier">char_</span><span class="special">;</span>
+ <span class="keyword">using</span> <span class="identifier">spirit</span><span class="special">::</span><span class="identifier">qi</span><span class="special">::</span><span class="identifier">double_</span><span class="special">;</span>
+ <span class="keyword">using</span> <span class="identifier">spirit</span><span class="special">::</span><span class="identifier">qi</span><span class="special">::</span><span class="identifier">eol</span><span class="special">;</span>
+
+ <span class="identifier">std</span><span class="special">::</span><span class="identifier">ifstream</span> <span class="identifier">in</span><span class="special">(</span><span class="string">"multi_pass.txt"</span><span class="special">);</span> <span class="comment">// we get our input from this file
+</span> <span class="keyword">if</span> <span class="special">(!</span><span class="identifier">in</span><span class="special">.</span><span class="identifier">is_open</span><span class="special">())</span> <span class="special">{</span>
+ <span class="identifier">std</span><span class="special">::</span><span class="identifier">cout</span> <span class="special">&lt;&lt;</span> <span class="string">"Could not open input file: 'multi_pass.txt'"</span> <span class="special">&lt;&lt;</span> <span class="identifier">std</span><span class="special">::</span><span class="identifier">endl</span><span class="special">;</span>
+ <span class="keyword">return</span> <span class="special">-</span><span class="number">1</span><span class="special">;</span>
+ <span class="special">}</span>
+
+ <span class="keyword">typedef</span> <span class="identifier">std</span><span class="special">::</span><span class="identifier">istreambuf_iterator</span><span class="special">&lt;</span><span class="keyword">char</span><span class="special">&gt;</span> <span class="identifier">base_iterator_type</span><span class="special">;</span>
+ <span class="identifier">spirit</span><span class="special">::</span><span class="identifier">multi_pass</span><span class="special">&lt;</span><span class="identifier">base_iterator_type</span><span class="special">&gt;</span> <span class="identifier">first</span> <span class="special">=</span>
+ <span class="identifier">spirit</span><span class="special">::</span><span class="identifier">make_default_multi_pass</span><span class="special">(</span><span class="identifier">base_iterator_type</span><span class="special">(</span><span class="identifier">in</span><span class="special">));</span>
+
+ <span class="identifier">std</span><span class="special">::</span><span class="identifier">vector</span><span class="special">&lt;</span><span class="keyword">double</span><span class="special">&gt;</span> <span class="identifier">v</span><span class="special">;</span>
+ <span class="keyword">bool</span> <span class="identifier">result</span> <span class="special">=</span> <span class="identifier">spirit</span><span class="special">::</span><span class="identifier">qi</span><span class="special">::</span><span class="identifier">phrase_parse</span><span class="special">(</span><span class="identifier">first</span>
+ <span class="special">,</span> <span class="identifier">spirit</span><span class="special">::</span><span class="identifier">make_default_multi_pass</span><span class="special">(</span><span class="identifier">base_iterator_type</span><span class="special">())</span>
+ <span class="special">,</span> <span class="identifier">double_</span> <span class="special">&gt;&gt;</span> <span class="special">*(</span><span class="char">','</span> <span class="special">&gt;&gt;</span> <span class="identifier">double_</span><span class="special">)</span> <span class="comment">// recognize list of doubles
+</span> <span class="special">,</span> <span class="identifier">space</span> <span class="special">|</span> <span class="char">'#'</span> <span class="special">&gt;&gt;</span> <span class="special">*(</span><span class="identifier">char_</span> <span class="special">-</span> <span class="identifier">eol</span><span class="special">)</span> <span class="special">&gt;&gt;</span> <span class="identifier">eol</span> <span class="comment">// comment skipper
+</span> <span class="special">,</span> <span class="identifier">v</span><span class="special">);</span> <span class="comment">// data read from file
+</span>
+ <span class="keyword">if</span> <span class="special">(!</span><span class="identifier">result</span><span class="special">)</span> <span class="special">{</span>
+ <span class="identifier">std</span><span class="special">::</span><span class="identifier">cout</span> <span class="special">&lt;&lt;</span> <span class="string">"Failed parsing input file!"</span> <span class="special">&lt;&lt;</span> <span class="identifier">std</span><span class="special">::</span><span class="identifier">endl</span><span class="special">;</span>
+ <span class="keyword">return</span> <span class="special">-</span><span class="number">2</span><span class="special">;</span>
+ <span class="special">}</span>
+
+ <span class="identifier">std</span><span class="special">::</span><span class="identifier">cout</span> <span class="special">&lt;&lt;</span> <span class="string">"Successfully parsed input file!"</span> <span class="special">&lt;&lt;</span> <span class="identifier">std</span><span class="special">::</span><span class="identifier">endl</span><span class="special">;</span>
+ <span class="keyword">return</span> <span class="number">0</span><span class="special">;</span>
+<span class="special">}</span>
+</pre>
+<p>
+ </p>
+<p>
+ </p>
+<a name="spirit.support.multi_pass.using_the_flush_multi_pass_parser"></a><h5>
+<a name="id1120281"></a>
+ <a class="link" href="multi_pass.html#spirit.support.multi_pass.using_the_flush_multi_pass_parser">Using
+ the flush_multi_pass parser</a>
+ </h5>
+<p>
+ The Spirit repository
+ contains the <code class="computeroutput"><span class="identifier">flush_multi_pass</span></code>
+ parser component. This is usable in conjunction with the <code class="computeroutput"><span class="identifier">multi_pass</span></code>
+ iterator to minimize the buffering. It allows to insert explicit synchronization
+ points into your grammar where it is safe to clear any stored input as it
+ is ensured that no backtracking can occur at this point anymore.
+ </p>
+<p>
+ When the <code class="computeroutput"><span class="identifier">flush_multi_pass</span></code>
+ parser is used with <code class="computeroutput"><span class="identifier">multi_pass</span></code>,
+ it will call <code class="computeroutput"><span class="identifier">multi_pass</span><span class="special">::</span><span class="identifier">clear_queue</span><span class="special">()</span></code>.
+ This will cause any buffered data to be erased. This also will invalidate
+ all other copies of multi_pass and they should not be used. If they are,
+ an <code class="computeroutput"><span class="identifier">boost</span><span class="special">::</span><span class="identifier">illegal_backtracking</span></code> exception will be
+ thrown.
+ </p>
+<a name="spirit.support.multi_pass.the_multi_pass_policies"></a><h5>
+<a name="id1120370"></a>
+ <a class="link" href="multi_pass.html#spirit.support.multi_pass.the_multi_pass_policies">The multi_pass
+ Policies</a>
+ </h5>
+<p>
+ The <code class="computeroutput"><span class="identifier">multi_pass</span></code> iterator is
+ a templated class configurable using policies. The description of <code class="computeroutput"><span class="identifier">multi_pass</span></code> above is how it was originally
+ implemented (before it used policies), and is the default configuration now.
+ But, <code class="computeroutput"><span class="identifier">multi_pass</span></code> is capable
+ of much more. Because of the open-ended nature of policies, you can write
+ your own policy to make <code class="computeroutput"><span class="identifier">multi_pass</span></code>
+ behave in a way that we never before imagined.
+ </p>
+<p>
+ The multi_pass class has two template parameters:
+ </p>
+<div class="variablelist" title="The multi_pass template parameters">
+<p class="title"><b>The multi_pass template parameters</b></p>
+<dl>
+<dt><span class="term">Input</span></dt>
+<dd><p>
+ The type multi_pass uses to acquire it's input. This is typically an
+ input iterator, or functor.
+ </p></dd>
+<dt><span class="term">Policies</span></dt>
+<dd><p>
+ The combined policies to use to create an instance of a multi_pass iterator.
+ This combined policy type is described below
+ </p></dd>
+</dl>
+</div>
+<p>
+ It is possible to implement all of the required functionality of the combinded
+ policy in a single class. But it has shown to be more convenient to split
+ this into four different groups of functions, i.e. four separate, but well
+ coordinated policies. For this reason the <code class="computeroutput"><span class="identifier">multi_pass</span></code>
+ framework implements a template <code class="computeroutput"><span class="identifier">iterator_policies</span><span class="special">::</span><span class="identifier">default_policy</span></code>
+ allowing to combine several different policies, each implementing one of
+ the functionality groups:
+ </p>
+<div class="table">
+<a name="id1120476"></a><p class="title"><b>Table 10. Policies needed for default_policy template</b></p>
+<div class="table-contents"><table class="table" summary="Policies needed for default_policy template">
+<colgroup>
+<col>
+<col>
+</colgroup>
+<thead><tr>
+<th>
+ <p>
+ Template Parameter
+ </p>
+ </th>
+<th>
+ <p>
+ Description
+ </p>
+ </th>
+</tr></thead>
+<tbody>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">OwnershipPolicy</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ This policy determines how <code class="computeroutput"><span class="identifier">multi_pass</span></code>
+ deals with it's shared components.
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">CheckingPolicy</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ This policy determines how checking for invalid iterators is done.
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">InputPolicy</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ A class that defines how <code class="computeroutput"><span class="identifier">multi_pass</span></code>
+ acquires its input. The <code class="computeroutput"><span class="identifier">InputPolicy</span></code>
+ is parameterized by the <code class="computeroutput"><span class="identifier">Input</span></code>
+ template parameter to the <code class="computeroutput"><span class="identifier">multi_pass</span></code>.
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">StoragePolicy</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ The buffering scheme used by <code class="computeroutput"><span class="identifier">multi_pass</span></code>
+ is determined and managed by the StoragePolicy.
+ </p>
+ </td>
+</tr>
+</tbody>
+</table></div>
+</div>
+<br class="table-break"><p>
+ The <code class="computeroutput"><span class="identifier">multi_pass</span></code> framework
+ contains several predefined policy implementations for each of the policy
+ types as described above. First we will describe those predefined types.
+ Afterwards we will give some guidelines how you can write your own policy
+ implementations.
+ </p>
+<a name="spirit.support.multi_pass.predefined_policies"></a><h5>
+<a name="id1120668"></a>
+ <a class="link" href="multi_pass.html#spirit.support.multi_pass.predefined_policies">Predefined
+ policies</a>
+ </h5>
+<p>
+ All predefined <code class="computeroutput"><span class="identifier">multi_pass</span></code>
+ policies are defined in the namespace <code class="computeroutput"><span class="identifier">boost</span><span class="special">::</span><span class="identifier">spirit</span><span class="special">::</span><span class="identifier">iterator_policies</span></code>.
+ </p>
+<div class="table">
+<a name="id1120710"></a><p class="title"><b>Table 11. Predefined InputPolicy classes</b></p>
+<div class="table-contents"><table class="table" summary="Predefined InputPolicy classes">
+<colgroup>
+<col>
+<col>
+</colgroup>
+<thead><tr>
+<th>
+ <p>
+ Class name
+ </p>
+ </th>
+<th>
+ <p>
+ Description
+ </p>
+ </th>
+</tr></thead>
+<tbody>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">input_iterator</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ This policy directs <code class="computeroutput"><span class="identifier">multi_pass</span></code>
+ to read from an input iterator of type <code class="computeroutput"><span class="identifier">Input</span></code>.
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">lex_input</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ This policy obtains it's input by calling yylex(), which would typically
+ be provided by a scanner generated by Flex.
+ If you use this policy your code must link against a Flex
+ generated scanner.
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">functor_input</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ This input policy obtains it's data by calling a functor of type <code class="computeroutput"><span class="identifier">Input</span></code>. The functor must meet certain
+ requirements. It must have a typedef called <code class="computeroutput"><span class="identifier">result_type</span></code>
+ which should be the type returned from <code class="computeroutput"><span class="keyword">operator</span><span class="special">()</span></code>. Also, since an input policy needs
+ a way to determine when the end of input has been reached, the functor
+ must contain a static variable named <code class="computeroutput"><span class="identifier">eof</span></code>
+ which is comparable to a variable of <code class="computeroutput"><span class="identifier">result_type</span></code>.
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">split_functor_input</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ This is essentially the same as the <code class="computeroutput"><span class="identifier">functor_input</span></code>
+ policy except that the (user supplied) funtion object exposes separate
+ <code class="computeroutput"><span class="identifier">unique</span></code> and <code class="computeroutput"><span class="identifier">shared</span></code> sub classes, allowing to integrate
+ the functors <span class="emphasis"><em>unique</em></span> data members with the <code class="computeroutput"><span class="identifier">multi_pass</span></code> data items held by each
+ instance and its <span class="emphasis"><em>shared</em></span> data members will be integrated
+ with the <code class="computeroutput"><span class="identifier">multi_pass</span></code>
+ members shared by all copies.
+ </p>
+ </td>
+</tr>
+</tbody>
+</table></div>
+</div>
+<br class="table-break"><div class="table">
+<a name="id1121050"></a><p class="title"><b>Table 12. Predefined OwnershipPolicy classes</b></p>
+<div class="table-contents"><table class="table" summary="Predefined OwnershipPolicy classes">
+<colgroup>
+<col>
+<col>
+</colgroup>
+<thead><tr>
+<th>
+ <p>
+ Class name
+ </p>
+ </th>
+<th>
+ <p>
+ Description
+ </p>
+ </th>
+</tr></thead>
+<tbody>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">ref_counted</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ This class uses a reference counting scheme. The <code class="computeroutput"><span class="identifier">multi_pass</span></code>
+ will delete it's shared components when the count reaches zero.
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">first_owner</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ When this policy is used, the first <code class="computeroutput"><span class="identifier">multi_pass</span></code>
+ created will be the one that deletes the shared data. Each copy will
+ not take ownership of the shared data. This works well for Spirit,
+ since no dynamic allocation of iterators is done. All copies are made
+ on the stack, so the original iterator has the longest lifespan.
+ </p>
+ </td>
+</tr>
+</tbody>
+</table></div>
+</div>
+<br class="table-break"><div class="table">
+<a name="id1121155"></a><p class="title"><b>Table 13. Predefined CheckingPolicy classes</b></p>
+<div class="table-contents"><table class="table" summary="Predefined CheckingPolicy classes">
+<colgroup>
+<col>
+<col>
+</colgroup>
+<thead><tr>
+<th>
+ <p>
+ Class name
+ </p>
+ </th>
+<th>
+ <p>
+ Description
+ </p>
+ </th>
+</tr></thead>
+<tbody>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">no_check</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ This policy does no checking at all.
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">buf_id_check</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ This policy keeps around a buffer id, or a buffer age. Every time
+ <code class="computeroutput"><span class="identifier">clear_queue</span><span class="special">()</span></code>
+ is called on a <code class="computeroutput"><span class="identifier">multi_pass</span></code>
+ iterator, it is possible that all other iterators become invalid. When
+ <code class="computeroutput"><span class="identifier">clear_queue</span><span class="special">()</span></code>
+ is called, <code class="computeroutput"><span class="identifier">buf_id_check</span></code>
+ increments the buffer id. When an iterator is dereferenced, this policy
+ checks that the buffer id of the iterator matches the shared buffer
+ id. This policy is most effective when used together with the <code class="computeroutput"><span class="identifier">split_std_deque</span></code> StoragePolicy. It
+ should not be used with the <code class="computeroutput"><span class="identifier">fixed_size_queue</span></code>
+ StoragePolicy, because it will not detect iterator dereferences that
+ are out of range.
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ full_check
+ </p>
+ </td>
+<td>
+ <p>
+ This policy has not been implemented yet. When it is, it will keep
+ track of all iterators and make sure that they are all valid. This
+ will be mostly useful for debugging purposes as it will incur significant
+ overhead.
+ </p>
+ </td>
+</tr>
+</tbody>
+</table></div>
+</div>
+<br class="table-break"><div class="table">
+<a name="id1121308"></a><p class="title"><b>Table 14. Predefined StoragePolicy classes</b></p>
+<div class="table-contents"><table class="table" summary="Predefined StoragePolicy classes">
+<colgroup>
+<col>
+<col>
+</colgroup>
+<thead><tr>
+<th>
+ <p>
+ Class name
+ </p>
+ </th>
+<th>
+ <p>
+ Description
+ </p>
+ </th>
+</tr></thead>
+<tbody>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">split_std_deque</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ Despite its name this policy keeps all buffered data in a <code class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">vector</span></code>. All data is stored as long
+ as there is more than one iterator. Once the iterator count goes down
+ to one, and the queue is no longer needed, it is cleared, freeing up
+ memory. The queue can also be forcibly cleared by calling <code class="computeroutput"><span class="identifier">multi_pass</span><span class="special">::</span><span class="identifier">clear_queue</span><span class="special">()</span></code>.
+ </p>
+ </td>
+</tr>
+<tr>
+<td>
+ <p>
+ <code class="computeroutput"><span class="identifier">fixed_size_queue</span><span class="special">&lt;</span><span class="identifier">N</span><span class="special">&gt;</span></code>
+ </p>
+ </td>
+<td>
+ <p>
+ This policy keeps a circular buffer that is size <code class="computeroutput"><span class="identifier">N</span><span class="special">+</span><span class="number">1</span></code> and
+ stores <code class="computeroutput"><span class="identifier">N</span></code> elements.
+ <code class="computeroutput"><span class="identifier">fixed_size_queue</span></code> is
+ a template with a <code class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">size_t</span></code>
+ parameter that specified the queue size. It is your responsibility
+ to ensure that <code class="computeroutput"><span class="identifier">N</span></code> is
+ big enough for your parser. Whenever the foremost iterator is incremented,
+ the last character of the buffer is automatically erased. Currently
+ there is no way to tell if an iterator is trailing too far behind and
+ has become invalid. No dynamic allocation is done by this policy during
+ normal iterator operation, only on initial construction. The memory
+ usage of this <code class="computeroutput"><span class="identifier">StoragePolicy</span></code>
+ is set at <code class="computeroutput"><span class="identifier">N</span><span class="special">+</span><span class="number">1</span></code> bytes, unlike <code class="computeroutput"><span class="identifier">split_std_deque</span></code>,
+ which is unbounded.
+ </p>
+ </td>
+</tr>
+</tbody>
+</table></div>
+</div>
+<br class="table-break"><a name="spirit.support.multi_pass.combinations__how_to_specify_your_own_custom_multi_pass"></a><h5>
+<a name="id1121520"></a>
+ <a class="link" href="multi_pass.html#spirit.support.multi_pass.combinations__how_to_specify_your_own_custom_multi_pass">Combinations:
+ How to specify your own custom multi_pass</a>
+ </h5>
+<p>
+ The beauty of policy based designs is that you can mix and match policies
+ to create your own custom iterator by selecting the policies you want. Here's
+ an example of how to specify a custom <code class="computeroutput"><span class="identifier">multi_pass</span></code>
+ that wraps an <code class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">istream_iterator</span><span class="special">&lt;</span><span class="keyword">char</span><span class="special">&gt;</span></code>,
+ and is slightly more efficient than the default <code class="computeroutput"><span class="identifier">multi_pass</span></code>
+ (as generated by the <code class="computeroutput"><span class="identifier">make_default_multi_pass</span><span class="special">()</span></code> API function) because it uses the <code class="computeroutput"><span class="identifier">iterator_policies</span><span class="special">::</span><span class="identifier">first_owner</span></code> OwnershipPolicy and the <code class="computeroutput"><span class="identifier">iterator_policies</span><span class="special">::</span><span class="identifier">no_check</span></code> CheckingPolicy:
+ </p>
+<pre class="programlisting"><span class="keyword">typedef</span> <span class="identifier">multi_pass</span><span class="special">&lt;</span>
+ <span class="identifier">std</span><span class="special">::</span><span class="identifier">istream_iterator</span><span class="special">&lt;</span><span class="keyword">char</span><span class="special">&gt;</span>
+ <span class="special">,</span> <span class="identifier">iterator_policies</span><span class="special">::</span><span class="identifier">default_policy</span><span class="special">&lt;</span>
+ <span class="identifier">iterator_policies</span><span class="special">::</span><span class="identifier">first_owner</span>
+ <span class="special">,</span> <span class="identifier">iterator_policies</span><span class="special">::</span><span class="identifier">no_check</span>
+ <span class="special">,</span> <span class="identifier">iterator_policies</span><span class="special">::</span><span class="identifier">input_iterator</span>
+ <span class="special">,</span> <span class="identifier">iterator_policies</span><span class="special">::</span><span class="identifier">split_std_deque</span>
+ <span class="special">&gt;</span>
+<span class="special">&gt;</span> <span class="identifier">first_owner_multi_pass_type</span><span class="special">;</span>
+</pre>
+<p>
+ The default template parameters for <code class="computeroutput"><span class="identifier">iterator_policies</span><span class="special">::</span><span class="identifier">default_policy</span></code>
+ are:
+ </p>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem">
+<code class="computeroutput"><span class="identifier">iterator_policies</span><span class="special">::</span><span class="identifier">ref_counted</span></code> OwnershipPolicy
+ </li>
+<li class="listitem">
+<code class="computeroutput"><span class="identifier">iterator_policies</span><span class="special">::</span><span class="identifier">no_check</span></code> CheckingPolicy, if <code class="computeroutput"><span class="identifier">BOOST_SPIRIT_DEBUG</span></code> is defined: <code class="computeroutput"><span class="identifier">iterator_policies</span><span class="special">::</span><span class="identifier">buf_id_check</span></code> CheckingPolicy
+ </li>
+<li class="listitem">
+<code class="computeroutput"><span class="identifier">iterator_policies</span><span class="special">::</span><span class="identifier">input_iterator</span></code> InputPolicy, and
+ </li>
+<li class="listitem">
+<code class="computeroutput"><span class="identifier">iterator_policies</span><span class="special">::</span><span class="identifier">split_std_deque</span></code> StoragePolicy.
+ </li>
+</ul></div>
+<p>
+ So if you use <code class="computeroutput"><span class="identifier">multi_pass</span><span class="special">&lt;</span><span class="identifier">std</span><span class="special">::</span><span class="identifier">istream_iterator</span><span class="special">&lt;</span><span class="keyword">char</span><span class="special">&gt;</span>
+ <span class="special">&gt;</span></code> you will get those pre-defined
+ behaviors while wrapping an <code class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">istream_iterator</span><span class="special">&lt;</span><span class="keyword">char</span><span class="special">&gt;</span></code>.
+ </p>
+<a name="spirit.support.multi_pass.dealing_with_constant_look_ahead"></a><h5>
+<a name="id1121942"></a>
+ <a class="link" href="multi_pass.html#spirit.support.multi_pass.dealing_with_constant_look_ahead">Dealing
+ with constant look ahead</a>
+ </h5>
+<p>
+ There is one other pre-defined class called <code class="computeroutput"><span class="identifier">look_ahead</span></code>.
+ The class <code class="computeroutput"><span class="identifier">look_ahead</span></code> is another
+ predefine <code class="computeroutput"><span class="identifier">multi_pass</span></code> iterator
+ type. It has two template parameters: <code class="computeroutput"><span class="identifier">Input</span></code>,
+ the type of the input iterator to wrap, and a <code class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">size_t</span> <span class="identifier">N</span></code>, which specifies the size of the buffer
+ to the <code class="computeroutput"><span class="identifier">fixed_size_queue</span></code> policy.
+ While the default multi_pass configuration is designed for safey, <code class="computeroutput"><span class="identifier">look_ahead</span></code> is designed for speed. <code class="computeroutput"><span class="identifier">look_ahead</span></code> is derived from a multi_pass
+ with the following policies: <code class="computeroutput"><span class="identifier">input_iterator</span></code>
+ InputPolicy, <code class="computeroutput"><span class="identifier">first_owner</span></code>
+ OwnershipPolicy, <code class="computeroutput"><span class="identifier">no_check</span></code>
+ CheckingPolicy, and <code class="computeroutput"><span class="identifier">fixed_size_queue</span><span class="special">&lt;</span><span class="identifier">N</span><span class="special">&gt;</span></code>
+ StoragePolicy.
+ </p>
+<a name="spirit.support.multi_pass.how_to_write_a_functor_for_use_with_the__code__phrase_role__identifier__functor_input__phrase___code__inputpolicy"></a><h5>
+<a name="id1122074"></a>
+ <a class="link" href="multi_pass.html#spirit.support.multi_pass.how_to_write_a_functor_for_use_with_the__code__phrase_role__identifier__functor_input__phrase___code__inputpolicy">How
+ to write a functor for use with the <code class="computeroutput"><span class="identifier">functor_input</span></code>
+ InputPolicy</a>
+ </h5>
+<p>
+ If you want to use the <code class="computeroutput"><span class="identifier">functor_input</span></code>
+ InputPolicy, you can write your own function object that will supply the
+ input to <code class="computeroutput"><span class="identifier">multi_pass</span></code>. The
+ function object must satisfy several requirements. It must have a typedef
+ <code class="computeroutput"><span class="identifier">result_type</span></code> which specifies
+ the return type of its <code class="computeroutput"><span class="keyword">operator</span><span class="special">()</span></code>. This is standard practice in the STL.
+ Also, it must supply a static variable called eof which is compared against
+ to know whether the input has reached the end. Last but not least the function
+ object must be default constructible. Here is an example:
+ </p>
+<pre class="programlisting"><span class="comment">// define the function object
+</span><span class="keyword">class</span> <span class="identifier">iterate_a2m</span>
+<span class="special">{</span>
+<span class="keyword">public</span><span class="special">:</span>
+ <span class="keyword">typedef</span> <span class="keyword">char</span> <span class="identifier">result_type</span><span class="special">;</span>
+
+ <span class="identifier">iterate_a2m</span><span class="special">()</span> <span class="special">:</span> <span class="identifier">c</span><span class="special">(</span><span class="char">'A'</span><span class="special">)</span> <span class="special">{}</span>
+ <span class="identifier">iterate_a2m</span><span class="special">(</span><span class="keyword">char</span> <span class="identifier">c</span><span class="special">)</span> <span class="special">:</span> <span class="identifier">c_</span><span class="special">(</span><span class="identifier">c</span><span class="special">)</span> <span class="special">{}</span>
+
+ <span class="identifier">result_type</span> <span class="keyword">operator</span><span class="special">()()</span> <span class="keyword">const</span>
+ <span class="special">{</span>
+ <span class="keyword">if</span> <span class="special">(</span><span class="identifier">c_</span> <span class="special">==</span> <span class="char">'M'</span><span class="special">)</span>
+ <span class="keyword">return</span> <span class="identifier">eof</span><span class="special">;</span>
+ <span class="keyword">return</span> <span class="identifier">c_</span><span class="special">++;</span>
+ <span class="special">}</span>
+
+ <span class="keyword">static</span> <span class="identifier">result_type</span> <span class="identifier">eof</span><span class="special">;</span>
+
+<span class="keyword">private</span><span class="special">:</span>
+ <span class="keyword">char</span> <span class="identifier">c_</span><span class="special">;</span>
+<span class="special">};</span>
+
+<span class="identifier">iterate_a2m</span><span class="special">::</span><span class="identifier">result_type</span> <span class="identifier">iterate_a2m</span><span class="special">::</span><span class="identifier">eof</span> <span class="special">=</span> <span class="identifier">iterate_a2m</span><span class="special">::</span><span class="identifier">result_type</span><span class="special">(</span><span class="char">'\0'</span><span class="special">);</span>
+
+<span class="comment">// create two iterators using the define function object, one of which is
+</span><span class="comment">// an end iterator
+</span><span class="keyword">typedef</span> <span class="identifier">multi_pass</span><span class="special">&lt;</span><span class="identifier">my_functor</span>
+ <span class="special">,</span> <span class="identifier">iterator_policies</span><span class="special">::</span><span class="identifier">functor_input</span>
+ <span class="special">,</span> <span class="identifier">iterator_policies</span><span class="special">::</span><span class="identifier">first_owner</span>
+ <span class="special">,</span> <span class="identifier">iterator_policies</span><span class="special">::</span><span class="identifier">no_check</span>
+ <span class="special">,</span> <span class="identifier">iterator_policies</span><span class="special">::</span><span class="identifier">split_std_deque</span><span class="special">&gt;</span>
+<span class="identifier">functor_multi_pass_type</span><span class="special">;</span>
+
+<span class="identifier">functor_multi_pass_type</span> <span class="identifier">first</span> <span class="special">=</span> <span class="identifier">functor_multi_pass_t</span><span class="special">(</span><span class="identifier">my_functor</span><span class="special">());</span>
+<span class="identifier">functor_multi_pass_type</span> <span class="identifier">last</span><span class="special">;</span>
+
+<span class="comment">// use the iterators: this will print "ABCDEFGHIJKL"
+</span><span class="keyword">while</span> <span class="special">(</span><span class="identifier">first</span> <span class="special">!=</span> <span class="identifier">last</span><span class="special">)</span> <span class="special">{</span>
+ <span class="identifier">std</span><span class="special">::</span><span class="identifier">cout</span> <span class="special">&lt;&lt;</span> <span class="special">*</span><span class="identifier">first</span><span class="special">;</span>
+ <span class="special">++</span><span class="identifier">first</span><span class="special">;</span>
+<span class="special">}</span>
+</pre>
+<a name="spirit.support.multi_pass.how_to_write_policies_for_use_with_multi_pass"></a><h5>
+<a name="id1122661"></a>
+ <a class="link" href="multi_pass.html#spirit.support.multi_pass.how_to_write_policies_for_use_with_multi_pass">How
+ to write policies for use with multi_pass</a>
+ </h5>
+<p>
+ All policies to be used with the <code class="computeroutput"><span class="identifier">default_policy</span></code>
+ template need to have two embedded classes: <code class="computeroutput"><span class="identifier">unique</span></code>
+ and <code class="computeroutput"><span class="identifier">shared</span></code>. The <code class="computeroutput"><span class="identifier">unique</span></code> class needs to implement all required
+ functions for a particular policy type. In addition it may hold all member
+ data items being <span class="emphasis"><em>unique</em></span> for a particular instance of
+ a <code class="computeroutput"><span class="identifier">multi_pass</span></code> (hence the name).
+ The <code class="computeroutput"><span class="identifier">shared</span></code> class does not
+ expose any member functions (except sometimes a constructor), but it may
+ hold all member data items to be <span class="emphasis"><em>shared</em></span> between all
+ copies of a particular <code class="computeroutput"><span class="identifier">multi_pass</span></code>.
+ </p>
+<a name="spirit.support.multi_pass.inputpolicy"></a><h5>
+<a name="id1122735"></a>
+ <a class="link" href="multi_pass.html#spirit.support.multi_pass.inputpolicy">InputPolicy</a>
+ </h5>
+<p>
+ An <code class="computeroutput"><span class="identifier">InputPolicy</span></code> must have
+ the following interface:
+ </p>
+<pre class="programlisting"><span class="keyword">struct</span> <span class="identifier">input_policy</span>
+<span class="special">{</span>
+ <span class="comment">// Input is the same type used as the first template parameter
+</span> <span class="comment">// while instantiating the multi_pass
+</span> <span class="keyword">template</span> <span class="special">&lt;</span><span class="keyword">typename</span> <span class="identifier">Input</span><span class="special">&gt;</span>
+ <span class="keyword">struct</span> <span class="identifier">unique</span>
+ <span class="special">{</span>
+ <span class="comment">// these typedef's will be exposed as the multi_pass iterator
+</span> <span class="comment">// properties
+</span> <span class="keyword">typedef</span> <span class="identifier">__unspecified_type__</span> <span class="identifier">value_type</span><span class="special">;</span>
+ <span class="keyword">typedef</span> <span class="identifier">__unspecified_type__</span> <span class="identifier">difference_type</span><span class="special">;</span>
+ <span class="keyword">typedef</span> <span class="identifier">__unspecified_type__</span> <span class="identifier">distance_type</span><span class="special">;</span>
+ <span class="keyword">typedef</span> <span class="identifier">__unspecified_type__</span> <span class="identifier">pointer</span><span class="special">;</span>
+ <span class="keyword">typedef</span> <span class="identifier">__unspecified_type__</span> <span class="identifier">reference</span><span class="special">;</span>
+
+ <span class="identifier">unique</span><span class="special">()</span> <span class="special">{}</span>
+ <span class="keyword">explicit</span> <span class="identifier">unique</span><span class="special">(</span><span class="identifier">Input</span><span class="special">)</span> <span class="special">{}</span>
+
+ <span class="comment">// destroy is called whenever the last copy of a multi_pass is
+</span> <span class="comment">// destructed (ownership_policy::release() returned true)
+</span> <span class="comment">//
+</span> <span class="comment">// mp: is a reference to the whole multi_pass instance
+</span> <span class="keyword">template</span> <span class="special">&lt;</span><span class="keyword">typename</span> <span class="identifier">MultiPass</span><span class="special">&gt;</span>
+ <span class="keyword">static</span> <span class="keyword">void</span> <span class="identifier">destroy</span><span class="special">(</span><span class="identifier">MultiPass</span><span class="special">&amp;</span> <span class="identifier">mp</span><span class="special">);</span>
+
+ <span class="comment">// swap is called by multi_pass::swap()
+</span> <span class="keyword">void</span> <span class="identifier">swap</span><span class="special">(</span><span class="identifier">unique</span><span class="special">&amp;);</span>
+
+ <span class="comment">// advance_input is called whenever the next input character/token
+</span> <span class="comment">// should be fetched.
+</span> <span class="comment">//
+</span> <span class="comment">// mp: is a reference to the whole multi_pass instance
+</span> <span class="comment">// t: is a reference where the next character/token should be
+</span> <span class="comment">// stored
+</span> <span class="comment">//
+</span> <span class="comment">// This method is expected to return the parameter t
+</span> <span class="keyword">template</span> <span class="special">&lt;</span><span class="keyword">typename</span> <span class="identifier">MultiPass</span><span class="special">&gt;</span>
+ <span class="keyword">static</span> <span class="identifier">value_type</span><span class="special">&amp;</span> <span class="identifier">advance_input</span><span class="special">(</span><span class="identifier">MultiPass</span><span class="special">&amp;</span> <span class="identifier">mp</span><span class="special">,</span> <span class="identifier">value_type</span><span class="special">&amp;</span> <span class="identifier">t</span><span class="special">);</span>
+
+ <span class="comment">// input_at_eof is called to test whether this instance is a
+</span> <span class="comment">// end of input iterator.
+</span> <span class="comment">//
+</span> <span class="comment">// mp: is a reference to the whole multi_pass instance
+</span> <span class="comment">// t: is the current token
+</span> <span class="comment">//
+</span> <span class="comment">// This method is expected to return true if the end of input is
+</span> <span class="comment">// reached. It is often used in the implementation of the function
+</span> <span class="comment">// storage_policy::is_eof.
+</span> <span class="keyword">template</span> <span class="special">&lt;</span><span class="keyword">typename</span> <span class="identifier">MultiPass</span><span class="special">&gt;</span>
+ <span class="keyword">static</span> <span class="keyword">bool</span> <span class="identifier">input_at_eof</span><span class="special">(</span><span class="identifier">MultiPass</span> <span class="keyword">const</span><span class="special">&amp;</span> <span class="identifier">mp</span><span class="special">,</span> <span class="identifier">value_type</span> <span class="keyword">const</span><span class="special">&amp;</span> <span class="identifier">t</span><span class="special">);</span>
+
+ <span class="comment">// input_is_valid is called to verify if the parameter t represents
+</span> <span class="comment">// a valid input character/token
+</span> <span class="comment">//
+</span> <span class="comment">// mp: is a reference to the whole multi_pass instance
+</span> <span class="comment">// t: is the character/token to test for validity
+</span> <span class="comment">//
+</span> <span class="comment">// This method is expected to return true if the parameter t
+</span> <span class="comment">// represents a valid character/token.
+</span> <span class="keyword">template</span> <span class="special">&lt;</span><span class="keyword">typename</span> <span class="identifier">MultiPass</span><span class="special">&gt;</span>
+ <span class="keyword">static</span> <span class="keyword">bool</span> <span class="identifier">input_is_valid</span><span class="special">(</span><span class="identifier">MultiPass</span> <span class="keyword">const</span><span class="special">&amp;</span> <span class="identifier">mp</span><span class="special">,</span> <span class="identifier">value_type</span> <span class="keyword">const</span><span class="special">&amp;</span> <span class="identifier">t</span><span class="special">);</span>
+ <span class="special">};</span>
+
+ <span class="comment">// Input is the same type used as the first template parameter
+</span> <span class="comment">// while instantiating the multi_pass
+</span> <span class="keyword">template</span> <span class="special">&lt;</span><span class="keyword">typename</span> <span class="identifier">Input</span><span class="special">&gt;</span>
+ <span class="keyword">struct</span> <span class="identifier">shared</span>
+ <span class="special">{</span>
+ <span class="keyword">explicit</span> <span class="identifier">shared</span><span class="special">(</span><span class="identifier">Input</span><span class="special">)</span> <span class="special">{}</span>
+ <span class="special">};</span>
+<span class="special">};</span>
+</pre>
+<p>
+ It is possible to derive the struct <code class="computeroutput"><span class="identifier">unique</span></code>
+ from the type <code class="computeroutput"><span class="identifier">boost</span><span class="special">::</span><span class="identifier">spirit</span><span class="special">::</span><span class="identifier">detail</span><span class="special">::</span><span class="identifier">default_input_policy</span></code>. This type implements
+ a minimal sufficient interface for some of the required functions, simplifying
+ the task of writing a new input policy.
+ </p>
+<p>
+ This class may implement a function <code class="computeroutput"><span class="identifier">destroy</span><span class="special">()</span></code> being called during destruction of the
+ last copy of a <code class="computeroutput"><span class="identifier">multi_pass</span></code>.
+ This function should be used to free any of the shared data items the policy
+ might have allocated during construction of its <code class="computeroutput"><span class="identifier">shared</span></code>
+ part. Because of the way <code class="computeroutput"><span class="identifier">multi_pass</span></code>
+ is implemented any allocated data members in <code class="computeroutput"><span class="identifier">shared</span></code>
+ should <span class="underline">not</span> be deep copied in a copy
+ constructor of <code class="computeroutput"><span class="identifier">shared</span></code>.
+ </p>
+<a name="spirit.support.multi_pass.ownershippolicy"></a><h5>
+<a name="id1125273"></a>
+ <a class="link" href="multi_pass.html#spirit.support.multi_pass.ownershippolicy">OwnershipPolicy</a>
+ </h5>
+<p>
+ The <code class="computeroutput"><span class="identifier">OwnershipPolicy</span></code> must
+ have the following interface:
+ </p>
+<pre class="programlisting"><span class="keyword">struct</span> <span class="identifier">ownership_policy</span>
+<span class="special">{</span>
+ <span class="keyword">struct</span> <span class="identifier">unique</span>
+ <span class="special">{</span>
+ <span class="comment">// destroy is called whenever the last copy of a multi_pass is
+</span> <span class="comment">// destructed (ownership_policy::release() returned true)
+</span> <span class="comment">//
+</span> <span class="comment">// mp: is a reference to the whole multi_pass instance
+</span> <span class="keyword">template</span> <span class="special">&lt;</span><span class="keyword">typename</span> <span class="identifier">MultiPass</span><span class="special">&gt;</span>
+ <span class="keyword">static</span> <span class="keyword">void</span> <span class="identifier">destroy</span><span class="special">(</span><span class="identifier">MultiPass</span><span class="special">&amp;</span> <span class="identifier">mp</span><span class="special">);</span>
+
+ <span class="comment">// swap is called by multi_pass::swap()
+</span> <span class="keyword">void</span> <span class="identifier">swap</span><span class="special">(</span><span class="identifier">unique</span><span class="special">&amp;);</span>
+
+ <span class="comment">// clone is called whenever a multi_pass is copied
+</span> <span class="comment">//
+</span> <span class="comment">// mp: is a reference to the whole multi_pass instance
+</span> <span class="keyword">template</span> <span class="special">&lt;</span><span class="keyword">typename</span> <span class="identifier">MultiPass</span><span class="special">&gt;</span>
+ <span class="keyword">static</span> <span class="keyword">void</span> <span class="identifier">clone</span><span class="special">(</span><span class="identifier">MultiPass</span><span class="special">&amp;</span> <span class="identifier">mp</span><span class="special">);</span>
+
+ <span class="comment">// release is called whenever a multi_pass is destroyed
+</span> <span class="comment">//
+</span> <span class="comment">// mp: is a reference to the whole multi_pass instance
+</span> <span class="comment">//
+</span> <span class="comment">// The method is expected to return true if the destructed
+</span> <span class="comment">// instance is the last copy of a particular multi_pass.
+</span> <span class="keyword">template</span> <span class="special">&lt;</span><span class="keyword">typename</span> <span class="identifier">MultiPass</span><span class="special">&gt;</span>
+ <span class="keyword">static</span> <span class="keyword">bool</span> <span class="identifier">release</span><span class="special">(</span><span class="identifier">MultiPass</span><span class="special">&amp;</span> <span class="identifier">mp</span><span class="special">);</span>
+
+ <span class="comment">// is_unique is called to test whether this instance is the only
+</span> <span class="comment">// existing copy of a particular multi_pass
+</span> <span class="comment">//
+</span> <span class="comment">// mp: is a reference to the whole multi_pass instance
+</span> <span class="comment">//
+</span> <span class="comment">// The method is expected to return true if this instance is unique
+</span> <span class="comment">// (no other copies of this multi_pass exist).
+</span> <span class="keyword">template</span> <span class="special">&lt;</span><span class="keyword">typename</span> <span class="identifier">MultiPass</span><span class="special">&gt;</span>
+ <span class="keyword">static</span> <span class="keyword">bool</span> <span class="identifier">is_unique</span><span class="special">(</span><span class="identifier">MultiPass</span> <span class="keyword">const</span><span class="special">&amp;</span> <span class="identifier">mp</span><span class="special">);</span>
+ <span class="special">};</span>
+
+ <span class="keyword">struct</span> <span class="identifier">shared</span> <span class="special">{};</span>
+<span class="special">};</span>
+</pre>
+<p>
+ It is possible to derive the struct <code class="computeroutput"><span class="identifier">unique</span></code>
+ from the type <code class="computeroutput"><span class="identifier">boost</span><span class="special">::</span><span class="identifier">spirit</span><span class="special">::</span><span class="identifier">detail</span><span class="special">::</span><span class="identifier">default_ownership_policy</span></code>. This type implements
+ a minimal sufficient interface for some of the required functions, simplifying
+ the task of writing a new ownership policy.
+ </p>
+<p>
+ This class may implement a function <code class="computeroutput"><span class="identifier">destroy</span><span class="special">()</span></code> being called during destruction of the
+ last copy of a <code class="computeroutput"><span class="identifier">multi_pass</span></code>.
+ This function should be used to free any of the shared data items the policy
+ might have allocated during construction of its <code class="computeroutput"><span class="identifier">shared</span></code>
+ part. Because of the way <code class="computeroutput"><span class="identifier">multi_pass</span></code>
+ is implemented any allocated data members in <code class="computeroutput"><span class="identifier">shared</span></code>
+ should <span class="underline">not</span> be deep copied in a copy
+ constructor of <code class="computeroutput"><span class="identifier">shared</span></code>.
+ </p>
+<a name="spirit.support.multi_pass.checkingpolicy"></a><h5>
+<a name="id1125807"></a>
+ <a class="link" href="multi_pass.html#spirit.support.multi_pass.checkingpolicy">CheckingPolicy</a>
+ </h5>
+<p>
+ The <code class="computeroutput"><span class="identifier">CheckingPolicy</span></code> must have
+ the following interface:
+ </p>
+<pre class="programlisting"><span class="keyword">struct</span> <span class="identifier">checking_policy</span>
+<span class="special">{</span>
+ <span class="keyword">struct</span> <span class="identifier">unique</span>
+ <span class="special">{</span>
+ <span class="comment">// swap is called by multi_pass::swap()
+</span> <span class="keyword">void</span> <span class="identifier">swap</span><span class="special">(</span><span class="identifier">unique</span><span class="special">&amp;);</span>
+
+ <span class="comment">// destroy is called whenever the last copy of a multi_pass is
+</span> <span class="comment">// destructed (ownership_policy::release() returned true)
+</span> <span class="comment">//
+</span> <span class="comment">// mp: is a reference to the whole multi_pass instance
+</span> <span class="keyword">template</span> <span class="special">&lt;</span><span class="keyword">typename</span> <span class="identifier">MultiPass</span><span class="special">&gt;</span>
+ <span class="keyword">static</span> <span class="keyword">void</span> <span class="identifier">destroy</span><span class="special">(</span><span class="identifier">MultiPass</span><span class="special">&amp;</span> <span class="identifier">mp</span><span class="special">);</span>
+
+ <span class="comment">// check is called before the multi_pass is dereferenced or
+</span> <span class="comment">// incremented.
+</span> <span class="comment">//
+</span> <span class="comment">// mp: is a reference to the whole multi_pass instance
+</span> <span class="comment">//
+</span> <span class="comment">// This method is expected to make sure the multi_pass instance is
+</span> <span class="comment">// still valid. If it is invalid an exception should be thrown.
+</span> <span class="keyword">template</span> <span class="special">&lt;</span><span class="keyword">typename</span> <span class="identifier">MultiPass</span><span class="special">&gt;</span>
+ <span class="keyword">static</span> <span class="keyword">void</span> <span class="identifier">check</span><span class="special">(</span><span class="identifier">MultiPass</span> <span class="keyword">const</span><span class="special">&amp;</span> <span class="identifier">mp</span><span class="special">);</span>
+
+ <span class="comment">// clear_queue is called whenever the function
+</span> <span class="comment">// multi_pass::clear_queue is called on this instance
+</span> <span class="comment">//
+</span> <span class="comment">// mp: is a reference to the whole multi_pass instance
+</span> <span class="keyword">template</span> <span class="special">&lt;</span><span class="keyword">typename</span> <span class="identifier">MultiPass</span><span class="special">&gt;</span>
+ <span class="keyword">static</span> <span class="keyword">void</span> <span class="identifier">clear_queue</span><span class="special">(</span><span class="identifier">MultiPass</span><span class="special">&amp;</span> <span class="identifier">mp</span><span class="special">);</span>
+ <span class="special">};</span>
+
+ <span class="keyword">struct</span> <span class="identifier">shared</span> <span class="special">{};</span>
+<span class="special">};</span>
+</pre>
+<p>
+ It is possible to derive the struct <code class="computeroutput"><span class="identifier">unique</span></code>
+ from the type <code class="computeroutput"><span class="identifier">boost</span><span class="special">::</span><span class="identifier">spirit</span><span class="special">::</span><span class="identifier">detail</span><span class="special">::</span><span class="identifier">default_checking_policy</span></code>. This type implements
+ a minimal sufficient interface for some of the required functions, simplifying
+ the task of writing a new checking policy.
+ </p>
+<p>
+ This class may implement a function <code class="computeroutput"><span class="identifier">destroy</span><span class="special">()</span></code> being called during destruction of the
+ last copy of a <code class="computeroutput"><span class="identifier">multi_pass</span></code>.
+ This function should be used to free any of the shared data items the policy
+ might have allocated during construction of its <code class="computeroutput"><span class="identifier">shared</span></code>
+ part. Because of the way <code class="computeroutput"><span class="identifier">multi_pass</span></code>
+ is implemented any allocated data members in <code class="computeroutput"><span class="identifier">shared</span></code>
+ should <span class="underline">not</span> be deep copied in a copy
+ constructor of <code class="computeroutput"><span class="identifier">shared</span></code>.
+ </p>
+<a name="spirit.support.multi_pass.storagepolicy"></a><h5>
+<a name="id1126258"></a>
+ <a class="link" href="multi_pass.html#spirit.support.multi_pass.storagepolicy">StoragePolicy</a>
+ </h5>
+<p>
+ A <code class="computeroutput"><span class="identifier">StoragePolicy</span></code> must have
+ the following interface:
+ </p>
+<pre class="programlisting"><span class="keyword">struct</span> <span class="identifier">storage_policy</span>
+<span class="special">{</span>
+ <span class="comment">// Value is the same type as typename MultiPass::value_type
+</span> <span class="keyword">template</span> <span class="special">&lt;</span><span class="keyword">typename</span> <span class="identifier">Value</span><span class="special">&gt;</span>
+ <span class="keyword">struct</span> <span class="identifier">unique</span>
+ <span class="special">{</span>
+ <span class="comment">// destroy is called whenever the last copy of a multi_pass is
+</span> <span class="comment">// destructed (ownership_policy::release() returned true)
+</span> <span class="comment">//
+</span> <span class="comment">// mp: is a reference to the whole multi_pass instance
+</span> <span class="keyword">template</span> <span class="special">&lt;</span><span class="keyword">typename</span> <span class="identifier">MultiPass</span><span class="special">&gt;</span>
+ <span class="keyword">static</span> <span class="keyword">void</span> <span class="identifier">destroy</span><span class="special">(</span><span class="identifier">MultiPass</span><span class="special">&amp;</span> <span class="identifier">mp</span><span class="special">);</span>
+
+ <span class="comment">// swap is called by multi_pass::swap()
+</span> <span class="keyword">void</span> <span class="identifier">swap</span><span class="special">(</span><span class="identifier">unique</span><span class="special">&amp;);</span>
+
+ <span class="comment">// dereference is called whenever multi_pass::operator*() is invoked
+</span> <span class="comment">//
+</span> <span class="comment">// mp: is a reference to the whole multi_pass instance
+</span> <span class="comment">//
+</span> <span class="comment">// This function is expected to return a reference to the current
+</span> <span class="comment">// character/token.
+</span> <span class="keyword">template</span> <span class="special">&lt;</span><span class="keyword">typename</span> <span class="identifier">MultiPass</span><span class="special">&gt;</span>
+ <span class="keyword">static</span> <span class="keyword">typename</span> <span class="identifier">MultiPass</span><span class="special">::</span><span class="identifier">reference</span> <span class="identifier">dereference</span><span class="special">(</span><span class="identifier">MultiPass</span> <span class="keyword">const</span><span class="special">&amp;</span> <span class="identifier">mp</span><span class="special">);</span>
+
+ <span class="comment">// increment is called whenever multi_pass::operator++ is invoked
+</span> <span class="comment">//
+</span> <span class="comment">// mp: is a reference to the whole multi_pass instance
+</span> <span class="keyword">template</span> <span class="special">&lt;</span><span class="keyword">typename</span> <span class="identifier">MultiPass</span><span class="special">&gt;</span>
+ <span class="keyword">static</span> <span class="keyword">void</span> <span class="identifier">increment</span><span class="special">(</span><span class="identifier">MultiPass</span><span class="special">&amp;</span> <span class="identifier">mp</span><span class="special">);</span>
+
+ <span class="comment">//
+</span> <span class="comment">// mp: is a reference to the whole multi_pass instance
+</span> <span class="keyword">template</span> <span class="special">&lt;</span><span class="keyword">typename</span> <span class="identifier">MultiPass</span><span class="special">&gt;</span>
+ <span class="keyword">static</span> <span class="keyword">void</span> <span class="identifier">clear_queue</span><span class="special">(</span><span class="identifier">MultiPass</span><span class="special">&amp;</span> <span class="identifier">mp</span><span class="special">);</span>
+
+ <span class="comment">// is_eof is called to test whether this instance is a end of input
+</span> <span class="comment">// iterator.
+</span> <span class="comment">//
+</span> <span class="comment">// mp: is a reference to the whole multi_pass instance
+</span> <span class="comment">//
+</span> <span class="comment">// This method is expected to return true if the end of input is
+</span> <span class="comment">// reached.
+</span> <span class="keyword">template</span> <span class="special">&lt;</span><span class="keyword">typename</span> <span class="identifier">MultiPass</span><span class="special">&gt;</span>
+ <span class="keyword">static</span> <span class="keyword">bool</span> <span class="identifier">is_eof</span><span class="special">(</span><span class="identifier">MultiPass</span> <span class="keyword">const</span><span class="special">&amp;</span> <span class="identifier">mp</span><span class="special">);</span>
+
+ <span class="comment">// less_than is called whenever multi_pass::operator==() is invoked
+</span> <span class="comment">//
+</span> <span class="comment">// mp: is a reference to the whole multi_pass instance
+</span> <span class="comment">// rhs: is the multi_pass reference this instance is compared
+</span> <span class="comment">// to
+</span> <span class="comment">//
+</span> <span class="comment">// This function is expected to return true if the current instance
+</span> <span class="comment">// is eual to the right hand side multi_pass instance
+</span> <span class="keyword">template</span> <span class="special">&lt;</span><span class="keyword">typename</span> <span class="identifier">MultiPass</span><span class="special">&gt;</span>
+ <span class="keyword">static</span> <span class="keyword">bool</span> <span class="identifier">equal_to</span><span class="special">(</span><span class="identifier">MultiPass</span> <span class="keyword">const</span><span class="special">&amp;</span> <span class="identifier">mp</span><span class="special">,</span> <span class="identifier">MultiPass</span> <span class="keyword">const</span><span class="special">&amp;</span> <span class="identifier">rhs</span><span class="special">);</span>
+
+ <span class="comment">// less_than is called whenever multi_pass::operator&lt;() is invoked
+</span> <span class="comment">//
+</span> <span class="comment">// mp: is a reference to the whole multi_pass instance
+</span> <span class="comment">// rhs: is the multi_pass reference this instance is compared
+</span> <span class="comment">// to
+</span> <span class="comment">//
+</span> <span class="comment">// This function is expected to return true if the current instance
+</span> <span class="comment">// is less than the right hand side multi_pass instance
+</span> <span class="keyword">template</span> <span class="special">&lt;</span><span class="keyword">typename</span> <span class="identifier">MultiPass</span><span class="special">&gt;</span>
+ <span class="keyword">static</span> <span class="keyword">bool</span> <span class="identifier">less_than</span><span class="special">(</span><span class="identifier">MultiPass</span> <span class="keyword">const</span><span class="special">&amp;</span> <span class="identifier">mp</span><span class="special">,</span> <span class="identifier">MultiPass</span> <span class="keyword">const</span><span class="special">&amp;</span> <span class="identifier">rhs</span><span class="special">);</span>
+ <span class="special">};</span>
+
+ <span class="comment">// Value is the same type as typename MultiPass::value_type
+</span> <span class="keyword">template</span> <span class="special">&lt;</span><span class="keyword">typename</span> <span class="identifier">Value</span><span class="special">&gt;</span>
+ <span class="keyword">struct</span> <span class="identifier">shared</span> <span class="special">{};</span>
+<span class="special">};</span>
+</pre>
+<p>
+ It is possible to derive the struct <code class="computeroutput"><span class="identifier">unique</span></code>
+ from the type <code class="computeroutput"><span class="identifier">boost</span><span class="special">::</span><span class="identifier">spirit</span><span class="special">::</span><span class="identifier">detail</span><span class="special">::</span><span class="identifier">default_storage_policy</span></code>. This type implements
+ a minimal sufficient interface for some of the required functions, simplifying
+ the task of writing a new storage policy.
+ </p>
+<p>
+ This class may implement a function <code class="computeroutput"><span class="identifier">destroy</span><span class="special">()</span></code> being called during destruction of the
+ last copy of a <code class="computeroutput"><span class="identifier">multi_pass</span></code>.
+ This function should be used to free any of the shared data items the policy
+ might have allocated during construction of its <code class="computeroutput"><span class="identifier">shared</span></code>
+ part. Because of the way <code class="computeroutput"><span class="identifier">multi_pass</span></code>
+ is implemented any allocated data members in <code class="computeroutput"><span class="identifier">shared</span></code>
+ should <span class="underline">not</span> be deep copied in a copy
+ constructor of <code class="computeroutput"><span class="identifier">shared</span></code>.
+ </p>
+<p>
+ Generally, a <code class="computeroutput"><span class="identifier">StoragePolicy</span></code>
+ is the trickiest policy to implement. You should study and understand the
+ existing <code class="computeroutput"><span class="identifier">StoragePolicy</span></code> classes
+ before you try and write your own.
+ </p>
+</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 © 2001-2009 Joel
+ de Guzman, Hartmut Kaiser<p>
+ Distributed under the Boost Software License, Version 1.0. (See accompanying
+ file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)
+ </p>
+</div></td>
+</tr></table>
+<hr>
+<div class="spirit-nav">
+<a accesskey="p" href="../support.html"><img src="../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../support.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="../faq.html"><img src="../../../../../../doc/html/images/next.png" alt="Next"></a>
+</div>
+</body>
+</html>

Modified: trunk/libs/spirit/doc/html/spirit/what_s_new.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/what_s_new.html (original)
+++ trunk/libs/spirit/doc/html/spirit/what_s_new.html 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -3,10 +3,10 @@
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <title>What's New</title>
 <link rel="stylesheet" href="../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.0">
 <link rel="home" href="../index.html" title="Spirit 2.1">
 <link rel="up" href="../index.html" title="Spirit 2.1">
-<link rel="previous" href="preface.html" title="Preface">
+<link rel="prev" href="preface.html" title="Preface">
 <link rel="next" href="introduction.html" title="Introduction">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -22,17 +22,14 @@
 <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="introduction.html"><img src="../../../../../doc/html/images/next.png" alt="Next"></a>
 </div>
-<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h2 class="title" style="clear: both">
-<a name="spirit.what_s_new"></a>What's New
-</h2></div></div>
-<div></div>
-</div>
-<a name="spirit.what_s_new.spirit_classic"></a><h3>
-<a name="id353457"></a>
- Spirit Classic
- </h3>
+<div class="section" title="What's New">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="spirit.what_s_new"></a><a class="link" href="what_s_new.html" title="What's New">What's New</a>
+</h2></div></div></div>
+<a name="spirit.what_s_new.spirit_classic"></a><h4>
+<a name="id1018312"></a>
+ <a class="link" href="what_s_new.html#spirit.what_s_new.spirit_classic">Spirit Classic</a>
+ </h4>
 <p>
       The Spirit V1.8.x code base has been integrated with Spirit V2. It is now called
       <span class="emphasis"><em>Spirit.Classic</em></span>. Since the directory structure has changed
@@ -56,11 +53,11 @@
 </pre>
 <p>
       To avoid namespace conflicts with the new Spirit V2 library we moved Spirit
- Classic into the namespace <tt class="computeroutput"><span class="identifier">boost</span><span class="special">::</span><span class="identifier">spirit</span><span class="special">::</span><span class="identifier">classic</span></tt>.
- All references to the former namespace <tt class="computeroutput"><span class="identifier">boost</span><span class="special">::</span><span class="identifier">spirit</span></tt>
+ Classic into the namespace <code class="computeroutput"><span class="identifier">boost</span><span class="special">::</span><span class="identifier">spirit</span><span class="special">::</span><span class="identifier">classic</span></code>.
+ All references to the former namespace <code class="computeroutput"><span class="identifier">boost</span><span class="special">::</span><span class="identifier">spirit</span></code>
       need to be adjusted as soon as the header names are corrected as described
- above. As an alternative you can define the preprocessor constant <tt class="computeroutput"><span class="identifier">BOOST_SPIRIT_USE_OLD_NAMESPACE</span></tt>, which will
- force the Spirit Classic code to be in the namespace <tt class="computeroutput"><span class="identifier">boost</span><span class="special">::</span><span class="identifier">spirit</span></tt>
+ above. As an alternative you can define the preprocessor constant <code class="computeroutput"><span class="identifier">BOOST_SPIRIT_USE_OLD_NAMESPACE</span></code>, which will
+ force the Spirit Classic code to be in the namespace <code class="computeroutput"><span class="identifier">boost</span><span class="special">::</span><span class="identifier">spirit</span></code>
       as before. This is not recommended, though, as it may result in naming clashes.
     </p>
 <p>
@@ -68,104 +65,104 @@
       deprecated include files are being used. This ensures full backwards compatibility
       for existing applications.
     </p>
-<a name="spirit.what_s_new.spirit_v2_1"></a><h3>
-<a name="id409221"></a>
- Spirit V2.1
- </h3>
-<a name="spirit.what_s_new.what_s_changed_in__emphasis_spirit_qi__emphasis__and__emphasis_spirit_karma__emphasis__from_v2_0_to_2_x"></a><h3>
-<a name="id409245"></a>
- <a href="what_s_new.html#spirit.what_s_new.what_s_changed_in__emphasis_spirit_qi__emphasis__and__emphasis_spirit_karma__emphasis__from_v2_0_to_2_x">What's
+<a name="spirit.what_s_new.spirit_v2_1"></a><h4>
+<a name="id1018503"></a>
+ <a class="link" href="what_s_new.html#spirit.what_s_new.spirit_v2_1">Spirit V2.1</a>
+ </h4>
+<a name="spirit.what_s_new.what_s_changed_in__emphasis_spirit_qi__emphasis__and__emphasis_spirit_karma__emphasis__from_v2_0_to_2_x"></a><h4>
+<a name="id1018516"></a>
+ <a class="link" href="what_s_new.html#spirit.what_s_new.what_s_changed_in__emphasis_spirit_qi__emphasis__and__emphasis_spirit_karma__emphasis__from_v2_0_to_2_x">What's
       changed in <span class="emphasis"><em>Spirit.Qi</em></span> and <span class="emphasis"><em>Spirit.Karma</em></span>
       from V2.0 to 2.x</a>
- </h3>
-<div class="itemizedlist"><ul type="disc">
-<li>
+ </h4>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem">
 <a href="http://spirit.sourceforge.net" target="_top">Spirit</a> is now based on
         the newest version of Boost.Proto
 </li>
-<li>
-<tt class="computeroutput"><span class="identifier">qi</span><span class="special">::</span><span class="identifier">phrase_parse</span></tt>, <tt class="computeroutput"><span class="identifier">qi</span><span class="special">::</span><span class="identifier">phrase_format</span></tt>
+<li class="listitem">
+<code class="computeroutput"><span class="identifier">qi</span><span class="special">::</span><span class="identifier">phrase_parse</span></code>, <code class="computeroutput"><span class="identifier">qi</span><span class="special">::</span><span class="identifier">phrase_format</span></code>
         now post-skip by default.
       </li>
-<li>
-<tt class="computeroutput"><span class="identifier">karma</span><span class="special">::</span><span class="identifier">generate_delimited</span></tt> and <tt class="computeroutput"><span class="identifier">karma</span><span class="special">::</span><span class="identifier">format_delimited</span></tt>
+<li class="listitem">
+<code class="computeroutput"><span class="identifier">karma</span><span class="special">::</span><span class="identifier">generate_delimited</span></code> and <code class="computeroutput"><span class="identifier">karma</span><span class="special">::</span><span class="identifier">format_delimited</span></code>
         now don't do pre- delimiting by default.
       </li>
-<li>
- Changed parameter sequence of <tt class="computeroutput"><span class="identifier">qi</span><span class="special">::</span><span class="identifier">phrase_parse</span></tt>,
- <tt class="computeroutput"><span class="identifier">qi</span><span class="special">::</span><span class="identifier">phrase_match</span></tt>, <tt class="computeroutput"><span class="identifier">karma</span><span class="special">::</span><span class="identifier">generate_delimited</span></tt>,
- and <tt class="computeroutput"><span class="identifier">match_delimited</span></tt>. The
+<li class="listitem">
+ Changed parameter sequence of <code class="computeroutput"><span class="identifier">qi</span><span class="special">::</span><span class="identifier">phrase_parse</span></code>,
+ <code class="computeroutput"><span class="identifier">qi</span><span class="special">::</span><span class="identifier">phrase_match</span></code>, <code class="computeroutput"><span class="identifier">karma</span><span class="special">::</span><span class="identifier">generate_delimited</span></code>,
+ and <code class="computeroutput"><span class="identifier">match_delimited</span></code>. The
         attribute is now always the last parameter.
       </li>
-<li>
+<li class="listitem">
         Added new overloads of those functions allowing to explicitely specify the
         post-skipping and pre-delimiting behavior.
       </li>
-<li>
+<li class="listitem">
         Added multi attribute API functions
       </li>
-<li>
- Removed <tt class="computeroutput"><span class="identifier">grammar_def</span><span class="special">&lt;&gt;</span></tt>
+<li class="listitem">
+ Removed <code class="computeroutput"><span class="identifier">grammar_def</span><span class="special">&lt;&gt;</span></code>
 </li>
-<li>
- Removed functions <tt class="computeroutput"><span class="identifier">make_parser</span><span class="special">()</span></tt> and <tt class="computeroutput"><span class="identifier">make_generator</span><span class="special">()</span></tt>
+<li class="listitem">
+ Removed functions <code class="computeroutput"><span class="identifier">make_parser</span><span class="special">()</span></code> and <code class="computeroutput"><span class="identifier">make_generator</span><span class="special">()</span></code>
 </li>
-<li>
- Removed <tt class="computeroutput"><span class="identifier">qi</span><span class="special">::</span><span class="identifier">none</span></tt> and <tt class="computeroutput"><span class="identifier">karma</span><span class="special">::</span><span class="identifier">none</span></tt>
+<li class="listitem">
+ Removed <code class="computeroutput"><span class="identifier">qi</span><span class="special">::</span><span class="identifier">none</span></code> and <code class="computeroutput"><span class="identifier">karma</span><span class="special">::</span><span class="identifier">none</span></code>
 </li>
-<li>
+<li class="listitem">
         Sequences and lists now accept a standard container as their attribute
       </li>
-<li>
+<li class="listitem">
         The string placeholder terminal now can take other strings as its parameter
         (i.e. std::string)
       </li>
-<li>
+<li class="listitem">
         All terminals taking literals now accept a (lazy) function object as well
       </li>
-<li>
- All placeholders for terminals and directives (such as <tt class="computeroutput"><span class="identifier">int_</span></tt>,
- <tt class="computeroutput"><span class="identifier">double_</span></tt>, <tt class="computeroutput"><span class="identifier">verbatim</span></tt>,
- etc.) were previously defined in the namespace <tt class="computeroutput"><span class="identifier">boost</span><span class="special">::</span><span class="identifier">spirit</span></tt>
- only. Now these are additionally imported into the namespaces <tt class="computeroutput"><span class="identifier">spirit</span><span class="special">::</span><span class="identifier">qi</span></tt>, <tt class="computeroutput"><span class="identifier">spirit</span><span class="special">::</span><span class="identifier">karma</span></tt>,
- and <tt class="computeroutput"><span class="identifier">spirit</span><span class="special">::</span><span class="identifier">lex</span></tt> (if they are supported by the corresponding
+<li class="listitem">
+ All placeholders for terminals and directives (such as <code class="computeroutput"><span class="identifier">int_</span></code>,
+ <code class="computeroutput"><span class="identifier">double_</span></code>, <code class="computeroutput"><span class="identifier">verbatim</span></code>,
+ etc.) were previously defined in the namespace <code class="computeroutput"><span class="identifier">boost</span><span class="special">::</span><span class="identifier">spirit</span></code>
+ only. Now these are additionally imported into the namespaces <code class="computeroutput"><span class="identifier">spirit</span><span class="special">::</span><span class="identifier">qi</span></code>, <code class="computeroutput"><span class="identifier">spirit</span><span class="special">::</span><span class="identifier">karma</span></code>,
+ and <code class="computeroutput"><span class="identifier">spirit</span><span class="special">::</span><span class="identifier">lex</span></code> (if they are supported by the corresponding
         sub-library).
       </li>
-<li>
- The terminal placeholders <tt class="computeroutput"><span class="identifier">char_</span></tt>
- and <tt class="computeroutput"><span class="identifier">string</span></tt> are not defined
- in the namespace <tt class="computeroutput"><span class="identifier">boost</span><span class="special">::</span><span class="identifier">spirit</span></tt> anymore as they have been moved
+<li class="listitem">
+ The terminal placeholders <code class="computeroutput"><span class="identifier">char_</span></code>
+ and <code class="computeroutput"><span class="identifier">string</span></code> are not defined
+ in the namespace <code class="computeroutput"><span class="identifier">boost</span><span class="special">::</span><span class="identifier">spirit</span></code> anymore as they have been moved
         to the character set namespaces, allowing to do proper character set handling
- based on the used namespace (as <tt class="computeroutput"><span class="identifier">spirit</span><span class="special">::</span><span class="identifier">ascii</span></tt>,
+ based on the used namespace (as <code class="computeroutput"><span class="identifier">spirit</span><span class="special">::</span><span class="identifier">ascii</span></code>,
         etc.)
       </li>
-<li>
- The <tt class="computeroutput"><span class="identifier">uint</span></tt>, <tt class="computeroutput"><span class="identifier">ushort</span></tt>,
- <tt class="computeroutput"><span class="identifier">ulong</span></tt>, and <tt class="computeroutput"><span class="identifier">byte</span></tt> terminal placeholders have been renamed
- to <tt class="computeroutput"><span class="identifier">uint_</span></tt>, <tt class="computeroutput"><span class="identifier">ushort_</span></tt>,
- <tt class="computeroutput"><span class="identifier">ulong_</span></tt>, and <tt class="computeroutput"><span class="identifier">byte_</span></tt>.
- </li>
-<li>
-<tt class="computeroutput"><span class="identifier">qi</span><span class="special">::</span><span class="identifier">skip</span><span class="special">[]</span></tt>
- now re-enables outer skipper if used inside <tt class="computeroutput"><span class="identifier">lexeme</span><span class="special">[]</span></tt>
+<li class="listitem">
+ The <code class="computeroutput"><span class="identifier">uint</span></code>, <code class="computeroutput"><span class="identifier">ushort</span></code>,
+ <code class="computeroutput"><span class="identifier">ulong</span></code>, and <code class="computeroutput"><span class="identifier">byte</span></code> terminal placeholders have been renamed
+ to <code class="computeroutput"><span class="identifier">uint_</span></code>, <code class="computeroutput"><span class="identifier">ushort_</span></code>,
+ <code class="computeroutput"><span class="identifier">ulong_</span></code>, and <code class="computeroutput"><span class="identifier">byte_</span></code>.
+ </li>
+<li class="listitem">
+<code class="computeroutput"><span class="identifier">qi</span><span class="special">::</span><span class="identifier">skip</span><span class="special">[]</span></code>
+ now re-enables outer skipper if used inside <code class="computeroutput"><span class="identifier">lexeme</span><span class="special">[]</span></code>
 </li>
-<li>
- Added <tt class="computeroutput"><span class="identifier">karma</span><span class="special">::</span><span class="identifier">maxwidth</span><span class="special">[]</span></tt>
+<li class="listitem">
+ Added <code class="computeroutput"><span class="identifier">karma</span><span class="special">::</span><span class="identifier">maxwidth</span><span class="special">[]</span></code>
         directive
       </li>
-<li>
-<tt class="computeroutput"><span class="identifier">karma</span><span class="special">::</span><span class="identifier">delimit</span><span class="special">[]</span></tt>
- now re-enables outer delimiter if used inside <tt class="computeroutput"><span class="identifier">verbatim</span><span class="special">[]</span></tt>
+<li class="listitem">
+<code class="computeroutput"><span class="identifier">karma</span><span class="special">::</span><span class="identifier">delimit</span><span class="special">[]</span></code>
+ now re-enables outer delimiter if used inside <code class="computeroutput"><span class="identifier">verbatim</span><span class="special">[]</span></code>
 </li>
-<li>
- karma: added and-predicate (<tt class="computeroutput"><span class="keyword">operator</span><span class="special">&amp;()</span></tt>) and not-predicate (<tt class="computeroutput"><span class="keyword">operator</span><span class="special">!()</span></tt>)
+<li class="listitem">
+ karma: added and-predicate (<code class="computeroutput"><span class="keyword">operator</span><span class="special">&amp;()</span></code>) and not-predicate (<code class="computeroutput"><span class="keyword">operator</span><span class="special">!()</span></code>)
       </li>
 </ul></div>
-<a name="spirit.what_s_new.what_s_changed_in__emphasis_spirit_lex__emphasis__from_v2_0_to_2_x"></a><h3>
-<a name="id409979"></a>
- <a href="what_s_new.html#spirit.what_s_new.what_s_changed_in__emphasis_spirit_lex__emphasis__from_v2_0_to_2_x">What's
+<a name="spirit.what_s_new.what_s_changed_in__emphasis_spirit_lex__emphasis__from_v2_0_to_2_x"></a><h4>
+<a name="id1019068"></a>
+ <a class="link" href="what_s_new.html#spirit.what_s_new.what_s_changed_in__emphasis_spirit_lex__emphasis__from_v2_0_to_2_x">What's
       changed in <span class="emphasis"><em>Spirit.Lex</em></span> from V2.0 to 2.x</a>
- </h3>
+ </h4>
 <p>
       Here is a list of changes in <span class="emphasis"><em>Spirit.Lex</em></span> since version
       2.0. <span class="emphasis"><em>Spirit.Lex</em></span> 2.x is a complete rewrite of the original
@@ -173,15 +170,15 @@
       library it is usable either standalone or in conjunction with the other parts.
       <span class="emphasis"><em>Spirit.Lex</em></span> now uses the infrastructure provided by Spirit version 2.1.
     </p>
-<div class="itemizedlist"><ul type="disc">
-<li>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem">
         The lex::lexer_def class has been renamed to lex::lexer, while the original
         class lex::lexer does not exist anymore. This simplifies the creation of
         lexers.
       </li>
-<li>
- The lex::lexer class does not have the function <tt class="computeroutput"><span class="identifier">def</span><span class="special">(</span><span class="identifier">Self</span><span class="special">&amp;</span>
- <span class="identifier">self</span><span class="special">)</span></tt>
+<li class="listitem">
+ The lex::lexer class does not have the function <code class="computeroutput"><span class="identifier">def</span><span class="special">(</span><span class="identifier">Self</span><span class="special">&amp;</span>
+ <span class="identifier">self</span><span class="special">)</span></code>
         anymore, token definitions can be added to the lexer at any time, usually
         in the constructor of the user defined lexer class:
 <pre class="programlisting"><span class="keyword">template</span> <span class="special">&lt;</span><span class="keyword">typename</span> <span class="identifier">Lexer</span><span class="special">&gt;</span>
@@ -195,75 +192,72 @@
 <span class="special">};</span>
 </pre>
 </li>
-<li>
+<li class="listitem">
         The new lexer class now can be directly used, their is no need anymore to
- wrap it using the <tt class="computeroutput"><span class="identifier">make_lexer</span><span class="special">()</span></tt> template as before. Therefore the function
- <tt class="computeroutput"><span class="identifier">make_lexer</span><span class="special">()</span></tt>
+ wrap it using the <code class="computeroutput"><span class="identifier">make_lexer</span><span class="special">()</span></code> template as before. Therefore the function
+ <code class="computeroutput"><span class="identifier">make_lexer</span><span class="special">()</span></code>
         has been removed.
       </li>
-<li>
- The <tt class="computeroutput"><span class="identifier">lex</span><span class="special">::</span><span class="identifier">tokenize_and_parse</span><span class="special">()</span></tt>
- and <tt class="computeroutput"><span class="identifier">lex</span><span class="special">::</span><span class="identifier">tokenize_and_phrase_parse</span><span class="special">()</span></tt>
+<li class="listitem">
+ The <code class="computeroutput"><span class="identifier">lex</span><span class="special">::</span><span class="identifier">tokenize_and_parse</span><span class="special">()</span></code>
+ and <code class="computeroutput"><span class="identifier">lex</span><span class="special">::</span><span class="identifier">tokenize_and_phrase_parse</span><span class="special">()</span></code>
         functions have been changed to match the parameter sequence as implemented
- by the <tt class="computeroutput"><span class="identifier">qi</span><span class="special">::</span><span class="identifier">parse</span><span class="special">()</span></tt>
- and <tt class="computeroutput"><span class="identifier">qi</span><span class="special">::</span><span class="identifier">phrase_parse</span><span class="special">()</span></tt>
+ by the <code class="computeroutput"><span class="identifier">qi</span><span class="special">::</span><span class="identifier">parse</span><span class="special">()</span></code>
+ and <code class="computeroutput"><span class="identifier">qi</span><span class="special">::</span><span class="identifier">phrase_parse</span><span class="special">()</span></code>
         functions. Both take a possibly arbitrary number of attribute arguments as
         its last parameters (well, the number of attributes is limited by the macro
- <tt class="computeroutput"><span class="identifier">SPIRIT_ARGUMENTS_LIMIT</span></tt>, which
- defaults to <tt class="computeroutput"><span class="identifier">PHOENIX_LIMIT</span></tt>).
+ <code class="computeroutput"><span class="identifier">SPIRIT_ARGUMENTS_LIMIT</span></code>, which
+ defaults to <code class="computeroutput"><span class="identifier">PHOENIX_LIMIT</span></code>).
       </li>
-<li>
- The <tt class="computeroutput"><span class="identifier">lex</span><span class="special">::</span><span class="identifier">lexertl_lexer</span></tt>, and <tt class="computeroutput"><span class="identifier">lex</span><span class="special">::</span><span class="identifier">lexertl_token</span></tt>
- classes have been moved to the <tt class="computeroutput"><span class="identifier">lex</span><span class="special">::</span><span class="identifier">lexertl</span></tt>
- namespace and the names have been changed to <tt class="computeroutput"><span class="identifier">lex</span><span class="special">::</span><span class="identifier">lexertl</span><span class="special">::</span><span class="identifier">lexer</span></tt>,
- <tt class="computeroutput"><span class="identifier">lex</span><span class="special">::</span><span class="identifier">lexertl</span><span class="special">::</span><span class="identifier">token</span></tt> (the same applies to the <tt class="computeroutput"><span class="identifier">lex</span><span class="special">::</span><span class="identifier">lexert_actor_lexer</span></tt>,
- and the <tt class="computeroutput"><span class="identifier">static_lexertl_</span><span class="special">*</span></tt>
+<li class="listitem">
+ The <code class="computeroutput"><span class="identifier">lex</span><span class="special">::</span><span class="identifier">lexertl_lexer</span></code>, and <code class="computeroutput"><span class="identifier">lex</span><span class="special">::</span><span class="identifier">lexertl_token</span></code>
+ classes have been moved to the <code class="computeroutput"><span class="identifier">lex</span><span class="special">::</span><span class="identifier">lexertl</span></code>
+ namespace and the names have been changed to <code class="computeroutput"><span class="identifier">lex</span><span class="special">::</span><span class="identifier">lexertl</span><span class="special">::</span><span class="identifier">lexer</span></code>,
+ <code class="computeroutput"><span class="identifier">lex</span><span class="special">::</span><span class="identifier">lexertl</span><span class="special">::</span><span class="identifier">token</span></code> (the same applies to the <code class="computeroutput"><span class="identifier">lex</span><span class="special">::</span><span class="identifier">lexert_actor_lexer</span></code>,
+ and the <code class="computeroutput"><span class="identifier">static_lexertl_</span><span class="special">*</span></code>
         family of types).
       </li>
-<li>
- The class <tt class="computeroutput"><span class="identifier">lex</span><span class="special">::</span><span class="identifier">lexertl_token_set</span></tt> has been removed alltogether
+<li class="listitem">
+ The class <code class="computeroutput"><span class="identifier">lex</span><span class="special">::</span><span class="identifier">lexertl_token_set</span></code> has been removed alltogether
         as its complete functionality is available from the lexer class.
       </li>
-<li>
+<li class="listitem">
         The <span class="emphasis"><em>Spirit.Lex</em></span> library has been updated to use the newest
         version of Ben Hansons Lexertl
         lexer construction library (Boost review pending).
       </li>
-<li>
- The <tt class="computeroutput"><span class="identifier">lex</span><span class="special">::</span><span class="identifier">lexer</span><span class="special">&lt;</span><span class="identifier">Lexer</span><span class="special">&gt;</span></tt>
- template constructor now takes an optional parameter specifying the <tt class="computeroutput"><span class="identifier">match_flags</span></tt> to be used for table generation.
+<li class="listitem">
+ The <code class="computeroutput"><span class="identifier">lex</span><span class="special">::</span><span class="identifier">lexer</span><span class="special">&lt;</span><span class="identifier">Lexer</span><span class="special">&gt;</span></code>
+ template constructor now takes an optional parameter specifying the <code class="computeroutput"><span class="identifier">match_flags</span></code> to be used for table generation.
         Currently, there are the following flags available:
 <pre class="programlisting"><span class="identifier">match_flags</span><span class="special">::</span><span class="identifier">match_default</span><span class="special">,</span> <span class="comment">// no flags
 </span><span class="identifier">match_flags</span><span class="special">::</span><span class="identifier">match_not_dot_newline</span><span class="special">,</span> <span class="comment">// the regex '.' doesn't match newlines
 </span><span class="identifier">match_flags</span><span class="special">::</span><span class="identifier">match_icase</span> <span class="comment">// all matching operations are case insensitive
 </span></pre>
- If no parameter is passed to the constructor, <tt class="computeroutput"><span class="identifier">match_flags</span><span class="special">::</span><span class="identifier">match_default</span></tt>
- is used, i.e. the <tt class="computeroutput"><span class="special">.</span></tt> matches
+ If no parameter is passed to the constructor, <code class="computeroutput"><span class="identifier">match_flags</span><span class="special">::</span><span class="identifier">match_default</span></code>
+ is used, i.e. the <code class="computeroutput"><span class="special">.</span></code> matches
         newlines and matching is case sensitive.
       </li>
-<li>
- The <tt class="computeroutput"><span class="identifier">char_</span><span class="special">()</span></tt>
- and <tt class="computeroutput"><span class="identifier">string</span><span class="special">()</span></tt>
+<li class="listitem">
+ The <code class="computeroutput"><span class="identifier">char_</span><span class="special">()</span></code>
+ and <code class="computeroutput"><span class="identifier">string</span><span class="special">()</span></code>
         placeholders can now be used for token definitions as a replacement for
- <tt class="computeroutput"><span class="identifier">token_def</span></tt>, although it is
+ <code class="computeroutput"><span class="identifier">token_def</span></code>, although it is
         still possible to use the latter.
       </li>
-<li>
- Lexer semantic actions now have to conform to a changed interface (see <a href="lex/abstracts/lexer_semantic_actions.html" title=" Lexer
- Semantic Actions">Lexer Semantic Actions</a>
+<li class="listitem">
+ Lexer semantic actions now have to conform to a changed interface (see <a class="link" href="lex/abstracts/lexer_semantic_actions.html" title="Lexer Semantic Actions">Lexer Semantic Actions</a>
         for details).
       </li>
-<li>
+<li class="listitem">
         Added placeholder symbols usable from the inside of lexer semantic actions
         while using Phoenix: _start, _end, _eoi, _state, _value, and _pass (see
- <a href="lex/abstracts/lexer_semantic_actions.html" title=" Lexer
- Semantic Actions">Lexer Semantic
+ <a class="link" href="lex/abstracts/lexer_semantic_actions.html" title="Lexer Semantic Actions">Lexer Semantic
         Actions</a> for more details).
       </li>
-<li>
+<li class="listitem">
         Added (lazy) support functions usable from the inside of lexer semantic actions
- while using Phoenix: <tt class="computeroutput"><span class="identifier">lex</span><span class="special">::</span><span class="identifier">more</span><span class="special">()</span></tt>, <tt class="computeroutput"><span class="identifier">lex</span><span class="special">::</span><span class="identifier">less</span><span class="special">()</span></tt>, and <tt class="computeroutput"><span class="identifier">lex</span><span class="special">::</span><span class="identifier">lookahead</span><span class="special">()</span></tt> (see <a href="lex/abstracts/lexer_semantic_actions.html" title=" Lexer
- Semantic Actions">Lexer
+ while using Phoenix: <code class="computeroutput"><span class="identifier">lex</span><span class="special">::</span><span class="identifier">more</span><span class="special">()</span></code>, <code class="computeroutput"><span class="identifier">lex</span><span class="special">::</span><span class="identifier">less</span><span class="special">()</span></code>, and <code class="computeroutput"><span class="identifier">lex</span><span class="special">::</span><span class="identifier">lookahead</span><span class="special">()</span></code> (see <a class="link" href="lex/abstracts/lexer_semantic_actions.html" title="Lexer Semantic Actions">Lexer
         Semantic Actions</a> for more details).
       </li>
 </ul></div>

Modified: trunk/libs/spirit/doc/lex/lexer_tutorials.qbk
==============================================================================
--- trunk/libs/spirit/doc/lex/lexer_tutorials.qbk (original)
+++ trunk/libs/spirit/doc/lex/lexer_tutorials.qbk 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -53,7 +53,7 @@
 introduce the __lex__ library while building two standalone applications, not
 being connected to or depending on any other part of __spirit__. The section
 __sec_lex_quickstart_3__ demonstrates how to use a lexer in conjunction with a
-parser (where certainly the parser is built using __qi__).
+parser (where obviously the parser is built using __qi__).
 
 [endsect]
 

Modified: trunk/libs/spirit/doc/qi/string.qbk
==============================================================================
--- trunk/libs/spirit/doc/qi/string.qbk (original)
+++ trunk/libs/spirit/doc/qi/string.qbk 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -248,4 +248,3 @@
 
 [endsect] [/ symbols]
 
-[endsect]

Modified: trunk/libs/spirit/doc/spirit2.qbk
==============================================================================
--- trunk/libs/spirit/doc/spirit2.qbk (original)
+++ trunk/libs/spirit/doc/spirit2.qbk 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -194,6 +194,7 @@
 [include qi.qbk]
 [include karma.qbk]
 [include lex.qbk]
+[include support.qbk]
 [include faq.qbk]
 [include notes.qbk]
 [/include rationale.qbk]

Added: trunk/libs/spirit/doc/support.qbk
==============================================================================
--- (empty file)
+++ trunk/libs/spirit/doc/support.qbk 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -0,0 +1,13 @@
+[/==============================================================================
+ Copyright (C) 2001-2009 Joel de Guzman
+ Copyright (C) 2001-2009 Hartmut Kaiser
+
+ 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)
+===============================================================================/]
+
+[section:support Supporting libraries]
+
+[include support/multi_pass.qbk]
+
+[endsect]

Added: trunk/libs/spirit/doc/support/multi_pass.qbk
==============================================================================
--- (empty file)
+++ trunk/libs/spirit/doc/support/multi_pass.qbk 2009-07-11 23:35:29 EDT (Sat, 11 Jul 2009)
@@ -0,0 +1,649 @@
+[/==============================================================================
+ Copyright (C) 2001-2009 Hartmut Kaiser
+ Copyright (C) 2001-2009 Joel de Guzman
+ Copyright (C) 2001-2002 Daniel C. Nuffer
+
+ 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)
+===============================================================================/]
+
+[section:multi_pass The multi pass iterator]
+
+Backtracking in __qi__ requires the use of the following types of iterator:
+forward, bidirectional, or random access. Because of backtracking, input
+iterators cannot be used. Therefore, the standard library classes
+`std::istreambuf_iterator` and `std::istream_iterator`, that fall under the
+category of input iterators, cannot be used. Another input iterator that is of
+interest is one that wraps a lexer, such as LEX.
+
+[note In general, __qi__ generates recursive descent parser which require
+ backtracking parsers by design. For this reason we need to provide at
+ least forward iterators to any of __qi__'s API functions. This is not an
+ absolute requirement though. In the future, we shall see more
+ deterministic parsers that require no more than 1 character (token) of
+ lookahead. Such parsers allow us to use input iterators such as the
+ `std::istream_iterator` as is. ]
+
+Backtracking can be implemented only if we are allowed to save an iterator
+position, i.e. making a copy of the current iterator. Unfortunately, with an
+input iterator, there is no way to do so, and thus input iterators will not
+work with backtracking in __qi__. One solution to this problem is to simply
+load all the data to be parsed into a container, such as a vector or deque,
+and then pass the begin and end of the container to __qi__. This method can be
+too memory intensive for certain applications, which is why the `multi_pass`
+iterator was created.
+
+[heading Using the multi_pass]
+
+The `multi_pass` iterator will convert any input iterator into a forward
+iterator suitable for use with __qi__. `multi_pass` will buffer data when
+needed and will discard the buffer when its contents is not needed anymore.
+This happens either if only one copy of the iterator exists or if no
+backtracking can occur.
+
+A grammar must be designed with care if the `multi_pass` iterator is used.
+Any rule that may need to backtrack, such as one that contains an alternative,
+will cause data to be buffered. The rules that are optimal to use are sequence
+and repetition. Sequences of the form `a >> b` will not buffer data at all.
+Any rule that repeats, such as kleene_star (`*a`) or positive such as (`+a`),
+will only buffer the data for the current repetition.
+
+In typical grammars, ambiguity and therefore lookahead is often localized. In
+fact, many well designed languages are fully deterministic and require no
+lookahead at all. Peeking at the first character from the input will
+immediately determine the alternative branch to take. Yet, even with highly
+ambiguous grammars, alternatives are often of the form `*(a | b | c | d)`.
+The input iterator moves on and is never stuck at the beginning. Let's look at
+a Pascal snippet for example:
+
+ program =
+ programHeading >> block >> '.'
+ ;
+
+ block =
+ *( labelDeclarationPart
+ | constantDefinitionPart
+ | typeDefinitionPart
+ | variableDeclarationPart
+ | procedureAndFunctionDeclarationPart
+ )
+ >> statementPart
+ ;
+
+Notice the alternatives inside the Kleene star in the rule block . The rule
+gobbles the input in a linear manner and throws away the past history with each
+iteration. As this is fully deterministic LL(1) grammar, each failed
+alternative only has to peek 1 character (token). The alternative that consumes
+more than 1 character (token) is definitely a winner. After which, the Kleene
+star moves on to the next.
+
+Now, after the lecture on the features to be careful with when using
+`multi_pass`, you may think that `multi_pass` is way too restrictive to use.
+That's not the case. If your grammar is deterministic, you can make use of
+the `flush_multi_pass` pseudo parser in your grammar to ensure that data is not
+buffered when unnecessary (`flush_multi_pass` is available from the __qi__
+parser repository).
+
+Here we present a minimal example showing a minimal use case. The `multi_pass`
+iterator is highly configurable, but the default policies have been chosen so
+that its easily usable with input iterators such as `std::istreambuf_iterator`.
+For the complete source code of this example please refer to
+[@../../example/support/multi_pass.cpp multi_pass.cpp].
+
+[import ../../example/support/multi_pass.cpp]
+[tutorial_multi_pass]
+
+[heading Using the flush_multi_pass parser]
+
+The __spirit__ repository contains the `flush_multi_pass` parser component.
+This is usable in conjunction with the `multi_pass` iterator to minimize the
+buffering. It allows to insert explicit synchronization points into your
+grammar where it is safe to clear any stored input as it is ensured that no
+backtracking can occur at this point anymore.
+
+When the `flush_multi_pass` parser is used with `multi_pass`, it will call
+`multi_pass::clear_queue()`. This will cause any buffered data to be erased.
+This also will invalidate all other copies of multi_pass and they should not
+be used. If they are, an `boost::illegal_backtracking` exception will be
+thrown.
+
+[heading The multi_pass Policies]
+
+The `multi_pass` iterator is a templated class configurable using policies.
+The description of `multi_pass` above is how it was originally implemented
+(before it used policies), and is the default configuration now. But,
+`multi_pass` is capable of much more. Because of the open-ended nature of
+policies, you can write your own policy to make `multi_pass` behave in a way
+that we never before imagined.
+
+The multi_pass class has two template parameters:
+
+[variablelist The multi_pass template parameters
+ [[Input] [The type multi_pass uses to acquire it's input. This is
+ typically an input iterator, or functor.]]
+ [[Policies] [The combined policies to use to create an instance of a
+ multi_pass iterator. This combined policy type is described
+ below]]
+]
+
+It is possible to implement all of the required functionality of the combinded
+policy in a single class. But it has shown to be more convenient to split this
+into four different groups of functions, i.e. four separate, but well
+coordinated policies. For this reason the `multi_pass` framework
+implements a template `iterator_policies::default_policy` allowing to combine
+several different policies, each implementing one of the functionality groups:
+
+[table Policies needed for default_policy template
+ [[Template Parameter] [Description]]
+ [[`OwnershipPolicy`] [This policy determines how `multi_pass` deals with
+ it's shared components.]]
+ [[`CheckingPolicy`] [This policy determines how checking for invalid
+ iterators is done.]]
+ [[`InputPolicy`] [A class that defines how `multi_pass` acquires its
+ input. The `InputPolicy` is parameterized by the
+ `Input` template parameter to the `multi_pass`.]]
+ [[`StoragePolicy`] [The buffering scheme used by `multi_pass` is
+ determined and managed by the StoragePolicy.]]
+]
+
+The `multi_pass` framework contains several predefined policy implementations
+for each of the policy types as described above. First we will describe those
+predefined types. Afterwards we will give some guidelines how you can write
+your own policy implementations.
+
+[heading Predefined policies]
+
+All predefined `multi_pass` policies are defined in the namespace
+`boost::spirit::iterator_policies`.
+
+[table Predefined InputPolicy classes
+ [[Class name] [Description]]
+ [[`input_iterator`] [This policy directs `multi_pass` to read from an
+ input iterator of type `Input`.]]
+ [[`lex_input`] [This policy obtains it's input by calling yylex(),
+ which would typically be provided by a scanner
+ generated by __flex__. If you use this policy your code
+ must link against a __flex__ generated scanner.]]
+ [[`functor_input`] [This input policy obtains it's data by calling a
+ functor of type `Input`. The functor must meet
+ certain requirements. It must have a typedef called
+ `result_type` which should be the type returned
+ from `operator()`. Also, since an input policy needs
+ a way to determine when the end of input has been
+ reached, the functor must contain a static variable
+ named `eof` which is comparable to a variable of
+ `result_type`.]]
+ [[`split_functor_input`][This is essentially the same as the `functor_input`
+ policy except that the (user supplied) funtion
+ object exposes separate `unique` and `shared` sub
+ classes, allowing to integrate the functors /unique/
+ data members with the `multi_pass` data items held
+ by each instance and its /shared/ data members will
+ be integrated with the `multi_pass` members shared
+ by all copies.]]
+]
+
+[table Predefined OwnershipPolicy classes
+ [[Class name] [Description]]
+ [[`ref_counted`] [This class uses a reference counting scheme.
+ The `multi_pass` will delete it's shared components
+ when the count reaches zero.]]
+ [[`first_owner`] [When this policy is used, the first `multi_pass`
+ created will be the one that deletes the shared data.
+ Each copy will not take ownership of the shared data.
+ This works well for __spirit__, since no dynamic
+ allocation of iterators is done. All copies are made
+ on the stack, so the original iterator has the
+ longest lifespan.]]
+]
+
+[table Predefined CheckingPolicy classes
+ [[Class name] [Description]]
+ [[`no_check`] [This policy does no checking at all.]]
+ [[`buf_id_check`] [This policy keeps around a buffer id, or a buffer
+ age. Every time `clear_queue()` is called on a
+ `multi_pass` iterator, it is possible that all other
+ iterators become invalid. When `clear_queue()` is
+ called, `buf_id_check` increments the buffer id.
+ When an iterator is dereferenced, this policy checks
+ that the buffer id of the iterator matches the shared
+ buffer id. This policy is most effective when used
+ together with the `split_std_deque` StoragePolicy.
+ It should not be used with the `fixed_size_queue`
+ StoragePolicy, because it will not detect iterator
+ dereferences that are out of range.]]
+ [[full_check] [This policy has not been implemented yet. When it
+ is, it will keep track of all iterators and make
+ sure that they are all valid. This will be mostly
+ useful for debugging purposes as it will incur
+ significant overhead.]]
+]
+
+[table Predefined StoragePolicy classes
+ [[Class name] [Description]]
+ [[`split_std_deque`] [Despite its name this policy keeps all buffered data
+ in a `std::vector`. All data is stored as long as
+ there is more than one iterator. Once the iterator
+ count goes down to one, and the queue is no longer
+ needed, it is cleared, freeing up memory. The queue
+ can also be forcibly cleared by calling
+ `multi_pass::clear_queue()`.]]
+ [[`fixed_size_queue<N>`][This policy keeps a circular buffer that is size
+ `N+1` and stores `N` elements. `fixed_size_queue`
+ is a template with a `std::size_t` parameter that
+ specified the queue size. It is your responsibility
+ to ensure that `N` is big enough for your parser.
+ Whenever the foremost iterator is incremented, the
+ last character of the buffer is automatically
+ erased. Currently there is no way to tell if an
+ iterator is trailing too far behind and has become
+ invalid. No dynamic allocation is done by this
+ policy during normal iterator operation, only on
+ initial construction. The memory usage of this
+ `StoragePolicy` is set at `N+1` bytes, unlike
+ `split_std_deque`, which is unbounded.]]
+]
+
+[heading Combinations: How to specify your own custom multi_pass]
+
+The beauty of policy based designs is that you can mix and match policies to
+create your own custom iterator by selecting the policies you want. Here's an
+example of how to specify a custom `multi_pass` that wraps an
+`std::istream_iterator<char>`, and is slightly more efficient than the default
+`multi_pass` (as generated by the `make_default_multi_pass()` API function)
+because it uses the `iterator_policies::first_owner` OwnershipPolicy and the
+`iterator_policies::no_check` CheckingPolicy:
+
+ typedef multi_pass<
+ std::istream_iterator<char>
+ , iterator_policies::default_policy<
+ iterator_policies::first_owner
+ , iterator_policies::no_check
+ , iterator_policies::input_iterator
+ , iterator_policies::split_std_deque
+ >
+ > first_owner_multi_pass_type;
+
+The default template parameters for `iterator_policies::default_policy` are:
+
+* `iterator_policies::ref_counted` OwnershipPolicy
+* `iterator_policies::no_check` CheckingPolicy, if `BOOST_SPIRIT_DEBUG` is
+ defined: `iterator_policies::buf_id_check` CheckingPolicy
+* `iterator_policies::input_iterator` InputPolicy, and
+* `iterator_policies::split_std_deque` StoragePolicy.
+
+So if you use `multi_pass<std::istream_iterator<char> >` you will get those
+pre-defined behaviors while wrapping an `std::istream_iterator<char>`.
+
+[heading Dealing with constant look ahead]
+
+There is one other pre-defined class called `look_ahead`. The class
+`look_ahead` is another predefine `multi_pass` iterator type. It has two
+template parameters: `Input`, the type of the input iterator to wrap, and a
+`std::size_t N`, which specifies the size of the buffer to the
+`fixed_size_queue` policy. While the default multi_pass configuration is
+designed for safey, `look_ahead` is designed for speed. `look_ahead` is derived
+from a multi_pass with the following policies: `input_iterator` InputPolicy,
+`first_owner` OwnershipPolicy, `no_check` CheckingPolicy, and
+`fixed_size_queue<N>` StoragePolicy.
+
+
+[heading How to write a functor for use with the `functor_input` InputPolicy]
+
+If you want to use the `functor_input` InputPolicy, you can write your own
+function object that will supply the input to `multi_pass`. The function object
+must satisfy several requirements. It must have a typedef `result_type` which
+specifies the return type of its `operator()`. This is standard practice in the
+STL. Also, it must supply a static variable called eof which is compared against
+to know whether the input has reached the end. Last but not least the function
+object must be default constructible. Here is an example:
+
+ // define the function object
+ class iterate_a2m
+ {
+ public:
+ typedef char result_type;
+
+ iterate_a2m() : c('A') {}
+ iterate_a2m(char c) : c_(c) {}
+
+ result_type operator()() const
+ {
+ if (c_ == 'M')
+ return eof;
+ return c_++;
+ }
+
+ static result_type eof;
+
+ private:
+ char c_;
+ };
+
+ iterate_a2m::result_type iterate_a2m::eof = iterate_a2m::result_type('\0');
+
+ // create two iterators using the define function object, one of which is
+ // an end iterator
+ typedef multi_pass<my_functor
+ , iterator_policies::functor_input
+ , iterator_policies::first_owner
+ , iterator_policies::no_check
+ , iterator_policies::split_std_deque>
+ functor_multi_pass_type;
+
+ functor_multi_pass_type first = functor_multi_pass_t(my_functor());
+ functor_multi_pass_type last;
+
+ // use the iterators: this will print "ABCDEFGHIJKL"
+ while (first != last) {
+ std::cout << *first;
+ ++first;
+ }
+
+[heading How to write policies for use with multi_pass]
+
+All policies to be used with the `default_policy` template need to have two
+embedded classes: `unique` and `shared`. The `unique` class needs to implement
+all required functions for a particular policy type. In addition it may hold
+all member data items being /unique/ for a particular instance of a `multi_pass`
+(hence the name). The `shared` class does not expose any member functions
+(except sometimes a constructor), but it may hold all member data items to be
+/shared/ between all copies of a particular `multi_pass`.
+
+[heading InputPolicy]
+
+An `InputPolicy` must have the following interface:
+
+ struct input_policy
+ {
+ // Input is the same type used as the first template parameter
+ // while instantiating the multi_pass
+ template <typename Input>
+ struct unique
+ {
+ // these typedef's will be exposed as the multi_pass iterator
+ // properties
+ typedef __unspecified_type__ value_type;
+ typedef __unspecified_type__ difference_type;
+ typedef __unspecified_type__ distance_type;
+ typedef __unspecified_type__ pointer;
+ typedef __unspecified_type__ reference;
+
+ unique() {}
+ explicit unique(Input) {}
+
+ // destroy is called whenever the last copy of a multi_pass is
+ // destructed (ownership_policy::release() returned true)
+ //
+ // mp: is a reference to the whole multi_pass instance
+ template <typename MultiPass>
+ static void destroy(MultiPass& mp);
+
+ // swap is called by multi_pass::swap()
+ void swap(unique&);
+
+ // advance_input is called whenever the next input character/token
+ // should be fetched.
+ //
+ // mp: is a reference to the whole multi_pass instance
+ // t: is a reference where the next character/token should be
+ // stored
+ //
+ // This method is expected to return the parameter t
+ template <typename MultiPass>
+ static value_type& advance_input(MultiPass& mp, value_type& t);
+
+ // input_at_eof is called to test whether this instance is a
+ // end of input iterator.
+ //
+ // mp: is a reference to the whole multi_pass instance
+ // t: is the current token
+ //
+ // This method is expected to return true if the end of input is
+ // reached. It is often used in the implementation of the function
+ // storage_policy::is_eof.
+ template <typename MultiPass>
+ static bool input_at_eof(MultiPass const& mp, value_type const& t);
+
+ // input_is_valid is called to verify if the parameter t represents
+ // a valid input character/token
+ //
+ // mp: is a reference to the whole multi_pass instance
+ // t: is the character/token to test for validity
+ //
+ // This method is expected to return true if the parameter t
+ // represents a valid character/token.
+ template <typename MultiPass>
+ static bool input_is_valid(MultiPass const& mp, value_type const& t);
+ };
+
+ // Input is the same type used as the first template parameter
+ // while instantiating the multi_pass
+ template <typename Input>
+ struct shared
+ {
+ explicit shared(Input) {}
+ };
+ };
+
+It is possible to derive the struct `unique` from the type
+`boost::spirit::detail::default_input_policy`. This type implements a minimal
+sufficient interface for some of the required functions, simplifying the task
+of writing a new input policy.
+
+This class may implement a function `destroy()` being called during destruction
+of the last copy of a `multi_pass`. This function should be used to free any of
+the shared data items the policy might have allocated during construction of
+its `shared` part. Because of the way `multi_pass` is implemented any allocated
+data members in `shared` should _not_ be deep copied in a copy constructor of
+`shared`.
+
+[heading OwnershipPolicy]
+
+The `OwnershipPolicy` must have the following interface:
+
+ struct ownership_policy
+ {
+ struct unique
+ {
+ // destroy is called whenever the last copy of a multi_pass is
+ // destructed (ownership_policy::release() returned true)
+ //
+ // mp: is a reference to the whole multi_pass instance
+ template <typename MultiPass>
+ static void destroy(MultiPass& mp);
+
+ // swap is called by multi_pass::swap()
+ void swap(unique&);
+
+ // clone is called whenever a multi_pass is copied
+ //
+ // mp: is a reference to the whole multi_pass instance
+ template <typename MultiPass>
+ static void clone(MultiPass& mp);
+
+ // release is called whenever a multi_pass is destroyed
+ //
+ // mp: is a reference to the whole multi_pass instance
+ //
+ // The method is expected to return true if the destructed
+ // instance is the last copy of a particular multi_pass.
+ template <typename MultiPass>
+ static bool release(MultiPass& mp);
+
+ // is_unique is called to test whether this instance is the only
+ // existing copy of a particular multi_pass
+ //
+ // mp: is a reference to the whole multi_pass instance
+ //
+ // The method is expected to return true if this instance is unique
+ // (no other copies of this multi_pass exist).
+ template <typename MultiPass>
+ static bool is_unique(MultiPass const& mp);
+ };
+
+ struct shared {};
+ };
+
+It is possible to derive the struct `unique` from the type
+`boost::spirit::detail::default_ownership_policy`. This type implements a
+minimal sufficient interface for some of the required functions, simplifying
+the task of writing a new ownership policy.
+
+This class may implement a function `destroy()` being called during destruction
+of the last copy of a `multi_pass`. This function should be used to free any of
+the shared data items the policy might have allocated during construction of
+its `shared` part. Because of the way `multi_pass` is implemented any allocated
+data members in `shared` should _not_ be deep copied in a copy constructor of
+`shared`.
+
+[heading CheckingPolicy]
+
+The `CheckingPolicy` must have the following interface:
+
+ struct checking_policy
+ {
+ struct unique
+ {
+ // swap is called by multi_pass::swap()
+ void swap(unique&);
+
+ // destroy is called whenever the last copy of a multi_pass is
+ // destructed (ownership_policy::release() returned true)
+ //
+ // mp: is a reference to the whole multi_pass instance
+ template <typename MultiPass>
+ static void destroy(MultiPass& mp);
+
+ // check is called before the multi_pass is dereferenced or
+ // incremented.
+ //
+ // mp: is a reference to the whole multi_pass instance
+ //
+ // This method is expected to make sure the multi_pass instance is
+ // still valid. If it is invalid an exception should be thrown.
+ template <typename MultiPass>
+ static void check(MultiPass const& mp);
+
+ // clear_queue is called whenever the function
+ // multi_pass::clear_queue is called on this instance
+ //
+ // mp: is a reference to the whole multi_pass instance
+ template <typename MultiPass>
+ static void clear_queue(MultiPass& mp);
+ };
+
+ struct shared {};
+ };
+
+It is possible to derive the struct `unique` from the type
+`boost::spirit::detail::default_checking_policy`. This type implements a
+minimal sufficient interface for some of the required functions, simplifying
+the task of writing a new checking policy.
+
+This class may implement a function `destroy()` being called during destruction
+of the last copy of a `multi_pass`. This function should be used to free any of
+the shared data items the policy might have allocated during construction of
+its `shared` part. Because of the way `multi_pass` is implemented any allocated
+data members in `shared` should _not_ be deep copied in a copy constructor of
+`shared`.
+
+[heading StoragePolicy]
+
+A `StoragePolicy` must have the following interface:
+
+ struct storage_policy
+ {
+ // Value is the same type as typename MultiPass::value_type
+ template <typename Value>
+ struct unique
+ {
+ // destroy is called whenever the last copy of a multi_pass is
+ // destructed (ownership_policy::release() returned true)
+ //
+ // mp: is a reference to the whole multi_pass instance
+ template <typename MultiPass>
+ static void destroy(MultiPass& mp);
+
+ // swap is called by multi_pass::swap()
+ void swap(unique&);
+
+ // dereference is called whenever multi_pass::operator*() is invoked
+ //
+ // mp: is a reference to the whole multi_pass instance
+ //
+ // This function is expected to return a reference to the current
+ // character/token.
+ template <typename MultiPass>
+ static typename MultiPass::reference dereference(MultiPass const& mp);
+
+ // increment is called whenever multi_pass::operator++ is invoked
+ //
+ // mp: is a reference to the whole multi_pass instance
+ template <typename MultiPass>
+ static void increment(MultiPass& mp);
+
+ //
+ // mp: is a reference to the whole multi_pass instance
+ template <typename MultiPass>
+ static void clear_queue(MultiPass& mp);
+
+ // is_eof is called to test whether this instance is a end of input
+ // iterator.
+ //
+ // mp: is a reference to the whole multi_pass instance
+ //
+ // This method is expected to return true if the end of input is
+ // reached.
+ template <typename MultiPass>
+ static bool is_eof(MultiPass const& mp);
+
+ // less_than is called whenever multi_pass::operator==() is invoked
+ //
+ // mp: is a reference to the whole multi_pass instance
+ // rhs: is the multi_pass reference this instance is compared
+ // to
+ //
+ // This function is expected to return true if the current instance
+ // is eual to the right hand side multi_pass instance
+ template <typename MultiPass>
+ static bool equal_to(MultiPass const& mp, MultiPass const& rhs);
+
+ // less_than is called whenever multi_pass::operator<() is invoked
+ //
+ // mp: is a reference to the whole multi_pass instance
+ // rhs: is the multi_pass reference this instance is compared
+ // to
+ //
+ // This function is expected to return true if the current instance
+ // is less than the right hand side multi_pass instance
+ template <typename MultiPass>
+ static bool less_than(MultiPass const& mp, MultiPass const& rhs);
+ };
+
+ // Value is the same type as typename MultiPass::value_type
+ template <typename Value>
+ struct shared {};
+ };
+
+It is possible to derive the struct `unique` from the type
+`boost::spirit::detail::default_storage_policy`. This type implements a
+minimal sufficient interface for some of the required functions, simplifying
+the task of writing a new storage policy.
+
+This class may implement a function `destroy()` being called during destruction
+of the last copy of a `multi_pass`. This function should be used to free any of
+the shared data items the policy might have allocated during construction of
+its `shared` part. Because of the way `multi_pass` is implemented any allocated
+data members in `shared` should _not_ be deep copied in a copy constructor of
+`shared`.
+
+Generally, a `StoragePolicy` is the trickiest policy to implement. You should
+study and understand the existing `StoragePolicy` classes before you try and
+write your own.
+
+
+[endsect]
+
+
+


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