Boost-Commit :

Date view	Thread view	Subject view	Author view

Subject: [Boost-commit] svn:boost r54259 - in trunk/libs/spirit/doc: . html html/spirit html/spirit/abstracts html/spirit/karma html/spirit/karma/quick_reference 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/tutorials html/spirit/structure
From: sohail_at_[hidden]
Date: 2009-06-23 00:30:29

Author: sohail
Date: 2009-06-23 00:30:19 EDT (Tue, 23 Jun 2009)
New Revision: 54259
URL: http://svn.boost.org/trac/boost/changeset/54259

Log:
Edit of preface complete.
Text files modified:
   trunk/libs/spirit/doc/html/index.html | 13
   trunk/libs/spirit/doc/html/spirit/abstracts.html | 15
   trunk/libs/spirit/doc/html/spirit/abstracts/parsing_expression_grammar.html | 91 -
   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 | 23
   trunk/libs/spirit/doc/html/spirit/introduction.html | 272 +++--
   trunk/libs/spirit/doc/html/spirit/karma.html | 17
   trunk/libs/spirit/doc/html/spirit/karma/quick_reference.html | 20
   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 | 306 ++++--
   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/lex.html | 19
   trunk/libs/spirit/doc/html/spirit/lex/abstracts.html | 20
   trunk/libs/spirit/doc/html/spirit/lex/abstracts/lexer_attributes.html | 22
   trunk/libs/spirit/doc/html/spirit/lex/abstracts/lexer_parsing.html | 24
   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 | 22
   trunk/libs/spirit/doc/html/spirit/lex/abstracts/lexer_primitives/lexer_token_definition.html | 23
   trunk/libs/spirit/doc/html/spirit/lex/abstracts/lexer_primitives/lexer_token_values.html | 122 +-
   trunk/libs/spirit/doc/html/spirit/lex/abstracts/lexer_semantic_actions.html | 454 ++++++++++
   trunk/libs/spirit/doc/html/spirit/lex/abstracts/lexer_states.html | 45
   trunk/libs/spirit/doc/html/spirit/lex/abstracts/lexer_static_model.html | 53
   trunk/libs/spirit/doc/html/spirit/lex/abstracts/lexer_tokenizing.html | 79 -
   trunk/libs/spirit/doc/html/spirit/lex/lexer_introduction.html | 60
   trunk/libs/spirit/doc/html/spirit/lex/quick_reference.html | 21
   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 | 671 +++++++++------
   trunk/libs/spirit/doc/html/spirit/lex/reference/concepts/token.html | 17
   trunk/libs/spirit/doc/html/spirit/lex/reference/concepts/tokendef.html | 17
   trunk/libs/spirit/doc/html/spirit/lex/reference/concepts/tokenset.html | 17
   trunk/libs/spirit/doc/html/spirit/lex/reference/lexer_class.html | 49
   trunk/libs/spirit/doc/html/spirit/lex/reference/token_class.html | 17
   trunk/libs/spirit/doc/html/spirit/lex/reference/tokendef_class.html | 17
   trunk/libs/spirit/doc/html/spirit/lex/reference/tokenset_class.html | 17
   trunk/libs/spirit/doc/html/spirit/lex/tutorials.html | 24
   trunk/libs/spirit/doc/html/spirit/lex/tutorials/lexer_quickstart1.html | 106 +-
   trunk/libs/spirit/doc/html/spirit/lex/tutorials/lexer_quickstart2.html | 196 +---
   trunk/libs/spirit/doc/html/spirit/lex/tutorials/lexer_quickstart3.html | 200 ++--
   trunk/libs/spirit/doc/html/spirit/lex/tutorials/lexer_tutorials.html | 37
   trunk/libs/spirit/doc/html/spirit/notes.html | 15
   trunk/libs/spirit/doc/html/spirit/notes/style_guide.html | 25
   trunk/libs/spirit/doc/html/spirit/preface.html | 327 ++++---
   trunk/libs/spirit/doc/html/spirit/qi.html | 18
   trunk/libs/spirit/doc/html/spirit/qi/quick_reference.html | 18
   trunk/libs/spirit/doc/html/spirit/qi/quick_reference/common_notation.html | 84 -
   trunk/libs/spirit/doc/html/spirit/qi/quick_reference/compound_attribute_rules.html | 223 ++--
   trunk/libs/spirit/doc/html/spirit/qi/quick_reference/lazy_arguments.html | 24
   trunk/libs/spirit/doc/html/spirit/qi/quick_reference/non_terminals.html | 306 ++++--
   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/tutorials.html | 17
   trunk/libs/spirit/doc/html/spirit/qi/tutorials/complex___our_first_complex_parser.html | 38
   trunk/libs/spirit/doc/html/spirit/qi/tutorials/employee___parsing_into_structs.html | 171 +--
   trunk/libs/spirit/doc/html/spirit/qi/tutorials/mini_xml___asts_.html | 237 ++--
   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 | 32
   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 | 117 +-
   trunk/libs/spirit/doc/html/spirit/qi/tutorials/semantic_actions.html | 56
   trunk/libs/spirit/doc/html/spirit/qi/tutorials/sum___adding_numbers.html | 111 +-
   trunk/libs/spirit/doc/html/spirit/qi/tutorials/warming_up.html | 137 +-
   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 | 15
   trunk/libs/spirit/doc/html/spirit/what_s_new.html | 157 +-
   trunk/libs/spirit/doc/preface.qbk | 173 ++-
   75 files changed, 5831 insertions(+), 4397 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-06-23 00:30:19 EDT (Tue, 23 Jun 2009)
@@ -3,8 +3,8 @@
<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">
-<link rel="home" href="index.html" title="Spirit 2.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" href="index.html" title="Spirit 2.1">
<link rel="next" href="spirit/preface.html" title="Preface">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -33,12 +33,13 @@
</div></div>
<div>Copyright © 2001-2009 Joel
 de Guzman, Hartmut Kaiser</div>
-<div><div class="legalnotice">
+<div><div class="legalnotice">
+<a name="id2593886"></a>
 Distributed under the Boost Software License, Version 1.0. (See accompanying
 file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)
- </div></div>
+ 
+</div></div>
</div>
-<div></div>
<hr>
</div>
<div class="toc">
@@ -158,7 +159,7 @@
</div>
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
-<td align="left">Last revised: June 19, 2009 at 02:23:07 GMT</td>
+<td align="left">Last revised: June 23, 2009 at 04:27:56 GMT</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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<link rel="home" href="../index.html" title="Spirit 2.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" 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">
@@ -23,12 +23,9 @@
<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="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>Syntax Diagram</dt>
<dt><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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<link rel="home" href="../../index.html" title="Spirit 2.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" 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>
@@ -24,14 +23,10 @@
<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="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>

 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.
 
-<a name="spirit.abstracts.parsing_expression_grammar.sequences"></a><h4>
-<a name="id414932"></a>
- Sequences
- </h4>
+<a name="spirit.abstracts.parsing_expression_grammar.sequences"></a><h5>
+<a name="id2609121"></a>
+ <a class="link" href="parsing_expression_grammar.html#spirit.abstracts.parsing_expression_grammar.sequences">Sequences</a>
+ </h5>

 Sequences are represented by juxtaposition like in EBNF:
 
<pre class="programlisting">a b
</pre>

- The PEG expression above states that, in order for this to succeed, <tt class="computeroutput">a</tt> must follow <tt class="computeroutput">b</tt>.
+ The PEG expression above states that, in order for this to succeed, <code class="computeroutput">a</code> must follow <code class="computeroutput">b</code>.
 Here's the syntax diagram:
 
<div class="blockquote"><blockquote class="blockquote">

 

- <img src="../../images/sequence.png" alt="sequence">
+ <img src="../../../../images/sequence.png" alt="sequence">
 

 
@@ -72,7 +67,7 @@
<pre class="programlisting">'x' digit
</pre>

- which means the character <tt class="computeroutput">x</tt>
+ which means the character <code class="computeroutput">x</code>
 must be followed by a digit.
 
<div class="note"><table border="0" summary="Note">
@@ -80,15 +75,15 @@
<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">
- In Spirit.Qi, we use the <tt class="computeroutput">>></tt>
+<tr><td align="left" valign="top">
+ In Spirit.Qi, we use the <code class="computeroutput">>></code>
 for sequences since C++ does not allow juxtaposition
 </td></tr>
</table></div>
-<a name="spirit.abstracts.parsing_expression_grammar.alternatives"></a><h4>
-<a name="id415082"></a>
- Alternatives
- </h4>
+<a name="spirit.abstracts.parsing_expression_grammar.alternatives"></a><h5>
+<a name="id2609256"></a>
+ <a class="link" href="parsing_expression_grammar.html#spirit.abstracts.parsing_expression_grammar.alternatives">Alternatives</a>
+ </h5>

 Alternatives are represented in PEG using the slash:
 
@@ -99,39 +94,39 @@
<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">
- In Spirit.Qi, we use the <tt class="computeroutput">|</tt>
+<tr><td align="left" valign="top">
+ In Spirit.Qi, we use the <code class="computeroutput">|</code>
 for alternatives just as in EBNF
 </td></tr>
</table></div>

 Alternatives allow for choices. The expression above reads: try to match
- <tt class="computeroutput">a</tt>. If <tt class="computeroutput">a</tt>
- succeeds, success, if not try to match <tt class="computeroutput">b</tt>.
+ <code class="computeroutput">a</code>. If <code class="computeroutput">a</code>
+ succeeds, success, if not try to match <code class="computeroutput">b</code>.
 This is a bit of a deviation from the usual EBNF interpretation where you
- simply match <tt class="computeroutput">a</tt> or <tt class="computeroutput">b</tt>.
+ simply match <code class="computeroutput">a</code> or <code class="computeroutput">b</code>.
 Here's the syntax diagram:
 
<div class="blockquote"><blockquote class="blockquote">

 

- <img src="../../images/alternative.png" alt="alternative">
+ <img src="../../../../images/alternative.png" alt="alternative">
 

 
</blockquote></div>

 PEGs allow for ambiguity in the alternatives. In the expression above, both
- <tt class="computeroutput">a</tt> or <tt class="computeroutput">b</tt>
+ <code class="computeroutput">a</code> or <code class="computeroutput">b</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 $$$).
 
-<a name="spirit.abstracts.parsing_expression_grammar.loops"></a><h4>
-<a name="id415268"></a>
- Loops
- </h4>
+<a name="spirit.abstracts.parsing_expression_grammar.loops"></a><h5>
+<a name="id2609427"></a>
+ <a class="link" href="parsing_expression_grammar.html#spirit.abstracts.parsing_expression_grammar.loops">Loops</a>
+ </h5>

 Again, like EBNF, PEG uses the regular-expression Kleene star and the plus
 loops:
@@ -144,7 +139,7 @@
<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">
 Spirit.Qi uses the prefix star and plus since there is no postfix star
 or plus in C++.
 </td></tr>
@@ -156,7 +151,7 @@

 

- <img src="../../images/kleene.png" alt="kleene">
+ <img src="../../../../images/kleene.png" alt="kleene">
 

 
@@ -165,14 +160,14 @@

 

- <img src="../../images/plus.png" alt="plus">
+ <img src="../../../../images/plus.png" alt="plus">
 

 
</blockquote></div>

- The first, called the Kleene star, matches zero or more of its subject <tt class="computeroutput">a</tt>. The second, plus, matches one ore more
- of its subject <tt class="computeroutput">a</tt>.
+ The first, called the Kleene star, matches zero or more of its subject <code class="computeroutput">a</code>. The second, plus, matches one ore more
+ of its subject <code class="computeroutput">a</code>.
 

 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.
 
-<a name="spirit.abstracts.parsing_expression_grammar.difference"></a><h4>
-<a name="id415445"></a>
- Difference
- </h4>
+<a name="spirit.abstracts.parsing_expression_grammar.difference"></a><h5>
+<a name="id2609605"></a>
+ <a class="link" href="parsing_expression_grammar.html#spirit.abstracts.parsing_expression_grammar.difference">Difference</a>
+ </h5>

 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">a - b
</pre>

- The expression reads: match <tt class="computeroutput">a</tt>
- but not <tt class="computeroutput">b</tt>.
+ The expression reads: match <code class="computeroutput">a</code>
+ but not <code class="computeroutput">b</code>.
 
</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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<link rel="home" href="../../index.html" title="Spirit 2.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" 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>
@@ -24,27 +23,24 @@
<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="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>

 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
- [<a name="id414434" href="#ftn.id414434">1</a>]
+ [<a name="id2553057" href="#ftn.id2553057" class="footnote">1</a>]
 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.
 
-<a name="spirit.abstracts.syntax_diagram.elements"></a><h4>
-<a name="id414452"></a>
- Elements
- </h4>
+<a name="spirit.abstracts.syntax_diagram.elements"></a><h5>
+<a name="id2553078"></a>
+ <a class="link" href="syntax_diagram.html#spirit.abstracts.syntax_diagram.elements">Elements</a>
+ </h5>

 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 @@

 

- <img src="../../images/start_stop.png" alt="start_stop">
+ <img src="../../../../images/start_stop.png" alt="start_stop">
 

 
@@ -66,7 +62,7 @@

 

- <img src="../../images/terminal.png" alt="terminal">
+ <img src="../../../../images/terminal.png" alt="terminal">
 

 
@@ -80,15 +76,15 @@

 

- <img src="../../images/non-terminal.png" alt="non-terminal">
+ <img src="../../../../images/non-terminal.png" alt="non-terminal">
 

 
</blockquote></div>
-<a name="spirit.abstracts.syntax_diagram.constructs"></a><h4>
-<a name="id414572"></a>
- Constructs
- </h4>
+<a name="spirit.abstracts.syntax_diagram.constructs"></a><h5>
+<a name="id2608787"></a>
+ <a class="link" href="syntax_diagram.html#spirit.abstracts.syntax_diagram.constructs">Constructs</a>
+ </h5>

 The most basic composition is the Sequence. B follows A:
 
@@ -96,7 +92,7 @@

 

- <img src="../../images/sequence.png" alt="sequence">
+ <img src="../../../../images/sequence.png" alt="sequence">
 

 
@@ -111,7 +107,7 @@

 

- <img src="../../images/alternative.png" alt="alternative">
+ <img src="../../../../images/alternative.png" alt="alternative">
 

 
@@ -123,7 +119,7 @@

 

- <img src="../../images/optional.png" alt="optional">
+ <img src="../../../../images/optional.png" alt="optional">
 

 
@@ -135,7 +131,7 @@

 

- <img src="../../images/kleene.png" alt="kleene">
+ <img src="../../../../images/kleene.png" alt="kleene">
 

 
@@ -144,7 +140,7 @@

 

- <img src="../../images/plus.png" alt="plus">
+ <img src="../../../../images/plus.png" alt="plus">
 

 
@@ -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.
 
-<a name="spirit.abstracts.syntax_diagram.predicates"></a><h4>
-<a name="id414755"></a>
- Predicates
- </h4>
+<a name="spirit.abstracts.syntax_diagram.predicates"></a><h5>
+<a name="id2608957"></a>
+ <a class="link" href="syntax_diagram.html#spirit.abstracts.syntax_diagram.predicates">Predicates</a>
+ </h5>

 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 @@

 

- <img src="../../images/predicate.png" alt="predicate">
+ <img src="../../../../images/predicate.png" alt="predicate">
 

 
@@ -189,7 +185,7 @@

 

- <img src="../../images/and_predicate.png" alt="and_predicate">
+ <img src="../../../../images/and_predicate.png" alt="and_predicate">
 

 
@@ -198,7 +194,7 @@

 

- <img src="../../images/not_predicate.png" alt="not_predicate">
+ <img src="../../../../images/not_predicate.png" alt="not_predicate">
 

 
@@ -212,7 +208,7 @@
 
<div class="footnotes">
 <hr width="100" align="left">
-<div class="footnote">[<a name="ftn.id414434" href="#id414434">1</a>] 
+<div class="footnote">[<a name="ftn.id2553057" href="#id2553057" class="para">1</a>] 
 Niklaus Wirth: The Programming Language Pascal. (July 1973)
 </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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<link rel="home" href="../index.html" title="Spirit 2.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" 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">
@@ -23,12 +23,9 @@
<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="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>

 This version of Spirit is a complete rewrite of the classic
 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:
 

- Eric Niebler for writing Boost.Proto, without
+ Eric Niebler 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.
 

- Ben Hanson for providing us with an early
+ Ben Hanson 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.
 

- FIXME: Add more people
+ FIXME: Add more people
 
-<a name="spirit.acknowledgments.acknowledgements_from_the_spirit_v1__emphasis_classic__emphasis__documentation"></a><h3>
-<a name="id487336"></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="id2676123"></a>
+ <a class="link" href="acknowledgments.html#spirit.acknowledgments.acknowledgements_from_the_spirit_v1__emphasis_classic__emphasis__documentation">Acknowledgements
 from the Spirit V1 classic Documentation</a>
- </h3>
+ </h4>

 Special thanks for working on Spirit classic to:
 

- Dan Nuffer for his work on lexers, parse trees,
+ Dan Nuffer 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.
 

- Hartmut Kaiser for his work on the C parser,
+ Hartmut Kaiser 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.
 

- Martin Wille who improved grammar multi thread
+ Martin Wille 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 :-).
 

- Martijn W. Van Der Lee our Web site administrator
+ Martijn W. Van Der Lee our Web site administrator
 and for contributing the RFC821 parser.
 

- Giovanni Bajo for last minute tweaks of Spirit
+ Giovanni Bajo 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.
 

- Juan Carlos Arevalo-Baeza (JCAB)* for his
+ Juan Carlos Arevalo-Baeza (JCAB)* for his
 work on the C++ parser, the position iterator, ports to v1.5 and keeping the
 mailing list discussions alive and kicking.
 

- Vaclav Vesely, lots of stuff, the no_actions
+ Vaclav Vesely, 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.
 

- Raghavendra Satish for doing the original
+ Raghavendra Satish for doing the original
 v1.3 port to VC++ and his work on Phoenix.
 

- Noah Stein for following up and helping Ragav
+ Noah Stein for following up and helping Ragav
 on the VC++ ports.
 

- Hakki Dogusan, for his original v1.0 Pascal
+ Hakki Dogusan, for his original v1.0 Pascal
 parser.
 

- John (EBo) David for his work on the VM and
+ John (EBo) David for his work on the VM and
 watching over my shoulder as I code giving the impression of distance eXtreme
 programming.
 

- Chris Uzdavinis for feeding in comments and
+ Chris Uzdavinis for feeding in comments and
 valuable suggestions as well as editing the documentation.
 

- Carsten Stoll, for his work on dynamic parsers.
+ Carsten Stoll, for his work on dynamic parsers.
 

- Andy Elvey and his conifer parser.
+ Andy Elvey and his conifer parser.
 

- Bruce Florman, who did the original v1.0 port
+ Bruce Florman, who did the original v1.0 port
 to VC++.
 

- Jeff Westfahl for porting the loop parsers
+ Jeff Westfahl for porting the loop parsers
 to v1.5 and contributing the file iterator.
 

- Peter Simons for the RFC date parser example
+ Peter Simons for the RFC date parser example
 and tutorial plus helping out with some nitty gritty details.
 

- Markus Schöpflin for suggesting the end_p parser
+ Markus Schöpflin for suggesting the end_p parser
 and lots of other nifty things and his active presence in the mailing list.
 

- Doug Gregor for mentoring and his ability
+ Doug Gregor for mentoring and his ability
 to see things that others don't.
 

- David Abrahams for giving Joel a job that
+ David Abrahams for giving Joel a job that
 allows him to still work on Spirit, plus countless advice and help on C++ and
 specifically template metaprogramming.
 

- Aleksey Gurtovoy for his MPL library from
+ Aleksey Gurtovoy for his MPL library from
 which we stole many metaprogramming tricks especially for less conforming compilers
 such as Borland and VC6/7.
 

- Gustavo Guerra for his last minute review
+ Gustavo Guerra 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).
 

- Nicola Musatti, Paul
- Snively, Alisdair Meredith and
- Hugo Duncan for testing and sending in various
+ Nicola Musatti, Paul
+ Snively, Alisdair Meredith and
+ Hugo Duncan for testing and sending in various
 patches.
 

- Steve Rowe for his splendid work on the TSTs
+ Steve Rowe for his splendid work on the TSTs
 that will soon be taken into Spirit.
 

- Jonathan de Halleux for his work on actors.
+ Jonathan de Halleux for his work on actors.
 

- Angus Leeming for last minute editing work
+ Angus Leeming 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.
 

- Joao Abecasis for his active presence in the
+ Joao Abecasis for his active presence in the
 Spirit mailing list, providing user support, participating in the discussions
 and so on.
 

- Guillaume Melquiond for a last minute patch
+ Guillaume Melquiond for a last minute patch
 to multi_pass for 1.8.1.
 

- Peder Holt for his porting work on Phoenix,
+ Peder Holt for his porting work on Phoenix,
 Fusion and Spirit to VC6.
 

@@ -206,19 +203,19 @@
 in the review:
 

- John Maddock, our review manager, Aleksey Gurtovoy, Andre Hentz,
- Beman Dawes, Carl Daniel,
- Christopher Currie, Dan
- Gohman, Dan Nuffer, Daryle
- Walker, David Abrahams, David B. Held, Dirk Gerrits,
- Douglas Gregor, Hartmut
- Kaiser, Iain K.Hanson, Juan Carlos Arevalo-Baeza, Larry
- Evans, Martin Wille, Mattias Flodin, Noah Stein,
- Nuno Lucas, Peter Dimov,
- Peter Simons, Petr Kocmid,
- Ross Smith, Scott Kirkwood,
- Steve Cleary, Thorsten
- Ottosen, Tom Wenisch, Vladimir Prus
+ John Maddock, our review manager, Aleksey Gurtovoy, Andre Hentz,
+ Beman Dawes, Carl Daniel,
+ Christopher Currie, Dan
+ Gohman, Dan Nuffer, Daryle
+ Walker, David Abrahams, David B. Held, Dirk Gerrits,
+ Douglas Gregor, Hartmut
+ Kaiser, Iain K.Hanson, Juan Carlos Arevalo-Baeza, Larry
+ Evans, Martin Wille, Mattias Flodin, Noah Stein,
+ Nuno Lucas, Peter Dimov,
+ Peter Simons, Petr Kocmid,
+ Ross Smith, Scott Kirkwood,
+ Steve Cleary, Thorsten
+ Ottosen, Tom Wenisch, Vladimir Prus
 

 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-06-23 00:30:19 EDT (Tue, 23 Jun 2009)
@@ -3,10 +3,10 @@
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>FAQ</title>
<link rel="stylesheet" href="../../../../../doc/html/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.65.1">
-<link rel="home" href="../index.html" title="Spirit 2.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" 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="lex/reference/tokenset_class.html" title="TokenSet Class">
<link rel="next" href="notes.html" title="Notes">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -23,18 +23,15 @@
<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>
</div>
<div class="section" lang="en">
-<div class="titlepage">
-<div><div><h2 class="title" style="clear: both">
-<a name="spirit.faq"></a>FAQ
-</h2></div></div>
-<div></div>
-</div>
-<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="id485771"></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
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="spirit.faq"></a><a class="link" href="faq.html" title="FAQ">FAQ</a>
+</h2></div></div></div>
+<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="id2674692"></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>

 The boost/spirit directory currently holds two versions of the Spirit library:
 Spirit.Classic (former V1.8.x) and SpiritV2. Both are

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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<link rel="home" href="../index.html" title="Spirit 2.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" 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">
@@ -23,12 +23,9 @@
<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="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>

 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
@@ -69,7 +66,7 @@
 to generate arbitrarily-formatted output.
 

- 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:
 
@@ -102,10 +99,9 @@
 
<div class="figure">
<a name="spirit.spiritstructure"></a>Figure 1. The overall structure of the Boost Spirit library
-<img src="./images/spiritstructure.png" alt="The
- overall structure of the Boost Spirit library">
+<div class="figure-contents"><img src=".././images/spiritstructure.png" alt="The overall structure of the Boost Spirit library"></div>
</div>
-
+ 
 

 The separate sublibraries Spirit.Qi, Spirit.Karma
@@ -118,8 +114,7 @@
 the input for a parser generated by Spirit.Qi.
 

- 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
@@ -130,17 +125,15 @@
<div class="figure">
<a name="spirit.spiritkarmaflow"></a>Figure 2. The place of Spirit.Qi and Spirit.Karma
 in a data transformation flow of a typical application
-<img src="./images/spiritkarmaflow.png" alt="The
- place of Spirit.Qi and Spirit.Karma
- in a data transformation flow of a typical application">
+<div class="figure-contents"><img src=".././images/spiritkarmaflow.png" alt="The place of Spirit.Qi and Spirit.Karma in a data transformation flow of a typical application"></div>
</div>
-
+ 
 
-<a name="spirit.introduction.a_quick_overview_of_parsing_with__emphasis_spirit_qi__emphasis_"></a><h3>
-<a name="id411290"></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="id2605650"></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 Spirit.Qi</a>
- </h3>
+ </h4>

 Spirit.Qi is Spirit's sublibrary dealing with generating
 parsers based on a given target grammar (essentially a format description of
@@ -165,14 +158,14 @@
</pre>

 Through the magic of expression templates, this is perfectly valid and executable
- C++ code. The production rule <tt class="computeroutput">expression</tt>
- is, in fact, an object that has a member function <tt class="computeroutput">parse</tt>
+ C++ code. The production rule <code class="computeroutput">expression</code>
+ is, in fact, an object that has a member function <code class="computeroutput">parse</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">integer</tt>
- invoked by <tt class="computeroutput">factor</tt>. Now, the
- production rule <tt class="computeroutput">expression</tt>
- in our grammar specification, traditionally called the <tt class="computeroutput">start</tt>
+ the type declarations and the definition of the rule <code class="computeroutput">integer</code>
+ invoked by <code class="computeroutput">factor</code>. Now, the
+ production rule <code class="computeroutput">expression</code>
+ in our grammar specification, traditionally called the <code class="computeroutput">start</code>
 symbol, can recognize inputs such as:
 
<pre class="programlisting">12345
@@ -199,19 +192,19 @@

 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">>></tt> operator instead
- for this purpose. We take the <tt class="computeroutput">>></tt>
+ the shift <code class="computeroutput">>></code> operator instead
+ for this purpose. We take the <code class="computeroutput">>></code>
 operator, with arrows pointing to the right, to mean "is followed by".
 Thus we write:
 
<pre class="programlisting">a >> b
</pre>

- The alternative operator <tt class="computeroutput">|</tt> and
- the parentheses <tt class="computeroutput">()</tt> remain as is.
- The assignment operator <tt class="computeroutput">=</tt> is used
- in place of EBNF's <tt class="computeroutput">::=</tt>. Last but
- not least, the Kleene star <tt class="computeroutput">*</tt> which
+ The alternative operator <code class="computeroutput">|</code> and
+ the parentheses <code class="computeroutput">()</code> remain as is.
+ The assignment operator <code class="computeroutput">=</code> is used
+ in place of EBNF's <code class="computeroutput">::=</code>. Last but
+ not least, the Kleene star <code class="computeroutput">*</code> which
 used to be a postfix operator in EBNF becomes a prefix. Instead of:
 
<pre class="programlisting">a* //... in EBNF syntax,
@@ -222,15 +215,15 @@
<pre class="programlisting">*a //... in Spirit.
</pre>

- since there are no postfix stars, <tt class="computeroutput">*</tt>,
+ since there are no postfix stars, <code class="computeroutput">*</code>,
 in C/C++. Finally, we terminate each rule with the ubiquitous semi-colon,
- <tt class="computeroutput">;</tt>.
+ <code class="computeroutput">;</code>.
 
-<a name="spirit.introduction.a_quick_overview_of_output_generation_with__emphasis_spirit_karma__emphasis_"></a><h3>
-<a name="id412498"></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="id2606750"></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 Spirit.Karma</a>
- </h3>
+ </h4>

 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
@@ -238,7 +231,7 @@
 

 Let's assume we need to generate a textual representation from a simple data
- structure such as a <tt class="computeroutput">std::vector<int></tt>. Conventional
+ structure such as a <code class="computeroutput">std::vector<int></code>. Conventional
 code probably would look like:
 
<pre class="programlisting">std::vector<int> v (initialize_and_fill());
@@ -257,84 +250,114 @@
</pre>

 Here are some more examples of format descriptions for different output representations
- of the same <tt class="computeroutput">std::vector<int></tt>:
+ of the same <code class="computeroutput">std::vector<int></code>:
 
<div class="table">
-<a name="id412935"></a>Table 2. Different output formats for `std::vector<int>`
-<table class="table" summary="Different output formats for `std::vector<int>`">
+<a name="id2607148"></a>Table 2. Different output formats for `std::vector<int>`
+<div class="table-contents"><table class="table" summary="Different output formats for `std::vector<int>`">
<colgroup>
<col>
<col>
<col>
</colgroup>
<thead><tr>
-<th>
+<th>
+ 
 Format
- </th>
-<th>
+ 
+ </th>
+<th>
+ 
 Example
- </th>
-<th>
+ 
+ </th>
+<th>
+ 
 Description
- </th>
+ 
+ </th>
</tr></thead>
<tbody>
<tr>
-<td>
- <tt class="computeroutput">'[' <<
+<td>
+ 
+ <code class="computeroutput">'[' <<
 *(int_
- << ',') << ']'</tt>
- </td>
-<td>
- <tt class="computeroutput">[1,8,10,]</tt>
- </td>
-<td>
+ << ',') << ']'</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">[1,8,10,]</code>
+ 
+ </td>
+<td>
+ 
 Comma separated list of integers
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">*('('
+<td>
+ 
+ <code class="computeroutput">*('('
 << int_
 << ')'
- << ',')</tt>
- </td>
-<td>
- <tt class="computeroutput">(1),(8),(10),]</tt>
- </td>
-<td>
+ << ',')</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">(1),(8),(10),]</code>
+ 
+ </td>
+<td>
+ 
 Comma separated list of integers in parenthesis
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">*hex</tt>
- </td>
-<td>
- <tt class="computeroutput">18a</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">*hex</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">18a</code>
+ 
+ </td>
+<td>
+ 
 A list of hexadecimal numbers
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">*(double_
- << ',')</tt>
- </td>
-<td>
- <tt class="computeroutput">1.0,8.0,10.0,</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">*(double_
+ << ',')</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">1.0,8.0,10.0,</code>
+ 
+ </td>
+<td>
+ 
 A list of floating point numbers
- </td>
+ 
+ </td>
</tr>
</tbody>
-</table>
+</table></div>
</div>
-
+ 
 The syntax is similar to Qi with the exception that we
- use the <tt class="computeroutput"><<</tt> operator for
+ use the <code class="computeroutput"><<</code> operator for
 output concatenation. This should be easy to understand as it follows the conventions
 used in the Standard's I/O streams.
 
@@ -345,56 +368,75 @@
 next table gives some related examples.
 
<div class="table">
-<a name="id413381"></a>Table 3. Different data types usable with the output format
+<a name="id2607555"></a>Table 3. Different data types usable with the output format
 `*(int_ << eol)`
-<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_ << eol)`">
<colgroup>
<col>
<col>
</colgroup>
<thead><tr>
-<th>
+<th>
+ 
 Data type
- </th>
+ 
+ </th>
<td class="auto-generated"> </td>
</tr></thead>
<tbody>
<tr>
-<td>
- <tt class="computeroutput">int i[4]</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">int i[4]</code>
+ 
+ </td>
+<td>
+ 
 C style arrays
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">std::vector<int></tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">std::vector<int></code>
+ 
+ </td>
+<td>
+ 
 Standard vector
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">std::list<int></tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">std::list<int></code>
+ 
+ </td>
+<td>
+ 
 Standard list
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">boost::array<long, 20></tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">boost::array<long, 20></code>
+ 
+ </td>
+<td>
+ 
 Boost array
- </td>
+ 
+ </td>
</tr>
</tbody>
-</table>
+</table></div>
</div>
+ 
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>

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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<link rel="home" href="../index.html" title="Spirit 2.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" href="../index.html" title="Spirit 2.1">
<link rel="up" href="../index.html" title="Spirit 2.1">
-<link rel="previous" href="qi/quick_reference/phoenix.html" title="Phoenix">
+<link rel="prev" href="qi/quick_reference/phoenix.html" title="Phoenix">
<link rel="next" href="karma/quick_reference.html" title="Quick Reference">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -23,12 +23,9 @@
<a accesskey="p" href="qi/quick_reference/phoenix.html"><img src="../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="karma/quick_reference.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>
-</div>
+<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>Quick Reference</dt>
<dd><dl>

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-06-23 00:30:19 EDT (Tue, 23 Jun 2009)
@@ -3,12 +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">
-<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="next" href="quick_reference/common_notation.html" title="Common
- Notation">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" href="../../index.html" title="Spirit 2.1">
+<link rel="up" href="../karma.html" title="Karma">
+<link rel="prev" href="../karma.html" title="Karma">
+<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,12 +23,9 @@
<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="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="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><a href="quick_reference/common_notation.html">Common
Notation</a></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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<link rel="home" href="../../../index.html" title="Spirit 2.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" 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>
@@ -25,111 +23,107 @@
<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="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>
+</h4></div></div></div>
<div class="variablelist">
Notation
<dl>
-<dt><tt class="computeroutput">P</tt></dt>
+<dt><code class="computeroutput">P</code></dt>
<dd>
 Parser type
 </dd>
-<dt><tt class="computeroutput">p, a,
+<dt><code class="computeroutput">p, a,
 b,
- c</tt></dt>
+ c</code></dt>
<dd>
 Parser objects
 </dd>
-<dt><tt class="computeroutput">A, B,
- C</tt></dt>
+<dt><code class="computeroutput">A, B,
+ C</code></dt>
<dd>
 Attribute types of parsers A, B and C
 </dd>
-<dt><tt class="computeroutput">I</tt></dt>
+<dt><code class="computeroutput">I</code></dt>
<dd>
 The iterator type used for parsing
 </dd>
-<dt><tt class="computeroutput">Unused</tt></dt>
+<dt><code class="computeroutput">Unused</code></dt>
<dd>
- An <tt class="computeroutput">unused_type</tt>
+ An <code class="computeroutput">unused_type</code>
 </dd>
-<dt><tt class="computeroutput">Context</tt></dt>
+<dt><code class="computeroutput">Context</code></dt>
<dd>
- The enclosing rule's <tt class="computeroutput">Context</tt>
+ The enclosing rule's <code class="computeroutput">Context</code>
 type
 </dd>
-<dt><tt class="computeroutput">Attr</tt></dt>
+<dt><code class="computeroutput">Attr</code></dt>
<dd>
 An attribute type
 </dd>
-<dt><tt class="computeroutput">b</tt></dt>
+<dt><code class="computeroutput">b</code></dt>
<dd>
 A boolean expression
 </dd>
-<dt><tt class="computeroutput">fp</tt></dt>
+<dt><code class="computeroutput">fp</code></dt>
<dd>
- A (lazy parser) function with signature <tt class="computeroutput">P(Unused, Context)</tt>
+ A (lazy parser) function with signature <code class="computeroutput">P(Unused, Context)</code>
 </dd>
-<dt><tt class="computeroutput">fa</tt></dt>
+<dt><code class="computeroutput">fa</code></dt>
<dd>
- A (semantic action) function with signature <tt class="computeroutput">void(Attr, Context, bool&)</tt>. The third parameter is a boolean
- flag that can be set to false to force the parse to fail. Both <tt class="computeroutput">Context</tt> and the boolean flag are
+ A (semantic action) function with signature <code class="computeroutput">void(Attr, Context, bool&)</code>. The third parameter is a boolean
+ flag that can be set to false to force the parse to fail. Both <code class="computeroutput">Context</code> and the boolean flag are
 optional.
 </dd>
-<dt><tt class="computeroutput">first</tt></dt>
+<dt><code class="computeroutput">first</code></dt>
<dd>
 An iterator pointing to the start of input
 </dd>
-<dt><tt class="computeroutput">last</tt></dt>
+<dt><code class="computeroutput">last</code></dt>
<dd>
 An iterator pointing to the end of input
 </dd>
-<dt><tt class="computeroutput">Ch</tt></dt>
+<dt><code class="computeroutput">Ch</code></dt>
<dd>
 Character-class specific character type (See __char_classtypes_)
 </dd>
-<dt><tt class="computeroutput">ch</tt></dt>
+<dt><code class="computeroutput">ch</code></dt>
<dd>
 Character-class specific character (See __char_classtypes_)
 </dd>
-<dt><tt class="computeroutput">ch2</tt></dt>
+<dt><code class="computeroutput">ch2</code></dt>
<dd>
 Character-class specific character (See __char_classtypes_)
 </dd>
-<dt><tt class="computeroutput">chset</tt></dt>
+<dt><code class="computeroutput">chset</code></dt>
<dd>
 Character-set specifier string (example: "a-z0-9")
 </dd>
-<dt><tt class="computeroutput">str</tt></dt>
+<dt><code class="computeroutput">str</code></dt>
<dd>
 Character-class specific string (See __char_classtypes_)
 </dd>
-<dt><tt class="computeroutput">Str</tt></dt>
+<dt><code class="computeroutput">Str</code></dt>
<dd>
- Attribute of <tt class="computeroutput">str</tt>:
- <tt class="computeroutput">std::basic_string<T></tt>
- where <tt class="computeroutput">T</tt> is the underlying
- character type of <tt class="computeroutput">str</tt>
+ Attribute of <code class="computeroutput">str</code>:
+ <code class="computeroutput">std::basic_string<T></code>
+ where <code class="computeroutput">T</code> is the underlying
+ character type of <code class="computeroutput">str</code>
 </dd>
-<dt><tt class="computeroutput">tuple<></tt></dt>
+<dt><code class="computeroutput">tuple<></code></dt>
<dd>
 Used as a placeholder for a fusion sequence
 </dd>
-<dt><tt class="computeroutput">vector<></tt></dt>
+<dt><code class="computeroutput">vector<></code></dt>
<dd>
 Used as a placeholder for an STL container
 </dd>
-<dt><tt class="computeroutput">variant<></tt></dt>
+<dt><code class="computeroutput">variant<></code></dt>
<dd>
 Used as a placeholder for a boost::variant
 </dd>
-<dt><tt class="computeroutput">optional<></tt></dt>
+<dt><code class="computeroutput">optional<></code></dt>
<dd>
 Used as a placeholder for a boost::optional
 </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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<link rel="home" href="../../../index.html" title="Spirit 2.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" 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">
@@ -25,49 +23,51 @@
<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="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>

 The notation will be for instance:
 
<pre class="programlisting">a: A, b: B --> (a >> b): tuple<A, B>
</pre>

- which reads as: given, <tt class="computeroutput">a</tt>
- and <tt class="computeroutput">b</tt> are parsers/generators,
- and <tt class="computeroutput">A</tt> is the type of the
- attribute of <tt class="computeroutput">a</tt>, and <tt class="computeroutput">B</tt> is the type of the attribute of <tt class="computeroutput">b</tt>, then the type of the attribute of
- <tt class="computeroutput">a >>
- b</tt> will be <tt class="computeroutput">tuple<A, B></tt>.
+ which reads as: given, <code class="computeroutput">a</code>
+ and <code class="computeroutput">b</code> are parsers/generators,
+ and <code class="computeroutput">A</code> is the type of the
+ attribute of <code class="computeroutput">a</code>, and <code class="computeroutput">B</code> is the type of the attribute of <code class="computeroutput">b</code>, then the type of the attribute of
+ <code class="computeroutput">a >>
+ b</code> will be <code class="computeroutput">tuple<A, B></code>.
 
<div class="table">
-<a name="id456662"></a>Table 5. /Spirit.Karma/ compound generator attribute types
-<table class="table" summary="/Spirit.Karma/ compound generator attribute types">
+<a name="id2646816"></a>Table 5. Spirit.Karma compound generator attribute types
+<div class="table-contents"><table class="table" summary="Spirit.Karma compound generator attribute types">
<colgroup>
<col>
<col>
</colgroup>
<thead><tr>
-<th>
+<th>
+ 
 Expression
- </th>
-<th>
+ 
+ </th>
+<th>
+ 
 Attribute
- </th>
+ 
+ </th>
</tr></thead>
<tbody>
<tr>
-<td>
- sequence (<tt class="computeroutput"><<</tt>)
- </td>
<td>
-
+ 
+ sequence (<code class="computeroutput"><<</code>)
+ 
+ </td>
+<td>
+ 


<pre class="programlisting">a: A, b: B --> (a << b): tuple<A, B>
@@ -77,14 +77,16 @@
a: A, b: A --> (a << b): vector<A></pre>

 
-</td>
+ </td>
</tr>
<tr>
-<td>
- alternative (<tt class="computeroutput">|</tt>)
- </td>
<td>
-
+ 
+ alternative (<code class="computeroutput">|</code>)
+ 
+ </td>
+<td>
+ 


<pre class="programlisting">a: A, b: B --> (a | b): variant<A, B>
@@ -94,101 +96,120 @@

 a: A, b: A --> (a | b): A`
 
