ViewVC logotype

Diff of /code/trunk/ChangeLog

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1033 by ph10, Mon Sep 10 11:02:48 2012 UTC revision 1600 by ph10, Wed Sep 2 08:54:57 2015 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 8.32  Note that the PCRE 8.xx series (PCRE1) is now in a bugfix-only state. All
5  ------------  development is happening in the PCRE2 10.xx series.
7    Version 8.38 xx-xxx-xxxx
8    ------------------------
10    1.  If a group that contained a recursive back reference also contained a
11        forward reference subroutine call followed by a non-forward-reference
12        subroutine call, for example /.((?2)(?R)\1)()/, pcre2_compile() failed to
13        compile correct code, leading to undefined behaviour or an internally
14        detected error. This bug was discovered by the LLVM fuzzer.
16    2.  Quantification of certain items (e.g. atomic back references) could cause
17        incorrect code to be compiled when recursive forward references were
18        involved. For example, in this pattern: /(?1)()((((((\1++))\x85)+)|))/.
19        This bug was discovered by the LLVM fuzzer.
21    3.  A repeated conditional group whose condition was a reference by name caused
22        a buffer overflow if there was more than one group with the given name.
23        This bug was discovered by the LLVM fuzzer.
25    4.  A recursive back reference by name within a group that had the same name as
26        another group caused a buffer overflow. For example:
27        /(?J)(?'d'(?'d'\g{d}))/. This bug was discovered by the LLVM fuzzer.
29    5.  A forward reference by name to a group whose number is the same as the
30        current group, for example in this pattern: /(?|(\k'Pm')|(?'Pm'))/, caused
31        a buffer overflow at compile time. This bug was discovered by the LLVM
32        fuzzer.
34    6.  A lookbehind assertion within a set of mutually recursive subpatterns could
35        provoke a buffer overflow. This bug was discovered by the LLVM fuzzer.
37    7.  Another buffer overflow bug involved duplicate named groups with a
38        reference between their definition, with a group that reset capture
39        numbers, for example: /(?J:(?|(?'R')(\k'R')|((?'R'))))/. This has been
40        fixed by always allowing for more memory, even if not needed. (A proper fix
41        is implemented in PCRE2, but it involves more refactoring.)
43    8.  There was no check for integer overflow in subroutine calls such as (?123).
45    9.  The table entry for \l in EBCDIC environments was incorrect, leading to its
46        being treated as a literal 'l' instead of causing an error.
48    10. There was a buffer overflow if pcre_exec() was called with an ovector of
49        size 1. This bug was found by american fuzzy lop.
51    11. If a non-capturing group containing a conditional group that could match
52        an empty string was repeated, it was not identified as matching an empty
53        string itself. For example: /^(?:(?(1)x|)+)+$()/.
55    12. In an EBCDIC environment, pcretest was mishandling the escape sequences
56        \a and \e in test subject lines.
58    13. In an EBCDIC environment, \a in a pattern was converted to the ASCII
59        instead of the EBCDIC value.
61    14. The handling of \c in an EBCDIC environment has been revised so that it is
62        now compatible with the specification in Perl's perlebcdic page.
64    15. The EBCDIC character 0x41 is a non-breaking space, equivalent to 0xa0 in
65        ASCII/Unicode. This has now been added to the list of characters that are
66        recognized as white space in EBCDIC.
68    16. When PCRE was compiled without UCP support, the use of \p and \P gave an
69        error (correctly) when used outside a class, but did not give an error
70        within a class.
72    17. \h within a class was incorrectly compiled in EBCDIC environments.
74    18. A pattern with an unmatched closing parenthesis that contained a backward
75        assertion which itself contained a forward reference caused buffer
76        overflow. And example pattern is: /(?=di(?<=(?1))|(?=(.))))/.
78    19. JIT should return with error when the compiled pattern requires more stack
79        space than the maximum.
81    20. A possessively repeated conditional group that could match an empty string,
82        for example, /(?(R))*+/, was incorrectly compiled.
84    21. Fix infinite recursion in the JIT compiler when certain patterns such as
85        /(?:|a|){100}x/ are analysed.
87    22. Some patterns with character classes involving [: and \\ were incorrectly
88        compiled and could cause reading from uninitialized memory or an incorrect
89        error diagnosis.
91    23. Pathological patterns containing many nested occurrences of [: caused
92        pcre_compile() to run for a very long time.
94    24. A conditional group with only one branch has an implicit empty alternative
95        branch and must therefore be treated as potentially matching an empty
96        string.
98    25. If (?R was followed by - or + incorrect behaviour happened instead of a
99        diagnostic.
101    26. Arrange to give up on finding the minimum matching length for overly
102        complex patterns.
104    27. Similar to (4) above: in a pattern with duplicated named groups and an
105        occurrence of (?| it is possible for an apparently non-recursive back
106        reference to become recursive if a later named group with the relevant
107        number is encountered. This could lead to a buffer overflow. Wen Guanxing
108        from Venustech ADLAB discovered this bug.
110    28. If pcregrep was given the -q option with -c or -l, or when handling a
111        binary file, it incorrectly wrote output to stdout.
113    29. The JIT compiler did not restore the control verb head in case of *THEN
114        control verbs. This issue was found by Karl Skomski with a custom LLVM
115        fuzzer.
117    30. Error messages for syntax errors following \g and \k were giving inaccurate
118        offsets in the pattern.
120    31. Added a check for integer overflow in conditions (?(<digits>) and
121        (?(R<digits>). This omission was discovered by Karl Skomski with the LLVM
122        fuzzer.
124    32. Handling recursive references such as (?2) when the reference is to a group
125        later in the pattern uses code that is very hacked about and error-prone.
126        It has been re-written for PCRE2. Here in PCRE1, a check has been added to
127        give an internal error if it is obvious that compiling has gone wrong.
129    33. The JIT compiler should not check repeats after a {0,1} repeat byte code.
130        This issue was found by Karl Skomski with a custom LLVM fuzzer.
132    34. The JIT compiler should restore the control chain for empty possessive
133        repeats. This issue was found by Karl Skomski with a custom LLVM fuzzer.
135    35. Match limit check added to JIT recursion. This issue was found by Karl
136        Skomski with a custom LLVM fuzzer.
138    36. Yet another case similar to 27 above has been circumvented by an
139        unconditional allocation of extra memory. This issue is fixed "properly" in
140        PCRE2 by refactoring the way references are handled. Wen Guanxing
141        from Venustech ADLAB discovered this bug.
143    37. Fix two assertion fails in JIT. These issues were found by Karl Skomski
144        with a custom LLVM fuzzer.
146    38. Fixed a corner case of range optimization in JIT.
148    39. An incorrect error "overran compiling workspace" was given if there were
149        exactly enough group forward references such that the last one extended
150        into the workspace safety margin. The next one would have expanded the
151        workspace. The test for overflow was not including the safety margin.
153    40. A match limit issue is fixed in JIT which was found by Karl Skomski
154        with a custom LLVM fuzzer.
156    41. Remove the use of /dev/null in testdata/testinput2, because it doesn't
157        work under Windows. (Why has it taken so long for anyone to notice?)
160    Version 8.37 28-April-2015
161    --------------------------
163    1.  When an (*ACCEPT) is triggered inside capturing parentheses, it arranges
164        for those parentheses to be closed with whatever has been captured so far.
165        However, it was failing to mark any other groups between the hightest
166        capture so far and the currrent group as "unset". Thus, the ovector for
167        those groups contained whatever was previously there. An example is the
168        pattern /(x)|((*ACCEPT))/ when matched against "abcd".
170    2.  If an assertion condition was quantified with a minimum of zero (an odd
171        thing to do, but it happened), SIGSEGV or other misbehaviour could occur.
173    3.  If a pattern in pcretest input had the P (POSIX) modifier followed by an
174        unrecognized modifier, a crash could occur.
176    4.  An attempt to do global matching in pcretest with a zero-length ovector
177        caused a crash.
179    5.  Fixed a memory leak during matching that could occur for a subpattern
180        subroutine call (recursive or otherwise) if the number of captured groups
181        that had to be saved was greater than ten.
183    6.  Catch a bad opcode during auto-possessification after compiling a bad UTF
184        string with NO_UTF_CHECK. This is a tidyup, not a bug fix, as passing bad
185        UTF with NO_UTF_CHECK is documented as having an undefined outcome.
187    7.  A UTF pattern containing a "not" match of a non-ASCII character and a
188        subroutine reference could loop at compile time. Example: /[^\xff]((?1))/.
190    8. When a pattern is compiled, it remembers the highest back reference so that
191       when matching, if the ovector is too small, extra memory can be obtained to
192       use instead. A conditional subpattern whose condition is a check on a
193       capture having happened, such as, for example in the pattern
194       /^(?:(a)|b)(?(1)A|B)/, is another kind of back reference, but it was not
195       setting the highest backreference number. This mattered only if pcre_exec()
196       was called with an ovector that was too small to hold the capture, and there
197       was no other kind of back reference (a situation which is probably quite
198       rare). The effect of the bug was that the condition was always treated as
199       FALSE when the capture could not be consulted, leading to a incorrect
200       behaviour by pcre_exec(). This bug has been fixed.
202    9. A reference to a duplicated named group (either a back reference or a test
203       for being set in a conditional) that occurred in a part of the pattern where
204       PCRE_DUPNAMES was not set caused the amount of memory needed for the pattern
205       to be incorrectly calculated, leading to overwriting.
207    10. A mutually recursive set of back references such as (\2)(\1) caused a
208        segfault at study time (while trying to find the minimum matching length).
209        The infinite loop is now broken (with the minimum length unset, that is,
210        zero).
212    11. If an assertion that was used as a condition was quantified with a minimum
213        of zero, matching went wrong. In particular, if the whole group had
214        unlimited repetition and could match an empty string, a segfault was
215        likely. The pattern (?(?=0)?)+ is an example that caused this. Perl allows
216        assertions to be quantified, but not if they are being used as conditions,
217        so the above pattern is faulted by Perl. PCRE has now been changed so that
218        it also rejects such patterns.
220    12. A possessive capturing group such as (a)*+ with a minimum repeat of zero
221        failed to allow the zero-repeat case if pcre2_exec() was called with an
222        ovector too small to capture the group.
224    13. Fixed two bugs in pcretest that were discovered by fuzzing and reported by
225        Red Hat Product Security:
227        (a) A crash if /K and /F were both set with the option to save the compiled
228        pattern.
230        (b) Another crash if the option to print captured substrings in a callout
231        was combined with setting a null ovector, for example \O\C+ as a subject
232        string.
234    14. A pattern such as "((?2){0,1999}())?", which has a group containing a
235        forward reference repeated a large (but limited) number of times within a
236        repeated outer group that has a zero minimum quantifier, caused incorrect
237        code to be compiled, leading to the error "internal error:
238        previously-checked referenced subpattern not found" when an incorrect
239        memory address was read. This bug was reported as "heap overflow",
240        discovered by Kai Lu of Fortinet's FortiGuard Labs and given the CVE number
241        CVE-2015-2325.
243    23. A pattern such as "((?+1)(\1))/" containing a forward reference subroutine
244        call within a group that also contained a recursive back reference caused
245        incorrect code to be compiled. This bug was reported as "heap overflow",
246        discovered by Kai Lu of Fortinet's FortiGuard Labs, and given the CVE
247        number CVE-2015-2326.
249    24. Computing the size of the JIT read-only data in advance has been a source
250        of various issues, and new ones are still appear unfortunately. To fix
251        existing and future issues, size computation is eliminated from the code,
252        and replaced by on-demand memory allocation.
254    25. A pattern such as /(?i)[A-`]/, where characters in the other case are
255        adjacent to the end of the range, and the range contained characters with
256        more than one other case, caused incorrect behaviour when compiled in UTF
257        mode. In that example, the range a-j was left out of the class.
259    26. Fix JIT compilation of conditional blocks, which assertion
260        is converted to (*FAIL). E.g: /(?(?!))/.
262    27. The pattern /(?(?!)^)/ caused references to random memory. This bug was
263        discovered by the LLVM fuzzer.
265    28. The assertion (?!) is optimized to (*FAIL). This was not handled correctly
266        when this assertion was used as a condition, for example (?(?!)a|b). In
267        pcre2_match() it worked by luck; in pcre2_dfa_match() it gave an incorrect
268        error about an unsupported item.
270    29. For some types of pattern, for example /Z*(|d*){216}/, the auto-
271        possessification code could take exponential time to complete. A recursion
272        depth limit of 1000 has been imposed to limit the resources used by this
273        optimization.
275    30. A pattern such as /(*UTF)[\S\V\H]/, which contains a negated special class
276        such as \S in non-UCP mode, explicit wide characters (> 255) can be ignored
277        because \S ensures they are all in the class. The code for doing this was
278        interacting badly with the code for computing the amount of space needed to
279        compile the pattern, leading to a buffer overflow. This bug was discovered
280        by the LLVM fuzzer.
282    31. A pattern such as /((?2)+)((?1))/ which has mutual recursion nested inside
283        other kinds of group caused stack overflow at compile time. This bug was
284        discovered by the LLVM fuzzer.
286    32. A pattern such as /(?1)(?#?'){8}(a)/ which had a parenthesized comment
287        between a subroutine call and its quantifier was incorrectly compiled,
288        leading to buffer overflow or other errors. This bug was discovered by the
289        LLVM fuzzer.
291    33. The illegal pattern /(?(?<E>.*!.*)?)/ was not being diagnosed as missing an
292        assertion after (?(. The code was failing to check the character after
293        (?(?< for the ! or = that would indicate a lookbehind assertion. This bug
294        was discovered by the LLVM fuzzer.
296    34. A pattern such as /X((?2)()*+){2}+/ which has a possessive quantifier with
297        a fixed maximum following a group that contains a subroutine reference was
298        incorrectly compiled and could trigger buffer overflow. This bug was
299        discovered by the LLVM fuzzer.
301    35. A mutual recursion within a lookbehind assertion such as (?<=((?2))((?1)))
302        caused a stack overflow instead of the diagnosis of a non-fixed length
303        lookbehind assertion. This bug was discovered by the LLVM fuzzer.
305    36. The use of \K in a positive lookbehind assertion in a non-anchored pattern
306        (e.g. /(?<=\Ka)/) could make pcregrep loop.
308    37. There was a similar problem to 36 in pcretest for global matches.
310    38. If a greedy quantified \X was preceded by \C in UTF mode (e.g. \C\X*),
311        and a subsequent item in the pattern caused a non-match, backtracking over
312        the repeated \X did not stop, but carried on past the start of the subject,
313        causing reference to random memory and/or a segfault. There were also some
314        other cases where backtracking after \C could crash. This set of bugs was
315        discovered by the LLVM fuzzer.
317    39. The function for finding the minimum length of a matching string could take
318        a very long time if mutual recursion was present many times in a pattern,
319        for example, /((?2){73}(?2))((?1))/. A better mutual recursion detection
320        method has been implemented. This infelicity was discovered by the LLVM
321        fuzzer.
323    40. Static linking against the PCRE library using the pkg-config module was
324        failing on missing pthread symbols.
327    Version 8.36 26-September-2014
328    ------------------------------
330    1.  Got rid of some compiler warnings in the C++ modules that were shown up by
331        -Wmissing-field-initializers and -Wunused-parameter.
333    2.  The tests for quantifiers being too big (greater than 65535) were being
334        applied after reading the number, and stupidly assuming that integer
335        overflow would give a negative number. The tests are now applied as the
336        numbers are read.
338    3.  Tidy code in pcre_exec.c where two branches that used to be different are
339        now the same.
341    4.  The JIT compiler did not generate match limit checks for certain
342        bracketed expressions with quantifiers. This may lead to exponential
343        backtracking, instead of returning with PCRE_ERROR_MATCHLIMIT. This
344        issue should be resolved now.
346    5.  Fixed an issue, which occures when nested alternatives are optimized
347        with table jumps.
349    6.  Inserted two casts and changed some ints to size_t in the light of some
350        reported 64-bit compiler warnings (Bugzilla 1477).
352    7.  Fixed a bug concerned with zero-minimum possessive groups that could match
353        an empty string, which sometimes were behaving incorrectly in the
354        interpreter (though correctly in the JIT matcher). This pcretest input is
355        an example:
357          '\A(?:[^"]++|"(?:[^"]*+|"")*+")++'
360        the interpreter was reporting a match of 'NON QUOTED ' only, whereas the
361        JIT matcher and Perl both matched 'NON QUOTED "QUOT""ED" AFTER '. The test
362        for an empty string was breaking the inner loop and carrying on at a lower
363        level, when possessive repeated groups should always return to a higher
364        level as they have no backtrack points in them. The empty string test now
365        occurs at the outer level.
367    8.  Fixed a bug that was incorrectly auto-possessifying \w+ in the pattern
368        ^\w+(?>\s*)(?<=\w) which caused it not to match "test test".
370    9.  Give a compile-time error for \o{} (as Perl does) and for \x{} (which Perl
371        doesn't).
373    10. Change 8.34/15 introduced a bug that caused the amount of memory needed
374        to hold a pattern to be incorrectly computed (too small) when there were
375        named back references to duplicated names. This could cause "internal
376        error: code overflow" or "double free or corruption" or other memory
377        handling errors.
379    11. When named subpatterns had the same prefixes, back references could be
380        confused. For example, in this pattern:
382          /(?P<Name>a)?(?P<Name2>b)?(?(<Name>)c|d)*l/
384        the reference to 'Name' was incorrectly treated as a reference to a
385        duplicate name.
387    12. A pattern such as /^s?c/mi8 where the optional character has more than
388        one "other case" was incorrectly compiled such that it would only try to
389        match starting at "c".
391    13. When a pattern starting with \s was studied, VT was not included in the
392        list of possible starting characters; this should have been part of the
393        8.34/18 patch.
395    14. If a character class started [\Qx]... where x is any character, the class
396        was incorrectly terminated at the ].
398    15. If a pattern that started with a caseless match for a character with more
399        than one "other case" was studied, PCRE did not set up the starting code
400        unit bit map for the list of possible characters. Now it does. This is an
401        optimization improvement, not a bug fix.
403    16. The Unicode data tables have been updated to Unicode 7.0.0.
405    17. Fixed a number of memory leaks in pcregrep.
407    18. Avoid a compiler warning (from some compilers) for a function call with
408        a cast that removes "const" from an lvalue by using an intermediate
409        variable (to which the compiler does not object).
411    19. Incorrect code was compiled if a group that contained an internal recursive
412        back reference was optional (had quantifier with a minimum of zero). This
413        example compiled incorrect code: /(((a\2)|(a*)\g<-1>))*/ and other examples
414        caused segmentation faults because of stack overflows at compile time.
416    20. A pattern such as /((?(R)a|(?1)))+/, which contains a recursion within a
417        group that is quantified with an indefinite repeat, caused a compile-time
418        loop which used up all the system stack and provoked a segmentation fault.
419        This was not the same bug as 19 above.
421    21. Add PCRECPP_EXP_DECL declaration to operator<< in pcre_stringpiece.h.
422        Patch by Mike Frysinger.
425    Version 8.35 04-April-2014
426    --------------------------
428    1.  A new flag is set, when property checks are present in an XCLASS.
429        When this flag is not set, PCRE can perform certain optimizations
430        such as studying these XCLASS-es.
432    2.  The auto-possessification of character sets were improved: a normal
433        and an extended character set can be compared now. Furthermore
434        the JIT compiler optimizes more character set checks.
436    3.  Got rid of some compiler warnings for potentially uninitialized variables
437        that show up only when compiled with -O2.
439    4.  A pattern such as (?=ab\K) that uses \K in an assertion can set the start
440        of a match later then the end of the match. The pcretest program was not
441        handling the case sensibly - it was outputting from the start to the next
442        binary zero. It now reports this situation in a message, and outputs the
443        text from the end to the start.
445    5.  Fast forward search is improved in JIT. Instead of the first three
446        characters, any three characters with fixed position can be searched.
447        Search order: first, last, middle.
449    6.  Improve character range checks in JIT. Characters are read by an inprecise
450        function now, which returns with an unknown value if the character code is
451        above a certain threshold (e.g: 256). The only limitation is that the value
452        must be bigger than the threshold as well. This function is useful when
453        the characters above the threshold are handled in the same way.
455    7.  The macros whose names start with RAWUCHAR are placeholders for a future
456        mode in which only the bottom 21 bits of 32-bit data items are used. To
457        make this more memorable for those maintaining the code, the names have
458        been changed to start with UCHAR21, and an extensive comment has been added
459        to their definition.
461    8.  Add missing (new) files sljitNativeTILEGX.c and sljitNativeTILEGX-encoder.c
462        to the export list in Makefile.am (they were accidentally omitted from the
463        8.34 tarball).
465    9.  The informational output from pcretest used the phrase "starting byte set"
466        which is inappropriate for the 16-bit and 32-bit libraries. As the output
467        for "first char" and "need char" really means "non-UTF-char", I've changed
468        "byte" to "char", and slightly reworded the output. The documentation about
469        these values has also been (I hope) clarified.
471    10. Another JIT related optimization: use table jumps for selecting the correct
472        backtracking path, when more than four alternatives are present inside a
473        bracket.
475    11. Empty match is not possible, when the minimum length is greater than zero,
476        and there is no \K in the pattern. JIT should avoid empty match checks in
477        such cases.
479    12. In a caseless character class with UCP support, when a character with more
480        than one alternative case was not the first character of a range, not all
481        the alternative cases were added to the class. For example, s and \x{17f}
482        are both alternative cases for S: the class [RST] was handled correctly,
483        but [R-T] was not.
485    13. The configure.ac file always checked for pthread support when JIT was
486        enabled. This is not used in Windows, so I have put this test inside a
487        check for the presence of windows.h (which was already tested for).
489    14. Improve pattern prefix search by a simplified Boyer-Moore algorithm in JIT.
490        The algorithm provides a way to skip certain starting offsets, and usually
491        faster than linear prefix searches.
493    15. Change 13 for 8.20 updated RunTest to check for the 'fr' locale as well
494        as for 'fr_FR' and 'french'. For some reason, however, it then used the
495        Windows-specific input and output files, which have 'french' screwed in.
496        So this could never have worked. One of the problems with locales is that
497        they aren't always the same. I have now updated RunTest so that it checks
498        the output of the locale test (test 3) against three different output
499        files, and it allows the test to pass if any one of them matches. With luck
500        this should make the test pass on some versions of Solaris where it was
501        failing. Because of the uncertainty, the script did not used to stop if
502        test 3 failed; it now does. If further versions of a French locale ever
503        come to light, they can now easily be added.
505    16. If --with-pcregrep-bufsize was given a non-integer value such as "50K",
506        there was a message during ./configure, but it did not stop. This now
507        provokes an error. The invalid example in README has been corrected.
508        If a value less than the minimum is given, the minimum value has always
509        been used, but now a warning is given.
511    17. If --enable-bsr-anycrlf was set, the special 16/32-bit test failed. This
512        was a bug in the test system, which is now fixed. Also, the list of various
513        configurations that are tested for each release did not have one with both
514        16/32 bits and --enable-bar-anycrlf. It now does.
516    18. pcretest was missing "-C bsr" for displaying the \R default setting.
518    19. Little endian PowerPC systems are supported now by the JIT compiler.
520    20. The fast forward newline mechanism could enter to an infinite loop on
521        certain invalid UTF-8 input. Although we don't support these cases
522        this issue can be fixed by a performance optimization.
524    21. Change 33 of 8.34 is not sufficient to ensure stack safety because it does
525        not take account if existing stack usage. There is now a new global
526        variable called pcre_stack_guard that can be set to point to an external
527        function to check stack availability. It is called at the start of
528        processing every parenthesized group.
530    22. A typo in the code meant that in ungreedy mode the max/min qualifier
531        behaved like a min-possessive qualifier, and, for example, /a{1,3}b/U did
532        not match "ab".
534    23. When UTF was disabled, the JIT program reported some incorrect compile
535        errors. These messages are silenced now.
537    24. Experimental support for ARM-64 and MIPS-64 has been added to the JIT
538        compiler.
540    25. Change all the temporary files used in RunGrepTest to be different to those
541        used by RunTest so that the tests can be run simultaneously, for example by
542        "make -j check".
545    Version 8.34 15-December-2013
546    -----------------------------
548    1.  Add pcre[16|32]_jit_free_unused_memory to forcibly free unused JIT
549        executable memory. Patch inspired by Carsten Klein.
551    2.  ./configure --enable-coverage defined SUPPORT_GCOV in config.h, although
552        this macro is never tested and has no effect, because the work to support
553        coverage involves only compiling and linking options and special targets in
554        the Makefile. The comment in config.h implied that defining the macro would
555        enable coverage support, which is totally false. There was also support for
556        setting this macro in the CMake files (my fault, I just copied it from
557        configure). SUPPORT_GCOV has now been removed.
559    3.  Make a small performance improvement in strlen16() and strlen32() in
560        pcretest.
562    4.  Change 36 for 8.33 left some unreachable statements in pcre_exec.c,
563        detected by the Solaris compiler (gcc doesn't seem to be able to diagnose
564        these cases). There was also one in pcretest.c.
566    5.  Cleaned up a "may be uninitialized" compiler warning in pcre_exec.c.
568    6.  In UTF mode, the code for checking whether a group could match an empty
569        string (which is used for indefinitely repeated groups to allow for
570        breaking an infinite loop) was broken when the group contained a repeated
571        negated single-character class with a character that occupied more than one
572        data item and had a minimum repetition of zero (for example, [^\x{100}]* in
573        UTF-8 mode). The effect was undefined: the group might or might not be
574        deemed as matching an empty string, or the program might have crashed.
576    7.  The code for checking whether a group could match an empty string was not
577        recognizing that \h, \H, \v, \V, and \R must match a character.
579    8.  Implemented PCRE_INFO_MATCH_EMPTY, which yields 1 if the pattern can match
580        an empty string. If it can, pcretest shows this in its information output.
582    9.  Fixed two related bugs that applied to Unicode extended grapheme clusters
583        that were repeated with a maximizing qualifier (e.g. \X* or \X{2,5}) when
584        matched by pcre_exec() without using JIT:
586        (a) If the rest of the pattern did not match after a maximal run of
587            grapheme clusters, the code for backing up to try with fewer of them
588            did not always back up over a full grapheme when characters that do not
589            have the modifier quality were involved, e.g. Hangul syllables.
591        (b) If the match point in a subject started with modifier character, and
592            there was no match, the code could incorrectly back up beyond the match
593            point, and potentially beyond the first character in the subject,
594            leading to a segfault or an incorrect match result.
596    10. A conditional group with an assertion condition could lead to PCRE
597        recording an incorrect first data item for a match if no other first data
598        item was recorded. For example, the pattern (?(?=ab)ab) recorded "a" as a
599        first data item, and therefore matched "ca" after "c" instead of at the
600        start.
602    11. Change 40 for 8.33 (allowing pcregrep to find empty strings) showed up a
603        bug that caused the command "echo a | ./pcregrep -M '|a'" to loop.
605    12. The source of pcregrep now includes z/OS-specific code so that it can be
606        compiled for z/OS as part of the special z/OS distribution.
608    13. Added the -T and -TM options to pcretest.
610    14. The code in pcre_compile.c for creating the table of named capturing groups
611        has been refactored. Instead of creating the table dynamically during the
612        actual compiling pass, the information is remembered during the pre-compile
613        pass (on the stack unless there are more than 20 named groups, in which
614        case malloc() is used) and the whole table is created before the actual
615        compile happens. This has simplified the code (it is now nearly 150 lines
616        shorter) and prepared the way for better handling of references to groups
617        with duplicate names.
619    15. A back reference to a named subpattern when there is more than one of the
620        same name now checks them in the order in which they appear in the pattern.
621        The first one that is set is used for the reference. Previously only the
622        first one was inspected. This change makes PCRE more compatible with Perl.
624    16. Unicode character properties were updated from Unicode 6.3.0.
626    17. The compile-time code for auto-possessification has been refactored, based
627        on a patch by Zoltan Herczeg. It now happens after instead of during
628        compilation. The code is cleaner, and more cases are handled. The option
629        PCRE_NO_AUTO_POSSESS is added for testing purposes, and the -O and /O
630        options in pcretest are provided to set it. It can also be set by
631        (*NO_AUTO_POSSESS) at the start of a pattern.
633    18. The character VT has been added to the default ("C" locale) set of
634        characters that match \s and are generally treated as white space,
635        following this same change in Perl 5.18. There is now no difference between
636        "Perl space" and "POSIX space". Whether VT is treated as white space in
637        other locales depends on the locale.
639    19. The code for checking named groups as conditions, either for being set or
640        for being recursed, has been refactored (this is related to 14 and 15
641        above). Processing unduplicated named groups should now be as fast at
642        numerical groups, and processing duplicated groups should be faster than
643        before.
645    20. Two patches to the CMake build system, by Alexander Barkov:
647          (1) Replace the "source" command by "." in CMakeLists.txt because
648              "source" is a bash-ism.
650          (2) Add missing HAVE_STDINT_H and HAVE_INTTYPES_H to config-cmake.h.in;
651              without these the CMake build does not work on Solaris.
653    21. Perl has changed its handling of \8 and \9. If there is no previously
654        encountered capturing group of those numbers, they are treated as the
655        literal characters 8 and 9 instead of a binary zero followed by the
656        literals. PCRE now does the same.
658    22. Following Perl, added \o{} to specify codepoints in octal, making it
659        possible to specify values greater than 0777 and also making them
660        unambiguous.
662    23. Perl now gives an error for missing closing braces after \x{... instead of
663        treating the string as literal. PCRE now does the same.
665    24. RunTest used to grumble if an inappropriate test was selected explicitly,
666        but just skip it when running all tests. This make it awkward to run ranges
667        of tests when one of them was inappropriate. Now it just skips any
668        inappropriate tests, as it always did when running all tests.
670    25. If PCRE_AUTO_CALLOUT and PCRE_UCP were set for a pattern that contained
671        character types such as \d or \w, too many callouts were inserted, and the
672        data that they returned was rubbish.
674    26. In UCP mode, \s was not matching two of the characters that Perl matches,
675        namely NEL (U+0085) and MONGOLIAN VOWEL SEPARATOR (U+180E), though they
676        were matched by \h. The code has now been refactored so that the lists of
677        the horizontal and vertical whitespace characters used for \h and \v (which
678        are defined only in one place) are now also used for \s.
680    27. Add JIT support for the 64 bit TileGX architecture.
681        Patch by Jiong Wang (Tilera Corporation).
683    28. Possessive quantifiers for classes (both explicit and automatically
684        generated) now use special opcodes instead of wrapping in ONCE brackets.
686    29. Whereas an item such as A{4}+ ignored the possessivenes of the quantifier
687        (because it's meaningless), this was not happening when PCRE_CASELESS was
688        set. Not wrong, but inefficient.
690    30. Updated perltest.pl to add /u (force Unicode mode) when /W (use Unicode
691        properties for \w, \d, etc) is present in a test regex. Otherwise if the
692        test contains no characters greater than 255, Perl doesn't realise it
693        should be using Unicode semantics.
695    31. Upgraded the handling of the POSIX classes [:graph:], [:print:], and
696        [:punct:] when PCRE_UCP is set so as to include the same characters as Perl
697        does in Unicode mode.
699    32. Added the "forbid" facility to pcretest so that putting tests into the
700        wrong test files can sometimes be quickly detected.
702    33. There is now a limit (default 250) on the depth of nesting of parentheses.
703        This limit is imposed to control the amount of system stack used at compile
704        time. It can be changed at build time by --with-parens-nest-limit=xxx or
705        the equivalent in CMake.
707    34. Character classes such as [A-\d] or [a-[:digit:]] now cause compile-time
708        errors. Perl warns for these when in warning mode, but PCRE has no facility
709        for giving warnings.
711    35. Change 34 for 8.13 allowed quantifiers on assertions, because Perl does.
712        However, this was not working for (?!) because it is optimized to (*FAIL),
713        for which PCRE does not allow quantifiers. The optimization is now disabled
714        when a quantifier follows (?!). I can't see any use for this, but it makes
715        things uniform.
717    36. Perl no longer allows group names to start with digits, so I have made this
718        change also in PCRE. It simplifies the code a bit.
720    37. In extended mode, Perl ignores spaces before a + that indicates a
721        possessive quantifier. PCRE allowed a space before the quantifier, but not
722        before the possessive +. It now does.
724    38. The use of \K (reset reported match start) within a repeated possessive
725        group such as (a\Kb)*+ was not working.
727    40. Document that the same character tables must be used at compile time and
728        run time, and that the facility to pass tables to pcre_exec() and
729        pcre_dfa_exec() is for use only with saved/restored patterns.
731    41. Applied Jeff Trawick's patch CMakeLists.txt, which "provides two new
732        features for Builds with MSVC:
734        1. Support pcre.rc and/or pcreposix.rc (as is already done for MinGW
735           builds). The .rc files can be used to set FileDescription and many other
736           attributes.
738        2. Add an option (-DINSTALL_MSVC_PDB) to enable installation of .pdb files.
739           This allows higher-level build scripts which want .pdb files to avoid
740           hard-coding the exact files needed."
742    42. Added support for [[:<:]] and [[:>:]] as used in the BSD POSIX library to
743        mean "start of word" and "end of word", respectively, as a transition aid.
745    43. A minimizing repeat of a class containing codepoints greater than 255 in
746        non-UTF 16-bit or 32-bit modes caused an internal error when PCRE was
747        compiled to use the heap for recursion.
749    44. Got rid of some compiler warnings for unused variables when UTF but not UCP
750        is configured.
753    Version 8.33 28-May-2013
754    ------------------------
756    1.  Added 'U' to some constants that are compared to unsigned integers, to
757        avoid compiler signed/unsigned warnings. Added (int) casts to unsigned
758        variables that are added to signed variables, to ensure the result is
759        signed and can be negated.
761    2.  Applied patch by Daniel Richard G for quashing MSVC warnings to the
762        CMake config files.
764    3.  Revise the creation of config.h.generic so that all boolean macros are
765        #undefined, whereas non-boolean macros are #ifndef/#endif-ed. This makes
766        overriding via -D on the command line possible.
768    4.  Changing the definition of the variable "op" in pcre_exec.c from pcre_uchar
769        to unsigned int is reported to make a quite noticeable speed difference in
770        a specific Windows environment. Testing on Linux did also appear to show
771        some benefit (and it is clearly not harmful). Also fixed the definition of
772        Xop which should be unsigned.
774    5.  Related to (4), changing the definition of the intermediate variable cc
775        in repeated character loops from pcre_uchar to pcre_uint32 also gave speed
776        improvements.
778    6.  Fix forward search in JIT when link size is 3 or greater. Also removed some
779        unnecessary spaces.
781    7.  Adjust autogen.sh and configure.ac to lose warnings given by automake 1.12
782        and later.
784    8.  Fix two buffer over read issues in 16 and 32 bit modes. Affects JIT only.
786    9.  Optimizing fast_forward_start_bits in JIT.
788    10. Adding support for callouts in JIT, and fixing some issues revealed
789        during this work. Namely:
791        (a) Unoptimized capturing brackets incorrectly reset on backtrack.
793        (b) Minimum length was not checked before the matching is started.
795    11. The value of capture_last that is passed to callouts was incorrect in some
796        cases when there was a capture on one path that was subsequently abandoned
797        after a backtrack. Also, the capture_last value is now reset after a
798        recursion, since all captures are also reset in this case.
800    12. The interpreter no longer returns the "too many substrings" error in the
801        case when an overflowing capture is in a branch that is subsequently
802        abandoned after a backtrack.
804    13. In the pathological case when an offset vector of size 2 is used, pcretest
805        now prints out the matched string after a yield of 0 or 1.
807    14. Inlining subpatterns in recursions, when certain conditions are fulfilled.
808        Only supported by the JIT compiler at the moment.
810    15. JIT compiler now supports 32 bit Macs thanks to Lawrence Velazquez.
812    16. Partial matches now set offsets[2] to the "bumpalong" value, that is, the
813        offset of the starting point of the matching process, provided the offsets
814        vector is large enough.
816    17. The \A escape now records a lookbehind value of 1, though its execution
817        does not actually inspect the previous character. This is to ensure that,
818        in partial multi-segment matching, at least one character from the old
819        segment is retained when a new segment is processed. Otherwise, if there
820        are no lookbehinds in the pattern, \A might match incorrectly at the start
821        of a new segment.
823    18. Added some #ifdef __VMS code into pcretest.c to help VMS implementations.
825    19. Redefined some pcre_uchar variables in pcre_exec.c as pcre_uint32; this
826        gives some modest performance improvement in 8-bit mode.
828    20. Added the PCRE-specific property \p{Xuc} for matching characters that can
829        be expressed in certain programming languages using Universal Character
830        Names.
832    21. Unicode validation has been updated in the light of Unicode Corrigendum #9,
833        which points out that "non characters" are not "characters that may not
834        appear in Unicode strings" but rather "characters that are reserved for
835        internal use and have only local meaning".
837    22. When a pattern was compiled with automatic callouts (PCRE_AUTO_CALLOUT) and
838        there was a conditional group that depended on an assertion, if the
839        assertion was false, the callout that immediately followed the alternation
840        in the condition was skipped when pcre_exec() was used for matching.
842    23. Allow an explicit callout to be inserted before an assertion that is the
843        condition for a conditional group, for compatibility with automatic
844        callouts, which always insert a callout at this point.
846    24. In 8.31, (*COMMIT) was confined to within a recursive subpattern. Perl also
847        confines (*SKIP) and (*PRUNE) in the same way, and this has now been done.
849    25. (*PRUNE) is now supported by the JIT compiler.
851    26. Fix infinite loop when /(?<=(*SKIP)ac)a/ is matched against aa.
853    27. Fix the case where there are two or more SKIPs with arguments that may be
854        ignored.
856    28. (*SKIP) is now supported by the JIT compiler.
858    29. (*THEN) is now supported by the JIT compiler.
860    30. Update RunTest with additional test selector options.
862    31. The way PCRE handles backtracking verbs has been changed in two ways.
864        (1) Previously, in something like (*COMMIT)(*SKIP), COMMIT would override
865        SKIP. Now, PCRE acts on whichever backtracking verb is reached first by
866        backtracking. In some cases this makes it more Perl-compatible, but Perl's
867        rather obscure rules do not always do the same thing.
869        (2) Previously, backtracking verbs were confined within assertions. This is
870        no longer the case for positive assertions, except for (*ACCEPT). Again,
871        this sometimes improves Perl compatibility, and sometimes does not.
873    32. A number of tests that were in test 2 because Perl did things differently
874        have been moved to test 1, because either Perl or PCRE has changed, and
875        these tests are now compatible.
877    32. Backtracking control verbs are now handled in the same way in JIT and
878        interpreter.
880    33. An opening parenthesis in a MARK/PRUNE/SKIP/THEN name in a pattern that
881        contained a forward subroutine reference caused a compile error.
883    34. Auto-detect and optimize limited repetitions in JIT.
885    35. Implement PCRE_NEVER_UTF to lock out the use of UTF, in particular,
886        blocking (*UTF) etc.
888    36. In the interpreter, maximizing pattern repetitions for characters and
889        character types now use tail recursion, which reduces stack usage.
891    37. The value of the max lookbehind was not correctly preserved if a compiled
892        and saved regex was reloaded on a host of different endianness.
894    38. Implemented (*LIMIT_MATCH) and (*LIMIT_RECURSION). As part of the extension
895        of the compiled pattern block, expand the flags field from 16 to 32 bits
896        because it was almost full.
898    39. Try madvise first before posix_madvise.
900    40. Change 7 for PCRE 7.9 made it impossible for pcregrep to find empty lines
901        with a pattern such as ^$. It has taken 4 years for anybody to notice! The
902        original change locked out all matches of empty strings. This has been
903        changed so that one match of an empty string per line is recognized.
904        Subsequent searches on the same line (for colouring or for --only-matching,
905        for example) do not recognize empty strings.
907    41. Applied a user patch to fix a number of spelling mistakes in comments.
909    42. Data lines longer than 65536 caused pcretest to crash.
911    43. Clarified the data type for length and startoffset arguments for pcre_exec
912        and pcre_dfa_exec in the function-specific man pages, where they were
913        explicitly stated to be in bytes, never having been updated. I also added
914        some clarification to the pcreapi man page.
916    44. A call to pcre_dfa_exec() with an output vector size less than 2 caused
917        a segmentation fault.
920    Version 8.32 30-November-2012
921    -----------------------------
923  1.  Improved JIT compiler optimizations for first character search and single  1.  Improved JIT compiler optimizations for first character search and single
924      character iterators.      character iterators.
# Line 16  Version 8.32 Line 932  Version 8.32
933  5.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.  5.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.
934      Reported by Giuseppe D'Angelo.      Reported by Giuseppe D'Angelo.
936  6.  The PCRE_STARTLINE bit, indicating that a match can occur only at the start  6.  The PCRE_STARTLINE bit, indicating that a match can occur only at the start
937      of a line, was being set incorrectly in cases where .* appeared inside      of a line, was being set incorrectly in cases where .* appeared inside
938      atomic brackets at the start of a pattern, or where there was a subsequent      atomic brackets at the start of a pattern, or where there was a subsequent
939      *PRUNE or *SKIP.      *PRUNE or *SKIP.
941  7.  Improved instruction cache flush for POWER/PowerPC.  7.  Improved instruction cache flush for POWER/PowerPC.
942      Patch by Daniel Richard G.      Patch by Daniel Richard G.
944  8.  Fixed a number of issues in pcregrep, making it more compatible with GNU  8.  Fixed a number of issues in pcregrep, making it more compatible with GNU
945      grep:      grep:
947      (a) There is now no limit to the number of patterns to be matched.      (a) There is now no limit to the number of patterns to be matched.
949      (b) An error is given if a pattern is too long.      (b) An error is given if a pattern is too long.
951      (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir      (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir
952          are now supported.          are now supported.
954      (d) --exclude-from and --include-from (multiple use) have been added.      (d) --exclude-from and --include-from (multiple use) have been added.
956      (e) Exclusions and inclusions now apply to all files and directories, not      (e) Exclusions and inclusions now apply to all files and directories, not
957          just to those obtained from scanning a directory recursively.          just to those obtained from scanning a directory recursively.
959      (f) Multiple uses of -f and --file-list are now supported.      (f) Multiple uses of -f and --file-list are now supported.
961      (g) In a Windows environment, the default for -d has been changed from      (g) In a Windows environment, the default for -d has been changed from
962          "read" (the GNU grep default) to "skip", because otherwise the presence          "read" (the GNU grep default) to "skip", because otherwise the presence
963          of a directory in the file list provokes an error.          of a directory in the file list provokes an error.
965      (h) The documentation has been revised and clarified in places.      (h) The documentation has been revised and clarified in places.
967  9.  Improve the matching speed of capturing brackets.  9.  Improve the matching speed of capturing brackets.
969  10. Changed the meaning of \X so that it now matches a Unicode extended  10. Changed the meaning of \X so that it now matches a Unicode extended
970      grapheme cluster.      grapheme cluster.
972  11. Patch by Daniel Richard G to the autoconf files to add a macro for sorting  11. Patch by Daniel Richard G to the autoconf files to add a macro for sorting
973      out POSIX threads when JIT support is configured.      out POSIX threads when JIT support is configured.
975  12. Added support for PCRE_STUDY_EXTRA_NEEDED.  12. Added support for PCRE_STUDY_EXTRA_NEEDED.
977  13. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg  13. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg
978      structure could go wrong in environments where size_t is not the same size      structure could go wrong in environments where size_t is not the same size
979      as int.      as int.
981  14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be  14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be
982      set.      set.
984  15. The EBCDIC support had decayed; later updates to the code had included  15. The EBCDIC support had decayed; later updates to the code had included
985      explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a      explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a
986      general tidy up of EBCDIC-related issues, and the documentation was also      general tidy up of EBCDIC-related issues, and the documentation was also
987      not quite right. There is now a test that can be run on ASCII systems to      not quite right. There is now a test that can be run on ASCII systems to
988      check some of the EBCDIC-related things (but is it not a full test).      check some of the EBCDIC-related things (but is it not a full test).
990    16. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting
991        in a small tidy to the code.
993    17. Fix JIT tests when UTF is disabled and both 8 and 16 bit mode are enabled.
995    18. If the --only-matching (-o) option in pcregrep is specified multiple
996        times, each one causes appropriate output. For example, -o1 -o2 outputs the
997        substrings matched by the 1st and 2nd capturing parentheses. A separating
998        string can be specified by --om-separator (default empty).
1000    19. Improving the first n character searches.
1002    20. Turn case lists for horizontal and vertical white space into macros so that
1003        they are defined only once.
1005    21. This set of changes together give more compatible Unicode case-folding
1006        behaviour for characters that have more than one other case when UCP
1007        support is available.
1009        (a) The Unicode property table now has offsets into a new table of sets of
1010            three or more characters that are case-equivalent. The MultiStage2.py
1011            script that generates these tables (the pcre_ucd.c file) now scans
1012            CaseFolding.txt instead of UnicodeData.txt for character case
1013            information.
1015        (b) The code for adding characters or ranges of characters to a character
1016            class has been abstracted into a generalized function that also handles
1017            case-independence. In UTF-mode with UCP support, this uses the new data
1018            to handle characters with more than one other case.
1020        (c) A bug that is fixed as a result of (b) is that codepoints less than 256
1021            whose other case is greater than 256 are now correctly matched
1022            caselessly. Previously, the high codepoint matched the low one, but not
1023            vice versa.
1025        (d) The processing of \h, \H, \v, and \ in character classes now makes use
1026            of the new class addition function, using character lists defined as
1027            macros alongside the case definitions of 20 above.
1029        (e) Caseless back references now work with characters that have more than
1030            one other case.
1032        (f) General caseless matching of characters with more than one other case
1033            is supported.
1035    22. Unicode character properties were updated from Unicode 6.2.0
1037    23. Improved CMake support under Windows. Patch by Daniel Richard G.
1039    24. Add support for 32-bit character strings, and UTF-32
1041    25. Major JIT compiler update (code refactoring and bugfixing).
1042        Experimental Sparc 32 support is added.
1044    26. Applied a modified version of Daniel Richard G's patch to create
1045        pcre.h.generic and config.h.generic by "make" instead of in the
1046        PrepareRelease script.
1048    27. Added a definition for CHAR_NULL (helpful for the z/OS port), and use it in
1049        pcre_compile.c when checking for a zero character.
1051    28. Introducing a native interface for JIT. Through this interface, the compiled
1052        machine code can be directly executed. The purpose of this interface is to
1053        provide fast pattern matching, so several sanity checks are not performed.
1054        However, feature tests are still performed. The new interface provides
1055        1.4x speedup compared to the old one.
1057    29. If pcre_exec() or pcre_dfa_exec() was called with a negative value for
1058        the subject string length, the error given was PCRE_ERROR_BADOFFSET, which
1059        was confusing. There is now a new error PCRE_ERROR_BADLENGTH for this case.
1061    30. In 8-bit UTF-8 mode, pcretest failed to give an error for data codepoints
1062        greater than 0x7fffffff (which cannot be represented in UTF-8, even under
1063        the "old" RFC 2279). Instead, it ended up passing a negative length to
1064        pcre_exec().
1066    31. Add support for GCC's visibility feature to hide internal functions.
1068    32. Running "pcretest -C pcre8" or "pcretest -C pcre16" gave a spurious error
1069        "unknown -C option" after outputting 0 or 1.
1071    33. There is now support for generating a code coverage report for the test
1072        suite in environments where gcc is the compiler and lcov is installed. This
1073        is mainly for the benefit of the developers.
1075    34. If PCRE is built with --enable-valgrind, certain memory regions are marked
1076        unaddressable using valgrind annotations, allowing valgrind to detect
1077        invalid memory accesses. This is mainly for the benefit of the developers.
1079    25. (*UTF) can now be used to start a pattern in any of the three libraries.
1081    26. Give configure error if --enable-cpp but no C++ compiler found.
1084  Version 8.31 06-July-2012  Version 8.31 06-July-2012
# Line 1416  Version 7.9 11-Apr-09 Line 2424  Version 7.9 11-Apr-09
2424  7.  A pattern that could match an empty string could cause pcregrep to loop; it  7.  A pattern that could match an empty string could cause pcregrep to loop; it
2425      doesn't make sense to accept an empty string match in pcregrep, so I have      doesn't make sense to accept an empty string match in pcregrep, so I have
2426      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
2427      seems to be how GNU grep behaves.      seems to be how GNU grep behaves. [But see later change 40 for release
2428        8.33.]
2430  8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at  8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
2431      start or after a newline", because the conditional assertion was not being      start or after a newline", because the conditional assertion was not being
# Line 1659  Version 7.7 07-May-08 Line 2668  Version 7.7 07-May-08
2668      containing () gave an internal compiling error instead of "reference to      containing () gave an internal compiling error instead of "reference to
2669      non-existent subpattern". Fortunately, when the pattern did exist, the      non-existent subpattern". Fortunately, when the pattern did exist, the
2670      compiled code was correct. (When scanning forwards to check for the      compiled code was correct. (When scanning forwards to check for the
2671      existencd of the subpattern, it was treating the data ']' as terminating      existence of the subpattern, it was treating the data ']' as terminating
2672      the class, so got the count wrong. When actually compiling, the reference      the class, so got the count wrong. When actually compiling, the reference
2673      was subsequently set up correctly.)      was subsequently set up correctly.)

Removed from v.1033  
changed lines
  Added in v.1600

  ViewVC Help
Powered by ViewVC 1.1.5