/[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 87 by nigel, Sat Feb 24 21:41:21 2007 UTC revision 386 by ph10, Tue Mar 10 11:48:33 2009 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] [-dfa] [-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 has 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  .TP 10
40  \fB-dfa\fP  \fB-dfa\fP
41  Behave as if each data line contains the \eD escape sequence; this causes the  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  alternative matching function, \fBpcre_dfa_exec()\fP, to be used instead of the
43  standard \fBpcre_exec()\fP function (more detail is given below).  standard \fBpcre_exec()\fP function (more detail is given below).
44  .TP 10  .TP 10
45    \fB-help\fP
46    Output a brief summary these options and then exit.
47    .TP 10
48  \fB-i\fP  \fB-i\fP
49  Behave as if each regex has 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
53    Behave as if each data line contains the \eM escape sequence; this causes
54    PCRE to discover the minimum MATCH_LIMIT and MATCH_LIMIT_RECURSION settings by
55    calling \fBpcre_exec()\fP repeatedly with different limits.
56    .TP 10
57  \fB-m\fP  \fB-m\fP
58  Output the size of each compiled pattern after it has been compiled. This is  Output the size of each compiled pattern after it has been compiled. This is
59  equivalent to adding \fB/M\fP to each regular expression. For compatibility  equivalent to adding \fB/M\fP to each regular expression. For compatibility
# Line 50  with earlier versions of pcretest, \fB-s Line 61  with earlier versions of pcretest, \fB-s
61  .TP 10  .TP 10
62  \fB-o\fP \fIosize\fP  \fB-o\fP \fIosize\fP
63  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
64  \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
65  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
66  matching calls by including \eO in the data line (see below).  22 different matches for \fBpcre_dfa_exec()\fP. The vector size can be
67    changed for individual matching calls by including \eO in the data line (see
68    below).
69  .TP 10  .TP 10
70  \fB-p\fP  \fB-p\fP
71  Behave as if each regex has the \fB/P\fP modifier; the POSIX wrapper API is  Behave as if each regex has the \fB/P\fP modifier; the POSIX wrapper API is
72  used to call PCRE. None of the other options has any effect when \fB-p\fP is  used to call PCRE. None of the other options has any effect when \fB-p\fP is
73  set.  set.
74  .TP 10  .TP 10
75  \fP-q\fP  \fB-q\fP
76  Do not output the version number of \fBpcretest\fP at the start of execution.  Do not output the version number of \fBpcretest\fP at the start of execution.
77  .TP 10  .TP 10
78    \fB-S\fP \fIsize\fP
79    On Unix-like systems, set the size of the runtime stack to \fIsize\fP
80    megabytes.
81    .TP 10
82  \fB-t\fP  \fB-t\fP
83  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
84  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
85  \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
86  timing will be distorted.  timing will be distorted. You can control the number of iterations that are
87    used for timing by following \fB-t\fP with a number (as a separate item on the
88    command line). For example, "-t 1000" would iterate 1000 times. The default is
89    to iterate 500000 times.
90    .TP 10
91    \fB-tm\fP
92    This is like \fB-t\fP except that it times only the matching phase, not the
93    compile or study phases.
94  .  .
95  .  .
96  .SH DESCRIPTION  .SH DESCRIPTION
# Line 78  that file and writes to stdout. Otherwis Line 102  that file and writes to stdout. Otherwis
102  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
103  expressions, and "data>" to prompt for data lines.  expressions, and "data>" to prompt for data lines.
104  .P  .P
105    When \fBpcretest\fP is built, a configuration option can specify that it should
106    be linked with the \fBlibreadline\fP library. When this is done, if the input
107    is from a terminal, it is read using the \fBreadline()\fP function. This
108    provides line-editing and history facilities. The output from the \fB-help\fP
109    option states whether or not \fBreadline()\fP will be used.
110    .P
111  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
112  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
113  lines to be matched against the pattern.  lines to be matched against the pattern.
114  .P  .P
115  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
116  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,
117  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
118  30,000 characters.  newline sequences. There is no limit on the length of data lines; the input
119    buffer is automatically extended if it is too small.
120  .P  .P
121  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
122  expression is read. The regular expressions are given enclosed in any  expression is read. The regular expressions are given enclosed in any
123  non-alphanumeric delimiters other than backslash, for example  non-alphanumeric delimiters other than backslash, for example:
124  .sp  .sp
125    /(a|bc)x+yz/    /(a|bc)x+yz/
126  .sp  .sp
# Line 137  effect as they do in Perl. For example: Line 168  effect as they do in Perl. For example:
168  The following table shows additional modifiers for setting PCRE options that do  The following table shows additional modifiers for setting PCRE options that do
169  not correspond to anything in Perl:  not correspond to anything in Perl:
170  .sp  .sp
171    \fB/A\fP    PCRE_ANCHORED    \fB/A\fP              PCRE_ANCHORED
172    \fB/C\fP    PCRE_AUTO_CALLOUT    \fB/C\fP              PCRE_AUTO_CALLOUT
173    \fB/E\fP    PCRE_DOLLAR_ENDONLY    \fB/E\fP              PCRE_DOLLAR_ENDONLY
174    \fB/f\fP    PCRE_FIRSTLINE    \fB/f\fP              PCRE_FIRSTLINE
175    \fB/N\fP    PCRE_NO_AUTO_CAPTURE    \fB/J\fP              PCRE_DUPNAMES
176    \fB/U\fP    PCRE_UNGREEDY    \fB/N\fP              PCRE_NO_AUTO_CAPTURE
177    \fB/X\fP    PCRE_EXTRA    \fB/U\fP              PCRE_UNGREEDY
178      \fB/X\fP              PCRE_EXTRA
179      \fB/<JS>\fP           PCRE_JAVASCRIPT_COMPAT
180      \fB/<cr>\fP           PCRE_NEWLINE_CR
181      \fB/<lf>\fP           PCRE_NEWLINE_LF
182      \fB/<crlf>\fP         PCRE_NEWLINE_CRLF
183      \fB/<anycrlf>\fP      PCRE_NEWLINE_ANYCRLF
184      \fB/<any>\fP          PCRE_NEWLINE_ANY
185      \fB/<bsr_anycrlf>\fP  PCRE_BSR_ANYCRLF
186      \fB/<bsr_unicode>\fP  PCRE_BSR_UNICODE
187    .sp
188    Those specifying line ending sequences are literal strings as shown, but the
189    letters can be in either case. This example sets multiline matching with CRLF
190    as the line ending sequence:
191    .sp
192      /^abc/m<crlf>
193    .sp
194    Details of the meanings of these PCRE options are given in the
195    .\" HREF
196    \fBpcreapi\fP
197    .\"
198    documentation.
199    .
200    .
201    .SS "Finding all matches in a string"
202    .rs
203  .sp  .sp
204  Searching for all possible matches within each subject string can be requested  Searching for all possible matches within each subject string can be requested
205  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 160  flags set in order to search for another Line 216  flags set in order to search for another
216  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
217  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
218  \fB/g\fP modifier or the \fBsplit()\fP function.  \fB/g\fP modifier or the \fBsplit()\fP function.
219  .P  .
220    .
221    .SS "Other modifiers"
222    .rs
223    .sp
224  There are yet more modifiers for controlling the way \fBpcretest\fP  There are yet more modifiers for controlling the way \fBpcretest\fP
225  operates.  operates.
226  .P  .P
# Line 169  matched the entire pattern, pcretest sho Line 229  matched the entire pattern, pcretest sho
229  the subject string. This is useful for tests where the subject contains  the subject string. This is useful for tests where the subject contains
230  multiple copies of the same substring.  multiple copies of the same substring.
231  .P  .P
232    The \fB/B\fP modifier is a debugging feature. It requests that \fBpcretest\fP
233    output a representation of the compiled byte code after compilation. Normally
234    this information contains length and offset values; however, if \fB/Z\fP is
235    also present, this data is replaced by spaces. This is a special feature for
236    use in the automatic test scripts; it ensures that the same output is generated
237    for different internal link sizes.
238    .P
239  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
240  example,  example,
241  .sp  .sp
# Line 185  compiled pattern (whether it is anchored Line 252  compiled pattern (whether it is anchored
252  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
253  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.
254  .P  .P
255  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
256  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.  
257  .P  .P
258  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
259  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 232  complicated features of PCRE. If you are Line 297  complicated features of PCRE. If you are
297  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
298  recognized:  recognized:
299  .sp  .sp
300    \ea         alarm (= BEL)    \ea         alarm (BEL, \ex07)
301    \eb         backspace    \eb         backspace (\ex08)
302    \ee         escape    \ee         escape (\ex27)
303    \ef         formfeed    \ef         formfeed (\ex0c)
304    \en         newline    \en         newline (\ex0a)
305    \er         carriage return  .\" JOIN
306    \et         tab    \eqdd       set the PCRE_MATCH_LIMIT limit to dd
307    \ev         vertical tab                 (any number of digits)
308      \er         carriage return (\ex0d)
309      \et         tab (\ex09)
310      \ev         vertical tab (\ex0b)
311    \ennn       octal character (up to 3 octal digits)    \ennn       octal character (up to 3 octal digits)
312    \exhh       hexadecimal character (up to 2 hex digits)    \exhh       hexadecimal character (up to 2 hex digits)
313  .\" JOIN  .\" JOIN
314    \ex{hh...}  hexadecimal character, any number of digits    \ex{hh...}  hexadecimal character, any number of digits
315                 in UTF-8 mode                 in UTF-8 mode
316    .\" JOIN
317    \eA         pass the PCRE_ANCHORED option to \fBpcre_exec()\fP    \eA         pass the PCRE_ANCHORED option to \fBpcre_exec()\fP
318                   or \fBpcre_dfa_exec()\fP
319    .\" JOIN
320    \eB         pass the PCRE_NOTBOL option to \fBpcre_exec()\fP    \eB         pass the PCRE_NOTBOL option to \fBpcre_exec()\fP
321                   or \fBpcre_dfa_exec()\fP
322  .\" JOIN  .\" JOIN
323    \eCdd       call pcre_copy_substring() for substring dd    \eCdd       call pcre_copy_substring() for substring dd
324                 after a successful match (number less than 32)                 after a successful match (number less than 32)
# Line 279  recognized: Line 351  recognized:
351  .\" JOIN  .\" JOIN
352    \eL         call pcre_get_substringlist() after a    \eL         call pcre_get_substringlist() after a
353                 successful match                 successful match
354    .\" JOIN
355    \eM         discover the minimum MATCH_LIMIT and    \eM         discover the minimum MATCH_LIMIT and
356                 MATCH_LIMIT_RECURSION settings                 MATCH_LIMIT_RECURSION settings
357    .\" JOIN
358    \eN         pass the PCRE_NOTEMPTY option to \fBpcre_exec()\fP    \eN         pass the PCRE_NOTEMPTY option to \fBpcre_exec()\fP
359                   or \fBpcre_dfa_exec()\fP
360  .\" JOIN  .\" JOIN
361    \eOdd       set the size of the output vector passed to    \eOdd       set the size of the output vector passed to
362                 \fBpcre_exec()\fP to dd (any number of digits)                 \fBpcre_exec()\fP to dd (any number of digits)
363  .\" JOIN  .\" JOIN
364    \eP         pass the PCRE_PARTIAL option to \fBpcre_exec()\fP    \eP         pass the PCRE_PARTIAL option to \fBpcre_exec()\fP
365                 or \fBpcre_dfa_exec()\fP                 or \fBpcre_dfa_exec()\fP
366    .\" JOIN
367      \eQdd       set the PCRE_MATCH_LIMIT_RECURSION limit to dd
368                   (any number of digits)
369    \eR         pass the PCRE_DFA_RESTART option to \fBpcre_dfa_exec()\fP    \eR         pass the PCRE_DFA_RESTART option to \fBpcre_dfa_exec()\fP
370    \eS         output details of memory get/free calls during matching    \eS         output details of memory get/free calls during matching
371    .\" JOIN
372    \eZ         pass the PCRE_NOTEOL option to \fBpcre_exec()\fP    \eZ         pass the PCRE_NOTEOL option to \fBpcre_exec()\fP
373                   or \fBpcre_dfa_exec()\fP
374  .\" JOIN  .\" JOIN
375    \e?         pass the PCRE_NO_UTF8_CHECK option to    \e?         pass the PCRE_NO_UTF8_CHECK option to
376                 \fBpcre_exec()\fP                 \fBpcre_exec()\fP or \fBpcre_dfa_exec()\fP
377    \e>dd       start the match at offset dd (any number of digits);    \e>dd       start the match at offset dd (any number of digits);
378    .\" JOIN
379                 this sets the \fIstartoffset\fP argument for \fBpcre_exec()\fP                 this sets the \fIstartoffset\fP argument for \fBpcre_exec()\fP
380                   or \fBpcre_dfa_exec()\fP
381    .\" JOIN
382      \e<cr>      pass the PCRE_NEWLINE_CR option to \fBpcre_exec()\fP
383                   or \fBpcre_dfa_exec()\fP
384    .\" JOIN
385      \e<lf>      pass the PCRE_NEWLINE_LF option to \fBpcre_exec()\fP
386                   or \fBpcre_dfa_exec()\fP
387    .\" JOIN
388      \e<crlf>    pass the PCRE_NEWLINE_CRLF option to \fBpcre_exec()\fP
389                   or \fBpcre_dfa_exec()\fP
390    .\" JOIN
391      \e<anycrlf> pass the PCRE_NEWLINE_ANYCRLF option to \fBpcre_exec()\fP
392                   or \fBpcre_dfa_exec()\fP
393    .\" JOIN
394      \e<any>     pass the PCRE_NEWLINE_ANY option to \fBpcre_exec()\fP
395                   or \fBpcre_dfa_exec()\fP
396  .sp  .sp
397  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
398  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.
399  an empty line as data, since a real empty line terminates the data input.  .P
400    A backslash followed by anything else just escapes the anything else. If
401    the very last character is a backslash, it is ignored. This gives a way of
402    passing an empty line as data, since a real empty line terminates the data
403    input.
404  .P  .P
405  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
406  different values in the \fImatch_limit\fP and \fImatch_limit_recursion\fP  different values in the \fImatch_limit\fP and \fImatch_limit_recursion\fP
# Line 325  and \eZ, causing REG_NOTBOL and REG_NOTE Line 426  and \eZ, causing REG_NOTBOL and REG_NOTE
426  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
427  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
428  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
429  six bytes, encoded according to the UTF-8 rules.  six bytes, encoded according to the original UTF-8 rules of RFC 2279. This
430    allows for values in the range 0 to 0x7FFFFFFF. Note that not all of those are
431    valid Unicode code points, or indeed valid UTF-8 characters according to the
432    later rules in RFC 3629.
433  .  .
434  .  .
435  .SH "THE ALTERNATIVE MATCHING FUNCTION"  .SH "THE ALTERNATIVE MATCHING FUNCTION"
# Line 362  respectively, and otherwise the PCRE neg Line 466  respectively, and otherwise the PCRE neg
466  of an interactive \fBpcretest\fP run.  of an interactive \fBpcretest\fP run.
467  .sp  .sp
468    $ pcretest    $ pcretest
469    PCRE version 5.00 07-Sep-2004    PCRE version 7.0 30-Nov-2006
470  .sp  .sp
471      re> /^abc(\ed+)/      re> /^abc(\ed+)/
472    data> abc123    data> abc123
# Line 371  of an interactive \fBpcretest\fP run. Line 475  of an interactive \fBpcretest\fP run.
475    data> xyz    data> xyz
476    No match    No match
477  .sp  .sp
478    Note that unset capturing substrings that are not followed by one that is set
479    are not returned by \fBpcre_exec()\fP, and are not shown by \fBpcretest\fP. In
480    the following example, there are two capturing substrings, but when the first
481    data line is matched, the second, unset substring is not shown. An "internal"
482    unset substring is shown as "<unset>", as for the second data line.
483    .sp
484        re> /(a)|(b)/
485      data> a
486       0: a
487       1: a
488      data> b
489       0: b
490       1: <unset>
491       2: b
492    .sp
493  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
494  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
495  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
496  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
497  this:  the the rest of the subject string, identified by "0+" like this:
498  .sp  .sp
499      re> /cat/+      re> /cat/+
500    data> cataract    data> cataract
# Line 403  instead of a colon. This is in addition Line 522  instead of a colon. This is in addition
522  length (that is, the return from the extraction function) is given in  length (that is, the return from the extraction function) is given in
523  parentheses after each string for \fB\eC\fP and \fB\eG\fP.  parentheses after each string for \fB\eC\fP and \fB\eG\fP.
524  .P  .P
525  Note that while patterns can be continued over several lines (a plain ">"  Note that whereas patterns can be continued over several lines (a plain ">"
526  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
527  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
528    the newline sequence setting).
529    .
530  .  .
531  .  .
532  .SH "OUTPUT FROM THE ALTERNATIVE MATCHING FUNCTION"  .SH "OUTPUT FROM THE ALTERNATIVE MATCHING FUNCTION"
# Line 425  the subject where there is at least one Line 546  the subject where there is at least one
546  (Using the normal matching function on this data finds only "tang".) The  (Using the normal matching function on this data finds only "tang".) The
547  longest matching string is always given first (and numbered zero).  longest matching string is always given first (and numbered zero).
548  .P  .P
549  If \fB/g\P is present on the pattern, the search for further matches resumes  If \fB/g\fP is present on the pattern, the search for further matches resumes
550  at the end of the longest match. For example:  at the end of the longest match. For example:
551  .sp  .sp
552      re> /(tang|tangerine|tan)/g      re> /(tang|tangerine|tan)/g
# Line 449  indicating that the subject partially ma Line 570  indicating that the subject partially ma
570  match with additional subject data by means of the \eR escape sequence. For  match with additional subject data by means of the \eR escape sequence. For
571  example:  example:
572  .sp  .sp
573      re> /^\d?\d(jan|feb|mar|apr|may|jun|jul|aug|sep|oct|nov|dec)\d\d$/      re> /^\ed?\ed(jan|feb|mar|apr|may|jun|jul|aug|sep|oct|nov|dec)\ed\ed$/
574    data> 23ja\eP\eD    data> 23ja\eP\eD
575    Partial match: 23ja    Partial match: 23ja
576    data> n05\eR\eD    data> n05\eR\eD
# Line 506  the Line 627  the
627  documentation.  documentation.
628  .  .
629  .  .
630    .
631    .SH "NON-PRINTING CHARACTERS"
632    .rs
633    .sp
634    When \fBpcretest\fP is outputting text in the compiled version of a pattern,
635    bytes other than 32-126 are always treated as non-printing characters are are
636    therefore shown as hex escapes.
637    .P
638    When \fBpcretest\fP is outputting text that is a matched part of a subject
639    string, it behaves in the same way, unless a different locale has been set for
640    the pattern (using the \fB/L\fP modifier). In this case, the \fBisprint()\fP
641    function to distinguish printing and non-printing characters.
642    .
643    .
644    .
645  .SH "SAVING AND RELOADING COMPILED PATTERNS"  .SH "SAVING AND RELOADING COMPILED PATTERNS"
646  .rs  .rs
647  .sp  .sp
# Line 566  Finally, if you attempt to load a file t Line 702  Finally, if you attempt to load a file t
702  result is undefined.  result is undefined.
703  .  .
704  .  .
705    .SH "SEE ALSO"
706    .rs
707    .sp
708    \fBpcre\fP(3), \fBpcreapi\fP(3), \fBpcrecallout\fP(3), \fBpcrematching\fP(3),
709    \fBpcrepartial\fP(d), \fBpcrepattern\fP(3), \fBpcreprecompile\fP(3).
710    .
711    .
712  .SH AUTHOR  .SH AUTHOR
713  .rs  .rs
714  .sp  .sp
715    .nf
716  Philip Hazel  Philip Hazel
717  .br  University Computing Service
718  University Computing Service,  Cambridge CB2 3QH, England.
719  .br  .fi
720  Cambridge CB2 3QG, England.  .
721  .P  .
722  .in 0  .SH REVISION
723  Last updated: 18 January 2006  .rs
724  .br  .sp
725  Copyright (c) 1997-2006 University of Cambridge.  .nf
726    Last updated: 10 March 2009
727    Copyright (c) 1997-2009 University of Cambridge.
728    .fi

Legend:
Removed from v.87  
changed lines
  Added in v.386

  ViewVC Help
Powered by ViewVC 1.1.5