diff options
| author | Andrei Zmievski <andrei@php.net> | 2002-10-15 13:59:58 +0000 |
|---|---|---|
| committer | Andrei Zmievski <andrei@php.net> | 2002-10-15 13:59:58 +0000 |
| commit | c65c18269302de59e7b657bce2e30b2726935d73 (patch) | |
| tree | 168fe26908b277d60d539ca10474e43a5c47b242 /ext/pcre/pcrelib/doc/Tech.Notes | |
| parent | b4348434be0c5e94cc09ba342660c81e0fc416bb (diff) | |
| download | php-git-c65c18269302de59e7b657bce2e30b2726935d73.tar.gz | |
Upgrade to version 3.92.
Diffstat (limited to 'ext/pcre/pcrelib/doc/Tech.Notes')
| -rw-r--r-- | ext/pcre/pcrelib/doc/Tech.Notes | 26 |
1 files changed, 13 insertions, 13 deletions
diff --git a/ext/pcre/pcrelib/doc/Tech.Notes b/ext/pcre/pcrelib/doc/Tech.Notes index f5ca280115..df8f21892f 100644 --- a/ext/pcre/pcrelib/doc/Tech.Notes +++ b/ext/pcre/pcrelib/doc/Tech.Notes @@ -231,23 +231,23 @@ Conditional subpatterns These are like other subpatterns, but they start with the opcode OP_COND. If the condition is a back reference, this is stored at the start of the subpattern using the opcode OP_CREF followed by two bytes containing the -reference number. Otherwise, a conditional subpattern will always start with -one of the assertions. +reference number. If the condition is "in recursion" (coded as "(?(R)"), the +same scheme is used, with a "reference number" of 0xffff. Otherwise, a +conditional subpattern always starts with one of the assertions. Changing options ---------------- -If any of the /i, /m, or /s options are changed within a parenthesized group, -an OP_OPT opcode is compiled, followed by one byte containing the new settings -of these flags. If there are several alternatives in a group, there is an -occurrence of OP_OPT at the start of all those following the first options -change, to set appropriate options for the start of the alternative. -Immediately after the end of the group there is another such item to reset the -flags to their previous values. Other changes of flag within the pattern can be -handled entirely at compile time, and so do not cause anything to be put into -the compiled data. - +If any of the /i, /m, or /s options are changed within a pattern, an OP_OPT +opcode is compiled, followed by one byte containing the new settings of these +flags. If there are several alternatives, there is an occurrence of OP_OPT at +the start of all those following the first options change, to set appropriate +options for the start of the alternative. Immediately after the end of the +group there is another such item to reset the flags to their previous values. A +change of flag right at the very start of the pattern can be handled entirely +at compile time, and so does not cause anything to be put into the compiled +data. Philip Hazel -August 2001 +August 2002 |