@@ -43,38 +44,75 @@ details of the regular expressions themselves, see the documentation. For details of the PCRE library function calls and their options, see the pcreapi -and +, pcre16 -documentation. The input for pcretest is a sequence of regular expression -patterns and strings to be matched, as described below. The output shows the -result of each match. Options on the command line and the patterns control PCRE -options and exactly what is output. +and +pcre32 +documentation.
-+The input for pcretest is a sequence of regular expression patterns and +strings to be matched, as described below. The output shows the result of each +match. Options on the command line and the patterns control PCRE options and +exactly what is output. +
++As PCRE has evolved, it has acquired many different features, and as a result, +pcretest now has rather a lot of obscure options for testing every +possible feature. Some of these options are specifically designed for use in +conjunction with the test script and data files that are distributed as part of +PCRE, and are unlikely to be of use otherwise. They are all documented here, +but without much justification. +
++Input to pcretest is processed line by line, either by calling the C +library's fgets() function, or via the libreadline library (see +below). In Unix-like environments, fgets() treats any bytes other than +newline as data characters. However, in some Windows environments character 26 +(hex 1A) causes an immediate end of file, and no further data is read. For +maximum portability, therefore, it is safest to use only ASCII characters in +pcretest input files. +
+From release 8.30, two separate PCRE libraries can be built. The original one supports 8-bit character strings, whereas the newer 16-bit library supports -character strings encoded in 16-bit units. The pcretest program can be -used to test both libraries. However, it is itself still an 8-bit program, -reading 8-bit input and writing 8-bit output. When testing the 16-bit library, -the patterns and data strings are converted to 16-bit format before being -passed to the PCRE library functions. Results are converted to 8-bit for -output. +character strings encoded in 16-bit units. From release 8.32, a third library +can be built, supporting character strings encoded in 32-bit units. The +pcretest program can be used to test all three libraries. However, it is +itself still an 8-bit program, reading 8-bit input and writing 8-bit output. +When testing the 16-bit or 32-bit library, the patterns and data strings are +converted to 16- or 32-bit format before being passed to the PCRE library +functions. Results are converted to 8-bit for output.
-References to functions and structures of the form pcre[16]_xx below -mean "pcre_xx when using the 8-bit library or pcre16_xx when using -the 16-bit library". +References to functions and structures of the form pcre[16|32]_xx below +mean "pcre_xx when using the 8-bit library, pcre16_xx when using +the 16-bit library, or pcre32_xx when using the 32-bit library".
---16 -If both the 8-bit and the 16-bit libraries have been built, this option causes -the 16-bit library to be used. If only the 16-bit library has been built, this -is the default (so has no effect). If only the 8-bit library has been built, +-8 +If both the 8-bit library has been built, this option causes the 8-bit library +to be used (which is the default); if the 8-bit library has not been built, this option causes an error.
+-16 +If both the 8-bit or the 32-bit, and the 16-bit libraries have been built, this +option causes the 16-bit library to be used. If only the 16-bit library has been +built, this is the default (so has no effect). If only the 8-bit or the 32-bit +library has been built, this option causes an error. +
++-32 +If both the 8-bit or the 16-bit, and the 32-bit libraries have been built, this +option causes the 32-bit library to be used. If only the 32-bit library has been +built, this is the default (so has no effect). If only the 8-bit or the 16-bit +library has been built, this option causes an error. +
+-b Behave as if each pattern has the /B (show byte code) modifier; the internal form is output after compilation. @@ -82,27 +120,38 @@ internal form is output after compilation.
-C Output the version number of the PCRE library, and all available information -about the optional features that are included, and then exit. All other options -are ignored. +about the optional features that are included, and then exit with zero exit +code. All other options are ignored.
-C option Output information about a specific build-time option, then exit. This functionality is intended for use in scripts such as RunTest. The -following options output the value indicated: +following options output the value and set the exit code as indicated:
- linksize the internal link size (2, 3, or 4)
+ ebcdic-nl the code for LF (= NL) in an EBCDIC environment:
+ 0x15 or 0x25
+ 0 if used in an ASCII environment
+ exit code is always 0
+ linksize the configured internal link size (2, 3, or 4)
+ exit code is set to the link size
newline the default newline setting:
CR, LF, CRLF, ANYCRLF, or ANY
+ exit code is always 0
-The following options output 1 for true or zero for false:
+The following options output 1 for true or 0 for false, and set the exit code
+to the same value:
+ ebcdic compiled for an EBCDIC environment jit just-in-time support is available pcre16 the 16-bit library was built + pcre32 the 32-bit library was built pcre8 the 8-bit library was built ucp Unicode property support is available - utf UTF-8 and/or UTF-16 support is available -+ utf UTF-8 and/or UTF-16 and/or UTF-32 support + is available + +If an unknown option is given, an error message is output; the exit code is 0.
-d @@ -113,8 +162,8 @@ form and information about the compiled pattern is out
-dfa Behave as if each data line contains the \D escape sequence; this causes the -alternative matching function, pcre[16]_dfa_exec(), to be used instead of -the standard pcre[16]_exec() function (more detail is given below). +alternative matching function, pcre[16|32]_dfa_exec(), to be used instead +of the standard pcre[16|32]_exec() function (more detail is given below).
-help @@ -129,7 +178,7 @@ compiled pattern is given after compilation. -M Behave as if each data line contains the \M escape sequence; this causes PCRE to discover the minimum MATCH_LIMIT and MATCH_LIMIT_RECURSION settings by -calling pcre[16]_exec() repeatedly with different limits. +calling pcre[16|32]_exec() repeatedly with different limits.
-m @@ -140,9 +189,10 @@ bytes for both libraries.
-o osize Set the number of elements in the output vector that is used when calling -pcre[16]_exec() or pcre[16]_dfa_exec() to be osize. The +pcre[16|32]_exec() or pcre[16|32]_dfa_exec() to be osize. The default value is 45, which is enough for 14 capturing subexpressions for -pcre[16]_exec() or 22 different matches for pcre[16]_dfa_exec(). +pcre[16|32]_exec() or 22 different matches for +pcre[16|32]_dfa_exec(). The vector size can be changed for individual matching calls by including \O in the data line (see below).
@@ -165,7 +215,7 @@ megabytes. -s or -s+ Behave as if each pattern has the /S modifier; in other words, force each pattern to be studied. If -s+ is used, all the JIT compile options are -passed to pcre[16]_study(), causing just-in-time optimization to be set +passed to pcre[16|32]_study(), causing just-in-time optimization to be set up if it is available, for both full and partial matching. Specific JIT compile options can be selected by following -s+ with a digit in the range 1 to 7, which selects the JIT compile modes as follows: @@ -180,8 +230,12 @@ options can be selected by following -s+ with a If -s++ is used instead of -s+ (with or without a following digit), the text "(JIT)" is added to the first output line after a match or no match when JIT-compiled code was actually used. - -
+
+
+Note that there are pattern options that can override -s, either
+specifying no studying at all, or suppressing JIT compilation.
+
+
If the /I or /D option is present on a pattern (requesting output
about the compiled pattern), information about the result of studying is not
included when studying is caused only by -s and neither -i nor
@@ -215,7 +269,7 @@ to iterate 500000 times.
This is like -t except that it times only the matching phase, not the
compile or study phases.
If pcretest is given two filename arguments, it reads from the first and writes to the second. If it is given only one filename argument, it reads from @@ -272,23 +326,80 @@ backslash, because is interpreted as the first line of a pattern that starts with "abc/", causing pcretest to read the next line as a continuation of the regular expression.
-A pattern may be followed by any number of modifiers, which are mostly single -characters. Following Perl usage, these are referred to below as, for example, -"the /i modifier", even though the delimiter of the pattern need not -always be a slash, and no slash is used when writing modifiers. White space may -appear between the final pattern delimiter and the first modifier, and between -the modifiers themselves. +characters, though some of these can be qualified by further characters. +Following Perl usage, these are referred to below as, for example, "the +/i modifier", even though the delimiter of the pattern need not always be +a slash, and no slash is used when writing modifiers. White space may appear +between the final pattern delimiter and the first modifier, and between the +modifiers themselves. For reference, here is a complete list of modifiers. They +fall into several groups that are described in detail in the following +sections. +
+ /8 set UTF mode + /9 set PCRE_NEVER_UTF (locks out UTF mode) + /? disable UTF validity check + /+ show remainder of subject after match + /= show all captures (not just those that are set) + + /A set PCRE_ANCHORED + /B show compiled code + /C set PCRE_AUTO_CALLOUT + /D same as /B plus /I + /E set PCRE_DOLLAR_ENDONLY + /F flip byte order in compiled pattern + /f set PCRE_FIRSTLINE + /G find all matches (shorten string) + /g find all matches (use startoffset) + /I show information about pattern + /i set PCRE_CASELESS + /J set PCRE_DUPNAMES + /K show backtracking control names + /L set locale + /M show compiled memory size + /m set PCRE_MULTILINE + /N set PCRE_NO_AUTO_CAPTURE + /P use the POSIX wrapper + /S study the pattern after compilation + /s set PCRE_DOTALL + /T select character tables + /U set PCRE_UNGREEDY + /W set PCRE_UCP + /X set PCRE_EXTRA + /x set PCRE_EXTENDED + /Y set PCRE_NO_START_OPTIMIZE + /Z don't show lengths in /B output + + /<any> set PCRE_NEWLINE_ANY + /<anycrlf> set PCRE_NEWLINE_ANYCRLF + /<cr> set PCRE_NEWLINE_CR + /<crlf> set PCRE_NEWLINE_CRLF + /<lf> set PCRE_NEWLINE_LF + /<bsr_anycrlf> set PCRE_BSR_ANYCRLF + /<bsr_unicode> set PCRE_BSR_UNICODE + /<JS> set PCRE_JAVASCRIPT_COMPAT + ++
The /i, /m, /s, and /x modifiers set the PCRE_CASELESS, PCRE_MULTILINE, PCRE_DOTALL, or PCRE_EXTENDED options, respectively, when -pcre[16]_compile() is called. These four modifier letters have the same +pcre[16|32]_compile() is called. These four modifier letters have the same effect as they do in Perl. For example:
/caseless/i -+ + + +
The following table shows additional modifiers for setting PCRE compile-time options that do not correspond to anything in Perl:
@@ -298,6 +409,10 @@ options that do not correspond to anything in Perl: /8 PCRE_UTF16 ) when using the 16-bit /? PCRE_NO_UTF16_CHECK ) library + /8 PCRE_UTF32 ) when using the 32-bit + /? PCRE_NO_UTF32_CHECK ) library + + /9 PCRE_NEVER_UTF /A PCRE_ANCHORED /C PCRE_AUTO_CALLOUT /E PCRE_DOLLAR_ENDONLY @@ -308,14 +423,14 @@ options that do not correspond to anything in Perl: /W PCRE_UCP /X PCRE_EXTRA /Y PCRE_NO_START_OPTIMIZE - /<JS> PCRE_JAVASCRIPT_COMPAT + /<any> PCRE_NEWLINE_ANY + /<anycrlf> PCRE_NEWLINE_ANYCRLF /<cr> PCRE_NEWLINE_CR - /<lf> PCRE_NEWLINE_LF /<crlf> PCRE_NEWLINE_CRLF - /<anycrlf> PCRE_NEWLINE_ANYCRLF - /<any> PCRE_NEWLINE_ANY + /<lf> PCRE_NEWLINE_LF /<bsr_anycrlf> PCRE_BSR_ANYCRLF /<bsr_unicode> PCRE_BSR_UNICODE + /<JS> PCRE_JAVASCRIPT_COMPATThe modifiers that are enclosed in angle brackets are literal strings as shown, including the angle brackets, but the letters within can be in either case. @@ -323,7 +438,7 @@ This example sets multiline matching with CRLF as the
/^abc/m<CRLF>-As well as turning on the PCRE_UTF8/16 option, the /8 modifier causes +As well as turning on the PCRE_UTF8/16/32 option, the /8 modifier causes all non-printing characters in output strings to be printed using the \x{hh...} notation. Otherwise, those less than 0x100 are output in hex without the curly brackets. @@ -341,13 +456,13 @@ Searching for all possible matches within each subject by the /g or /G modifier. After finding a match, PCRE is called again to search the remainder of the subject string. The difference between /g and /G is that the former uses the startoffset argument to -pcre[16]_exec() to start searching at a new point within the entire +pcre[16|32]_exec() to start searching at a new point within the entire string (which is in effect what Perl does), whereas the latter passes over a shortened substring. This makes a difference to the matching process if the pattern begins with a lookbehind assertion (including \b or \B).
-If any call to pcre[16]_exec() in a /g or /G sequence matches +If any call to pcre[16|32]_exec() in a /g or /G sequence matches an empty string, the next call is done with the PCRE_NOTEMPTY_ATSTART and PCRE_ANCHORED flags set in order to search for another, non-empty, match at the same point. If this second match fails, the start offset is advanced, and the @@ -378,7 +493,7 @@ modifier because /S+ and /S++ have other meanings. The /= modifier requests that the values of all potential captured parentheses be output after a match. By default, only those up to the highest one actually used in the match are output (corresponding to the return code -from pcre[16]_exec()). Values in the offsets vector corresponding to +from pcre[16|32]_exec()). Values in the offsets vector corresponding to higher numbers should be set to -1, and these are output as "<unset>". This modifier gives a way of checking that this is happening.
@@ -406,16 +521,16 @@ below.The /I modifier requests that pcretest output information about the compiled pattern (whether it is anchored, has a fixed first character, and -so on). It does this by calling pcre[16]_fullinfo() after compiling a +so on). It does this by calling pcre[16|32]_fullinfo() after compiling a pattern. If the pattern is studied, the results of that are also output.
The /K modifier requests pcretest to show names from backtracking -control verbs that are returned from calls to pcre[16]_exec(). It causes -pcretest to create a pcre[16]_extra block if one has not already -been created by a call to pcre[16]_study(), and to set the +control verbs that are returned from calls to pcre[16|32]_exec(). It causes +pcretest to create a pcre[16|32]_extra block if one has not already +been created by a call to pcre[16|32]_study(), and to set the PCRE_EXTRA_MARK flag and the mark field within it, every time that -pcre[16]_exec() is called. If the variable that the mark field +pcre[16|32]_exec() is called. If the variable that the mark field points to is non-NULL for a match, non-match, or partial match, pcretest prints the string to which it points. For a match, this is shown on a line by itself, tagged with "MK:". For a non-match it is added to the message. @@ -427,8 +542,8 @@ example, /pattern/Lfr_FR For this reason, it must be the last modifier. The given locale is set, -pcre[16]_maketables() is called to build a set of character tables for -the locale, and this is then passed to pcre[16]_compile() when compiling +pcre[16|32]_maketables() is called to build a set of character tables for +the locale, and this is then passed to pcre[16|32]_compile() when compiling the regular expression. Without an /L (or /T) modifier, NULL is passed as the tables pointer; that is, /L applies only to the expression on which it appears. @@ -436,22 +551,31 @@ on which it appears.
The /M modifier causes the size in bytes of the memory block used to hold the compiled pattern to be output. This does not include the size of the -pcre[16] block; it is just the actual compiled data. If the pattern is +pcre[16|32] block; it is just the actual compiled data. If the pattern is successfully studied with the PCRE_STUDY_JIT_COMPILE option, the size of the JIT compiled code is also output.
-If the /S modifier appears once, it causes pcre[16]_study() to be -called after the expression has been compiled, and the results used when the -expression is matched. If /S appears twice, it suppresses studying, even +The /S modifier causes pcre[16|32]_study() to be called after the +expression has been compiled, and the results used when the expression is +matched. There are a number of qualifying characters that may follow /S. +They may appear in any order. +
++If S is followed by an exclamation mark, pcre[16|32]_study() is called +with the PCRE_STUDY_EXTRA_NEEDED option, causing it always to return a +pcre_extra block, even when studying discovers no useful information. +
++If /S is followed by a second S character, it suppresses studying, even if it was requested externally by the -s command line option. This makes it possible to specify that certain patterns are always studied, and others are never studied, independently of -s. This feature is used in the test files in a few cases where the output is different when the pattern is studied.
-If the /S modifier is immediately followed by a + character, the call to -pcre[16]_study() is made with all the JIT study options, requesting +If the /S modifier is followed by a + character, the call to +pcre[16|32]_study() is made with all the JIT study options, requesting just-in-time optimization support if it is available, for both normal and partial matching. If you want to restrict the JIT compiling modes, you can follow /S+ with a digit in the range 1 to 7: @@ -473,15 +597,21 @@ immediately after /S or /S+ because this
If JIT studying is successful, the compiled JIT code will automatically be used -when pcre[16]_exec() is run, except when incompatible run-time options +when pcre[16|32]_exec() is run, except when incompatible run-time options are specified. For more details, see the pcrejit documentation. See also the \J escape sequence below for a way of setting the size of the JIT stack.
+Finally, if /S is followed by a minus character, JIT compilation is +suppressed, even if it was requested externally by the -s command line +option. This makes it possible to specify that JIT is never to be used for +certain patterns. +
+The /T modifier must be followed by a single digit. It causes a specific -set of built-in character tables to be passed to pcre[16]_compile(). It +set of built-in character tables to be passed to pcre[16|32]_compile(). It is used in the standard PCRE tests to check behaviour with different character tables. The digit specifies the tables as follows:
@@ -512,9 +642,9 @@ function: The /+ modifier works as described above. All other modifiers are ignored. -The use of \x{hh...} is not dependent on the use of the /8 modifier on the pattern. It is recognized always. There may be any number of hexadecimal @@ -588,6 +718,10 @@ In UTF-16 mode, all 4-digit \x{hhhh} values are accept possible to construct invalid UTF-16 sequences for testing purposes.
DATA LINES
+
DATA LINES
-Before each data line is passed to pcre[16]_exec(), leading and trailing +Before each data line is passed to pcre[16|32]_exec(), leading and trailing white space is removed, and it is then scanned for \ escapes. Some of these are pretty esoteric features, intended for checking out some of the more complicated features of PCRE. If you are just testing "ordinary" regular @@ -531,45 +661,45 @@ recognized: \t tab (\x09) \v vertical tab (\x0b) \nnn octal character (up to 3 octal digits); always - a byte unless > 255 in UTF-8 or 16-bit mode + a byte unless > 255 in UTF-8 or 16-bit or 32-bit mode \xhh hexadecimal byte (up to 2 hex digits) \x{hh...} hexadecimal character (any number of hex digits) - \A pass the PCRE_ANCHORED option to pcre[16]_exec() or pcre[16]_dfa_exec() - \B pass the PCRE_NOTBOL option to pcre[16]_exec() or pcre[16]_dfa_exec() - \Cdd call pcre[16]_copy_substring() for substring dd after a successful match (number less than 32) - \Cname call pcre[16]_copy_named_substring() for substring "name" after a successful match (name termin- + \A pass the PCRE_ANCHORED option to pcre[16|32]_exec() or pcre[16|32]_dfa_exec() + \B pass the PCRE_NOTBOL option to pcre[16|32]_exec() or pcre[16|32]_dfa_exec() + \Cdd call pcre[16|32]_copy_substring() for substring dd after a successful match (number less than 32) + \Cname call pcre[16|32]_copy_named_substring() for substring "name" after a successful match (name termin- ated by next non alphanumeric character) \C+ show the current captured substrings at callout time \C- do not supply a callout function \C!n return 1 instead of 0 when callout number n is reached \C!n!m return 1 instead of 0 when callout number n is reached for the nth time \C*n pass the number n (may be negative) as callout data; this is used as the callout return value - \D use the pcre[16]_dfa_exec() match function - \F only shortest match for pcre[16]_dfa_exec() - \Gdd call pcre[16]_get_substring() for substring dd after a successful match (number less than 32) - \Gname call pcre[16]_get_named_substring() for substring "name" after a successful match (name termin- + \D use the pcre[16|32]_dfa_exec() match function + \F only shortest match for pcre[16|32]_dfa_exec() + \Gdd call pcre[16|32]_get_substring() for substring dd after a successful match (number less than 32) + \Gname call pcre[16|32]_get_named_substring() for substring "name" after a successful match (name termin- ated by next non-alphanumeric character) \Jdd set up a JIT stack of dd kilobytes maximum (any number of digits) - \L call pcre[16]_get_substringlist() after a successful match + \L call pcre[16|32]_get_substringlist() after a successful match \M discover the minimum MATCH_LIMIT and MATCH_LIMIT_RECURSION settings - \N pass the PCRE_NOTEMPTY option to pcre[16]_exec() or pcre[16]_dfa_exec(); if used twice, pass the + \N pass the PCRE_NOTEMPTY option to pcre[16|32]_exec() or pcre[16|32]_dfa_exec(); if used twice, pass the PCRE_NOTEMPTY_ATSTART option - \Odd set the size of the output vector passed to pcre[16]_exec() to dd (any number of digits) - \P pass the PCRE_PARTIAL_SOFT option to pcre[16]_exec() or pcre[16]_dfa_exec(); if used twice, pass the + \Odd set the size of the output vector passed to pcre[16|32]_exec() to dd (any number of digits) + \P pass the PCRE_PARTIAL_SOFT option to pcre[16|32]_exec() or pcre[16|32]_dfa_exec(); if used twice, pass the PCRE_PARTIAL_HARD option \Qdd set the PCRE_MATCH_LIMIT_RECURSION limit to dd (any number of digits) - \R pass the PCRE_DFA_RESTART option to pcre[16]_dfa_exec() + \R pass the PCRE_DFA_RESTART option to pcre[16|32]_dfa_exec() \S output details of memory get/free calls during matching - \Y pass the PCRE_NO_START_OPTIMIZE option to pcre[16]_exec() or pcre[16]_dfa_exec() - \Z pass the PCRE_NOTEOL option to pcre[16]_exec() or pcre[16]_dfa_exec() - \? pass the PCRE_NO_UTF[8|16]_CHECK option to pcre[16]_exec() or pcre[16]_dfa_exec() + \Y pass the PCRE_NO_START_OPTIMIZE option to pcre[16|32]_exec() or pcre[16|32]_dfa_exec() + \Z pass the PCRE_NOTEOL option to pcre[16|32]_exec() or pcre[16|32]_dfa_exec() + \? pass the PCRE_NO_UTF[8|16|32]_CHECK option to pcre[16|32]_exec() or pcre[16|32]_dfa_exec() \>dd start the match at offset dd (optional "-"; then any number of digits); this sets the startoffset - argument for pcre[16]_exec() or pcre[16]_dfa_exec() - \<cr> pass the PCRE_NEWLINE_CR option to pcre[16]_exec() or pcre[16]_dfa_exec() - \<lf> pass the PCRE_NEWLINE_LF option to pcre[16]_exec() or pcre[16]_dfa_exec() - \<crlf> pass the PCRE_NEWLINE_CRLF option to pcre[16]_exec() or pcre[16]_dfa_exec() - \<anycrlf> pass the PCRE_NEWLINE_ANYCRLF option to pcre[16]_exec() or pcre[16]_dfa_exec() - \<any> pass the PCRE_NEWLINE_ANY option to pcre[16]_exec() or pcre[16]_dfa_exec() + argument for pcre[16|32]_exec() or pcre[16|32]_dfa_exec() + \<cr> pass the PCRE_NEWLINE_CR option to pcre[16|32]_exec() or pcre[16|32]_dfa_exec() + \<lf> pass the PCRE_NEWLINE_LF option to pcre[16|32]_exec() or pcre[16|32]_dfa_exec() + \<crlf> pass the PCRE_NEWLINE_CRLF option to pcre[16|32]_exec() or pcre[16|32]_dfa_exec() + \<anycrlf> pass the PCRE_NEWLINE_ANYCRLF option to pcre[16|32]_exec() or pcre[16|32]_dfa_exec() + \<any> pass the PCRE_NEWLINE_ANY option to pcre[16|32]_exec() or pcre[16|32]_dfa_exec()
+In UTF-32 mode, all 4- to 8-digit \x{...} values are accepted. This makes it +possible to construct invalid UTF-32 sequences for testing purposes. +
+The escapes that specify line ending sequences are literal strings, exactly as shown. No more than one newline setting should be present in any data line.
@@ -604,12 +738,12 @@ is not being used. Providing a stack that is larger th necessary only for very complicated patterns.-If \M is present, pcretest calls pcre[16]_exec() several times, +If \M is present, pcretest calls pcre[16|32]_exec() several times, with different values in the match_limit and match_limit_recursion -fields of the pcre[16]_extra data structure, until it finds the minimum -numbers for each parameter that allow pcre[16]_exec() to complete without +fields of the pcre[16|32]_extra data structure, until it finds the minimum +numbers for each parameter that allow pcre[16|32]_exec() to complete without error. Because this is testing a specific feature of the normal interpretive -pcre[16]_exec() execution, the use of any JIT optimization that might +pcre[16|32]_exec() execution, the use of any JIT optimization that might have been set up by the /S+ qualifier of -s+ option is disabled.
@@ -624,7 +758,7 @@ needed to complete the match attempt.
When \O is used, the value specified may be higher or lower than the size set by the -O command line option (or defaulted to 45); \O applies only to -the call of pcre[16]_exec() for the line in which it appears. +the call of pcre[16|32]_exec() for the line in which it appears.
If the /P modifier was present on the pattern, causing the POSIX wrapper @@ -632,11 +766,11 @@ API to be used, the only option-setting sequences that \N, and \Z, causing REG_NOTBOL, REG_NOTEMPTY, and REG_NOTEOL, respectively, to be passed to regexec().
-By default, pcretest uses the standard PCRE matching function, -pcre[16]_exec() to match each data line. PCRE also supports an -alternative matching function, pcre[16]_dfa_test(), which operates in a +pcre[16|32]_exec() to match each data line. PCRE also supports an +alternative matching function, pcre[16|32]_dfa_test(), which operates in a different way, and has some restrictions. The differences between the two functions are described in the pcrematching @@ -649,17 +783,17 @@ This function finds all possible matches at a given po escape sequence is present in the data line, it stops after the first match is found. This is always the shortest possible match.
-This section describes the output when the normal matching function, -pcre[16]_exec(), is being used. +pcre[16|32]_exec(), is being used.
When a match succeeds, pcretest outputs the list of captured substrings -that pcre[16]_exec() returns, starting with number 0 for the string that +that pcre[16|32]_exec() returns, starting with number 0 for the string that matched the whole pattern. Otherwise, it outputs "No match" when the return is PCRE_ERROR_NOMATCH, and "Partial match:" followed by the partially matching -substring when pcre[16]_exec() returns PCRE_ERROR_PARTIAL. (Note that +substring when pcre[16|32]_exec() returns PCRE_ERROR_PARTIAL. (Note that this is the entire substring that was inspected during the partial match; it may include characters before the actual match start if a lookbehind assertion, \K, \b, or \B was involved.) For any other return, pcretest outputs @@ -679,7 +813,7 @@ at least two. Here is an example of an interactive No match Unset capturing substrings that are not followed by one that is set are not -returned by pcre[16]_exec(), and are not shown by pcretest. In the +returned by pcre[16|32]_exec(), and are not shown by pcretest. In the following example, there are two capturing substrings, but when the first data line is matched, the second, unset substring is not shown. An "internal" unset substring is shown as "<unset>", as for the second data line. @@ -740,9 +874,9 @@ prompt is used for continuations), data lines may not. included in data by means of the \n escape (or \r, \r\n, etc., depending on the newline sequence setting).
--When the alternative matching function, pcre[16]_dfa_exec(), is used (by +When the alternative matching function, pcre[16|32]_dfa_exec(), is used (by means of the \D escape sequence or the -dfa command line option), the output consists of a list of all the matches that start at the first point in the subject where there is at least one match. For example: @@ -776,7 +910,7 @@ at the end of the longest match. For example: Since the matching function does not support substring capture, the escape sequences that are concerned with captured substrings are not relevant.
-When the alternative matching function has given the PCRE_ERROR_PARTIAL return, indicating that the subject partially matched the pattern, you can restart the @@ -793,7 +927,7 @@ For further information about partial matching, see th pcrepartial documentation.
-If the pattern contains any callout requests, pcretest's callout function is called during matching. This works with both matching functions. By default, @@ -854,7 +988,7 @@ the pcrecallout documentation.
-When pcretest is outputting text in the compiled version of a pattern, bytes other than 32-126 are always treated as non-printing characters are are @@ -866,7 +1000,7 @@ string, it behaves in the same way, unless a different the pattern (using the /L modifier). In this case, the isprint() function to distinguish printing and non-printing characters.
-The facilities described in this section are not available when the POSIX interface to PCRE is being used, that is, when the /P pattern modifier is @@ -939,13 +1073,14 @@ string using a reloaded pattern is likely to cause Finally, if you attempt to load a file that is not in the correct format, the result is undefined.
--pcre(3), pcre16(3), pcreapi(3), pcrecallout(3), +pcre(3), pcre16(3), pcre32(3), pcreapi(3), +pcrecallout(3), pcrejit, pcrematching(3), pcrepartial(d), pcrepattern(3), pcreprecompile(3).
-
Philip Hazel
@@ -954,11 +1089,11 @@ University Computing Service
Cambridge CB2 3QH, England.
-Last updated: 21 February 2012
+Last updated: 26 April 2013
-Copyright © 1997-2012 University of Cambridge.
+Copyright © 1997-2013 University of Cambridge.
Return to the PCRE index page.