Rebuild the regex documentation.

[SVN r63768]
This commit is contained in:
Daniel James
2010-07-08 22:49:58 +00:00
parent 73fc09f4a3
commit 446b1d7c6e
82 changed files with 7675 additions and 7924 deletions

View File

@ -2,8 +2,8 @@
<head>
<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Partial Matches</title>
<link rel="stylesheet" href="../../../../../doc/html/boostbook.css" type="text/css">
<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
<link rel="stylesheet" href="../../../../../doc/src/boostbook.css" type="text/css">
<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
<link rel="home" href="../index.html" title="Boost.Regex">
<link rel="up" href="../index.html" title="Boost.Regex">
<link rel="prev" href="captures.html" title="Understanding Marked Sub-Expressions and Captures">
@ -20,9 +20,9 @@
</tr></table>
<hr>
<div class="spirit-nav">
<a accesskey="p" href="captures.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="syntax.html"><img src="../../../../../doc/html/images/next.png" alt="Next"></a>
<a accesskey="p" href="captures.html"><img src="../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="syntax.html"><img src="../../../../../doc/src/images/next.png" alt="Next"></a>
</div>
<div class="section" lang="en">
<div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
<a name="boost_regex.partial_matches"></a><a class="link" href="partial_matches.html" title="Partial Matches"> Partial Matches</a>
</h2></div></div></div>
@ -54,110 +54,108 @@
</colgroup>
<thead><tr>
<th>
<p>
</p>
</th>
<th>
<p>
Result
</p>
<p>
Result
</p>
</th>
<th>
<p>
M[0].matched
</p>
<p>
M[0].matched
</p>
</th>
<th>
<p>
M[0].first
</p>
<p>
M[0].first
</p>
</th>
<th>
<p>
M[0].second
</p>
<p>
M[0].second
</p>
</th>
</tr></thead>
<tbody>
<tr>
<td>
<p>
No match
</p>
<p>
No match
</p>
</td>
<td>
<p>
False
</p>
<p>
False
</p>
</td>
<td>
<p>
Undefined
</p>
<p>
Undefined
</p>
</td>
<td>
<p>
Undefined
</p>
<p>
Undefined
</p>
</td>
<td>
<p>
Undefined
</p>
<p>
Undefined
</p>
</td>
</tr>
<tr>
<td>
<p>
Partial match
</p>
<p>
Partial match
</p>
</td>
<td>
<p>
True
</p>
<p>
True
</p>
</td>
<td>
<p>
False
</p>
<p>
False
</p>
</td>
<td>
<p>
Start of partial match.
</p>
<p>
Start of partial match.
</p>
</td>
<td>
<p>
End of partial match (end of text).
</p>
<p>
End of partial match (end of text).
</p>
</td>
</tr>
<tr>
<td>
<p>
Full match
</p>
<p>
Full match
</p>
</td>
<td>
<p>
True
</p>
<p>
True
</p>
</td>
<td>
<p>
True
</p>
<p>
True
</p>
</td>
<td>
<p>
Start of full match.
</p>
<p>
Start of full match.
</p>
</td>
<td>
<p>
End of full match.
</p>
<p>
End of full match.
</p>
</td>
</tr>
</tbody>
@ -166,20 +164,20 @@
Be aware that using partial matches can sometimes result in somewhat imperfect
behavior:
</p>
<div class="itemizedlist"><ul type="disc">
<li>
There are some expressions, such as ".*abc" that will always produce
a partial match. This problem can be reduced by careful construction of the
regular expressions used, or by setting flags like match_not_dot_newline
so that expressions like .* can't match past line boundaries.
</li>
<li>
Boost.Regex currently prefers leftmost matches to full matches, so for example
matching "abc|b" against "ab" produces a partial match
against the "ab" rather than a full match against "b".
It's more efficient to work this way, but may not be the behavior you want
in all situations.
</li>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
There are some expressions, such as ".*abc" that will always
produce a partial match. This problem can be reduced by careful construction
of the regular expressions used, or by setting flags like match_not_dot_newline
so that expressions like .* can't match past line boundaries.
</li>
<li class="listitem">
Boost.Regex currently prefers leftmost matches to full matches, so for
example matching "abc|b" against "ab" produces a partial
match against the "ab" rather than a full match against "b".
It's more efficient to work this way, but may not be the behavior you want
in all situations.
</li>
</ul></div>
<p>
The following example tests to see whether the text could be a valid credit
@ -301,7 +299,7 @@
</tr></table>
<hr>
<div class="spirit-nav">
<a accesskey="p" href="captures.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="syntax.html"><img src="../../../../../doc/html/images/next.png" alt="Next"></a>
<a accesskey="p" href="captures.html"><img src="../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="syntax.html"><img src="../../../../../doc/src/images/next.png" alt="Next"></a>
</div>
</body>
</html>