Gecko [ www.thearyasamaj.org ]

Name	Size	Permission
NON-AUTOTOOLS-BUILD.txt	17.35 KB	-rw-r--r--
README.txt	40.99 KB	-rw-r--r--
index.html	13.38 KB	-rw-r--r--
pcre2-config.html	3.42 KB	-rw-r--r--
pcre2.html	9.35 KB	-rw-r--r--
pcre2_callout_enumerate.html	2.37 KB	-rw-r--r--
pcre2_code_copy.html	1.34 KB	-rw-r--r--
pcre2_code_copy_with_tables.ht...	1.46 KB	-rw-r--r--
pcre2_code_free.html	1.21 KB	-rw-r--r--
pcre2_compile.html	4.22 KB	-rw-r--r--
pcre2_compile_context_copy.htm...	1.15 KB	-rw-r--r--
pcre2_compile_context_create.h...	1.24 KB	-rw-r--r--
pcre2_compile_context_free.htm...	1.2 KB	-rw-r--r--
pcre2_config.html	3.49 KB	-rw-r--r--
pcre2_convert_context_copy.htm...	1.13 KB	-rw-r--r--
pcre2_convert_context_create.h...	1.22 KB	-rw-r--r--
pcre2_convert_context_free.htm...	1.19 KB	-rw-r--r--
pcre2_converted_pattern_free.h...	1.22 KB	-rw-r--r--
pcre2_dfa_match.html	3.42 KB	-rw-r--r--
pcre2_general_context_copy.htm...	1.2 KB	-rw-r--r--
pcre2_general_context_create.h...	1.45 KB	-rw-r--r--
pcre2_general_context_free.htm...	1.14 KB	-rw-r--r--
pcre2_get_error_message.html	1.7 KB	-rw-r--r--
pcre2_get_mark.html	1.47 KB	-rw-r--r--
pcre2_get_ovector_count.html	1.05 KB	-rw-r--r--
pcre2_get_ovector_pointer.html	1.12 KB	-rw-r--r--
pcre2_get_startchar.html	1.4 KB	-rw-r--r--
pcre2_jit_compile.html	1.8 KB	-rw-r--r--
pcre2_jit_free_unused_memory.h...	1.3 KB	-rw-r--r--
pcre2_jit_match.html	1.99 KB	-rw-r--r--
pcre2_jit_stack_assign.html	2.5 KB	-rw-r--r--
pcre2_jit_stack_create.html	1.68 KB	-rw-r--r--
pcre2_jit_stack_free.html	1.19 KB	-rw-r--r--
pcre2_maketables.html	1.61 KB	-rw-r--r--
pcre2_match.html	3.49 KB	-rw-r--r--
pcre2_match_context_copy.html	1.14 KB	-rw-r--r--
pcre2_match_context_create.htm...	1.23 KB	-rw-r--r--
pcre2_match_context_free.html	1.19 KB	-rw-r--r--
pcre2_match_data_create.html	1.58 KB	-rw-r--r--
pcre2_match_data_create_from_p...	1.7 KB	-rw-r--r--
pcre2_match_data_free.html	1.21 KB	-rw-r--r--
pcre2_pattern_convert.html	2.6 KB	-rw-r--r--
pcre2_pattern_info.html	4.69 KB	-rw-r--r--
pcre2_serialize_decode.html	2.49 KB	-rw-r--r--
pcre2_serialize_encode.html	2.66 KB	-rw-r--r--
pcre2_serialize_free.html	1.16 KB	-rw-r--r--
pcre2_serialize_get_number_of_...	1.6 KB	-rw-r--r--
pcre2_set_bsr.html	1.17 KB	-rw-r--r--
pcre2_set_callout.html	1.25 KB	-rw-r--r--
pcre2_set_character_tables.htm...	1.21 KB	-rw-r--r--
pcre2_set_compile_extra_option...	1.48 KB	-rw-r--r--
pcre2_set_compile_recursion_gu...	1.63 KB	-rw-r--r--
pcre2_set_depth_limit.html	1.05 KB	-rw-r--r--
pcre2_set_glob_escape.html	1.33 KB	-rw-r--r--
pcre2_set_glob_separator.html	1.3 KB	-rw-r--r--
pcre2_set_heap_limit.html	1.05 KB	-rw-r--r--
pcre2_set_match_limit.html	1.04 KB	-rw-r--r--
pcre2_set_max_pattern_length.h...	1.3 KB	-rw-r--r--
pcre2_set_newline.html	1.53 KB	-rw-r--r--
pcre2_set_offset_limit.html	1.05 KB	-rw-r--r--
pcre2_set_parens_nest_limit.ht...	1.1 KB	-rw-r--r--
pcre2_set_recursion_limit.html	1.07 KB	-rw-r--r--
pcre2_set_recursion_memory_man...	1.22 KB	-rw-r--r--
pcre2_substitute.html	3.99 KB	-rw-r--r--
pcre2_substring_copy_byname.ht...	2.01 KB	-rw-r--r--
pcre2_substring_copy_bynumber....	1.82 KB	-rw-r--r--
pcre2_substring_free.html	1.17 KB	-rw-r--r--
pcre2_substring_get_byname.htm...	2.14 KB	-rw-r--r--
pcre2_substring_get_bynumber.h...	1.98 KB	-rw-r--r--
pcre2_substring_length_byname....	1.33 KB	-rw-r--r--
pcre2_substring_length_bynumbe...	1.48 KB	-rw-r--r--
pcre2_substring_list_free.html	1.18 KB	-rw-r--r--
pcre2_substring_list_get.html	2.09 KB	-rw-r--r--
pcre2_substring_nametable_scan...	1.8 KB	-rw-r--r--
pcre2_substring_number_from_na...	1.61 KB	-rw-r--r--
pcre2api.html	167.89 KB	-rw-r--r--
pcre2build.html	24.21 KB	-rw-r--r--
pcre2callout.html	19.59 KB	-rw-r--r--
pcre2compat.html	10.06 KB	-rw-r--r--
pcre2convert.html	7.7 KB	-rw-r--r--
pcre2demo.html	19.69 KB	-rw-r--r--
pcre2grep.html	46.98 KB	-rw-r--r--
pcre2jit.html	19.57 KB	-rw-r--r--
pcre2limits.html	3.18 KB	-rw-r--r--
pcre2matching.html	10.61 KB	-rw-r--r--
pcre2partial.html	20.34 KB	-rw-r--r--
pcre2pattern.html	152.23 KB	-rw-r--r--
pcre2perform.html	11.57 KB	-rw-r--r--
pcre2posix.html	14.16 KB	-rw-r--r--
pcre2sample.html	3.81 KB	-rw-r--r--
pcre2serialize.html	9.85 KB	-rw-r--r--
pcre2syntax.html	20 KB	-rw-r--r--
pcre2test.html	85.01 KB	-rw-r--r--
pcre2unicode.html	11.87 KB	-rw-r--r--

