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

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

Parent Directory | Revision Log | View Patch Patch

-revision 518 by ph10,
Tue May 18 15:47:01 2010 UTC
+revision 788 by ph10,
Tue Dec  6 15:38:01 2011 UTC
 Line 4 
 pcretest - a program for testing Perl-co
  .SH SYNOPSIS
  .rs
  .sp
- .B pcretest "[options] [source] [destination]"
+ .B pcretest "[options] [input file [output file]]"
  .sp
  \fBpcretest\fP was written as a test program for the PCRE regular expression
  library itself, but it can also be used for experimenting with regular
 Line 18 
 options, see the
  .\" HREF
  \fBpcreapi\fP
  .\"
- documentation.
+ documentation. The input for \fBpcretest\fP is a sequence of regular expression
+ patterns and strings to be matched, as described below. The output shows the
+ result of each match. Options on the command line and the patterns control PCRE
+ options and exactly what is output.
  .
  .
- .SH OPTIONS
+ .SH COMMAND LINE OPTIONS
  .rs
  .TP 10
  \fB-b\fP
- Behave as if each regex has the \fB/B\fP (show bytecode) modifier; the internal
+ Behave as if each pattern has the \fB/B\fP (show byte code) modifier; the
- form is output after compilation.
+ internal form is output after compilation.
  .TP 10
  \fB-C\fP
  Output the version number of the PCRE library, and all available information
  about the optional features that are included, and then exit.
  .TP 10
  \fB-d\fP
- Behave as if each regex has the \fB/D\fP (debug) modifier; the internal
+ Behave as if each pattern has the \fB/D\fP (debug) modifier; the internal
  form and information about the compiled pattern is output after compilation;
  \fB-d\fP is equivalent to \fB-b -i\fP.
  .TP 10
