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 | |
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')
-rw-r--r-- | doc/html/NON-AUTOTOOLS-BUILD.txt | 6 | ||||
-rw-r--r-- | doc/html/README.txt | 6 | ||||
-rw-r--r-- | doc/html/index.html | 14 | ||||
-rw-r--r-- | doc/html/pcreapi.html | 10 | ||||
-rw-r--r-- | doc/html/pcredemo.html | 4 | ||||
-rw-r--r-- | doc/html/pcrejit.html | 2 | ||||
-rw-r--r-- | doc/html/pcrepattern.html | 6 | ||||
-rw-r--r-- | doc/html/pcresyntax.html | 2 |
8 files changed, 25 insertions, 25 deletions
diff --git a/doc/html/NON-AUTOTOOLS-BUILD.txt b/doc/html/NON-AUTOTOOLS-BUILD.txt index 908c5c3..23c4e64 100644 --- a/doc/html/NON-AUTOTOOLS-BUILD.txt +++ b/doc/html/NON-AUTOTOOLS-BUILD.txt @@ -768,6 +768,6 @@ Everything, source and executable, is in EBCDIC and native z/OS file formats. However, this software is not maintained and will not be upgraded. If you are new to PCRE you should be looking at PCRE2 (version 10.30 or later). -=============================== -Last Updated: 13 September 2017 -=============================== +========================== +Last Updated: 15 June 2021 +========================== diff --git a/doc/html/README.txt b/doc/html/README.txt index 46617c0..65f5e19 100644 --- a/doc/html/README.txt +++ b/doc/html/README.txt @@ -997,6 +997,6 @@ pcre_xxx, one with the name pcre16_xx, and a third with the name pcre32_xxx. RunTest.bat a script for running tests under Windows Philip Hazel -Email local part: ph10 -Email domain: cam.ac.uk -Last updated: 12 February 2020 +Email local part: Philip.Hazel +Email domain: gmail.com +Last updated: 15 June 2021 diff --git a/doc/html/index.html b/doc/html/index.html index 887f4d7..352c55d 100644 --- a/doc/html/index.html +++ b/doc/html/index.html @@ -1,10 +1,10 @@ <html> -<!-- This is a manually maintained file that is the root of the HTML version of - the PCRE documentation. When the HTML documents are built from the man - page versions, the entire doc/html directory is emptied, this file is then - copied into doc/html/index.html, and the remaining files therein are +<!-- This is a manually maintained file that is the root of the HTML version of + the PCRE documentation. When the HTML documents are built from the man + page versions, the entire doc/html directory is emptied, this file is then + copied into doc/html/index.html, and the remaining files therein are created by the 132html script. ---> +--> <head> <title>PCRE specification</title> </head> @@ -96,7 +96,7 @@ in the library. There is a single page for each triple of 8-bit/16-bit/32-bit functions. </p> -<table> +<table> <tr><td><a href="pcre_assign_jit_stack.html">pcre_assign_jit_stack</a></td> <td> Assign stack for JIT matching</td></tr> @@ -162,7 +162,7 @@ functions. <tr><td><a href="pcre_maketables.html">pcre_maketables</a></td> <td> Build character tables in current locale</td></tr> - + <tr><td><a href="pcre_pattern_to_host_byte_order.html">pcre_pattern_to_host_byte_order</a></td> <td> Convert compiled pattern to host byte order if necessary</td></tr> 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. diff --git a/doc/html/pcredemo.html b/doc/html/pcredemo.html index 894a930..d84c5c8 100644 --- a/doc/html/pcredemo.html +++ b/doc/html/pcredemo.html @@ -161,7 +161,7 @@ if (rc < 0) return 1; } -/* Match succeded */ +/* Match succeeded */ printf("\nMatch succeeded at offset %d\n", ovector[0]); @@ -379,7 +379,7 @@ for (;;) return 1; } - /* Match succeded */ + /* Match succeeded */ printf("\nMatch succeeded again at offset %d\n", ovector[0]); diff --git a/doc/html/pcrejit.html b/doc/html/pcrejit.html index abb3425..c1e0310 100644 --- a/doc/html/pcrejit.html +++ b/doc/html/pcrejit.html @@ -299,7 +299,7 @@ recommended. This is a suggestion for how a multithreaded program that needs to set up non-default JIT stacks might operate: <pre> - During thread initalization + During thread initialization thread_local_var = pcre_jit_stack_alloc(...) During thread exit diff --git a/doc/html/pcrepattern.html b/doc/html/pcrepattern.html index 96fc729..2e3e626 100644 --- a/doc/html/pcrepattern.html +++ b/doc/html/pcrepattern.html @@ -655,7 +655,7 @@ recognized. <P> It is possible to restrict \R to match only CR, LF, or CRLF (instead of the complete set of Unicode line endings) by setting the option PCRE_BSR_ANYCRLF -either at compile time or when the pattern is matched. (BSR is an abbrevation +either at compile time or when the pattern is matched. (BSR is an abbreviation for "backslash R".) This can be made the default when PCRE is built; if this is the case, the other behaviour can be requested via the PCRE_BSR_UNICODE option. It is also possible to specify these settings by starting a pattern string with @@ -972,7 +972,7 @@ additional characters according to the following rules for ending a cluster: 3. Do not break Hangul (a Korean script) syllable sequences. Hangul characters are of five types: L, V, T, LV, and LVT. An L character may be followed by an L, V, LV, or LVT character; an LV or V character may be followed by a V or T -character; an LVT or T character may be follwed only by a T character. +character; an LVT or T character may be followed only by a T character. </P> <P> 4. Do not end before extending characters or spacing marks. Characters with @@ -3080,7 +3080,7 @@ successful match. Consider: </pre> If the subject is "aaaac...", after the first match attempt fails (starting at the first character in the string), the starting point skips on to start the -next attempt at "c". Note that a possessive quantifer does not have the same +next attempt at "c". Note that a possessive quantifier does not have the same effect as this example; although it would suppress backtracking during the first match attempt, the second attempt would start at the second character instead of skipping on to "c". diff --git a/doc/html/pcresyntax.html b/doc/html/pcresyntax.html index 5896b9e..2946ab3 100644 --- a/doc/html/pcresyntax.html +++ b/doc/html/pcresyntax.html @@ -157,7 +157,7 @@ is changed to use Unicode properties and they match many more characters. Xan Alphanumeric: union of properties L and N Xps POSIX space: property Z or tab, NL, VT, FF, CR Xsp Perl space: property Z or tab, NL, VT, FF, CR - Xuc Univerally-named character: one that can be + Xuc Universally-named character: one that can be represented by a Universal Character Name Xwd Perl word: property Xan or underscore </pre> |