-</td>
+ </td>
</tr>
<tr>
-<td>
- kleene (<tt class="computeroutput">*</tt>)
- </td>
<td>
-
+ 
+ kleene (<code class="computeroutput">*</code>)
+ 
+ </td>
+<td>
+ 


<pre class="programlisting">a: A --> *a: vector<A>
a: Unused --> a: Unused</pre>

 
-</td>
+ </td>
</tr>
<tr>
-<td>
- plus (<tt class="computeroutput">+</tt>)
- </td>
<td>
-
+ 
+ plus (<code class="computeroutput">+</code>)
+ 
+ </td>
+<td>
+ 


<pre class="programlisting">a: A --> +a: vector<A>
a: Unused --> a: Unused</pre>

 
-</td>
+ </td>
</tr>
<tr>
-<td>
- list (<tt class="computeroutput">%</tt>)
- </td>
<td>
-
+ 
+ list (<code class="computeroutput">%</code>)
+ 
+ </td>
+<td>
+ 


<pre class="programlisting">a: A, b: B --> (a % b): vector<A>
a: Unused, b: B --> (a % b): Unused</pre>

 
-</td>
+ </td>
</tr>
<tr>
-<td>
+<td>
+ 
 repetition
- </td>
+ 
+ </td>
<td>
-
+ 


<pre class="programlisting">a: A --> repeat(...,...)[a]: vector<A>
a: Unused --> repeat(...,...)[a]: Unused</pre>

 
-</td>
+ </td>
</tr>
<tr>
-<td>
- optional (<tt class="computeroutput">-</tt>)
- </td>
<td>
-
+ 
+ optional (<code class="computeroutput">-</code>)
+ 
+ </td>
+<td>
+ 


<pre class="programlisting">a: A --> -a: optional<A>
a: Unused --> -a: Unused</pre>

 
-</td>
+ </td>
</tr>
<tr>
-<td>
- and predicate (<tt class="computeroutput">&</tt>)
- </td>
-<td>
- <tt class="computeroutput">a:
+<td>
+ 
+ and predicate (<code class="computeroutput">&</code>)
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">a:
 A -->
- &a: Unused</tt>
- </td>
+ &a: Unused</code>
+ 
+ </td>
</tr>
<tr>
-<td>
- not predicate (<tt class="computeroutput">!</tt>)
- </td>
-<td>
- <tt class="computeroutput">a:
+<td>
+ 
+ not predicate (<code class="computeroutput">!</code>)
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">a:
 A -->
- !a: Unused</tt>
- </td>
+ !a: Unused</code>
+ 
+ </td>
</tr>
</tbody>
-</table>
+</table></div>
</div>
+ 
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>

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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<link rel="home" href="../../../index.html" title="Spirit 2.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" 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">
@@ -24,26 +23,23 @@
<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="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>

 For all expressions of the form:
 
<pre class="programlisting">p(a1, a2,... aN)
</pre>

- where <tt class="computeroutput">p</tt> is a parser, each
+ where <code class="computeroutput">p</code> is a parser, each
 of the arguments (a1...aN) can either be an immediate value, or a lazy
 function with signature:
 
<pre class="programlisting">T(Unused, Context)
</pre>

- where <tt class="computeroutput">T</tt>, the function's
+ where <code class="computeroutput">T</code>, the function's
 return value, is compatible with the argument type expected. For example,
 this is a valid expression:
 
@@ -57,8 +53,8 @@
 // of flag at parse time
</pre>

- since <tt class="computeroutput">phoenix::ref(f)</tt> is
- a function that returns a <tt class="computeroutput">bool</tt>.
+ since <code class="computeroutput">phoenix::ref(f)</code> is
+ a function that returns a <code class="computeroutput">bool</code>.
 
</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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<link rel="home" href="../../../index.html" title="Spirit 2.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" 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>
@@ -24,42 +23,39 @@
<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="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">
Notation
<dl>
-<dt><tt class="computeroutput">RT</tt></dt>
+<dt><code class="computeroutput">RT</code></dt>
<dd>
 Synthesized attribute. The rule or grammar's return type.
 </dd>
-<dt><tt class="computeroutput">Arg1</tt>,
- <tt class="computeroutput">Arg2</tt>, <tt class="computeroutput">ArgN</tt></dt>
+<dt><code class="computeroutput">Arg1</code>,
+ <code class="computeroutput">Arg2</code>, <code class="computeroutput">ArgN</code></dt>
<dd>
 Inherited attributes. Zero or more or arguments.
 </dd>
-<dt><tt class="computeroutput">L1</tt>,
- <tt class="computeroutput">L2</tt>, <tt class="computeroutput">LN</tt></dt>
+<dt><code class="computeroutput">L1</code>,
+ <code class="computeroutput">L2</code>, <code class="computeroutput">LN</code></dt>
<dd>
 Zero or more local variables.
 </dd>
-<dt><tt class="computeroutput">r, r2</tt></dt>
+<dt><code class="computeroutput">r, r2</code></dt>
<dd>
 Rules
 </dd>
-<dt><tt class="computeroutput">g</tt></dt>
+<dt><code class="computeroutput">g</code></dt>
<dd>
 A grammar
 </dd>
-<dt><tt class="computeroutput">p</tt></dt>
+<dt><code class="computeroutput">p</code></dt>
<dd>
 A parser expression
 </dd>
-<dt><tt class="computeroutput">my_grammar</tt></dt>
+<dt><code class="computeroutput">my_grammar</code></dt>
<dd>
 A user defined grammar
 </dd>
@@ -70,14 +66,14 @@
<dl>
<dt>Signature</dt>
<dd>
- <tt class="computeroutput">RT(Arg1, Arg2 ...
- ,ArgN)</tt>. The signature specifies the synthesized
+ <code class="computeroutput">RT(Arg1, Arg2 ...
+ ,ArgN)</code>. The signature specifies the synthesized
 (return value) and inherited (arguments) attributes.
 </dd>
<dt>Locals</dt>
<dd>
- <tt class="computeroutput">locals<L1, L2 ...,
- LN></tt>.
+ <code class="computeroutput">locals<L1, L2 ...,
+ LN></code>.
 The local variables.
 </dd>
<dt>Skipper</dt>
@@ -89,12 +85,12 @@
<div class="variablelist">
Template Arguments
<dl>
-<dt><tt class="computeroutput">Iterator</tt></dt>
+<dt><code class="computeroutput">Iterator</code></dt>
<dd>
 The iterator type you will use for parsing.
 </dd>
-<dt><tt class="computeroutput">A1</tt>,
- <tt class="computeroutput">A2</tt>, <tt class="computeroutput">A3</tt></dt>
+<dt><code class="computeroutput">A1</code>,
+ <code class="computeroutput">A2</code>, <code class="computeroutput">A3</code></dt>
<dd>
 Can be one of 1)Signature 2)Locals 3)Skipper.
 </dd>
@@ -106,120 +102,164 @@
<col>
</colgroup>
<thead><tr>
-<th>
+<th>
+ 
 Expression
- </th>
-<th>
+ 
+ </th>
+<th>
+ 
 Description
- </th>
+ 
+ </th>
</tr></thead>
<tbody>
<tr>
-<td>
- <tt class="computeroutput">rule<Iterator,
+<td>
+ 
+ <code class="computeroutput">rule<Iterator,
 A1,
 A2,
 A3>
- r(name);</tt>
- </td>
-<td>
- Rule declaration. <tt class="computeroutput">Iterator</tt>
- is required. <tt class="computeroutput">A1, A2, A3</tt>
- are optional and can be specified in any order. <tt class="computeroutput">name</tt>
+ r(name);</code>
+ 
+ </td>
+<td>
+ 
+ Rule declaration. <code class="computeroutput">Iterator</code>
+ is required. <code class="computeroutput">A1, A2, A3</code>
+ are optional and can be specified in any order. <code class="computeroutput">name</code>
 is an optional string that gives the rule its name, useful for
 debugging and error handling.
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">rule<Iterator,
+<td>
+ 
+ <code class="computeroutput">rule<Iterator,
 A1,
 A2,
 A3>
- r(r2);</tt>
- </td>
-<td>
- Copy construct rule <tt class="computeroutput">r</tt>
- from rule <tt class="computeroutput">r2</tt>.
- <tt class="computeroutput">boost::shared_ptr</tt> semantics.
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">r =
- r2;</tt>
- </td>
-<td>
- Assign rule <tt class="computeroutput">r2</tt>
- to <tt class="computeroutput">r</tt>. <tt class="computeroutput">boost::shared_ptr</tt> semantics.
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">r.alias()</tt>
- </td>
-<td>
- return an alias of <tt class="computeroutput">r</tt>.
- The alias is a parser that holds a reference to <tt class="computeroutput">r</tt>.
+ r(r2);</code>
+ 
+ </td>
+<td>
+ 
+ Copy construct rule <code class="computeroutput">r</code>
+ from rule <code class="computeroutput">r2</code>.
+ <code class="computeroutput">boost::shared_ptr</code> semantics.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">r =
+ r2;</code>
+ 
+ </td>
+<td>
+ 
+ Assign rule <code class="computeroutput">r2</code>
+ to <code class="computeroutput">r</code>. <code class="computeroutput">boost::shared_ptr</code> semantics.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">r.alias()</code>
+ 
+ </td>
+<td>
+ 
+ return an alias of <code class="computeroutput">r</code>.
+ The alias is a parser that holds a reference to <code class="computeroutput">r</code>.
 Reference semantics.
- </td>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">r.copy()</code>
+ 
+ </td>
+<td>
+ 
+ Get a copy of <code class="computeroutput">r</code>.
+ <code class="computeroutput">boost::shared_ptr</code> semantics.
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">r.copy()</tt>
- </td>
-<td>
- Get a copy of <tt class="computeroutput">r</tt>.
- <tt class="computeroutput">boost::shared_ptr</tt> semantics.
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">r.name(name)</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">r.name(name)</code>
+ 
+ </td>
+<td>
+ 
 Naming a rule
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">r.name()</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">r.name()</code>
+ 
+ </td>
+<td>
+ 
 Getting the name of a rule
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
+<td>
+ 
 debug(r)
- </td>
-<td>
- Debug rule <tt class="computeroutput">r</tt>
- </td>
+ 
+ </td>
+<td>
+ 
+ Debug rule <code class="computeroutput">r</code>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">r =
- p;</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">r =
+ p;</code>
+ 
+ </td>
+<td>
+ 
 Rule definition
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">r %=
- p;</tt>
- </td>
-<td>
- Auto-rule definition. The attribute of <tt class="computeroutput">p</tt>
- should be compatible with the synthesized attribute of <tt class="computeroutput">r</tt>. When <tt class="computeroutput">p</tt>
- is successful, its attribute is automatically propagated to <tt class="computeroutput">r</tt>'s synthesized attribute.
- </td>
+<td>
+ 
+ <code class="computeroutput">r %=
+ p;</code>
+ 
+ </td>
+<td>
+ 
+ Auto-rule definition. The attribute of <code class="computeroutput">p</code>
+ should be compatible with the synthesized attribute of <code class="computeroutput">r</code>. When <code class="computeroutput">p</code>
+ is successful, its attribute is automatically propagated to <code class="computeroutput">r</code>'s synthesized attribute.
+ 
+ </td>
</tr>
<tr>
<td>
-
+ 


<pre xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="table-programlisting">template <typename Iterator>
@@ -237,36 +277,50 @@
</pre>

 
-</td>
-<td>
- Grammar definition. <tt class="computeroutput">name</tt>
+ </td>
+<td>
+ 
+ Grammar definition. <code class="computeroutput">name</code>
 is an optional string that gives the grammar its name, useful for
 debugging and error handling.
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
+<td>
+ 
 my_grammar<Iterator> g
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 Instantiating a grammar
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">g.name(name)</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">g.name(name)</code>
+ 
+ </td>
+<td>
+ 
 Naming a grammar
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">g.name()</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">g.name()</code>
+ 
+ </td>
+<td>
+ 
 Getting the name of a grammar
- </td>
+ 
+ </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-06-23 00:30:19 EDT (Tue, 23 Jun 2009)
@@ -3,12 +3,11 @@
<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">
-<link rel="home" href="../../../index.html" title="Spirit 2.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" 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="next" href="../../lex.html" title=" Spirit.Lex">
+<link rel="prev" href="semantic_actions.html" title="Semantic Actions">
+<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>
@@ -24,12 +23,9 @@
<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="../../lex.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="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>

 __boostphoenix_ makes it easier to
 attach semantic actions. You just inline your lambda expressions:
@@ -38,37 +34,37 @@
</pre>

 Spirit.Qi provides some __boostphoenix_
- placeholders to important information from the <tt class="computeroutput">Attr</tt>
- and <tt class="computeroutput">Context</tt> that are otherwise
+ placeholders to important information from the <code class="computeroutput">Attr</code>
+ and <code class="computeroutput">Context</code> that are otherwise
 fiddly to extract.
 
<div class="variablelist">
Spirit.Qi specific Phoenix placeholders
<dl>
-<dt><tt class="computeroutput">_1, _2... , _N</tt></dt>
+<dt><code class="computeroutput">_1, _2... , _N</code></dt>
<dd>
- Nth attribute of <tt class="computeroutput">p</tt>
+ Nth attribute of <code class="computeroutput">p</code>
 </dd>
-<dt><tt class="computeroutput">_val</tt></dt>
+<dt><code class="computeroutput">_val</code></dt>
<dd>
 The enclosing rule's synthesized attribute.
 </dd>
-<dt><tt class="computeroutput">_r1, _r2... , _rN</tt></dt>
+<dt><code class="computeroutput">_r1, _r2... , _rN</code></dt>
<dd>
 The enclosing rule's Nth inherited attribute.
 </dd>
-<dt><tt class="computeroutput">_a, _b... , _j</tt></dt>
+<dt><code class="computeroutput">_a, _b... , _j</code></dt>
<dd>
- The enclosing rule's local variables (<tt class="computeroutput">_a</tt>
+ The enclosing rule's local variables (<code class="computeroutput">_a</code>
 refers to the first).
 </dd>
-<dt><tt class="computeroutput">_val</tt></dt>
+<dt><code class="computeroutput">_val</code></dt>
<dd>
 The enclosing rule's synthesized attribute.
 </dd>
-<dt><tt class="computeroutput">_pass</tt></dt>
+<dt><code class="computeroutput">_pass</code></dt>
<dd>
- Assign <tt class="computeroutput">false</tt> to <tt class="computeroutput">_pass</tt> to force a parser failure.
+ Assign <code class="computeroutput">false</code> to <code class="computeroutput">_pass</code> to force a parser failure.
 </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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<link rel="home" href="../../../index.html" title="Spirit 2.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" 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>
@@ -26,14 +23,10 @@
<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="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>
+<th>
+ 
 Expression
- </th>
-<th>
+ 
+ </th>
+<th>
+ 
 Attribute
- </th>
-<th>
+ 
+ </th>
+<th>
+ 
 Description
- </th>
+ 
+ </th>
</tr></thead>
<tbody>
<tr>
-<td>
- <tt class="computeroutput">eol</tt>
- </td>
-<td>
- <tt class="computeroutput">Unused</tt>
- </td>
-<td>
- Generates the end of line (<tt class="computeroutput">\n</tt>)
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">eps</tt>
- </td>
-<td>
- <tt class="computeroutput">Unused</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">eol</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">Unused</code>
+ 
+ </td>
+<td>
+ 
+ Generates the end of line (<code class="computeroutput">\n</code>)
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">eps</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">Unused</code>
+ 
+ </td>
+<td>
+ 
 Generate an empty string
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">eps(b)</tt>
- </td>
-<td>
- <tt class="computeroutput">Unused</tt>
- </td>
-<td>
- If <tt class="computeroutput">b</tt> is true, generate
+<td>
+ 
+ <code class="computeroutput">eps(b)</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">Unused</code>
+ 
+ </td>
+<td>
+ 
+ If <code class="computeroutput">b</code> is true, generate
 an empty string
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">lazy(fg)</tt>
- </td>
-<td>
- Attribute of <tt class="computeroutput">G</tt>
- where <tt class="computeroutput">G</tt> is the
- return type of <tt class="computeroutput">fg</tt>
- </td>
-<td>
- Invoke <tt class="computeroutput">fg</tt> at generation
- time, returning a generator <tt class="computeroutput">g</tt>
+<td>
+ 
+ <code class="computeroutput">lazy(fg)</code>
+ 
+ </td>
+<td>
+ 
+ Attribute of <code class="computeroutput">G</code>
+ where <code class="computeroutput">G</code> is the
+ return type of <code class="computeroutput">fg</code>
+ 
+ </td>
+<td>
+ 
+ Invoke <code class="computeroutput">fg</code> at generation
+ time, returning a generator <code class="computeroutput">g</code>
 which is then called to generate.
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">fg</tt>
- </td>
-<td>
- see <tt class="computeroutput">lazy(fg)</tt>
+<td>
+ 
+ <code class="computeroutput">fg</code>
+ 
+ </td>
+<td>
+ 
+ see <code class="computeroutput">lazy(fg)</code>
 above
- </td>
-<td>
- Equivalent to <tt class="computeroutput">lazy[fp]</tt>
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">g[fa]</tt>
- </td>
-<td>
- Attribute of <tt class="computeroutput">g</tt>
- </td>
-<td>
- Call semantic action <tt class="computeroutput">fa</tt>
- (before executing <tt class="computeroutput">g</tt>).
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">byte_</tt>
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
+ Equivalent to <code class="computeroutput">lazy[fp]</code>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">g[fa]</code>
+ 
+ </td>
+<td>
+ 
+ Attribute of <code class="computeroutput">g</code>
+ 
+ </td>
+<td>
+ 
+ Call semantic action <code class="computeroutput">fa</code>
+ (before executing <code class="computeroutput">g</code>).
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">byte_</code>
+ 
+ </td>
+<td>
+ 
 8 bits native endian
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 Generates an 8 bit binary
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">word</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">word</code>
+ 
+ </td>
+<td>
+ 
 16 bits native endian
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 Generates a 16 bit binary
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">big_word</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">big_word</code>
+ 
+ </td>
+<td>
+ 
 16 bits big endian
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 Generates a 16 bit binary
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">little_word</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">little_word</code>
+ 
+ </td>
+<td>
+ 
 16 bits little endian
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 Generates a 16 bit binary
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">dword</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">dword</code>
+ 
+ </td>
+<td>
+ 
 32 bits native endian
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 Generates a 32 bit binary
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">big_dword</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">big_dword</code>
+ 
+ </td>
+<td>
+ 
 32 bits big endian
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 Generates a 32 bit binary
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">little_dword</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">little_dword</code>
+ 
+ </td>
+<td>
+ 
 32 bits little endian
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 Generates a 32 bit binary
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">qword</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">qword</code>
+ 
+ </td>
+<td>
+ 
 64 bits native endian
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 Generates a 64 bit binary
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">big_qword</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">big_qword</code>
+ 
+ </td>
+<td>
+ 
 64 bits big endian
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 Generates a 64 bit binary
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">little_qword</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">little_qword</code>
+ 
+ </td>
+<td>
+ 
 64 bits little endian
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 Generates a 64 bit binary
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">char_(ch)</tt>
- </td>
-<td>
- <tt class="computeroutput">Ch</tt>
- </td>
-<td>
- Generates <tt class="computeroutput">ch</tt>
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">char_("c")</tt>
- </td>
-<td>
- <tt class="computeroutput">Ch</tt>
- </td>
-<td>
- Generates a single char string literal, <tt class="computeroutput">c</tt>
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">ch</tt>
- </td>
-<td>
- <tt class="computeroutput">Unused</tt>
- </td>
-<td>
- Generates <tt class="computeroutput">ch</tt>
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">str</tt>
- </td>
-<td>
- <tt class="computeroutput">Unused</tt>
- </td>
-<td>
- Generates <tt class="computeroutput">str</tt>
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">lit(ch)</tt>
- </td>
-<td>
- <tt class="computeroutput">Unused</tt>
- </td>
-<td>
- Generates <tt class="computeroutput">ch</tt>
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">lit(str)</tt>
- </td>
-<td>
- <tt class="computeroutput">Unused</tt>
- </td>
-<td>
- Generates <tt class="computeroutput">str</tt>
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">string(str)</tt>
- </td>
-<td>
- <tt class="computeroutput">Str</tt>
- </td>
-<td>
- Generates <tt class="computeroutput">str</tt>
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">lower[a]</tt>
- </td>
-<td>
- <tt class="computeroutput">A</tt>
- </td>
-<td>
- Generate <tt class="computeroutput">a</tt> as lower
+<td>
+ 
+ <code class="computeroutput">char_(ch)</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">Ch</code>
+ 
+ </td>
+<td>
+ 
+ Generates <code class="computeroutput">ch</code>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">char_("c")</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">Ch</code>
+ 
+ </td>
+<td>
+ 
+ Generates a single char string literal, <code class="computeroutput">c</code>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">ch</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">Unused</code>
+ 
+ </td>
+<td>
+ 
+ Generates <code class="computeroutput">ch</code>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">str</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">Unused</code>
+ 
+ </td>
+<td>
+ 
+ Generates <code class="computeroutput">str</code>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">lit(ch)</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">Unused</code>
+ 
+ </td>
+<td>
+ 
+ Generates <code class="computeroutput">ch</code>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">lit(str)</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">Unused</code>
+ 
+ </td>
+<td>
+ 
+ Generates <code class="computeroutput">str</code>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">string(str)</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">Str</code>
+ 
+ </td>
+<td>
+ 
+ Generates <code class="computeroutput">str</code>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">lower[a]</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">A</code>
+ 
+ </td>
+<td>
+ 
+ Generate <code class="computeroutput">a</code> as lower
 case
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">upper[a]</tt>
- </td>
-<td>
- <tt class="computeroutput">A</tt>
- </td>
-<td>
- Generate <tt class="computeroutput">a</tt> as upper
+<td>
+ 
+ <code class="computeroutput">upper[a]</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">A</code>
+ 
+ </td>
+<td>
+ 
+ Generate <code class="computeroutput">a</code> as upper
 case
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">left_align[a]</tt>
- </td>
-<td>
- <tt class="computeroutput">A</tt>
- </td>
-<td>
- Generate <tt class="computeroutput">a</tt> left
+<td>
+ 
+ <code class="computeroutput">left_align[a]</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">A</code>
+ 
+ </td>
+<td>
+ 
+ Generate <code class="computeroutput">a</code> left
 aligned in column of width BOOST_KARMA_DEFAULT_FIELD_LENGTH
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">left_align(N)[a]</tt>
- </td>
-<td>
- <tt class="computeroutput">A</tt>
- </td>
-<td>
- Generate <tt class="computeroutput">a</tt> left
- aligned in column of width <tt class="computeroutput">N</tt>
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">left_align(N,
- g)[a]</tt>
- </td>
-<td>
- <tt class="computeroutput">A</tt>
- </td>
-<td>
- Generate <tt class="computeroutput">a</tt> left
- aligned in column of width <tt class="computeroutput">N</tt>
- while using <tt class="computeroutput">g</tt> to
+<td>
+ 
+ <code class="computeroutput">left_align(N)[a]</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">A</code>
+ 
+ </td>
+<td>
+ 
+ Generate <code class="computeroutput">a</code> left
+ aligned in column of width <code class="computeroutput">N</code>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">left_align(N,
+ g)[a]</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">A</code>
+ 
+ </td>
+<td>
+ 
+ Generate <code class="computeroutput">a</code> left
+ aligned in column of width <code class="computeroutput">N</code>
+ while using <code class="computeroutput">g</code> to
 generate the necesssary padding
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">right_align[a]</tt>
- </td>
-<td>
- <tt class="computeroutput">A</tt>
- </td>
-<td>
- Generate <tt class="computeroutput">a</tt> right
+<td>
+ 
+ <code class="computeroutput">right_align[a]</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">A</code>
+ 
+ </td>
+<td>
+ 
+ Generate <code class="computeroutput">a</code> right
 aligned in column of width BOOST_KARMA_DEFAULT_FIELD_LENGTH
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">right_align(N)[a]</tt>
- </td>
-<td>
- <tt class="computeroutput">A</tt>
- </td>
-<td>
- Generate <tt class="computeroutput">a</tt> right
- aligned in column of width <tt class="computeroutput">N</tt>
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">right_align(N,
- g)[a]</tt>
- </td>
-<td>
- <tt class="computeroutput">A</tt>
- </td>
-<td>
- Generate <tt class="computeroutput">a</tt> right
- aligned in column of width <tt class="computeroutput">N</tt>
- while using <tt class="computeroutput">g</tt> to
+<td>
+ 
+ <code class="computeroutput">right_align(N)[a]</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">A</code>
+ 
+ </td>
+<td>
+ 
+ Generate <code class="computeroutput">a</code> right
+ aligned in column of width <code class="computeroutput">N</code>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">right_align(N,
+ g)[a]</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">A</code>
+ 
+ </td>
+<td>
+ 
+ Generate <code class="computeroutput">a</code> right
+ aligned in column of width <code class="computeroutput">N</code>
+ while using <code class="computeroutput">g</code> to
 generate the necesssary padding
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">center[a]</tt>
- </td>
-<td>
- <tt class="computeroutput">A</tt>
- </td>
-<td>
- Generate <tt class="computeroutput">a</tt> centered
+<td>
+ 
+ <code class="computeroutput">center[a]</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">A</code>
+ 
+ </td>
+<td>
+ 
+ Generate <code class="computeroutput">a</code> centered
 in column of width BOOST_KARMA_DEFAULT_FIELD_LENGTH
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">center(N)[a]</tt>
- </td>
-<td>
- <tt class="computeroutput">A</tt>
- </td>
-<td>
- Generate <tt class="computeroutput">a</tt> centered
- in column of width <tt class="computeroutput">N</tt>
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">center(N,
- g)[a]</tt>
- </td>
-<td>
- <tt class="computeroutput">A</tt>
- </td>
-<td>
- Generate <tt class="computeroutput">a</tt> centered
- in column of width <tt class="computeroutput">N</tt>
- while using <tt class="computeroutput">g</tt> to
+<td>
+ 
+ <code class="computeroutput">center(N)[a]</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">A</code>
+ 
+ </td>
+<td>
+ 
+ Generate <code class="computeroutput">a</code> centered
+ in column of width <code class="computeroutput">N</code>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">center(N,
+ g)[a]</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">A</code>
+ 
+ </td>
+<td>
+ 
+ Generate <code class="computeroutput">a</code> centered
+ in column of width <code class="computeroutput">N</code>
+ while using <code class="computeroutput">g</code> to
 generate the necesssary padding
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">maxwidth[a]</tt>
- </td>
-<td>
- <tt class="computeroutput">A</tt>
- </td>
-<td>
- Generate <tt class="computeroutput">a</tt> truncated
+<td>
+ 
+ <code class="computeroutput">maxwidth[a]</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">A</code>
+ 
+ </td>
+<td>
+ 
+ Generate <code class="computeroutput">a</code> truncated
 to column of width BOOST_KARMA_DEFAULT_FIELD_MAXWIDTH
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">maxwidth(N)[a]</tt>
- </td>
-<td>
- <tt class="computeroutput">A</tt>
- </td>
-<td>
- Generate <tt class="computeroutput">a</tt> truncated
- to column of width <tt class="computeroutput">N</tt>
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">repeat[a]</tt>
- </td>
-<td>
- <tt class="computeroutput">vector<A></tt>
- </td>
-<td>
- Repeat <tt class="computeroutput">a</tt> zero or
+<td>
+ 
+ <code class="computeroutput">maxwidth(N)[a]</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">A</code>
+ 
+ </td>
+<td>
+ 
+ Generate <code class="computeroutput">a</code> truncated
+ to column of width <code class="computeroutput">N</code>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">repeat[a]</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">vector<A></code>
+ 
+ </td>
+<td>
+ 
+ Repeat <code class="computeroutput">a</code> zero or
 more times
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">repeat(N)[a]</tt>
- </td>
-<td>
- <tt class="computeroutput">vector<A></tt>
- </td>
-<td>
- Repeat <tt class="computeroutput">a</tt> <tt class="computeroutput">N</tt> times
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">repeat(N,
- M)[a]</tt>
- </td>
-<td>
- <tt class="computeroutput">vector<A></tt>
- </td>
-<td>
- Repeat <tt class="computeroutput">a</tt> <tt class="computeroutput">N</tt> to <tt class="computeroutput">M</tt>
+<td>
+ 
+ <code class="computeroutput">repeat(N)[a]</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">vector<A></code>
+ 
+ </td>
+<td>
+ 
+ Repeat <code class="computeroutput">a</code> <code class="computeroutput">N</code> times
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">repeat(N,
+ M)[a]</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">vector<A></code>
+ 
+ </td>
+<td>
+ 
+ Repeat <code class="computeroutput">a</code> <code class="computeroutput">N</code> to <code class="computeroutput">M</code>
 times
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">repeat(N,
- inf)[a]</tt>
- </td>
-<td>
- <tt class="computeroutput">vector<A></tt>
- </td>
-<td>
- Repeat <tt class="computeroutput">a</tt> <tt class="computeroutput">N</tt> or more times
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">verbatim[a]</tt>
- </td>
-<td>
- <tt class="computeroutput">A</tt>
- </td>
-<td>
- Disable delimited generation for <tt class="computeroutput">a</tt>
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">delimit[a]</tt>
- </td>
-<td>
- <tt class="computeroutput">A</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">repeat(N,
+ inf)[a]</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">vector<A></code>
+ 
+ </td>
+<td>
+ 
+ Repeat <code class="computeroutput">a</code> <code class="computeroutput">N</code> or more times
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">verbatim[a]</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">A</code>
+ 
+ </td>
+<td>
+ 
+ Disable delimited generation for <code class="computeroutput">a</code>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">delimit[a]</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">A</code>
+ 
+ </td>
+<td>
+ 
 Reestablish the delimiter that got inhibited by verbatim
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">delimit(g)[a]</tt>
- </td>
-<td>
- <tt class="computeroutput">A</tt>
- </td>
-<td>
- Use <tt class="computeroutput">g</tt> as a skipper
- for generating <tt class="computeroutput">a</tt>
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">float_</tt>
- </td>
-<td>
- <tt class="computeroutput">float</tt>
- </td>
-<td>
- Generate a floating point number from a <tt class="computeroutput">float</tt>
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">double_</tt>
- </td>
-<td>
- <tt class="computeroutput">double</tt>
- </td>
-<td>
- Generate a floating point number from a <tt class="computeroutput">double</tt>
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">long_double</tt>
- </td>
-<td>
- <tt class="computeroutput">long double</tt>
- </td>
-<td>
- Generate a floating point number from a <tt class="computeroutput">long
- double</tt>
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">bin</tt>
- </td>
-<td>
- <tt class="computeroutput">unsigned</tt>
- </td>
-<td>
- Generate a binary integer from an <tt class="computeroutput">unsigned</tt>
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">oct</tt>
- </td>
-<td>
- <tt class="computeroutput">unsigned</tt>
- </td>
-<td>
- Generate an octal integer from an <tt class="computeroutput">unsigned</tt>
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">hex</tt>
- </td>
-<td>
- <tt class="computeroutput">unsigned</tt>
- </td>
-<td>
- Generate a hexadecimal integer from an <tt class="computeroutput">unsigned</tt>
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">ushort_</tt>
- </td>
-<td>
- <tt class="computeroutput">unsigned short</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">delimit(g)[a]</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">A</code>
+ 
+ </td>
+<td>
+ 
+ Use <code class="computeroutput">g</code> as a skipper
+ for generating <code class="computeroutput">a</code>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">float_</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">float</code>
+ 
+ </td>
+<td>
+ 
+ Generate a floating point number from a <code class="computeroutput">float</code>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">double_</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">double</code>
+ 
+ </td>
+<td>
+ 
+ Generate a floating point number from a <code class="computeroutput">double</code>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">long_double</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">long double</code>
+ 
+ </td>
+<td>
+ 
+ Generate a floating point number from a <code class="computeroutput">long
+ double</code>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">bin</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">unsigned</code>
+ 
+ </td>
+<td>
+ 
+ Generate a binary integer from an <code class="computeroutput">unsigned</code>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">oct</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">unsigned</code>
+ 
+ </td>
+<td>
+ 
+ Generate an octal integer from an <code class="computeroutput">unsigned</code>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">hex</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">unsigned</code>
+ 
+ </td>
+<td>
+ 
+ Generate a hexadecimal integer from an <code class="computeroutput">unsigned</code>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">ushort_</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">unsigned short</code>
+ 
+ </td>
+<td>
+ 
 Generate an unsigned short integer
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">ulong_</tt>
- </td>
-<td>
- <tt class="computeroutput">unsigned long</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">ulong_</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">unsigned long</code>
+ 
+ </td>
+<td>
+ 
 Generate an unsigned long integer
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">uint_</tt>
- </td>
-<td>
- <tt class="computeroutput">unsigned int</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">uint_</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">unsigned int</code>
+ 
+ </td>
+<td>
+ 
 Generate an unsigned int
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">ulong_long</tt>
- </td>
-<td>
- <tt class="computeroutput">unsigned long
- long</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">ulong_long</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">unsigned long
+ long</code>
+ 
+ </td>
+<td>
+ 
 Generate an unsigned long long
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">short_</tt>
- </td>
-<td>
- <tt class="computeroutput">short</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">short_</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">short</code>
+ 
+ </td>
+<td>
+ 
 Generate a short integer
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">long_</tt>
- </td>
-<td>
- <tt class="computeroutput">long</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">long_</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">long</code>
+ 
+ </td>
+<td>
+ 
 Generate a long integer
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">int_</tt>
- </td>
-<td>
- <tt class="computeroutput">int</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">int_</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">int</code>
+ 
+ </td>
+<td>
+ 
 Generate an int
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">long_long</tt>
- </td>
-<td>
- <tt class="computeroutput">long long</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">long_long</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">long long</code>
+ 
+ </td>
+<td>
+ 
 Generate a long long
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">!a</tt>
- </td>
-<td>
- <tt class="computeroutput">Unused</tt>
- </td>
-<td>
- Not predicate. Ensure that <tt class="computeroutput">a</tt>
+<td>
+ 
+ <code class="computeroutput">!a</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">Unused</code>
+ 
+ </td>
+<td>
+ 
+ Not predicate. Ensure that <code class="computeroutput">a</code>
 does not succeed generating but don't create any output
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">&a</tt>
- </td>
-<td>
- <tt class="computeroutput">Unused</tt>
- </td>
-<td>
- And predicate. Ensure that <tt class="computeroutput">a</tt>
+<td>
+ 
+ <code class="computeroutput">&a</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">Unused</code>
+ 
+ </td>
+<td>
+ 
+ And predicate. Ensure that <code class="computeroutput">a</code>
 does succeed generating but don't create any output
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">-a</tt>
- </td>
-<td>
- <tt class="computeroutput">optional<A></tt>
- </td>
-<td>
- Optional. Generate <tt class="computeroutput">a</tt>
+<td>
+ 
+ <code class="computeroutput">-a</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">optional<A></code>
+ 
+ </td>
+<td>
+ 
+ Optional. Generate <code class="computeroutput">a</code>
 zero or one time
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">*a</tt>
- </td>
-<td>
- <tt class="computeroutput">vector<A></tt>
- </td>
-<td>
- Kleene. Generate <tt class="computeroutput">a</tt>
+<td>
+ 
+ <code class="computeroutput">*a</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">vector<A></code>
+ 
+ </td>
+<td>
+ 
+ Kleene. Generate <code class="computeroutput">a</code>
 zero or more times
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">+a</tt>
- </td>
-<td>
- <tt class="computeroutput">vector<A></tt>
- </td>
-<td>
- Plus. Generate <tt class="computeroutput">a</tt>
+<td>
+ 
+ <code class="computeroutput">+a</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">vector<A></code>
+ 
+ </td>
+<td>
+ 
+ Plus. Generate <code class="computeroutput">a</code>
 one or more times
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">a |
- b</tt>
- </td>
-<td>
- <tt class="computeroutput">variant<A,
- B></tt>
- </td>
-<td>
- Alternative. Generate <tt class="computeroutput">a</tt>
- or <tt class="computeroutput">b</tt>
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">a <<
- b</tt>
- </td>
-<td>
- <tt class="computeroutput">tuple<A,
- B></tt>
- </td>
-<td>
- Sequence. Generate <tt class="computeroutput">a</tt>
- followed by <tt class="computeroutput">b</tt>
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">a %
- b</tt>
- </td>
-<td>
- <tt class="computeroutput">vector<A></tt>
- </td>
-<td>
- List. Generate <tt class="computeroutput">a</tt>
- delimited <tt class="computeroutput">b</tt> one
+<td>
+ 
+ <code class="computeroutput">a |
+ b</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">variant<A,
+ B></code>
+ 
+ </td>
+<td>
+ 
+ Alternative. Generate <code class="computeroutput">a</code>
+ or <code class="computeroutput">b</code>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">a <<
+ b</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">tuple<A,
+ B></code>
+ 
+ </td>
+<td>
+ 
+ Sequence. Generate <code class="computeroutput">a</code>
+ followed by <code class="computeroutput">b</code>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">a %
+ b</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">vector<A></code>
+ 
+ </td>
+<td>
+ 
+ List. Generate <code class="computeroutput">a</code>
+ delimited <code class="computeroutput">b</code> one
 or more times
