summaryrefslogtreecommitdiffstats
path: root/Doc/lib
diff options
context:
space:
mode:
authorFred Drake <fdrake@acm.org>1999-06-29 21:21:19 (GMT)
committerFred Drake <fdrake@acm.org>1999-06-29 21:21:19 (GMT)
commit3d0971e33e81538862cd71425d97c3cfea5e3c00 (patch)
tree4629cb82a29ded817479a82e3051dae4166f5b3c /Doc/lib
parent9b59a303a83c71b1e82c0b11278be5ed579e7ac3 (diff)
downloadcpython-3d0971e33e81538862cd71425d97c3cfea5e3c00.zip
cpython-3d0971e33e81538862cd71425d97c3cfea5e3c00.tar.gz
cpython-3d0971e33e81538862cd71425d97c3cfea5e3c00.tar.bz2
For "Matching vs. Searching", remove comment that the section is
incomplete; I don't remember what else I thought I was going to put in, but it looks o.k. to me know.
Diffstat (limited to 'Doc/lib')
-rw-r--r--Doc/lib/libre.tex14
1 files changed, 6 insertions, 8 deletions
diff --git a/Doc/lib/libre.tex b/Doc/lib/libre.tex
index b9f5f32..1144fec 100644
--- a/Doc/lib/libre.tex
+++ b/Doc/lib/libre.tex
@@ -286,8 +286,6 @@ for the current locale.
\subsection{Matching vs. Searching \label{matching-searching}}
\sectionauthor{Fred L. Drake, Jr.}{fdrake@acm.org}
-\strong{XXX This section is still incomplete!}
-
Python offers two different primitive operations based on regular
expressions: match and search. If you are accustomed to Perl's
semantics, the search operation is what you're looking for. See the
@@ -295,12 +293,12 @@ semantics, the search operation is what you're looking for. See the
regular expression objects.
Note that match may differ from search using a regular expression
-beginning with \character{\^}: \character{\^} matches only at the start
-of the string, or in \constant{MULTILINE} mode also immediately
-following a newline. "match" succeeds only if the pattern matches at
-the start of the string regardless of mode, or at the starting
-position given by the optional \var{pos} argument regardless of
-whether a newline precedes it.
+beginning with \character{\^}: \character{\^} matches only at the
+start of the string, or in \constant{MULTILINE} mode also immediately
+following a newline. The ``match'' operation succeeds only if the
+pattern matches at the start of the string regardless of mode, or at
+the starting position given by the optional \var{pos} argument
+regardless of whether a newline precedes it.
% Examples from Tim Peters:
\begin{verbatim}