/[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 75 by nigel, Sat Feb 24 21:40:37 2007 UTC revision 227 by ph10, Tue Aug 21 15:00:15 2007 UTC
# Line 4  pcretest - a program for testing Perl-co Line 4  pcretest - a program for testing Perl-co
4  .SH SYNOPSIS  .SH SYNOPSIS
5  .rs  .rs
6  .sp  .sp
7  .B pcretest "[-C] [-d] [-i] [-m] [-o osize] [-p] [-t] [source]"  .B pcretest "[options] [source] [destination]"
8  .ti +5n  .sp
 .B "[destination]"  
 .P  
9  \fBpcretest\fP was written as a test program for the PCRE regular expression  \fBpcretest\fP was written as a test program for the PCRE regular expression
10  library itself, but it can also be used for experimenting with regular  library itself, but it can also be used for experimenting with regular
11  expressions. This document describes the features of the test program; for  expressions. This document describes the features of the test program; for
# Line 26  documentation. Line 24  documentation.
24  .SH OPTIONS  .SH OPTIONS
25  .rs  .rs
26  .TP 10  .TP 10
27    \fB-b\fP
28    Behave as if each regex has the \fB/B\fP (show bytecode) modifier; the internal
29    form is output after compilation.
30    .TP 10
31  \fB-C\fP  \fB-C\fP
32  Output the version number of the PCRE library, and all available information  Output the version number of the PCRE library, and all available information
33  about the optional features that are included, and then exit.  about the optional features that are included, and then exit.
34  .TP 10  .TP 10
35  \fB-d\fP  \fB-d\fP
36  Behave as if each regex had the \fB/D\fP (debug) modifier; the internal  Behave as if each regex has the \fB/D\fP (debug) modifier; the internal
37  form is output after compilation.  form and information about the compiled pattern is output after compilation;
38    \fB-d\fP is equivalent to \fB-b -i\fP.
39    .TP 10
40    \fB-dfa\fP
41    Behave as if each data line contains the \eD escape sequence; this causes the
42    alternative matching function, \fBpcre_dfa_exec()\fP, to be used instead of the
43    standard \fBpcre_exec()\fP function (more detail is given below).
44    .TP 10
45    \fB-help\fP
46    Output a brief summary these options and then exit.
47  .TP 10  .TP 10
48  \fB-i\fP  \fB-i\fP
49  Behave as if each regex had the \fB/I\fP modifier; information about the  Behave as if each regex has the \fB/I\fP modifier; information about the
50  compiled pattern is given after compilation.  compiled pattern is given after compilation.
51  .TP 10  .TP 10
52  \fB-m\fP  \fB-m\fP
# Line 45  with earlier versions of pcretest, \fB-s Line 56  with earlier versions of pcretest, \fB-s
56  .TP 10  .TP 10
57  \fB-o\fP \fIosize\fP  \fB-o\fP \fIosize\fP
58  Set the number of elements in the output vector that is used when calling  Set the number of elements in the output vector that is used when calling
59  \fBpcre_exec()\fP to be \fIosize\fP. The default value is 45, which is enough  \fBpcre_exec()\fP or \fBpcre_dfa_exec()\fP to be \fIosize\fP. The default value
60  for 14 capturing subexpressions. The vector size can be changed for individual  is 45, which is enough for 14 capturing subexpressions for \fBpcre_exec()\fP or
61  matching calls by including \eO in the data line (see below).  22 different matches for \fBpcre_dfa_exec()\fP. The vector size can be
62    changed for individual matching calls by including \eO in the data line (see
63    below).
64  .TP 10  .TP 10
65  \fB-p\fP  \fB-p\fP
66  Behave as if each regex has \fB/P\fP modifier; the POSIX wrapper API is used  Behave as if each regex has the \fB/P\fP modifier; the POSIX wrapper API is
67  to call PCRE. None of the other options has any effect when \fB-p\fP is set.  used to call PCRE. None of the other options has any effect when \fB-p\fP is
68    set.
69    .TP 10
70    \fB-q\fP
71    Do not output the version number of \fBpcretest\fP at the start of execution.
72    .TP 10
73    \fB-S\fP \fIsize\fP
74    On Unix-like systems, set the size of the runtime stack to \fIsize\fP
75    megabytes.
76  .TP 10  .TP 10
77  \fB-t\fP  \fB-t\fP
78  Run each compile, study, and match many times with a timer, and output  Run each compile, study, and match many times with a timer, and output
79  resulting time per compile or match (in milliseconds). Do not set \fB-m\fP with  resulting time per compile or match (in milliseconds). Do not set \fB-m\fP with
80  \fB-t\fP, because you will then get the size output a zillion times, and the  \fB-t\fP, because you will then get the size output a zillion times, and the
81  timing will be distorted.  timing will be distorted. You can control the number of iterations that are
82    used for timing by following \fB-t\fP with a number (as a separate item on the
83    command line). For example, "-t 1000" would iterate 1000 times. The default is
84    to iterate 500000 times.
85    .TP 10
86    \fB-tm\fP
87    This is like \fB-t\fP except that it times only the matching phase, not the
88    compile or study phases.
89  .  .
90  .  .
91  .SH DESCRIPTION  .SH DESCRIPTION
# Line 74  set starts with a regular expression, an Line 102  set starts with a regular expression, an
102  lines to be matched against the pattern.  lines to be matched against the pattern.
103  .P  .P
104  Each data line is matched separately and independently. If you want to do  Each data line is matched separately and independently. If you want to do
105  multiple-line matches, you have to use the \en escape sequence in a single line  multi-line matches, you have to use the \en escape sequence (or \er or \er\en,
106  of input to encode the newline characters. The maximum length of data line is  etc., depending on the newline setting) in a single line of input to encode the
107  30,000 characters.  newline sequences. There is no limit on the length of data lines; the input
108    buffer is automatically extended if it is too small.
109  .P  .P
110  An empty line signals the end of the data lines, at which point a new regular  An empty line signals the end of the data lines, at which point a new regular
111  expression is read. The regular expressions are given enclosed in any  expression is read. The regular expressions are given enclosed in any
112  non-alphanumeric delimiters other than backslash, for example  non-alphanumeric delimiters other than backslash, for example:
113  .sp  .sp
114    /(a|bc)x+yz/    /(a|bc)x+yz/
115  .sp  .sp
# Line 128  effect as they do in Perl. For example: Line 157  effect as they do in Perl. For example:
157  The following table shows additional modifiers for setting PCRE options that do  The following table shows additional modifiers for setting PCRE options that do
158  not correspond to anything in Perl:  not correspond to anything in Perl:
159  .sp  .sp
160    \fB/A\fP    PCRE_ANCHORED    \fB/A\fP          PCRE_ANCHORED
161    \fB/C\fP    PCRE_AUTO_CALLOUT    \fB/C\fP          PCRE_AUTO_CALLOUT
162    \fB/E\fP    PCRE_DOLLAR_ENDONLY    \fB/E\fP          PCRE_DOLLAR_ENDONLY
163    \fB/N\fP    PCRE_NO_AUTO_CAPTURE    \fB/f\fP          PCRE_FIRSTLINE
164    \fB/U\fP    PCRE_UNGREEDY    \fB/J\fP          PCRE_DUPNAMES
165    \fB/X\fP    PCRE_EXTRA    \fB/N\fP          PCRE_NO_AUTO_CAPTURE
166      \fB/U\fP          PCRE_UNGREEDY
167      \fB/X\fP          PCRE_EXTRA
168      \fB/<cr>\fP       PCRE_NEWLINE_CR
169      \fB/<lf>\fP       PCRE_NEWLINE_LF
170      \fB/<crlf>\fP     PCRE_NEWLINE_CRLF
171      \fB/<anycrlf>\fP  PCRE_NEWLINE_ANYCRLF
172      \fB/<any>\fP      PCRE_NEWLINE_ANY
173    .sp
174    Those specifying line ending sequences are literal strings as shown, but the
175    letters can be in either case. This example sets multiline matching with CRLF
176    as the line ending sequence:
177    .sp
178      /^abc/m<crlf>
179    .sp
180    Details of the meanings of these PCRE options are given in the
181    .\" HREF
182    \fBpcreapi\fP
183    .\"
184    documentation.
185    .
186    .
187    .SS "Finding all matches in a string"
188    .rs
189  .sp  .sp
190  Searching for all possible matches within each subject string can be requested  Searching for all possible matches within each subject string can be requested
191  by the \fB/g\fP or \fB/G\fP modifier. After finding a match, PCRE is called  by the \fB/g\fP or \fB/G\fP modifier. After finding a match, PCRE is called
# Line 150  flags set in order to search for another Line 202  flags set in order to search for another
202  If this second match fails, the start offset is advanced by one, and the normal  If this second match fails, the start offset is advanced by one, and the normal
203  match is retried. This imitates the way Perl handles such cases when using the  match is retried. This imitates the way Perl handles such cases when using the
204  \fB/g\fP modifier or the \fBsplit()\fP function.  \fB/g\fP modifier or the \fBsplit()\fP function.
205  .P  .
206    .
207    .SS "Other modifiers"
208    .rs
209    .sp
210  There are yet more modifiers for controlling the way \fBpcretest\fP  There are yet more modifiers for controlling the way \fBpcretest\fP
211  operates.  operates.
212  .P  .P
# Line 159  matched the entire pattern, pcretest sho Line 215  matched the entire pattern, pcretest sho
215  the subject string. This is useful for tests where the subject contains  the subject string. This is useful for tests where the subject contains
216  multiple copies of the same substring.  multiple copies of the same substring.
217  .P  .P
218    The \fB/B\fP modifier is a debugging feature. It requests that \fBpcretest\fP
219    output a representation of the compiled byte code after compilation. Normally
220    this information contains length and offset values; however, if \fB/Z\fP is
221    also present, this data is replaced by spaces. This is a special feature for
222    use in the automatic test scripts; it ensures that the same output is generated
223    for different internal link sizes.
224    .P
225  The \fB/L\fP modifier must be followed directly by the name of a locale, for  The \fB/L\fP modifier must be followed directly by the name of a locale, for
226  example,  example,
227  .sp  .sp
# Line 175  compiled pattern (whether it is anchored Line 238  compiled pattern (whether it is anchored
238  so on). It does this by calling \fBpcre_fullinfo()\fP after compiling a  so on). It does this by calling \fBpcre_fullinfo()\fP after compiling a
239  pattern. If the pattern is studied, the results of that are also output.  pattern. If the pattern is studied, the results of that are also output.
240  .P  .P
241  The \fB/D\fP modifier is a PCRE debugging feature, which also assumes \fB/I\fP.  The \fB/D\fP modifier is a PCRE debugging feature, and is equivalent to
242  It causes the internal form of compiled regular expressions to be output after  \fB/BI\fP, that is, both the \fB/B\fP and the \fB/I\fP modifiers.
 compilation. If the pattern was studied, the information returned is also  
 output.  