- </td>
+ 
+ </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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<link rel="home" href="../../../index.html" title="Spirit 2.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" 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">
@@ -24,21 +23,17 @@
<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="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>

 Has the form:
 
<pre class="programlisting">p[f]
</pre>

- where <tt class="computeroutput">f</tt> is a function with
+ where <code class="computeroutput">f</code> is a function with
 the signatures:
 
<pre class="programlisting">void f(Attr const&);
@@ -46,7 +41,7 @@
void f(Attr const&, Context&, bool&);
</pre>

- 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:
 
@@ -55,7 +50,7 @@
void operator()(Attr const&, Context&, bool&) const;
</pre>

- The <tt class="computeroutput">unused_type</tt> is used
+ The <code class="computeroutput">unused_type</code> is used
 in the signatures above to signify 'don't care'.
 
</div>

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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<link rel="home" href="../index.html" title="Spirit 2.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" href="../index.html" title="Spirit 2.1">
<link rel="up" href="../index.html" title="Spirit 2.1">
-<link rel="previous" href="karma/quick_reference/phoenix.html" title="Phoenix">
-<link rel="next" href="lex/lexer_introduction.html" title=" Introduction to Spirit.Lex">
+<link rel="prev" href="karma/quick_reference/phoenix.html" title="Phoenix">
+<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>
@@ -23,12 +23,9 @@
<a accesskey="p" href="karma/quick_reference/phoenix.html"><img src="../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="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="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="spirit.lex"></a><a class="link" href="lex.html" title="Spirit.Lex"> Spirit.Lex</a>
+</h2></div></div></div>
<div class="toc"><dl>
<dt> Introduction to Spirit.Lex</dt>
<dt><a href="lex/tutorials.html"> Spirit.Lex

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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<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">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" href="../../index.html" title="Spirit 2.1">
+<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">
@@ -24,12 +23,9 @@
<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="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>Lexer Primitives</dt>
<dt><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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<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">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" href="../../../index.html" title="Spirit 2.1">
+<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" lang="en"><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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<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">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" href="../../../index.html" title="Spirit 2.1">
+<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" lang="en"><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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<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">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" href="../../../index.html" title="Spirit 2.1">
+<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>
@@ -24,12 +23,9 @@
<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="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><a href="lexer_primitives/lexer_primitives.html">
Lexer Primitives</a></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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<link rel="home" href="../../../../index.html" title="Spirit 2.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" 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" lang="en"><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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<link rel="home" href="../../../../index.html" title="Spirit 2.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" 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" lang="en"><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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<link rel="home" href="../../../../index.html" title="Spirit 2.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" 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>
@@ -26,14 +23,10 @@
<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="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>

 As already discussed, lexical scanning is the process of analyzing the
 stream of input characters and separating it into strings called tokens,
@@ -49,23 +42,23 @@
 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">lexertl_token<></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 Spirit.Lex library.
 
<a name="spirit.lex.abstracts.lexer_primitives.lexer_token_values.the_anatomy_of_a_token"></a><h6>
-<a name="id474470"></a>
- <a href="lexer_token_values.html#spirit.lex.abstracts.lexer_primitives.lexer_token_values.the_anatomy_of_a_token">The
+<a name="id2662273"></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>

 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">token_def<></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">lexertl_token<></code></a>
 template).
 

@@ -101,32 +94,31 @@
 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.
 

 
<div class="figure">
<a name="spirit.lex.tokenstructure"></a>Figure 5. The structure of a token
-<img src="./images/tokenstructure.png" alt="The
- structure of a token">
+<div class="figure-contents"><img src="../../../.././images/tokenstructure.png" alt="The structure of a token"></div>
</div>
-
+ 
 

 The token value and the token state 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<> template while defining
+ <a class="link" href="../../reference/token_class.html" title="Token Class"><code class="computeroutput">lexertl_token<></code></a> template while defining
 the token type.
 

 The lexer iterator returns the same token type for each of the different
 matched token definitions. To accomodate for the possibly different token
 value 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.
 
@@ -135,13 +127,13 @@
<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">
 If the lexical analyzer is used in conjunction with a Spirit.Qi
- 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 Spirit.Qi, even
@@ -149,7 +141,7 @@
 </td></tr>
</table></div>

- 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">lexertl_token<></code></a>
 template:
 
<pre class="programlisting">template <
@@ -165,22 +157,22 @@
<dt>Iterator</dt>
<dd>
 This is the type of the iterator used to access the underlying input
- stream. It defaults to a plain <tt class="computeroutput">char
- const*</tt>.
+ stream. It defaults to a plain <code class="computeroutput">char
+ const*</code>.
 </dd>
<dt>AttributeTypes</dt>
<dd>
 This is either a mpl sequence containing all attribute types used
- for the token definitions or the type <tt class="computeroutput">omitted</tt>.
+ for the token definitions or the type <code class="computeroutput">omitted</code>.
 If the mpl sequence is empty (which is the default), all token instances
- will store a <tt class="computeroutput">boost::iterator_range<Iterator></tt> pointing to the start and the
- end of the matched section in the input stream. If the type is <tt class="computeroutput">omitted</tt>, the generated tokens will
+ will store a <code class="computeroutput">boost::iterator_range<Iterator></code> pointing to the start and the
+ end of the matched section in the input stream. If the type is <code class="computeroutput">omitted</code>, the generated tokens will
 contain no token value (attribute) at all.
 </dd>
<dt>HasState</dt>
<dd>
- This is either <tt class="computeroutput">mpl::true_</tt>
- or <tt class="computeroutput">mpl::false_</tt>, allowing to control whether
+ This is either <code class="computeroutput">mpl::true_</code>
+ or <code class="computeroutput">mpl::false_</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>

 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">omitted</tt> token value type). This iterator
+ boost::iterator_range<>
+ as its token value (except, if it has been defined using the <code class="computeroutput">omitted</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.
 
<a name="spirit.lex.abstracts.lexer_primitives.lexer_token_values.the_physiognomy_of_a_token_definition"></a><h6>
-<a name="id475277"></a>
- <a href="lexer_token_values.html#spirit.lex.abstracts.lexer_primitives.lexer_token_values.the_physiognomy_of_a_token_definition">The
+<a name="id2663017"></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>

- 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">token_def<></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 Spirit.Qi.
@@ -223,17 +215,17 @@
 instances representing this token type. This attribute type is exposed
 to the Spirit.Qi library, whenever this token
 definition is used as a parser component. The default attribute type
- is <tt class="computeroutput">unused_type</tt>, which
- means the token instance holds a boost::iterator_range<>
+ is <code class="computeroutput">unused_type</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">omitted</tt>
+ stream. If the attribute is <code class="computeroutput">omitted</code>
 the token instance will expose no token type at all. Any other type
 will be used directly as the token value type.
 </dd>
<dt>Char</dt>
<dd>
 This is the value type of the iterator for the underlying input sequence.
- It defaults to <tt class="computeroutput">char</tt>.
+ It defaults to <code class="computeroutput">char</code>.
 </dd>
</dl>
</div>
@@ -241,7 +233,7 @@
 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">identifier</tt> or <tt class="computeroutput">integer</tt>).
+ everything related to a single specific token type (such as <code class="computeroutput">identifier</code> or <code class="computeroutput">integer</code>).
 On the other hand the token type is used to define the general proerties
 of all token instances generated by the Spirit.Lex
 library.
@@ -251,26 +243,26 @@
<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">

 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.
 

 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">token_def<></code></a>
 declarations in the token definition class, otherwise compilation errors
 will occur.
 
</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="id475687"></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="id2663381"></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">lexertl_token<></code></a></a>
 </h6>

 Let's start with some examples. We refer to one of the Spirit.Lex
@@ -279,13 +271,13 @@

 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">if_</tt>,
- <tt class="computeroutput">else_</tt>, and <tt class="computeroutput">while_</tt>). Their token value will always
+ not expose a special token value (<code class="computeroutput">if_</code>,
+ <code class="computeroutput">else_</code>, and <code class="computeroutput">while_</code>). Their token value will always
 hold the iterator range of the matched input sequence only. The token
- definitions for the <tt class="computeroutput">identifier</tt>
- and the integer <tt class="computeroutput">constant</tt>
- are specialized to expose an explicit token type each: <tt class="computeroutput">std::string</tt> and <tt class="computeroutput">unsigned
- int</tt>.
+ definitions for the <code class="computeroutput">identifier</code>
+ and the integer <code class="computeroutput">constant</code>
+ are specialized to expose an explicit token type each: <code class="computeroutput">std::string</code> and <code class="computeroutput">unsigned
+ int</code>.
 

 
@@ -318,7 +310,7 @@

 As the parsers generated by Spirit.Qi are fully
 attributed, any Spirit.Qi 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">token_def<></code></a> exposes the token value
 type as its parser attribute, enabling a smooth integration with Spirit.Qi.
 

@@ -354,9 +346,9 @@

 

- To avoid the token to have a token value at all, the special tag <tt class="computeroutput">omitted</tt> can be used: <tt class="computeroutput">token_def<omitted></tt>
- and <tt class="computeroutput">lexertl_token<base_iterator_type,
- omitted></tt>.
+ To avoid the token to have a token value at all, the special tag <code class="computeroutput">omitted</code> can be used: <code class="computeroutput">token_def<omitted></code>
+ and <code class="computeroutput">lexertl_token<base_iterator_type,
+ omitted></code>.
 
</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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<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">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" href="../../../index.html" title="Spirit 2.1">
+<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,14 +22,439 @@
<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" lang="en">
+<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></div>
+</h4></div></div></div>
+
+ The main task of a lexer normally is to recognize tokens in the input.
+ Traditionally this has been complemented with the possibility to execute
+ arbitrary code whenever a certain token has been detected. Spirit.Lex
+ has been designed to support this mode of operation as well. We borrow
+ from the concept of semantic actions for parsers (Spirit.Qi)
+ and generators (Spirit.Karma). 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 <code class="computeroutput">D</code>,
+ and a C++ function <code class="computeroutput">f</code>, you
+ can make the lexer call <code class="computeroutput">f</code>
+ whenever it matches an input by attaching <code class="computeroutput">f</code>:
+ 
+<pre class="programlisting">D[f]
+</pre>
+
+ The expression above links <code class="computeroutput">f</code>
+ to the token definition, <code class="computeroutput">D</code>.
+ The required prototype of <code class="computeroutput">f</code>
+ is:
+ 
+<pre class="programlisting">void f (Iterator& start, Iterator& end, pass_flag& matched, Idtype& id, Context& ctx);
+</pre>
+<div class="variablelist">
+where:
+<dl>
+<dt><code class="computeroutput">Iterator& start</code></dt>
+<dd>
+ 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 <code class="computeroutput">lexertl_lexer<...></code> (its first template parameter).
+ The semantic action is allowed to change the value of this iterator
+ influencing, the matched input sequence.
+ </dd>
+<dt><code class="computeroutput">Iterator& end</code></dt>
+<dd>
+ 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 <code class="computeroutput">lexertl_lexer<...></code> (its first template parameter).
+ The semantic action is allowed to change the value of this iterator
+ influencing, the matched input sequence.
+ </dd>
+<dt><code class="computeroutput">pass_flag& matched</code></dt>
+<dd>
+ This value is pre/initialized to <code class="computeroutput">pass_normal</code>.
+ If the semantic action sets it to <code class="computeroutput">pass_fail</code>
+ the behaves as if the token has not been matched in the first place.
+ If the semantic action sets this to <code class="computeroutput">pass_ignore</code>
+ the lexer ignores the current token and tries to match a next token
+ from the input.
+ </dd>
+<dt><code class="computeroutput">Idtype& id</code></dt>
+<dd>
+ This is the token id of the type Idtype (most of the time this will
+ be a <code class="computeroutput">std::size_t</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.
+ </dd>
+<dt><code class="computeroutput">Context& ctx</code></dt>
+<dd>
+ 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
+ internal data items and is needed for lexer state control from inside
+ a semantic action.
+ </dd>
+</dl>
+</div>
+
+ When using a C++ function as the semantic action the following prototypes
+ are allowed as well:
+ 
+<pre class="programlisting">void f (Iterator& start, Iterator& end, pass_flag& matched, Idtype& id);
+void f (Iterator& start, Iterator& end, pass_flag& matched);
+void f (Iterator& start, Iterator& end);
+void f ();
+</pre>
+<a name="spirit.lex.abstracts.lexer_semantic_actions.the_context_of_a_lexer_semantic_action"></a><h6>
+<a name="id2667673"></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>
+ </h6>
+
+ The last parameter passed to any lexer semantic action is a reference to
+ an unspecified type (see the <code class="computeroutput">Context</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
+ is expected to expose a couple of functions allowing to influence the behavior
+ of the lexer. The following table gives an overview and a short description
+ of the available functionality.
+ 
+<div class="table">
+<a name="id2667713"></a>Table 6. Functions exposed by any context passed to a lexer
+ semantic action
+<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>
+ 
+ Name
+ 
+ </th>
+<th>
+ 
+ Description
+ 
+ </th>
+</tr></thead>
+<tbody>
+<tr>
+<td>
+ 
+ <code class="computeroutput">Iterator const& get_eoi() const</code>
+ 
+ </td>
+<td>
+ 
+ The function <code class="computeroutput">get_eoi()</code> may be used by to access the end
+ iterator of the input stream the lexer has been initialized with
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">void more()</code>
+ 
+ </td>
+<td>
+ 
+ The function <code class="computeroutput">more()</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.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">Iterator const& less(Iterator
+ const&
+ it,
+ int n)</code>
+ 
+ </td>
+<td>
+ 
+ The function <code class="computeroutput">less()</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 <code class="computeroutput">end</code> it is possible to return all
+ but the first n characters of the current token back to the input
+ stream.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">bool lookahead(std::size_t
+ id)</code>
+ 
+ </td>
+<td>
+ 
+ The function <code class="computeroutput">lookahead()</code> can be for instance used to implement
+ lookahead for lexer engines not supporting constructs like flex'
+ <code class="computeroutput">a/b</code> (match <code class="computeroutput">a</code>,
+ but only when followed by <code class="computeroutput">b</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
+ <code class="computeroutput">id</code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">std::size_t get_state() const</code>
+ and <code class="computeroutput">void set_state(std::size_t
+ state)</code>
+ 
+ </td>
+<td>
+ 
+ The functions <code class="computeroutput">get_state()</code> and <code class="computeroutput">set_state()</code> may be used to introspect and change
+ the current lexer state.
+ 
+ </td>
+</tr>
+</tbody>
+</table></div>
+</div>
+ <a name="spirit.lex.abstracts.lexer_semantic_actions.lexer_semantic_actions_using_phoenix"></a><h6>
+<a name="id2668262"></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>
+ </h6>
+
+ 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
+ lexer semantic actions is to use Phoenix2.
+ In this case you can access the parameters described above by using the
+ predefined Spirit placeholders:
+ 
+<div class="table">
+<a name="id2668299"></a>Table 7. Predefined Phoenix placeholders for lexer semantic
+ actions
+<div class="table-contents"><table class="table" summary="Predefined Phoenix placeholders for lexer semantic
+ actions">
+<colgroup>
+<col>
+<col>
+</colgroup>
+<thead><tr>
+<th>
+ 
+ Placeholder
+ 
+ </th>
+<th>
+ 
+ Description
+ 
+ </th>
+</tr></thead>
+<tbody>
+<tr>
+<td>
+ 
+ <code class="computeroutput">_start</code>
+ 
+ </td>
+<td>
+ 
+ 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.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">_end</code>
+ 
+ </td>
+<td>
+ 
+ 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.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">_pass</code>
+ 
+ </td>
+<td>
+ 
+ References the value signaling the outcome of the semantic action.
+ This is pre-initialized to <code class="computeroutput">lex::pass_flags::pass_normal</code>.
+ If this is set to <code class="computeroutput">lex::pass_flags::pass_fail</code>,
+ the lexer will behave as if no token has been matched, if is set
+ to <code class="computeroutput">lex::pass_flags::pass_ignore</code>, the lexer will ignore
+ the current match and proceed trying to match tokens from the input.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">_tokenid</code>
+ 
+ </td>
+<td>
+ 
+ Refers to the token id of the token to be generated. Any modifications
+ to this value will be reflected in the generated token.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">_state</code>
+ 
+ </td>
+<td>
+ 
+ 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.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">_eoi</code>
+ 
+ </td>
+<td>
+ 
+ References the end iterator of the overall lexer input. This value
+ cannot be changed.
+ 
+ </td>
+</tr>
+</tbody>
+</table></div>
+</div>
+ 
+ The context object passed as the last parameter to any lexer semantic action
+ is not directly accessible while using Phoenix2
+ expressions. We rather provide predefine Phoenix functions allowing to
+ invoke the different support functions as mentioned above. The following
+ table lists the available support functions and describes their functionality:
+ 
+<div class="table">
+<a name="id2668617"></a>Table 8. Support functions usable from Phoenix expressions
+ inside lexer semantic actions
+<div class="table-contents"><table class="table" summary="Support functions usable from Phoenix expressions
+ inside lexer semantic actions">
+<colgroup>
+<col>
+<col>
+<col>
+</colgroup>
+<thead><tr>
+<th>
+ 
+ Plain function
+ 
+ </th>
+<th>
+ 
+ Phoenix function
+ 
+ </th>
+<th>
+ 
+ Description
+ 
+ </th>
+</tr></thead>
+<tbody>
+<tr>
+<td>
+ 
+ <code class="computeroutput">ctx.more()</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">more()</code>
+ 
+ </td>
+<td>
+ 
+ The function <code class="computeroutput">more()</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.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">ctx.less()</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">less(n)</code>
+ 
+ </td>
+<td>
+ 
+ The function <code class="computeroutput">less()</code> takes a single integer parameter
+ <code class="computeroutput">n</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
+ <code class="computeroutput">_end</code> it is possible
+ to return all but the first <code class="computeroutput">n</code>
+ characters of the current token back to the input stream.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">ctx.lookahead()</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">lookahead(std::size_t)</code>
+ or <code class="computeroutput">lookahead(token_def)</code>
+ 
+ </td>
+<td>
+ 
+ The function <code class="computeroutput">lookahead()</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' <code class="computeroutput">a/b</code> (match <code class="computeroutput">a</code>,
+ but only when followed by <code class="computeroutput">b</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.
+ 
+ </td>
+</tr>
+</tbody>
+</table></div>
+</div>
+ 
+</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
<td align="right"><div class="copyright-footer">Copyright © 2001-2009 Joel

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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<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">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" href="../../../index.html" title="Spirit 2.1">
+<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>
@@ -23,27 +23,24 @@
<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="id482984"></a>
- <a href="lexer_states.html#spirit.lex.abstracts.lexer_states.controlling_the_lexer_state_from_lexer_semantic_actions">Controlling
+<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="id2672168"></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="id483010"></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="id2672193"></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="id483038"></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="id2672216"></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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<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">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" href="../../../index.html" title="Spirit 2.1">
+<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>
@@ -26,14 +23,10 @@
<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 Static
+<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 Static
 Lexer Model</a>
-</h4></div></div>
-<div></div>
-</div>
+</h4></div></div></div>

 The documentation of Spirit.Lex so far mostly was
 about describing the features of the dynamic model,
@@ -132,8 +125,8 @@

 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">lexertl_lexer<></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">lexertl_static_lexer<></code></a>
 type as the template parameter.
 

@@ -182,17 +175,17 @@
 

 
-<a name="spirit.lex.abstracts.lexer_static_model.generating_the_static_analyzer"></a><h5>
-<a name="id481125"></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="id2670469"></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>

 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
 Spirit.Lex library exposes a special API - the function
- generate_static().
+ <a class="link" href="../../../"><code class="computeroutput">generate_static()</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).
 
-<a name="spirit.lex.abstracts.lexer_static_model.modifying_the_dynamic_analyzer"></a><h5>
-<a name="id481589"></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="id2670892"></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>

 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">lexertl_lexer<></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">lexertl_static_lexer<></code></a>
 type. The second change is tightly related to the first one and involves
- correcting the corresponding <tt class="computeroutput">#include</tt>
+ correcting the corresponding <code class="computeroutput">#include</code>
 statement to:

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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<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">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" href="../../../index.html" title="Spirit 2.1">
+<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>
@@ -26,27 +23,22 @@
<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="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="id476495"></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="id2664124"></a>
+ <a class="link" href="lexer_tokenizing.html#spirit.lex.abstracts.lexer_tokenizing.the_tokenize_function">The
 tokenize function</a>
- </h5>
+ </h6>

- The <tt class="computeroutput">tokenize()</tt>
+ The <code class="computeroutput">tokenize()</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 Spirit.Lex</a>.
 As a reminder, here is the token definition class:
 
@@ -87,7 +79,7 @@

 The construct used to tokenize the given input, while discarding all generated
 tokens is a common application of the lexer. For this reason Spirit.Lex
- exposes an API function <tt class="computeroutput">tokenize()</tt> minimizing the code required:
+ exposes an API function <code class="computeroutput">tokenize()</code> minimizing the code required:
 
<pre class="programlisting">// Read input from the given file
std::string str (read_from_file(1 == argc ? "word_count.input" : argv[1]));
@@ -100,15 +92,14 @@
</pre>

 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 Spirit.Lex</a>.
- The function <tt class="computeroutput">tokenize()</tt>
+ The function <code class="computeroutput">tokenize()</code>
 will return either if the end of the input has been reached (in this case
- the return value will be <tt class="computeroutput">true</tt>),
+ the return value will be <code class="computeroutput">true</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">false</tt>
- and the iterator <tt class="computeroutput">first</tt>
+ (in this case the return value will be <code class="computeroutput">false</code>
+ and the iterator <code class="computeroutput">first</code>
 will point to the first not matched character in the input sequence).
 

@@ -143,7 +134,7 @@
</dl>
</div>

- A second overload of the <tt class="computeroutput">tokenize()</tt> function allows to specify any arbitrary
+ A second overload of the <code class="computeroutput">tokenize()</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 @@

 

- The main function simply loads the given file into memory (as a <tt class="computeroutput">std::string</tt>), instantiates an instance of
- the token definition template using the correct iterator type (<tt class="computeroutput">word_count_tokens<char const*></tt>), and finally calls <tt class="computeroutput">lex::tokenize</tt>, passing an instance of the
- counter function object. The return value of <tt class="computeroutput">lex::tokenize()</tt> will be <tt class="computeroutput">true</tt>
- if the whole input sequence has been successfully tokenized, and <tt class="computeroutput">false</tt> otherwise.
+ The main function simply loads the given file into memory (as a <code class="computeroutput">std::string</code>), instantiates an instance of
+ the token definition template using the correct iterator type (<code class="computeroutput">word_count_tokens<char const*></code>), and finally calls <code class="computeroutput">lex::tokenize</code>, passing an instance of the
+ counter function object. The return value of <code class="computeroutput">lex::tokenize()</code> will be <code class="computeroutput">true</code>
+ if the whole input sequence has been successfully tokenized, and <code class="computeroutput">false</code> otherwise.
 

 
@@ -198,7 +189,7 @@

 

- Here is the prototype of this <tt class="computeroutput">tokenize()</tt> function overload:
+ Here is the prototype of this <code class="computeroutput">tokenize()</code> function overload:
 