-Line 46 
 standard \fBpcre_exec()\fP function (mor
+Line 49 
 standard \fBpcre_exec()\fP function (mor
  Output a brief summary these options and then exit.
  .TP 10
  \fB-i\fP
- Behave as if each regex has the \fB/I\fP modifier; information about the
+ Behave as if each pattern has the \fB/I\fP modifier; information about the
  compiled pattern is given after compilation.
  .TP 10
  \fB-M\fP
-Line 56 
 calling \fBpcre_exec()\fP repeatedly wit
+Line 59 
 calling \fBpcre_exec()\fP repeatedly wit
  .TP 10
  \fB-m\fP
  Output the size of each compiled pattern after it has been compiled. This is
- equivalent to adding \fB/M\fP to each regular expression. For compatibility
+ equivalent to adding \fB/M\fP to each regular expression.
- with earlier versions of pcretest, \fB-s\fP is a synonym for \fB-m\fP.
  .TP 10
  \fB-o\fP \fIosize\fP
  Set the number of elements in the output vector that is used when calling
-Line 68 
 changed for individual matching calls by
+Line 70 
 changed for individual matching calls by
  below).
  .TP 10
  \fB-p\fP
- Behave as if each regex has the \fB/P\fP modifier; the POSIX wrapper API is
+ Behave as if each pattern has the \fB/P\fP modifier; the POSIX wrapper API is
  used to call PCRE. None of the other options has any effect when \fB-p\fP is
  set.
  .TP 10
-Line 76 
 set.
+Line 78 
 set.
  Do not output the version number of \fBpcretest\fP at the start of execution.
  .TP 10
  \fB-S\fP \fIsize\fP
- On Unix-like systems, set the size of the runtime stack to \fIsize\fP
+ On Unix-like systems, set the size of the run-time stack to \fIsize\fP
  megabytes.
  .TP 10
+ \fB-s\fP or \fB-s+\fP
+ Behave as if each pattern has the \fB/S\fP modifier; in other words, force each
+ pattern to be studied. If \fB-s+\fP is used, the PCRE_STUDY_JIT_COMPILE flag is
+ passed to \fBpcre_study()\fP, causing just-in-time optimization to be set up if
+ it is available. If the \fB/I\fP or \fB/D\fP option is present on a pattern
+ (requesting output about the compiled pattern), information about the result of
+ studying is not included when studying is caused only by \fB-s\fP and neither
+ \fB-i\fP nor \fB-d\fP is present on the command line. This behaviour means that
+ the output from tests that are run with and without \fB-s\fP should be
+ identical, except when options that output information about the actual running
+ of a match are set. The \fB-M\fP, \fB-t\fP, and \fB-tm\fP options, which give
+ information about resources used, are likely to produce different output with
+ and without \fB-s\fP. Output may also differ if the \fB/C\fP option is present
+ on an individual pattern. This uses callouts to trace the the matching process,
+ and this may be different between studied and non-studied patterns. If the
+ pattern contains (*MARK) items there may also be differences, for the same
+ reason. The \fB-s\fP command line option can be overridden for specific
+ patterns that should never be studied (see the \fB/S\fP pattern modifier
+ below).
+ .TP 10
  \fB-t\fP
  Run each compile, study, and match many times with a timer, and output
  resulting time per compile or match (in milliseconds). Do not set \fB-m\fP with
-Line 154 
 pcretest to read the next line as a cont
+Line 176 
 pcretest to read the next line as a cont
  A pattern may be followed by any number of modifiers, which are mostly single
  characters. Following Perl usage, these are referred to below as, for example,
  "the \fB/i\fP modifier", even though the delimiter of the pattern need not
- 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
  appear between the final pattern delimiter and the first modifier, and between
  the modifiers themselves.
  .P
-Line 169 
 The following table shows additional mod
+Line 191 
 The following table shows additional mod
  options that do not correspond to anything in Perl:
  .sp
    \fB/8\fP              PCRE_UTF8
    \fB/?\fP              PCRE_NO_UTF8_CHECK
    \fB/A\fP              PCRE_ANCHORED
    \fB/C\fP              PCRE_AUTO_CALLOUT
    \fB/E\fP              PCRE_DOLLAR_ENDONLY
-Line 177 
 options that do not correspond to anythi
+Line 199 
 options that do not correspond to anythi
    \fB/J\fP              PCRE_DUPNAMES
    \fB/N\fP              PCRE_NO_AUTO_CAPTURE
    \fB/U\fP              PCRE_UNGREEDY
    \fB/W\fP              PCRE_UCP
    \fB/X\fP              PCRE_EXTRA
+   \fB/Y\fP              PCRE_NO_START_OPTIMIZE
    \fB/<JS>\fP           PCRE_JAVASCRIPT_COMPAT
    \fB/<cr>\fP           PCRE_NEWLINE_CR
    \fB/<lf>\fP           PCRE_NEWLINE_LF
-Line 189 
 options that do not correspond to anythi
+Line 212 
 options that do not correspond to anythi
    \fB/<bsr_unicode>\fP  PCRE_BSR_UNICODE
  .sp
  The modifiers that are enclosed in angle brackets are literal strings as shown,
- 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.
- example sets multiline matching with CRLF as the line ending sequence:
+ This example sets multiline matching with CRLF as the line ending sequence:
  .sp
-   /^abc/m<crlf>
+   /^abc/m<CRLF>
  .sp
  As well as turning on the PCRE_UTF8 option, the \fB/8\fP modifier also causes
  any non-printing characters in output strings to be printed using the
-Line 201 
 options are given in the
+Line 224 
 options are given in the
  .\" HREF
  \fBpcreapi\fP
  .\"
  documentation.
  .
  .
  .SS "Finding all matches in a string"
-Line 219 
 begins with a lookbehind assertion (incl
+Line 242 
 begins with a lookbehind assertion (incl
  If any call to \fBpcre_exec()\fP in a \fB/g\fP or \fB/G\fP sequence matches an
  empty string, the next call is done with the PCRE_NOTEMPTY_ATSTART and
  PCRE_ANCHORED flags set in order to search for another, non-empty, match at the
- same point. If this second match fails, the start offset is advanced by one
+ same point. If this second match fails, the start offset is advanced, and the
- character, and the normal match is retried. This imitates the way Perl handles
+ normal match is retried. This imitates the way Perl handles such cases when
- such cases when using the \fB/g\fP modifier or the \fBsplit()\fP function.
+ using the \fB/g\fP modifier or the \fBsplit()\fP function. Normally, the start
+ offset is advanced by one character, but if the newline convention recognizes
+ CRLF as a newline, and the current character is CR followed by LF, an advance
+ of two is used.
  .
  .
  .SS "Other modifiers"
-Line 231 
 There are yet more modifiers for control
+Line 257 
 There are yet more modifiers for control
  operates.
  .P
  The \fB/+\fP modifier requests that as well as outputting the substring that
- matched the entire pattern, pcretest should in addition output the remainder of
+ matched the entire pattern, \fBpcretest\fP should in addition output the
- 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
- multiple copies of the same substring.
+ contains multiple copies of the same substring. If the \fB+\fP modifier appears
+ twice, the same action is taken for captured substrings. In each case the
+ remainder is output on the following line with a plus character following the
+ capture number. Note that this modifier must not immediately follow the /S
+ modifier because /S+ has another meaning.
+ .P
+ The \fB/=\fP modifier requests that the values of all potential captured
+ parentheses be output after a match by \fBpcre_exec()\fP. By default, only
+ those up to the highest one actually used in the match are output
+ (corresponding to the return code from \fBpcre_exec()\fP). Values in the
+ offsets vector corresponding to higher numbers should be set to -1, and these
+ are output as "<unset>". This modifier gives a way of checking that this is
+ happening.
  .P
  The \fB/B\fP modifier is a debugging feature. It requests that \fBpcretest\fP
  output a representation of the compiled byte code after compilation. Normally
-Line 276 
 example,
+Line 314 
 example,
  For this reason, it must be the last modifier. The given locale is set,
  \fBpcre_maketables()\fP is called to build a set of character tables for the
  locale, and this is then passed to \fBpcre_compile()\fP when compiling the
- regular expression. Without an \fB/L\fP modifier, NULL is passed as the tables
+ regular expression. Without an \fB/L\fP (or \fB/T\fP) modifier, NULL is passed
- pointer; that is, \fB/L\fP applies only to the expression on which it appears.
+ as the tables pointer; that is, \fB/L\fP applies only to the expression on
+ which it appears.
  .P
  The \fB/M\fP modifier causes the size of memory block used to hold the compiled
- pattern to be output.
+ pattern to be output. This does not include the size of the \fBpcre\fP block;
+ it is just the actual compiled data. If the pattern is successfully studied
+ with the PCRE_STUDY_JIT_COMPILE option, the size of the JIT compiled code is
+ also output.
+ .P
+ If the \fB/S\fP modifier appears once, it causes \fBpcre_study()\fP to be
+ called after the expression has been compiled, and the results used when the
+ expression is matched. If \fB/S\fP appears twice, it suppresses studying, even
+ if it was requested externally by the \fB-s\fP command line option. This makes
+ it possible to specify that certain patterns are always studied, and others are
+ never studied, independently of \fB-s\fP. This feature is used in the test
+ files in a few cases where the output is different when the pattern is studied.
+ .P
+ If the \fB/S\fP modifier is immediately followed by a + character, the call to
+ \fBpcre_study()\fP is made with the PCRE_STUDY_JIT_COMPILE option, requesting
+ just-in-time optimization support if it is available. Note that there is also a
+ \fB/+\fP modifier; it must not be given immediately after \fB/S\fP because this
+ will be misinterpreted. If JIT studying is successful, it will automatically be
+ used when \fBpcre_exec()\fP is run, except when incompatible run-time options
+ are specified. These include the partial matching options; a complete list is
+ given in the
+ .\" HREF
+ \fBpcrejit\fP
+ .\"
+ documentation. See also the \fB\eJ\fP escape sequence below for a way of
+ setting the size of the JIT stack.
  .P
- The \fB/S\fP modifier causes \fBpcre_study()\fP to be called after the
+ The \fB/T\fP modifier must be followed by a single digit. It causes a specific
- expression has been compiled, and the results used when the expression is
+ set of built-in character tables to be passed to \fBpcre_compile()\fP. It is
- matched.
+ used in the standard PCRE tests to check behaviour with different character
+ tables. The digit specifies the tables as follows:
+ .sp
+  the default ASCII tables, as distributed in
+         pcre_chartables.c.dist
+  a set of tables defining ISO 8859 characters
+ .sp
+ In table 1, some characters whose codes are greater than 128 are identified as
+ letters, digits, spaces, etc.
  .
  .
  .SS "Using the POSIX wrapper API"
  .rs
  .sp
  The \fB/P\fP modifier causes \fBpcretest\fP to call PCRE via the POSIX wrapper
  API rather than its native API. When \fB/P\fP is set, the following modifiers
  set options for the \fBregcomp()\fP function:
  .sp
    /i    REG_ICASE
    /m    REG_NEWLINE
    /N    REG_NOSUB
    /s    REG_DOTALL     )
    /U    REG_UNGREEDY   ) These options are not part of
    /W    REG_UCP        )   the POSIX standard
    /8    REG_UTF8       )
  .sp
