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

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

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

revision 77 by nigel, Sat Feb 24 21:40:45 2007 UTC revision 150 by ph10, Tue Apr 17 08:22:40 2007 UTC
# Line 23  man page, in case the conversion went wr Line 23  man page, in case the conversion went wr
23  <li><a name="TOC8" href="#SEC8">OUTPUT FROM THE ALTERNATIVE MATCHING FUNCTION</a>  <li><a name="TOC8" href="#SEC8">OUTPUT FROM THE ALTERNATIVE MATCHING FUNCTION</a>
24  <li><a name="TOC9" href="#SEC9">RESTARTING AFTER A PARTIAL MATCH</a>  <li><a name="TOC9" href="#SEC9">RESTARTING AFTER A PARTIAL MATCH</a>
25  <li><a name="TOC10" href="#SEC10">CALLOUTS</a>  <li><a name="TOC10" href="#SEC10">CALLOUTS</a>
26  <li><a name="TOC11" href="#SEC11">SAVING AND RELOADING COMPILED PATTERNS</a>  <li><a name="TOC11" href="#SEC11">NON-PRINTING CHARACTERS</a>
27  <li><a name="TOC12" href="#SEC12">AUTHOR</a>  <li><a name="TOC12" href="#SEC12">SAVING AND RELOADING COMPILED PATTERNS</a>
28    <li><a name="TOC13" href="#SEC13">SEE ALSO</a>
29    <li><a name="TOC14" href="#SEC14">AUTHOR</a>
30    <li><a name="TOC15" href="#SEC15">REVISION</a>
31  </ul>  </ul>
32  <br><a name="SEC1" href="#TOC1">SYNOPSIS</a><br>  <br><a name="SEC1" href="#TOC1">SYNOPSIS</a><br>
33  <P>  <P>
34  <b>pcretest [-C] [-d] [-dfa] [-i] [-m] [-o osize] [-p] [-t] [source]</b>  <b>pcretest [options] [source] [destination]</b>
35  <b>[destination]</b>  <br>
36  </P>  <br>
 <P>  
