diff options
Diffstat (limited to 'doc/html/pcre2api.html')
| -rw-r--r-- | doc/html/pcre2api.html | 272 |
1 files changed, 193 insertions, 79 deletions
diff --git a/doc/html/pcre2api.html b/doc/html/pcre2api.html index bf1dd8e..fa9f342 100644 --- a/doc/html/pcre2api.html +++ b/doc/html/pcre2api.html @@ -43,16 +43,17 @@ please consult the man page, in case the conversion went wrong. <li><a name="TOC28" href="#SEC28">HOW PCRE2_MATCH() RETURNS A STRING AND CAPTURED SUBSTRINGS</a> <li><a name="TOC29" href="#SEC29">OTHER INFORMATION ABOUT A MATCH</a> <li><a name="TOC30" href="#SEC30">ERROR RETURNS FROM <b>pcre2_match()</b></a> -<li><a name="TOC31" href="#SEC31">EXTRACTING CAPTURED SUBSTRINGS BY NUMBER</a> -<li><a name="TOC32" href="#SEC32">EXTRACTING A LIST OF ALL CAPTURED SUBSTRINGS</a> -<li><a name="TOC33" href="#SEC33">EXTRACTING CAPTURED SUBSTRINGS BY NAME</a> -<li><a name="TOC34" href="#SEC34">CREATING A NEW STRING WITH SUBSTITUTIONS</a> -<li><a name="TOC35" href="#SEC35">DUPLICATE SUBPATTERN NAMES</a> -<li><a name="TOC36" href="#SEC36">FINDING ALL POSSIBLE MATCHES AT ONE POSITION</a> -<li><a name="TOC37" href="#SEC37">MATCHING A PATTERN: THE ALTERNATIVE FUNCTION</a> -<li><a name="TOC38" href="#SEC38">SEE ALSO</a> -<li><a name="TOC39" href="#SEC39">AUTHOR</a> -<li><a name="TOC40" href="#SEC40">REVISION</a> +<li><a name="TOC31" href="#SEC31">OBTAINING A TEXTUAL ERROR MESSAGE</a> +<li><a name="TOC32" href="#SEC32">EXTRACTING CAPTURED SUBSTRINGS BY NUMBER</a> +<li><a name="TOC33" href="#SEC33">EXTRACTING A LIST OF ALL CAPTURED SUBSTRINGS</a> +<li><a name="TOC34" href="#SEC34">EXTRACTING CAPTURED SUBSTRINGS BY NAME</a> +<li><a name="TOC35" href="#SEC35">CREATING A NEW STRING WITH SUBSTITUTIONS</a> +<li><a name="TOC36" href="#SEC36">DUPLICATE SUBPATTERN NAMES</a> +<li><a name="TOC37" href="#SEC37">FINDING ALL POSSIBLE MATCHES AT ONE POSITION</a> +<li><a name="TOC38" href="#SEC38">MATCHING A PATTERN: THE ALTERNATIVE FUNCTION</a> +<li><a name="TOC39" href="#SEC39">SEE ALSO</a> +<li><a name="TOC40" href="#SEC40">AUTHOR</a> +<li><a name="TOC41" href="#SEC41">REVISION</a> </ul> <P> <b>#include <pcre2.h></b> @@ -290,6 +291,9 @@ document for an overview of all the PCRE2 documentation. </P> <br><a name="SEC10" href="#TOC1">PCRE2 NATIVE API AUXILIARY FUNCTIONS</a><br> <P> +<b>pcre2_code *pcre2_code_copy(const pcre2_code *<i>code</i>);</b> +<br> +<br> <b>int pcre2_get_error_message(int <i>errorcode</i>, PCRE2_UCHAR *<i>buffer</i>,</b> <b> PCRE2_SIZE <i>bufflen</i>);</b> <br> @@ -414,9 +418,10 @@ More complicated programs might need to make use of the specialist functions <b>pcre2_jit_stack_assign()</b> in order to control the JIT code's memory usage. </P> <P> -JIT matching is automatically used by <b>pcre2_match()</b> if it is available. -There is also a direct interface for JIT matching, which gives improved -performance. The JIT-specific functions are discussed in the +JIT matching is automatically used by <b>pcre2_match()</b> if it is available, +unless the PCRE2_NO_JIT option is set. There is also a direct interface for JIT +matching, which gives improved performance. The JIT-specific functions are +discussed in the <a href="pcre2jit.html"><b>pcre2jit</b></a> documentation. </P> @@ -455,10 +460,19 @@ return a copy of the subject string with substitutions for parts that were matched. </P> <P> +Functions whose names begin with <b>pcre2_serialize_</b> are used for saving +compiled patterns on disc or elsewhere, and reloading them later. +</P> +<P> Finally, there are functions for finding out information about a compiled pattern (<b>pcre2_pattern_info()</b>) and about the configuration with which PCRE2 was built (<b>pcre2_config()</b>). </P> +<P> +Functions with names ending with <b>_free()</b> are used for freeing memory +blocks of various sorts. In all cases, if one of these functions is called with +a NULL argument, it does nothing. +</P> <br><a name="SEC13" href="#TOC1">STRING LENGTHS AND OFFSETS</a><br> <P> The PCRE2 API uses string lengths and offsets into strings of code units in @@ -516,20 +530,51 @@ time ensuring that multithreaded applications can use it. There are several different blocks of data that are used to pass information between the application and the PCRE2 libraries. </P> +<br><b> +The compiled pattern +</b><br> <P> -(1) A pointer to the compiled form of a pattern is returned to the user when +A pointer to the compiled form of a pattern is returned to the user when <b>pcre2_compile()</b> is successful. The data in the compiled pattern is fixed, and does not change when the pattern is matched. Therefore, it is thread-safe, that is, the same compiled pattern can be used by more than one thread -simultaneously. An application can compile all its patterns at the start, -before forking off multiple threads that use them. However, if the just-in-time -optimization feature is being used, it needs separate memory stack areas for -each thread. See the +simultaneously. For example, an application can compile all its patterns at the +start, before forking off multiple threads that use them. However, if the +just-in-time optimization feature is being used, it needs separate memory stack +areas for each thread. See the <a href="pcre2jit.html"><b>pcre2jit</b></a> documentation for more details. </P> <P> -(2) The next section below introduces the idea of "contexts" in which PCRE2 +In a more complicated situation, where patterns are compiled only when they are +first needed, but are still shared between threads, pointers to compiled +patterns must be protected from simultaneous writing by multiple threads, at +least until a pattern has been compiled. The logic can be something like this: +<pre> + Get a read-only (shared) lock (mutex) for pointer + if (pointer == NULL) + { + Get a write (unique) lock for pointer + pointer = pcre2_compile(... + } + Release the lock + Use pointer in pcre2_match() +</pre> +Of course, testing for compilation errors should also be included in the code. +</P> +<P> +If JIT is being used, but the JIT compilation is not being done immediately, +(perhaps waiting to see if the pattern is used often enough) similar logic is +required. JIT compilation updates a pointer within the compiled code block, so +a thread must gain unique write access to the pointer before calling +<b>pcre2_jit_compile()</b>. Alternatively, <b>pcre2_code_copy()</b> can be used +to obtain a private copy of the compiled code. +</P> +<br><b> +Context blocks +</b><br> +<P> +The next main section below introduces the idea of "contexts" in which PCRE2 functions are called. A context is nothing more than a collection of parameters that control the way PCRE2 operates. Grouping a number of parameters together in a context is a convenient way of passing them to a PCRE2 function without @@ -543,11 +588,14 @@ are never changed, the same context can be used by all the threads. However, if any thread needs to change any value in a context, it must make its own thread-specific copy. </P> +<br><b> +Match blocks +</b><br> <P> -(3) The matching functions need a block of memory for working space and for -storing the results of a match. This includes details of what was matched, as -well as additional information such as the name of a (*MARK) setting. Each -thread must provide its own version of this memory. +The matching functions need a block of memory for working space and for storing +the results of a match. This includes details of what was matched, as well as +additional information such as the name of a (*MARK) setting. Each thread must +provide its own copy of this memory. </P> <br><a name="SEC16" href="#TOC1">PCRE2 CONTEXTS</a><br> <P> @@ -1007,34 +1055,50 @@ zero. <br> <br> <b>void pcre2_code_free(pcre2_code *<i>code</i>);</b> +<br> +<br> +<b>pcre2_code *pcre2_code_copy(const pcre2_code *<i>code</i>);</b> </P> <P> The <b>pcre2_compile()</b> function compiles a pattern into an internal form. -The pattern is defined by a pointer to a string of code units and a length, If +The pattern is defined by a pointer to a string of code units and a length. If the pattern is zero-terminated, the length can be specified as PCRE2_ZERO_TERMINATED. The function returns a pointer to a block of memory that -contains the compiled pattern and related data. The caller must free the memory -by calling <b>pcre2_code_free()</b> when it is no longer needed. +contains the compiled pattern and related data, or NULL if an error occurred. +</P> +<P> +If the compile context argument <i>ccontext</i> is NULL, memory for the compiled +pattern is obtained by calling <b>malloc()</b>. Otherwise, it is obtained from +the same memory function that was used for the compile context. The caller must +free the memory by calling <b>pcre2_code_free()</b> when it is no longer needed. +</P> +<P> +The function <b>pcre2_code_copy()</b> makes a copy of the compiled code in new +memory, using the same memory allocator as was used for the original. However, +if the code has been processed by the JIT compiler (see +<a href="#jitcompiling">below),</a> +the JIT information cannot be copied (because it is position-dependent). +The new copy can initially be used only for non-JIT matching, though it can be +passed to <b>pcre2_jit_compile()</b> if required. The <b>pcre2_code_copy()</b> +function provides a way for individual threads in a multithreaded application +to acquire a private copy of shared compiled code. </P> <P> NOTE: When one of the matching functions is called, pointers to the compiled pattern and the subject string are set in the match data block so that they can -be referenced by the extraction functions. After running a match, you must not -free a compiled pattern (or a subject string) until after all operations on the +be referenced by the substring extraction functions. After running a match, you +must not free a compiled pattern (or a subject string) until after all +operations on the <a href="#matchdatablock">match data block</a> have taken place. </P> <P> -If the compile context argument <i>ccontext</i> is NULL, memory for the compiled -pattern is obtained by calling <b>malloc()</b>. Otherwise, it is obtained from -the same memory function that was used for the compile context. -</P> -<P> -The <i>options</i> argument contains various bit settings that affect the -compilation. It should be zero if no options are required. The available -options are described below. Some of them (in particular, those that are -compatible with Perl, but some others as well) can also be set and unset from -within the pattern (see the detailed description in the +The <i>options</i> argument for <b>pcre2_compile()</b> contains various bit +settings that affect the compilation. It should be zero if no options are +required. The available options are described below. Some of them (in +particular, those that are compatible with Perl, but some others as well) can +also be set and unset from within the pattern (see the detailed description in +the <a href="pcre2pattern.html"><b>pcre2pattern</b></a> documentation). </P> @@ -1051,13 +1115,20 @@ newline setting) can be provided in a compile context (as described </P> <P> If <i>errorcode</i> or <i>erroroffset</i> is NULL, <b>pcre2_compile()</b> returns -NULL immediately. Otherwise, if compilation of a pattern fails, -<b>pcre2_compile()</b> returns NULL, having set these variables to an error code -and an offset (number of code units) within the pattern, respectively. The -<b>pcre2_get_error_message()</b> function provides a textual message for each -error code. Compilation errors are positive numbers, but UTF formatting errors -are negative numbers. For an invalid UTF-8 or UTF-16 string, the offset is that -of the first code unit of the failing character. +NULL immediately. Otherwise, the variables to which these point are set to an +error code and an offset (number of code units) within the pattern, +respectively, when <b>pcre2_compile()</b> returns NULL because a compilation +error has occurred. The values are not defined when compilation is successful +and <b>pcre2_compile()</b> returns a non-NULL value. +</P> +<P> +The <b>pcre2_get_error_message()</b> function (see "Obtaining a textual error +message" +<a href="#geterrormessage">below)</a> +provides a textual message for each error code. Compilation errors have +positive error codes; UTF formatting error codes are negative. For an invalid +UTF-8 or UTF-16 string, the offset is that of the first code unit of the +failing character. </P> <P> Some errors are not detected until the whole pattern has been scanned; in these @@ -1282,7 +1353,9 @@ If this option is set, it disables the use of numbered capturing parentheses in the pattern. Any opening parenthesis that is not followed by ? behaves as if it were followed by ?: but named parentheses can still be used for capturing (and they acquire numbers in the usual way). There is no equivalent of this option -in Perl. +in Perl. Note that, if this option is set, references to capturing groups (back +references or recursion/subroutine calls) may only refer to named groups, +though the reference can be by name or by number. <pre> PCRE2_NO_AUTO_POSSESS </pre> @@ -1424,14 +1497,17 @@ page. </P> <br><a name="SEC19" href="#TOC1">COMPILATION ERROR CODES</a><br> <P> -There are over 80 positive error codes that <b>pcre2_compile()</b> may return if -it finds an error in the pattern. There are also some negative error codes that -are used for invalid UTF strings. These are the same as given by -<b>pcre2_match()</b> and <b>pcre2_dfa_match()</b>, and are described in the +There are over 80 positive error codes that <b>pcre2_compile()</b> may return +(via <i>errorcode</i>) if it finds an error in the pattern. There are also some +negative error codes that are used for invalid UTF strings. These are the same +as given by <b>pcre2_match()</b> and <b>pcre2_dfa_match()</b>, and are described +in the <a href="pcre2unicode.html"><b>pcre2unicode</b></a> -page. The <b>pcre2_get_error_message()</b> function can be called to obtain a -textual error message from any error code. -</P> +page. The <b>pcre2_get_error_message()</b> function (see "Obtaining a textual +error message" +<a href="#geterrormessage">below)</a> +can be called to obtain a textual error message from any error code. +<a name="jitcompiling"></a></P> <br><a name="SEC20" href="#TOC1">JUST-IN-TIME (JIT) COMPILATION</a><br> <P> <b>int pcre2_jit_compile(pcre2_code *<i>code</i>, uint32_t <i>options</i>);</b> @@ -1567,10 +1643,15 @@ are as follows: Return a copy of the pattern's options. The third argument should point to a <b>uint32_t</b> variable. PCRE2_INFO_ARGOPTIONS returns exactly the options that were passed to <b>pcre2_compile()</b>, whereas PCRE2_INFO_ALLOPTIONS returns -the compile options as modified by any top-level option settings such as (*UTF) -at the start of the pattern itself. For example, if the pattern /(*UTF)abc/ is -compiled with the PCRE2_EXTENDED option, the result is PCRE2_EXTENDED and -PCRE2_UTF. +the compile options as modified by any top-level (*XXX) option settings such as +(*UTF) at the start of the pattern itself. +</P> +<P> +For example, if the pattern /(*UTF)abc/ is compiled with the PCRE2_EXTENDED +option, the result for PCRE2_INFO_ALLOPTIONS is PCRE2_EXTENDED and PCRE2_UTF. +Option settings such as (?i) that can change within a pattern do not affect the +result of PCRE2_INFO_ALLOPTIONS, even if they appear right at the start of the +pattern. (This was different in some earlier releases.) </P> <P> A pattern compiled without PCRE2_ANCHORED is automatically anchored by PCRE2 if @@ -2025,14 +2106,15 @@ Option bits for <b>pcre2_match()</b> <P> The unused bits of the <i>options</i> argument for <b>pcre2_match()</b> must be zero. The only bits that may be set are PCRE2_ANCHORED, PCRE2_NOTBOL, -PCRE2_NOTEOL, PCRE2_NOTEMPTY, PCRE2_NOTEMPTY_ATSTART, PCRE2_NO_UTF_CHECK, -PCRE2_PARTIAL_HARD, and PCRE2_PARTIAL_SOFT. Their action is described below. +PCRE2_NOTEOL, PCRE2_NOTEMPTY, PCRE2_NOTEMPTY_ATSTART, PCRE2_NO_JIT, +PCRE2_NO_UTF_CHECK, PCRE2_PARTIAL_HARD, and PCRE2_PARTIAL_SOFT. Their action is +described below. </P> <P> Setting PCRE2_ANCHORED at match time is not supported by the just-in-time (JIT) compiler. If it is set, JIT matching is disabled and the normal interpretive -code in <b>pcre2_match()</b> is run. The remaining options are supported for JIT -matching. +code in <b>pcre2_match()</b> is run. Apart from PCRE2_NO_JIT (obviously), the +remaining options are supported for JIT matching. <pre> PCRE2_ANCHORED </pre> @@ -2080,6 +2162,13 @@ the starting offset. An empty string match later in the subject is permitted. If the pattern is anchored, such a match can occur only if the pattern contains \K. <pre> + PCRE2_NO_JIT +</pre> +By default, if a pattern has been successfully processed by +<b>pcre2_jit_compile()</b>, JIT is automatically used when <b>pcre2_match()</b> +is called with options that JIT supports. Setting PCRE2_NO_JIT disables the use +of JIT; it forces matching to be done by the interpreter. +<pre> PCRE2_NO_UTF_CHECK </pre> When PCRE2_UTF is set at compile time, the validity of the subject as a UTF @@ -2339,11 +2428,13 @@ page. <br><a name="SEC30" href="#TOC1">ERROR RETURNS FROM <b>pcre2_match()</b></a><br> <P> If <b>pcre2_match()</b> fails, it returns a negative number. This can be -converted to a text string by calling <b>pcre2_get_error_message()</b>. Negative -error codes are also returned by other functions, and are documented with them. -The codes are given names in the header file. If UTF checking is in force and -an invalid UTF subject string is detected, one of a number of UTF-specific -negative error codes is returned. Details are given in the +converted to a text string by calling the <b>pcre2_get_error_message()</b> +function (see "Obtaining a textual error message" +<a href="#geterrormessage">below).</a> +Negative error codes are also returned by other functions, and are documented +with them. The codes are given names in the header file. If UTF checking is in +force and an invalid UTF subject string is detected, one of a number of +UTF-specific negative error codes is returned. Details are given in the <a href="pcre2unicode.html"><b>pcre2unicode</b></a> page. The following are the other errors that may be returned by <b>pcre2_match()</b>: @@ -2444,8 +2535,29 @@ is attempted. PCRE2_ERROR_RECURSIONLIMIT </pre> The internal recursion limit was reached. +<a name="geterrormessage"></a></P> +<br><a name="SEC31" href="#TOC1">OBTAINING A TEXTUAL ERROR MESSAGE</a><br> +<P> +<b>int pcre2_get_error_message(int <i>errorcode</i>, PCRE2_UCHAR *<i>buffer</i>,</b> +<b> PCRE2_SIZE <i>bufflen</i>);</b> +</P> +<P> +A text message for an error code from any PCRE2 function (compile, match, or +auxiliary) can be obtained by calling <b>pcre2_get_error_message()</b>. The code +is passed as the first argument, with the remaining two arguments specifying a +code unit buffer and its length, into which the text message is placed. Note +that the message is returned in code units of the appropriate width for the +library that is being used. +</P> +<P> +The returned message is terminated with a trailing zero, and the function +returns the number of code units used, excluding the trailing zero. If the +error number is unknown, the negative error code PCRE2_ERROR_BADDATA is +returned. If the buffer is too small, the message is truncated (but still with +a trailing zero), and the negative error code PCRE2_ERROR_NOMEMORY is returned. +None of the messages are very long; a buffer size of 120 code units is ample. <a name="extractbynumber"></a></P> -<br><a name="SEC31" href="#TOC1">EXTRACTING CAPTURED SUBSTRINGS BY NUMBER</a><br> +<br><a name="SEC32" href="#TOC1">EXTRACTING CAPTURED SUBSTRINGS BY NUMBER</a><br> <P> <b>int pcre2_substring_length_bynumber(pcre2_match_data *<i>match_data</i>,</b> <b> uint32_t <i>number</i>, PCRE2_SIZE *<i>length</i>);</b> @@ -2542,7 +2654,7 @@ The substring did not participate in the match. For example, if the pattern is (abc)|(def) and the subject is "def", and the ovector contains at least two capturing slots, substring number 1 is unset. </P> -<br><a name="SEC32" href="#TOC1">EXTRACTING A LIST OF ALL CAPTURED SUBSTRINGS</a><br> +<br><a name="SEC33" href="#TOC1">EXTRACTING A LIST OF ALL CAPTURED SUBSTRINGS</a><br> <P> <b>int pcre2_substring_list_get(pcre2_match_data *<i>match_data</i>,</b> <b>" PCRE2_UCHAR ***<i>listptr</i>, PCRE2_SIZE **<i>lengthsptr</i>);</b> @@ -2581,7 +2693,7 @@ can be distinguished from a genuine zero-length substring by inspecting the appropriate offset in the ovector, which contain PCRE2_UNSET for unset substrings, or by calling <b>pcre2_substring_length_bynumber()</b>. <a name="extractbyname"></a></P> -<br><a name="SEC33" href="#TOC1">EXTRACTING CAPTURED SUBSTRINGS BY NAME</a><br> +<br><a name="SEC34" href="#TOC1">EXTRACTING CAPTURED SUBSTRINGS BY NAME</a><br> <P> <b>int pcre2_substring_number_from_name(const pcre2_code *<i>code</i>,</b> <b> PCRE2_SPTR <i>name</i>);</b> @@ -2641,7 +2753,7 @@ names are not included in the compiled code. The matching process uses only numbers. For this reason, the use of different names for subpatterns of the same number causes an error at compile time. </P> -<br><a name="SEC34" href="#TOC1">CREATING A NEW STRING WITH SUBSTITUTIONS</a><br> +<br><a name="SEC35" href="#TOC1">CREATING A NEW STRING WITH SUBSTITUTIONS</a><br> <P> <b>int pcre2_substitute(const pcre2_code *<i>code</i>, PCRE2_SPTR <i>subject</i>,</b> <b> PCRE2_SIZE <i>length</i>, PCRE2_SIZE <i>startoffset</i>,</b> @@ -2844,9 +2956,11 @@ started, which can happen if \K is used in an assertion). </P> <P> As for all PCRE2 errors, a text message that describes the error can be -obtained by calling <b>pcre2_get_error_message()</b>. +obtained by calling the <b>pcre2_get_error_message()</b> function (see +"Obtaining a textual error message" +<a href="#geterrormessage">above).</a> </P> -<br><a name="SEC35" href="#TOC1">DUPLICATE SUBPATTERN NAMES</a><br> +<br><a name="SEC36" href="#TOC1">DUPLICATE SUBPATTERN NAMES</a><br> <P> <b>int pcre2_substring_nametable_scan(const pcre2_code *<i>code</i>,</b> <b> PCRE2_SPTR <i>name</i>, PCRE2_SPTR *<i>first</i>, PCRE2_SPTR *<i>last</i>);</b> @@ -2891,7 +3005,7 @@ in the section entitled <i>Information about a pattern</i>. Given all the relevant entries for the name, you can extract each of their numbers, and hence the captured data. </P> -<br><a name="SEC36" href="#TOC1">FINDING ALL POSSIBLE MATCHES AT ONE POSITION</a><br> +<br><a name="SEC37" href="#TOC1">FINDING ALL POSSIBLE MATCHES AT ONE POSITION</a><br> <P> The traditional matching function uses a similar algorithm to Perl, which stops when it finds the first match at a given point in the subject. If you want to @@ -2909,7 +3023,7 @@ substring. Then return 1, which forces <b>pcre2_match()</b> to backtrack and try other alternatives. Ultimately, when it runs out of matches, <b>pcre2_match()</b> will yield PCRE2_ERROR_NOMATCH. <a name="dfamatch"></a></P> -<br><a name="SEC37" href="#TOC1">MATCHING A PATTERN: THE ALTERNATIVE FUNCTION</a><br> +<br><a name="SEC38" href="#TOC1">MATCHING A PATTERN: THE ALTERNATIVE FUNCTION</a><br> <P> <b>int pcre2_dfa_match(const pcre2_code *<i>code</i>, PCRE2_SPTR <i>subject</i>,</b> <b> PCRE2_SIZE <i>length</i>, PCRE2_SIZE <i>startoffset</i>,</b> @@ -3104,13 +3218,13 @@ some plausibility checks are made on the contents of the workspace, which should contain data about the previous partial match. If any of these checks fail, this error is given. </P> -<br><a name="SEC38" href="#TOC1">SEE ALSO</a><br> +<br><a name="SEC39" href="#TOC1">SEE ALSO</a><br> <P> <b>pcre2build</b>(3), <b>pcre2callout</b>(3), <b>pcre2demo(3)</b>, <b>pcre2matching</b>(3), <b>pcre2partial</b>(3), <b>pcre2posix</b>(3), <b>pcre2sample</b>(3), <b>pcre2stack</b>(3), <b>pcre2unicode</b>(3). </P> -<br><a name="SEC39" href="#TOC1">AUTHOR</a><br> +<br><a name="SEC40" href="#TOC1">AUTHOR</a><br> <P> Philip Hazel <br> @@ -3119,11 +3233,11 @@ University Computing Service Cambridge, England. <br> </P> -<br><a name="SEC40" href="#TOC1">REVISION</a><br> +<br><a name="SEC41" href="#TOC1">REVISION</a><br> <P> -Last updated: 16 December 2015 +Last updated: 17 June 2016 <br> -Copyright © 1997-2015 University of Cambridge. +Copyright © 1997-2016 University of Cambridge. <br> <p> Return to the <a href="index.html">PCRE2 index page</a>. |