-Line 310 
 ignored.
+Line 382 
 ignored.
  .rs
  .sp
  Before each data line is passed to \fBpcre_exec()\fP, leading and trailing
- whitespace is removed, and it is then scanned for \e escapes. Some of these are
+ white space is removed, and it is then scanned for \e escapes. Some of these
- pretty esoteric features, intended for checking out some of the more
+ are pretty esoteric features, intended for checking out some of the more
  complicated features of PCRE. If you are just testing "ordinary" regular
  expressions, you probably don't need any of these. The following escapes are
  recognized:
-Line 319 
 recognized:
+Line 391 
 recognized:
    \ea         alarm (BEL, \ex07)
    \eb         backspace (\ex08)
    \ee         escape (\ex27)
-   \ef         formfeed (\ex0c)
+   \ef         form feed (\ex0c)
    \en         newline (\ex0a)
  .\" JOIN
    \eqdd       set the PCRE_MATCH_LIMIT limit to dd
-Line 328 
 recognized:
+Line 400 
 recognized:
    \et         tab (\ex09)
    \ev         vertical tab (\ex0b)
    \ennn       octal character (up to 3 octal digits)
-   \exhh       hexadecimal character (up to 2 hex digits)
+                always a byte unless > 255 in UTF-8 mode
+   \exhh       hexadecimal byte (up to 2 hex digits)
  .\" JOIN
    \ex{hh...}  hexadecimal character, any number of digits
                 in UTF-8 mode
