/[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 579 by ph10, Wed Nov 24 17:39:25 2010 UTC revision 691 by ph10, Sun Sep 11 14:31:21 2011 UTC
# Line 14  man page, in case the conversion went wr Line 14  man page, in case the conversion went wr
14  <br>  <br>
15  <ul>  <ul>
16  <li><a name="TOC1" href="#SEC1">SYNOPSIS</a>  <li><a name="TOC1" href="#SEC1">SYNOPSIS</a>
17  <li><a name="TOC2" href="#SEC2">OPTIONS</a>  <li><a name="TOC2" href="#SEC2">COMMAND LINE OPTIONS</a>
18  <li><a name="TOC3" href="#SEC3">DESCRIPTION</a>  <li><a name="TOC3" href="#SEC3">DESCRIPTION</a>
19  <li><a name="TOC4" href="#SEC4">PATTERN MODIFIERS</a>  <li><a name="TOC4" href="#SEC4">PATTERN MODIFIERS</a>
20  <li><a name="TOC5" href="#SEC5">DATA LINES</a>  <li><a name="TOC5" href="#SEC5">DATA LINES</a>
# Line 31  man page, in case the conversion went wr Line 31  man page, in case the conversion went wr
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 [options] [source] [destination]</b>  <b>pcretest [options] [input file [output file]]</b>
35  <br>  <br>
36  <br>  <br>
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
# Line 42  details of the regular expressions thems Line 42  details of the regular expressions thems
42  documentation. For details of the PCRE library function calls and their  documentation. For details of the PCRE library function calls and their
43  options, see the  options, see the
44  <a href="pcreapi.html"><b>pcreapi</b></a>  <a href="pcreapi.html"><b>pcreapi</b></a>
45  documentation.  documentation. The input for <b>pcretest</b> is a sequence of regular expression
46    patterns and strings to be matched, as described below. The output shows the
47    result of each match. Options on the command line and the patterns control PCRE
48    options and exactly what is output.
49  </P>  </P>
50  <br><a name="SEC2" href="#TOC1">OPTIONS</a><br>  <br><a name="SEC2" href="#TOC1">COMMAND LINE OPTIONS</a><br>
51  <P>  <P>
52  <b>-b</b>  <b>-b</b>
53  Behave as if each regex has the <b>/B</b> (show bytecode) modifier; the internal  Behave as if each pattern has the <b>/B</b> (show byte code) modifier; the
54  form is output after compilation.  internal form is output after compilation.
55  </P>  </P>
56  <P>  <P>
57  <b>-C</b>  <b>-C</b>
# Line 57  about the optional features that are inc Line 60  about the optional features that are inc
60  </P>  </P>
61  <P>  <P>
62  <b>-d</b>  <b>-d</b>
63  Behave as if each regex has the <b>/D</b> (debug) modifier; the internal  Behave as if each pattern has the <b>/D</b> (debug) modifier; the internal
64  form and information about the compiled pattern is output after compilation;  form and information about the compiled pattern is output after compilation;
65  <b>-d</b> is equivalent to <b>-b -i</b>.  <b>-d</b> is equivalent to <b>-b -i</b>.
66  </P>  </P>
# Line 73  Output a brief summary these options and Line 76  Output a brief summary these options and
76  </P>  </P>
77  <P>  <P>
78  <b>-i</b>  <b>-i</b>
79  Behave as if each regex has the <b>/I</b> modifier; information about the  Behave as if each pattern has the <b>/I</b> modifier; information about the
80  compiled pattern is given after compilation.  compiled pattern is given after compilation.
81  </P>  </P>
82  <P>  <P>
# Line 85  calling <b>pcre_exec()</b> repeatedly wi Line 88  calling <b>pcre_exec()</b> repeatedly wi
88  <P>  <P>
89  <b>-m</b>  <b>-m</b>
90  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
91  equivalent to adding <b>/M</b> to each regular expression. For compatibility  equivalent to adding <b>/M</b> to each regular expression.
 with earlier versions of pcretest, <b>-s</b> is a synonym for <b>-m</b>.  
92  </P>  </P>
93  <P>  <P>
94  <b>-o</b> <i>osize</i>  <b>-o</b> <i>osize</i>
# Line 99  below). Line 101  below).
101  </P>  </P>
102  <P>  <P>
103  <b>-p</b>  <b>-p</b>
104  Behave as if each regex has the <b>/P</b> modifier; the POSIX wrapper API is  Behave as if each pattern has the <b>/P</b> modifier; the POSIX wrapper API is
105  used to call PCRE. None of the other options has any effect when <b>-p</b> is  used to call PCRE. None of the other options has any effect when <b>-p</b> is
106  set.  set.
107  </P>  </P>
# Line 109  Do not output the version number of <b>p Line 111  Do not output the version number of <b>p
111  </P>  </P>
112  <P>  <P>
113  <b>-S</b> <i>size</i>  <b>-S</b> <i>size</i>
114  On Unix-like systems, set the size of the runtime stack to <i>size</i>  On Unix-like systems, set the size of the run-time stack to <i>size</i>
115  megabytes.  megabytes.
116  </P>  </P>
117  <P>  <P>
118    <b>-s</b> or <b>-s+</b>
119    Behave as if each pattern has the <b>/S</b> modifier; in other words, force each
120    pattern to be studied. If <b>-s+</b> is used, the PCRE_STUDY_JIT_COMPILE flag is
121    passed to <b>pcre_study()</b>, causing just-in-time optimization to be set up if
122    it is available. If the <b>/I</b> or <b>/D</b> option is present on a pattern
123    (requesting output about the compiled pattern), information about the result of
124    studying is not included when studying is caused only by <b>-s</b> and neither
125    <b>-i</b> nor <b>-d</b> is present on the command line. This behaviour means that
126    the output from tests that are run with and without <b>-s</b> should be
127    identical, except when options that output information about the actual running
128    of a match are set. The <b>-M</b>, <b>-t</b>, and <b>-tm</b> options, which give
129    information about resources used, are likely to produce different output with
130    and without <b>-s</b>. Output may also differ if the <b>/C</b> option is present
131    on an individual pattern. This uses callouts to trace the the matching process,
132    and this may be different between studied and non-studied patterns. If the
133    pattern contains (*MARK) items there may also be differences, for the same
134    reason. The <b>-s</b> command line option can be overridden for specific
135    patterns that should never be studied (see the <b>/S</b> pattern modifier
136    below).
137    </P>
138    <P>
139  <b>-t</b>  <b>-t</b>
140  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
141  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
# Line 189  pcretest to read the next line as a cont Line 212  pcretest to read the next line as a cont
212  A pattern may be followed by any number of modifiers, which are mostly single  A pattern may be followed by any number of modifiers, which are mostly single
213  characters. Following Perl usage, these are referred to below as, for example,  characters. Following Perl usage, these are referred to below as, for example,
214  "the <b>/i</b> modifier", even though the delimiter of the pattern need not  "the <b>/i</b> modifier", even though the delimiter of the pattern need not
215  always be a slash, and no slash is used when writing modifiers. Whitespace may  always be a slash, and no slash is used when writing modifiers. White space may
216  appear between the final pattern delimiter and the first modifier, and between  appear between the final pattern delimiter and the first modifier, and between
217  the modifiers themselves.  the modifiers themselves.
218  </P>  </P>
# Line 226  options that do not correspond to anythi Line 249  options that do not correspond to anythi
249    <b>/&#60;bsr_unicode&#62;</b>  PCRE_BSR_UNICODE    <b>/&#60;bsr_unicode&#62;</b>  PCRE_BSR_UNICODE
250  </pre>  </pre>
251  The modifiers that are enclosed in angle brackets are literal strings as shown,  The modifiers that are enclosed in angle brackets are literal strings as shown,
252  including the angle brackets, but the letters can be in either case. This  including the angle brackets, but the letters within can be in either case.
253  example sets multiline matching with CRLF as the line ending sequence:  This example sets multiline matching with CRLF as the line ending sequence:
254  <pre>  <pre>
255    /^abc/m&#60;crlf&#62;    /^abc/m&#60;CRLF&#62;
256  </pre>  </pre>
257  As well as turning on the PCRE_UTF8 option, the <b>/8</b> modifier also causes  As well as turning on the PCRE_UTF8 option, the <b>/8</b> modifier also causes
258  any non-printing characters in output strings to be printed using the  any non-printing characters in output strings to be printed using the
# Line 271  operates. Line 294  operates.
294  </P>  </P>
295  <P>  <P>
296  The <b>/+</b> modifier requests that as well as outputting the substring that  The <b>/+</b> modifier requests that as well as outputting the substring that
297  matched the entire pattern, pcretest should in addition output the remainder of  matched the entire pattern, <b>pcretest</b> should in addition output the
298  the subject string. This is useful for tests where the subject contains  remainder of the subject string. This is useful for tests where the subject
299  multiple copies of the same substring.  contains multiple copies of the same substring. If the <b>+</b> modifier appears
300    twice, the same action is taken for captured substrings. In each case the
301    remainder is output on the following line with a plus character following the
302    capture number. Note that this modifier must not immediately follow the /S
303    modifier because /S+ has another meaning.
304    </P>
305    <P>
306    The <b>/=</b> modifier requests that the values of all potential captured
307    parentheses be output after a match by <b>pcre_exec()</b>. By default, only
308    those up to the highest one actually used in the match are output
309    (corresponding to the return code from <b>pcre_exec()</b>). Values in the
310    offsets vector corresponding to higher numbers should be set to -1, and these
311    are output as "&#60;unset&#62;". This modifier gives a way of checking that this is
312    happening.
313  </P>  </P>
314  <P>  <P>
315  The <b>/B</b> modifier is a debugging feature. It requests that <b>pcretest</b>  The <b>/B</b> modifier is a debugging feature. It requests that <b>pcretest</b>
# Line 331  The <b>/M</b> modifier causes the size o Line 367  The <b>/M</b> modifier causes the size o
367  pattern to be output.  pattern to be output.
368  </P>  </P>
369  <P>  <P>
370  The <b>/S</b> modifier causes <b>pcre_study()</b> to be called after the  If the <b>/S</b> modifier appears once, it causes <b>pcre_study()</b> to be
371  expression has been compiled, and the results used when the expression is  called after the expression has been compiled, and the results used when the
372  matched.  expression is matched. If <b>/S</b> appears twice, it suppresses studying, even
373    if it was requested externally by the <b>-s</b> command line option. This makes
374    it possible to specify that certain patterns are always studied, and others are
375    never studied, independently of <b>-s</b>. This feature is used in the test
376    files in a few cases where the output is different when the pattern is studied.
377    </P>
378    <P>
379    If the <b>/S</b> modifier is immediately followed by a + character, the call to
380    <b>pcre_study()</b> is made with the PCRE_STUDY_JIT_COMPILE option, requesting
381    just-in-time optimization support if it is available. Note that there is also a
382    <b>/+</b> modifier; it must not be given immediately after <b>/S</b> because this
383    will be misinterpreted. If JIT studying is successful, it will automatically be
384    used when <b>pcre_exec()</b> is run, except when incompatible run-time options
385    are specified. These include the partial matching options; a complete list is
386    given in the
387    <a href="pcrejit.html"><b>pcrejit</b></a>
388    documentation. See also the <b>\J</b> escape sequence below for a way of
389    setting the size of the JIT stack.
390  </P>  </P>
391  <P>  <P>
392  The <b>/T</b> modifier must be followed by a single digit. It causes a specific  The <b>/T</b> modifier must be followed by a single digit. It causes a specific
# Line 370  ignored. Line 423  ignored.
423  <br><a name="SEC5" href="#TOC1">DATA LINES</a><br>  <br><a name="SEC5" href="#TOC1">DATA LINES</a><br>
424  <P>  <P>
425  Before each data line is passed to <b>pcre_exec()</b>, leading and trailing  Before each data line is passed to <b>pcre_exec()</b>, leading and trailing
426  whitespace is removed, and it is then scanned for \ escapes. Some of these are  white space is removed, and it is then scanned for \ escapes. Some of these
427  pretty esoteric features, intended for checking out some of the more  are pretty esoteric features, intended for checking out some of the more
428  complicated features of PCRE. If you are just testing "ordinary" regular  complicated features of PCRE. If you are just testing "ordinary" regular
429  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
430  recognized:  recognized:
# Line 379  recognized: Line 432  recognized:
432    \a         alarm (BEL, \x07)    \a         alarm (BEL, \x07)
433    \b         backspace (\x08)    \b         backspace (\x08)
434    \e         escape (\x27)    \e         escape (\x27)
435    \f         formfeed (\x0c)    \f         form feed (\x0c)
436    \n         newline (\x0a)    \n         newline (\x0a)
437    \qdd       set the PCRE_MATCH_LIMIT limit to dd (any number of digits)    \qdd       set the PCRE_MATCH_LIMIT limit to dd (any number of digits)
438    \r         carriage return (\x0d)    \r         carriage return (\x0d)
# Line 404  recognized: Line 457  recognized:
457    \Gdd       call pcre_get_substring() for substring dd after a successful match (number less than 32)    \Gdd       call pcre_get_substring() for substring dd after a successful match (number less than 32)
458    \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-
459                 ated by next non-alphanumeric character)                 ated by next non-alphanumeric character)
460      \Jdd       set up a JIT stack of dd kilobytes maximum (any number of digits)
461    \L         call pcre_get_substringlist() after a successful match    \L         call pcre_get_substringlist() after a successful match
462    \M         discover the minimum MATCH_LIMIT and MATCH_LIMIT_RECURSION settings    \M         discover the minimum MATCH_LIMIT and MATCH_LIMIT_RECURSION settings
463    \N         pass the PCRE_NOTEMPTY option to <b>pcre_exec()</b> or <b>pcre_dfa_exec()</b>; if used twice, pass the    \N         pass the PCRE_NOTEMPTY option to <b>pcre_exec()</b> or <b>pcre_dfa_exec()</b>; if used twice, pass the
# Line 443  passing an empty line as data, since a r Line 497  passing an empty line as data, since a r
497  input.  input.
498  </P>  </P>
499  <P>  <P>
500    The <b>\J</b> escape provides a way of setting the maximum stack size that is
501    used by the just-in-time optimization code. It is ignored if JIT optimization
502    is not being used. Providing a stack that is larger than the default 32K is
503    necessary only for very complicated patterns.
504    </P>
505    <P>
506  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
507  different values in the <i>match_limit</i> and <i>match_limit_recursion</i>  different values in the <i>match_limit</i> and <i>match_limit_recursion</i>
508  fields of the <b>pcre_extra</b> data structure, until it finds the minimum  fields of the <b>pcre_extra</b> data structure, until it finds the minimum
509  numbers for each parameter that allow <b>pcre_exec()</b> to complete. The  numbers for each parameter that allow <b>pcre_exec()</b> to complete without
510  <i>match_limit</i> number is a measure of the amount of backtracking that takes  error. Because this is testing a specific feature of the normal interpretive
511  place, and checking it out can be instructive. For most simple matches, the  <b>pcre_exec()</b> execution, the use of any JIT optimization that might have
512  number is quite small, but for patterns with very large numbers of matching  been set up by the <b>/S+</b> qualifier of <b>-s+</b> option is disabled.
513  possibilities, it can become large very quickly with increasing length of  </P>
514  subject string. The <i>match_limit_recursion</i> number is a measure of how much  <P>
515  stack (or, if PCRE is compiled with NO_RECURSE, how much heap) memory is needed  The <i>match_limit</i> number is a measure of the amount of backtracking
516  to complete the match attempt.  that takes place, and checking it out can be instructive. For most simple
517    matches, the number is quite small, but for patterns with very large numbers of
518    matching possibilities, it can become large very quickly with increasing length
519    of subject string. The <i>match_limit_recursion</i> number is a measure of how
520    much stack (or, if PCRE is compiled with NO_RECURSE, how much heap) memory is
521    needed to complete the match attempt.
522  </P>  </P>
523  <P>  <P>
524  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 498  This section describes the output when t Line 563  This section describes the output when t
563  <b>pcre_exec()</b>, is being used.  <b>pcre_exec()</b>, is being used.
564  </P>  </P>
565  <P>  <P>
566  When a match succeeds, pcretest outputs the list of captured substrings that  When a match succeeds, <b>pcretest</b> outputs the list of captured substrings
567  <b>pcre_exec()</b> returns, starting with number 0 for the string that matched  that <b>pcre_exec()</b> returns, starting with number 0 for the string that
568  the whole pattern. Otherwise, it outputs "No match" when the return is  matched the whole pattern. Otherwise, it outputs "No match" when the return is
569  PCRE_ERROR_NOMATCH, and "Partial match:" followed by the partially matching  PCRE_ERROR_NOMATCH, and "Partial match:" followed by the partially matching
570  substring when <b>pcre_exec()</b> returns PCRE_ERROR_PARTIAL. (Note that this is  substring when <b>pcre_exec()</b> returns PCRE_ERROR_PARTIAL. (Note that this is
571  the entire substring that was inspected during the partial match; it may  the entire substring that was inspected during the partial match; it may
572  include characters before the actual match start if a lookbehind assertion,  include characters before the actual match start if a lookbehind assertion,
573  \K, \b, or \B was involved.) For any other returns, it outputs the PCRE  \K, \b, or \B was involved.) For any other return, <b>pcretest</b> outputs
574  negative error number. Here is an example of an interactive <b>pcretest</b> run.  the PCRE negative error number and a short descriptive phrase. If the error is
575    a failed UTF-8 string check, the byte offset of the start of the failing
576    character and the reason code are also output, provided that the size of the
577    output vector is at least two. Here is an example of an interactive
578    <b>pcretest</b> run.
579  <pre>  <pre>
580    $ pcretest    $ pcretest
581    PCRE version 7.0 30-Nov-2006    PCRE version 8.13 2011-04-30
582    
583      re&#62; /^abc(\d+)/      re&#62; /^abc(\d+)/
584    data&#62; abc123    data&#62; abc123
# Line 518  negative error number. Here is an exampl Line 587  negative error number. Here is an exampl
587    data&#62; xyz    data&#62; xyz
588    No match    No match
589  </pre>  </pre>
590  Note that unset capturing substrings that are not followed by one that is set  Unset capturing substrings that are not followed by one that is set are not
591  are not returned by <b>pcre_exec()</b>, and are not shown by <b>pcretest</b>. In  returned by <b>pcre_exec()</b>, and are not shown by <b>pcretest</b>. In the
592  the following example, there are two capturing substrings, but when the first  following example, there are two capturing substrings, but when the first data
593  data line is matched, the second, unset substring is not shown. An "internal"  line is matched, the second, unset substring is not shown. An "internal" unset
594  unset substring is shown as "&#60;unset&#62;", as for the second data line.  substring is shown as "&#60;unset&#62;", as for the second data line.
595  <pre>  <pre>
596      re&#62; /(a)|(b)/      re&#62; /(a)|(b)/
597    data&#62; a    data&#62; a
# Line 556  matching attempts are output in sequence Line 625  matching attempts are output in sequence
625     0: ipp     0: ipp
626     1: pp     1: pp
627  </pre>  </pre>
628  "No match" is output only if the first match attempt fails.  "No match" is output only if the first match attempt fails. Here is an example
629    of a failure message (the offset 4 that is specified by \&#62;4 is past the end of
630    the subject string):
631    <pre>
632        re&#62; /xyz/
633      data&#62; xyz\&#62;4
634      Error -24 (bad offset value)
635    </PRE>
636  </P>  </P>
637  <P>  <P>
638  If any of the sequences <b>\C</b>, <b>\G</b>, or <b>\L</b> are present in a  If any of the sequences <b>\C</b>, <b>\G</b>, or <b>\L</b> are present in a
# Line 656  example: Line 732  example:
732    +10 ^ ^    +10 ^ ^
733     0: E*     0: E*
734  </pre>  </pre>
735    If a pattern contains (*MARK) items, an additional line is output whenever
736    a change of latest mark is passed to the callout function. For example:
737    <pre>
738        re&#62; /a(*MARK:X)bc/C
739      data&#62; abc
740      ---&#62;abc
741       +0 ^       a
742       +1 ^^      (*MARK:X)
743      +10 ^^      b
744      Latest Mark: X
745      +11 ^ ^     c
746      +12 ^  ^
747       0: abc
748    </pre>
749    The mark changes between matching "a" and "b", but stays the same for the rest
750    of the match, so nothing more is output. If, as a result of backtracking, the
751    mark reverts to being unset, the text "&#60;unset&#62;" is output.
752    </P>
753    <P>
754  The callout function in <b>pcretest</b> returns zero (carry on matching) by  The callout function in <b>pcretest</b> returns zero (carry on matching) by
755  default, but you can use a \C item in a data line (as described above) to  default, but you can use a \C item in a data line (as described above) to
756  change this.  change this and other parameters of the callout.
757  </P>  </P>
758  <P>  <P>
759  Inserting callouts can be helpful when using <b>pcretest</b> to check  Inserting callouts can be helpful when using <b>pcretest</b> to check
# Line 682  function to distinguish printing and non Line 777  function to distinguish printing and non
777  <br><a name="SEC12" href="#TOC1">SAVING AND RELOADING COMPILED PATTERNS</a><br>  <br><a name="SEC12" href="#TOC1">SAVING AND RELOADING COMPILED PATTERNS</a><br>
778  <P>  <P>
779  The facilities described in this section are not available when the POSIX  The facilities described in this section are not available when the POSIX
780  inteface to PCRE is being used, that is, when the <b>/P</b> pattern modifier is  interface to PCRE is being used, that is, when the <b>/P</b> pattern modifier is
781  specified.  specified.
782  </P>  </P>
783  <P>  <P>
# Line 695  For example: Line 790  For example:
790  See the  See the
791  <a href="pcreprecompile.html"><b>pcreprecompile</b></a>  <a href="pcreprecompile.html"><b>pcreprecompile</b></a>
792  documentation for a discussion about saving and re-using compiled patterns.  documentation for a discussion about saving and re-using compiled patterns.
793    Note that if the pattern was successfully studied with JIT optimization, the
794    JIT data cannot be saved.
795  </P>  </P>
796  <P>  <P>
797  The data that is written is binary. The first eight bytes are the length of the  The data that is written is binary. The first eight bytes are the length of the
# Line 703  written as four bytes in big-endian orde Line 800  written as four bytes in big-endian orde
800  there is no study data (either the pattern was not studied, or studying did not  there is no study data (either the pattern was not studied, or studying did not
801  return any data), the second length is zero. The lengths are followed by an  return any data), the second length is zero. The lengths are followed by an
802  exact copy of the compiled pattern. If there is additional study data, this  exact copy of the compiled pattern. If there is additional study data, this
803  follows immediately after the compiled pattern. After writing the file,  (excluding any JIT data) follows immediately after the compiled pattern. After
804  <b>pcretest</b> expects to read a new pattern.  writing the file, <b>pcretest</b> expects to read a new pattern.
805  </P>  </P>
806  <P>  <P>
807  A saved pattern can be reloaded into <b>pcretest</b> by specifing &#60; and a file  A saved pattern can be reloaded into <b>pcretest</b> by specifying &#60; and a file
808  name instead of a pattern. The name of the file must not contain a &#60; character,  name instead of a pattern. The name of the file must not contain a &#60; character,
809  as otherwise <b>pcretest</b> will interpret the line as a pattern delimited by &#60;  as otherwise <b>pcretest</b> will interpret the line as a pattern delimited by &#60;
810  characters.  characters.
811  For example:  For example:
812  <pre>  <pre>
813     re&#62; &#60;/some/file     re&#62; &#60;/some/file
814    Compiled regex loaded from /some/file    Compiled pattern loaded from /some/file
815    No study data    No study data
816  </pre>  </pre>
817  When the pattern has been loaded, <b>pcretest</b> proceeds to read data lines in  If the pattern was previously studied with the JIT optimization, the JIT
818  the usual way.  information cannot be saved and restored, and so is lost. When the pattern has
819    been loaded, <b>pcretest</b> proceeds to read data lines in the usual way.
820  </P>  </P>
821  <P>  <P>
822  You can copy a file written by <b>pcretest</b> to a different host and reload it  You can copy a file written by <b>pcretest</b> to a different host and reload it
# Line 743  result is undefined. Line 841  result is undefined.
841  </P>  </P>
842  <br><a name="SEC13" href="#TOC1">SEE ALSO</a><br>  <br><a name="SEC13" href="#TOC1">SEE ALSO</a><br>
843  <P>  <P>
844  <b>pcre</b>(3), <b>pcreapi</b>(3), <b>pcrecallout</b>(3), <b>pcrematching</b>(3),  <b>pcre</b>(3), <b>pcreapi</b>(3), <b>pcrecallout</b>(3), <b>pcrejit</b>,
845  <b>pcrepartial</b>(d), <b>pcrepattern</b>(3), <b>pcreprecompile</b>(3).  <b>pcrematching</b>(3), <b>pcrepartial</b>(d), <b>pcrepattern</b>(3),
846    <b>pcreprecompile</b>(3).
847  </P>  </P>
848  <br><a name="SEC14" href="#TOC1">AUTHOR</a><br>  <br><a name="SEC14" href="#TOC1">AUTHOR</a><br>
849  <P>  <P>
# Line 757  Cambridge CB2 3QH, England. Line 856  Cambridge CB2 3QH, England.
856  </P>  </P>
857  <br><a name="SEC15" href="#TOC1">REVISION</a><br>  <br><a name="SEC15" href="#TOC1">REVISION</a><br>
858  <P>  <P>
859  Last updated: 21 November 2010  Last updated: 26 August 2011
860  <br>  <br>
861  Copyright &copy; 1997-2010 University of Cambridge.  Copyright &copy; 1997-2011 University of Cambridge.
862  <br>  <br>
863  <p>  <p>
864  Return to the <a href="index.html">PCRE index page</a>.  Return to the <a href="index.html">PCRE index page</a>.

Legend:
Removed from v.579  
changed lines
  Added in v.691

  ViewVC Help
Powered by ViewVC 1.1.5