<pre class="programlisting">template <typename Iterator, typename Lexer, typename F>
bool tokenize(Iterator& first, Iterator last, Lexer const& lex, F f
@@ -224,10 +215,10 @@
<dt>F f</dt>
<dd>
 A function or function object to be called for each matched token.
- This function is expected to have the prototype: <tt class="computeroutput">bool
- f(Lexer::token_type);</tt>
- and should return <tt class="computeroutput">false</tt>
- if the supplied token instance is invald (the <tt class="computeroutput">tokenize()</tt> function will return immediatly).
+ This function is expected to have the prototype: <code class="computeroutput">bool
+ f(Lexer::token_type);</code>
+ and should return <code class="computeroutput">false</code>
+ if the supplied token instance is invald (the <code class="computeroutput">tokenize()</code> function will return immediatly).
 </dd>
<dt>Lexer::char_type const* initial_state</dt>
<dd>
@@ -236,11 +227,11 @@
 </dd>
</dl>
</div>
-<a name="spirit.lex.abstracts.lexer_tokenizing.the_generate_static_function"></a><h5>
-<a name="id479500"></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="id2666848"></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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<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">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" href="../../index.html" title="Spirit 2.1">
+<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>
@@ -24,12 +23,9 @@
<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="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 Spirit.Lex</a>
+</h3></div></div></div>

 Lexical scanning is the process of analyzing the stream of input characters
 and separating it into strings called tokens, separated by whitespace. Most
@@ -49,7 +45,7 @@
 </li>
<li>
 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>
@@ -59,11 +55,11 @@
 is not perfect.
 </li>
</ul></div>
-<a name="spirit.lex.lexer_introduction.why_use_a_separate_lexer_"></a><h4>
-<a name="id461595"></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="id2651275"></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>

 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
@@ -158,11 +154,11 @@
 it is even possible to use the provided functionality to build more complex
 grammar recognizers.
 
-<a name="spirit.lex.lexer_introduction.advantages_of_using__emphasis_spirit_lex__emphasis_"></a><h4>
-<a name="id461933"></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="id2651596"></a>
+ <a class="link" href="lexer_introduction.html#spirit.lex.lexer_introduction.advantages_of_using__emphasis_spirit_lex__emphasis_">Advantages
 of using Spirit.Lex</a>
- </h4>
+ </h5>

 The advantage of using Spirit.Lex to create the lexical
 analyzer over using more traditional tools such as Flex
@@ -195,8 +191,7 @@
 Even if it is possible to use Spirit.Lex to generate
 C++ code representing the lexical analyzer (we will refer to that as the
 static model, described in more detail in the section
- <a href="abstracts/lexer_static_model.html" title=" The Static
- Lexer Model">The Static
+ <a class="link" href="abstracts/lexer_static_model.html" title="The Static Lexer Model">The Static
 Model</a>) - a model very similar to the way Flex
 operates - we will mainly focus on the opposite, the dynamic
 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.
 
-<a name="spirit.lex.lexer_introduction.the_library_structure_of__emphasis_spirit_lex__emphasis_"></a><h4>
-<a name="id462104"></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="id2651753"></a>
+ <a class="link" href="lexer_introduction.html#spirit.lex.lexer_introduction.the_library_structure_of__emphasis_spirit_lex__emphasis_">The
 Library Structure of Spirit.Lex</a>
- </h4>
+ </h5>

- 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 Spirit.Lex library might be used
 in an application. Spirit.Lex 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>Figure 3. The Library structure and Common Flow of Information while
 using Spirit.Lex in an application
-<img src="./images/lexerflow.png" alt="The
- Library structure and Common Flow of Information while using Spirit.Lex
- in an application">
+<div class="figure-contents"><img src="../.././images/lexerflow.png" alt="The Library structure and Common Flow of Information while using Spirit.Lex in an application"></div>
</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/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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<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">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" href="../../index.html" title="Spirit 2.1">
+<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" lang="en"><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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<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">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" href="../../index.html" title="Spirit 2.1">
+<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>
@@ -23,12 +23,9 @@
<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="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> Concepts</dt>
<dt>Lexer Class</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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<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">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" href="../../../index.html" title="Spirit 2.1">
+<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">
@@ -23,12 +23,9 @@
<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="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>Lexer</dt>
<dt>Token</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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<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">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" href="../../../../index.html" title="Spirit 2.1">
+<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">
@@ -23,374 +23,515 @@
<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="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="id483131"></a>Table 6. Regular expressions support
-<table class="table" summary="Regular expressions support">
+<a name="id2672299"></a>Table 9. Regular expressions support
+<div class="table-contents"><table class="table" summary="Regular expressions support">
<colgroup>
<col>
<col>
</colgroup>
<thead><tr>
-<th>
+<th>
+ 
 Expression
- </th>
-<th>
+ 
+ </th>
+<th>
+ 
 Meaning
- </th>
+ 
+ </th>
</tr></thead>
<tbody>
<tr>
-<td>
- <tt class="computeroutput">x</tt>
- </td>
-<td>
- Match any character <tt class="computeroutput">x</tt>
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">.</tt>
- </td>
-<td>
- Match any except newline (or optionally any
+<td>
+ 
+ <code class="computeroutput">x</code>
+ 
+ </td>
+<td>
+ 
+ Match any character <code class="computeroutput">x</code>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">.</code>
+ 
+ </td>
+<td>
+ 
+ Match any except newline (or optionally any
 character)
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">[xyz]</tt>
- </td>
-<td>
- A character class; in this case matches <tt class="computeroutput">x</tt>,
- <tt class="computeroutput">y</tt> or <tt class="computeroutput">z</tt>
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">[abj-oZ]</tt>
- </td>
-<td>
- A character class with a range in it; matches <tt class="computeroutput">a</tt>,
- <tt class="computeroutput">b</tt> any letter from
- <tt class="computeroutput">j</tt> through <tt class="computeroutput">o</tt> or a <tt class="computeroutput">Z</tt>
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">[^A-Z]</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">[xyz]</code>
+ 
+ </td>
+<td>
+ 
+ A character class; in this case matches <code class="computeroutput">x</code>,
+ <code class="computeroutput">y</code> or <code class="computeroutput">z</code>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">[abj-oZ]</code>
+ 
+ </td>
+<td>
+ 
+ A character class with a range in it; matches <code class="computeroutput">a</code>,
+ <code class="computeroutput">b</code> any letter from
+ <code class="computeroutput">j</code> through <code class="computeroutput">o</code> or a <code class="computeroutput">Z</code>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">[^A-Z]</code>
+ 
+ </td>
+<td>
+ 
 A negated character class i.e. any character but those in the class.
 In this case, any character except an uppercase letter
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">r*</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">r*</code>
+ 
+ </td>
+<td>
+ 
 Zero or more r's (greedy), where r is any regular expression
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">r*?</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">r*?</code>
+ 
+ </td>
+<td>
+ 
 Zero or more r's (abstemious), where r is any regular expression
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">r+</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">r+</code>
+ 
+ </td>
+<td>
+ 
 One or more r's (greedy)
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">r+?</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">r+?</code>
+ 
+ </td>
+<td>
+ 
 One or more r's (abstemious)
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">r?</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">r?</code>
+ 
+ </td>
+<td>
+ 
 Zero or one r's (greedy), i.e. optional
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">r??</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">r??</code>
+ 
+ </td>
+<td>
+ 
 Zero or one r's (abstemious), i.e. optional
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">r{2,5}</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">r{2,5}</code>
+ 
+ </td>
+<td>
+ 
 Anywhere between two and five r's (greedy)
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">r{2,5}?</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">r{2,5}?</code>
+ 
+ </td>
+<td>
+ 
 Anywhere between two and five r's (abstemious)
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">r{2,}</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">r{2,}</code>
+ 
+ </td>
+<td>
+ 
 Two or more r's (greedy)
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">r{2,}?</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">r{2,}?</code>
+ 
+ </td>
+<td>
+ 
 Two or more r's (abstemious)
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">r{4}</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">r{4}</code>
+ 
+ </td>
+<td>
+ 
 Exactly four r's
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">{NAME}</tt>
- </td>
-<td>
- The macro <tt class="computeroutput">NAME</tt>
+<td>
+ 
+ <code class="computeroutput">{NAME}</code>
+ 
+ </td>
+<td>
+ 
+ The macro <code class="computeroutput">NAME</code>
 (see below)
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">"[xyz]\"foo"</tt>
- </td>
-<td>
- The literal string <tt class="computeroutput">[xyz]\"foo</tt>
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">\X</tt>
- </td>
-<td>
- If X is <tt class="computeroutput">a</tt>, <tt class="computeroutput">b</tt>, <tt class="computeroutput">e</tt>,
- <tt class="computeroutput">n</tt>, <tt class="computeroutput">r</tt>, <tt class="computeroutput">f</tt>,
- <tt class="computeroutput">t</tt>, <tt class="computeroutput">v</tt> then the ANSI-C interpretation
- of <tt class="computeroutput">\x</tt>.
- Otherwise a literal <tt class="computeroutput">X</tt>
- (used to escape operators such as <tt class="computeroutput">*</tt>)
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">\0</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">"[xyz]\"foo"</code>
+ 
+ </td>
+<td>
+ 
+ The literal string <code class="computeroutput">[xyz]\"foo</code>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">\X</code>
+ 
+ </td>
+<td>
+ 
+ If X is <code class="computeroutput">a</code>, <code class="computeroutput">b</code>, <code class="computeroutput">e</code>,
+ <code class="computeroutput">n</code>, <code class="computeroutput">r</code>, <code class="computeroutput">f</code>,
+ <code class="computeroutput">t</code>, <code class="computeroutput">v</code> then the ANSI-C interpretation
+ of <code class="computeroutput">\x</code>.
+ Otherwise a literal <code class="computeroutput">X</code>
+ (used to escape operators such as <code class="computeroutput">*</code>)
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">\0</code>
+ 
+ </td>
+<td>
+ 
 A NUL character (ASCII code 0)
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">\123</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">\123</code>
+ 
+ </td>
+<td>
+ 
 The character with octal value 123
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">\x2a</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">\x2a</code>
+ 
+ </td>
+<td>
+ 
 The character with hexadecimal value 2a
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">\cX</tt>
- </td>
-<td>
- A named control character <tt class="computeroutput">X</tt>.
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">\d</tt>
- </td>
-<td>
- A shortcut for <tt class="computeroutput">[0-9]</tt>
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">\D</tt>
- </td>
-<td>
- A shortcut for <tt class="computeroutput">[^0-9]</tt>
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">\s</tt>
- </td>
-<td>
- A shortcut for <tt class="computeroutput">[\x20\t\n\r\f\v]</tt>
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">\S</tt>
- </td>
-<td>
- A shortcut for <tt class="computeroutput">[^\x20\t\n\r\f\v]</tt>
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">\w</tt>
- </td>
-<td>
- A shortcut for <tt class="computeroutput">[a-zA-Z0-9_]</tt>
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">\W</tt>
- </td>
-<td>
- A shortcut for <tt class="computeroutput">[^a-zA-Z0-9_]</tt>
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">(r)</tt>
- </td>
-<td>
- Match an <tt class="computeroutput">r</tt>; parenthesis
+<td>
+ 
+ <code class="computeroutput">\cX</code>
+ 
+ </td>
+<td>
+ 
+ A named control character <code class="computeroutput">X</code>.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">\d</code>
+ 
+ </td>
+<td>
+ 
+ A shortcut for <code class="computeroutput">[0-9]</code>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">\D</code>
+ 
+ </td>
+<td>
+ 
+ A shortcut for <code class="computeroutput">[^0-9]</code>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">\s</code>
+ 
+ </td>
+<td>
+ 
+ A shortcut for <code class="computeroutput">[\x20\t\n\r\f\v]</code>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">\S</code>
+ 
+ </td>
+<td>
+ 
+ A shortcut for <code class="computeroutput">[^\x20\t\n\r\f\v]</code>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">\w</code>
+ 
+ </td>
+<td>
+ 
+ A shortcut for <code class="computeroutput">[a-zA-Z0-9_]</code>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">\W</code>
+ 
+ </td>
+<td>
+ 
+ A shortcut for <code class="computeroutput">[^a-zA-Z0-9_]</code>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">(r)</code>
+ 
+ </td>
+<td>
+ 
+ Match an <code class="computeroutput">r</code>; parenthesis
 are used to override precedence (see below)
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">(?r-s:pattern)</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">(?r-s:pattern)</code>
+ 
+ </td>
+<td>
+ 
 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">\n</tt>'.
- </td>
+ alters the meaning of '.' to match any character except '<code class="computeroutput">\n</code>'.
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">rs</tt>
- </td>
-<td>
- The regular expression <tt class="computeroutput">r</tt>
- followed by the regular expression <tt class="computeroutput">s</tt>
+<td>
+ 
+ <code class="computeroutput">rs</code>
+ 
+ </td>
+<td>
+ 
+ The regular expression <code class="computeroutput">r</code>
+ followed by the regular expression <code class="computeroutput">s</code>
 (a sequence)
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">r|s</tt>
- </td>
-<td>
- Either an <tt class="computeroutput">r</tt> or
- and <tt class="computeroutput">s</tt>
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">^r</tt>
- </td>
-<td>
- An <tt class="computeroutput">r</tt> but only at
+<td>
+ 
+ <code class="computeroutput">r|s</code>
+ 
+ </td>
+<td>
+ 
+ Either an <code class="computeroutput">r</code> or
+ and <code class="computeroutput">s</code>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">^r</code>
+ 
+ </td>
+<td>
+ 
+ An <code class="computeroutput">r</code> but only at
 the beginning of a line (i.e. when just starting to scan, or right
 after a newline has been scanned)
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">r</tt>$
- </td>
-<td>
- An <tt class="computeroutput">r</tt> but only at
+<td>
+ 
+ <code class="computeroutput">r</code>$
+ 
+ </td>
+<td>
+ 
+ An <code class="computeroutput">r</code> but only at
 the end of a line (i.e. just before a newline)
- </td>
+ 
+ </td>
</tr>
</tbody>
-</table>
+</table></div>
</div>
-<div class="note"><table border="0" summary="Note">
+ <div class="note"><table border="0" summary="Note">
<tr>
<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../../../../images/note.png"></td>
<th align="left">Note</th>
</tr>
-<tr><td colspan="2" align="left" valign="top">
+<tr><td align="left" valign="top">
 POSIX character classes are not currently supported, due to performance
 issues when creating them in wide character mode.
 </td></tr>
</table></div>
<a name="spirit.lex.reference.concepts.lexer.regular_expression_precedence"></a><h6>
-<a name="id485221"></a>
- <a href="lexer.html#spirit.lex.reference.concepts.lexer.regular_expression_precedence">Regular
+<a name="id2674195"></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">rs</tt> has highest precedence
+<code class="computeroutput">rs</code> has highest precedence
 </li>
<li>
-<tt class="computeroutput">r*</tt>
- has next highest (<tt class="computeroutput">+</tt>,
- <tt class="computeroutput">?</tt>, <tt class="computeroutput">{n,m}</tt>
- have the same precedence as <tt class="computeroutput">*</tt>)
+<code class="computeroutput">r*</code>
+ has next highest (<code class="computeroutput">+</code>,
+ <code class="computeroutput">?</code>, <code class="computeroutput">{n,m}</code>
+ have the same precedence as <code class="computeroutput">*</code>)
 </li>
<li>
-<tt class="computeroutput">r|s</tt> has the lowest precedence
+<code class="computeroutput">r|s</code> has the lowest precedence
 </li>
</ul></div>
<a name="spirit.lex.reference.concepts.lexer.macros"></a><h6>
-<a name="id485378"></a>
- Macros
+<a name="id2674337"></a>
+ <a class="link" href="lexer.html#spirit.lex.reference.concepts.lexer.macros">Macros</a>
 </h6>

 Regular expressions can be given a name and referred to in rules using
- the syntax <tt class="computeroutput">{NAME}</tt> where <tt class="computeroutput">NAME</tt>
+ the syntax <code class="computeroutput">{NAME}</code> where <code class="computeroutput">NAME</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">_</tt>
- or a letter. Subsequent characters can be <tt class="computeroutput">_</tt>,
- <tt class="computeroutput">-</tt>, a letter or a decimal
- digit. Use the <tt class="computeroutput">rules::add_macro()</tt> method to define a macro.
+ 30 characters long and must start with a <code class="computeroutput">_</code>
+ or a letter. Subsequent characters can be <code class="computeroutput">_</code>,
+ <code class="computeroutput">-</code>, a letter or a decimal
+ digit. Use the <code class="computeroutput">rules::add_macro()</code> method to define a macro.
 
</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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<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">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" href="../../../../index.html" title="Spirit 2.1">
+<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" lang="en"><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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<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">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" href="../../../../index.html" title="Spirit 2.1">
+<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" lang="en"><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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<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">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" href="../../../../index.html" title="Spirit 2.1">
+<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" lang="en"><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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<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">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" href="../../../index.html" title="Spirit 2.1">
+<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">
@@ -23,32 +23,29 @@
<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="id485584"></a>
- <a href="lexer_class.html#spirit.lex.reference.lexer_class.the_lexertl_lexer_class_implementing_the_dynamic_model">The
+<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="id2674525"></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="id485611"></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="id2674548"></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="id485637"></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="id2674573"></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="id485667"></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="id2674599"></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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<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">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" href="../../../index.html" title="Spirit 2.1">
+<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" lang="en"><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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<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">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" href="../../../index.html" title="Spirit 2.1">
+<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" lang="en"><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-06-23 00:30:19 EDT (Tue, 23 Jun 2009)
@@ -3,10 +3,10 @@
<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">
-<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">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" href="../../../index.html" title="Spirit 2.1">
+<link rel="up" href="../reference.html" title="Reference">
+<link rel="prev" href="tokendef_class.html" title="TokenDef Class">
<link rel="next" href="../../faq.html" title="FAQ">
</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_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>
</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" lang="en"><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

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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<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">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" href="../../index.html" title="Spirit 2.1">
+<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>
@@ -25,14 +23,10 @@
<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"> Spirit.Lex
+<div class="titlepage"><div><div><h3 class="title">
+<a name="spirit.lex.tutorials"></a><a class="link" href="tutorials.html" title="Spirit.Lex Tutorials"> Spirit.Lex
Tutorials</a>
-</h3></div></div>
-<div></div>
-</div>
+</h3></div></div></div>
<div class="toc"><dl>
<dt><a href="tutorials/lexer_tutorials.html"> Spirit.Lex
Tutorials Overview</a></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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<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">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" href="../../../index.html" title="Spirit 2.1">
+<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>
@@ -27,14 +23,10 @@
<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="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 Spirit.Lex</a>
-</h4></div></div>
-<div></div>
-</div>
+</h4></div></div></div>

 Spirit.Lex 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">wc</tt> is doing
+ Unix command <code class="computeroutput">wc</code> is doing
 (for the full example code see here: word_count_functor.cpp).
 
-<a name="spirit.lex.tutorials.lexer_quickstart1.prerequisites"></a><h5>
-<a name="id462569"></a>
- Prerequisites
- </h5>
+<a name="spirit.lex.tutorials.lexer_quickstart1.prerequisites"></a><h6>
+<a name="id2652151"></a>
+ <a class="link" href="lexer_quickstart1.html#spirit.lex.tutorials.lexer_quickstart1.prerequisites">Prerequisites</a>
+ </h6>

- The only required <tt class="computeroutput">#include</tt>
+ The only required <code class="computeroutput">#include</code>
 specific to Spirit.Lex follows. It is a wrapper for
 all necessary definitions to use Spirit.Lex in a standalone
 fashion, and on top of the Lexertl
- library. Additionally we <tt class="computeroutput">#include</tt>
- two of the Boost headers to define <tt class="computeroutput">boost::bind()</tt> and <tt class="computeroutput">boost::ref()</tt>.
+ library. Additionally we <code class="computeroutput">#include</code>
+ two of the Boost headers to define <code class="computeroutput">boost::bind()</code> and <code class="computeroutput">boost::ref()</code>.
 

 
@@ -85,11 +77,11 @@
 

 
-<a name="spirit.lex.tutorials.lexer_quickstart1.defining_tokens"></a><h5>
-<a name="id462916"></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="id2652469"></a>
+ <a class="link" href="lexer_quickstart1.html#spirit.lex.tutorials.lexer_quickstart1.defining_tokens">Defining
 Tokens</a>
- </h5>
+ </h6>

 The most important step while creating a lexer using Spirit.Lex
 is to define the tokens to be recognized in the input sequence. This is
@@ -102,16 +94,16 @@

 

- The template <tt class="computeroutput">word_count_tokens</tt>
- defines three different tokens: <tt class="computeroutput">ID_WORD</tt>,
- <tt class="computeroutput">ID_EOL</tt>, and <tt class="computeroutput">ID_CHAR</tt>, representing a word (anything
+ The template <code class="computeroutput">word_count_tokens</code>
+ defines three different tokens: <code class="computeroutput">ID_WORD</code>,
+ <code class="computeroutput">ID_EOL</code>, and <code class="computeroutput">ID_CHAR</code>, representing a word (anything
 except a whitespace or a newline), a newline character, and any other
- character (<tt class="computeroutput">ID_WORD</tt>,
- <tt class="computeroutput">ID_EOL</tt>, and <tt class="computeroutput">ID_CHAR</tt> are enum values representing
+ character (<code class="computeroutput">ID_WORD</code>,
+ <code class="computeroutput">ID_EOL</code>, and <code class="computeroutput">ID_CHAR</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">lexer_def<></tt>, where the corresponding template
- parameter (here: <tt class="computeroutput">lexertl_lexer<BaseIterator></tt>) defines which underlying lexer engine
+ the template <code class="computeroutput">lexer_def<></code>, where the corresponding template
+ parameter (here: <code class="computeroutput">lexertl_lexer<BaseIterator></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 @@
 

 
-<a name="spirit.lex.tutorials.lexer_quickstart1.doing_the_useful_work"></a><h5>
-<a name="id463365"></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="id2652885"></a>
+ <a class="link" href="lexer_quickstart1.html#spirit.lex.tutorials.lexer_quickstart1.doing_the_useful_work">Doing
 the Useful Work</a>
- </h5>
+ </h6>

 We will use a setup, where we want the Spirit.Lex
 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">iterator_range<BaseIterator></tt> pointing to the matched range in the
+ in this example carries a token value of the type <code class="computeroutput">iterator_range<BaseIterator></code> pointing to the matched range in the
 underlying input sequence.
 

@@ -198,25 +190,25 @@
 

 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">lex::tokenize()</tt>
+ the pieces described so far. To simplify this example we call the <code class="computeroutput">lex::tokenize()</code>
 function implemented in Spirit.Lex (for a more detailed
- description of this function see here: FIXME),
+ description of this function see here: FIXME),
 even if we could have written a loop to iterate over the lexer iterators
- [<tt class="computeroutput">first</tt>, <tt class="computeroutput">last</tt>)
+ [<code class="computeroutput">first</code>, <code class="computeroutput">last</code>)
 as well.
 
-<a name="spirit.lex.tutorials.lexer_quickstart1.pulling_everything_together"></a><h5>
-<a name="id464062"></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="id2653518"></a>
+ <a class="link" href="lexer_quickstart1.html#spirit.lex.tutorials.lexer_quickstart1.pulling_everything_together">Pulling
 Everything Together</a>
- </h5>
+ </h6>

 

- The main function simply loads the given file into memory (as a <tt class="computeroutput">std::string</tt>), instantiates an instance of
- the token definition template using the correct iterator type (<tt class="computeroutput">word_count_tokens<char const*></tt>), and finally calls <tt class="computeroutput">lex::tokenize</tt>, passing an instance of the
- counter function object. The return value of <tt class="computeroutput">lex::tokenize()</tt> will be <tt class="computeroutput">true</tt>
- if the whole input sequence has been successfully tokenized, and <tt class="computeroutput">false</tt> otherwise.
+ The main function simply loads the given file into memory (as a <code class="computeroutput">std::string</code>), instantiates an instance of
+ the token definition template using the correct iterator type (<code class="computeroutput">word_count_tokens<char const*></code>), and finally calls <code class="computeroutput">lex::tokenize</code>, passing an instance of the
+ counter function object. The return value of <code class="computeroutput">lex::tokenize()</code> will be <code class="computeroutput">true</code>
+ if the whole input sequence has been successfully tokenized, and <code class="computeroutput">false</code> otherwise.
 

 
@@ -258,11 +250,11 @@
 

 
-<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="id465192"></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="id2654539"></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
 Spirit.Lex with Flex</a>
- </h5>
+ </h6>

 This example was deliberately chosen to be as much as possible similar
 to the equivalent Flex
@@ -274,7 +266,7 @@
<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">
 Interestingly enough, performance comparisons of lexical analyzers written
 using Spirit.Lex 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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<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">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" href="../../../index.html" title="Spirit 2.1">
+<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>
@@ -27,18 +23,13 @@
<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="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 Spirit.Lex</a>
-</h4></div></div>
-<div></div>
-</div>
+</h4></div></div></div>

 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 Spirit.Lex</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).
 
-<a name="spirit.lex.tutorials.lexer_quickstart2.prerequisites"></a><h5>
-<a name="id466248"></a>
- Prerequisites
- </h5>
+<a name="spirit.lex.tutorials.lexer_quickstart2.prerequisites"></a><h6>
+<a name="id2655500"></a>
+ <a class="link" href="lexer_quickstart2.html#spirit.lex.tutorials.lexer_quickstart2.prerequisites">Prerequisites</a>
+ </h6>

- In addition to the only required <tt class="computeroutput">#include</tt>
+ In addition to the only required <code class="computeroutput">#include</code>
 specific to Spirit.Lex this example needs to include
 a couple of header files from the Phoenix2
 library. This example shows how to attach functors to token definitions,
@@ -122,18 +113,18 @@
 

 
-<a name="spirit.lex.tutorials.lexer_quickstart2.semantic_actions_in__emphasis_spirit_lex__emphasis_"></a><h5>
-<a name="id467138"></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="id2656306"></a>
+ <a class="link" href="lexer_quickstart2.html#spirit.lex.tutorials.lexer_quickstart2.semantic_actions_in__emphasis_spirit_lex__emphasis_">Semantic
 Actions in Spirit.Lex</a>
- </h5>
+ </h6>

 Spirit.Lex 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">[]</tt> brackets. In order to be able to attach
+ as well): specifying the operations to execute inside of a pair of <code class="computeroutput">[]</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">token_def<></tt>.
+ an instance of a <code class="computeroutput">token_def<></code>.
 

 
@@ -170,97 +161,30 @@

 

- The semantics of the shown code is as follows. The code inside the <tt class="computeroutput">[]</tt> brackets will be executed whenever the
+ The semantics of the shown code is as follows. The code inside the <code class="computeroutput">[]</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
 the recognition of a matching input sequence. The code above uses function
 objects constructed using Phoenix2,
 but it is possible to insert any C++ function or function object as long
- as it exposes the interface:
- 
-<pre class="programlisting">void f (Iterator& start, Iterator& end, pass_flag& matched, Idtype& id, Context& ctx);
-</pre>
-<div class="variablelist">
-where:
-<dl>
-<dt><tt class="computeroutput">Iterator& start</tt></dt>
-<dd>
- 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">lexertl_lexer<...></tt> (its first template parameter).
- The semantic action is allowed to change the value of this iterator
- influencing, the matched input sequence.
- </dd>
-<dt><tt class="computeroutput">Iterator& end</tt></dt>
-<dd>
- 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">lexertl_lexer<...></tt> (its first template parameter).
- The semantic action is allowed to change the value of this iterator
- influencing, the matched input sequence.
- </dd>
-<dt><tt class="computeroutput">pass_flag& matched</tt></dt>
-<dd>
- This value is pre/initialized to <tt class="computeroutput">pass_normal</tt>.
- If the semantic action sets it to <tt class="computeroutput">pass_fail</tt>
- the behaves as if the token has not been matched in the first place.
- If the semantic action sets this to <tt class="computeroutput">pass_ignore</tt>
- the lexer ignores the current token and tries to match a next token
- from the input.
- </dd>
-<dt><tt class="computeroutput">Idtype& id</tt></dt>
-<dd>
- This is the token id of the type Idtype (most of the time this will
- be a <tt class="computeroutput">std::size_t</tt>) for the matched token. The
- semantic action is allowed to change the value of this token id, influencing
- the if of the created token.
- </dd>
-<dt><tt class="computeroutput">Context& ctx</tt></dt>
-<dd>
- 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
- internal data items and is needed for lexer state control from inside
- a semantic action.
- </dd>
-</dl>
-</div>
-
- When using a C++ function as the semantic action the following prototypes
- are allowed as well:
- 
-<pre class="programlisting">void f (Iterator& start, Iterator& end, pass_flag& matched, Idtype& id);
-void f (Iterator& start, Iterator& end, pass_flag& matched);
-void f (Iterator& start, Iterator& end);
-void f ();
-</pre>
-
- 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
- lexer semantic actions is to use Phoenix2.
- In this case you can access the four parameters described in the table
- above by using the predefined Spirit
- placeholders: <tt class="computeroutput">_1</tt> for the
- iterator range, <tt class="computeroutput">_2</tt> for
- the token id, <tt class="computeroutput">_3</tt> for the
- reference to the boolean value signaling the outcome of the semantic action,
- and <tt class="computeroutput">_4</tt> for the reference
- to the internal lexer context.
- 
-<a name="spirit.lex.tutorials.lexer_quickstart2.associating_token_definitions_with_the_lexer"></a><h5>
-<a name="id468776"></a>
- <a href="lexer_quickstart2.html#spirit.lex.tutorials.lexer_quickstart2.associating_token_definitions_with_the_lexer">Associating
+ as it exposes the proper interface. For more details on please refer to
+ the section <a class="link" href="../abstracts/lexer_semantic_actions.html" title="Lexer Semantic Actions">Lexer
+ Semantic Actions</a>.
+ 
+<a name="spirit.lex.tutorials.lexer_quickstart2.associating_token_definitions_with_the_lexer"></a><h6>
+<a name="id2657082"></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>

- 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 Spirit.Lex</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">self.add()</tt> style of the API, while we here directly
- assign the token definitions to <tt class="computeroutput">self</tt>,
- combining the different token definitions using the <tt class="computeroutput">|</tt>
+ we have been using the <code class="computeroutput">self.add()</code> style of the API, while we here directly
+ assign the token definitions to <code class="computeroutput">self</code>,
+ combining the different token definitions using the <code class="computeroutput">|</code>
 operator. Here is the code snippet again:
 
<pre class="programlisting">self = word [++ref(w), ref(c) += distance(_1)]
@@ -271,10 +195,10 @@

 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">=</tt>') tokens
- as defined by any of ('<tt class="computeroutput">|</tt>')
- the token definitions <tt class="computeroutput">word</tt>,
- <tt class="computeroutput">eol</tt>, and <tt class="computeroutput">any</tt>.
+ will recognize ('<code class="computeroutput">=</code>') tokens
+ as defined by any of ('<code class="computeroutput">|</code>')
+ the token definitions <code class="computeroutput">word</code>,
+ <code class="computeroutput">eol</code>, and <code class="computeroutput">any</code>.
 

 A second difference to the previous example is that we do not explicitly
@@ -282,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 Spirit.Lex
 library internally assigns unique numbers to the token definitions, starting
- with the constant defined by <tt class="computeroutput">boost::spirit::lex::min_token_id</tt>.
+ with the constant defined by <code class="computeroutput">boost::spirit::lex::min_token_id</code>.
 
-<a name="spirit.lex.tutorials.lexer_quickstart2.pulling_everything_together"></a><h5>
-<a name="id469203"></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="id2657472"></a>
+ <a class="link" href="lexer_quickstart2.html#spirit.lex.tutorials.lexer_quickstart2.pulling_everything_together">Pulling
 everything together</a>
- </h5>
+ </h6>

 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
@@ -303,20 +227,20 @@
<pre class="programlisting">int main(int argc, char* argv[])
{

-<a name="spirit4co" href="lexer_quickstart2.html#spirit4"><img src="../../../../../../../doc/src/images/callouts/1.png" alt="1" border="0"></a> typedef lexertl::token<char const*, omitted, boost::mpl::false_> token_type;
+<a class="co" name="spirit4co" href="lexer_quickstart2.html#spirit4"><img src="../../../../../../../doc/src/images/callouts/1.png" alt="1" border="0"></a> typedef lexertl::token<char const*, omitted, boost::mpl::false_> token_type;

-<a name="spirit5co" href="lexer_quickstart2.html#spirit5"><img src="../../../../../../../doc/src/images/callouts/2.png" alt="2" border="0"></a> typedef lexertl::actor_lexer<token_type> lexer_type;
+<a class="co" name="spirit5co" href="lexer_quickstart2.html#spirit5"><img src="../../../../../../../doc/src/images/callouts/2.png" alt="2" border="0"></a> typedef lexertl::actor_lexer<token_type> lexer_type;

-<a name="spirit6co" href="lexer_quickstart2.html#spirit6"><img src="../../../../../../../doc/src/images/callouts/3.png" alt="3" border="0"></a> word_count_tokens<lexer_type> word_count_lexer;
+<a class="co" name="spirit6co" href="lexer_quickstart2.html#spirit6"><img src="../../../../../../../doc/src/images/callouts/3.png" alt="3" border="0"></a> word_count_tokens<lexer_type> word_count_lexer;

-<a name="spirit7co" href="lexer_quickstart2.html#spirit7"><img src="../../../../../../../doc/src/images/callouts/4.png" alt="4" border="0"></a> std::string str (read_from_file(1 == argc ? "word_count.input" : argv[1]));
+<a class="co" name="spirit7co" href="lexer_quickstart2.html#spirit7"><img src="../../../../../../../doc/src/images/callouts/4.png" alt="4" border="0"></a> std::string str (read_from_file(1 == argc ? "word_count.input" : argv[1]));
 char const* first = str.c_str();
 char const* last = &first[str.size()];

-<a name="spirit8co" href="lexer_quickstart2.html#spirit8"><img src="../../../../../../../doc/src/images/callouts/5.png" alt="5" border="0"></a> lexer_type::iterator_type iter = word_count_lexer.begin(first, last);
+<a class="co" name="spirit8co" href="lexer_quickstart2.html#spirit8"><img src="../../../../../../../doc/src/images/callouts/5.png" alt="5" border="0"></a> lexer_type::iterator_type iter = word_count_lexer.begin(first, last);
 lexer_type::iterator_type end = word_count_lexer.end();

-<a name="spirit9co" href="lexer_quickstart2.html#spirit9"><img src="../../../../../../../doc/src/images/callouts/6.png" alt="6" border="0"></a> while (iter != end && token_is_valid(*iter))
+<a class="co" name="spirit9co" href="lexer_quickstart2.html#spirit9"><img src="../../../../../../../doc/src/images/callouts/6.png" alt="6" border="0"></a> while (iter != end && token_is_valid(*iter))
 ++iter;

 if (iter == end) {
@@ -341,44 +265,38 @@
 
<div class="calloutlist"><table border="0" summary="Callout list">
<tr>
-<td width="5%" valign="top" align="left">
-<a name="spirit4"></a> </td>
-<td valign="top" align="left"> Specifying <tt class="computeroutput">omitted</tt> as
+<td width="5%" valign="top" align="left"><a name="spirit4"></a> </td>
+<td valign="top" align="left"> Specifying <code class="computeroutput">omitted</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">mpl::false_</tt>
+ as much as possible. Specifying <code class="computeroutput">mpl::false_</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. </td>
</tr>
<tr>
-<td width="5%" valign="top" align="left">
-<a name="spirit5"></a> </td>
+<td width="5%" valign="top" align="left"><a name="spirit5"></a> </td>
<td valign="top" align="left"> This defines the lexer type to use </td>
</tr>
<tr>
-<td width="5%" valign="top" align="left">
-<a name="spirit6"></a> </td>
+<td width="5%" valign="top" align="left"><a name="spirit6"></a> </td>
<td valign="top" align="left"> Create the lexer object instance
 needed to invoke the lexical analysis </td>
</tr>
<tr>
-<td width="5%" valign="top" align="left">
-<a name="spirit7"></a> </td>
+<td width="5%" valign="top" align="left"><a name="spirit7"></a> </td>
<td valign="top" align="left"> Read input from the given file,
 tokenize all the input, while discarding all generated tokens </td>
</tr>
<tr>
-<td width="5%" valign="top" align="left">
-<a name="spirit8"></a> </td>
+<td width="5%" valign="top" align="left"><a name="spirit8"></a> </td>
<td valign="top" align="left"> Create
 a pair of iterators returning the sequence of generated tokens </td>
</tr>
<tr>
-<td width="5%" valign="top" align="left">
-<a name="spirit9"></a> </td>
+<td width="5%" valign="top" align="left"><a name="spirit9"></a> </td>
<td valign="top" align="left"> Here we
 simply iterate over all tokens, making sure to break the loop if an invalid
 token gets returned from the lexer </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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<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">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" href="../../../index.html" title="Spirit 2.1">
+<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>
@@ -26,14 +23,10 @@
<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="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>

 The whole purpose of integrating Spirit.Lex 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.
 
@@ -56,16 +48,15 @@
<div class="figure">
<a name="spirit.lex.flowcontrol"></a>Figure 4. The common flow control implemented while parsing
 combined with lexical analysis
-<img src="./images/flowofcontrol.png" alt="The common flow
- control implemented while parsing combined with lexical analysis">
+<div class="figure-contents"><img src="../../.././images/flowofcontrol.png" alt="The common flow control implemented while parsing combined with lexical analysis"></div>
</div>
-
+ 
 

 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">token_def<></tt> class the most natural way of integration
+ For tokens defined as instances of the <code class="computeroutput">token_def<></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).
 
-<a name="spirit.lex.tutorials.lexer_quickstart3.prerequisites"></a><h5>
-<a name="id470618"></a>
- Prerequisites
- </h5>
+<a name="spirit.lex.tutorials.lexer_quickstart3.prerequisites"></a><h6>
+<a name="id2658766"></a>
+ <a class="link" href="lexer_quickstart3.html#spirit.lex.tutorials.lexer_quickstart3.prerequisites">Prerequisites</a>
+ </h6>

 This example uses two of the Spirit
 library components: Spirit.Lex and Spirit.Qi,
- consequently we have to <tt class="computeroutput">#include</tt>
+ consequently we have to <code class="computeroutput">#include</code>
 the corresponding header files. Again, we need to include a couple of header
 files from the Phoenix2
 library. This example shows how to attach functors to parser components,
@@ -123,22 +114,20 @@
 

 
-<a name="spirit.lex.tutorials.lexer_quickstart3.defining_tokens"></a><h5>
-<a name="id471222"></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="id2659314"></a>
+ <a class="link" href="lexer_quickstart3.html#spirit.lex.tutorials.lexer_quickstart3.defining_tokens">Defining
 Tokens</a>
- </h5>
+ </h6>

- 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 Spirit.Lex</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 Spirit.Lex</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 FIXME. Generally, any token definition
+ section FIXME. Generally, any token definition
 is usable without modification either for a standalone lexical analyzer
 or in conjunction with a parser.
 
@@ -178,11 +167,11 @@
 

 
-<a name="spirit.lex.tutorials.lexer_quickstart3.using_token_definition_instances_as_parsers"></a><h5>
-<a name="id471697"></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="id2659745"></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>

 While the integration of lexer and parser in the control flow is achieved
 by using special iterators wrapping the lexical analyzer, we still nead
@@ -191,9 +180,9 @@
 
<div class="itemizedlist"><ul type="disc">
<li>
- Using an instance of a <tt class="computeroutput">token_def<></tt>, which is handy whenever you
+ Using an instance of a <code class="computeroutput">token_def<></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>
@@ -218,47 +207,63 @@
<col>
</colgroup>
<thead><tr>
-<th>
+<th>
+ 
 Token definition
- </th>
-<th>
+ 
+ </th>
+<th>
+ 
 Parser integration
- </th>
+ 
+ </th>
</tr></thead>
<tbody>
<tr>
-<td>
- <tt class="computeroutput">token_def<></tt>
- </td>
-<td>
- The <tt class="computeroutput">token_def<></tt>
+<td>
+ 
+ <code class="computeroutput">token_def<></code>
+ 
+ </td>
+<td>
+ 
+ The <code class="computeroutput">token_def<></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.
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
+<td>
+ 
 single character
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 The single character is directly usable in the grammar, under certain
- circumstances it needs to be wrapped by a <tt class="computeroutput">char_()</tt> parser component, though. Parsing
+ circumstances it needs to be wrapped by a <code class="computeroutput">char_()</code> parser component, though. Parsing
 of this component will succeed if the single character has been
 matched.
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
+<td>
+ 
 explicit token id
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 To use an explicit token id in a Spirit.Qi
- grammar you are required to wrap it with the special <tt class="computeroutput">token()</tt>
+ grammar you are required to wrap it with the special <code class="computeroutput">token()</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">token(<id>)</tt>.
- </td>
+ <code class="computeroutput">token(<id>)</code>.
+ 
+ </td>
</tr>
</tbody>
</table></div>
@@ -298,54 +303,53 @@

 

- As already described (see: Attributes),
+ As already described (see: <a class="link" href="../../../">Attributes</a>),
 the Spirit.Qi 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">token_def<></tt>'s parser attributes: the <tt class="computeroutput">word</tt> token definition is declared as
- a <tt class="computeroutput">token_def<std::string></tt>,
- making every instance of a <tt class="computeroutput">word</tt>
+ full integration of the token values as the <code class="computeroutput">token_def<></code>'s parser attributes: the <code class="computeroutput">word</code> token definition is declared as
+ a <code class="computeroutput">token_def<std::string></code>,
+ making every instance of a <code class="computeroutput">word</code>
 token carry the string representation of the matched input sequence as
- its value. The semantic action attached to <tt class="computeroutput">tok.word</tt>
- receives this string (represented by the <tt class="computeroutput">_1</tt>
+ its value. The semantic action attached to <code class="computeroutput">tok.word</code>
+ receives this string (represented by the <code class="computeroutput">_1</code>
 placeholder) and uses it to calculate the number of matched characters:
- <tt class="computeroutput">ref(c) +=
- size(_1)</tt>.
+ <code class="computeroutput">ref(c) +=
+ size(_1)</code>.
 
<div class="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">
- All placeholders (<tt class="computeroutput">_1</tt>,
- <tt class="computeroutput">_2</tt>, etc.) used in parser
+<tr><td align="left" valign="top">
+ All placeholders (<code class="computeroutput">_1</code>,
+ <code class="computeroutput">_2</code>, etc.) used in parser
 semantic actions in conjunction with functors created based on Phoenix2 need to be imported
- from the <tt class="computeroutput">namespace boost::spirit::arg_names</tt>
- (and not <tt class="computeroutput">namespace
- boost::phoenix::arg_names</tt>, which is different from
+ from the <code class="computeroutput">namespace boost::spirit::arg_names</code>
+ (and not <code class="computeroutput">namespace
+ boost::phoenix::arg_names</code>, which is different from
 using placeholders in Spirit.Lex). Using the wrong
 placeholders leads to subtle compilation errors which are difficult to
 backtrack to their cause.
 </td></tr>
</table></div>
-<a name="spirit.lex.tutorials.lexer_quickstart3.pulling_everything_together"></a><h5>
-<a name="id473032"></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="id2660965"></a>
+ <a class="link" href="lexer_quickstart3.html#spirit.lex.tutorials.lexer_quickstart3.pulling_everything_together">Pulling
 Everything Together</a>
- </h5>
+ </h6>

 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">typedef</tt>
+ as well. The three type definitions (<code class="computeroutput">typedef</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">tokenize_and_parse()</code></a>
 to initialize the lexical analysis and parsing processes.
 

@@ -355,13 +359,13 @@

<pre class="programlisting">int main(int argc, char* argv[])
{
-<a name="spirit10co" href="lexer_quickstart3.html#spirit10"><img src="../../../../../../../doc/src/images/callouts/1.png" alt="1" border="0"></a> typedef lexertl::token<
+<a class="co" name="spirit10co" href="lexer_quickstart3.html#spirit10"><img src="../../../../../../../doc/src/images/callouts/1.png" alt="1" border="0"></a> typedef lexertl::token<
 char const*, boost::mpl::vector<std::string>
 > token_type;

-<a name="spirit11co" href="lexer_quickstart3.html#spirit11"><img src="../../../../../../../doc/src/images/callouts/2.png" alt="2" border="0"></a> typedef lexertl::lexer<token_type> lexer_type;
+<a class="co" name="spirit11co" href="lexer_quickstart3.html#spirit11"><img src="../../../../../../../doc/src/images/callouts/2.png" alt="2" border="0"></a> typedef lexertl::lexer<token_type> lexer_type;

-<a name="spirit12co" href="lexer_quickstart3.html#spirit12"><img src="../../../../../../../doc/src/images/callouts/3.png" alt="3" border="0"></a> typedef word_count_tokens<lexer_type>::iterator_type iterator_type;
+<a class="co" name="spirit12co" href="lexer_quickstart3.html#spirit12"><img src="../../../../../../../doc/src/images/callouts/3.png" alt="3" border="0"></a> typedef word_count_tokens<lexer_type>::iterator_type iterator_type;

 // now we use the types defined above to create the lexer and grammar
 // object instances needed to invoke the parsing process
@@ -373,7 +377,7 @@
 char const* first = str.c_str();
 char const* last = &first[str.size()];

-<a name="spirit13co" href="lexer_quickstart3.html#spirit13"><img src="../../../../../../../doc/src/images/callouts/4.png" alt="4" border="0"></a> bool r = tokenize_and_parse(first, last, word_count, g);
+<a class="co" name="spirit13co" href="lexer_quickstart3.html#spirit13"><img src="../../../../../../../doc/src/images/callouts/4.png" alt="4" border="0"></a> bool r = tokenize_and_parse(first, last, word_count, g);

 if (r) {
 std::cout << "lines: " << g.l << ", words: " << g.w
@@ -395,29 +399,25 @@
 
<div class="calloutlist"><table border="0" summary="Callout list">
<tr>
-<td width="5%" valign="top" align="left">
-<a name="spirit10"></a> </td>
-<td valign="top" align="left"> Define the token type to be used: <tt class="computeroutput">std::string</tt>
+<td width="5%" valign="top" align="left"><a name="spirit10"></a> </td>
+<td valign="top" align="left"> Define the token type to be used: <code class="computeroutput">std::string</code>
 is available as the type of the token attribute </td>
</tr>
<tr>
-<td width="5%" valign="top" align="left">
-<a name="spirit11"></a> </td>
+<td width="5%" valign="top" align="left"><a name="spirit11"></a> </td>
<td valign="top" align="left"> Define the lexer type
 to use implementing the state machine </td>
</tr>
<tr>
-<td width="5%" valign="top" align="left">
-<a name="spirit12"></a> </td>
+<td width="5%" valign="top" align="left"><a name="spirit12"></a> </td>
<td valign="top" align="left"> Define the iterator type exposed
 by the lexer type </td>
</tr>
<tr>
-<td width="5%" valign="top" align="left">
-<a name="spirit13"></a> </td>
+<td width="5%" valign="top" align="left"><a name="spirit13"></a> </td>
<td valign="top" align="left"> Parsing is done based on the the token stream, not
- the character stream read from the input. The function <tt class="computeroutput">tokenize_and_parse()</tt>
- wraps the passed iterator range <tt class="computeroutput">[first, last)</tt>
+ the character stream read from the input. The function <code class="computeroutput">tokenize_and_parse()</code>
+ wraps the passed iterator range <code class="computeroutput">[first, last)</code>
 by the lexical analyzer and uses its exposed iterators to parse the toke
 stream. </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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<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">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" href="../../../index.html" title="Spirit 2.1">
+<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>
@@ -27,14 +23,10 @@
<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"> Spirit.Lex
+<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"> Spirit.Lex
 Tutorials Overview</a>
-</h4></div></div>
-<div></div>
-</div>
+</h4></div></div></div>

 The Spirit.Lex library implements several components
 on top of possibly different lexer generator libraries. It exposes a pair
@@ -58,7 +50,7 @@
<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">
 For the sake of clarity all examples in this documentation assume Spirit.Lex
 to be used on top of Lexertl.
 </td></tr>
@@ -100,17 +92,14 @@

 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 Spirit.Lex</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 Spirit.Lex</a>)
 introduce the Spirit.Lex 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
 Spirit.Qi).

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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<link rel="home" href="../index.html" title="Spirit 2.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" href="../index.html" title="Spirit 2.1">
<link rel="up" href="../index.html" title="Spirit 2.1">
-<link rel="previous" href="faq.html" title="FAQ">
+<link rel="prev" href="faq.html" title="FAQ">
<link rel="next" href="notes/style_guide.html" title="Style Guide">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -23,12 +23,9 @@
<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="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>Style Guide</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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<link rel="home" href="../../index.html" title="Spirit 2.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" 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">
@@ -23,12 +23,9 @@
<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="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>

 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
@@ -71,15 +68,15 @@
</pre>
<div class="itemizedlist"><ul type="disc">
<li>
- Prefer literals in the grammar instead of identifiers. e.g. <tt class="computeroutput">"program"</tt> instead of <tt class="computeroutput">PROGRAM</tt>, <tt class="computeroutput">'>='</tt>
- instead of <tt class="computeroutput">GTE</tt> and <tt class="computeroutput">'.'</tt> instead of <tt class="computeroutput">DOT</tt>.
+ Prefer literals in the grammar instead of identifiers. e.g. <code class="computeroutput">"program"</code> instead of <code class="computeroutput">PROGRAM</code>, <code class="computeroutput">'>='</code>
+ instead of <code class="computeroutput">GTE</code> and <code class="computeroutput">'.'</code> instead of <code class="computeroutput">DOT</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">*(',' >>
- file_identifier)</tt>
+ Breaking the operands may not be needed for short expressions. e.g. <code class="computeroutput">*(',' >>
+ file_identifier)</code>
 as long as the line does not exceed 80 characters.
 </li>
<li>
@@ -115,7 +112,7 @@
</pre>
<div class="itemizedlist"><ul type="disc"><li>
 Nesting unary operators (e.g.Kleene star): Unary rule operators (Kleene
- star, <tt class="computeroutput">'!'</tt>, <tt class="computeroutput">'+'</tt>
+ star, <code class="computeroutput">'!'</code>, <code class="computeroutput">'+'</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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<link rel="home" href="../index.html" title="Spirit 2.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" 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">
@@ -23,80 +23,71 @@
<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="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">

 

 “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.”
- --Bjarne Stroustrup
+ "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.”
+ --Bjarne Stroustrup
 

 
</blockquote></div>
-<a name="spirit.preface.history"></a><h3>
-<a name="id355311"></a>
- History
- </h3>
-<a name="spirit.preface._emphasis_80s__emphasis_"></a><h3>
-<a name="id355325"></a>
- 80s
- </h3>
+<a name="spirit.preface.history"></a><h4>
+<a name="id2554266"></a>
+ <a class="link" href="preface.html#spirit.preface.history">History</a>
+ </h4>
+<a name="spirit.preface._emphasis_80s__emphasis_"></a><h4>
+<a name="id2554286"></a>
+ <a class="link" href="preface.html#spirit.preface._emphasis_80s__emphasis_">80s</a>
+ </h4>

- In the Mid 80s, Joel wrote his first calculator in Pascal. It has been an unforgettable
- coding experience. He was amazed how a mutually recursive set of functions
+ 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
 can model a grammar specification. In time, the skills he acquired from that
 academic experience became very practical. Periodically Joel was tasked to
- do some parsing. For instance, whenever he needs to perform any form of I/O,
- even in binary, he tries to approach the task somewhat formally by writing
- a grammar using Pascal- like syntax diagrams and then write a corresponding
- recursive-descent parser. This worked very well.
- 
-<a name="spirit.preface._emphasis_90s__emphasis_"></a><h3>
-<a name="id353704"></a>
- 90s
- </h3>
+ do some parsing. For instance, whenever he needed to perform any form of I/O,
+ even in binary, he tried to approach the task somewhat formally by writing
+ a grammar using Pascal-like syntax diagrams and then a corresponding recursive-descent
+ parser. This worked very well.
+ 
+<a name="spirit.preface._emphasis_90s__emphasis_"></a><h4>
+<a name="id2554320"></a>
+ <a class="link" href="preface.html#spirit.preface._emphasis_90s__emphasis_">90s</a>
+ </h4>

 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
 got a recursive-descent HTML parser working based on the W3C formal specifications
 easily. He was certainly glad that HTML had a formal grammar specification.
 Because of the influence of the Internet, Joel then had to do more parsing.
- RFC specifications were everywhere. SGML, HTML, XML, even email addresses and
- those seemingly trivial URLs were all formally specified using small EBNF-
- style grammar specifications. This made him wish for a tool similar to big-
- time parser generators such as YACC and ANTLR, where a parser is built automatically
- from a grammar specification. Yet, he wants it to be extremely small; small
- enough to fit in my pocket, yet scalable.
- 
-
- It must be able to practically parse simple grammars such as email addresses
- to moderately complex grammars such as XML and perhaps some small to medium-sized
- scripting languages. Scalability is a prime goal. You should be able to use
- it for small tasks such as parsing command lines without incurring a heavy
- payload, as you do when you are using YACC or PCCTS. Even now that it has evolved
- and matured to become a multi-module library, true to its original intent,
- Spirit can still be used for extreme micro-parsing tasks. You only pay for
- features that you need. The power of Spirit comes from its modularity and extensibility.
- Instead of giving you a sledgehammer, it gives you the right ingredients to
- create a sledgehammer easily.
+ RFC specifications were everywhere! SGML, HTML, XML, email addresses and even
+ those seemingly trivial URLs were all formally specified using small EBNF-style
+ grammar specifications. This made him wish for a tool similar to larger parser
+ generators such as YACC and ANTLR, where a parser is built automatically from
+ a grammar specification.
+ 
+
+ This ideal tool would be able to parse anything from email addresses and command
+ lines, to XML and scripting languages. Scalability was a prime goal. The tool
+ should be able to do this without incurring a heavy development load, which
+ was not possible with the above mentioned parser generators.
 

 The result was Spirit. Spirit was a personal project that was conceived when
- Joel was doing R&D in Japan. Inspired by the GoF's composite and interpreter
- patterns, he realized that he can model a recursive-descent parser with hierarchical-object
- composition of primitives (terminals) and composites (productions). The original
- version was implemented with run-time polymorphic classes. A parser is generated
- at run time by feeding in production rule strings such as:
+ Joel was involved in R&D in Japan. Inspired by the GoF's composite and
+ interpreter patterns, he realized that he can model a recursive-descent parser
+ with hierarchical-object composition of primitives (terminals) and composites
+ (productions). The original version was implemented with run-time polymorphic
+ classes. A parser was generated at run time by feeding in production rule strings
+ such as:
 
<pre class="programlisting">"prod ::= {'A' | 'B'} 'C';"
</pre>
@@ -105,11 +96,11 @@
 objects and linking semantic actions on the fly. A very early text can be found
 here: pre-Spirit.
 
-<a name="spirit.preface._emphasis_2001_to_2006__emphasis_"></a><h3>
-<a name="id353805"></a>
- <a href="preface.html#spirit.preface._emphasis_2001_to_2006__emphasis_">2001
+<a name="spirit.preface._emphasis_2001_to_2006__emphasis_"></a><h4>
+<a name="id2554416"></a>
+ <a class="link" href="preface.html#spirit.preface._emphasis_2001_to_2006__emphasis_">2001
 to 2006</a>
- </h3>
+ </h4>

 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
@@ -118,57 +109,64 @@
 was meant only to replace the core of the original dynamic-Spirit. Dynamic-spirit
 needed a parser to implement itself anyway. The original employed a hand-coded
 recursive-descent parser to parse the input grammar specification strings.
- Incidentially it was the time, when Hartmut joined the Spirit development.
+ It was at this time when Hartmut joined the Spirit development.
 

 After its initial "open-source" debut in May 2001, static-Spirit
 became a success. At around November 2001, the Spirit website had an activity
 percentile of 98%, making it the number one parser tool at Source Forge at
- the time. Not bad for such a niche project such as a parser library. The "static"
+ the time. Not bad for a niche project like a parser library. The "static"
 portion of Spirit was forgotten and static-Spirit simply became Spirit. The
 library soon evolved to acquire more dynamic features.
 

 Spirit was formally accepted into Boost
 in October 2002. Boost is a peer-reviewed, open collaborative development effort
- that is a collection of free Open Source C++ libraries covering a wide range
+ around a collection of free Open Source C++ libraries covering a wide range
 of domains. The Boost Libraries have become widely known as an industry standard
 for design and implementation quality, robustness, and reusability.
 
-<a name="spirit.preface._emphasis_2007__emphasis_"></a><h3>
-<a name="id353862"></a>
- 2007
- </h3>
+<a name="spirit.preface._emphasis_2007__emphasis_"></a><h4>
+<a name="id2553182"></a>
+ <a class="link" href="preface.html#spirit.preface._emphasis_2007__emphasis_">2007</a>
+ </h4>

 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 Classic-Spirit (versions prior
+ served its purpose quite admirably. The focus of what we'll now call Classic-Spirit (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 rather in an
+ time came to add attributes to the parser library, it was done in a rather
 ad-hoc manner, with the goal being 100% backward compatible with classic Spirit.
- Some parsers have attributes, some don't.
+ As a result, some parsers have attributes, some don't.
 

 Spirit V2 is another major rewrite. Spirit V2 grammars are fully attributed
 (see <a href="http://en.wikipedia.org/wiki/Attribute_grammar" target="_top">Attribute
- Grammar</a>). All parser components have attributes. To do this efficiently
- and ellegantly, we had to use a couple of infrastructure libraries. Some of
- which haven't been written yet at the time, some were quite new when Spirit
- debuted, and some needed work. MPL
+ Grammar</a>) which means that all parser components have attributes. To
+ do this efficiently and elegantly, we had to use a couple of infrastructure
+ libraries. Some did not exist, some were quite new when Spirit debuted, and
+ some needed work. MPL
 is an important infrastructure library, yet is not sufficient to implement
 Spirit V2. Another library had to be written: Fusion.
 Fusion sits between MPL and STL --between compile time and runtime -- mapping
- types to values. Fusion is a direct descendant of both MPL and Boost.Tuples
- (Fusion is now a full fledged Boost
- library). Phoenix also
+ types to values. Fusion is a direct descendant of both MPL and Boost.Tuples.
+ Fusion is now a full-fledged Boost
+ library. Phoenix also
 had to be beefed up to support Spirit V2. The result is Phoenix2.
 Last but not least, Spirit V2 uses an <a href="http://ubiety.uwaterloo.ca/~tveldhui/papers/Expression-Templates/exprtmpl.html" target="_top">Expression
 Templates</a> library called Boost.Proto.
 
-<a name="spirit.preface.new_ideas__spirit_v2"></a><h3>
-<a name="id355502"></a>
- New Ideas: Spirit V2
- </h3>
+
+ Even though it has evolved and matured to become a multi-module library, Spirit
+ is still used for micro-parsing tasks as well as scripting languages. Like
+ C++, you only pay for features that you need. The power of Spirit comes from
+ its modularity and extensibility. Instead of giving you a sledgehammer, it
+ gives you the right ingredients to create a sledgehammer easily.
+ 
+<a name="spirit.preface.new_ideas__spirit_v2"></a><h4>
+<a name="id2553304"></a>
+ <a class="link" href="preface.html#spirit.preface.new_ideas__spirit_v2">New Ideas: Spirit V2</a>
+ </h4>

 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
@@ -176,10 +174,10 @@
 formatted text output. With it, he got the the idea of using a formal notation
 (a grammar) to describe the expected structure of an input character sequence.
 The same grammar may be used to formalize the structure of a corresponding
- output character sequence. This is possible because parsing, most of the time,
- is implemented by comparing the input with the patterns defined by the grammar.
- If we use the same patterns to format a matching output, the generated sequence
- will follow the rules of the grammar as well.
+ output character sequence. This is possible because parsing is usually implemented
+ by comparing the input with patterns defined by the grammar. If we use the
+ same patterns to format a matching output, the generated sequence will follow
+ the rules of the grammar as well.
 

 This insight lead to the implementation of a grammar driven output generation
@@ -191,32 +189,33 @@
 

 The idea of creating a lexer library well integrated with the Spirit parsers
- is not new. This has been discussed almost for the whole time of the existence
- of Classic-Spirit (pre V2) now. Several attempts to integrate existing lexer
- libraries and frameworks with Spirit have been made and served as a proof of
- concept and usability (for example see Wave:
+ is not new. This has been discussed almost since Classic-Spirit (pre V2) initially
+ debuted. Several attempts to integrate existing lexer libraries and frameworks
+ with Spirit have been made and served as a proof of concept and usability (for
+ example see Wave:
 The Boost C/C++ Preprocessor Library, and SLex:
 a fully dynamic C++ lexer implemented with Spirit). Based on these experiences
 we added Spirit.Lex: a fully integrated lexer library
- to the mix, allowing to take advantage of the power of regular expressions
+ to the mix, allowing the user to take advantage of the power of regular expressions
 for token matching, removing pressure from the parser components, simplifying
 parser grammars. Again, Spirit's modular structure allowed us to reuse the
 same underlying component library as for the parser and generator libraries.
 
-<a name="spirit.preface.how_to_use_this_manual"></a><h3>
-<a name="id355572"></a>
- How to use this manual
- </h3>
+<a name="spirit.preface.how_to_use_this_manual"></a><h4>
+<a name="id2553396"></a>
+ <a class="link" href="preface.html#spirit.preface.how_to_use_this_manual">How to use this manual</a>
+ </h4>

- 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:
 
<div class="orderedlist"><ol type="1">
<li>
 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 using abundant
- examples and detailed instructions. Examples speak volumes.
+ 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>
 Abstracts: A high level summary of key topics. The objective is to give the
@@ -234,94 +233,130 @@
 icons precede some text to indicate:
 
<div class="table">
-<a name="id355643"></a>Table 1. Icons
-<table class="table" summary="Icons">
+<a name="id2553480"></a>Table 1. Icons
+<div class="table-contents"><table class="table" summary="Icons">
<colgroup>
<col>
<col>
<col>
</colgroup>
<thead><tr>
-<th>
+<th>
+ 
 Icon
- </th>
-<th>
+ 
+ </th>
+<th>
+ 
 Name
- </th>
-<th>
+ 
+ </th>
+<th>
+ 
 Meaning
- </th>
+ 
+ </th>
</tr></thead>
<tbody>
<tr>
-<td>
- <img src="images/note.png" alt="note">
- </td>
-<td>
+<td>
+ 
+ <img src="../images/note.png" alt="note">
+ 
+ </td>
+<td>
+ 
 Note
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 Generally useful information (an aside that doesn't fit in the flow of
 the text)
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <img src="images/tip.png" alt="tip">
- </td>
-<td>
+<td>
+ 
+ <img src="../images/tip.png" alt="tip">
+ 
+ </td>
+<td>
+ 
 Tip
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 Suggestion on how to do something (especially something that not be obvious)
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <img src="images/important.png" alt="important">
- </td>
-<td>
+<td>
+ 
+ <img src="../images/important.png" alt="important">
+ 
+ </td>
+<td>
+ 
 Important
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 Important note on something to take particular notice of
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <img src="images/caution.png" alt="caution">
- </td>
-<td>
+<td>
+ 
+ <img src="../images/caution.png" alt="caution">
+ 
+ </td>
+<td>
+ 
 Caution
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 Take special care with this - it may not be what you expect and may cause
 bad results
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <img src="images/alert.png" alt="alert">
- </td>
-<td>
+<td>
+ 
+ <img src="../images/alert.png" alt="alert">
+ 
+ </td>
+<td>
+ 
 Danger
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 This is likely to cause serious trouble if ignored
- </td>
+ 
+ </td>
</tr>
</tbody>
-</table>
+</table></div>
</div>
-
+ 
 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>.
 
-<a name="spirit.preface.support"></a><h3>
-<a name="id353379"></a>
- Support
- </h3>
+<a name="spirit.preface.support"></a><h4>
+<a name="id2553728"></a>
+ <a class="link" href="preface.html#spirit.preface.support">Support</a>
+ </h4>

 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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<link rel="home" href="../index.html" title="Spirit 2.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" 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">
@@ -24,12 +23,9 @@
<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="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>Tutorials</dt>
<dd><dl>

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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<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">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" href="../../index.html" title="Spirit 2.1">
+<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">
@@ -24,12 +23,9 @@
<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="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>Common Notation</dt>
<dt><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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<link rel="home" href="../../../index.html" title="Spirit 2.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" 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>
@@ -24,109 +23,106 @@
<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="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">
Notation
<dl>
-<dt><tt class="computeroutput">P</tt></dt>
+<dt><code class="computeroutput">P</code></dt>
<dd>
 Parser type
 </dd>
-<dt><tt class="computeroutput">p, a,
+<dt><code class="computeroutput">p, a,
 b,
- c</tt></dt>
+ c</code></dt>
<dd>
 Parser objects
 </dd>
-<dt><tt class="computeroutput">A, B,
- C</tt></dt>
+<dt><code class="computeroutput">A, B,
+ C</code></dt>
<dd>
 Attribute types of parsers A, B and C
 </dd>
-<dt><tt class="computeroutput">I</tt></dt>
+<dt><code class="computeroutput">I</code></dt>
<dd>
 The iterator type used for parsing
 </dd>
-<dt><tt class="computeroutput">Unused</tt></dt>
+<dt><code class="computeroutput">Unused</code></dt>
<dd>
- An <tt class="computeroutput">unused_type</tt>
+ An <code class="computeroutput">unused_type</code>
 </dd>
-<dt><tt class="computeroutput">Context</tt></dt>
+<dt><code class="computeroutput">Context</code></dt>
<dd>
- The enclosing rule's <tt class="computeroutput">Context</tt>
+ The enclosing rule's <code class="computeroutput">Context</code>
 type
 </dd>
-<dt><tt class="computeroutput">Attr</tt></dt>
+<dt><code class="computeroutput">Attr</code></dt>
<dd>
 An attribute type
 </dd>
-<dt><tt class="computeroutput">b</tt></dt>
+<dt><code class="computeroutput">b</code></dt>
<dd>
 A boolean expression
 </dd>
-<dt><tt class="computeroutput">fp</tt></dt>
+<dt><code class="computeroutput">fp</code></dt>
<dd>
- A (lazy parser) function with signature <tt class="computeroutput">P(Unused, Context)</tt>
+ A (lazy parser) function with signature <code class="computeroutput">P(Unused, Context)</code>
 </dd>
-<dt><tt class="computeroutput">fa</tt></dt>
+<dt><code class="computeroutput">fa</code></dt>
<dd>
- A (semantic action) function with signature <tt class="computeroutput">void(Attr, Context, bool&)</tt>. The third parameter is a boolean
- flag that can be set to false to force the parse to fail. Both <tt class="computeroutput">Context</tt> and the boolean flag are
+ A (semantic action) function with signature <code class="computeroutput">void(Attr, Context, bool&)</code>. The third parameter is a boolean
+ flag that can be set to false to force the parse to fail. Both <code class="computeroutput">Context</code> and the boolean flag are
 optional.
 </dd>
-<dt><tt class="computeroutput">first</tt></dt>
+<dt><code class="computeroutput">first</code></dt>
<dd>
 An iterator pointing to the start of input
 </dd>
-<dt><tt class="computeroutput">last</tt></dt>
+<dt><code class="computeroutput">last</code></dt>
<dd>
 An iterator pointing to the end of input
 </dd>
-<dt><tt class="computeroutput">Ch</tt></dt>
+<dt><code class="computeroutput">Ch</code></dt>
<dd>
 Character-class specific character type (See __char_classtypes_)
 </dd>
-<dt><tt class="computeroutput">ch</tt></dt>
+<dt><code class="computeroutput">ch</code></dt>
<dd>
 Character-class specific character (See __char_classtypes_)
 </dd>
-<dt><tt class="computeroutput">ch2</tt></dt>
+<dt><code class="computeroutput">ch2</code></dt>
<dd>
 Character-class specific character (See __char_classtypes_)
 </dd>
-<dt><tt class="computeroutput">chset</tt></dt>
+<dt><code class="computeroutput">chset</code></dt>
<dd>
 Character-set specifier string (example: "a-z0-9")
 </dd>
-<dt><tt class="computeroutput">str</tt></dt>
+<dt><code class="computeroutput">str</code></dt>
<dd>
 Character-class specific string (See __char_classtypes_)
 </dd>
-<dt><tt class="computeroutput">Str</tt></dt>
+<dt><code class="computeroutput">Str</code></dt>
<dd>
- Attribute of <tt class="computeroutput">str</tt>:
- <tt class="computeroutput">std::basic_string<T></tt>
- where <tt class="computeroutput">T</tt> is the underlying
- character type of <tt class="computeroutput">str</tt>
+ Attribute of <code class="computeroutput">str</code>:
+ <code class="computeroutput">std::basic_string<T></code>
+ where <code class="computeroutput">T</code> is the underlying
+ character type of <code class="computeroutput">str</code>
 </dd>
-<dt><tt class="computeroutput">tuple<></tt></dt>
+<dt><code class="computeroutput">tuple<></code></dt>
<dd>
 Used as a placeholder for a fusion sequence
 </dd>
-<dt><tt class="computeroutput">vector<></tt></dt>
+<dt><code class="computeroutput">vector<></code></dt>
<dd>
 Used as a placeholder for an STL container
 </dd>
-<dt><tt class="computeroutput">variant<></tt></dt>
+<dt><code class="computeroutput">variant<></code></dt>
<dd>
 Used as a placeholder for a boost::variant
 </dd>
-<dt><tt class="computeroutput">optional<></tt></dt>
+<dt><code class="computeroutput">optional<></code></dt>
<dd>
 Used as a placeholder for a boost::optional
 </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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<link rel="home" href="../../../index.html" title="Spirit 2.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" 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="lazy_arguments.html" title="Lazy Arguments">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -25,49 +23,51 @@
<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="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.qi.quick_reference.compound_attribute_rules"></a><a href="compound_attribute_rules.html" title="Compound
- Attribute Rules">Compound
+<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>

 The notation will be for instance:
 
<pre class="programlisting">a: A, b: B --> (a >> b): tuple<A, B>
</pre>

- which reads as: given, <tt class="computeroutput">a</tt>
- and <tt class="computeroutput">b</tt> are parsers/generators,
- and <tt class="computeroutput">A</tt> is the type of the
- attribute of <tt class="computeroutput">a</tt>, and <tt class="computeroutput">B</tt> is the type of the attribute of <tt class="computeroutput">b</tt>, then the type of the attribute of
- <tt class="computeroutput">a >>
- b</tt> will be <tt class="computeroutput">tuple<A, B></tt>.
+ which reads as: given, <code class="computeroutput">a</code>
+ and <code class="computeroutput">b</code> are parsers/generators,
+ and <code class="computeroutput">A</code> is the type of the
+ attribute of <code class="computeroutput">a</code>, and <code class="computeroutput">B</code> is the type of the attribute of <code class="computeroutput">b</code>, then the type of the attribute of
+ <code class="computeroutput">a >>
+ b</code> will be <code class="computeroutput">tuple<A, B></code>.
 
<div class="table">
-<a name="id444464"></a>Table 4. compound parser attribute types
-<table class="table" summary="compound parser attribute types">
+<a name="id2635767"></a>Table 4. compound parser attribute types
+<div class="table-contents"><table class="table" summary="compound parser attribute types">
<colgroup>
<col>
<col>
</colgroup>
<thead><tr>
-<th>
+<th>
+ 
 Expression
- </th>
-<th>
+ 
+ </th>
+<th>
+ 
 Attribute
- </th>
+ 
+ </th>
</tr></thead>
<tbody>
<tr>
-<td>
- sequence (<tt class="computeroutput">>></tt>)
- </td>
<td>
-
+ 
+ sequence (<code class="computeroutput">>></code>)
+ 
+ </td>
+<td>
+ 


<pre class="programlisting">a: A, b: B --> (a >> b): tuple<A, B>
@@ -77,14 +77,16 @@
a: A, b: A --> (a >> b): vector<A></pre>

 
-</td>
+ </td>
</tr>
<tr>
-<td>
- expect (<tt class="computeroutput">></tt>)
- </td>
<td>
-
+ 
+ expect (<code class="computeroutput">></code>)
+ 
+ </td>
+<td>
+ 


<pre class="programlisting">a: A, b: B --> (a > b): tuple<A, B>
@@ -94,14 +96,16 @@
a: A, b: A --> (a > b): vector<A></pre>

 
-</td>
+ </td>
</tr>
<tr>
-<td>
- alternative (<tt class="computeroutput">|</tt>)
- </td>
<td>
-
+ 
+ alternative (<code class="computeroutput">|</code>)
+ 
+ </td>
+<td>
+ 


<pre class="programlisting">a: A, b: B --> (a | b): variant<A, B>
@@ -111,83 +115,97 @@
a: A, b: A --> (a | b): A</pre>

 
-</td>
+ </td>
</tr>
<tr>
-<td>
- difference (<tt class="computeroutput">-</tt>)
- </td>
-<td>
- <tt class="computeroutput">a:
+<td>
+ 
+ difference (<code class="computeroutput">-</code>)
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">a:
 A,
 b:
 B -->
 (a
- - b): A</tt>
- </td>
+ - b): A</code>
+ 
+ </td>
</tr>
<tr>
-<td>
- kleene (<tt class="computeroutput">*</tt>)
- </td>
<td>
-
+ 
+ kleene (<code class="computeroutput">*</code>)
+ 
+ </td>
+<td>
+ 


<pre class="programlisting">a: A --> *a: vector<A>
a: Unused --> a: Unused</pre>

 
-</td>
+ </td>
</tr>
<tr>
-<td>
- plus (<tt class="computeroutput">+</tt>)
- </td>
<td>
-
+ 
+ plus (<code class="computeroutput">+</code>)
+ 
+ </td>
+<td>
+ 


<pre class="programlisting">a: A --> +a: vector<A>
a: Unused --> a: Unused</pre>

 
-</td>
+ </td>
</tr>
<tr>
-<td>
- list (<tt class="computeroutput">%</tt>)
- </td>
<td>
-
+ 
+ list (<code class="computeroutput">%</code>)
+ 
+ </td>
+<td>
+ 


<pre class="programlisting">a: A, b: B --> (a % b): vector<A>
a: Unused, b: B --> (a % b): Unused</pre>

 
-</td>
+ </td>
</tr>
<tr>
-<td>
+<td>
+ 
 repetition
- </td>
+ 
+ </td>
<td>
-
+ 


<pre class="programlisting">a: A --> repeat(...,...)[a]: vector<A>
a: Unused --> repeat(...,...)[a]: Unused</pre>

 
-</td>
+ </td>
</tr>
<tr>
-<td>
- sequential or (<tt class="computeroutput">||</tt>)
- </td>
<td>
-
+ 
+ sequential or (<code class="computeroutput">||</code>)
+ 
+ </td>
+<td>
+ 


<pre class="programlisting">a: A, b: B --> (a || b): tuple<optional<A>, optional<B> >
@@ -196,48 +214,60 @@
a: Unused, b: Unused --> (a || b): Unused</pre>

 
-</td>
+ </td>
</tr>
<tr>
-<td>
- optional (<tt class="computeroutput">-</tt>)
- </td>
<td>
-
+ 
+ optional (<code class="computeroutput">-</code>)
+ 
+ </td>
+<td>
+ 


<pre class="programlisting">a: A --> -a: optional<A>
a: Unused --> -a: Unused</pre>

 
-</td>
+ </td>
</tr>
<tr>
-<td>
- and predicate (<tt class="computeroutput">&</tt>)
- </td>
-<td>
- <tt class="computeroutput">a:
+<td>
+ 
+ and predicate (<code class="computeroutput">&</code>)
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">a:
 A -->
- &a: Unused</tt>
- </td>
+ &a: Unused</code>
+ 
+ </td>
</tr>
<tr>
-<td>
- not predicate (<tt class="computeroutput">!</tt>)
- </td>
-<td>
- <tt class="computeroutput">a:
+<td>
+ 
+ not predicate (<code class="computeroutput">!</code>)
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">a:
 A -->
- !a: Unused</tt>
- </td>
+ !a: Unused</code>
+ 
+ </td>
</tr>
<tr>
-<td>
- permutation (<tt class="computeroutput">^</tt>)
- </td>
<td>
-
+ 
+ permutation (<code class="computeroutput">^</code>)
+ 
+ </td>
+<td>
+ 


<pre class="programlisting">a: A, b: B --> (a ^ b): tuple<optional<A>, optional<B> >
@@ -246,11 +276,12 @@
a: Unused, b: Unused --> (a ^ b): Unused</pre>

 
-</td>
+ </td>
</tr>
</tbody>
-</table>
+</table></div>
</div>
+ 
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>

Modified: trunk/libs/spirit/doc/html/spirit/qi/quick_reference/lazy_arguments.html
==============================================================================
--- trunk/libs/spirit/doc/html/spirit/qi/quick_reference/lazy_arguments.html (original)
+++ trunk/libs/spirit/doc/html/spirit/qi/quick_reference/lazy_arguments.html 2009-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<link rel="home" href="../../../index.html" title="Spirit 2.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" 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">
@@ -24,26 +23,23 @@
<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.qi.quick_reference.lazy_arguments"></a>Lazy Arguments
-</h4></div></div>
-<div></div>
-</div>
+<div class="titlepage"><div><div><h4 class="title">
+<a name="spirit.qi.quick_reference.lazy_arguments"></a><a class="link" href="lazy_arguments.html" title="Lazy Arguments">Lazy Arguments</a>
+</h4></div></div></div>

 For all expressions of the form:
 
<pre class="programlisting">p(a1, a2,... aN)
</pre>

- where <tt class="computeroutput">p</tt> is a parser, each
+ where <code class="computeroutput">p</code> is a parser, each
 of the arguments (a1...aN) can either be an immediate value, or a lazy
 function with signature:
 
<pre class="programlisting">T(Unused, Context)
</pre>

- where <tt class="computeroutput">T</tt>, the function's
+ where <code class="computeroutput">T</code>, the function's
 return value, is compatible with the argument type expected. For example,
 this is a valid expression:
 
@@ -57,8 +53,8 @@
 // of flag at parse time
</pre>

- since <tt class="computeroutput">phoenix::ref(f)</tt> is
- a function that returns a <tt class="computeroutput">bool</tt>.
+ since <code class="computeroutput">phoenix::ref(f)</code> is
+ a function that returns a <code class="computeroutput">bool</code>.
 
</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/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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<link rel="home" href="../../../index.html" title="Spirit 2.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" 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>
@@ -24,42 +23,39 @@
<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.qi.quick_reference.non_terminals"></a>Non-terminals
-</h4></div></div>
-<div></div>
-</div>
+<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">
Notation
<dl>
-<dt><tt class="computeroutput">RT</tt></dt>
+<dt><code class="computeroutput">RT</code></dt>
<dd>
 Synthesized attribute. The rule or grammar's return type.
 </dd>
-<dt><tt class="computeroutput">Arg1</tt>,
- <tt class="computeroutput">Arg2</tt>, <tt class="computeroutput">ArgN</tt></dt>
+<dt><code class="computeroutput">Arg1</code>,
+ <code class="computeroutput">Arg2</code>, <code class="computeroutput">ArgN</code></dt>
<dd>
 Inherited attributes. Zero or more or arguments.
 </dd>
-<dt><tt class="computeroutput">L1</tt>,
- <tt class="computeroutput">L2</tt>, <tt class="computeroutput">LN</tt></dt>
+<dt><code class="computeroutput">L1</code>,
+ <code class="computeroutput">L2</code>, <code class="computeroutput">LN</code></dt>
<dd>
 Zero or more local variables.
 </dd>
-<dt><tt class="computeroutput">r, r2</tt></dt>
+<dt><code class="computeroutput">r, r2</code></dt>
<dd>
 Rules
 </dd>
-<dt><tt class="computeroutput">g</tt></dt>
+<dt><code class="computeroutput">g</code></dt>
<dd>
 A grammar
 </dd>
-<dt><tt class="computeroutput">p</tt></dt>
+<dt><code class="computeroutput">p</code></dt>
<dd>
 A parser expression
 </dd>
-<dt><tt class="computeroutput">my_grammar</tt></dt>
+<dt><code class="computeroutput">my_grammar</code></dt>
<dd>
 A user defined grammar
 </dd>
@@ -70,14 +66,14 @@
<dl>
<dt>Signature</dt>
<dd>
- <tt class="computeroutput">RT(Arg1, Arg2 ...
- ,ArgN)</tt>. The signature specifies the synthesized
+ <code class="computeroutput">RT(Arg1, Arg2 ...
+ ,ArgN)</code>. The signature specifies the synthesized
 (return value) and inherited (arguments) attributes.
 </dd>
<dt>Locals</dt>
<dd>
- <tt class="computeroutput">locals<L1, L2 ...,
- LN></tt>.
+ <code class="computeroutput">locals<L1, L2 ...,
+ LN></code>.
 The local variables.
 </dd>
<dt>Skipper</dt>
@@ -89,12 +85,12 @@
<div class="variablelist">
Template Arguments
<dl>
-<dt><tt class="computeroutput">Iterator</tt></dt>
+<dt><code class="computeroutput">Iterator</code></dt>
<dd>
 The iterator type you will use for parsing.
 </dd>
-<dt><tt class="computeroutput">A1</tt>,
- <tt class="computeroutput">A2</tt>, <tt class="computeroutput">A3</tt></dt>
+<dt><code class="computeroutput">A1</code>,
+ <code class="computeroutput">A2</code>, <code class="computeroutput">A3</code></dt>
<dd>
 Can be one of 1)Signature 2)Locals 3)Skipper.
 </dd>
@@ -106,120 +102,164 @@
<col>
</colgroup>
<thead><tr>
-<th>
+<th>
+ 
 Expression
- </th>
-<th>
+ 
+ </th>
+<th>
+ 
 Description
- </th>
+ 
+ </th>
</tr></thead>
<tbody>
<tr>
-<td>
- <tt class="computeroutput">rule<Iterator,
+<td>
+ 
+ <code class="computeroutput">rule<Iterator,
 A1,
 A2,
 A3>
- r(name);</tt>
- </td>
-<td>
- Rule declaration. <tt class="computeroutput">Iterator</tt>
- is required. <tt class="computeroutput">A1, A2, A3</tt>
- are optional and can be specified in any order. <tt class="computeroutput">name</tt>
+ r(name);</code>
+ 
+ </td>
+<td>
+ 
+ Rule declaration. <code class="computeroutput">Iterator</code>
+ is required. <code class="computeroutput">A1, A2, A3</code>
+ are optional and can be specified in any order. <code class="computeroutput">name</code>
 is an optional string that gives the rule its name, useful for
 debugging and error handling.
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">rule<Iterator,
+<td>
+ 
+ <code class="computeroutput">rule<Iterator,
 A1,
 A2,
 A3>
- r(r2);</tt>
- </td>
-<td>
- Copy construct rule <tt class="computeroutput">r</tt>
- from rule <tt class="computeroutput">r2</tt>.
- <tt class="computeroutput">boost::shared_ptr</tt> semantics.
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">r =
- r2;</tt>
- </td>
-<td>
- Assign rule <tt class="computeroutput">r2</tt>
- to <tt class="computeroutput">r</tt>. <tt class="computeroutput">boost::shared_ptr</tt> semantics.
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">r.alias()</tt>
- </td>
-<td>
- return an alias of <tt class="computeroutput">r</tt>.
- The alias is a parser that holds a reference to <tt class="computeroutput">r</tt>.
+ r(r2);</code>
+ 
+ </td>
+<td>
+ 
+ Copy construct rule <code class="computeroutput">r</code>
+ from rule <code class="computeroutput">r2</code>.
+ <code class="computeroutput">boost::shared_ptr</code> semantics.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">r =
+ r2;</code>
+ 
+ </td>
+<td>
+ 
+ Assign rule <code class="computeroutput">r2</code>
+ to <code class="computeroutput">r</code>. <code class="computeroutput">boost::shared_ptr</code> semantics.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">r.alias()</code>
+ 
+ </td>
+<td>
+ 
+ return an alias of <code class="computeroutput">r</code>.
+ The alias is a parser that holds a reference to <code class="computeroutput">r</code>.
 Reference semantics.
- </td>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">r.copy()</code>
+ 
+ </td>
+<td>
+ 
+ Get a copy of <code class="computeroutput">r</code>.
+ <code class="computeroutput">boost::shared_ptr</code> semantics.
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">r.copy()</tt>
- </td>
-<td>
- Get a copy of <tt class="computeroutput">r</tt>.
- <tt class="computeroutput">boost::shared_ptr</tt> semantics.
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">r.name(name)</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">r.name(name)</code>
+ 
+ </td>
+<td>
+ 
 Naming a rule
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">r.name()</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">r.name()</code>
+ 
+ </td>
+<td>
+ 
 Getting the name of a rule
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
+<td>
+ 
 debug(r)
- </td>
-<td>
- Debug rule <tt class="computeroutput">r</tt>
- </td>
+ 
+ </td>
+<td>
+ 
+ Debug rule <code class="computeroutput">r</code>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">r =
- p;</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">r =
+ p;</code>
+ 
+ </td>
+<td>
+ 
 Rule definition
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">r %=
- p;</tt>
- </td>
-<td>
- Auto-rule definition. The attribute of <tt class="computeroutput">p</tt>
- should be compatible with the synthesized attribute of <tt class="computeroutput">r</tt>. When <tt class="computeroutput">p</tt>
- is successful, its attribute is automatically propagated to <tt class="computeroutput">r</tt>'s synthesized attribute.
- </td>
+<td>
+ 
+ <code class="computeroutput">r %=
+ p;</code>
+ 
+ </td>
+<td>
+ 
+ Auto-rule definition. The attribute of <code class="computeroutput">p</code>
+ should be compatible with the synthesized attribute of <code class="computeroutput">r</code>. When <code class="computeroutput">p</code>
+ is successful, its attribute is automatically propagated to <code class="computeroutput">r</code>'s synthesized attribute.
+ 
+ </td>
</tr>
<tr>
<td>
-
+ 


<pre xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="table-programlisting">template <typename Iterator>
@@ -237,36 +277,50 @@
</pre>

 
-</td>
-<td>
- Grammar definition. <tt class="computeroutput">name</tt>
+ </td>
+<td>
+ 
+ Grammar definition. <code class="computeroutput">name</code>
 is an optional string that gives the grammar its name, useful for
 debugging and error handling.
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
+<td>
+ 
 my_grammar<Iterator> g
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 Instantiating a grammar
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">g.name(name)</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">g.name(name)</code>
+ 
+ </td>
+<td>
+ 
 Naming a grammar
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">g.name()</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">g.name()</code>
+ 
+ </td>
+<td>
+ 
 Getting the name of a grammar
- </td>
+ 
+ </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-06-23 00:30:19 EDT (Tue, 23 Jun 2009)
@@ -3,12 +3,11 @@
<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">
-<link rel="home" href="../../../index.html" title="Spirit 2.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" 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="next" href="../../karma.html" title=" Karma">
+<link rel="prev" href="semantic_actions.html" title="Semantic Actions">
+<link rel="next" href="../../karma.html" title="Karma">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
<table cellpadding="2" width="100%"><tr>
@@ -24,12 +23,9 @@
<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="../../karma.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="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>

 __boostphoenix_ makes it easier to
 attach semantic actions. You just inline your lambda expressions:
@@ -38,37 +34,37 @@
</pre>

 Spirit.Qi provides some __boostphoenix_
- placeholders to important information from the <tt class="computeroutput">Attr</tt>
- and <tt class="computeroutput">Context</tt> that are otherwise
+ placeholders to important information from the <code class="computeroutput">Attr</code>
+ and <code class="computeroutput">Context</code> that are otherwise
 fiddly to extract.
 
<div class="variablelist">
Spirit.Qi specific Phoenix placeholders
<dl>
-<dt><tt class="computeroutput">_1, _2... , _N</tt></dt>
+<dt><code class="computeroutput">_1, _2... , _N</code></dt>
<dd>
- Nth attribute of <tt class="computeroutput">p</tt>
+ Nth attribute of <code class="computeroutput">p</code>
 </dd>
-<dt><tt class="computeroutput">_val</tt></dt>
+<dt><code class="computeroutput">_val</code></dt>
<dd>
 The enclosing rule's synthesized attribute.
 </dd>
-<dt><tt class="computeroutput">_r1, _r2... , _rN</tt></dt>
+<dt><code class="computeroutput">_r1, _r2... , _rN</code></dt>
<dd>
 The enclosing rule's Nth inherited attribute.
 </dd>
-<dt><tt class="computeroutput">_a, _b... , _j</tt></dt>
+<dt><code class="computeroutput">_a, _b... , _j</code></dt>
<dd>
- The enclosing rule's local variables (<tt class="computeroutput">_a</tt>
+ The enclosing rule's local variables (<code class="computeroutput">_a</code>
 refers to the first).
 </dd>
-<dt><tt class="computeroutput">_val</tt></dt>
+<dt><code class="computeroutput">_val</code></dt>
<dd>
 The enclosing rule's synthesized attribute.
 </dd>
-<dt><tt class="computeroutput">_pass</tt></dt>
+<dt><code class="computeroutput">_pass</code></dt>
<dd>
- Assign <tt class="computeroutput">false</tt> to <tt class="computeroutput">_pass</tt> to force a parser failure.
+ Assign <code class="computeroutput">false</code> to <code class="computeroutput">_pass</code> to force a parser failure.
 </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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<link rel="home" href="../../../index.html" title="Spirit 2.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" 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,14 +23,10 @@
<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="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>
+<th>
+ 
 Expression
- </th>
-<th>
+ 
+ </th>
+<th>
+ 
 Attribute
- </th>
-<th>
+ 
+ </th>
+<th>
+ 
 Description
- </th>
+ 
+ </th>
</tr></thead>
<tbody>
<tr>
-<td>
- <tt class="computeroutput">eol</tt>
- </td>
-<td>
- <tt class="computeroutput">Unused</tt>
- </td>
-<td>
- Matches the end of line (<tt class="computeroutput">\r</tt> or <tt class="computeroutput">\n</tt> or <tt class="computeroutput">\r\n</tt>)
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">eoi</tt>
- </td>
-<td>
- <tt class="computeroutput">Unused</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">eol</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">Unused</code>
+ 
+ </td>
+<td>
+ 
+ Matches the end of line (<code class="computeroutput">\r</code> or <code class="computeroutput">\n</code> or <code class="computeroutput">\r\n</code>)
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">eoi</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">Unused</code>
+ 
+ </td>
+<td>
+ 
 Matches the end of input (first == last)
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">eps</tt>
- </td>
-<td>
- <tt class="computeroutput">Unused</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">eps</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">Unused</code>
+ 
+ </td>
+<td>
+ 
 Match an empty string
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">eps(b)</tt>
- </td>
-<td>
- <tt class="computeroutput">Unused</tt>
- </td>
-<td>
- If <tt class="computeroutput">b</tt> is true, match
+<td>
+ 
+ <code class="computeroutput">eps(b)</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">Unused</code>
+ 
+ </td>
+<td>
+ 
+ If <code class="computeroutput">b</code> is true, match
 an empty string
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">lazy(fp)</tt>
- </td>
-<td>
- Attribute of <tt class="computeroutput">P</tt>
- where <tt class="computeroutput">P</tt> is the
- return type of <tt class="computeroutput">fp</tt>
- </td>
-<td>
- Invoke <tt class="computeroutput">fp</tt> at parse
- time, returning a parser <tt class="computeroutput">p</tt>
+<td>
+ 
+ <code class="computeroutput">lazy(fp)</code>
+ 
+ </td>
+<td>
+ 
+ Attribute of <code class="computeroutput">P</code>
+ where <code class="computeroutput">P</code> is the
+ return type of <code class="computeroutput">fp</code>
+ 
+ </td>
+<td>
+ 
+ Invoke <code class="computeroutput">fp</code> at parse
+ time, returning a parser <code class="computeroutput">p</code>
 which is then called to parse.
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">fp</tt>
- </td>
-<td>
- see <tt class="computeroutput">lazy(fp)</tt>
+<td>
+ 
+ <code class="computeroutput">fp</code>
+ 
+ </td>
+<td>
+ 
+ see <code class="computeroutput">lazy(fp)</code>
 above
- </td>
-<td>
- Equivalent to <tt class="computeroutput">lazy[fp]</tt>
- </td>
+ 
+ </td>
+<td>
+ 
+ Equivalent to <code class="computeroutput">lazy[fp]</code>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">p[fa]</tt>
- </td>
-<td>
- Attribute of <tt class="computeroutput">p</tt>
- </td>
-<td>
- Call semantic action, <tt class="computeroutput">fa</tt>
+<td>
+ 
+ <code class="computeroutput">p[fa]</code>
+ 
+ </td>
+<td>
+ 
+ Attribute of <code class="computeroutput">p</code>
+ 
+ </td>
+<td>
+ 
+ Call semantic action, <code class="computeroutput">fa</code>
 if p succeeds.
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">byte_</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">byte_</code>
+ 
+ </td>
+<td>
+ 
 8 bits native endian
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 Matches an 8 bit binary
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">word</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">word</code>
+ 
+ </td>
+<td>
+ 
 16 bits native endian
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 Matches a 16 bit binary
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">big_word</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">big_word</code>
+ 
+ </td>
+<td>
+ 
 16 bits big endian
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 Matches a 16 bit binary
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">little_word</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">little_word</code>
+ 
+ </td>
+<td>
+ 
 16 bits little endian
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 Matches a 16 bit binary
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">dword</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">dword</code>
+ 
+ </td>
+<td>
+ 
 32 bits native endian
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 Matches a 32 bit binary
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">big_dword</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">big_dword</code>
+ 
+ </td>
+<td>
+ 
 32 bits big endian
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 Matches a 32 bit binary
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">little_dword</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">little_dword</code>
+ 
+ </td>
+<td>
+ 
 32 bits little endian
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 Matches a 32 bit binary
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">qword</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">qword</code>
+ 
+ </td>
+<td>
+ 
 64 bits native endian
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 Matches a 64 bit binary
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">big_qword</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">big_qword</code>
+ 
+ </td>
+<td>
+ 
 64 bits big endian
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 Matches a 64 bit binary
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">little_qword</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">little_qword</code>
+ 
+ </td>
+<td>
+ 
 64 bits little endian
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 Matches a 64 bit binary
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">char_</tt>
- </td>
-<td>
- <tt class="computeroutput">Ch</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">char_</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">Ch</code>
+ 
+ </td>
+<td>
+ 
 Matches any character
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">char_(ch)</tt>
- </td>
-<td>
- <tt class="computeroutput">Ch</tt>
- </td>
-<td>
- Matches <tt class="computeroutput">ch</tt>
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">char_("c")</tt>
- </td>
-<td>
- <tt class="computeroutput">Ch</tt>
- </td>
-<td>
- Matches a single char string literal, <tt class="computeroutput">c</tt>
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">char_(ch,
- ch2)</tt>
- </td>
-<td>
- <tt class="computeroutput">Ch</tt>
- </td>
-<td>
- Matches a range of chars from <tt class="computeroutput">ch</tt>
- to <tt class="computeroutput">ch2</tt> (inclusive)
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">char_(chset)</tt>
- </td>
-<td>
- <tt class="computeroutput">Ch</tt>
- </td>
-<td>
- Matches a character set <tt class="computeroutput">chset</tt>
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">ch</tt>
- </td>
-<td>
- <tt class="computeroutput">Unused</tt>
- </td>
-<td>
- Matches <tt class="computeroutput">ch</tt>
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">str</tt>
- </td>
-<td>
- <tt class="computeroutput">Unused</tt>
- </td>
-<td>
- Matches <tt class="computeroutput">str</tt>
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">lit(ch)</tt>
- </td>
-<td>
- <tt class="computeroutput">Unused</tt>
- </td>
-<td>
- Matches <tt class="computeroutput">ch</tt>
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">lit(str)</tt>
- </td>
-<td>
- <tt class="computeroutput">Unused</tt>
- </td>
-<td>
- Matches <tt class="computeroutput">str</tt>
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">string(str)</tt>
- </td>
-<td>
- <tt class="computeroutput">Str</tt>
- </td>
-<td>
- Matches <tt class="computeroutput">str</tt>
- </td>
+<td>
+ 
+ <code class="computeroutput">char_(ch)</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">Ch</code>
+ 
+ </td>
+<td>
+ 
+ Matches <code class="computeroutput">ch</code>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">char_("c")</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">Ch</code>
+ 
+ </td>
+<td>
+ 
+ Matches a single char string literal, <code class="computeroutput">c</code>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">symbols<Ch,
+<td>
+ 
+ <code class="computeroutput">char_(ch,
+ ch2)</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">Ch</code>
+ 
+ </td>
+<td>
+ 
+ Matches a range of chars from <code class="computeroutput">ch</code>
+ to <code class="computeroutput">ch2</code> (inclusive)
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">char_(chset)</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">Ch</code>
+ 
+ </td>
+<td>
+ 
+ Matches a character set <code class="computeroutput">chset</code>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">ch</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">Unused</code>
+ 
+ </td>
+<td>
+ 
+ Matches <code class="computeroutput">ch</code>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">str</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">Unused</code>
+ 
+ </td>
+<td>
+ 
+ Matches <code class="computeroutput">str</code>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">lit(ch)</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">Unused</code>
+ 
+ </td>
+<td>
+ 
+ Matches <code class="computeroutput">ch</code>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">lit(str)</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">Unused</code>
+ 
+ </td>
+<td>
+ 
+ Matches <code class="computeroutput">str</code>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">string(str)</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">Str</code>
+ 
+ </td>
+<td>
+ 
+ Matches <code class="computeroutput">str</code>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">symbols<Ch,
 T>
- sym;</tt>
- </td>
-<td>
+ sym;</code>
+ 
+ </td>
+<td>
+ 
 N/A
- </td>
-<td>
- Declare a symbol table, <tt class="computeroutput">sym</tt>.
- <tt class="computeroutput">Ch</tt> is the underlying
- char type of the symbol table keys. <tt class="computeroutput">T</tt>
+ 
+ </td>
+<td>
+ 
+ Declare a symbol table, <code class="computeroutput">sym</code>.
+ <code class="computeroutput">Ch</code> is the underlying
+ char type of the symbol table keys. <code class="computeroutput">T</code>
 is the data type associated with each key.
- </td>
+ 
+ </td>
</tr>
<tr>
<td>
-
+ 


<pre xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="table-programlisting">sym.add
@@ -386,461 +554,687 @@
</pre>

 
-</td>
-<td>
+ </td>
+<td>
+ 
 N/A
- </td>
-<td>
- Add symbols into a symbol table, <tt class="computeroutput">sym</tt>.
- val1 and val2 are optional data of type <tt class="computeroutput">T</tt>,
+ 
+ </td>
+<td>
+ 
+ Add symbols into a symbol table, <code class="computeroutput">sym</code>.
+ val1 and val2 are optional data of type <code class="computeroutput">T</code>,
 the data type associated with each key.
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">sym</tt>
- </td>
-<td>
- <tt class="computeroutput">T</tt>
- </td>
-<td>
- Matches entries in the symbol table, <tt class="computeroutput">sym</tt>.
+<td>
+ 
+ <code class="computeroutput">sym</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">T</code>
+ 
+ </td>
+<td>
+ 
+ Matches entries in the symbol table, <code class="computeroutput">sym</code>.
 If successful, returns the data associated with the key
- </td>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">lexeme[a]</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">A</code>
+ 
+ </td>
+<td>
+ 
+ Disable skip parsing for <code class="computeroutput">a</code>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">nocase[a]</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">A</code>
+ 
+ </td>
+<td>
+ 
+ Inhibits case-sensitivity for <code class="computeroutput">a</code>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">omit[a]</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">Unused</code>
+ 
+ </td>
+<td>
+ 
+ Ignores the attribute type of <code class="computeroutput">a</code>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">lexeme[a]</tt>
- </td>
-<td>
- <tt class="computeroutput">A</tt>
- </td>
-<td>
- Disable skip parsing for <tt class="computeroutput">a</tt>
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">nocase[a]</tt>
- </td>
-<td>
- <tt class="computeroutput">A</tt>
- </td>
-<td>
- Inhibits case-sensitivity for <tt class="computeroutput">a</tt>
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">omit[a]</tt>
- </td>
-<td>
- <tt class="computeroutput">Unused</tt>
- </td>
-<td>
- Ignores the attribute type of <tt class="computeroutput">a</tt>
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">raw[a]</tt>
- </td>
-<td>
- <tt class="computeroutput">boost::iterator_range<I></tt>
- </td>
-<td>
- Presents the transduction of <tt class="computeroutput">a</tt>
+<td>
+ 
+ <code class="computeroutput">raw[a]</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">boost::iterator_range<I></code>
+ 
+ </td>
+<td>
+ 
+ Presents the transduction of <code class="computeroutput">a</code>
 as an iterator range
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">repeat[a]</tt>
- </td>
-<td>
- <tt class="computeroutput">vector<A></tt>
- </td>
-<td>
- Repeat <tt class="computeroutput">a</tt> zero or
+<td>
+ 
+ <code class="computeroutput">repeat[a]</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">vector<A></code>
+ 
+ </td>
+<td>
+ 
+ Repeat <code class="computeroutput">a</code> zero or
 more times
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">repeat(N)[a]</tt>
- </td>
-<td>
- <tt class="computeroutput">vector<A></tt>
- </td>
-<td>
- Repeat <tt class="computeroutput">a</tt> <tt class="computeroutput">N</tt> times
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">repeat(N,
- M)[a]</tt>
- </td>
-<td>
- <tt class="computeroutput">vector<A></tt>
- </td>
-<td>
- Repeat <tt class="computeroutput">a</tt> <tt class="computeroutput">N</tt> to <tt class="computeroutput">M</tt>
+<td>
+ 
+ <code class="computeroutput">repeat(N)[a]</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">vector<A></code>
+ 
+ </td>
+<td>
+ 
+ Repeat <code class="computeroutput">a</code> <code class="computeroutput">N</code> times
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">repeat(N,
+ M)[a]</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">vector<A></code>
+ 
+ </td>
+<td>
+ 
+ Repeat <code class="computeroutput">a</code> <code class="computeroutput">N</code> to <code class="computeroutput">M</code>
 times
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">repeat(N,
- inf)[a]</tt>
- </td>
-<td>
- <tt class="computeroutput">vector<A></tt>
- </td>
-<td>
- Repeat <tt class="computeroutput">a</tt> <tt class="computeroutput">N</tt> or more times
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">skip[a]</tt>
- </td>
-<td>
- <tt class="computeroutput">A</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">repeat(N,
+ inf)[a]</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">vector<A></code>
+ 
+ </td>
+<td>
+ 
+ Repeat <code class="computeroutput">a</code> <code class="computeroutput">N</code> or more times
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">skip[a]</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">A</code>
+ 
+ </td>
+<td>
+ 
 Reestablish the skipper that got inhibited by lexeme
