/[pcre]/code/trunk/doc/pcretest.1
ViewVC logotype

Diff of /code/trunk/doc/pcretest.1

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 273 by ph10, Mon Nov 19 10:09:04 2007 UTC revision 287 by ph10, Tue Dec 18 20:11:28 2007 UTC
# Line 97  that file and writes to stdout. Otherwis Line 97  that file and writes to stdout. Otherwis
97  stdout, and prompts for each line of input, using "re>" to prompt for regular  stdout, and prompts for each line of input, using "re>" to prompt for regular
98  expressions, and "data>" to prompt for data lines.  expressions, and "data>" to prompt for data lines.
99  .P  .P
100    When \fBpcretest\fP is built, a configuration option can specify that it should
101    be linked with the \fBlibreadline\fP library. When this is done, if the input
102    is from a terminal, it is read using the \fBreadline()\fP function. This
103    provides line-editing and history facilities. The output from the \fB-help\fP
104    option states whether or not \fBreadline()\fP will be used.
105    .P
106  The program handles any number of sets of input on a single input file. Each  The program handles any number of sets of input on a single input file. Each
107  set starts with a regular expression, and continues with any number of data  set starts with a regular expression, and continues with any number of data
108  lines to be matched against the pattern.  lines to be matched against the pattern.
# Line 463  of an interactive \fBpcretest\fP run. Line 469  of an interactive \fBpcretest\fP run.
469    data> xyz    data> xyz
470    No match    No match
471  .sp  .sp
472  Note that unset capturing substrings that are not followed by one that is set  Note that unset capturing substrings that are not followed by one that is set
473  are not returned by \fBpcre_exec()\fP, and are not shown by \fBpcretest\fP. In  are not returned by \fBpcre_exec()\fP, and are not shown by \fBpcretest\fP. In
474  the following example, there are two capturing substrings, but when the first  the following example, there are two capturing substrings, but when the first
475  data line is matched, the second, unset substring is not shown. An "internal"  data line is matched, the second, unset substring is not shown. An "internal"
476  unset substring is shown as "<unset>", as for the second data line.  unset substring is shown as "<unset>", as for the second data line.
477  .sp  .sp
478      re> /(a)|(b)/      re> /(a)|(b)/
# Line 476  unset substring is shown as "", a Line 482  unset substring is shown as "", a
482    data> b    data> b
483     0: b     0: b
484     1: <unset>     1: <unset>
485     2: b     2: b
486  .sp  .sp
487  If the strings contain any non-printing characters, they are output as \e0x  If the strings contain any non-printing characters, they are output as \e0x
488  escapes, or as \ex{...} escapes if the \fB/8\fP modifier was present on the  escapes, or as \ex{...} escapes if the \fB/8\fP modifier was present on the
# Line 711  Cambridge CB2 3QH, England. Line 717  Cambridge CB2 3QH, England.
717  .rs  .rs
718  .sp  .sp
719  .nf  .nf
720  Last updated: 19 November 2007  Last updated: 18 December 2007
721  Copyright (c) 1997-2007 University of Cambridge.  Copyright (c) 1997-2007 University of Cambridge.
722  .fi  .fi

Legend:
Removed from v.273  
changed lines
  Added in v.287

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12