Code Editor : pcre2matching.html

<html>
<head>
<title>pcre2matching specification</title>
</head>
<body bgcolor="#FFFFFF" text="#00005A" link="#0066FF" alink="#3399FF" vlink="#2222BB">
<h1>pcre2matching man page</h1>

Return to the <a href="index.html">PCRE2 index page</a>.


This page is part of the PCRE2 HTML documentation. It was generated
automatically from the original man page. If there is any nonsense in it,
please consult the man page, in case the conversion went wrong.
 
<ul>
<li><a name="TOC1" href="#SEC1">PCRE2 MATCHING ALGORITHMS</a>
<li><a name="TOC2" href="#SEC2">REGULAR EXPRESSIONS AS TREES</a>
<li><a name="TOC3" href="#SEC3">THE STANDARD MATCHING ALGORITHM</a>
<li><a name="TOC4" href="#SEC4">THE ALTERNATIVE MATCHING ALGORITHM</a>
<li><a name="TOC5" href="#SEC5">ADVANTAGES OF THE ALTERNATIVE ALGORITHM</a>
<li><a name="TOC6" href="#SEC6">DISADVANTAGES OF THE ALTERNATIVE ALGORITHM</a>
<li><a name="TOC7" href="#SEC7">AUTHOR</a>
<li><a name="TOC8" href="#SEC8">REVISION</a>
</ul>
 <a name="SEC1" href="#TOC1">PCRE2 MATCHING ALGORITHMS</a> 

