summaryrefslogtreecommitdiff
path: root/libs/Pcre16/docs/doc/html/pcrecompat.html
diff options
context:
space:
mode:
Diffstat (limited to 'libs/Pcre16/docs/doc/html/pcrecompat.html')
-rw-r--r--libs/Pcre16/docs/doc/html/pcrecompat.html2
1 files changed, 1 insertions, 1 deletions
diff --git a/libs/Pcre16/docs/doc/html/pcrecompat.html b/libs/Pcre16/docs/doc/html/pcrecompat.html
index 3e6226692e..d95570ef17 100644
--- a/libs/Pcre16/docs/doc/html/pcrecompat.html
+++ b/libs/Pcre16/docs/doc/html/pcrecompat.html
@@ -128,7 +128,7 @@ the pattern /^(a(b)?)+$/ in Perl leaves $2 unset, but in PCRE it is set to "b".
14. PCRE's handling of duplicate subpattern numbers and duplicate subpattern
names is not as general as Perl's. This is a consequence of the fact the PCRE
works internally just with numbers, using an external table to translate
-between numbers and names. In particular, a pattern such as (?|(?<a>A)|(?<b)B),
+between numbers and names. In particular, a pattern such as (?|(?<a>A)|(?<b>B),
where the two capturing parentheses have the same number but different names,
is not supported, and causes an error at compile time. If it were allowed, it
would not be possible to distinguish which parentheses matched, because both