| 262 |
contains multiple copies of the same substring. If the \fB+\fP modifier appears |
contains multiple copies of the same substring. If the \fB+\fP modifier appears |
| 263 |
twice, the same action is taken for captured substrings. In each case the |
twice, the same action is taken for captured substrings. In each case the |
| 264 |
remainder is output on the following line with a plus character following the |
remainder is output on the following line with a plus character following the |
| 265 |
capture number. Note that this modifier must not immediately follow the /S |
capture number. Note that this modifier must not immediately follow the /S |
| 266 |
modifier because /S+ has another meaning. |
modifier because /S+ has another meaning. |
| 267 |
.P |
.P |
| 268 |
The \fB/=\fP modifier requests that the values of all potential captured |
The \fB/=\fP modifier requests that the values of all potential captured |
| 329 |
never studied, independently of \fB-s\fP. This feature is used in the test |
never studied, independently of \fB-s\fP. This feature is used in the test |
| 330 |
files in a few cases where the output is different when the pattern is studied. |
files in a few cases where the output is different when the pattern is studied. |
| 331 |
.P |
.P |
| 332 |
If the \fB/S\fP modifier is immediately followed by a + character, the call to |
If the \fB/S\fP modifier is immediately followed by a + character, the call to |
| 333 |
\fBpcre_study()\fP is made with the PCRE_STUDY_JIT_COMPILE option, requesting |
\fBpcre_study()\fP is made with the PCRE_STUDY_JIT_COMPILE option, requesting |
| 334 |
just-in-time optimization support if it is available. Note that there is also a |
just-in-time optimization support if it is available. Note that there is also a |
| 335 |
\fB/+\fP modifier; it must not be given immediately after \fB/S\fP because this |
\fB/+\fP modifier; it must not be given immediately after \fB/S\fP because this |
| 336 |
will be misinterpreted. If JIT studying is successful, it will automatically be |
will be misinterpreted. If JIT studying is successful, it will automatically be |
| 337 |
used when \fBpcre_exec()\fP is run, except when incompatible run-time options |
used when \fBpcre_exec()\fP is run, except when incompatible run-time options |
| 338 |
are specified. These include the partial matching options; a complete list is |
are specified. These include the partial matching options; a complete list is |
| 339 |
given in the |
given in the |
| 340 |
.\" HREF |
.\" HREF |
| 341 |
\fBpcrejit\fP |
\fBpcrejit\fP |
| 342 |
.\" |
.\" |
| 343 |
documentation. See also the \fB\eJ\fP escape sequence below for a way of |
documentation. See also the \fB\eJ\fP escape sequence below for a way of |
| 344 |
setting the size of the JIT stack. |
setting the size of the JIT stack. |
| 345 |
.P |
.P |
| 346 |
The \fB/T\fP modifier must be followed by a single digit. It causes a specific |
The \fB/T\fP modifier must be followed by a single digit. It causes a specific |
| 439 |
ated by next non-alphanumeric character) |
ated by next non-alphanumeric character) |
| 440 |
.\" JOIN |
.\" JOIN |
| 441 |
\eJdd set up a JIT stack of dd kilobytes maximum (any |
\eJdd set up a JIT stack of dd kilobytes maximum (any |
| 442 |
number of digits) |
number of digits) |
| 443 |
.\" JOIN |
.\" JOIN |
| 444 |
\eL call pcre_get_substringlist() after a |
\eL call pcre_get_substringlist() after a |
| 445 |
successful match |
successful match |
| 507 |
input. |
input. |
| 508 |
.P |
.P |
| 509 |
The \fB\eJ\fP escape provides a way of setting the maximum stack size that is |
The \fB\eJ\fP escape provides a way of setting the maximum stack size that is |
| 510 |
used by the just-in-time optimization code. It is ignored if JIT optimization |
used by the just-in-time optimization code. It is ignored if JIT optimization |
| 511 |
is not being used. Providing a stack that is larger than the default 32K is |
is not being used. Providing a stack that is larger than the default 32K is |
| 512 |
necessary only for very complicated patterns. |
necessary only for very complicated patterns. |
| 513 |
.P |
.P |
| 514 |
If \eM is present, \fBpcretest\fP calls \fBpcre_exec()\fP several times, with |
If \eM is present, \fBpcretest\fP calls \fBpcre_exec()\fP several times, with |
| 515 |
different values in the \fImatch_limit\fP and \fImatch_limit_recursion\fP |
different values in the \fImatch_limit\fP and \fImatch_limit_recursion\fP |
| 516 |
fields of the \fBpcre_extra\fP data structure, until it finds the minimum |
fields of the \fBpcre_extra\fP data structure, until it finds the minimum |
| 517 |
numbers for each parameter that allow \fBpcre_exec()\fP to complete without |
numbers for each parameter that allow \fBpcre_exec()\fP to complete without |
| 518 |
error. Because this is testing a specific feature of the normal interpretive |
error. Because this is testing a specific feature of the normal interpretive |
| 519 |
\fBpcre_exec()\fP execution, the use of any JIT optimization that might have |
\fBpcre_exec()\fP execution, the use of any JIT optimization that might have |
| 520 |
been set up by the \fB/S+\fP qualifier of \fB-s+\fP option is disabled. |
been set up by the \fB/S+\fP qualifier of \fB-s+\fP option is disabled. |
| 521 |
.P |
.P |
| 522 |
The \fImatch_limit\fP number is a measure of the amount of backtracking |
The \fImatch_limit\fP number is a measure of the amount of backtracking |
| 795 |
.sp |
.sp |
| 796 |
The facilities described in this section are not available when the POSIX |
The facilities described in this section are not available when the POSIX |
| 797 |
interface 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 |
| 798 |
specified. |
specified. |
| 799 |
.P |
.P |
| 800 |
When the POSIX interface is not in use, you can cause \fBpcretest\fP to write a |
When the POSIX interface is not in use, you can cause \fBpcretest\fP to write a |
| 801 |
compiled pattern to a file, by following the modifiers with > and a file name. |
compiled pattern to a file, by following the modifiers with > and a file name. |