Lines Matching refs:had
55 the class, even if it had been included by some previous item, for example
112 (b) The pcretest code also had a bug, causing it to loop forever in UTF-8
133 17. Nobody had reported that the --include_dir option, which was added in
321 overrun had occurred. This is a "should never occur" error, but it can be
346 was incorrectly treated as false if the SKIP had been reached during the
416 14. Change 8.00/11 was not quite complete: code had been accidentally omitted,
499 which had an unlimited repeat of a nested, fixed maximum repeat of a wide
524 if the pattern had a "must contain" character that was already found in the
591 (It was back references and recursion that I had previously got hung up
598 26. While implementing 25, I discovered to my embarrassment that pcretest had
600 study optimizations had never been tested with that matching function.
689 19. A conditional group that had only one branch was not being correctly
783 11. An option change at the start of a pattern that had top-level alternatives
791 12. For a pattern where the match had to start at the beginning or immediately
892 14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
1020 11. The program that makes PCRE's Unicode character property table had a bug
1124 of both had grown to the point where there were only 3 bits left.
1232 from the 1000-entry workspace that had been reserved. So now there is no
1296 19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
1297 something other than just ASCII characters) inside a group that had an
1440 3. I had an email from Eric Raymond about problems translating some of PCRE's
1460 to be caused by a trailing space on an input line that had got lost in his
1507 some cases like this - I found 11), and the matching function had to
1562 buffer for a data line had to be extended.
1582 2. The -S option for pcretest uses setrlimit(); I had omitted to #include
1727 25. Realized that a little bit of performance could be had by replacing
1762 whole, these are just syntactic alternatives for features that PCRE had
1931 17. A character class other than a single negated character that had a minimum
2093 4. I had overlooked the fact that, in some locales, there are characters for
2127 (d) Split off pcrecpparg.h from pcrecpp.h and had the former built by
2128 "configure" and the latter not, in order to fix a problem somebody had
2176 (a) pcreposix.h still had just "extern" instead of either of these macros;
2180 but external in the C sense, all had PCRE_EXPORT in their definitions.
2355 6. The man pages all had just "PCRE" as their title. I have changed them to
2360 7. The NON-UNIX-USE file had not been updated for the different set of source
2385 the library but which are not part of the API. These have all had their
2550 whether it really works. (The user who reported this had patched the
2565 to find the match, as PCRE was deluded into thinking that the match had to
2647 had to patch ltmain.sh to ensure that ${SED} is set (it isn't on my
2696 I had written "if ((digitab[*p++] && chtab_digit) == 0)" where the "&&"
2700 6. I had used a variable called "isblank" - this is a C99 function, causing
2728 that had a minimum quantifier of zero caused PCRE to crash. For example,
2730 recursion. If the recursively-called subpattern itself had a zero repeat,
2760 2. Three internal functions had redundant arguments passed to them. Removal
2843 had no effect on PCRE's behaviour, but in some circumstances it could
3169 39. Change 25 above had to resort to a heavy-handed test for the .* anchoring
3380 1. A bit of extraneous text had somehow crept into the pcregrep documentation.
3401 2. The Makefile had to be changed to make it work on BSD systems, where 'make'
3413 2. The config.guess and config.sub files had not been updated when I moved to
3421 had been forgotten.
3454 9. Fixed typo (3.4/1) in pcre.h again. Sigh. I had changed pcre.h (which is
3459 because it had an ifdef in the middle of a string argument for printf(). Fixed
3615 the next newline as if a previous match had failed.
3856 1. Corrected the man page, where some "const" qualifiers had been omitted.
3872 7. I had screwed up change 6 below and broken the rules for the use of
3914 outcome, but in this particular case used more store than had been allocated,
3960 of the memory it had got.
4000 3. Fixed serious bug. If a pattern had a back reference, but the call to
4121 a subpattern that had matched an empty string, e.g. /(a|)\1*/. It now does what