summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorph10 <ph10@2f5784b3-3f2a-0410-8824-cb99058d5e15>2007-11-19 10:09:04 +0000
committerph10 <ph10@2f5784b3-3f2a-0410-8824-cb99058d5e15>2007-11-19 10:09:04 +0000
commitef30a350f473bbc9dc5a115843b3da0d4c760253 (patch)
treebb73152b8b7c959cbc6a9fe14296f4f7be36f0db
parent0e5661b91ca6b911345a010516d404eb658cd516 (diff)
downloadpcre-ef30a350f473bbc9dc5a115843b3da0d4c760253.tar.gz
Update pcretest doc to clarify the output for unset substrings.
git-svn-id: svn://vcs.exim.org/pcre/code/trunk@273 2f5784b3-3f2a-0410-8824-cb99058d5e15
-rw-r--r--doc/pcretest.117
1 files changed, 16 insertions, 1 deletions
diff --git a/doc/pcretest.1 b/doc/pcretest.1
index 63248b6..4715401 100644
--- a/doc/pcretest.1
+++ b/doc/pcretest.1
@@ -463,6 +463,21 @@ of an interactive \fBpcretest\fP run.
data> xyz
No match
.sp
+Note that unset capturing substrings that are not followed by one that is set
+are not returned by \fBpcre_exec()\fP, and are not shown by \fBpcretest\fP. 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.
+.sp
+ re> /(a)|(b)/
+ data> a
+ 0: a
+ 1: a
+ data> b
+ 0: b
+ 1: <unset>
+ 2: b
+.sp
If the strings contain any non-printing characters, they are output as \e0x
escapes, or as \ex{...} escapes if the \fB/8\fP modifier was present on the
pattern. See below for the definition of non-printing characters. If the
@@ -696,6 +711,6 @@ Cambridge CB2 3QH, England.
.rs
.sp
.nf
-Last updated: 11 September 2007
+Last updated: 19 November 2007
Copyright (c) 1997-2007 University of Cambridge.
.fi