- </td>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">skip(p)[a]</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">A</code>
+ 
+ </td>
+<td>
+ 
+ Use <code class="computeroutput">p</code> as a skipper
+ for parsing <code class="computeroutput">a</code>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">float_</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">float</code>
+ 
+ </td>
+<td>
+ 
+ Parse a floating point number into a <code class="computeroutput">float</code>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">skip(p)[a]</tt>
- </td>
-<td>
- <tt class="computeroutput">A</tt>
- </td>
-<td>
- Use <tt class="computeroutput">p</tt> as a skipper
- for parsing <tt class="computeroutput">a</tt>
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">float_</tt>
- </td>
-<td>
- <tt class="computeroutput">float</tt>
- </td>
-<td>
- Parse a floating point number into a <tt class="computeroutput">float</tt>
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">double_</tt>
- </td>
-<td>
- <tt class="computeroutput">double</tt>
- </td>
-<td>
- Parse a floating point number into a <tt class="computeroutput">double</tt>
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">long_double</tt>
- </td>
-<td>
- <tt class="computeroutput">long double</tt>
- </td>
-<td>
- Parse a floating point number into a <tt class="computeroutput">long
- double</tt>
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">bin</tt>
- </td>
-<td>
- <tt class="computeroutput">unsigned</tt>
- </td>
-<td>
- Parse a binary integer into an <tt class="computeroutput">unsigned</tt>
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">oct</tt>
- </td>
-<td>
- <tt class="computeroutput">unsigned</tt>
- </td>
-<td>
- Parse an octal integer into an <tt class="computeroutput">unsigned</tt>
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">hex</tt>
- </td>
-<td>
- <tt class="computeroutput">unsigned</tt>
- </td>
-<td>
- Parse a hexadecimal integer into an <tt class="computeroutput">unsigned</tt>
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">ushort_</tt>
- </td>
-<td>
- <tt class="computeroutput">unsigned short</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">double_</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">double</code>
+ 
+ </td>
+<td>
+ 
+ Parse a floating point number into a <code class="computeroutput">double</code>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">long_double</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">long double</code>
+ 
+ </td>
+<td>
+ 
+ Parse a floating point number into a <code class="computeroutput">long
+ double</code>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">bin</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">unsigned</code>
+ 
+ </td>
+<td>
+ 
+ Parse a binary integer into an <code class="computeroutput">unsigned</code>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">oct</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">unsigned</code>
+ 
+ </td>
+<td>
+ 
+ Parse an octal integer into an <code class="computeroutput">unsigned</code>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">hex</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">unsigned</code>
+ 
+ </td>
+<td>
+ 
+ Parse a hexadecimal integer into an <code class="computeroutput">unsigned</code>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">ushort_</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">unsigned short</code>
+ 
+ </td>
+<td>
+ 
 Parse an unsigned short integer
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">ulong_</tt>
- </td>
-<td>
- <tt class="computeroutput">unsigned long</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">ulong_</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">unsigned long</code>
+ 
+ </td>
+<td>
+ 
 Parse an unsigned long integer
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">uint_</tt>
- </td>
-<td>
- <tt class="computeroutput">unsigned int</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">uint_</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">unsigned int</code>
+ 
+ </td>
+<td>
+ 
 Parse an unsigned int
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">ulong_long</tt>
- </td>
-<td>
- <tt class="computeroutput">unsigned long
- long</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">ulong_long</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">unsigned long
+ long</code>
+ 
+ </td>
+<td>
+ 
 Parse an unsigned long long
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">short_</tt>
- </td>
-<td>
- <tt class="computeroutput">short</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">short_</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">short</code>
+ 
+ </td>
+<td>
+ 
 Parse a short integer
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">long_</tt>
- </td>
-<td>
- <tt class="computeroutput">long</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">long_</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">long</code>
+ 
+ </td>
+<td>
+ 
 Parse a long integer
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">int_</tt>
- </td>
-<td>
- <tt class="computeroutput">int</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">int_</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">int</code>
+ 
+ </td>
+<td>
+ 
 Parse an int
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">long_long</tt>
- </td>
-<td>
- <tt class="computeroutput">long long</tt>
- </td>
-<td>
+<td>
+ 
+ <code class="computeroutput">long_long</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">long long</code>
+ 
+ </td>
+<td>
+ 
 Parse a long long
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">!a</tt>
- </td>
-<td>
- <tt class="computeroutput">Unused</tt>
- </td>
-<td>
- Not predicate. Ensure that <tt class="computeroutput">a</tt>
+<td>
+ 
+ <code class="computeroutput">!a</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">Unused</code>
+ 
+ </td>
+<td>
+ 
+ Not predicate. Ensure that <code class="computeroutput">a</code>
 does not match but don't move the iterator position
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">&a</tt>
- </td>
-<td>
- <tt class="computeroutput">Unused</tt>
- </td>
-<td>
- And predicate. Ensure that <tt class="computeroutput">a</tt>
+<td>
+ 
+ <code class="computeroutput">&a</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">Unused</code>
+ 
+ </td>
+<td>
+ 
+ And predicate. Ensure that <code class="computeroutput">a</code>
 matches but don't move the iterator position
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">-a</tt>
- </td>
-<td>
- <tt class="computeroutput">optional<A></tt>
- </td>
-<td>
- Optional. Parse <tt class="computeroutput">a</tt>
+<td>
+ 
+ <code class="computeroutput">-a</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">optional<A></code>
+ 
+ </td>
+<td>
+ 
+ Optional. Parse <code class="computeroutput">a</code>
 zero or one time
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">*a</tt>
- </td>
-<td>
- <tt class="computeroutput">vector<A></tt>
- </td>
-<td>
- Kleene. Parse <tt class="computeroutput">a</tt>
+<td>
+ 
+ <code class="computeroutput">*a</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">vector<A></code>
+ 
+ </td>
+<td>
+ 
+ Kleene. Parse <code class="computeroutput">a</code>
 zero or more times
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">+a</tt>
- </td>
-<td>
- <tt class="computeroutput">vector<A></tt>
- </td>
-<td>
- Plus. Parse <tt class="computeroutput">a</tt> one
+<td>
+ 
+ <code class="computeroutput">+a</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">vector<A></code>
+ 
+ </td>
+<td>
+ 
+ Plus. Parse <code class="computeroutput">a</code> one
 or more times