243  .P  .P
244  The \fB/F\fP modifier causes \fBpcretest\fP to flip the byte order of the  The \fB/F\fP modifier causes \fBpcretest\fP to flip the byte order of the
245  fields in the compiled pattern that contain 2-byte and 4-byte numbers. This  fields in the compiled pattern that contain 2-byte and 4-byte numbers. This
# Line 222  complicated features of PCRE. If you are Line 283  complicated features of PCRE. If you are
283  expressions, you probably don't need any of these. The following escapes are  expressions, you probably don't need any of these. The following escapes are
284  recognized:  recognized:
285  .sp  .sp
286    \ea         alarm (= BEL)    \ea         alarm (BEL, \ex07)
287    \eb         backspace    \eb         backspace (\ex08)
288    \ee         escape    \ee         escape (\ex27)
289    \ef         formfeed    \ef         formfeed (\ex0c)
290    \en         newline    \en         newline (\ex0a)
291    \er         carriage return  .\" JOIN
292    \et         tab    \eqdd       set the PCRE_MATCH_LIMIT limit to dd
293    \ev         vertical tab                 (any number of digits)
294      \er         carriage return (\ex0d)
295      \et         tab (\ex09)
296      \ev         vertical tab (\ex0b)
297    \ennn       octal character (up to 3 octal digits)    \ennn       octal character (up to 3 octal digits)
298    \exhh       hexadecimal character (up to 2 hex digits)    \exhh       hexadecimal character (up to 2 hex digits)
299  .\" JOIN  .\" JOIN
300    \ex{hh...}  hexadecimal character, any number of digits    \ex{hh...}  hexadecimal character, any number of digits
301                 in UTF-8 mode                 in UTF-8 mode
302    .\" JOIN
303    \eA         pass the PCRE_ANCHORED option to \fBpcre_exec()\fP    \eA         pass the PCRE_ANCHORED option to \fBpcre_exec()\fP
304                   or \fBpcre_dfa_exec()\fP
305    .\" JOIN
306    \eB         pass the PCRE_NOTBOL option to \fBpcre_exec()\fP    \eB         pass the PCRE_NOTBOL option to \fBpcre_exec()\fP
307                   or \fBpcre_dfa_exec()\fP
308  .\" JOIN  .\" JOIN
309    \eCdd       call pcre_copy_substring() for substring dd    \eCdd       call pcre_copy_substring() for substring dd
310                 after a successful match (number less than 32)                 after a successful match (number less than 32)
# Line 257  recognized: Line 325  recognized:
325  .\" JOIN  .\" JOIN
326    \eC*n       pass the number n (may be negative) as callout    \eC*n       pass the number n (may be negative) as callout
327                 data; this is used as the callout return value                 data; this is used as the callout return value
328      \eD         use the \fBpcre_dfa_exec()\fP match function
329      \eF         only shortest match for \fBpcre_dfa_exec()\fP
330  .\" JOIN  .\" JOIN
331    \eGdd       call pcre_get_substring() for substring dd    \eGdd       call pcre_get_substring() for substring dd
332                 after a successful match (number less than 32)                 after a successful match (number less than 32)
# Line 267  recognized: Line 337  recognized:
337  .\" JOIN  .\" JOIN
338    \eL         call pcre_get_substringlist() after a    \eL         call pcre_get_substringlist() after a
339                 successful match                 successful match
340    \eM         discover the minimum MATCH_LIMIT setting  .\" JOIN
341      \eM         discover the minimum MATCH_LIMIT and
342                   MATCH_LIMIT_RECURSION settings
343    .\" JOIN
344    \eN         pass the PCRE_NOTEMPTY option to \fBpcre_exec()\fP    \eN         pass the PCRE_NOTEMPTY option to \fBpcre_exec()\fP
345                   or \fBpcre_dfa_exec()\fP
346  .\" JOIN  .\" JOIN
347    \eOdd       set the size of the output vector passed to    \eOdd       set the size of the output vector passed to
348                 \fBpcre_exec()\fP to dd (any number of digits)                 \fBpcre_exec()\fP to dd (any number of digits)
349    .\" JOIN
350    \eP         pass the PCRE_PARTIAL option to \fBpcre_exec()\fP    \eP         pass the PCRE_PARTIAL option to \fBpcre_exec()\fP
351                   or \fBpcre_dfa_exec()\fP
352    .\" JOIN
353      \eQdd       set the PCRE_MATCH_LIMIT_RECURSION limit to dd
354                   (any number of digits)
355      \eR         pass the PCRE_DFA_RESTART option to \fBpcre_dfa_exec()\fP
356    \eS         output details of memory get/free calls during matching    \eS         output details of memory get/free calls during matching
357    .\" JOIN
358    \eZ         pass the PCRE_NOTEOL option to \fBpcre_exec()\fP    \eZ         pass the PCRE_NOTEOL option to \fBpcre_exec()\fP
359                   or \fBpcre_dfa_exec()\fP
360  .\" JOIN  .\" JOIN
361    \e?         pass the PCRE_NO_UTF8_CHECK option to    \e?         pass the PCRE_NO_UTF8_CHECK option to
362                 \fBpcre_exec()\fP                 \fBpcre_exec()\fP or \fBpcre_dfa_exec()\fP
363    \e>dd       start the match at offset dd (any number of digits);    \e>dd       start the match at offset dd (any number of digits);
364    .\" JOIN
365                 this sets the \fIstartoffset\fP argument for \fBpcre_exec()\fP                 this sets the \fIstartoffset\fP argument for \fBpcre_exec()\fP
366                   or \fBpcre_dfa_exec()\fP
367    .\" JOIN
368      \e<cr>      pass the PCRE_NEWLINE_CR option to \fBpcre_exec()\fP
369                   or \fBpcre_dfa_exec()\fP
370    .\" JOIN
371      \e<lf>      pass the PCRE_NEWLINE_LF option to \fBpcre_exec()\fP
372                   or \fBpcre_dfa_exec()\fP
373    .\" JOIN
374      \e<crlf>    pass the PCRE_NEWLINE_CRLF option to \fBpcre_exec()\fP
375                   or \fBpcre_dfa_exec()\fP
376    .\" JOIN
377      \e<anycrlf> pass the PCRE_NEWLINE_ANYCRLF option to \fBpcre_exec()\fP
378                   or \fBpcre_dfa_exec()\fP
379    .\" JOIN
380      \e<any>     pass the PCRE_NEWLINE_ANY option to \fBpcre_exec()\fP
381                   or \fBpcre_dfa_exec()\fP
382  .sp  .sp
383  A backslash followed by anything else just escapes the anything else. If the  The escapes that specify line ending sequences are literal strings, exactly as
384  very last character is a backslash, it is ignored. This gives a way of passing  shown. No more than one newline setting should be present in any data line.
385  an empty line as data, since a real empty line terminates the data input.  .P
386    A backslash followed by anything else just escapes the anything else. If
387    the very last character is a backslash, it is ignored. This gives a way of
388    passing an empty line as data, since a real empty line terminates the data
389    input.
390  .P  .P
391  If \eM is present, \fBpcretest\fP calls \fBpcre_exec()\fP several times, with  If \eM is present, \fBpcretest\fP calls \fBpcre_exec()\fP several times, with
392  different values in the \fImatch_limit\fP field of the \fBpcre_extra\fP data  different values in the \fImatch_limit\fP and \fImatch_limit_recursion\fP
393  structure, until it finds the minimum number that is needed for  fields of the \fBpcre_extra\fP data structure, until it finds the minimum
394  \fBpcre_exec()\fP to complete. This number is a measure of the amount of  numbers for each parameter that allow \fBpcre_exec()\fP to complete. The
395  recursion and backtracking that takes place, and checking it out can be  \fImatch_limit\fP number is a measure of the amount of backtracking that takes
396  instructive. For most simple matches, the number is quite small, but for  place, and checking it out can be instructive. For most simple matches, the
397  patterns with very large numbers of matching possibilities, it can become large  number is quite small, but for patterns with very large numbers of matching
398  very quickly with increasing length of subject string.  possibilities, it can become large very quickly with increasing length of
399    subject string. The \fImatch_limit_recursion\fP number is a measure of how much
400    stack (or, if PCRE is compiled with NO_RECURSE, how much heap) memory is needed
401    to complete the match attempt.
402  .P  .P
403  When \eO is used, the value specified may be higher or lower than the size set  When \eO is used, the value specified may be higher or lower than the size set
404  by the \fB-O\fP command line option (or defaulted to 45); \eO applies only to  by the \fB-O\fP command line option (or defaulted to 45); \eO applies only to
405  the call of \fBpcre_exec()\fP for the line in which it appears.  the call of \fBpcre_exec()\fP for the line in which it appears.
406  .P  .P
407  If the \fB/P\fP modifier was present on the pattern, causing the POSIX wrapper  If the \fB/P\fP modifier was present on the pattern, causing the POSIX wrapper
408  API to be used, only \eB and \eZ have any effect, causing REG_NOTBOL and  API to be used, the only option-setting sequences that have any effect are \eB
409  REG_NOTEOL to be passed to \fBregexec()\fP respectively.  and \eZ, causing REG_NOTBOL and REG_NOTEOL, respectively, to be passed to
410    \fBregexec()\fP.
411  .P  .P
412  The use of \ex{hh...} to represent UTF-8 characters is not dependent on the use  The use of \ex{hh...} to represent UTF-8 characters is not dependent on the use
413  of the \fB/8\fP modifier on the pattern. It is recognized always. There may be  of the \fB/8\fP modifier on the pattern. It is recognized always. There may be
414  any number of hexadecimal digits inside the braces. The result is from one to  any number of hexadecimal digits inside the braces. The result is from one to
415  six bytes, encoded according to the UTF-8 rules.  six bytes, encoded according to the original UTF-8 rules of RFC 2279. This
416    allows for values in the range 0 to 0x7FFFFFFF. Note that not all of those are
417    valid Unicode code points, or indeed valid UTF-8 characters according to the
418    later rules in RFC 3629.
419  .  .
420  .  .
421  .SH "OUTPUT FROM PCRETEST"  .SH "THE ALTERNATIVE MATCHING FUNCTION"
422  .rs  .rs
423  .sp  .sp
424    By default, \fBpcretest\fP uses the standard PCRE matching function,
425    \fBpcre_exec()\fP to match each data line. From release 6.0, PCRE supports an
426    alternative matching function, \fBpcre_dfa_test()\fP, which operates in a
427    different way, and has some restrictions. The differences between the two
428    functions are described in the
429    .\" HREF
430    \fBpcrematching\fP
431    .\"
432    documentation.
433    .P
434    If a data line contains the \eD escape sequence, or if the command line
435    contains the \fB-dfa\fP option, the alternative matching function is called.
436    This function finds all possible matches at a given point. If, however, the \eF
437    escape sequence is present in the data line, it stops after the first match is
438    found. This is always the shortest possible match.
439    .
440    .
441    .SH "DEFAULT OUTPUT FROM PCRETEST"
442    .rs
443    .sp
444    This section describes the output when the normal matching function,
445    \fBpcre_exec()\fP, is being used.
446    .P
447  When a match succeeds, pcretest outputs the list of captured substrings that  When a match succeeds, pcretest outputs the list of captured substrings that
448  \fBpcre_exec()\fP returns, starting with number 0 for the string that matched  \fBpcre_exec()\fP returns, starting with number 0 for the string that matched
449  the whole pattern. Otherwise, it outputs "No match" or "Partial match"  the whole pattern. Otherwise, it outputs "No match" or "Partial match"
450  when \fBpcre_exec()\fP returns PCRE_ERROR_NOMATCH or PCRE_ERROR_PARTIAL,  when \fBpcre_exec()\fP returns PCRE_ERROR_NOMATCH or PCRE_ERROR_PARTIAL,
451  respectively, and otherwise the PCRE negative error number. Here is an example  respectively, and otherwise the PCRE negative error number. Here is an example
452  of an interactive pcretest run.  of an interactive \fBpcretest\fP run.
453  .sp  .sp
454    $ pcretest    $ pcretest
455    PCRE version 5.00 07-Sep-2004    PCRE version 7.0 30-Nov-2006
456  .sp  .sp
457      re> /^abc(\ed+)/      re> /^abc(\ed+)/
458    data> abc123    data> abc123
# Line 330  of an interactive pcretest run. Line 463  of an interactive pcretest run.
463  .sp  .sp
464  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
465  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
466  pattern. If the pattern has the \fB/+\fP modifier, the output for substring 0  pattern. See below for the definition of non-printing characters. If the
467  is followed by the the rest of the subject string, identified by "0+" like  pattern has the \fB/+\fP modifier, the output for substring 0 is followed by
468  this:  the the rest of the subject string, identified by "0+" like this:
469  .sp  .sp
470      re> /cat/+      re> /cat/+
471    data> cataract    data> cataract
# Line 360  instead of a colon. This is in addition Line 493  instead of a colon. This is in addition
493  length (that is, the return from the extraction function) is given in  length (that is, the return from the extraction function) is given in
494  parentheses after each string for \fB\eC\fP and \fB\eG\fP.  parentheses after each string for \fB\eC\fP and \fB\eG\fP.
495  .P  .P
496  Note that while patterns can be continued over several lines (a plain ">"  Note that whereas patterns can be continued over several lines (a plain ">"
497  prompt is used for continuations), data lines may not. However newlines can be  prompt is used for continuations), data lines may not. However newlines can be
498  included in data by means of the \en escape.  included in data by means of the \en escape (or \er, \er\en, etc., depending on
499    the newline sequence setting).
500    .
501    .
502    .
503    .SH "OUTPUT FROM THE ALTERNATIVE MATCHING FUNCTION"
504    .rs
505    .sp
506    When the alternative matching function, \fBpcre_dfa_exec()\fP, is used (by
507    means of the \eD escape sequence or the \fB-dfa\fP command line option), the
508    output consists of a list of all the matches that start at the first point in
509    the subject where there is at least one match. For example:
510    .sp
511        re> /(tang|tangerine|tan)/
512      data> yellow tangerine\eD
513       0: tangerine
514       1: tang
515       2: tan
516    .sp
517    (Using the normal matching function on this data finds only "tang".) The
518    longest matching string is always given first (and numbered zero).
519    .P
520    If \fB/g\fP is present on the pattern, the search for further matches resumes
521    at the end of the longest match. For example:
522    .sp
523        re> /(tang|tangerine|tan)/g
524      data> yellow tangerine and tangy sultana\eD
525       0: tangerine
526       1: tang
527       2: tan
528       0: tang
529       1: tan
530       0: tan
531    .sp
532    Since the matching function does not support substring capture, the escape
533    sequences that are concerned with captured substrings are not relevant.
534    .
535    .
536    .SH "RESTARTING AFTER A PARTIAL MATCH"
537    .rs
538    .sp
539    When the alternative matching function has given the PCRE_ERROR_PARTIAL return,
540    indicating that the subject partially matched the pattern, you can restart the
541    match with additional subject data by means of the \eR escape sequence. For
542    example:
543    .sp
544        re> /^\ed?\ed(jan|feb|mar|apr|may|jun|jul|aug|sep|oct|nov|dec)\ed\ed$/
545      data> 23ja\eP\eD
546      Partial match: 23ja
547      data> n05\eR\eD
548       0: n05
549    .sp
550    For further information about partial matching, see the
551    .\" HREF
552    \fBpcrepartial\fP
553    .\"
554    documentation.
555  .  .
556  .  .
557  .SH CALLOUTS  .SH CALLOUTS
558  .rs  .rs
559  .sp  .sp
560  If the pattern contains any callout requests, \fBpcretest\fP's callout function  If the pattern contains any callout requests, \fBpcretest\fP's callout function
561  is called during matching. By default, it displays the callout number, the  is called during matching. This works with both matching functions. By default,
562  start and current positions in the text at the callout time, and the next  the called function displays the callout number, the start and current
563  pattern item to be tested. For example, the output  positions in the text at the callout time, and the next pattern item to be
564    tested. For example, the output
565  .sp  .sp
566    --->pqrabcdef    --->pqrabcdef
567      0    ^  ^     \ed      0    ^  ^     \ed
# Line 396  example: Line 586  example:
586     0: E*     0: E*
587  .sp  .sp
588  The callout function in \fBpcretest\fP returns zero (carry on matching) by  The callout function in \fBpcretest\fP returns zero (carry on matching) by
589  default, but you can use an \eC item in a data line (as described above) to  default, but you can use a \eC item in a data line (as described above) to
590  change this.  change this.
591  .P  .P
592  Inserting callouts can be helpful when using \fBpcretest\fP to check  Inserting callouts can be helpful when using \fBpcretest\fP to check
# Line 408  the Line 598  the
598  documentation.  documentation.
599  .  .
600  .  .
601    .
602    .SH "NON-PRINTING CHARACTERS"
603    .rs
604    .sp
605    When \fBpcretest\fP is outputting text in the compiled version of a pattern,
606    bytes other than 32-126 are always treated as non-printing characters are are
607    therefore shown as hex escapes.
608    .P
609    When \fBpcretest\fP is outputting text that is a matched part of a subject
610    string, it behaves in the same way, unless a different locale has been set for
611    the pattern (using the \fB/L\fP modifier). In this case, the \fBisprint()\fP
612    function to distinguish printing and non-printing characters.
613    .
614    .
615    .
616  .SH "SAVING AND RELOADING COMPILED PATTERNS"  .SH "SAVING AND RELOADING COMPILED PATTERNS"
617  .rs  .rs
618  .sp  .sp
# Line 468  Finally, if you attempt to load a file t Line 673  Finally, if you attempt to load a file t
673  result is undefined.  result is undefined.
674  .  .
675  .  .
676    .SH "SEE ALSO"
677    .rs
678    .sp
679    \fBpcre\fP(3), \fBpcreapi\fP(3), \fBpcrecallout\fP(3), \fBpcrematching\fP(3),
680    \fBpcrepartial\fP(d), \fBpcrepattern\fP(3), \fBpcreprecompile\fP(3).
681    .
682    .
683  .SH AUTHOR  .SH AUTHOR
684  .rs  .rs
685  .sp  .sp
686  Philip Hazel <ph10@cam.ac.uk>  .nf
687  .br  Philip Hazel
688  University Computing Service,  University Computing Service
689  .br  Cambridge CB2 3QH, England.
690  Cambridge CB2 3QG, England.  .fi
691  .P  .
692  .in 0  .
693  Last updated: 10 September 2004  .SH REVISION
694  .br  .rs
695  Copyright (c) 1997-2004 University of Cambridge.  .sp
696    .nf
697    Last updated: 21 August 2007
698    Copyright (c) 1997-2007 University of Cambridge.
699    .fi
Legend:
Removed from v.75  
changed lines
  Added in v.227
webmaster@exim.org
 ViewVC Help
Powered by ViewVC 1.1.12