Lines Matching refs:lookbehind

99 a pattern. Because \G is in a lookbehind assertion, there has to be a
104 22. When checking to see if a lookbehind is of fixed length, lookaheads were
106 to an incorrect "lookbehind assertion is not fixed length" error.
399 5. If a lookbehind assertion that contained a back reference to a group
511 35. A lookbehind assertion that had a zero-length branch caused undefined
598   (b) {0} can now be used after a group in a lookbehind assertion; previously
624 lookbehind assertion it now points to the start of the assertion. Another
638   (a) An overall recursion such as (?0) inside a lookbehind assertion was not
650       lookbehind contained more than one toplevel branch and the first branch
675   (l) If a lookbehind contained a subroutine call, and the called group
699       a lookbehind that was within another lookbehind, the calculation of the
700       lookbehind length went wrong and could provoke an internal error.
705 4. Back references are now permitted in lookbehind assertions when there are
990 11. A pattern such as /(?<=((?C)0))/, which has a callout inside a lookbehind
1361 lookbehind involved an out-of-bounds pointer, which could potentially cause
1364 73. The maximum lookbehind length was incorrectly calculated for patterns such
1367 74. Give an error if a lookbehind assertion is longer than 65535 code units.
1403 not dereferencing it) while handling lookbehind assertions.
1550 for the ! or = that would indicate a lookbehind assertion. This bug was
1566 16. A mutual recursion within a lookbehind assertion such as (?<=((?2))((?1)))
1568 lookbehind assertion. This bug was discovered by the LLVM fuzzer.
1570 17. The use of \K in a positive lookbehind assertion in a non-anchored pattern
1632 33. A lookbehind assertion within a set of mutually recursive subpatterns could