This document describes the two different algorithms that are available in
PCRE2 for matching a compiled regular expression against a given subject
string. The "standard" algorithm is the one provided by the pcre2_match()
function. This works in the same as as Perl's matching function, and provide a
Perl-compatible matching operation. The just-in-time (JIT) optimization that is
described in the
<a href="pcre2jit.html">pcre2jit</a>
documentation is compatible with this function.


An alternative algorithm is provided by the pcre2_dfa_match() function;
it operates in a different way, and is not Perl-compatible. This alternative
has advantages and disadvantages compared with the standard algorithm, and
these are described below.


When there is only one possible way in which a given subject string can match a
pattern, the two algorithms give the same answer. A difference arises, however,
when there are multiple possibilities. For example, if the pattern
<pre>
 ^&#60;.*&#62;
</pre>
is matched against the string
<pre>
 &#60;something&#62; &#60;something else&#62; &#60;something further&#62;
</pre>
there are three possible answers. The standard algorithm finds only one of
them, whereas the alternative algorithm finds all three.

 <a name="SEC2" href="#TOC1">REGULAR EXPRESSIONS AS TREES</a> 

The set of strings that are matched by a regular expression can be represented
as a tree structure. An unlimited repetition in the pattern makes the tree of
infinite size, but it is still a tree. Matching the pattern to a given subject
string (from a given starting point) can be thought of as a search of the tree.
There are two ways to search a tree: depth-first and breadth-first, and these
correspond to the two matching algorithms provided by PCRE2.

 <a name="SEC3" href="#TOC1">THE STANDARD MATCHING ALGORITHM</a> 

In the terminology of Jeffrey Friedl's book "Mastering Regular Expressions",
the standard algorithm is an "NFA algorithm". It conducts a depth-first search
of the pattern tree. That is, it proceeds along a single path through the tree,
checking that the subject matches what is required. When there is a mismatch,
the algorithm tries any alternatives at the current point, and if they all
fail, it backs up to the previous branch point in the tree, and tries the next
alternative branch at that level. This often involves backing up (moving to the
left) in the subject string as well. The order in which repetition branches are
tried is controlled by the greedy or ungreedy nature of the quantifier.


If a leaf node is reached, a matching string has been found, and at that point
the algorithm stops. Thus, if there is more than one possible match, this
algorithm returns the first one that it finds. Whether this is the shortest,
the longest, or some intermediate length depends on the way the greedy and
ungreedy repetition quantifiers are specified in the pattern.


Because it ends up with a single path through the tree, it is relatively
straightforward for this algorithm to keep track of the substrings that are
matched by portions of the pattern in parentheses. This provides support for
capturing parentheses and backreferences.

 <a name="SEC4" href="#TOC1">THE ALTERNATIVE MATCHING ALGORITHM</a> 

This algorithm conducts a breadth-first search of the tree. Starting from the
first matching point in the subject, it scans the subject string from left to
right, once, character by character, and as it does this, it remembers all the
paths through the tree that represent valid matches. In Friedl's terminology,
this is a kind of "DFA algorithm", though it is not implemented as a
traditional finite state machine (it keeps multiple states active
simultaneously).


Although the general principle of this matching algorithm is that it scans the
subject string only once, without backtracking, there is one exception: when a
lookaround assertion is encountered, the characters following or preceding the
current point have to be independently inspected.


The scan continues until either the end of the subject is reached, or there are
no more unterminated paths. At this point, terminated paths represent the
different matching possibilities (if there are none, the match has failed).
Thus, if there is more than one possible match, this algorithm finds all of
them, and in particular, it finds the longest. The matches are returned in
decreasing order of length. There is an option to stop the algorithm after the
first match (which is necessarily the shortest) is found.


Note that all the matches that are found start at the same point in the
subject. If the pattern
<pre>
 cat(er(pillar)?)?
