summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorph10 <ph10@2f5784b3-3f2a-0410-8824-cb99058d5e15>2016-10-18 15:38:16 +0000
committerph10 <ph10@2f5784b3-3f2a-0410-8824-cb99058d5e15>2016-10-18 15:38:16 +0000
commita7227d234e6f8b936c264871a91ac3f21cfe842f (patch)
treed5107a1d4a7838546fe24369e9b6559ad7818825
parentd6d45d15235fc6f010cfb193db8fb672a152e41c (diff)
downloadpcre-a7227d234e6f8b936c264871a91ac3f21cfe842f.tar.gz
Fix typo.
git-svn-id: svn://vcs.exim.org/pcre/code/trunk@1670 2f5784b3-3f2a-0410-8824-cb99058d5e15
-rw-r--r--doc/pcrecompat.32
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/pcrecompat.3 b/doc/pcrecompat.3
index 0cc4019..6156e77 100644
--- a/doc/pcrecompat.3
+++ b/doc/pcrecompat.3
@@ -113,7 +113,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