|
Boost-Commit : |
Subject: [Boost-commit] svn:boost r56508 - in trunk/libs/spirit/doc: . qi
From: joel_at_[hidden]
Date: 2009-10-02 04:34:21
Author: djowel
Date: 2009-10-02 04:34:18 EDT (Fri, 02 Oct 2009)
New Revision: 56508
URL: http://svn.boost.org/trac/boost/changeset/56508
Log:
#3502 fix
Text files modified:
trunk/libs/spirit/doc/qi/employee.qbk | 12 ++++++------
trunk/libs/spirit/doc/qi/warming_up.qbk | 12 ++++++------
trunk/libs/spirit/doc/what_s_new.qbk | 2 +-
3 files changed, 13 insertions(+), 13 deletions(-)
Modified: trunk/libs/spirit/doc/qi/employee.qbk
==============================================================================
--- trunk/libs/spirit/doc/qi/employee.qbk (original)
+++ trunk/libs/spirit/doc/qi/employee.qbk 2009-10-02 04:34:18 EDT (Fri, 02 Oct 2009)
@@ -8,12 +8,12 @@
[section Employee - Parsing into structs]
-It's a common question in the __spirit_list__: How do I parse and place the
-results into a C++ struct? Of course, at this point, you already know various
-ways to do it, using semantic actions. There are many ways to skin a cat.
-Spirit2, being fully attributed, makes it even easier. The next example
-demonstrates some features of Spirit2 that makes this easy. In the process,
-you'll learn about:
+It's a common question in the __spirit_list__: How do I parse and place
+the results into a C++ struct? Of course, at this point, you already
+know various ways to do it, using semantic actions. There are many ways
+to skin a cat. Spirit2, being fully attributed, makes it even easier.
+The next example demonstrates some features of Spirit2 that make this
+easy. In the process, you'll learn about:
* More about attributes
* Auto rules
Modified: trunk/libs/spirit/doc/qi/warming_up.qbk
==============================================================================
--- trunk/libs/spirit/doc/qi/warming_up.qbk (original)
+++ trunk/libs/spirit/doc/qi/warming_up.qbk 2009-10-02 04:34:18 EDT (Fri, 02 Oct 2009)
@@ -99,12 +99,12 @@
[import ../../example/qi/num_list1.cpp]
[tutorial_numlist1]
-The parse function returns `true` or `false` 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 match.
-If not, then we have a partial match. A partial match happens when the
-parser is only able to parse a portion of the input.
+The parse function returns `true` or `false` 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 `last`, then we have a full
+match. If not, then we have a partial match. A partial match happens
+when the parser is only able to parse a portion of the input.
Note that we inlined the parser directly in the call to parse. Upon calling
parse, the expression evaluates into a temporary, unnamed parser which is passed
Modified: trunk/libs/spirit/doc/what_s_new.qbk
==============================================================================
--- trunk/libs/spirit/doc/what_s_new.qbk (original)
+++ trunk/libs/spirit/doc/what_s_new.qbk 2009-10-02 04:34:18 EDT (Fri, 02 Oct 2009)
@@ -113,7 +113,7 @@
template <typename Lexer>
struct example_tokens : lex::lexer<Lexer>
{
- example_lexer()
+ example_tokens()
{
// your token definitions here
this->self = ...
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