37  <b>pcretest</b> was written as a test program for the PCRE regular expression  <b>pcretest</b> was written as a test program for the PCRE regular expression
38  library itself, but it can also be used for experimenting with regular  library itself, but it can also be used for experimenting with regular
39  expressions. This document describes the features of the test program; for  expressions. This document describes the features of the test program; for
# Line 44  documentation. Line 46  documentation.
46  </P>  </P>
47  <br><a name="SEC2" href="#TOC1">OPTIONS</a><br>  <br><a name="SEC2" href="#TOC1">OPTIONS</a><br>
48  <P>  <P>
49    <b>-b</b>
50    Behave as if each regex has the <b>/B</b> (show bytecode) modifier; the internal
51    form is output after compilation.
52    </P>
53    <P>
54  <b>-C</b>  <b>-C</b>
55  Output the version number of the PCRE library, and all available information  Output the version number of the PCRE library, and all available information
56  about the optional features that are included, and then exit.  about the optional features that are included, and then exit.
# Line 51  about the optional features that are inc Line 58  about the optional features that are inc
58  <P>  <P>
59  <b>-d</b>  <b>-d</b>
60  Behave as if each regex has the <b>/D</b> (debug) modifier; the internal  Behave as if each regex has the <b>/D</b> (debug) modifier; the internal
61  form is output after compilation.  form and information about the compiled pattern is output after compilation;
62    <b>-d</b> is equivalent to <b>-b -i</b>.
63  </P>  </P>
64  <P>  <P>
65  <b>-dfa</b>  <b>-dfa</b>
# Line 60  alternative matching function, <b>pcre_d Line 68  alternative matching function, <b>pcre_d
68  standard <b>pcre_exec()</b> function (more detail is given below).  standard <b>pcre_exec()</b> function (more detail is given below).
69  </P>  </P>
70  <P>  <P>
71    <b>-help</b>
72    Output a brief summary these options and then exit.
73    </P>
74    <P>
75  <b>-i</b>  <b>-i</b>
76  Behave as if each regex has the <b>/I</b> modifier; information about the  Behave as if each regex has the <b>/I</b> modifier; information about the
77  compiled pattern is given after compilation.  compiled pattern is given after compilation.
# Line 73  with earlier versions of pcretest, <b>-s Line 85  with earlier versions of pcretest, <b>-s
85  <P>  <P>
86  <b>-o</b> <i>osize</i>  <b>-o</b> <i>osize</i>
87  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
88  <b>pcre_exec()</b> to be <i>osize</i>. The default value is 45, which is enough  <b>pcre_exec()</b> or <b>pcre_dfa_exec()</b> to be <i>osize</i>. The default value
89  for 14 capturing subexpressions. The vector size can be changed for individual  is 45, which is enough for 14 capturing subexpressions for <b>pcre_exec()</b> or
90  matching calls by including \O in the data line (see below).  22 different matches for <b>pcre_dfa_exec()</b>. The vector size can be
91    changed for individual matching calls by including \O in the data line (see
92    below).
93  </P>  </P>
94  <P>  <P>
95  <b>-p</b>  <b>-p</b>
# Line 84  used to call PCRE. None of the other opt Line 98  used to call PCRE. None of the other opt
98  set.  set.
99  </P>  </P>
100  <P>  <P>
101    <b>-q</b>
102    Do not output the version number of <b>pcretest</b> at the start of execution.
103    </P>
104    <P>
105    <b>-S</b> <i>size</i>
106    On Unix-like systems, set the size of the runtime stack to <i>size</i>
107    megabytes.
108    </P>
109    <P>
110  <b>-t</b>  <b>-t</b>
111  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
112  resulting time per compile or match (in milliseconds). Do not set <b>-m</b> with  resulting time per compile or match (in milliseconds). Do not set <b>-m</b> with
113  <b>-t</b>, because you will then get the size output a zillion times, and the  <b>-t</b>, because you will then get the size output a zillion times, and the
114  timing will be distorted.  timing will be distorted. You can control the number of iterations that are
115    used for timing by following <b>-t</b> with a number (as a separate item on the
116    command line). For example, "-t 1000" would iterate 1000 times. The default is
117    to iterate 500000 times.
118    </P>
119    <P>
120    <b>-tm</b>
121    This is like <b>-t</b> except that it times only the matching phase, not the
122    compile or study phases.
123  </P>  </P>
124  <br><a name="SEC3" href="#TOC1">DESCRIPTION</a><br>  <br><a name="SEC3" href="#TOC1">DESCRIPTION</a><br>
125  <P>  <P>
# Line 105  lines to be matched against the pattern. Line 136  lines to be matched against the pattern.
136  </P>  </P>
137  <P>  <P>
138  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
139  multiple-line matches, you have to use the \n escape sequence in a single line  multi-line matches, you have to use the \n escape sequence (or \r or \r\n,
140  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
141  30,000 characters.  newline sequences. There is no limit on the length of data lines; the input
142    buffer is automatically extended if it is too small.
143  </P>  </P>
144  <P>  <P>
145  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
146  expression is read. The regular expressions are given enclosed in any  expression is read. The regular expressions are given enclosed in any
147  non-alphanumeric delimiters other than backslash, for example  non-alphanumeric delimiters other than backslash, for example:
148  <pre>  <pre>
149    /(a|bc)x+yz/    /(a|bc)x+yz/
150  </pre>  </pre>
# Line 159  effect as they do in Perl. For example: Line 191  effect as they do in Perl. For example:
191  The following table shows additional modifiers for setting PCRE options that do  The following table shows additional modifiers for setting PCRE options that do
192  not correspond to anything in Perl:  not correspond to anything in Perl:
193  <pre>  <pre>
194    <b>/A</b>    PCRE_ANCHORED    <b>/A</b>          PCRE_ANCHORED
195    <b>/C</b>    PCRE_AUTO_CALLOUT    <b>/C</b>          PCRE_AUTO_CALLOUT
196    <b>/E</b>    PCRE_DOLLAR_ENDONLY    <b>/E</b>          PCRE_DOLLAR_ENDONLY
197    <b>/f</b>    PCRE_FIRSTLINE    <b>/f</b>          PCRE_FIRSTLINE
198    <b>/N</b>    PCRE_NO_AUTO_CAPTURE    <b>/J</b>          PCRE_DUPNAMES
199    <b>/U</b>    PCRE_UNGREEDY    <b>/N</b>          PCRE_NO_AUTO_CAPTURE
200    <b>/X</b>    PCRE_EXTRA    <b>/U</b>          PCRE_UNGREEDY
201      <b>/X</b>          PCRE_EXTRA
202      <b>/&#60;cr&#62;</b>       PCRE_NEWLINE_CR
203      <b>/&#60;lf&#62;</b>       PCRE_NEWLINE_LF
204      <b>/&#60;crlf&#62;</b>     PCRE_NEWLINE_CRLF
205      <b>/&#60;anycrlf&#62;</b>  PCRE_NEWLINE_ANY
206      <b>/&#60;any&#62;</b>      PCRE_NEWLINE_ANY
207    </pre>
208    Those specifying line ending sequencess are literal strings as shown. This
209    example sets multiline matching with CRLF as the line ending sequence:
210    <pre>
211      /^abc/m&#60;crlf&#62;
212  </pre>  </pre>
213    Details of the meanings of these PCRE options are given in the
214    <a href="pcreapi.html"><b>pcreapi</b></a>
215    documentation.
216    </P>
217    <br><b>
218    Finding all matches in a string
219    </b><br>
220    <P>
221  Searching for all possible matches within each subject string can be requested  Searching for all possible matches within each subject string can be requested
222  by the <b>/g</b> or <b>/G</b> modifier. After finding a match, PCRE is called  by the <b>/g</b> or <b>/G</b> modifier. After finding a match, PCRE is called
223  again to search the remainder of the subject string. The difference between  again to search the remainder of the subject string. The difference between
# Line 184  If this second match fails, the start of Line 235  If this second match fails, the start of
235  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
236  <b>/g</b> modifier or the <b>split()</b> function.  <b>/g</b> modifier or the <b>split()</b> function.
237  </P>  </P>
238    <br><b>
239    Other modifiers
240    </b><br>
241  <P>  <P>
242  There are yet more modifiers for controlling the way <b>pcretest</b>  There are yet more modifiers for controlling the way <b>pcretest</b>
243  operates.  operates.
# Line 195  the subject string. This is useful for t Line 249  the subject string. This is useful for t
249  multiple copies of the same substring.  multiple copies of the same substring.
250  </P>  </P>
251  <P>  <P>
252    The <b>/B</b> modifier is a debugging feature. It requests that <b>pcretest</b>
253    output a representation of the compiled byte code after compilation. Normally
254    this information contains length and offset values; however, if <b>/Z</b> is
255    also present, this data is replaced by spaces. This is a special feature for
256    use in the automatic test scripts; it ensures that the same output is generated
257    for different internal link sizes.
258    </P>
259    <P>
260  The <b>/L</b> modifier must be followed directly by the name of a locale, for  The <b>/L</b> modifier must be followed directly by the name of a locale, for
261  example,  example,
262  <pre>  <pre>
# Line 213  so on). It does this by calling <b>pcre_ Line 275  so on). It does this by calling <b>pcre_
275  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.
276  </P>  </P>
277  <P>  <P>
278  The <b>/D</b> modifier is a PCRE debugging feature, which also assumes <b>/I</b>.  The <b>/D</b> modifier is a PCRE debugging feature, and is equivalent to
279  It causes the internal form of compiled regular expressions to be output after  <b>/BI</b>, that is, both the <b>/B</b> and the <b>/I</b> modifiers.
 compilation. If the pattern was studied, the information returned is also  
 output.  
280  </P>  </P>
281  <P>  <P>
282  The <b>/F</b> modifier causes <b>pcretest</b> to flip the byte order of the  The <b>/F</b> modifier causes <b>pcretest</b> to flip the byte order of the
# Line 264  complicated features of PCRE. If you are Line 324  complicated features of PCRE. If you are
324  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
325  recognized:  recognized:
326  <pre>  <pre>
327    \a         alarm (= BEL)    \a         alarm (BEL, \x07)
328    \b         backspace    \b         backspace (\x08)
329    \e         escape    \e         escape (\x27)
330    \f         formfeed    \f         formfeed (\x0c)
331    \n         newline    \n         newline (\x0a)
332    \r         carriage return    \qdd       set the PCRE_MATCH_LIMIT limit to dd (any number of digits)
333    \t         tab    \r         carriage return (\x0d)
334    \v         vertical tab    \t         tab (\x09)
335      \v         vertical tab (\x0b)
336    \nnn       octal character (up to 3 octal digits)    \nnn       octal character (up to 3 octal digits)
337    \xhh       hexadecimal character (up to 2 hex digits)    \xhh       hexadecimal character (up to 2 hex digits)
338    \x{hh...}  hexadecimal character, any number of digits in UTF-8 mode    \x{hh...}  hexadecimal character, any number of digits in UTF-8 mode
339    \A         pass the PCRE_ANCHORED option to <b>pcre_exec()</b>    \A         pass the PCRE_ANCHORED option to <b>pcre_exec()</b> or <b>pcre_dfa_exec()</b>
340    \B         pass the PCRE_NOTBOL option to <b>pcre_exec()</b>    \B         pass the PCRE_NOTBOL option to <b>pcre_exec()</b> or <b>pcre_dfa_exec()</b>
341    \Cdd       call pcre_copy_substring() for substring dd after a successful match (number less than 32)    \Cdd       call pcre_copy_substring() for substring dd after a successful match (number less than 32)
342    \Cname     call pcre_copy_named_substring() for substring "name" after a successful match (name termin-    \Cname     call pcre_copy_named_substring() for substring "name" after a successful match (name termin-
343                 ated by next non alphanumeric character)                 ated by next non alphanumeric character)
# Line 291  recognized: Line 352  recognized:
352    \Gname     call pcre_get_named_substring() for substring "name" after a successful match (name termin-    \Gname     call pcre_get_named_substring() for substring "name" after a successful match (name termin-
353                 ated by next non-alphanumeric character)                 ated by next non-alphanumeric character)
354    \L         call pcre_get_substringlist() after a successful match    \L         call pcre_get_substringlist() after a successful match
355    \M         discover the minimum MATCH_LIMIT setting    \M         discover the minimum MATCH_LIMIT and MATCH_LIMIT_RECURSION settings
356    \N         pass the PCRE_NOTEMPTY option to <b>pcre_exec()</b>    \N         pass the PCRE_NOTEMPTY option to <b>pcre_exec()</b> or <b>pcre_dfa_exec()</b>
357    \Odd       set the size of the output vector passed to <b>pcre_exec()</b> to dd (any number of digits)    \Odd       set the size of the output vector passed to <b>pcre_exec()</b> to dd (any number of digits)
358    \P         pass the PCRE_PARTIAL option to <b>pcre_exec()</b> or <b>pcre_dfa_exec()</b>    \P         pass the PCRE_PARTIAL option to <b>pcre_exec()</b> or <b>pcre_dfa_exec()</b>
359      \Qdd       set the PCRE_MATCH_LIMIT_RECURSION limit to dd (any number of digits)
360    \R         pass the PCRE_DFA_RESTART option to <b>pcre_dfa_exec()</b>    \R         pass the PCRE_DFA_RESTART option to <b>pcre_dfa_exec()</b>
361    \S         output details of memory get/free calls during matching    \S         output details of memory get/free calls during matching
362    \Z         pass the PCRE_NOTEOL option to <b>pcre_exec()</b>    \Z         pass the PCRE_NOTEOL option to <b>pcre_exec()</b> or <b>pcre_dfa_exec()</b>
363    \?         pass the PCRE_NO_UTF8_CHECK option to <b>pcre_exec()</b>    \?         pass the PCRE_NO_UTF8_CHECK option to <b>pcre_exec()</b> or <b>pcre_dfa_exec()</b>
364    \&#62;dd       start the match at offset dd (any number of digits);    \&#62;dd       start the match at offset dd (any number of digits);
365                 this sets the <i>startoffset</i> argument for <b>pcre_exec()</b>                 this sets the <i>startoffset</i> argument for <b>pcre_exec()</b> or <b>pcre_dfa_exec()</b>
366  </pre>    \&#60;cr&#62;      pass the PCRE_NEWLINE_CR option to <b>pcre_exec()</b> or <b>pcre_dfa_exec()</b>
367  A backslash followed by anything else just escapes the anything else. If the    \&#60;lf&#62;      pass the PCRE_NEWLINE_LF option to <b>pcre_exec()</b> or <b>pcre_dfa_exec()</b>
368  very last character is a backslash, it is ignored. This gives a way of passing    \&#60;crlf&#62;    pass the PCRE_NEWLINE_CRLF option to <b>pcre_exec()</b> or <b>pcre_dfa_exec()</b>
369  an empty line as data, since a real empty line terminates the data input.    \&#60;anycrlf&#62; pass the PCRE_NEWLINE_ANYCRLF option to <b>pcre_exec()</b> or <b>pcre_dfa_exec()</b>
370      \&#60;any&#62;     pass the PCRE_NEWLINE_ANY option to <b>pcre_exec()</b> or <b>pcre_dfa_exec()</b>
371    </pre>
372    The escapes that specify line ending sequences are literal strings, exactly as
373    shown. No more than one newline setting should be present in any data line.
374    </P>
375    <P>
376    A backslash followed by anything else just escapes the anything else. If
377    the very last character is a backslash, it is ignored. This gives a way of
378    passing an empty line as data, since a real empty line terminates the data
379    input.
380  </P>  </P>
381  <P>  <P>
382  If \M is present, <b>pcretest</b> calls <b>pcre_exec()</b> several times, with  If \M is present, <b>pcretest</b> calls <b>pcre_exec()</b> several times, with
383  different values in the <i>match_limit</i> field of the <b>pcre_extra</b> data  different values in the <i>match_limit</i> and <i>match_limit_recursion</i>
384  structure, until it finds the minimum number that is needed for  fields of the <b>pcre_extra</b> data structure, until it finds the minimum
385  <b>pcre_exec()</b> to complete. This number is a measure of the amount of  numbers for each parameter that allow <b>pcre_exec()</b> to complete. The
386  recursion and backtracking that takes place, and checking it out can be  <i>match_limit</i> number is a measure of the amount of backtracking that takes
387  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
388  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
389  very quickly with increasing length of subject string.  possibilities, it can become large very quickly with increasing length of
390    subject string. The <i>match_limit_recursion</i> number is a measure of how much
391    stack (or, if PCRE is compiled with NO_RECURSE, how much heap) memory is needed
392    to complete the match attempt.
393  </P>  </P>
394  <P>  <P>
395  When \O is used, the value specified may be higher or lower than the size set  When \O is used, the value specified may be higher or lower than the size set
# Line 323  the call of <b>pcre_exec()</b> for the l Line 398  the call of <b>pcre_exec()</b> for the l
398  </P>  </P>
399  <P>  <P>
400  If the <b>/P</b> modifier was present on the pattern, causing the POSIX wrapper  If the <b>/P</b> modifier was present on the pattern, causing the POSIX wrapper
401  API to be used, only \B and \Z have any effect, causing REG_NOTBOL and  API to be used, the only option-setting sequences that have any effect are \B
402  REG_NOTEOL to be passed to <b>regexec()</b> respectively.  and \Z, causing REG_NOTBOL and REG_NOTEOL, respectively, to be passed to
403    <b>regexec()</b>.
404  </P>  </P>
405  <P>  <P>
406  The use of \x{hh...} to represent UTF-8 characters is not dependent on the use  The use of \x{hh...} to represent UTF-8 characters is not dependent on the use
# Line 363  respectively, and otherwise the PCRE neg Line 439  respectively, and otherwise the PCRE neg
439  of an interactive <b>pcretest</b> run.  of an interactive <b>pcretest</b> run.
440  <pre>  <pre>
441    $ pcretest    $ pcretest
442    PCRE version 5.00 07-Sep-2004    PCRE version 7.0 30-Nov-2006
443    
444      re&#62; /^abc(\d+)/      re&#62; /^abc(\d+)/
445    data&#62; abc123    data&#62; abc123
# Line 374  of an interactive <b>pcretest</b> run. Line 450  of an interactive <b>pcretest</b> run.
450  </pre>  </pre>
451  If the strings contain any non-printing characters, they are output as \0x  If the strings contain any non-printing characters, they are output as \0x
452  escapes, or as \x{...} escapes if the <b>/8</b> modifier was present on the  escapes, or as \x{...} escapes if the <b>/8</b> modifier was present on the
453  pattern. If the pattern has the <b>/+</b> modifier, the output for substring 0  pattern. See below for the definition of non-printing characters. If the
454  is followed by the the rest of the subject string, identified by "0+" like  pattern has the <b>/+</b> modifier, the output for substring 0 is followed by
455  this:  the the rest of the subject string, identified by "0+" like this:
456  <pre>  <pre>
457      re&#62; /cat/+      re&#62; /cat/+
458    data&#62; cataract    data&#62; cataract
# Line 406  length (that is, the return from the ext Line 482  length (that is, the return from the ext
482  parentheses after each string for <b>\C</b> and <b>\G</b>.  parentheses after each string for <b>\C</b> and <b>\G</b>.
483  </P>  </P>
484  <P>  <P>
485  Note that while patterns can be continued over several lines (a plain "&#62;"  Note that whereas patterns can be continued over several lines (a plain "&#62;"
486  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
487  included in data by means of the \n escape.  included in data by means of the \n escape (or \r, \r\n, etc., depending on
488    the newline sequence setting).
489  </P>  </P>
490  <br><a name="SEC8" href="#TOC1">OUTPUT FROM THE ALTERNATIVE MATCHING FUNCTION</a><br>  <br><a name="SEC8" href="#TOC1">OUTPUT FROM THE ALTERNATIVE MATCHING FUNCTION</a><br>
491  <P>  <P>
# Line 427  the subject where there is at least one Line 504  the subject where there is at least one
504  longest matching string is always given first (and numbered zero).  longest matching string is always given first (and numbered zero).
505  </P>  </P>
506  <P>  <P>
507  If \fB/g\P is present on the pattern, the search for further matches resumes  If <b>/g</b> is present on the pattern, the search for further matches resumes
508  at the end of the longest match. For example:  at the end of the longest match. For example:
509  <pre>  <pre>
510      re&#62; /(tang|tangerine|tan)/g      re&#62; /(tang|tangerine|tan)/g
# Line 501  the Line 578  the
578  <a href="pcrecallout.html"><b>pcrecallout</b></a>  <a href="pcrecallout.html"><b>pcrecallout</b></a>
579  documentation.  documentation.
580  </P>  </P>
581  <br><a name="SEC11" href="#TOC1">SAVING AND RELOADING COMPILED PATTERNS</a><br>  <br><a name="SEC11" href="#TOC1">NON-PRINTING CHARACTERS</a><br>
582    <P>
583    When <b>pcretest</b> is outputting text in the compiled version of a pattern,
584    bytes other than 32-126 are always treated as non-printing characters are are
585    therefore shown as hex escapes.
586    </P>
587    <P>
588    When <b>pcretest</b> is outputting text that is a matched part of a subject
589    string, it behaves in the same way, unless a different locale has been set for
590    the pattern (using the <b>/L</b> modifier). In this case, the <b>isprint()</b>
591    function to distinguish printing and non-printing characters.
592    </P>
593    <br><a name="SEC12" href="#TOC1">SAVING AND RELOADING COMPILED PATTERNS</a><br>
594  <P>  <P>
595  The facilities described in this section are not available when the POSIX  The facilities described in this section are not available when the POSIX
596  inteface to PCRE is being used, that is, when the <b>/P</b> pattern modifier is  inteface to PCRE is being used, that is, when the <b>/P</b> pattern modifier is
# Line 563  string using a reloaded pattern is likel Line 652  string using a reloaded pattern is likel
652  Finally, if you attempt to load a file that is not in the correct format, the  Finally, if you attempt to load a file that is not in the correct format, the
653  result is undefined.  result is undefined.
654  </P>  </P>
655  <br><a name="SEC12" href="#TOC1">AUTHOR</a><br>  <br><a name="SEC13" href="#TOC1">SEE ALSO</a><br>
656    <P>
657    <b>pcre</b>(3), <b>pcreapi</b>(3), <b>pcrecallout</b>(3), <b>pcrematching</b>(3),
658    <b>pcrepartial</b>(d), <b>pcrepattern</b>(3), <b>pcreprecompile</b>(3).
659    </P>
660    <br><a name="SEC14" href="#TOC1">AUTHOR</a><br>
661  <P>  <P>
662  Philip Hazel  Philip Hazel
663  <br>  <br>
664  University Computing Service,  University Computing Service
665    <br>
666    Cambridge CB2 3QH, England.
667  <br>  <br>
 Cambridge CB2 3QG, England.  
668  </P>  </P>
669    <br><a name="SEC15" href="#TOC1">REVISION</a><br>
670  <P>  <P>
671  Last updated: 28 February 2005  Last updated: 16 April 2007
672    <br>
673    Copyright &copy; 1997-2007 University of Cambridge.
674  <br>  <br>
 Copyright &copy; 1997-2005 University of Cambridge.  
675  <p>  <p>
676  Return to the <a href="index.html">PCRE index page</a>.  Return to the <a href="index.html">PCRE index page</a>.
677  </p>  </p>

Legend:
Removed from v.77  
changed lines
  Added in v.150

  ViewVC Help
Powered by ViewVC 1.1.5