Fix unclear wording pointed out by Tim Peters, about the interaction between
^ and the pos argument to re.match(). Also, fixed a typo in libregex.tex.
This commit is contained in:
parent
a8a1b9bc65
commit
65b7863efc
|
@ -476,9 +476,11 @@ attributes:
|
|||
match.
|
||||
|
||||
The optional second parameter \var{pos} gives an index in the string
|
||||
where the search is to start; it defaults to \code{0}. The
|
||||
\character{\^} pattern character will not match at the index where the
|
||||
search is to start.
|
||||
where the search is to start; it defaults to \code{0}. This is not
|
||||
completely equivalent to slicing the string; the \code{'\^'} pattern
|
||||
character matches at the real beginning of the string and at positions
|
||||
just after a newline, but not necessarily at the index where the search
|
||||
is to start.
|
||||
|
||||
The optional parameter \var{endpos} limits how far the string will
|
||||
be searched; it will be as if the string is \var{endpos} characters
|
||||
|
|
|
@ -288,7 +288,7 @@ Compiled regular expression objects support these methods:
|
|||
The optional second parameter, \var{pos}, gives an index in the string
|
||||
where the search is to start; it defaults to \code{0}. This is not
|
||||
completely equivalent to slicing the string; the \code{'\^'} pattern
|
||||
character matches at the real begin of the string and at positions
|
||||
character matches at the real beginning of the string and at positions
|
||||
just after a newline, not necessarily at the index where the search
|
||||
is to start.
|
||||
\end{funcdesc}
|
||||
|
|
Loading…
Reference in New Issue