Boost-Commit :

Date view	Thread view	Subject view	Author view

Subject: [Boost-commit] svn:boost r54099 - trunk/libs/spirit/classic/doc
From: joel_at_[hidden]
Date: 2009-06-19 01:38:42

Next message: christian.schladetsch_at_[hidden]: "[Boost-commit] svn:boost r54100 - sandbox/monotonic/libs/monotonic/test"
Previous message: christian.schladetsch_at_[hidden]: "[Boost-commit] svn:boost r54098 - sandbox/monotonic/libs/monotonic/test"

Author: djowel
Date: 2009-06-19 01:38:42 EDT (Fri, 19 Jun 2009)
New Revision: 54099
URL: http://svn.boost.org/trac/boost/changeset/54099

Log:
Typo-fix
Text files modified:
trunk/libs/spirit/classic/doc/dynamic_parsers.html | 68 +++++++++++++++++++++------------------
1 files changed, 36 insertions(+), 32 deletions(-)

Modified: trunk/libs/spirit/classic/doc/dynamic_parsers.html
==============================================================================
--- trunk/libs/spirit/classic/doc/dynamic_parsers.html (original)
+++ trunk/libs/spirit/classic/doc/dynamic_parsers.html 2009-06-19 01:38:42 EDT (Fri, 19 Jun 2009)
@@ -1,30 +1,35 @@
-<html>
-<head>
-<title>Dynamic Parsers</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="theme/style.css" type="text/css">
-</head>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html><head>

+<title>Dynamic Parsers</title><meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+<link rel="stylesheet" href="theme/style.css" type="text/css"></head>
<body>
-<table width="100%" border="0" background="theme/bkd2.gif" cellspacing="2">
- <tr>
+<table background="theme/bkd2.gif" border="0" cellspacing="2" width="100%">
+ <tbody><tr>
 <td width="10">
 </td>
- <td width="85%"> Dynamic
+ <td width="85%"> Dynamic
 Parsers </td>
- <td width="112"></td>
+ <td width="112"></td>
 </tr>
-</table>
+</tbody></table>
 
<table border="0">
- <tr>
+ <tbody><tr>
 <td width="10"></td>
 <td width="30"></td>
 <td width="30"></td>
 <td width="30"></td>
 </tr>
-</table>
-We see dynamic parsing everywhere in Spirit. A special group of parsers, aptly named dynamic parsers, form the most basic building blocks to dynamic parsing. This chapter focuses on these critters. You'll notice the similarity of these parsers with C++'s control structures. The similarity is not a coincidence. These parsers give an imperative flavor to parsing, and, since imperative constructs are not native to declarative EBNF, mimicking the host language, C++, should make their use immediately familiar. 
+</tbody></table>
+We see dynamic parsing everywhere in Spirit. A special group of
+parsers, aptly named dynamic parsers, form the most basic building
+blocks to dynamic parsing. This chapter focuses on these critters.
+You'll notice the similarity of these parsers with C++'s control
+structures. The similarity is not a coincidence. These parsers give an
+imperative flavor to parsing, and, since imperative constructs are not
+native to declarative EBNF, mimicking the host language, C++, should
+make their use immediately familiar. 
Dynamic parsers modify the parsing behavior according to conditions. Constructing
 dynamic parsers requires a condition argument and a body parser argument. Additional
 arguments are required by some parsers.
@@ -38,58 +43,57 @@
A failure to meet the condition will not result in a parse error.
<h2>if_p</h2>
<tt>if_p</tt> can be used with or without an else-part. The syntax is:
-<pre> if_p(condition)[then-parser]</pre>
-or
-<pre> if_p(condition)[then-parser].else_p[else-parser]</pre>
+<pre> if_p(condition)[then-parser]</pre>
+or
+<pre> if_p(condition)[then-parser].else_p[else-parser]</pre>
When the condition is met the then-parser is used next in the parsing process.
 When the condition is not met and an else-parser is available the else-parser
 is used next. When the condition isn't met and no else-parser is available then
- the whole parser matches the empty sequence. (<img src="theme/alert.gif" width="16" height="16">
+ the whole parser matches the empty sequence. (<img src="theme/alert.gif" height="16" width="16">
 Note: older versions of <tt>if_p</tt> report a failure when the condition isn't
 met and no else-parser is available.)
Example:
-<pre> if_p("0x")[hex_p].else_p[uint_p]</pre>
+<pre> if_p("0x")[hex_p].else_p[uint_p]</pre>
<h2>while_p, do_p</h2>
<tt>while_p</tt>/<tt>do_p</tt> syntax is:
-<pre> while_p(condition)[body-parser]
- do_p[body-parser].while_p(condition)</pre>
+<pre> while_p(condition)[body-parser] do_p[body-parser].while_p(condition)</pre>
As long as the condition is met the dynamic parser constructed by <tt>while_p</tt>
 will try to match the body-parser. <tt>do_p</tt> returns a parser that tries
 to match the body-parser and then behaves just like the parser returned by <tt>while_p</tt>.
 A failure to match the body-parser will cause a failure to be reported by the
 while/do-parser.
Example:
-<pre> uint_p[assign_a(sum)] >> while_p('+')[uint_p(add(sum)]
- '"' >> while_p(~eps_p('"'))[c_escape_ch_p[push_back_a(result)]] >> '"'
+<pre> uint_p[assign_a(sum)] >> while_p('+')[uint_p[add(sum)]] '"' >> while_p(~eps_p('"'))[c_escape_ch_p[push_back_a(result)]] >> '"'
</pre>
-<h2>for_p</h2>
+Assuming add is a user defined function object. <h2>for_p</h2>
<tt>for_p</tt> requires four arguments. The syntax is:
-<pre> for_p(init, condition, step)[body-parser]</pre>
+<pre> for_p(init, condition, step)[body-parser]</pre>
init and step have to be 0-ary functions/functors. for_p returns a parser that
 will:
<ol>
 <li> call init</li>
- <li>check the condition, if the condition isn't met then a match is returned. The match will cover everything that has been matched successfully up to this point.</li>
+ <li>check the condition, if the
+condition isn't met then a match is returned. The match will cover
+everything that has been matched successfully up to this point.</li>
 <li> tries to match the body-parser. A failure to match the body-parser will cause a failure to be reported by the for-parser</li>
 <li> calls step</li>
 <li> goes to 2.</li>
</ol>
<table border="0">
- <tr>
+ <tbody><tr>
 <td width="10"></td>
 <td width="30"></td>
 <td width="30"></td>
 <td width="30"></td>
 </tr>
-</table>
+</tbody></table>
 
<hr size="1">
-Copyright © 2002-2003 Joel de Guzman 
- Copyright © 2002-2003 Martin Wille 
+Copyright © 2002-2003 Joel de Guzman 
+ Copyright © 2002-2003 Martin Wille 
 
Use, modification and distribution is subject to 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)
 
-</body>
-</html>
+</body></html>
\ No newline at end of file

Next message: christian.schladetsch_at_[hidden]: "[Boost-commit] svn:boost r54100 - sandbox/monotonic/libs/monotonic/test"
Previous message: christian.schladetsch_at_[hidden]: "[Boost-commit] svn:boost r54098 - sandbox/monotonic/libs/monotonic/test"

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