</pre>
is matched against the string "the caterpillar catchment", the result is the
three strings "caterpillar", "cater", and "cat" that start at the fifth
character of the subject. The algorithm does not automatically move on to find
matches that start at later positions.


PCRE2's "auto-possessification" optimization usually applies to character
repeats at the end of a pattern (as well as internally). For example, the
pattern "a\d+" is compiled as if it were "a\d++" because there is no point
even considering the possibility of backtracking into the repeated digits. For
DFA matching, this means that only one possible match is found. If you really
do want multiple matches in such cases, either use an ungreedy repeat
("a\d+?") or set the PCRE2_NO_AUTO_POSSESS option when compiling.


There are a number of features of PCRE2 regular expressions that are not
supported by the alternative matching algorithm. They are as follows:


1. Because the algorithm finds all possible matches, the greedy or ungreedy
nature of repetition quantifiers is not relevant (though it may affect
auto-possessification, as just described). During matching, greedy and ungreedy
quantifiers are treated in exactly the same way. However, possessive
quantifiers can make a difference when what follows could also match what is
quantified, for example in a pattern like this:
<pre>
 ^a++\w!
</pre>
This pattern matches "aaab!" but not "aaa!", which would be matched by a
non-possessive quantifier. Similarly, if an atomic group is present, it is
matched as if it were a standalone pattern at the current point, and the
longest match is then "locked in" for the rest of the overall pattern.


2. When dealing with multiple paths through the tree simultaneously, it is not
straightforward to keep track of captured substrings for the different matching
possibilities, and PCRE2's implementation of this algorithm does not attempt to
do this. This means that no captured substrings are available.


3. Because no substrings are captured, backreferences within the pattern are
not supported, and cause errors if encountered.


4. For the same reason, conditional expressions that use a backreference as the
condition or test for a specific group recursion are not supported.


5. Because many paths through the tree may be active, the \K escape sequence,
which resets the start of the match when encountered (but may be on some paths
and not on others), is not supported. It causes an error if encountered.


6. Callouts are supported, but the value of the capture_top field is
always 1, and the value of the capture_last field is always 0.


7. The \C escape sequence, which (in the standard algorithm) always matches a
single code unit, even in a UTF mode, is not supported in these modes, because
the alternative algorithm moves through the subject string one character (not
code unit) at a time, for all active paths through the tree.


8. Except for (*FAIL), the backtracking control verbs such as (*PRUNE) are not
supported. (*FAIL) is supported, and behaves like a failing negative assertion.

 <a name="SEC5" href="#TOC1">ADVANTAGES OF THE ALTERNATIVE ALGORITHM</a> 

Using the alternative matching algorithm provides the following advantages:


1. All possible matches (at a single point in the subject) are automatically
found, and in particular, the longest match is found. To find more than one
match using the standard algorithm, you have to do kludgy things with
callouts.


2. Because the alternative algorithm scans the subject string just once, and
never needs to backtrack (except for lookbehinds), it is possible to pass very
long subject strings to the matching function in several pieces, checking for
partial matching each time. Although it is also possible to do multi-segment
matching using the standard algorithm, by retaining partially matched
substrings, it is more complicated. The
<a href="pcre2partial.html">pcre2partial</a>
documentation gives details of partial matching and discusses multi-segment
matching.

 <a name="SEC6" href="#TOC1">DISADVANTAGES OF THE ALTERNATIVE ALGORITHM</a> 

The alternative algorithm suffers from a number of disadvantages:


1. It is substantially slower than the standard algorithm. This is partly
because it has to search for all possible matches, but is also because it is
less susceptible to optimization.


2. Capturing parentheses and backreferences are not supported.


3. Although atomic groups are supported, their use does not provide the
performance advantage that it does for the standard algorithm.

 <a name="SEC7" href="#TOC1">AUTHOR</a> 

Philip Hazel
 
University Computing Service
 
Cambridge, England.
 

 <a name="SEC8" href="#TOC1">REVISION</a> 

Last updated: 29 September 2014
 
Copyright &copy; 1997-2014 University of Cambridge.
 

Return to the <a href="index.html">PCRE2 index page</a>.

${this.title}

Code Editor : pcre2matching.html