diff options
| author | ph10 <ph10@2f5784b3-3f2a-0410-8824-cb99058d5e15> | 2021-06-15 16:15:50 +0000 |
|---|---|---|
| committer | ph10 <ph10@2f5784b3-3f2a-0410-8824-cb99058d5e15> | 2021-06-15 16:15:50 +0000 |
| commit | 5d8a6b628ded65e28eb2a4a0f4baa1a9538da408 (patch) | |
| tree | 0bd323316d4f23f5a3e73ebeb5393467b58aa840 /doc/html/pcreapi.html | |
| parent | 453977045ee8d1e2d70824fbea9ed433518fb724 (diff) | |
| download | pcre-master.tar.gz | |
git-svn-id: svn://vcs.exim.org/pcre/code/trunk@1766 2f5784b3-3f2a-0410-8824-cb99058d5e15
Diffstat (limited to 'doc/html/pcreapi.html')
| -rw-r--r-- | doc/html/pcreapi.html | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/html/pcreapi.html b/doc/html/pcreapi.html index 2fdfbff..2a0491f 100644 --- a/doc/html/pcreapi.html +++ b/doc/html/pcreapi.html @@ -1718,7 +1718,7 @@ very long time, and so the <i>match_limit</i> value is also used in this case <P> The default value for the limit can be set when PCRE is built; the default default is 10 million, which handles all but the most extreme cases. You can -override the default by suppling <b>pcre_exec()</b> with a <b>pcre_extra</b> +override the default by supplying <b>pcre_exec()</b> with a <b>pcre_extra</b> block in which <i>match_limit</i> is set, and PCRE_EXTRA_MATCH_LIMIT is set in the <i>flags</i> field. If the limit is exceeded, <b>pcre_exec()</b> returns PCRE_ERROR_MATCHLIMIT. @@ -1749,7 +1749,7 @@ and is ignored, when matching is done using JIT compiled code. <P> The default value for <i>match_limit_recursion</i> can be set when PCRE is built; the default default is the same value as the default for -<i>match_limit</i>. You can override the default by suppling <b>pcre_exec()</b> +<i>match_limit</i>. You can override the default by supplying <b>pcre_exec()</b> with a <b>pcre_extra</b> block in which <i>match_limit_recursion</i> is set, and PCRE_EXTRA_MATCH_LIMIT_RECURSION is set in the <i>flags</i> field. If the limit is exceeded, <b>pcre_exec()</b> returns PCRE_ERROR_RECURSIONLIMIT. @@ -2063,10 +2063,10 @@ lookbehind. For example, consider the pattern </pre> which finds occurrences of "iss" in the middle of words. (\B matches only if the current position in the subject is not a word boundary.) When applied to -the string "Mississipi" the first call to <b>pcre_exec()</b> finds the first +the string "Mississippi" the first call to <b>pcre_exec()</b> finds the first occurrence. If <b>pcre_exec()</b> is called again with just the remainder of the -subject, namely "issipi", it does not match, because \B is always false at the -start of the subject, which is deemed to be a word boundary. However, if +subject, namely "issippi", it does not match, because \B is always false at +the start of the subject, which is deemed to be a word boundary. However, if <b>pcre_exec()</b> is passed the entire string again, but with <i>startoffset</i> set to 4, it finds the second occurrence of "iss" because it is able to look behind the starting point to discover that it is preceded by a letter. |