Lines Matching refs:assertion
34 6. A lookbehind assertion within a set of mutually recursive subpatterns could
75 assertion which itself contained a forward reference caused buffer
143 37. Fix two assertion fails in JIT. These issues were found by Karl Skomski
190 2. If an assertion condition was quantified with a minimum of zero (an odd
232 11. If an assertion that was used as a condition was quantified with a minimum
279 26. Fix JIT compilation of conditional blocks, which assertion
285 28. The assertion (?!) is optimized to (*FAIL). This was not handled correctly
286 when this assertion was used as a condition, for example (?(?!)a|b). In
312 assertion after (?(. The code was failing to check the character after
313 (?(?< for the ! or = that would indicate a lookbehind assertion. This bug
321 35. A mutual recursion within a lookbehind assertion such as (?<=((?2))((?1)))
323 lookbehind assertion. This bug was discovered by the LLVM fuzzer.
325 36. The use of \K in a positive lookbehind assertion in a non-anchored pattern
459 4. A pattern such as (?=ab\K) that uses \K in an assertion can set the start
616 10. A conditional group with an assertion condition could lead to PCRE
858 there was a conditional group that depended on an assertion, if the
859 assertion was false, the callout that immediately followed the alternation
862 23. Allow an explicit callout to be inserted before an assertion that is the
1161 14. As documented, (*COMMIT) is now confined to within a positive assertion.
1659 21. When (*ACCEPT) was used in an assertion that matched an empty string and
1660 PCRE_NOTEMPTY was set, PCRE applied the non-empty test to the assertion.
1682 25. If an assertion condition captured any substrings, they were not passed
1711 32. A *MARK encountered during the processing of a positive assertion is now
1718 with a backwards assertion. For example /\b01|\b02/ also matched "0102"
2097 was called as a "subroutine", or in an assertion. Perl 5.11 documents that
2098 \K is "not well defined" if used in an assertion. PCRE now accepts it if
2099 the assertion is positive, but not if it is negative.
2136 3. A pattern such as ^(?!a(*SKIP)b) where a negative assertion contained one
2138 assertion pattern did not match (meaning that the assertion was true), it
2143 assertion subpattern, including such a pattern used as a condition,
2326 starts with a lookbehind assertion or \b or \B (\K is not supported by
2451 start or after a newline", because the conditional assertion was not being
2452 correctly handled. The rule now is that both the assertion and what follows
2456 condition was an assertion, PCRE could crash during matching, both with
2695 15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
3671 compile error "lookbehind assertion is not fixed length".
4814 14. PCRE now supports the \G assertion. It is true when the current matching
