| 40 |
-i Behave as if each regex has the /I modifier; information |
-i Behave as if each regex has the /I modifier; information |
| 41 |
about the compiled pattern is given after compilation. |
about the compiled pattern is given after compilation. |
| 42 |
|
|
| 43 |
-m Output the size of each compiled pattern after it has been |
-M Behave as if each data line contains the \M escape sequence; |
| 44 |
compiled. This is equivalent to adding /M to each regular |
this causes PCRE to discover the minimum MATCH_LIMIT and |
| 45 |
expression. For compatibility with earlier versions of |
MATCH_LIMIT_RECURSION settings by calling pcre_exec() repeat- |
| 46 |
|
edly with different limits. |
| 47 |
|
|
| 48 |
|
-m Output the size of each compiled pattern after it has been |
| 49 |
|
compiled. This is equivalent to adding /M to each regular |
| 50 |
|
expression. For compatibility with earlier versions of |
| 51 |
pcretest, -s is a synonym for -m. |
pcretest, -s is a synonym for -m. |
| 52 |
|
|
| 53 |
-o osize Set the number of elements in the output vector that is used |
-o osize Set the number of elements in the output vector that is used |
| 54 |
when calling pcre_exec() or pcre_dfa_exec() to be osize. The |
when calling pcre_exec() or pcre_dfa_exec() to be osize. The |
| 55 |
default value is 45, which is enough for 14 capturing subex- |
default value is 45, which is enough for 14 capturing subex- |
| 56 |
pressions for pcre_exec() or 22 different matches for |
pressions for pcre_exec() or 22 different matches for |
| 57 |
pcre_dfa_exec(). The vector size can be changed for individ- |
pcre_dfa_exec(). The vector size can be changed for individ- |
| 58 |
ual matching calls by including \O in the data line (see |
ual matching calls by including \O in the data line (see |
| 59 |
below). |
below). |
| 60 |
|
|
| 61 |
-p Behave as if each regex has the /P modifier; the POSIX wrap- |
-p Behave as if each regex has the /P modifier; the POSIX wrap- |
| 62 |
per API is used to call PCRE. None of the other options has |
per API is used to call PCRE. None of the other options has |
| 63 |
any effect when -p is set. |
any effect when -p is set. |
| 64 |
|
|
| 65 |
-q Do not output the version number of pcretest at the start of |
-q Do not output the version number of pcretest at the start of |
| 66 |
execution. |
execution. |
| 67 |
|
|
| 68 |
-S size On Unix-like systems, set the size of the runtime stack to |
-S size On Unix-like systems, set the size of the runtime stack to |
| 69 |
size megabytes. |
size megabytes. |
| 70 |
|
|
| 71 |
-t Run each compile, study, and match many times with a timer, |
-t Run each compile, study, and match many times with a timer, |
| 72 |
and output resulting time per compile or match (in millisec- |
and output resulting time per compile or match (in millisec- |
| 73 |
onds). Do not set -m with -t, because you will then get the |
onds). Do not set -m with -t, because you will then get the |
| 74 |
size output a zillion times, and the timing will be dis- |
size output a zillion times, and the timing will be dis- |
| 75 |
torted. You can control the number of iterations that are |
torted. You can control the number of iterations that are |
| 76 |
used for timing by following -t with a number (as a separate |
used for timing by following -t with a number (as a separate |
| 77 |
item on the command line). For example, "-t 1000" would iter- |
item on the command line). For example, "-t 1000" would iter- |
| 78 |
ate 1000 times. The default is to iterate 500000 times. |
ate 1000 times. The default is to iterate 500000 times. |
| 79 |
|
|
| 83 |
|
|
| 84 |
DESCRIPTION |
DESCRIPTION |
| 85 |
|
|
| 86 |
If pcretest is given two filename arguments, it reads from the first |
If pcretest is given two filename arguments, it reads from the first |
| 87 |
and writes to the second. If it is given only one filename argument, it |
and writes to the second. If it is given only one filename argument, it |
| 88 |
reads from that file and writes to stdout. Otherwise, it reads from |
reads from that file and writes to stdout. Otherwise, it reads from |
| 89 |
stdin and writes to stdout, and prompts for each line of input, using |
stdin and writes to stdout, and prompts for each line of input, using |
| 90 |
"re>" to prompt for regular expressions, and "data>" to prompt for data |
"re>" to prompt for regular expressions, and "data>" to prompt for data |
| 91 |
lines. |
lines. |
| 92 |
|
|
| 93 |
When pcretest is built, a configuration option can specify that it |
When pcretest is built, a configuration option can specify that it |
| 94 |
should be linked with the libreadline library. When this is done, if |
should be linked with the libreadline library. When this is done, if |
| 95 |
the input is from a terminal, it is read using the readline() function. |
the input is from a terminal, it is read using the readline() function. |
| 96 |
This provides line-editing and history facilities. The output from the |
This provides line-editing and history facilities. The output from the |
| 97 |
-help option states whether or not readline() will be used. |
-help option states whether or not readline() will be used. |
| 98 |
|
|
| 99 |
The program handles any number of sets of input on a single input file. |
The program handles any number of sets of input on a single input file. |
| 100 |
Each set starts with a regular expression, and continues with any num- |
Each set starts with a regular expression, and continues with any num- |
| 101 |
ber of data lines to be matched against the pattern. |
ber of data lines to be matched against the pattern. |
| 102 |
|
|
| 103 |
Each data line is matched separately and independently. If you want to |
Each data line is matched separately and independently. If you want to |
| 104 |
do multi-line matches, you have to use the \n escape sequence (or \r or |
do multi-line matches, you have to use the \n escape sequence (or \r or |
| 105 |
\r\n, etc., depending on the newline setting) in a single line of input |
\r\n, etc., depending on the newline setting) in a single line of input |
| 106 |
to encode the newline sequences. There is no limit on the length of |
to encode the newline sequences. There is no limit on the length of |
| 107 |
data lines; the input buffer is automatically extended if it is too |
data lines; the input buffer is automatically extended if it is too |
| 108 |
small. |
small. |
| 109 |
|
|
| 110 |
An empty line signals the end of the data lines, at which point a new |
An empty line signals the end of the data lines, at which point a new |
| 111 |
regular expression is read. The regular expressions are given enclosed |
regular expression is read. The regular expressions are given enclosed |
| 112 |
in any non-alphanumeric delimiters other than backslash, for example: |
in any non-alphanumeric delimiters other than backslash, for example: |
| 113 |
|
|
| 114 |
/(a|bc)x+yz/ |
/(a|bc)x+yz/ |
| 115 |
|
|
| 116 |
White space before the initial delimiter is ignored. A regular expres- |
White space before the initial delimiter is ignored. A regular expres- |
| 117 |
sion may be continued over several input lines, in which case the new- |
sion may be continued over several input lines, in which case the new- |
| 118 |
line characters are included within it. It is possible to include the |
line characters are included within it. It is possible to include the |
| 119 |
delimiter within the pattern by escaping it, for example |
delimiter within the pattern by escaping it, for example |
| 120 |
|
|
| 121 |
/abc\/def/ |
/abc\/def/ |
| 122 |
|
|
| 123 |
If you do so, the escape and the delimiter form part of the pattern, |
If you do so, the escape and the delimiter form part of the pattern, |
| 124 |
but since delimiters are always non-alphanumeric, this does not affect |
but since delimiters are always non-alphanumeric, this does not affect |
| 125 |
its interpretation. If the terminating delimiter is immediately fol- |
its interpretation. If the terminating delimiter is immediately fol- |
| 126 |
lowed by a backslash, for example, |
lowed by a backslash, for example, |
| 127 |
|
|
| 128 |
/abc/\ |
/abc/\ |
| 129 |
|
|
| 130 |
then a backslash is added to the end of the pattern. This is done to |
then a backslash is added to the end of the pattern. This is done to |
| 131 |
provide a way of testing the error condition that arises if a pattern |
provide a way of testing the error condition that arises if a pattern |
| 132 |
finishes with a backslash, because |
finishes with a backslash, because |
| 133 |
|
|
| 134 |
/abc\/ |
/abc\/ |
| 135 |
|
|
| 136 |
is interpreted as the first line of a pattern that starts with "abc/", |
is interpreted as the first line of a pattern that starts with "abc/", |
| 137 |
causing pcretest to read the next line as a continuation of the regular |
causing pcretest to read the next line as a continuation of the regular |
| 138 |
expression. |
expression. |
| 139 |
|
|
| 140 |
|
|
| 141 |
PATTERN MODIFIERS |
PATTERN MODIFIERS |
| 142 |
|
|
| 143 |
A pattern may be followed by any number of modifiers, which are mostly |
A pattern may be followed by any number of modifiers, which are mostly |
| 144 |
single characters. Following Perl usage, these are referred to below |
single characters. Following Perl usage, these are referred to below |
| 145 |
as, for example, "the /i modifier", even though the delimiter of the |
as, for example, "the /i modifier", even though the delimiter of the |
| 146 |
pattern need not always be a slash, and no slash is used when writing |
pattern need not always be a slash, and no slash is used when writing |
| 147 |
modifiers. Whitespace may appear between the final pattern delimiter |
modifiers. Whitespace may appear between the final pattern delimiter |
| 148 |
and the first modifier, and between the modifiers themselves. |
and the first modifier, and between the modifiers themselves. |
| 149 |
|
|
| 150 |
The /i, /m, /s, and /x modifiers set the PCRE_CASELESS, PCRE_MULTILINE, |
The /i, /m, /s, and /x modifiers set the PCRE_CASELESS, PCRE_MULTILINE, |
| 151 |
PCRE_DOTALL, or PCRE_EXTENDED options, respectively, when pcre_com- |
PCRE_DOTALL, or PCRE_EXTENDED options, respectively, when pcre_com- |
| 152 |
pile() is called. These four modifier letters have the same effect as |
pile() is called. These four modifier letters have the same effect as |
| 153 |
they do in Perl. For example: |
they do in Perl. For example: |
| 154 |
|
|
| 155 |
/caseless/i |
/caseless/i |
| 165 |
/N PCRE_NO_AUTO_CAPTURE |
/N PCRE_NO_AUTO_CAPTURE |
| 166 |
/U PCRE_UNGREEDY |
/U PCRE_UNGREEDY |
| 167 |
/X PCRE_EXTRA |
/X PCRE_EXTRA |
| 168 |
|
/<JS> PCRE_JAVASCRIPT_COMPAT |
| 169 |
/<cr> PCRE_NEWLINE_CR |
/<cr> PCRE_NEWLINE_CR |
| 170 |
/<lf> PCRE_NEWLINE_LF |
/<lf> PCRE_NEWLINE_LF |
| 171 |
/<crlf> PCRE_NEWLINE_CRLF |
/<crlf> PCRE_NEWLINE_CRLF |
| 174 |
/<bsr_anycrlf> PCRE_BSR_ANYCRLF |
/<bsr_anycrlf> PCRE_BSR_ANYCRLF |
| 175 |
/<bsr_unicode> PCRE_BSR_UNICODE |
/<bsr_unicode> PCRE_BSR_UNICODE |
| 176 |
|
|
| 177 |
Those specifying line ending sequences are literal strings as shown, |
Those specifying line ending sequences are literal strings as shown, |
| 178 |
but the letters can be in either case. This example sets multiline |
but the letters can be in either case. This example sets multiline |
| 179 |
matching with CRLF as the line ending sequence: |
matching with CRLF as the line ending sequence: |
| 180 |
|
|
| 181 |
/^abc/m<crlf> |
/^abc/m<crlf> |
| 182 |
|
|
| 183 |
Details of the meanings of these PCRE options are given in the pcreapi |
Details of the meanings of these PCRE options are given in the pcreapi |
| 184 |
documentation. |
documentation. |
| 185 |
|
|
| 186 |
Finding all matches in a string |
Finding all matches in a string |
| 187 |
|
|
| 188 |
Searching for all possible matches within each subject string can be |
Searching for all possible matches within each subject string can be |
| 189 |
requested by the /g or /G modifier. After finding a match, PCRE is |
requested by the /g or /G modifier. After finding a match, PCRE is |
| 190 |
called again to search the remainder of the subject string. The differ- |
called again to search the remainder of the subject string. The differ- |
| 191 |
ence between /g and /G is that the former uses the startoffset argument |
ence between /g and /G is that the former uses the startoffset argument |
| 192 |
to pcre_exec() to start searching at a new point within the entire |
to pcre_exec() to start searching at a new point within the entire |
| 193 |
string (which is in effect what Perl does), whereas the latter passes |
string (which is in effect what Perl does), whereas the latter passes |
| 194 |
over a shortened substring. This makes a difference to the matching |
over a shortened substring. This makes a difference to the matching |
| 195 |
process if the pattern begins with a lookbehind assertion (including \b |
process if the pattern begins with a lookbehind assertion (including \b |
| 196 |
or \B). |
or \B). |
| 197 |
|
|
| 198 |
If any call to pcre_exec() in a /g or /G sequence matches an empty |
If any call to pcre_exec() in a /g or /G sequence matches an empty |
| 199 |
string, the next call is done with the PCRE_NOTEMPTY and PCRE_ANCHORED |
string, the next call is done with the PCRE_NOTEMPTY and PCRE_ANCHORED |
| 200 |
flags set in order to search for another, non-empty, match at the same |
flags set in order to search for another, non-empty, match at the same |
| 201 |
point. If this second match fails, the start offset is advanced by |
point. If this second match fails, the start offset is advanced by |
| 202 |
one, and the normal match is retried. This imitates the way Perl han- |
one, and the normal match is retried. This imitates the way Perl han- |
| 203 |
dles such cases when using the /g modifier or the split() function. |
dles such cases when using the /g modifier or the split() function. |
| 204 |
|
|
| 205 |
Other modifiers |
Other modifiers |
| 250 |
The /S modifier causes pcre_study() to be called after the expression |
The /S modifier causes pcre_study() to be called after the expression |
| 251 |
has been compiled, and the results used when the expression is matched. |
has been compiled, and the results used when the expression is matched. |
| 252 |
|
|
| 253 |
The /M modifier causes the size of memory block used to hold the com- |
The /M modifier causes the size of memory block used to hold the com- |
| 254 |
piled pattern to be output. |
piled pattern to be output. |
| 255 |
|
|
| 256 |
The /P modifier causes pcretest to call PCRE via the POSIX wrapper API |
The /P modifier causes pcretest to call PCRE via the POSIX wrapper API |
| 257 |
rather than its native API. When this is done, all other modifiers |
rather than its native API. When this is done, all other modifiers |
| 258 |
except /i, /m, and /+ are ignored. REG_ICASE is set if /i is present, |
except /i, /m, and /+ are ignored. REG_ICASE is set if /i is present, |
| 259 |
and REG_NEWLINE is set if /m is present. The wrapper functions force |
and REG_NEWLINE is set if /m is present. The wrapper functions force |
| 260 |
PCRE_DOLLAR_ENDONLY always, and PCRE_DOTALL unless REG_NEWLINE is set. |
PCRE_DOLLAR_ENDONLY always, and PCRE_DOTALL unless REG_NEWLINE is set. |
| 261 |
|
|
| 262 |
The /8 modifier causes pcretest to call PCRE with the PCRE_UTF8 option |
The /8 modifier causes pcretest to call PCRE with the PCRE_UTF8 option |
| 263 |
set. This turns on support for UTF-8 character handling in PCRE, pro- |
set. This turns on support for UTF-8 character handling in PCRE, pro- |
| 326 |
or pcre_dfa_exec() |
or pcre_dfa_exec() |
| 327 |
\Odd set the size of the output vector passed to |
\Odd set the size of the output vector passed to |
| 328 |
pcre_exec() to dd (any number of digits) |
pcre_exec() to dd (any number of digits) |
| 329 |
\P pass the PCRE_PARTIAL option to pcre_exec() |
\P pass the PCRE_PARTIAL_SOFT option to pcre_exec() |
| 330 |
or pcre_dfa_exec() |
or pcre_dfa_exec(); if used twice, pass the |
| 331 |
|
PCRE_PARTIAL_HARD option |
| 332 |
\Qdd set the PCRE_MATCH_LIMIT_RECURSION limit to dd |
\Qdd set the PCRE_MATCH_LIMIT_RECURSION limit to dd |
| 333 |
(any number of digits) |
(any number of digits) |
| 334 |
\R pass the PCRE_DFA_RESTART option to pcre_dfa_exec() |
\R pass the PCRE_DFA_RESTART option to pcre_dfa_exec() |
| 414 |
When a match succeeds, pcretest outputs the list of captured substrings |
When a match succeeds, pcretest outputs the list of captured substrings |
| 415 |
that pcre_exec() returns, starting with number 0 for the string that |
that pcre_exec() returns, starting with number 0 for the string that |
| 416 |
matched the whole pattern. Otherwise, it outputs "No match" or "Partial |
matched the whole pattern. Otherwise, it outputs "No match" or "Partial |
| 417 |
match" when pcre_exec() returns PCRE_ERROR_NOMATCH or PCRE_ERROR_PAR- |
match:" followed by the partially matching substring when pcre_exec() |
| 418 |
TIAL, respectively, and otherwise the PCRE negative error number. Here |
returns PCRE_ERROR_NOMATCH or PCRE_ERROR_PARTIAL, respectively, and |
| 419 |
is an example of an interactive pcretest run. |
otherwise the PCRE negative error number. Here is an example of an |
| 420 |
|
interactive pcretest run. |
| 421 |
|
|
| 422 |
$ pcretest |
$ pcretest |
| 423 |
PCRE version 7.0 30-Nov-2006 |
PCRE version 7.0 30-Nov-2006 |
| 429 |
data> xyz |
data> xyz |
| 430 |
No match |
No match |
| 431 |
|
|
| 432 |
Note that unset capturing substrings that are not followed by one that |
Note that unset capturing substrings that are not followed by one that |
| 433 |
is set are not returned by pcre_exec(), and are not shown by pcretest. |
is set are not returned by pcre_exec(), and are not shown by pcretest. |
| 434 |
In the following example, there are two capturing substrings, but when |
In the following example, there are two capturing substrings, but when |
| 435 |
the first data line is matched, the second, unset substring is not |
the first data line is matched, the second, unset substring is not |
| 436 |
shown. An "internal" unset substring is shown as "<unset>", as for the |
shown. An "internal" unset substring is shown as "<unset>", as for the |
| 437 |
second data line. |
second data line. |
| 438 |
|
|
| 439 |
re> /(a)|(b)/ |
re> /(a)|(b)/ |
| 445 |
1: <unset> |
1: <unset> |
| 446 |
2: b |
2: b |
| 447 |
|
|
| 448 |
If the strings contain any non-printing characters, they are output as |
If the strings contain any non-printing characters, they are output as |
| 449 |
\0x escapes, or as \x{...} escapes if the /8 modifier was present on |
\0x escapes, or as \x{...} escapes if the /8 modifier was present on |
| 450 |
the pattern. See below for the definition of non-printing characters. |
the pattern. See below for the definition of non-printing characters. |
| 451 |
If the pattern has the /+ modifier, the output for substring 0 is fol- |
If the pattern has the /+ modifier, the output for substring 0 is fol- |
| 452 |
lowed by the the rest of the subject string, identified by "0+" like |
lowed by the the rest of the subject string, identified by "0+" like |
| 453 |
this: |
this: |
| 454 |
|
|
| 455 |
re> /cat/+ |
re> /cat/+ |
| 457 |
0: cat |
0: cat |
| 458 |
0+ aract |
0+ aract |
| 459 |
|
|
| 460 |
If the pattern has the /g or /G modifier, the results of successive |
If the pattern has the /g or /G modifier, the results of successive |
| 461 |
matching attempts are output in sequence, like this: |
matching attempts are output in sequence, like this: |
| 462 |
|
|
| 463 |
re> /\Bi(\w\w)/g |
re> /\Bi(\w\w)/g |
| 471 |
|
|
| 472 |
"No match" is output only if the first match attempt fails. |
"No match" is output only if the first match attempt fails. |
| 473 |
|
|
| 474 |
If any of the sequences \C, \G, or \L are present in a data line that |
If any of the sequences \C, \G, or \L are present in a data line that |
| 475 |
is successfully matched, the substrings extracted by the convenience |
is successfully matched, the substrings extracted by the convenience |
| 476 |
functions are output with C, G, or L after the string number instead of |
functions are output with C, G, or L after the string number instead of |
| 477 |
a colon. This is in addition to the normal full list. The string length |
a colon. This is in addition to the normal full list. The string length |
| 478 |
(that is, the return from the extraction function) is given in paren- |
(that is, the return from the extraction function) is given in paren- |
| 479 |
theses after each string for \C and \G. |
theses after each string for \C and \G. |
| 480 |
|
|
| 481 |
Note that whereas patterns can be continued over several lines (a plain |
Note that whereas patterns can be continued over several lines (a plain |
| 482 |
">" prompt is used for continuations), data lines may not. However new- |
">" prompt is used for continuations), data lines may not. However new- |
| 483 |
lines can be included in data by means of the \n escape (or \r, \r\n, |
lines can be included in data by means of the \n escape (or \r, \r\n, |
| 484 |
etc., depending on the newline sequence setting). |
etc., depending on the newline sequence setting). |
| 485 |
|
|
| 486 |
|
|
| 487 |
OUTPUT FROM THE ALTERNATIVE MATCHING FUNCTION |
OUTPUT FROM THE ALTERNATIVE MATCHING FUNCTION |
| 488 |
|
|
| 489 |
When the alternative matching function, pcre_dfa_exec(), is used (by |
When the alternative matching function, pcre_dfa_exec(), is used (by |
| 490 |
means of the \D escape sequence or the -dfa command line option), the |
means of the \D escape sequence or the -dfa command line option), the |
| 491 |
output consists of a list of all the matches that start at the first |
output consists of a list of all the matches that start at the first |
| 492 |
point in the subject where there is at least one match. For example: |
point in the subject where there is at least one match. For example: |
| 493 |
|
|
| 494 |
re> /(tang|tangerine|tan)/ |
re> /(tang|tangerine|tan)/ |
| 497 |
1: tang |
1: tang |
| 498 |
2: tan |
2: tan |
| 499 |
|
|
| 500 |
(Using the normal matching function on this data finds only "tang".) |
(Using the normal matching function on this data finds only "tang".) |
| 501 |
The longest matching string is always given first (and numbered zero). |
The longest matching string is always given first (and numbered zero). |
| 502 |
|
After a PCRE_ERROR_PARTIAL return, the output is "Partial match:", fol- |
| 503 |
|
lowed by the partially matching substring. |
| 504 |
|
|
| 505 |
If /g is present on the pattern, the search for further matches resumes |
If /g is present on the pattern, the search for further matches resumes |
| 506 |
at the end of the longest match. For example: |
at the end of the longest match. For example: |
| 590 |
|
|
| 591 |
SAVING AND RELOADING COMPILED PATTERNS |
SAVING AND RELOADING COMPILED PATTERNS |
| 592 |
|
|
| 593 |
The facilities described in this section are not available when the |
The facilities described in this section are not available when the |
| 594 |
POSIX inteface to PCRE is being used, that is, when the /P pattern mod- |
POSIX inteface to PCRE is being used, that is, when the /P pattern mod- |
| 595 |
ifier is specified. |
ifier is specified. |
| 596 |
|
|
| 597 |
When the POSIX interface is not in use, you can cause pcretest to write |
When the POSIX interface is not in use, you can cause pcretest to write |
| 598 |
a compiled pattern to a file, by following the modifiers with > and a |
a compiled pattern to a file, by following the modifiers with > and a |
| 599 |
file name. For example: |
file name. For example: |
| 600 |
|
|
| 601 |
/pattern/im >/some/file |
/pattern/im >/some/file |
| 602 |
|
|
| 603 |
See the pcreprecompile documentation for a discussion about saving and |
See the pcreprecompile documentation for a discussion about saving and |
| 604 |
re-using compiled patterns. |
re-using compiled patterns. |
| 605 |
|
|
| 606 |
The data that is written is binary. The first eight bytes are the |
The data that is written is binary. The first eight bytes are the |
| 607 |
length of the compiled pattern data followed by the length of the |
length of the compiled pattern data followed by the length of the |
| 608 |
optional study data, each written as four bytes in big-endian order |
optional study data, each written as four bytes in big-endian order |
| 609 |
(most significant byte first). If there is no study data (either the |
(most significant byte first). If there is no study data (either the |
| 610 |
pattern was not studied, or studying did not return any data), the sec- |
pattern was not studied, or studying did not return any data), the sec- |
| 611 |
ond length is zero. The lengths are followed by an exact copy of the |
ond length is zero. The lengths are followed by an exact copy of the |
| 612 |
compiled pattern. If there is additional study data, this follows imme- |
compiled pattern. If there is additional study data, this follows imme- |
| 613 |
diately after the compiled pattern. After writing the file, pcretest |
diately after the compiled pattern. After writing the file, pcretest |
| 614 |
expects to read a new pattern. |
expects to read a new pattern. |
| 615 |
|
|
| 616 |
A saved pattern can be reloaded into pcretest by specifing < and a file |
A saved pattern can be reloaded into pcretest by specifing < and a file |
| 617 |
name instead of a pattern. The name of the file must not contain a < |
name instead of a pattern. The name of the file must not contain a < |
| 618 |
character, as otherwise pcretest will interpret the line as a pattern |
character, as otherwise pcretest will interpret the line as a pattern |
| 619 |
delimited by < characters. For example: |
delimited by < characters. For example: |
| 620 |
|
|
| 621 |
re> </some/file |
re> </some/file |
| 622 |
Compiled regex loaded from /some/file |
Compiled regex loaded from /some/file |
| 623 |
No study data |
No study data |
| 624 |
|
|
| 625 |
When the pattern has been loaded, pcretest proceeds to read data lines |
When the pattern has been loaded, pcretest proceeds to read data lines |
| 626 |
in the usual way. |
in the usual way. |
| 627 |
|
|
| 628 |
You can copy a file written by pcretest to a different host and reload |
You can copy a file written by pcretest to a different host and reload |
| 629 |
it there, even if the new host has opposite endianness to the one on |
it there, even if the new host has opposite endianness to the one on |
| 630 |
which the pattern was compiled. For example, you can compile on an i86 |
which the pattern was compiled. For example, you can compile on an i86 |
| 631 |
machine and run on a SPARC machine. |
machine and run on a SPARC machine. |
| 632 |
|
|
| 633 |
File names for saving and reloading can be absolute or relative, but |
File names for saving and reloading can be absolute or relative, but |
| 634 |
note that the shell facility of expanding a file name that starts with |
note that the shell facility of expanding a file name that starts with |
| 635 |
a tilde (~) is not available. |
a tilde (~) is not available. |
| 636 |
|
|
| 637 |
The ability to save and reload files in pcretest is intended for test- |
The ability to save and reload files in pcretest is intended for test- |
| 638 |
ing and experimentation. It is not intended for production use because |
ing and experimentation. It is not intended for production use because |
| 639 |
only a single pattern can be written to a file. Furthermore, there is |
only a single pattern can be written to a file. Furthermore, there is |
| 640 |
no facility for supplying custom character tables for use with a |
no facility for supplying custom character tables for use with a |
| 641 |
reloaded pattern. If the original pattern was compiled with custom |
reloaded pattern. If the original pattern was compiled with custom |
| 642 |
tables, an attempt to match a subject string using a reloaded pattern |
tables, an attempt to match a subject string using a reloaded pattern |
| 643 |
is likely to cause pcretest to crash. Finally, if you attempt to load |
is likely to cause pcretest to crash. Finally, if you attempt to load |
| 644 |
a file that is not in the correct format, the result is undefined. |
a file that is not in the correct format, the result is undefined. |
| 645 |
|
|
| 646 |
|
|
| 647 |
SEE ALSO |
SEE ALSO |
| 648 |
|
|
| 649 |
pcre(3), pcreapi(3), pcrecallout(3), pcrematching(3), pcrepartial(d), |
pcre(3), pcreapi(3), pcrecallout(3), pcrematching(3), pcrepartial(d), |
| 650 |
pcrepattern(3), pcreprecompile(3). |
pcrepattern(3), pcreprecompile(3). |
| 651 |
|
|
| 652 |
|
|
| 659 |
|
|
| 660 |
REVISION |
REVISION |
| 661 |
|
|
| 662 |
Last updated: 18 December 2007 |
Last updated: 29 August 2009 |
| 663 |
Copyright (c) 1997-2007 University of Cambridge. |
Copyright (c) 1997-2009 University of Cambridge. |