-Line 368 
 recognized:
+Line 441 
 recognized:
                 "name" after a successful match (name termin-
                 ated by next non-alphanumeric character)
  .\" JOIN
+   \eJdd       set up a JIT stack of dd kilobytes maximum (any
+                number of digits)
+ .\" JOIN
    \eL         call pcre_get_substringlist() after a
                 successful match
  .\" JOIN
-Line 398 
 recognized:
+Line 474 
 recognized:
  .\" JOIN
    \e?         pass the PCRE_NO_UTF8_CHECK option to
                 \fBpcre_exec()\fP or \fBpcre_dfa_exec()\fP
-   \e>dd       start the match at offset dd (any number of digits);
  .\" JOIN
-                this sets the \fIstartoffset\fP argument for \fBpcre_exec()\fP
+   \e>dd       start the match at offset dd (optional "-"; then
-                or \fBpcre_dfa_exec()\fP
+                any number of digits); this sets the \fIstartoffset\fP
+                argument for \fBpcre_exec()\fP or \fBpcre_dfa_exec()\fP
  .\" JOIN
    \e<cr>      pass the PCRE_NEWLINE_CR option to \fBpcre_exec()\fP
                 or \fBpcre_dfa_exec()\fP
-Line 418 
 recognized:
+Line 494 
 recognized:
    \e<any>     pass the PCRE_NEWLINE_ANY option to \fBpcre_exec()\fP
                 or \fBpcre_dfa_exec()\fP
  .sp