- </td>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">a |
+ b</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">variant<A,
+ B></code>
+ 
+ </td>
+<td>
+ 
+ Alternative. Parse <code class="computeroutput">a</code>
+ or <code class="computeroutput">b</code>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">a >>
+ b</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">tuple<A,
+ B></code>
+ 
+ </td>
+<td>
+ 
+ Sequence. Parse <code class="computeroutput">a</code>
+ followed by <code class="computeroutput">b</code>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">a |
- b</tt>
- </td>
-<td>
- <tt class="computeroutput">variant<A,
- B></tt>
- </td>
-<td>
- Alternative. Parse <tt class="computeroutput">a</tt>
- or <tt class="computeroutput">b</tt>
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">a >>
- b</tt>
- </td>
-<td>
- <tt class="computeroutput">tuple<A,
- B></tt>
- </td>
-<td>
- Sequence. Parse <tt class="computeroutput">a</tt>
- followed by <tt class="computeroutput">b</tt>
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">a >
- b</tt>
- </td>
-<td>
- <tt class="computeroutput">tuple<A,
- B></tt>
- </td>
-<td>
- Expect. Parse <tt class="computeroutput">a</tt>
- followed by <tt class="computeroutput">b</tt>.
- <tt class="computeroutput">b</tt> is expected to
- match when <tt class="computeroutput">a</tt> matches,
- otherwise, an <tt class="computeroutput">expectation_failure</tt>
+<td>
+ 
+ <code class="computeroutput">a >
+ b</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">tuple<A,
+ B></code>
+ 
+ </td>
+<td>
+ 
+ Expect. Parse <code class="computeroutput">a</code>
+ followed by <code class="computeroutput">b</code>.
+ <code class="computeroutput">b</code> is expected to
+ match when <code class="computeroutput">a</code> matches,
+ otherwise, an <code class="computeroutput">expectation_failure</code>
 is thrown.
- </td>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">a -
+ b</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">A</code>
+ 
+ </td>
+<td>
+ 
+ Difference. Parse <code class="computeroutput">a</code>
+ but not <code class="computeroutput">b</code>
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">a ||
+ b</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">tuple<A,
+ B></code>
+ 
+ </td>
+<td>
+ 
+ Sequential Or. Parse <code class="computeroutput">a</code>
+ or <code class="computeroutput">b</code> or <code class="computeroutput">a</code> followed by <code class="computeroutput">b</code>
+ 
+ </td>
</tr>
<tr>
-<td>
- <tt class="computeroutput">a -
- b</tt>
- </td>
-<td>
- <tt class="computeroutput">A</tt>
- </td>
-<td>
- Difference. Parse <tt class="computeroutput">a</tt>
- but not <tt class="computeroutput">b</tt>
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">a ||
- b</tt>
- </td>
-<td>
- <tt class="computeroutput">tuple<A,
- B></tt>
- </td>
-<td>
- Sequential Or. Parse <tt class="computeroutput">a</tt>
- or <tt class="computeroutput">b</tt> or <tt class="computeroutput">a</tt> followed by <tt class="computeroutput">b</tt>
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">a %
- b</tt>
- </td>
-<td>
- <tt class="computeroutput">vector<A></tt>
- </td>
-<td>
- List. Parse <tt class="computeroutput">a</tt> delimited
- <tt class="computeroutput">b</tt> one or more times
- </td>
-</tr>
-<tr>
-<td>
- <tt class="computeroutput">a ^
- b</tt>
- </td>
-<td>
- <tt class="computeroutput">tuple<</tt>
- <tt class="computeroutput">optional<A>,</tt>
- <tt class="computeroutput">optional<B>
- ></tt>
- </td>
-<td>
- Permutation. Parse <tt class="computeroutput">a</tt>
- and <tt class="computeroutput">b</tt> in any order
- </td>
+<td>
+ 
+ <code class="computeroutput">a %
+ b</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">vector<A></code>
+ 
+ </td>
+<td>
+ 
+ List. Parse <code class="computeroutput">a</code> delimited
+ <code class="computeroutput">b</code> one or more times
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ <code class="computeroutput">a ^
+ b</code>
+ 
+ </td>
+<td>
+ 
+ <code class="computeroutput">tuple<</code>
+ <code class="computeroutput">optional<A>,</code>
+ <code class="computeroutput">optional<B>
+ ></code>
+ 
+ </td>
+<td>
+ 
+ Permutation. Parse <code class="computeroutput">a</code>
+ and <code class="computeroutput">b</code> in any order
+ 
+ </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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<link rel="home" href="../../../index.html" title="Spirit 2.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" 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">
@@ -24,21 +23,17 @@
<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="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>

 Has the form:
 
<pre class="programlisting">p[f]
</pre>

- where <tt class="computeroutput">f</tt> is a function with
+ where <code class="computeroutput">f</code> is a function with
 the signatures:
 
<pre class="programlisting">void f(Attr const&);
@@ -46,7 +41,7 @@
void f(Attr const&, Context&, bool&);
</pre>

- 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:
 
@@ -55,7 +50,7 @@
void operator()(Attr const&, Context&, bool&) const;
</pre>

- The <tt class="computeroutput">unused_type</tt> is used
+ The <code class="computeroutput">unused_type</code> is used
 in the signatures above to signify 'don't care'.
 
</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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<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">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" href="../../index.html" title="Spirit 2.1">
+<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">
@@ -23,12 +23,9 @@
<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="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>Quick Start</dt>
<dt>Warming up</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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<link rel="home" href="../../../index.html" title="Spirit 2.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" 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>
@@ -25,14 +23,10 @@
<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="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>

 Well, not really a complex parser, but a parser that parses complex numbers.
 This time, we're using Phoenix
@@ -49,9 +43,9 @@
 
<div class="orderedlist"><ol type="1">
<li>
- Alternates: e.g. <tt class="computeroutput">a |
- b</tt>. Try <tt class="computeroutput">a</tt>
- first. If it succeeds, good. If not, try the next alternative, <tt class="computeroutput">b</tt>.
+ Alternates: e.g. <code class="computeroutput">a |
+ b</code>. Try <code class="computeroutput">a</code>
+ first. If it succeeds, good. If not, try the next alternative, <code class="computeroutput">b</code>.
 </li>
<li>
 Optionals: e.g. -p. Match the parser p zero or one time.
@@ -66,7 +60,7 @@
 number is optional)
 </li>
<li>
-OR a single real number.
+OR a single real number.
 </li>
</ul></div>

@@ -124,15 +118,15 @@
 The full cpp file for this example can be found here: ../../example/qi/complex_number.cpp
 

- The <tt class="computeroutput">double_</tt> parser attaches
+ The <code class="computeroutput">double_</code> parser attaches
 this action:
 
<pre class="programlisting">ref(n) = _1
</pre>

- This assigns the parsed result (actually, the attribute of <tt class="computeroutput">double_</tt>) to n. <tt class="computeroutput">ref(n)</tt>
- tells Phoenix that <tt class="computeroutput">n</tt> is
- a mutable reference. <tt class="computeroutput">_1</tt>
+ This assigns the parsed result (actually, the attribute of <code class="computeroutput">double_</code>) to n. <code class="computeroutput">ref(n)</code>
+ tells Phoenix that <code class="computeroutput">n</code> is
+ a mutable reference. <code class="computeroutput">_1</code>
 is a Phoenix placeholder for the parsed result attribute.
 
</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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<link rel="home" href="../../../index.html" title="Spirit 2.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" 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">
@@ -24,14 +23,10 @@
<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="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>

 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?
@@ -158,15 +153,15 @@
struct employee_parser : grammar<Iterator, employee(), space_type>
</pre>

- <tt class="computeroutput">employee_parser</tt> is a grammar.
+ <code class="computeroutput">employee_parser</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:
 
<pre class="programlisting">employee()
</pre>

- meaning, the parser generates employee structs. <tt class="computeroutput">employee_parser</tt>
- skips white spaces using <tt class="computeroutput">space_type</tt>
+ meaning, the parser generates employee structs. <code class="computeroutput">employee_parser</code>
+ skips white spaces using <code class="computeroutput">space_type</code>
 as its skip parser.
 
<pre class="programlisting">employee_parser() : employee_parser::base_type(start)
@@ -178,19 +173,19 @@
rule<Iterator, employee(), space_type> start;
</pre>

- Declares two rules: <tt class="computeroutput">quoted_string</tt>
- and <tt class="computeroutput">start</tt>. <tt class="computeroutput">start</tt> has the same template parameters
- as the grammar itself. <tt class="computeroutput">quoted_string</tt>
- has a <tt class="computeroutput">std::string</tt> attribute.
- 
-<a name="spirit.qi.tutorials.employee___parsing_into_structs.lexeme"></a><h5>
-<a name="id428735"></a>
- Lexeme
- </h5>
+ Declares two rules: <code class="computeroutput">quoted_string</code>
+ and <code class="computeroutput">start</code>. <code class="computeroutput">start</code> has the same template parameters
+ as the grammar itself. <code class="computeroutput">quoted_string</code>
+ has a <code class="computeroutput">std::string</code> attribute.
+ 
+<a name="spirit.qi.tutorials.employee___parsing_into_structs.lexeme"></a><h6>
+<a name="id2621491"></a>
+ <a class="link" href="employee___parsing_into_structs.html#spirit.qi.tutorials.employee___parsing_into_structs.lexeme">Lexeme</a>
+ </h6>
<pre class="programlisting">lexeme['"' >> +(char_ - '"') >> '"'];
</pre>

- <tt class="computeroutput">lexeme</tt> inhibits space skipping
+ <code class="computeroutput">lexeme</code> inhibits space skipping
 from the open brace to the closing brace. The expression parses quoted
 strings.
 
@@ -200,35 +195,35 @@
 parses one or more chars, except the double quote. It stops when it sees
 a double quote.
 
-<a name="spirit.qi.tutorials.employee___parsing_into_structs.difference"></a><h5>
-<a name="id428891"></a>
- Difference
- </h5>
+<a name="spirit.qi.tutorials.employee___parsing_into_structs.difference"></a><h6>
+<a name="id2621635"></a>
+ <a class="link" href="employee___parsing_into_structs.html#spirit.qi.tutorials.employee___parsing_into_structs.difference">Difference</a>
+ </h6>

 The expression:
 
<pre class="programlisting">a - b
</pre>

- parses <tt class="computeroutput">a</tt> but not <tt class="computeroutput">b</tt>. Its attribute is just <tt class="computeroutput">A</tt>, the attribute of <tt class="computeroutput">a</tt>.
- <tt class="computeroutput">b</tt>'s attribute is ignored.
+ parses <code class="computeroutput">a</code> but not <code class="computeroutput">b</code>. Its attribute is just <code class="computeroutput">A</code>, the attribute of <code class="computeroutput">a</code>.
+ <code class="computeroutput">b</code>'s attribute is ignored.
 Hence, the attribute of:
 
<pre class="programlisting">char_ - '"'
</pre>

- is just <tt class="computeroutput">char</tt>.
+ is just <code class="computeroutput">char</code>.
 
-<a name="spirit.qi.tutorials.employee___parsing_into_structs.plus"></a><h5>
-<a name="id429050"></a>
- Plus
- </h5>
+<a name="spirit.qi.tutorials.employee___parsing_into_structs.plus"></a><h6>
+<a name="id2621778"></a>
+ <a class="link" href="employee___parsing_into_structs.html#spirit.qi.tutorials.employee___parsing_into_structs.plus">Plus</a>
+ </h6>
<pre class="programlisting">+a
</pre>

 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">std::vector<A></tt> where <tt class="computeroutput">A</tt>
- is the attribute of <tt class="computeroutput">a</tt>.
+ Like it's kin, the kleene star, its attribute is a <code class="computeroutput">std::vector<A></code> where <code class="computeroutput">A</code>
+ is the attribute of <code class="computeroutput">a</code>.
 So, putting all these together, the attribute of
 
<pre class="programlisting">+(char_ - '"')
@@ -238,11 +233,11 @@
 
<pre class="programlisting">std::vector<char>
</pre>
-<a name="spirit.qi.tutorials.employee___parsing_into_structs.sequence_attribute"></a><h5>
-<a name="id429236"></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="id2621946"></a>
+ <a class="link" href="employee___parsing_into_structs.html#spirit.qi.tutorials.employee___parsing_into_structs.sequence_attribute">Sequence
 Attribute</a>
- </h5>
+ </h6>

 Now what's the attribute of
 
@@ -262,45 +257,45 @@
<pre class="programlisting">fusion::vector<A, B, C>
</pre>

- where <tt class="computeroutput">A</tt> is the attribute
- of <tt class="computeroutput">a</tt>, <tt class="computeroutput">B</tt>
- is the attribute of <tt class="computeroutput">b</tt> and
- <tt class="computeroutput">C</tt> is the attribute of
- <tt class="computeroutput">c</tt>. What is <tt class="computeroutput">fusion::vector</tt>? - a tuple.
+ where <code class="computeroutput">A</code> is the attribute
+ of <code class="computeroutput">a</code>, <code class="computeroutput">B</code>
+ is the attribute of <code class="computeroutput">b</code> and
+ <code class="computeroutput">C</code> is the attribute of
+ <code class="computeroutput">c</code>. What is <code class="computeroutput">fusion::vector</code>? - a tuple.
 
<div class="note"><table border="0" summary="Note">
<tr>
<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../../../images/note.png"></td>
<th align="left">Note</th>
</tr>
-<tr><td colspan="2" align="left" valign="top">
+<tr><td align="left" valign="top">
 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.
 </td></tr>
</table></div>
-<a name="spirit.qi.tutorials.employee___parsing_into_structs.attribute_collapsing"></a><h5>
-<a name="id429558"></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="id2622239"></a>
+ <a class="link" href="employee___parsing_into_structs.html#spirit.qi.tutorials.employee___parsing_into_structs.attribute_collapsing">Attribute
 Collapsing</a>
- </h5>
+ </h6>

 Some parsers, especially those very little literal parsers you see, like
- <tt class="computeroutput">'"'</tt>, do not have attributes.
+ <code class="computeroutput">'"'</code>, do not have attributes.
 

 Nodes without attributes are disregarded. In a sequence, like above, all
- nodes with no attributes are filtered out of the <tt class="computeroutput">fusion:vector</tt>.
- So, since <tt class="computeroutput">'"'</tt> has no attribute,
- and <tt class="computeroutput">+(char_
- - '"')</tt> has a <tt class="computeroutput">std::vector<char></tt> attribute, the whole expression's attribute
+ nodes with no attributes are filtered out of the <code class="computeroutput">fusion:vector</code>.
+ So, since <code class="computeroutput">'"'</code> has no attribute,
+ and <code class="computeroutput">+(char_
+ - '"')</code> has a <code class="computeroutput">std::vector<char></code> attribute, the whole expression's attribute
 should have been:
 
<pre class="programlisting">fusion::vector<std::vector<char> >
</pre>

 But wait, there's one more collapsing rule: If after the attribute is a
- single element <tt class="computeroutput">fusion::vector</tt>, The element is stripped naked
+ single element <code class="computeroutput">fusion::vector</code>, The element is stripped naked
 from its container. So, to make a long story short, the attribute of the
 expression:
 
@@ -311,11 +306,11 @@
 
<pre class="programlisting">std::vector<char>
</pre>
-<a name="spirit.qi.tutorials.employee___parsing_into_structs.auto_rules"></a><h5>
-<a name="id429907"></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="id2622559"></a>
+ <a class="link" href="employee___parsing_into_structs.html#spirit.qi.tutorials.employee___parsing_into_structs.auto_rules">Auto
 Rules</a>
- </h5>
+ </h6>

 It is typical to see rules like:
 
@@ -329,11 +324,11 @@
<pre class="programlisting">r %= p;
</pre>

- The attribute of <tt class="computeroutput">p</tt> automatically
- uses the attribute of <tt class="computeroutput">r</tt>.
+ The attribute of <code class="computeroutput">p</code> automatically
+ uses the attribute of <code class="computeroutput">r</code>.
 

- So, going back to our <tt class="computeroutput">quoted_string</tt>
+ So, going back to our <code class="computeroutput">quoted_string</code>
 rule:
 
<pre class="programlisting">quoted_string %= lexeme['"' >> +(char_ - '"') >> '"'];
@@ -344,15 +339,15 @@
<pre class="programlisting">quoted_string = lexeme['"' >> +(char_ - '"') >> '"'][val_ = _1];
</pre>

- The attribute of the <tt class="computeroutput">quoted_string</tt>
- rule: <tt class="computeroutput">std::string</tt> is compatible
- with the attribute of the RHS: <tt class="computeroutput">std::vector<char></tt>. The RHS extracts the parsed attribute
+ The attribute of the <code class="computeroutput">quoted_string</code>
+ rule: <code class="computeroutput">std::string</code> is compatible
+ with the attribute of the RHS: <code class="computeroutput">std::vector<char></code>. The RHS extracts the parsed attribute
 directly into the rule's attribute, in-situ.
 
-<a name="spirit.qi.tutorials.employee___parsing_into_structs.finally"></a><h5>
-<a name="id430351"></a>
- Finally
- </h5>
+<a name="spirit.qi.tutorials.employee___parsing_into_structs.finally"></a><h6>
+<a name="id2622965"></a>
+ <a class="link" href="employee___parsing_into_structs.html#spirit.qi.tutorials.employee___parsing_into_structs.finally">Finally</a>
+ </h6>

 We're down to one rule, the start rule:
 
@@ -375,27 +370,27 @@
 These nodes do not have an attribute:
 
