Lines Matching refs:after
129 33. The JIT compiler should not check repeats after a {0,1} repeat byte code.
203 6. Catch a bad opcode during auto-possessification after compiling a bad UTF
312 assertion after (?(. The code was failing to check the character after
334 other cases where backtracking after \C could crash. This set of bugs was
354 applied after reading the number, and stupidly assuming that integer
606 (a) If the rest of the pattern did not match after a maximal run of
619 first data item, and therefore matched "ca" after "c" instead of at the
647 on a patch by Zoltan Herczeg. It now happens after instead of during
682 23. Perl now gives an error for missing closing braces after \x{... instead of
817 after a backtrack. Also, the capture_last value is now reset after a
822 abandoned after a backtrack.
825 now prints out the matched string after a yield of 0 or 1.
1089 "unknown -C option" after outputting 0 or 1.
1127 (c) \X did not give a hard partial match after matching one or more
1355 (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
1381 incorrectly expecting the subject to contain another "a" after the start.
1500 character after the value is now allowed for.
1611 (.*a|.*)+ was not marked as matching at start or after a newline.
1672 subject after a captured substring, to make it easier to tell which of a
1842 such as (A(*COMMIT)B(*THEN)C|D) any failure after matching A should
1902 only one byte after an empty string match just before CRLF (this case
2113 14. The checks for overrunning compiling workspace could trigger after an
2316 12. Restarting a match using pcre_dfa_exec() after a partial match did not work
2323 13. The string returned by pcre_dfa_exec() after a partial match has been
2451 start or after a newline", because the conditional assertion was not being
2586 after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
2742 - Added an listing of the option settings after cmake has run.
2763 of a program that users should build themselves after PCRE is installed, so
2853 inclusion of <windows.h> to before rather than after the definition of
2885 this means that the match must be either at the beginning, or after a
2886 newline. The bug was in the code for advancing after a failed match and
2940 reversed later after testing - see 16 below.]
3058 10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty
3135 characters after failing to match at the start. However, the pattern \nA
3338 that would hit this one: something like ^ABC$ would have failed after \r
3339 and then tried again after \r\n.
3349 "abc\r\n\r\n", it found an unwanted second match after the second \r. This
3350 was because its rules for how to advance for /g after matching an empty
3453 13. Removed some redundant semicolons after macro calls in pcrecpparg.h.in
3501 empty string contained only one non-empty item after a nested subpattern.
3682 7. In multiline (/m) mode, PCRE was matching ^ after a terminating newline at
3685 the start of the subject and immediately after *internal* newlines.
3730 class but used an invalid character after [ (for example [[,abc,]]) caused
3733 the pattern terminated after [[ but there just happened to be a sequence of
3997 considerably. I realized I did not need to use a tree structure after
4189 including restarting after a partial match.
4365 10. In UTF-8 mode, when moving forwards in the subject after a failed match
4747 1. If a comment in an extended regex that started immediately after a meta-item
4944 numbers. The function pcre_fullinfo() can be used after compilation to extract
5076 pcretest has been extended so that this information is shown after a successful
5079 48. Cosmetic change to Makefile: there's no need to have / after $(DESTDIR)
5198 this fix an hour or so after the initial 3.7 release.)
5316 infinite loops after an iteration that matches an empty string was't working
5445 7. Fixed bug: a zero repetition after a literal string (e.g. /abcde{0}/) was
5495 must be retried after every newline in the subject.
5510 compiled in such a way that the backtracking after subsequent failure was
5528 4. Added the convenience functions for extracting substrings after a successful