+ Note that \exhh always specifies one byte, even in UTF-8 mode; this makes it
+ possible to construct invalid UTF-8 sequences for testing purposes. On the
+ other hand, \ex{hh} is interpreted as a UTF-8 character in UTF-8 mode,
+ generating more than one byte if the value is greater than 127. When not in
+ UTF-8 mode, it generates one byte for values less than 256, and causes an error
+ for greater values.
+ .P
  The escapes that specify line ending sequences are literal strings, exactly as
  shown. No more than one newline setting should be present in any data line.
  .P
-Line 426 
 the very last character is a backslash,
+Line 509 
 the very last character is a backslash,
  passing an empty line as data, since a real empty line terminates the data
  input.
  .P
+ The \fB\eJ\fP escape provides a way of setting the maximum stack size that is
+ used by the just-in-time optimization code. It is ignored if JIT optimization
+ is not being used. Providing a stack that is larger than the default 32K is
+ necessary only for very complicated patterns.
+ .P
  If \eM is present, \fBpcretest\fP calls \fBpcre_exec()\fP several times, with
  different values in the \fImatch_limit\fP and \fImatch_limit_recursion\fP
  fields of the \fBpcre_extra\fP data structure, until it finds the minimum
- numbers for each parameter that allow \fBpcre_exec()\fP to complete. The
+ numbers for each parameter that allow \fBpcre_exec()\fP to complete without
- \fImatch_limit\fP number is a measure of the amount of backtracking that takes
+ error. Because this is testing a specific feature of the normal interpretive
- place, and checking it out can be instructive. For most simple matches, the
+ \fBpcre_exec()\fP execution, the use of any JIT optimization that might have
- number is quite small, but for patterns with very large numbers of matching
+ been set up by the \fB/S+\fP qualifier of \fB-s+\fP option is disabled.
- possibilities, it can become large very quickly with increasing length of
+ .P
- subject string. The \fImatch_limit_recursion\fP number is a measure of how much
+ The \fImatch_limit\fP number is a measure of the amount of backtracking
- stack (or, if PCRE is compiled with NO_RECURSE, how much heap) memory is needed
+ that takes place, and checking it out can be instructive. For most simple
- to complete the match attempt.
+ matches, the number is quite small, but for patterns with very large numbers of
+ matching possibilities, it can become large very quickly with increasing length
+ of subject string. The \fImatch_limit_recursion\fP number is a measure of how
+ much stack (or, if PCRE is compiled with NO_RECURSE, how much heap) memory is
+ needed to complete the match attempt.
  .P
  When \eO is used, the value specified may be higher or lower than the size set
  by the \fB-O\fP command line option (or defaulted to 45); \eO applies only to
-Line 482 
 found. This is always the shortest possi
+Line 574 
 found. This is always the shortest possi
  This section describes the output when the normal matching function,
  \fBpcre_exec()\fP, is being used.
  .P
- When a match succeeds, pcretest outputs the list of captured substrings that
+ When a match succeeds, \fBpcretest\fP outputs the list of captured substrings
- \fBpcre_exec()\fP returns, starting with number 0 for the string that matched
+ that \fBpcre_exec()\fP returns, starting with number 0 for the string that
- 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
  PCRE_ERROR_NOMATCH, and "Partial match:" followed by the partially matching