<div class="itemizedlist"><ul type="disc">
-<li><tt class="computeroutput">lit("employee")</tt></li>
-<li><tt class="computeroutput">'{'</tt></li>
-<li><tt class="computeroutput">'}'</tt></li>
+<li><code class="computeroutput">lit("employee")</code></li>
+<li><code class="computeroutput">'{'</code></li>
+<li><code class="computeroutput">'}'</code></li>
</ul></div>
<div class="note"><table border="0" summary="Note">
<tr>
<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../../../images/note.png"></td>
<th align="left">Note</th>
</tr>
-<tr><td colspan="2" align="left" valign="top">
- In case you are wondering, <tt class="computeroutput">lit("employee")</tt> is the same as "employee".
- We had to wrap it inside <tt class="computeroutput">lit</tt>
- because immediately after it is <tt class="computeroutput">>>
- '{'</tt>. You can't right-shift a <tt class="computeroutput">char[]</tt>
- and a <tt class="computeroutput">char</tt> - you know, C++
+<tr><td align="left" valign="top">
+ In case you are wondering, <code class="computeroutput">lit("employee")</code> is the same as "employee".
+ We had to wrap it inside <code class="computeroutput">lit</code>
+ because immediately after it is <code class="computeroutput">>>
+ '{'</code>. You can't right-shift a <code class="computeroutput">char[]</code>
+ and a <code class="computeroutput">char</code> - you know, C++
 syntax rules.
 </td></tr>
</table></div>

- Recall that the attribute of <tt class="computeroutput">start</tt>
- is the <tt class="computeroutput">employee</tt> struct:
+ Recall that the attribute of <code class="computeroutput">start</code>
+ is the <code class="computeroutput">employee</code> struct:
 

 
@@ -415,11 +410,11 @@

 

- Now everything is clear, right? The <tt class="computeroutput">struct
- employee</tt> IS
- compatible with <tt class="computeroutput">fusion::vector<int, std::string, std::string, double></tt>. So, the RHS of <tt class="computeroutput">start</tt>
- uses start's attribute (a <tt class="computeroutput">struct
- employee</tt>) in-situ when it does
+ Now everything is clear, right? The <code class="computeroutput">struct
+ employee</code> IS
+ compatible with <code class="computeroutput">fusion::vector<int, std::string, std::string, double></code>. So, the RHS of <code class="computeroutput">start</code>
+ uses start's attribute (a <code class="computeroutput">struct
+ employee</code>) in-situ when it does
 its work.
 
</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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<link rel="home" href="../../../index.html" title="Spirit 2.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" 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>
@@ -25,18 +23,15 @@
<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="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>

 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">struct
- employee</tt>. If we changed the implementation
- to parse one or more employees, the result would be a <tt class="computeroutput">std::vector<employee></tt>. We can go on and add more hierarchy:
+ representation of it in the form of a struct: the <code class="computeroutput">struct
+ employee</code>. If we changed the implementation
+ to parse one or more employees, the result would be a <code class="computeroutput">std::vector<employee></code>. We can go on and add more hierarchy:
 teams, departments, corporations. Then we'll have an AST representation
 of it all.
 
@@ -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.
 
-<a name="spirit.qi.tutorials.mini_xml___asts_.first_cut"></a><h5>
-<a name="id431258"></a>
- First Cut
- </h5>
+<a name="spirit.qi.tutorials.mini_xml___asts_.first_cut"></a><h6>
+<a name="id2623790"></a>
+ <a class="link" href="mini_xml___asts_.html#spirit.qi.tutorials.mini_xml___asts_.first_cut">First Cut</a>
+ </h6>

 Without further delay, here's the first version of the XML grammar:
 
@@ -134,7 +129,7 @@

 

- Going bottom up, let's examine the <tt class="computeroutput">text</tt>
+ Going bottom up, let's examine the <code class="computeroutput">text</code>
 rule:
 
<pre class="programlisting">rule<Iterator, std::string(), space_type> text;
@@ -146,13 +141,13 @@
</pre>

 The semantic action collects the chars and appends them (via +=) to the
- <tt class="computeroutput">std::string</tt> attribute of the rule (represented
- by the placeholder <tt class="computeroutput">_val</tt>).
+ <code class="computeroutput">std::string</code> attribute of the rule (represented
+ by the placeholder <code class="computeroutput">_val</code>).
 
-<a name="spirit.qi.tutorials.mini_xml___asts_.alternates"></a><h5>
-<a name="id432858"></a>
- Alternates
- </h5>
+<a name="spirit.qi.tutorials.mini_xml___asts_.alternates"></a><h6>
+<a name="id2625239"></a>
+ <a class="link" href="mini_xml___asts_.html#spirit.qi.tutorials.mini_xml___asts_.alternates">Alternates</a>
+ </h6>
<pre class="programlisting">rule<Iterator, mini_xml_node(), space_type> node;
</pre>

@@ -161,15 +156,15 @@
<pre class="programlisting">node = (xml | text) [_val = _1];
</pre>

- We'll see what a <tt class="computeroutput">mini_xml_node</tt>
+ We'll see what a <code class="computeroutput">mini_xml_node</code>
 structure later. Looking at the rule definition, we see some alternation
- goiing on here. An xml <tt class="computeroutput">node</tt>
- is either an <tt class="computeroutput">xml</tt> OR <tt class="computeroutput">text</tt>. Hmmm... hold on to that thought...
+ goiing on here. An xml <code class="computeroutput">node</code>
+ is either an <code class="computeroutput">xml</code> OR <code class="computeroutput">text</code>. Hmmm... hold on to that thought...
 
<pre class="programlisting">rule<Iterator, std::string(), space_type> start_tag;
</pre>

- Again, with an attribute of <tt class="computeroutput">std::string</tt>.
+ Again, with an attribute of <code class="computeroutput">std::string</code>.
 Then, it's definition:
 
<pre class="programlisting">start_tag =
@@ -179,46 +174,46 @@
 >> '>'
;
</pre>
-<a name="spirit.qi.tutorials.mini_xml___asts_.not_predicate"></a><h5>
-<a name="id433320"></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="id2625658"></a>
+ <a class="link" href="mini_xml___asts_.html#spirit.qi.tutorials.mini_xml___asts_.not_predicate">Not
 Predicate</a>
- </h5>
+ </h6>

- <tt class="computeroutput">start_tag</tt> is similar to
- the <tt class="computeroutput">text</tt> rule apart from
- the added <tt class="computeroutput">'<'</tt> and <tt class="computeroutput">'>'</tt>. But wait, to make sure that the <tt class="computeroutput">start_tag</tt> does not parse <tt class="computeroutput">end_tag</tt>s too, we add: <tt class="computeroutput">!char_('/')</tt>. This
+ <code class="computeroutput">start_tag</code> is similar to
+ the <code class="computeroutput">text</code> rule apart from
+ the added <code class="computeroutput">'<'</code> and <code class="computeroutput">'>'</code>. But wait, to make sure that the <code class="computeroutput">start_tag</code> does not parse <code class="computeroutput">end_tag</code>s too, we add: <code class="computeroutput">!char_('/')</code>. This
 is a "Not Predicate":
 
<pre class="programlisting">!p
</pre>

- It will try the parser, <tt class="computeroutput">p</tt>.
+ It will try the parser, <code class="computeroutput">p</code>.
 If it is successful, fail, otherwise, pass. In other words, it negates
- the result of <tt class="computeroutput">p</tt>. Like the
- <tt class="computeroutput">eps</tt>, it does not consume
+ the result of <code class="computeroutput">p</code>. Like the
+ <code class="computeroutput">eps</code>, it does not consume
 any input though. It will always rewind the iterator position to where
 it was upon entry. So, the expression:
 
<pre class="programlisting">!char_('/')
</pre>

- basically says: we should not have a <tt class="computeroutput">'/'</tt>
+ basically says: we should not have a <code class="computeroutput">'/'</code>
 at this point.
 
-<a name="spirit.qi.tutorials.mini_xml___asts_.inherited_attribute"></a><h5>
-<a name="id433560"></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="id2625877"></a>
+ <a class="link" href="mini_xml___asts_.html#spirit.qi.tutorials.mini_xml___asts_.inherited_attribute">Inherited
 Attribute</a>
- </h5>
+ </h6>

- The <tt class="computeroutput">end_tag</tt>:
+ The <code class="computeroutput">end_tag</code>:
 
<pre class="programlisting">rule<Iterator, void(std::string), space_type> end_tag;
</pre>

- Ohh! Now we see an inherited attribute there: <tt class="computeroutput">std::string</tt>.
- The <tt class="computeroutput">end_tag</tt> does not have
+ Ohh! Now we see an inherited attribute there: <code class="computeroutput">std::string</code>.
+ The <code class="computeroutput">end_tag</code> does not have
 a synthesized attribute. Let's see its definition:
 
<pre class="programlisting">end_tag =
@@ -228,28 +223,28 @@
;
</pre>

- <tt class="computeroutput">_r1</tt> is yet another Phoenix placeholder for
- the 1st inherited attribute (we have only one, use <tt class="computeroutput">_r2</tt>,
- <tt class="computeroutput">_r3</tt>, etc. if you have more).
- 
-<a name="spirit.qi.tutorials.mini_xml___asts_.a_lazy_lit"></a><h5>
-<a name="id433840"></a>
- <a href="mini_xml___asts_.html#spirit.qi.tutorials.mini_xml___asts_.a_lazy_lit">A Lazy
+ <code class="computeroutput">_r1</code> is yet another Phoenix placeholder for
+ the 1st inherited attribute (we have only one, use <code class="computeroutput">_r2</code>,
+ <code class="computeroutput">_r3</code>, etc. if you have more).
+ 
+<a name="spirit.qi.tutorials.mini_xml___asts_.a_lazy_lit"></a><h6>
+<a name="id2626132"></a>
+ <a class="link" href="mini_xml___asts_.html#spirit.qi.tutorials.mini_xml___asts_.a_lazy_lit">A Lazy
 Lit</a>
- </h5>
+ </h6>

- Check out how we used <tt class="computeroutput">lit</tt>
+ Check out how we used <code class="computeroutput">lit</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">std::string</tt>
+ inherited attribute, which is specified as <code class="computeroutput">std::string</code>
 in our rule declaration.
 

- Finally, our <tt class="computeroutput">xml</tt> rule:
+ Finally, our <code class="computeroutput">xml</code> rule:
 
<pre class="programlisting">rule<Iterator, mini_xml(), space_type> xml;
</pre>

- <tt class="computeroutput">mini_xml</tt> is our attribute
+ <code class="computeroutput">mini_xml</code> is our attribute
 here. We'll see later what it is. Let's see its definition:
 
<pre class="programlisting">xml =
@@ -260,37 +255,37 @@
</pre>

 Those who know Fusion
- now will notice <tt class="computeroutput">at_c<0></tt> and
- <tt class="computeroutput">at_c<1></tt>. This
- gives us a hint that <tt class="computeroutput">mini_xml</tt>
- is a sort of a tuple - a fusion sequence. <tt class="computeroutput">at_c<N></tt> here is a lazy version of the tuple
+ now will notice <code class="computeroutput">at_c<0></code> and
+ <code class="computeroutput">at_c<1></code>. This
+ gives us a hint that <code class="computeroutput">mini_xml</code>
+ is a sort of a tuple - a fusion sequence. <code class="computeroutput">at_c<N></code> here is a lazy version of the tuple
 accessors, provided by Phoenix.
 
-<a name="spirit.qi.tutorials.mini_xml___asts_.how_it_all_works"></a><h5>
-<a name="id434319"></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="id2626567"></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>

 So, what's happening?
 
<div class="orderedlist"><ol type="1">
<li>
- Upon parsing <tt class="computeroutput">start_tag</tt>,
- the parsed start-tag string is placed in <tt class="computeroutput">at_c<0>(_val)</tt>.
+ Upon parsing <code class="computeroutput">start_tag</code>,
+ the parsed start-tag string is placed in <code class="computeroutput">at_c<0>(_val)</code>.
 </li>
<li>
- Then we parse zero or more <tt class="computeroutput">node</tt>s.
- At each step, we <tt class="computeroutput">push_back</tt>
- the result into <tt class="computeroutput">at_c<1>(_val)</tt>.
+ Then we parse zero or more <code class="computeroutput">node</code>s.
+ At each step, we <code class="computeroutput">push_back</code>
+ the result into <code class="computeroutput">at_c<1>(_val)</code>.
 </li>
<li>
- Finally, we parse the <tt class="computeroutput">end_tag</tt>
- giving it an inherited attribute: <tt class="computeroutput">at_c<0>(_val)</tt>.
- This is the string we obtained from the <tt class="computeroutput">start_tag</tt>.
- Investigate <tt class="computeroutput">end_tag</tt> above.
+ Finally, we parse the <code class="computeroutput">end_tag</code>
+ giving it an inherited attribute: <code class="computeroutput">at_c<0>(_val)</code>.
+ This is the string we obtained from the <code class="computeroutput">start_tag</code>.
+ Investigate <code class="computeroutput">end_tag</code> above.
 It will fail to parse if it gets something different from what we got
- from the <tt class="computeroutput">start_tag</tt>. This
+ from the <code class="computeroutput">start_tag</code>. This
 ensures that our tags are balanced.
 </li>
</ol></div>
@@ -309,15 +304,15 @@
;
</pre>

- passing in <tt class="computeroutput">at_c<0>(_val)</tt>, the string from start tag. This is referred
- to in the <tt class="computeroutput">end_tag</tt> body
- as <tt class="computeroutput">_r1</tt>.
- 
-<a name="spirit.qi.tutorials.mini_xml___asts_.the_structures"></a><h5>
-<a name="id434763"></a>
- <a href="mini_xml___asts_.html#spirit.qi.tutorials.mini_xml___asts_.the_structures">The
+ passing in <code class="computeroutput">at_c<0>(_val)</code>, the string from start tag. This is referred
+ to in the <code class="computeroutput">end_tag</code> body
+ as <code class="computeroutput">_r1</code>.
+ 
+<a name="spirit.qi.tutorials.mini_xml___asts_.the_structures"></a><h6>
+<a name="id2626972"></a>
+ <a class="link" href="mini_xml___asts_.html#spirit.qi.tutorials.mini_xml___asts_.the_structures">The
 Structures</a>
- </h5>
+ </h6>

 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 @@
 

 
-<a name="spirit.qi.tutorials.mini_xml___asts_.of_alternates_and_variants"></a><h5>
-<a name="id435031"></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="id2627215"></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>

- So that's how a <tt class="computeroutput">mini_xml_node</tt>
- looks like. We had a hint that it is either a <tt class="computeroutput">string</tt>
- or a <tt class="computeroutput">mini_xml</tt>. For this,
- we use boost.variant<>.
- <tt class="computeroutput">boost::recursive_wrapper</tt> wraps <tt class="computeroutput">mini_xml</tt>, making it a recursive data
+ So that's how a <code class="computeroutput">mini_xml_node</code>
+ looks like. We had a hint that it is either a <code class="computeroutput">string</code>
+ or a <code class="computeroutput">mini_xml</code>. For this,
+ we use boost.variant<>.
+ <code class="computeroutput">boost::recursive_wrapper</code> wraps <code class="computeroutput">mini_xml</code>, making it a recursive data
 structure.
 

@@ -370,16 +365,16 @@
<pre class="programlisting">boost::variant<A, B>
</pre>

- where <tt class="computeroutput">A</tt> is the attribute
- of <tt class="computeroutput">a</tt> and <tt class="computeroutput">B</tt> is the attribute of <tt class="computeroutput">b</tt>.
+ where <code class="computeroutput">A</code> is the attribute
+ of <code class="computeroutput">a</code> and <code class="computeroutput">B</code> is the attribute of <code class="computeroutput">b</code>.
 
-<a name="spirit.qi.tutorials.mini_xml___asts_.adapting_structs_again"></a><h5>
-<a name="id435297"></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="id2627457"></a>
+ <a class="link" href="mini_xml___asts_.html#spirit.qi.tutorials.mini_xml___asts_.adapting_structs_again">Adapting
 structs again</a>
- </h5>
+ </h6>

- <tt class="computeroutput">mini_xml</tt> is no brainier.
+ <code class="computeroutput">mini_xml</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 @@
 

 
-<a name="spirit.qi.tutorials.mini_xml___asts_.one_more_take"></a><h5>
-<a name="id435495"></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="id2627637"></a>
+ <a class="link" href="mini_xml___asts_.html#spirit.qi.tutorials.mini_xml___asts_.one_more_take">One
 More Take</a>
- </h5>
+ </h6>

 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">xml</tt> rule:
+ in the <code class="computeroutput">xml</code> rule:
 
-<a name="spirit.qi.tutorials.mini_xml___asts_.local_variables"></a><h5>
-<a name="id436739"></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="id2628761"></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">rule<Iterator, mini_xml(), locals<std::string>, space_type> xml;
</pre>

- Wow, we have four template parameters now. What's that <tt class="computeroutput">locals</tt>
- guy doing there? Well, it declares that the rule <tt class="computeroutput">xml</tt>
- will have one local variable: a <tt class="computeroutput">string</tt>.
+ Wow, we have four template parameters now. What's that <code class="computeroutput">locals</code>
+ guy doing there? Well, it declares that the rule <code class="computeroutput">xml</code>
+ will have one local variable: a <code class="computeroutput">string</code>.
 Let's see how this is used in action:
 
<pre class="programlisting">xml %=
@@ -489,23 +484,23 @@
</pre>
<div class="orderedlist"><ol type="1">
<li>
- Upon parsing <tt class="computeroutput">start_tag</tt>,
+ Upon parsing <code class="computeroutput">start_tag</code>,
 the parsed start-tag string is placed in the local variable specified
 by (yet another) Phoenix
- placeholder: <tt class="computeroutput">_a</tt>. We have
- only one local variable. If we had more, these are designated by <tt class="computeroutput">_b</tt>..<tt class="computeroutput">_z</tt>.
+ placeholder: <code class="computeroutput">_a</code>. We have
+ only one local variable. If we had more, these are designated by <code class="computeroutput">_b</code>..<code class="computeroutput">_z</code>.
 </li>
<li>
- Then we parse zero or more <tt class="computeroutput">node</tt>s.
+ Then we parse zero or more <code class="computeroutput">node</code>s.
 </li>
<li>
- Finally, we parse the <tt class="computeroutput">end_tag</tt>
- giving it an inherited attribute: <tt class="computeroutput">_a</tt>,
+ Finally, we parse the <code class="computeroutput">end_tag</code>
+ giving it an inherited attribute: <code class="computeroutput">_a</code>,
 our local variable.
 </li>
</ol></div>

- There are no actions involved in stuffing data into our <tt class="computeroutput">xml</tt>
+ There are no actions involved in stuffing data into our <code class="computeroutput">xml</code>
 attribute. It's all taken cared of thatnks to the auto-rule.
 
</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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<link rel="home" href="../../../index.html" title="Spirit 2.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" 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">
@@ -24,14 +23,10 @@
<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="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>

 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 @@

 What's new?
 
-<a name="spirit.qi.tutorials.mini_xml___error_handling.readable_names"></a><h5>
-<a name="id437192"></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="id2629173"></a>
+ <a class="link" href="mini_xml___error_handling.html#spirit.qi.tutorials.mini_xml___error_handling.readable_names">Readable
 Names</a>
- </h5>
+ </h6>

 First, when we call the base class, we give the grammar a name:
 
@@ -67,13 +62,13 @@
start_tag.name("start_tag");
end_tag.name("end_tag");
</pre>
-<a name="spirit.qi.tutorials.mini_xml___error_handling.on_error"></a><h5>
-<a name="id437443"></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="id2629401"></a>
+ <a class="link" href="mini_xml___error_handling.html#spirit.qi.tutorials.mini_xml___error_handling.on_error">On
 Error</a>
- </h5>
+ </h6>

- <tt class="computeroutput">on_error</tt> declares our error
+ <code class="computeroutput">on_error</code> declares our error
 handler:
 
<pre class="programlisting">on_error<Action>(rule, handler)
@@ -95,8 +90,8 @@
);
</pre>

- we choose to <tt class="computeroutput">fail</tt> in our
- example for the <tt class="computeroutput">Action</tt>:
+ we choose to <code class="computeroutput">fail</code> in our
+ example for the <code class="computeroutput">Action</code>:
 Quit and fail. Return a no_match (false). It can be one of:
 
<div class="informaltable"><table class="table">
@@ -105,55 +100,75 @@
<col>
</colgroup>
<thead><tr>
-<th>
- <tt class="computeroutput">Action</tt>
- </th>
-<th>
+<th>
+ 
+ <code class="computeroutput">Action</code>
+ 
+ </th>
+<th>
+ 
 Description
- </th>
+ 
+ </th>
</tr></thead>
<tbody>
<tr>
-<td>
+<td>
+ 
 fail
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 Quit and fail. Return a no_match.
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
+<td>
+ 
 retry
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 Attempt error recovery, possibly moving the iterator position.
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
+<td>
+ 
 accept
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 Force success, moving the iterator position appropriately.
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
+<td>
+ 
 rethrow
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 Rethrows the error.
- </td>
+ 
+ </td>
</tr>
</tbody>
</table></div>

- <tt class="computeroutput">rule</tt> is the rule we attach
- the handler to. In our case, we are attaching to the <tt class="computeroutput">xml</tt>
+ <code class="computeroutput">rule</code> is the rule we attach
+ the handler to. In our case, we are attaching to the <code class="computeroutput">xml</code>
 rule.
 

- <tt class="computeroutput">handler</tt> is the actual error
+ <code class="computeroutput">handler</code> is the actual error
 handling function. It expects 4 arguments:
 
<div class="informaltable"><table class="table">
@@ -162,57 +177,77 @@
<col>
</colgroup>
<thead><tr>
-<th>
+<th>
+ 
 Arg
- </th>
-<th>
+ 
+ </th>
+<th>
+ 
 Description
- </th>
+ 
+ </th>
</tr></thead>
<tbody>
<tr>
-<td>
+<td>
+ 
 first
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 The position of the iterator when the rule with the handler was
 entered.
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
+<td>
+ 
 last
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 The end of input.
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
+<td>
+ 
 error-pos
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 The actual position of the iterator where the error occurred.
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
+<td>
+ 
 what
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 What failed: a string decribing the failure.
- </td>
+ 
+ </td>
</tr>
</tbody>
</table></div>
-<a name="spirit.qi.tutorials.mini_xml___error_handling.expectation_points"></a><h5>
-<a name="id438113"></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="id2630005"></a>
+ <a class="link" href="mini_xml___error_handling.html#spirit.qi.tutorials.mini_xml___error_handling.expectation_points">Expectation
 Points</a>
- </h5>
+ </h6>

 You might not have noticed it, but some of our expressions changed from
- using the <tt class="computeroutput">>></tt> to <tt class="computeroutput">></tt>. Look, for example:
+ using the <code class="computeroutput">>></code> to <code class="computeroutput">></code>. Look, for example:
 
<pre class="programlisting">end_tag =
 "</"
@@ -223,10 +258,10 @@

 What is it? It's the expectation operator. You will
 have some "deterministic points" in the grammar. Those are the
- places where backtracking cannot occur.
- For our example above, when you get a <tt class="computeroutput">"</"</tt>,
+ places where backtracking cannot occur.
+ For our example above, when you get a <code class="computeroutput">"</"</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">'>'</tt> next. Otherwise, there is no point in
+ you got from the start-tag. After that, you definitely must have a <code class="computeroutput">'>'</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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<link rel="home" href="../../../index.html" title="Spirit 2.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" 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>
@@ -26,14 +23,10 @@
<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="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>

 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 @@
 

 This, again, is the same parser as before. This time, instead of summing
- up the numbers, we stuff them in a <tt class="computeroutput">std::vector</tt>.
- <tt class="computeroutput">push_back</tt> is supplied by
+ up the numbers, we stuff them in a <code class="computeroutput">std::vector</code>.
+ <code class="computeroutput">push_back</code> is supplied by
 <a href="../../../../../phoenix/doc/html/index.html" target="_top">Phoenix</a>. The expression:
 
<pre class="programlisting">push_back(ref(v), _1)
</pre>

- appends the parsed number. Like before, <tt class="computeroutput">_1</tt>
+ appends the parsed number. Like before, <code class="computeroutput">_1</code>
 is a Phoenix placeholder
- for the parsed result attribute. Also, like before, <tt class="computeroutput">ref(v)</tt>
+ for the parsed result attribute. Also, like before, <code class="computeroutput">ref(v)</code>
 tells Phoenix that
- <tt class="computeroutput">v</tt>, the <tt class="computeroutput">std::vector</tt>,
+ <code class="computeroutput">v</code>, the <code class="computeroutput">std::vector</code>,
 is a mutable reference.
 
</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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<link rel="home" href="../../../index.html" title="Spirit 2.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" 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">
@@ -25,17 +23,13 @@
<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="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>

- You've seen that the <tt class="computeroutput">double_</tt>
- parser has a <tt class="computeroutput">double</tt> attribute.
+ You've seen that the <code class="computeroutput">double_</code>
+ parser has a <code class="computeroutput">double</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">p % d
</pre>

- is a <tt class="computeroutput">std::vector</tt> of the attribute of <tt class="computeroutput">p</tt>. So, for our parser:
+ is a <code class="computeroutput">std::vector</code> of the attribute of <code class="computeroutput">p</code>. So, for our parser:
 
<pre class="programlisting">double_ % ','
</pre>
@@ -53,9 +47,9 @@
<pre class="programlisting">std::vector<double>
</pre>

- So, what does this give us? Well, we can simply pass in a <tt class="computeroutput">std::vector<double></tt>
+ So, what does this give us? Well, we can simply pass in a <code class="computeroutput">std::vector<double></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">phrase_parse</tt> with an additional argument:
+ vector. For that to happen, we'll use a variation of the <code class="computeroutput">phrase_parse</code> with an additional argument:
 the parser's attribute:
 
<div class="orderedlist"><ol type="1">
@@ -115,7 +109,7 @@
 The full cpp file for this example can be found here: ../../example/qi/num_list4.cpp
 

- Hey, no more actions!!! Now we're entering
+ Hey, no more actions!!! Now we're entering
 the realm of attribute grammars. Cool eh?
 
</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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<link rel="home" href="../../../index.html" title="Spirit 2.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" 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>
@@ -26,14 +23,10 @@
<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="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>

 So far, we've been using the syntax:
 
@@ -47,7 +40,7 @@
<pre class="programlisting">double_ % ','
</pre>

- read as: a list of doubles separated by <tt class="computeroutput">','</tt>.
+ read as: a list of doubles separated by <code class="computeroutput">','</code>.
 

 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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<link rel="home" href="../../../index.html" title="Spirit 2.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" 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">
@@ -23,17 +23,14 @@
<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="id415562"></a>
- <a href="quick_start.html#spirit.qi.tutorials.quick_start.why_would_you_want_to_use_spirit_qi_">Why
+<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="id2609711"></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>

 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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<link rel="home" href="../../../index.html" title="Spirit 2.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" 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>
@@ -25,12 +23,9 @@
<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="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>

 This example demonstrates:
 
@@ -45,14 +40,14 @@
 grammar
 </li>
</ul></div>
-<a name="spirit.qi.tutorials.roman_numerals.symbol_table"></a><h5>
-<a name="id423543"></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="id2616774"></a>
+ <a class="link" href="roman_numerals.html#spirit.qi.tutorials.roman_numerals.symbol_table">Symbol
 Table</a>
- </h5>
+ </h6>

 The symbol table holds a dictionary of symbols where each symbol is a sequence
