Lines Matching refs:lookbehind
34 6. A lookbehind assertion within a set of mutually recursive subpatterns could
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
836 17. The \A escape now records a lookbehind value of 1, though its execution
911 37. The value of the max lookbehind was not correctly preserved if a compiled
1607 (?<=(a)+) was not diagnosed as invalid (non-fixed-length lookbehind).
2094 10. \K gave a compile-time error if it appeared in a lookbehind assersion.
2326 starts with a lookbehind assertion or \b or \B (\K is not supported by
2850 and both kinds of lookbehind were skipped).
3110 (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
3670 in lookbehind assertions such as (?<=[^f]), leading to an incorrect
3671 compile error "lookbehind assertion is not fixed length".
4220 for matching (and similarly the previous 8K for lookbehind assertions).
4640 6. A lookbehind at the start of a pattern in UTF-8 mode could also cause PCRE
4643 7. A lookbehind in a pattern matched in non-UTF-8 mode on a PCRE compiled with
4645 contained bytes with the 0x80 bit set and the 0x40 bit unset in a lookbehind
4833 PCRE_DOTALL. However, PCRE does not permit \C to appear in lookbehind
4835 calculate the length of the lookbehind. At least, that's the case for Perl
5479 with \b or \B, though it was doing it for other lookbehind assertions. That is,
5583 $(?<= positive lookbehind
5584 $(?<! negative lookbehind