- substring when \fBpcre_exec()\fP returns PCRE_ERROR_PARTIAL. For any other
+ substring when \fBpcre_exec()\fP returns PCRE_ERROR_PARTIAL. (Note that this is
- returns, it outputs the PCRE negative error number. Here is an example of an
+ the entire substring that was inspected during the partial match; it may
- interactive \fBpcretest\fP run.
+ include characters before the actual match start if a lookbehind assertion,
+ \eK, \eb, or \eB was involved.) For any other return, \fBpcretest\fP outputs
+ the PCRE negative error number and a short descriptive phrase. If the error is
+ a failed UTF-8 string check, the byte offset of the start of the failing
+ character and the reason code are also output, provided that the size of the
+ output vector is at least two. Here is an example of an interactive
+ \fBpcretest\fP run.
  .sp
    $ pcretest
-   PCRE version 7.0 30-Nov-2006
+   PCRE version 8.13 2011-04-30
  .sp
      re> /^abc(\ed+)/
    data> abc123
-Line 500 
 interactive \fBpcretest\fP run.
+Line 598 
 interactive \fBpcretest\fP run.
    data> xyz
    No match
  .sp
- 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
- are not returned by \fBpcre_exec()\fP, and are not shown by \fBpcretest\fP. In
+ returned by \fBpcre_exec()\fP, and are not shown by \fBpcretest\fP. In the
- the following example, there are two capturing substrings, but when the first
+ following example, there are two capturing substrings, but when the first data
- 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
- unset substring is shown as "<unset>", as for the second data line.
+ substring is shown as "<unset>", as for the second data line.
  .sp
      re> /(a)|(b)/
    data> a
-Line 538 
 matching attempts are output in sequence
+Line 636 
 matching attempts are output in sequence
 : ipp
 : pp
  .sp
- "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
+ of a failure message (the offset 4 that is specified by \e>4 is past the end of
+ the subject string):
+ .sp
+     re> /xyz/
+   data> xyz\e>4
+   Error -24 (bad offset value)
  .P
  If any of the sequences \fB\eC\fP, \fB\eG\fP, or \fB\eL\fP are present in a
  data line that is successfully matched, the substrings extracted by the
-Line 571 
 the subject where there is at least one
+Line 675 
 the subject where there is at least one
  (Using the normal matching function on this data finds only "tang".) The
  longest matching string is always given first (and numbered zero). After a
  PCRE_ERROR_PARTIAL return, the output is "Partial match:", followed by the
- partially matching substring.
+ partially matching substring. (Note that this is the entire substring that was
+ inspected during the partial match; it may include characters before the actual
+ match start if a lookbehind assertion, \eK, \eb, or \eB was involved.)
  .P
  If \fB/g\fP is present on the pattern, the search for further matches resumes
  at the end of the longest match. For example:
-Line 641 
 example:
+Line 747 
 example:
    +10 ^ ^
 : E*
  .sp
+ If a pattern contains (*MARK) items, an additional line is output whenever
+ a change of latest mark is passed to the callout function. For example:
+ .sp
+     re> /a(*MARK:X)bc/C
+   data> abc
+   --->abc
+    +0 ^       a
+    +1 ^^      (*MARK:X)
+   +10 ^^      b
+   Latest Mark: X
+   +11 ^ ^     c
+   +12 ^  ^
+: abc
+ .sp
+ The mark changes between matching "a" and "b", but stays the same for the rest
+ of the match, so nothing more is output. If, as a result of backtracking, the
+ mark reverts to being unset, the text "<unset>" is output.
+ .P
  The callout function in \fBpcretest\fP returns zero (carry on matching) by
  default, but you can use a \eC item in a data line (as described above) to