- of characters (a <tt class="computeroutput">char</tt>, <tt class="computeroutput">wchar_t</tt>, <tt class="computeroutput">int</tt>,
+ of characters (a <code class="computeroutput">char</code>, <code class="computeroutput">wchar_t</code>, <code class="computeroutput">int</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 @@

 

- Now we can use <tt class="computeroutput">hundreds</tt>,
- <tt class="computeroutput">tens</tt> and <tt class="computeroutput">ones</tt> anywhere in our parser expressions.
+ Now we can use <code class="computeroutput">hundreds</code>,
+ <code class="computeroutput">tens</code> and <code class="computeroutput">ones</code> anywhere in our parser expressions.
 They are all parsers.
 
-<a name="spirit.qi.tutorials.roman_numerals.rules"></a><h5>
-<a name="id424857"></a>
- Rules
- </h5>
+<a name="spirit.qi.tutorials.roman_numerals.rules"></a><h6>
+<a name="id2617970"></a>
+ <a class="link" href="roman_numerals.html#spirit.qi.tutorials.roman_numerals.rules">Rules</a>
+ </h6>

 Up until now, we've been inlining our parser expressions, passing them
- directly to the <tt class="computeroutput">phrase_parse</tt>
+ directly to the <code class="computeroutput">phrase_parse</code>
 function. The expression evaluates into a temporary, unnamed parser which
- is passed into the <tt class="computeroutput">phrase_parse</tt>
+ is passed into the <code class="computeroutput">phrase_parse</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>

 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">phrase_parse</tt>.
- It can only be used with the <tt class="computeroutput">parse</tt>
+ working on. This rule cannot be used with <code class="computeroutput">phrase_parse</code>.
+ It can only be used with the <code class="computeroutput">parse</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">rule<std::string::iterator, space_type> r;
</pre>

- This type of rule can be used for both <tt class="computeroutput">phrase_parse</tt>
- and <tt class="computeroutput">parse</tt>.
+ This type of rule can be used for both <code class="computeroutput">phrase_parse</code>
+ and <code class="computeroutput">parse</code>.
 

 For our next example, there's one more rule form you should know about:
@@ -231,14 +226,14 @@
<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">
+<tr><td align="left" valign="top">
 All rule template arguments after Iterator can be supplied in any order.
 </td></tr>
</table></div>

 The Signature specifies the attributes of the rule. You've seen that our
- parsers can have an attribute. Recall that the <tt class="computeroutput">double_</tt>
- parser has an attribute of <tt class="computeroutput">double</tt>.
+ parsers can have an attribute. Recall that the <code class="computeroutput">double_</code>
+ parser has an attribute of <code class="computeroutput">double</code>.
 To be precise, these are synthesized attributes. The
 parser "synthesizes" the attribute value. Think of them as function
 return values.
@@ -257,17 +252,17 @@
 
<pre class="programlisting">r = double_ >> *(',' >> double_);
</pre>
-<a name="spirit.qi.tutorials.roman_numerals.grammars"></a><h5>
-<a name="id425438"></a>
- Grammars
- </h5>
+<a name="spirit.qi.tutorials.roman_numerals.grammars"></a><h6>
+<a name="id2618502"></a>
+ <a class="link" href="roman_numerals.html#spirit.qi.tutorials.roman_numerals.grammars">Grammars</a>
+ </h6>

 A grammar encapsulates one or more rules. It has the same template parameters
 as the rule. You declare a grammar by:
 
<div class="orderedlist"><ol type="1">
<li>
- deriving a struct (or class) from the <tt class="computeroutput">grammar</tt>
+ deriving a struct (or class) from the <code class="computeroutput">grammar</code>
 class template
 </li>
<li>
@@ -322,8 +317,8 @@
 
<div class="itemizedlist"><ul type="disc">
<li>
- The grammar and start rule signature is <tt class="computeroutput">unsigned()</tt>. It has a synthesized attribute (return
- value) of type <tt class="computeroutput">unsigned</tt>
+ The grammar and start rule signature is <code class="computeroutput">unsigned()</code>. It has a synthesized attribute (return
+ value) of type <code class="computeroutput">unsigned</code>
 with no inherited attributes (arguments).
 </li>
<li>
@@ -331,9 +326,9 @@
 numerals.
 </li>
<li>
-<tt class="computeroutput">roman::base_type</tt> is a typedef for <tt class="computeroutput">grammar<Iterator,
- unsigned()></tt>.
- If <tt class="computeroutput">roman</tt> was not a template,
+<code class="computeroutput">roman::base_type</code> is a typedef for <code class="computeroutput">grammar<Iterator,
+ unsigned()></code>.
+ If <code class="computeroutput">roman</code> was not a template,
 you can simply write: base_type(start)
 </li>
<li>
@@ -341,31 +336,31 @@
 for different iterator types.
 </li>
<li>
-<tt class="computeroutput">_val</tt> is another Phoenix placeholder representing
+<code class="computeroutput">_val</code> is another Phoenix placeholder representing
 the rule's synthesized attribute.
 </li>
<li>
-<tt class="computeroutput">eps</tt> is a special spirit
+<code class="computeroutput">eps</code> is a special spirit
 parser that consumes no input but is always successful. We use it to
- initialize <tt class="computeroutput">_val</tt>, the
+ initialize <code class="computeroutput">_val</code>, the
 rule's synthesized attribute, to zero before anything else. The actual
- parser starts at <tt class="computeroutput">+char_('M')</tt>,
- parsing roman thousands. Using <tt class="computeroutput">eps</tt>
+ parser starts at <code class="computeroutput">+char_('M')</code>,
+ parsing roman thousands. Using <code class="computeroutput">eps</code>
 this way is good for doing pre and post initializations.
 </li>
<li>
- The expression <tt class="computeroutput">a ||
- b</tt> reads: match a or b and in
- sequence. That is, if both <tt class="computeroutput">a</tt>
- and <tt class="computeroutput">b</tt> match, it must
- be in sequence; this is equivalent to <tt class="computeroutput">a
- >> -b | b</tt>, but more efficient.
+ The expression <code class="computeroutput">a ||
+ b</code> reads: match a or b and in
+ sequence. That is, if both <code class="computeroutput">a</code>
+ and <code class="computeroutput">b</code> match, it must
+ be in sequence; this is equivalent to <code class="computeroutput">a
+ >> -b | b</code>, but more efficient.
 </li>
</ul></div>
-<a name="spirit.qi.tutorials.roman_numerals.let_s_parse_"></a><h5>
-<a name="id426455"></a>
- Let's Parse!
- </h5>
+<a name="spirit.qi.tutorials.roman_numerals.let_s_parse_"></a><h6>
+<a name="id2619426"></a>
+ <a class="link" href="roman_numerals.html#spirit.qi.tutorials.roman_numerals.let_s_parse_">Let's Parse!</a>
+ </h6>

 

@@ -394,12 +389,12 @@

 

- <tt class="computeroutput">roman_parser</tt> is an object
- of type <tt class="computeroutput">roman</tt> -our roman
+ <code class="computeroutput">roman_parser</code> is an object
+ of type <code class="computeroutput">roman</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">unsigned
- result</tt>, which will receive the
+ passing in an attribute, <code class="computeroutput">unsigned
+ result</code>, which will receive the
 parsed value.

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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<link rel="home" href="../../../index.html" title="Spirit 2.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" 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>
@@ -24,12 +23,9 @@
<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="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>

 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">P</tt>,
- and a C++ function <tt class="computeroutput">F</tt>, you
- can make the parser call <tt class="computeroutput">F</tt>
- whenever it matches an input by attaching <tt class="computeroutput">F</tt>:
+ a portion of the input. Say you have a parser <code class="computeroutput">P</code>,
+ and a C++ function <code class="computeroutput">F</code>, you
+ can make the parser call <code class="computeroutput">F</code>
+ whenever it matches an input by attaching <code class="computeroutput">F</code>:
 
<pre class="programlisting">P[F]
</pre>

- The expression above links <tt class="computeroutput">F</tt>
- to the parser, <tt class="computeroutput">P</tt>.
+ The expression above links <code class="computeroutput">F</code>
+ to the parser, <code class="computeroutput">P</code>.
 

 The function/function object signature depends on the type of the parser
- to which it is attached. The parser <tt class="computeroutput">double_</tt>
- passes the parsed number. Thus, if we were to attach a function <tt class="computeroutput">F</tt> to <tt class="computeroutput">double_</tt>,
- we need <tt class="computeroutput">F</tt> to be declared
+ to which it is attached. The parser <code class="computeroutput">double_</code>
+ passes the parsed number. Thus, if we were to attach a function <code class="computeroutput">F</code> to <code class="computeroutput">double_</code>,
+ we need <code class="computeroutput">F</code> to be declared
 as:
 
<pre class="programlisting">void F(double n);
@@ -132,11 +128,11 @@

 

- Take note that with function objects, we need to have an <tt class="computeroutput">operator()</tt>
+ Take note that with function objects, we need to have an <code class="computeroutput">operator()</code>
 with 3 arguments. Since we don't care about the other two, we can use
- <tt class="computeroutput">unused_type</tt> for these.
- We'll see more of <tt class="computeroutput">unused_type</tt>
- elsewhere. Get used to it. <tt class="computeroutput">unused_type</tt>
+ <code class="computeroutput">unused_type</code> for these.
+ We'll see more of <code class="computeroutput">unused_type</code>
+ elsewhere. Get used to it. <code class="computeroutput">unused_type</code>
 is a Spirit supplied support class.
 

@@ -162,8 +158,8 @@

 

- What's new? Well <tt class="computeroutput">int_</tt> is
- the sibbling of <tt class="computeroutput">double_</tt>.
+ What's new? Well <code class="computeroutput">int_</code> is
+ the sibbling of <code class="computeroutput">double_</code>.
 I'm sure you can guess what this parser does.
 

@@ -236,10 +232,10 @@

 The examples above can be found here: ../../example/qi/actions.cpp
 
-<a name="spirit.qi.tutorials.semantic_actions.phoenix"></a><h5>
-<a name="id418498"></a>
- Phoenix
- </h5>
+<a name="spirit.qi.tutorials.semantic_actions.phoenix"></a><h6>
+<a name="id2612385"></a>
+ <a class="link" href="semantic_actions.html#spirit.qi.tutorials.semantic_actions.phoenix">Phoenix</a>
+ </h6>

 <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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<link rel="home" href="../../../index.html" title="Spirit 2.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" 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>
@@ -26,14 +23,10 @@
<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="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>

 Here's a parser that sums a comma-separated list of numbers.
 
@@ -83,55 +76,79 @@
<col>
</colgroup>
<thead><tr>
-<th>
+<th>
+ 
 Namespace
- </th>
-<th>
+ 
+ </th>
+<th>
+ 
 Description
- </th>
+ 
+ </th>
</tr></thead>
<tbody>
<tr>
-<td>
+<td>
+ 
 boost::phoenix
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 All of phoenix
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
+<td>
+ 
 boost::spirit
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 All of spirit
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
+<td>
+ 
 boost::spirit::qi
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 All of spirit.qi
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
+<td>
+ 
 boost::spirit::ascii
- </td>
-<td>
- ASCII version of <tt class="computeroutput">char_</tt>
+ 
+ </td>
+<td>
+ 
+ ASCII version of <code class="computeroutput">char_</code>
 and all char related parsers. Other encodings are also provided
 (e.g. also an ISO8859.1)
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
+<td>
+ 
 boost::spirit::arg_names
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 Special phoenix placeholders for spirit
- </td>
+ 
+ </td>
</tr>
</tbody>
</table></div>
@@ -140,7 +157,7 @@
<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">
 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.
 

- The first <tt class="computeroutput">double_</tt> parser
+ The first <code class="computeroutput">double_</code> parser
 attaches this action:
 
<pre class="programlisting">ref(n) = _1
</pre>

- This assigns the parsed result (actually, the attribute of <tt class="computeroutput">double_</tt>) to <tt class="computeroutput">n</tt>.
- <tt class="computeroutput">ref(n)</tt> tells
- Phoenix that <tt class="computeroutput">n</tt> is a mutable reference. <tt class="computeroutput">_1</tt> is a Phoenix
+ This assigns the parsed result (actually, the attribute of <code class="computeroutput">double_</code>) to <code class="computeroutput">n</code>.
+ <code class="computeroutput">ref(n)</code> tells
+ Phoenix that <code class="computeroutput">n</code> is a mutable reference. <code class="computeroutput">_1</code> is a Phoenix
 placeholder for the parsed result attribute.
 

- The second <tt class="computeroutput">double_</tt> parser
+ The second <code class="computeroutput">double_</code> parser
 attaches this action:
 
<pre class="programlisting">ref(n) += _1
</pre>

- So, subsequent numbers add into <tt class="computeroutput">n</tt>.
+ So, subsequent numbers add into <code class="computeroutput">n</code>.
 

 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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<link rel="home" href="../../../index.html" title="Spirit 2.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" 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">
@@ -23,21 +23,18 @@
<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="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>

 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.
 
-<a name="spirit.qi.tutorials.warming_up.trivial_example__1_parsing_a_number"></a><h5>
-<a name="id415635"></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="id2609802"></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>

 Create a parser that will parse a floating-point number.
 
@@ -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!
 
-<a name="spirit.qi.tutorials.warming_up.trivial_example__2_parsing_two_numbers"></a><h5>
-<a name="id415681"></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="id2609845"></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>

 Create a parser that will accept a line consisting of two floating-point
 numbers.
@@ -60,8 +57,8 @@
<pre class="programlisting">double_ >> double_
</pre>

- Here you see the familiar floating-point numeric parser <tt class="computeroutput">double_</tt>
- used twice, once for each number. What's that <tt class="computeroutput">>></tt>
+ Here you see the familiar floating-point numeric parser <code class="computeroutput">double_</code>
+ used twice, once for each number. What's that <code class="computeroutput">>></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
@@ -74,18 +71,18 @@
<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">
 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.
 </td></tr>
</table></div>
-<a name="spirit.qi.tutorials.warming_up.trivial_example__3_parsing_one_or_more_numbers"></a><h5>
-<a name="id415769"></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="id2609934"></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>

 Create a parser that will accept zero or more floating-point numbers.
 
@@ -93,7 +90,7 @@
</pre>

 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">*</tt> operator overloaded like this. Actually,
+ look a bit odd for a C++ programmer not used to seeing the <code class="computeroutput">*</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.
 
-<a name="spirit.qi.tutorials.warming_up.trivial_example__4_parsing_a_comma_delimited_list_of_numbers"></a><h5>
-<a name="id415845"></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="id2610005"></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>

 This example will create a parser that accepts a comma-delimited list of
 numbers.
@@ -117,8 +114,8 @@
<pre class="programlisting">double_ >> *(char_(',') >> double_)
</pre>

- Notice <tt class="computeroutput">char_(',')</tt>. It is
- a literal character parser that can recognize the comma <tt class="computeroutput">','</tt>.
+ Notice <code class="computeroutput">char_(',')</code>. It is
+ a literal character parser that can recognize the comma <code class="computeroutput">','</code>.
 In this case, the Kleene Star is modifying a more complex parser, namely,
 the one generated by the expression:
 
@@ -128,14 +125,14 @@
 Note that this is a case where the parentheses are necessary. The Kleene
 star encloses the complete expression above.
 
-<a name="spirit.qi.tutorials.warming_up.let_s_parse_"></a><h5>
-<a name="id416022"></a>
- Let's Parse!
- </h5>
+<a name="spirit.qi.tutorials.warming_up.let_s_parse_"></a><h6>
+<a name="id2610167"></a>
+ <a class="link" href="warming_up.html#spirit.qi.tutorials.warming_up.let_s_parse_">Let's Parse!</a>
+ </h6>

 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">phrase_parse</tt>
+ we will use the <code class="computeroutput">phrase_parse</code>
 function. One overload of this function accepts four arguments:
 
<div class="orderedlist"><ol type="1">
@@ -154,12 +151,12 @@
</ol></div>

 In our example, we wish to skip spaces and tabs. Another parser named
- <tt class="computeroutput">space</tt> is included in Spirit's
+ <code class="computeroutput">space</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">space</tt>
+ recognizes whitespace. We will use <code class="computeroutput">space</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">double_</tt>
- and <tt class="computeroutput">char_</tt>.
+ characters in between parser elements such as the <code class="computeroutput">double_</code>
+ and <code class="computeroutput">char_</code>.
 

 Ok, so now let's parse!
@@ -177,10 +174,10 @@
 using ascii::space;

 bool r = phrase_parse(
- first, <a name="spirit0co" href="warming_up.html#spirit0"><img src="../../../../../../../doc/src/images/callouts/1.png" alt="1" border="0"></a>
- last, <a name="spirit1co" href="warming_up.html#spirit1"><img src="../../../../../../../doc/src/images/callouts/2.png" alt="2" border="0"></a>
- double_ >> *(',' >> double_), <a name="spirit2co" href="warming_up.html#spirit2"><img src="../../../../../../../doc/src/images/callouts/3.png" alt="3" border="0"></a>
- space <a name="spirit3co" href="warming_up.html#spirit3"><img src="../../../../../../../doc/src/images/callouts/4.png" alt="4" border="0"></a>
+ first, <a class="co" name="spirit0co" href="warming_up.html#spirit0"><img src="../../../../../../../doc/src/images/callouts/1.png" alt="1" border="0"></a>
+ last, <a class="co" name="spirit1co" href="warming_up.html#spirit1"><img src="../../../../../../../doc/src/images/callouts/2.png" alt="2" border="0"></a>
+ double_ >> *(',' >> double_), <a class="co" name="spirit2co" href="warming_up.html#spirit2"><img src="../../../../../../../doc/src/images/callouts/3.png" alt="3" border="0"></a>
+ space <a class="co" name="spirit3co" href="warming_up.html#spirit3"><img src="../../../../../../../doc/src/images/callouts/4.png" alt="4" border="0"></a>
 );
 if (first != last) // fail if we did not get a full match
 return false;
@@ -195,23 +192,19 @@
 
<div class="calloutlist"><table border="0" summary="Callout list">
<tr>
-<td width="5%" valign="top" align="left">
-<a name="spirit0"></a> </td>
+<td width="5%" valign="top" align="left"><a name="spirit0"></a> </td>
<td valign="top" align="left"> start iterator </td>
</tr>
<tr>
-<td width="5%" valign="top" align="left">
-<a name="spirit1"></a> </td>
+<td width="5%" valign="top" align="left"><a name="spirit1"></a> </td>
<td valign="top" align="left"> end iterator </td>
</tr>
<tr>
-<td width="5%" valign="top" align="left">
-<a name="spirit2"></a> </td>
+<td width="5%" valign="top" align="left"><a name="spirit2"></a> </td>
<td valign="top" align="left"> the parser </td>
</tr>
<tr>
-<td width="5%" valign="top" align="left">
-<a name="spirit3"></a> </td>
+<td width="5%" valign="top" align="left"><a name="spirit3"></a> </td>
<td valign="top" align="left"> the skip-parser </td>
</tr>
</table></div>
@@ -220,8 +213,8 @@

 

- The parse function returns <tt class="computeroutput">true</tt>
- or <tt class="computeroutput">false</tt> depending on the
+ The parse function returns <code class="computeroutput">true</code>
+ or <code class="computeroutput">false</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
@@ -246,34 +239,34 @@
<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">

- <tt class="computeroutput">char</tt> and <tt class="computeroutput">wchar_t</tt>
+ <code class="computeroutput">char</code> and <code class="computeroutput">wchar_t</code>
 operands
 

- The careful reader may notice that the parser expression has <tt class="computeroutput">','</tt> instead of <tt class="computeroutput">char_(',')</tt>
+ The careful reader may notice that the parser expression has <code class="computeroutput">','</code> instead of <code class="computeroutput">char_(',')</code>
 as the previous examples did. This is ok due to C++ syntax rules of conversion.
- There are <tt class="computeroutput">>></tt> operators
- that are overloaded to accept a <tt class="computeroutput">char</tt>
- or <tt class="computeroutput">wchar_t</tt> argument on its
+ There are <code class="computeroutput">>></code> operators
+ that are overloaded to accept a <code class="computeroutput">char</code>
+ or <code class="computeroutput">wchar_t</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">double_</tt> is the 2nd argument to <tt class="computeroutput">operator>></tt>,
- and so the proper overload of <tt class="computeroutput">>></tt>
- is used, converting <tt class="computeroutput">','</tt> into
+ one of its parameters is a user-defined type. In this case, the <code class="computeroutput">double_</code> is the 2nd argument to <code class="computeroutput">operator>></code>,
+ and so the proper overload of <code class="computeroutput">>></code>
+ is used, converting <code class="computeroutput">','</code> into
 a character literal parser.
 

- The problem with omiting the <tt class="computeroutput">char_</tt>
- should be obvious: <tt class="computeroutput">'a' >>
- 'b'</tt> is not a spirit parser, it is
+ The problem with omiting the <code class="computeroutput">char_</code>
+ should be obvious: <code class="computeroutput">'a' >>
+ 'b'</code> is not a spirit parser, it is
 a numeric expression, right-shifting the ASCII (or another encoding)
- value of <tt class="computeroutput">'a'</tt> by the ASCII value
- of <tt class="computeroutput">'b'</tt>. However, both <tt class="computeroutput">char_('a') >>
- 'b'</tt> and <tt class="computeroutput">'a'
- >> char_('b')</tt>
- are Spirit sequence parsers for the letter <tt class="computeroutput">'a'</tt>
- followed by <tt class="computeroutput">'b'</tt>. You'll get
+ value of <code class="computeroutput">'a'</code> by the ASCII value
+ of <code class="computeroutput">'b'</code>. However, both <code class="computeroutput">char_('a') >>
+ 'b'</code> and <code class="computeroutput">'a'
+ >> char_('b')</code>
+ are Spirit sequence parsers for the letter <code class="computeroutput">'a'</code>
+ followed by <code class="computeroutput">'b'</code>. You'll get
 used to it, sooner or later.
 
</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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<link rel="home" href="../index.html" title="Spirit 2.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" 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>
@@ -22,12 +22,9 @@
<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="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>
- </th>
-<th>
+<th>
+ 
+ 
+ </th>
+<th>
+ 
 Authors
- </th>
-<th>
+ 
+ </th>
+<th>
+ 
 Title, Publisher/link, Date Published
- </th>
+ 
+ </th>
</tr></thead>
<tbody>
<tr>
-<td>
+<td>
+ 
 1.
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 Todd Veldhuizen
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 <a href="http://www.extreme.indiana.edu/%7Etveldhui/papers/Expression-Templates/exprtmpl.html" target="_top">"Expression
 Templates"</a>. C++ Report, June 1995.
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
+<td>
+ 
 2.
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 Peter Naur (ed.)
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 <a href="http://www.masswerk.at/algol60/report.htm" target="_top">"Report
 on the Algorithmic Language ALGOL 60"</a>. CACM, May 1960.
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
+<td>
+ 
 3.
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 ISO/IEC
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 <a href="http://www.cl.cam.ac.uk/%7Emgk25/iso-14977.pdf" target="_top">"ISO-EBNF"</a>,
 ISO/IEC 14977: 1996(E).
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
+<td>
+ 
 4.
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 Richard J.Botting, Ph.D.
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 <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.
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
+<td>
+ 
 5.
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 James Coplien.
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 "Curiously Recurring Template Pattern". C++ Report, Feb.
 1995.
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
+<td>
+ 
 6.
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 Thierry Geraud and Alexandre Duret-Lutz
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 <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.
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
+<td>
+ 
 7.
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 Geoffrey Furnish
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 <a href="http://www.adtmag.com/joop/carticle.aspx?ID=627" target="_top">"Disambiguated
 Glommable Expression Templates Reintroduced"</a> C++ Report,
 May 2000
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
+<td>
+ 
 8.
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 Erich Gamma, Richard Helm, Ralph Jhonson, and John Vlissides
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 Design Patterns, Elements of Reusable Object-Oriented Software. Addison-Wesley,
 1995.
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
+<td>
+ 
 9.
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 Alfred V. Aho, Revi Sethi, Feffrey D. Ulman
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 Compilers, Principles, Techniques and Tools Addison-Wesley, June 1987.
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
+<td>
+ 
 10.
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 Dick Grune and Ceriel Jacobs
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 <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).
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
+<td>
+ 
 11.
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 T. J. Parr, H. G. Dietz, and W. E. Cohen
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 <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.
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
+<td>
+ 
 12.
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 Adrian Johnstone and Elizabeth Scott.
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 <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.
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
+<td>
+ 
 13.
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 Adrian Johnstone
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 <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
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
+<td>
+ 
 14.
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 Damian Conway
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 <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.
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
+<td>
+ 
 15.
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 Joel de Guzman
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 <a href="http://spirit.sourceforge.net/distrib/spirit_1_8_5/libs/spirit/index.html" target="_top">"Spirit
 Version 1.8"</a>, 1998-2003.
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
+<td>
+ 
 16.
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 S. Doaitse Swierstra and Luc Duponcheel
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 <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
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
+<td>
+ 
 17.
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 Bjarne Stroustrup
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 <a href="http://www.research.att.com/%7Ebs/whitespace98.pdf" target="_top">Generalizing
 Overloading for C++2000</a> Overload, Issue 25. April 1, 1998.
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
+<td>
+ 
 18.
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 Dr. John Maddock
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 <a href="http://www.boost.org/libs/regex/index.html" target="_top">Regex++ Documentation</a>
 http://www.boost.org/libs/regex/index.htm
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
+<td>
+ 
 19.
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 Anonymous Edited by Graham Hutton
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 <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.
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
+<td>
+ 
 20.
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 Hewlett-Packard
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 <a href="http://www.sgi.com/tech/stl/" target="_top">Standard Template Library
 Programmer's Guide.</a>, Hewlett-Packard Company, 1994
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
+<td>
+ 
 21.
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 Boost Libraries
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 <a href="http://boost.org/libs/libraries.htm" target="_top">Boost Libraries Documentation</a>.
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
+<td>
+ 
 22.
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 Brian McNamara and Yannis Smaragdakis
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 <a href="http://www.cc.gatech.edu/~yannis/fc++/" target="_top">FC++:Functional
 Programming in C++</a>.
- </td>
+ 
+ </td>
</tr>
<tr>
-<td>
+<td>
+ 
 23.
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 Todd Veldhuizen
- </td>
-<td>
+ 
+ </td>
+<td>
+ 
 <a href="ftp://ftp.cs.indiana.edu/pub/techreports/TR542.pdf" target="_top">Techniques
 for Scientic C++.</a>
- </td>
+ 
+ </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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<link rel="home" href="../index.html" title="Spirit 2.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" 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">
@@ -23,12 +23,9 @@
<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="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>Include</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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<link rel="home" href="../../index.html" title="Spirit 2.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" 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">
@@ -23,12 +23,9 @@
<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="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>

Spirit is a header file only library. There are no libraries to link to.
This section documents the structure of the Spirit headers.

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-06-23 00:30:19 EDT (Tue, 23 Jun 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">
-<link rel="home" href="../index.html" title="Spirit 2.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<link rel="start" 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">
@@ -23,16 +23,13 @@
<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="id353454"></a>
- Spirit Classic
- </h3>
+<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="id2603609"></a>
+ <a class="link" href="what_s_new.html#spirit.what_s_new.spirit_classic">Spirit Classic</a>
+ </h4>

 The Spirit V1.8.x code base has been integrated with Spirit V2. It is now called
 Spirit.Classic. Even if the directory structure has changed
@@ -56,11 +53,11 @@
</pre>

 To avoid namespace conflicts with the new Spirit V2 library we moved Spirit
- Classic into the namespace <tt class="computeroutput">boost::spirit::classic</tt>.
- All references to the former namespace <tt class="computeroutput">boost::spirit</tt>
+ Classic into the namespace <code class="computeroutput">boost::spirit::classic</code>.
+ All references to the former namespace <code class="computeroutput">boost::spirit</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">BOOST_SPIRIT_USE_OLD_NAMESPACE</tt>, which will
- force the Spirit Classic code to be in the namespace <tt class="computeroutput">boost::spirit</tt>
+ above. As an alternative you can define the preprocessor constant <code class="computeroutput">BOOST_SPIRIT_USE_OLD_NAMESPACE</code>, which will
+ force the Spirit Classic code to be in the namespace <code class="computeroutput">boost::spirit</code>
 as before. This is not recommended, though, as it may result in naming clashes.
 

@@ -68,33 +65,33 @@
 deprecated include files are being used. This ensures full backwards compatibility
 for existing applications.
 
-<a name="spirit.what_s_new.spirit_v2_1"></a><h3>
-<a name="id353512"></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="id353536"></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="id2603856"></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="id2603874"></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 Spirit.Qi and Spirit.Karma
 from V2.0 to 2.x</a>
- </h3>
+ </h4>
<div class="itemizedlist"><ul type="disc">
<li>
<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">qi::phrase_parse</tt>, <tt class="computeroutput">qi::phrase_format</tt>
+<code class="computeroutput">qi::phrase_parse</code>, <code class="computeroutput">qi::phrase_format</code>
 now post-skip by default.
 </li>
<li>
-<tt class="computeroutput">karma::generate_delimited</tt> and <tt class="computeroutput">karma::format_delimited</tt>
+<code class="computeroutput">karma::generate_delimited</code> and <code class="computeroutput">karma::format_delimited</code>
 now don't do pre- delimiting by default.
 </li>
<li>
- Changed parameter sequence of <tt class="computeroutput">qi::phrase_parse</tt>,
- <tt class="computeroutput">qi::phrase_match</tt>, <tt class="computeroutput">karma::generate_delimited</tt>,
- and <tt class="computeroutput">match_delimited</tt>. The
+ Changed parameter sequence of <code class="computeroutput">qi::phrase_parse</code>,
+ <code class="computeroutput">qi::phrase_match</code>, <code class="computeroutput">karma::generate_delimited</code>,
+ and <code class="computeroutput">match_delimited</code>. The
 attribute is now always the last parameter.
 </li>
<li>
@@ -105,13 +102,13 @@
 multi attribute API functions
 </li>
<li>
- removed <tt class="computeroutput">grammar_def<></tt>
+ removed <code class="computeroutput">grammar_def<></code>
</li>
<li>
- removed functions <tt class="computeroutput">make_parser()</tt> and <tt class="computeroutput">make_generator()</tt>
+ removed functions <code class="computeroutput">make_parser()</code> and <code class="computeroutput">make_generator()</code>
</li>
<li>
- removed <tt class="computeroutput">qi::none</tt> and <tt class="computeroutput">karma::none</tt>
+ removed <code class="computeroutput">qi::none</code> and <code class="computeroutput">karma::none</code>
</li>
<li>
 sequences and lists now accept a standard container as its attribute
@@ -124,46 +121,46 @@
 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">int_</tt>,
- <tt class="computeroutput">double_</tt>, <tt class="computeroutput">verbatim</tt>,
- etc.) were previously defined in the namespace <tt class="computeroutput">boost::spirit</tt>
- only. Now these are additionally imported into the namespaces <tt class="computeroutput">spirit::qi</tt>, <tt class="computeroutput">spirit::karma</tt>,
- and <tt class="computeroutput">spirit::lex</tt> (if they are supported by the corresponding
+ All placeholders for terminals and directives (such as <code class="computeroutput">int_</code>,
+ <code class="computeroutput">double_</code>, <code class="computeroutput">verbatim</code>,
+ etc.) were previously defined in the namespace <code class="computeroutput">boost::spirit</code>
+ only. Now these are additionally imported into the namespaces <code class="computeroutput">spirit::qi</code>, <code class="computeroutput">spirit::karma</code>,
+ and <code class="computeroutput">spirit::lex</code> (if they are supported by the corresponding
 sub-library.
 </li>
<li>
- The terminal placeholders <tt class="computeroutput">char_</tt>
- and <tt class="computeroutput">string</tt> are not defined
- in the namespace <tt class="computeroutput">boost::spirit</tt> anymore as they have been moved
+ The terminal placeholders <code class="computeroutput">char_</code>
+ and <code class="computeroutput">string</code> are not defined
+ in the namespace <code class="computeroutput">boost::spirit</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">spirit::ascii</tt>,
+ based on the used namespace (as <code class="computeroutput">spirit::ascii</code>,
 etc.)
 </li>
<li>
- The <tt class="computeroutput">uint</tt>, <tt class="computeroutput">ushort</tt>,
- <tt class="computeroutput">ulong</tt>, and <tt class="computeroutput">byte</tt> terminal placeholders have been renamed
- to <tt class="computeroutput">uint_</tt>, <tt class="computeroutput">ushort_</tt>,
- <tt class="computeroutput">ulong_</tt>, and <tt class="computeroutput">byte_</tt>.
+ The <code class="computeroutput">uint</code>, <code class="computeroutput">ushort</code>,
+ <code class="computeroutput">ulong</code>, and <code class="computeroutput">byte</code> terminal placeholders have been renamed
+ to <code class="computeroutput">uint_</code>, <code class="computeroutput">ushort_</code>,
+ <code class="computeroutput">ulong_</code>, and <code class="computeroutput">byte_</code>.
 </li>
<li>
- qi::skip[]<tt class="computeroutput"> now re-enables outer skipper
+ qi::skip[]<code class="computeroutput"> now re-enables outer skipper
 if used
- inside </tt>lexeme[]<tt class="computeroutput"> *
- Added </tt>karma::maxwidth[]<tt class="computeroutput">
+ inside </code>lexeme[]<code class="computeroutput"> *
+ Added </code>karma::maxwidth[]<code class="computeroutput">
 directive *
- </tt>karma::delimit[]<tt class="computeroutput"> now re-enables
+ </code>karma::delimit[]<code class="computeroutput"> now re-enables
 outer delimiter
 if used
- inside </tt>verbatim[]<tt class="computeroutput"> * karma: added and-predicate
- (</tt>operator&()<tt class="computeroutput">)
- and not-predicate (</tt>operator!()`)
+ inside </code>verbatim[]<code class="computeroutput"> * karma: added and-predicate
+ (</code>operator&()<code class="computeroutput">)
+ and not-predicate (</code>operator!()`)
 </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="id410200"></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="id2604626"></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 Spirit.Lex from V2.0 to 2.x</a>
- </h3>
+ </h4>

 Here is a list of changes in Spirit.Lex since version
 2.0. Spirit.Lex 2.x is a complete rewrite of the original
@@ -178,8 +175,8 @@
 lexers.
 </li>
<li>
- The lex::lexer class does not have the function <tt class="computeroutput">def(Self&
- self)</tt>
+ The lex::lexer class does not have the function <code class="computeroutput">def(Self&
+ self)</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">template <typename Lexer>
@@ -195,28 +192,28 @@
</li>
<li>
 The new lexer class now can be directly used, their is no need anymore to
- wrap it using the <tt class="computeroutput">make_lexer()</tt> template as before. Therefor the function
- <tt class="computeroutput">make_lexer()</tt>
+ wrap it using the <code class="computeroutput">make_lexer()</code> template as before. Therefor the function
+ <code class="computeroutput">make_lexer()</code>
 has been removed.
 </li>
<li>
- The <tt class="computeroutput">lex::tokenize_and_parse()</tt>
- and <tt class="computeroutput">lex::tokenize_and_phrase_parse()</tt>
+ The <code class="computeroutput">lex::tokenize_and_parse()</code>
+ and <code class="computeroutput">lex::tokenize_and_phrase_parse()</code>
 functions have been changed to match the parameter sequence as implemented
- by the <tt class="computeroutput">qi::parse()</tt>
- and <tt class="computeroutput">qi::phrase_parse()</tt>
+ by the <code class="computeroutput">qi::parse()</code>
+ and <code class="computeroutput">qi::phrase_parse()</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">SPIRIT_ARGUMENTS_LIMIT</tt>, which
- defaults to <tt class="computeroutput">PHOENIX_LIMIT</tt>).
+ <code class="computeroutput">SPIRIT_ARGUMENTS_LIMIT</code>, which
+ defaults to <code class="computeroutput">PHOENIX_LIMIT</code>).
 </li>
<li>
- The <tt class="computeroutput">lex::lexertl_lexer</tt>, <tt class="computeroutput">lex::lexertl_token_set</tt>,
- and <tt class="computeroutput">lex::lexertl_token</tt> classes has been moved to
- the <tt class="computeroutput">lex::lexertl</tt> namespace and the names have been
- changed to <tt class="computeroutput">lex::lexertl::lexer</tt>, <tt class="computeroutput">lex::lexertl::token_set</tt>,
- <tt class="computeroutput">lex::lexertl::token</tt> (the same applies to the <tt class="computeroutput">lex::lexert_actor_lexer</tt>,
- and the <tt class="computeroutput">static_lexertl_*</tt>
+ The <code class="computeroutput">lex::lexertl_lexer</code>, <code class="computeroutput">lex::lexertl_token_set</code>,
+ and <code class="computeroutput">lex::lexertl_token</code> classes has been moved to
+ the <code class="computeroutput">lex::lexertl</code> namespace and the names have been
+ changed to <code class="computeroutput">lex::lexertl::lexer</code>, <code class="computeroutput">lex::lexertl::token_set</code>,
+ <code class="computeroutput">lex::lexertl::token</code> (the same applies to the <code class="computeroutput">lex::lexert_actor_lexer</code>,
+ and the <code class="computeroutput">static_lexertl_*</code>
 family of types).
 </li>
<li>
@@ -225,21 +222,21 @@
 lexer construction library (Boost review pending).
 </li>
<li>
- The <tt class="computeroutput">lex::lexer<Lexer></tt>
- template constructor now takes an optional parameter specifying the <tt class="computeroutput">match_flags</tt> to be used for table generation.
+ The <code class="computeroutput">lex::lexer<Lexer></code>
+ template constructor now takes an optional parameter specifying the <code class="computeroutput">match_flags</code> to be used for table generation.
 Currently, there are the following flags available:
<pre class="programlisting">match_flags::match_default, // no flags
match_flags::match_not_dot_newline, // the regex '.' doesn't match newlines
match_flags::match_icase // all matching operations are case insensitive
</pre>
- If no parameter is passed to the constructor, <tt class="computeroutput">match_flags::match_default</tt>
- is used, i.e. the <tt class="computeroutput">.</tt> matches
+ If no parameter is passed to the constructor, <code class="computeroutput">match_flags::match_default</code>
+ is used, i.e. the <code class="computeroutput">.</code> matches
 newlines and matching is case sensitive.
 </li>
<li>
- Now the <tt class="computeroutput">char_()</tt>
- and <tt class="computeroutput">string()</tt>
- placeholders can be used for token definitions as a replacement for <tt class="computeroutput">token_def</tt>, although it is still possible
+ Now the <code class="computeroutput">char_()</code>
+ and <code class="computeroutput">string()</code>
+ placeholders can be used for token definitions as a replacement for <code class="computeroutput">token_def</code>, although it is still possible
 to use the latter one.
 </li>
</ul></div>

Modified: trunk/libs/spirit/doc/preface.qbk
==============================================================================
--- trunk/libs/spirit/doc/preface.qbk (original)
+++ trunk/libs/spirit/doc/preface.qbk 2009-06-23 00:30:19 EDT (Tue, 23 Jun 2009)
@@ -9,25 +9,26 @@
[section Preface]

[:['["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.]] [*--Bjarne Stroustrup]]
+"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.]] [*--Bjarne
+Stroustrup]]

[heading History]

[heading /80s/]

-In the Mid 80s, Joel wrote his first calculator in Pascal. It has been
-an unforgettable coding experience. He was amazed how a mutually
+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 can model a grammar specification. In time,
the skills he acquired from that academic experience became very
practical. Periodically Joel was tasked to do some parsing. For
-instance, whenever he needs to perform any form of I/O, even in
-binary, he tries to approach the task somewhat formally by writing a
-grammar using Pascal- like syntax diagrams and then write a
-corresponding recursive-descent parser. This worked very well.
+instance, whenever he needed to perform any form of I/O, even in
+binary, he tried to approach the task somewhat formally by writing a
+grammar using Pascal-like syntax diagrams and then a corresponding
+recursive-descent parser. This worked very well.

[heading /90s/]

@@ -37,32 +38,26 @@
on the W3C formal specifications easily. He was certainly glad that
HTML had a formal grammar specification. Because of the influence of
the Internet, Joel then had to do more parsing. RFC specifications
-were everywhere. SGML, HTML, XML, even email addresses and those
-seemingly trivial URLs were all formally specified using small EBNF-
-style grammar specifications. This made him wish for a tool similar to
-big- time parser generators such as YACC and ANTLR, where a parser is
-built automatically from a grammar specification. Yet, he wants it to
-be extremely small; small enough to fit in my pocket, yet scalable.
-
-It must be able to practically parse simple grammars such as email
-addresses to moderately complex grammars such as XML and perhaps some
-small to medium-sized scripting languages. Scalability is a prime
-goal. You should be able to use it for small tasks such as parsing
-command lines without incurring a heavy payload, as you do when you
-are using YACC or PCCTS. Even now that it has evolved and matured to
-become a multi-module library, true to its original intent, Spirit can
-still be used for extreme micro-parsing tasks. You only pay for
-features that you need. The power of Spirit comes from its modularity
-and extensibility. Instead of giving you a sledgehammer, it gives you
-the right ingredients to create a sledgehammer easily.
+were everywhere! SGML, HTML, XML, email addresses and even those
+seemingly trivial URLs were all formally specified using small
+EBNF-style grammar specifications. This made him wish for a tool
+similar to larger parser generators such as YACC and ANTLR, where a
+parser is built automatically from a grammar specification.
+
+This ideal tool would be able to parse anything from email addresses
+and command lines, to XML and scripting languages. Scalability was a
+prime goal. The tool should be able to do this without incurring a
+heavy development load, which was not possible with the above
+mentioned parser generators.

The result was Spirit. Spirit was a personal project that was
-conceived when Joel was doing R&D in Japan. Inspired by the GoF's
-composite and interpreter patterns, he realized that he can model a
-recursive-descent parser with hierarchical-object composition of
-primitives (terminals) and composites (productions). The original
-version was implemented with run-time polymorphic classes. A parser is
-generated at run time by feeding in production rule strings such as:
+conceived when Joel was involved in R&D in Japan. Inspired by the
+GoF's composite and interpreter patterns, he realized that he can
+model a recursive-descent parser with hierarchical-object composition
+of primitives (terminals) and composites (productions). The original
+version was implemented with run-time polymorphic classes. A parser
+was generated at run time by feeding in production rule strings such
+as:

     "prod ::= {'A' | 'B'} 'C';"

@@ -76,22 +71,22 @@
parser using expression templates and static polymorphism, inspired by
the works of Todd Veldhuizen (__todd__exprtemplates__, C++ Report,
June 1995). Initially, the static-Spirit version was meant only to
-replace the core of the original dynamic-Spirit. Dynamic-spirit
-needed a parser to implement itself anyway. The original employed a
+replace the core of the original dynamic-Spirit. Dynamic-spirit needed
+a parser to implement itself anyway. The original employed a
hand-coded recursive-descent parser to parse the input grammar
-specification strings. Incidentially it was the time, when Hartmut
-joined the Spirit development.
+specification strings. It was at this time when Hartmut joined the
+Spirit development.

After its initial "open-source" debut in May 2001, static-Spirit
became a success. At around November 2001, the Spirit website had an
activity percentile of 98%, making it the number one parser tool at
-Source Forge at the time. Not bad for such a niche project such as a
-parser library. The "static" portion of Spirit was forgotten and
+Source Forge at the time. Not bad for a niche project like a parser
+library. The "static" portion of Spirit was forgotten and
static-Spirit simply became Spirit. The library soon evolved to
acquire more dynamic features.

Spirit was formally accepted into __boost__ in October 2002. Boost is
-a peer-reviewed, open collaborative development effort that is a
+a peer-reviewed, open collaborative development effort around a
collection of free Open Source C++ libraries covering a wide range of
domains. The Boost Libraries have become widely known as an industry
standard for design and implementation quality, robustness, and
@@ -104,24 +99,31 @@
now call [*/Classic-Spirit/] (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 rather
-in an ad-hoc manner, with the goal being 100% backward compatible with
-classic Spirit. Some parsers have attributes, some don't.
+time came to add attributes to the parser library, it was done in a
+rather ad-hoc manner, with the goal being 100% backward compatible
+with classic Spirit. As a result, some parsers have attributes, some
+don't.

Spirit V2 is another major rewrite. Spirit V2 grammars are fully
-attributed (see __attr_grammar__). All parser components have
-attributes. To do this efficiently and ellegantly, we had to use a
-couple of infrastructure libraries. Some of which haven't been written
-yet at the time, some were quite new when Spirit debuted, and some
-needed work. __mpl__ is an important infrastructure library, yet is
-not sufficient to implement Spirit V2. Another library had to be
-written: __fusion__. Fusion sits between MPL and STL --between compile
-time and runtime -- mapping types to values. Fusion is a direct
-descendant of both MPL and __boost_tuples__ (Fusion is now a full
-fledged __boost__ library). __phoenix__ also had to be beefed up to
-support Spirit V2. The result is __phoenix2__. Last but not least,
-Spirit V2 uses an __todd__exprtemplates__ library called
-__boost_proto__.
+attributed (see __attr_grammar__) which means that all parser
+components have attributes. To do this efficiently and elegantly, we
+had to use a couple of infrastructure libraries. Some did not exist,
+some were quite new when Spirit debuted, and some needed work. __mpl__
+is an important infrastructure library, yet is not sufficient to
+implement Spirit V2. Another library had to be written:
+__fusion__. Fusion sits between MPL and STL --between compile time and
+runtime -- mapping types to values. Fusion is a direct descendant of
+both MPL and __boost_tuples__. Fusion is now a full-fledged __boost__
+library. __phoenix__ also had to be beefed up to support Spirit
+V2. The result is __phoenix2__. Last but not least, Spirit V2 uses an
+__todd__exprtemplates__ library called __boost_proto__.
+
+Even though it has evolved and matured to become a multi-module
+library, Spirit is still used for micro-parsing tasks as well as
+scripting languages. Like C++, you only pay for features that you
+need. The power of Spirit comes from its modularity and
+extensibility. Instead of giving you a sledgehammer, it gives you the
+right ingredients to create a sledgehammer easily.

[heading New Ideas: Spirit V2]

@@ -133,30 +135,32 @@
(a grammar) to describe the expected structure of an input character
sequence. The same grammar may be used to formalize the structure of a
corresponding output character sequence. This is possible because
-parsing, most of the time, is implemented by comparing the input with
-the patterns defined by the grammar. If we use the same patterns to
-format a matching output, the generated sequence will follow the rules
-of the grammar as well.
-
-This insight lead to the implementation of a grammar driven output generation
-library compatibile with the Spirit parser library. As it turned out, parsing
-and generation are tightly connected and have very similar concepts. The
-duality of these two sides of the same medal is ubiquitous, which
-allowed us to build the parser library __qi__ and the generator library
-__karma__ using the same component infastructure.
-
-The idea of creating a lexer library well integrated with the Spirit parsers is
-not new. This has been discussed almost for the whole time of the existence of
-Classic-Spirit (pre V2) now. Several attempts to integrate existing lexer
-libraries and frameworks with Spirit have been made and served as a proof of
-concept and usability (for example see __wave__: The Boost C/C++ Preprocessor
-Library, and __slex__: a fully dynamic C++ lexer implemented with Spirit).
-Based on these experiences we added __lex__: a fully integrated lexer library
-to the mix, allowing to take advantage of the power of regular expressions for
-token matching, removing pressure from the parser components, simplifying
-parser grammars. Again, Spirit's modular structure allowed us to reuse the same
-underlying component library as for the parser and generator libraries.
-
+parsing is usually implemented by comparing the input with patterns
+defined by the grammar. If we use the same patterns to format a
+matching output, the generated sequence will follow the rules of the
+grammar as well.
+
+This insight lead to the implementation of a grammar driven output
+generation library compatibile with the Spirit parser library. As it
+turned out, parsing and generation are tightly connected and have very
+similar concepts. The duality of these two sides of the same medal is
+ubiquitous, which allowed us to build the parser library __qi__ and
+the generator library __karma__ using the same component
+infastructure.
+
+The idea of creating a lexer library well integrated with the Spirit
+parsers is not new. This has been discussed almost since
+Classic-Spirit (pre V2) initially debuted. Several attempts to
+integrate existing lexer libraries and frameworks with Spirit have
+been made and served as a proof of concept and usability (for example
+see __wave__: The Boost C/C++ Preprocessor Library, and __slex__: a
+fully dynamic C++ lexer implemented with Spirit). Based on these
+experiences we added __lex__: a fully integrated lexer library to the
+mix, allowing the user to take advantage of the power of regular
+expressions for token matching, removing pressure from the parser
+components, simplifying parser grammars. Again, Spirit's modular
+structure allowed us to reuse the same underlying component library as
+for the parser and generator libraries.

[heading How to use this manual]

@@ -166,8 +170,9 @@
# 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 using abundant examples and detailed instructions.
- Examples speak volumes.
+ using the library through abundant examples and detailed
+ instructions. Examples speak volumes and we have volumes of
+ examples!

# 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,

Date view	Thread view	Subject view	Author view

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