Lines Matching refs:condition
21 3. A repeated conditional group whose condition was a reference by name caused
190 2. If an assertion condition was quantified with a minimum of zero (an odd
212 use instead. A conditional subpattern whose condition is a check on a
218 rare). The effect of the bug was that the condition was always treated as
232 11. If an assertion that was used as a condition was quantified with a minimum
286 when this assertion was used as a condition, for example (?(?!)a|b). In
616 10. A conditional group with an assertion condition could lead to PCRE
860 in the condition was skipped when pcre_exec() was used for matching.
863 condition for a conditional group, for compatibility with automatic
1682 25. If an assertion condition captured any substrings, they were not passed
2143 assertion subpattern, including such a pattern used as a condition,
2408 tested, and the overall condition is true if the condition is true for any
2424 "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
2456 condition was an assertion, PCRE could crash during matching, both with
3063 condition was not nested. This bug has been fixed.
3576 called as "subroutines" from elsewhere. In effect, the DEFINE condition
3580 as the simple (?(R). The condition is true only if the most recent
3711 13. Added the ability to use a named substring as a condition, using the
4854 23. Added a new extension: a condition to go with recursion. If a conditional
5273 2. Diagnose condition (?(0) as an error instead of crashing on matching.
5520 2. Added 4th condition (GPL supersedes if conflict) and created separate