- change this.
+ change this and other parameters of the callout.
  .P
  Inserting callouts can be helpful when using \fBpcretest\fP to check
  complicated regular expressions. For further information about callouts, see
-Line 673 
 function to distinguish printing and non
+Line 797 
 function to distinguish printing and non
  .rs
  .sp
  The facilities described in this section are not available when the POSIX
- inteface to PCRE is being used, that is, when the \fB/P\fP pattern modifier is
+ interface to PCRE is being used, that is, when the \fB/P\fP pattern modifier is
  specified.
  .P
  When the POSIX interface is not in use, you can cause \fBpcretest\fP to write a
-Line 687 
 See the
+Line 811 
 See the
  \fBpcreprecompile\fP
  .\"
  documentation for a discussion about saving and re-using compiled patterns.
+ Note that if the pattern was successfully studied with JIT optimization, the
+ JIT data cannot be saved.
  .P
  The data that is written is binary. The first eight bytes are the length of the
  compiled pattern data followed by the length of the optional study data, each
-Line 694 
 written as four bytes in big-endian orde
+Line 820 
 written as four bytes in big-endian orde
  there is no study data (either the pattern was not studied, or studying did not
  return any data), the second length is zero. The lengths are followed by an
  exact copy of the compiled pattern. If there is additional study data, this
- follows immediately after the compiled pattern. After writing the file,
+ (excluding any JIT data) follows immediately after the compiled pattern. After
- \fBpcretest\fP expects to read a new pattern.
+ writing the file, \fBpcretest\fP expects to read a new pattern.
  .P
- A saved pattern can be reloaded into \fBpcretest\fP by specifing < and a file
+ A saved pattern can be reloaded into \fBpcretest\fP by specifying < and a file
  name instead of a pattern. The name of the file must not contain a < character,
  as otherwise \fBpcretest\fP will interpret the line as a pattern delimited by <
  characters.
  For example:
  .sp
     re> </some/file
-   Compiled regex loaded from /some/file
+   Compiled pattern loaded from /some/file
    No study data
  .sp
- When the pattern has been loaded, \fBpcretest\fP proceeds to read data lines in
+ If the pattern was previously studied with the JIT optimization, the JIT
- the usual way.
+ information cannot be saved and restored, and so is lost. When the pattern has
+ been loaded, \fBpcretest\fP proceeds to read data lines in the usual way.
  .P
  You can copy a file written by \fBpcretest\fP to a different host and reload it
  there, even if the new host has opposite endianness to the one on which the
-Line 732 
 result is undefined.
+Line 859 
 result is undefined.
  .SH "SEE ALSO"
  .rs
  .sp
- \fBpcre\fP(3), \fBpcreapi\fP(3), \fBpcrecallout\fP(3), \fBpcrematching\fP(3),
+ \fBpcre\fP(3), \fBpcreapi\fP(3), \fBpcrecallout\fP(3), \fBpcrejit\fP,
- \fBpcrepartial\fP(d), \fBpcrepattern\fP(3), \fBpcreprecompile\fP(3).
+ \fBpcrematching\fP(3), \fBpcrepartial\fP(d), \fBpcrepattern\fP(3),
+ \fBpcreprecompile\fP(3).
  .
  .
  .SH AUTHOR
-Line 750 
 Cambridge CB2 3QH, England.
+Line 878 
 Cambridge CB2 3QH, England.
  .rs
  .sp
  .nf
- Last updated: 16 May 2010
+ Last updated: 02 December 2011
- Copyright (c) 1997-2010 University of Cambridge.
+ Copyright (c) 1997-2011 University of Cambridge.
  .fi

 Legend:



Removed from v.518
 


changed lines


 
Added in v.788
 Legend:



Removed from v.518
 


changed lines


 
Added in v.788
-Removed from v.518
+Added in v.788

webmaster@exim.org	ViewVC Help
Powered by ViewVC 1.1.12