Lines Matching refs:assertion
93 (b) Some patterns starting with an assertion that started with .* were
97 start with spaces. Starting .* in an assertion is no longer taken as an
144 assertion, caused pcretest to generate incorrect output, and also to read
163 ("assertion expected") when (?(?C) was not followed by an opening
220 6. A lookbehind assertion within a set of mutually recursive subpatterns could
261 assertion which itself contained a forward reference caused buffer
329 37. Fix two assertion fails in JIT. These issues were found by Karl Skomski
376 2. If an assertion condition was quantified with a minimum of zero (an odd
418 11. If an assertion that was used as a condition was quantified with a minimum
465 26. Fix JIT compilation of conditional blocks, which assertion
471 28. The assertion (?!) is optimized to (*FAIL). This was not handled correctly
472 when this assertion was used as a condition, for example (?(?!)a|b). In
498 assertion after (?(. The code was failing to check the character after
499 (?(?< for the ! or = that would indicate a lookbehind assertion. This bug
507 35. A mutual recursion within a lookbehind assertion such as (?<=((?2))((?1)))
509 lookbehind assertion. This bug was discovered by the LLVM fuzzer.
511 36. The use of \K in a positive lookbehind assertion in a non-anchored pattern
645 4. A pattern such as (?=ab\K) that uses \K in an assertion can set the start
802 10. A conditional group with an assertion condition could lead to PCRE
1044 there was a conditional group that depended on an assertion, if the
1045 assertion was false, the callout that immediately followed the alternation
1048 23. Allow an explicit callout to be inserted before an assertion that is the
1347 14. As documented, (*COMMIT) is now confined to within a positive assertion.
1845 21. When (*ACCEPT) was used in an assertion that matched an empty string and
1846 PCRE_NOTEMPTY was set, PCRE applied the non-empty test to the assertion.
1868 25. If an assertion condition captured any substrings, they were not passed
1897 32. A *MARK encountered during the processing of a positive assertion is now
1904 with a backwards assertion. For example /\b01|\b02/ also matched "0102"
2283 was called as a "subroutine", or in an assertion. Perl 5.11 documents that
2284 \K is "not well defined" if used in an assertion. PCRE now accepts it if
2285 the assertion is positive, but not if it is negative.
2322 3. A pattern such as ^(?!a(*SKIP)b) where a negative assertion contained one
2324 assertion pattern did not match (meaning that the assertion was true), it
2329 assertion subpattern, including such a pattern used as a condition,
2512 starts with a lookbehind assertion or \b or \B (\K is not supported by
2637 start or after a newline", because the conditional assertion was not being
2638 correctly handled. The rule now is that both the assertion and what follows
2642 condition was an assertion, PCRE could crash during matching, both with
2881 15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
3857 compile error "lookbehind assertion is not fixed length".
5000 14. PCRE now supports the \G assertion. It is true when the current matching
