/[pcre]/code/trunk/ChangeLog
ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 1011 by ph10, Sat Aug 25 11:36:15 2012 UTC revision 1515 by ph10, Tue Feb 3 17:08:54 2015 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.32  Version 8.37 xx-xxx-201x
5  ------------  ------------------------
6    
7    1.  When an (*ACCEPT) is triggered inside capturing parentheses, it arranges
8        for those parentheses to be closed with whatever has been captured so far.
9        However, it was failing to mark any other groups between the hightest
10        capture so far and the currrent group as "unset". Thus, the ovector for
11        those groups contained whatever was previously there. An example is the
12        pattern /(x)|((*ACCEPT))/ when matched against "abcd".
13    
14    2.  If an assertion condition was quantified with a minimum of zero (an odd
15        thing to do, but it happened), SIGSEGV or other misbehaviour could occur.
16    
17    3.  If a pattern in pcretest input had the P (POSIX) modifier followed by an
18        unrecognized modifier, a crash could occur.
19    
20    4.  An attempt to do global matching in pcretest with a zero-length ovector
21        caused a crash.
22    
23    
24    
25    Version 8.36 26-September-2014
26    ------------------------------
27    
28    1.  Got rid of some compiler warnings in the C++ modules that were shown up by
29        -Wmissing-field-initializers and -Wunused-parameter.
30    
31    2.  The tests for quantifiers being too big (greater than 65535) were being
32        applied after reading the number, and stupidly assuming that integer
33        overflow would give a negative number. The tests are now applied as the
34        numbers are read.
35    
36    3.  Tidy code in pcre_exec.c where two branches that used to be different are
37        now the same.
38    
39    4.  The JIT compiler did not generate match limit checks for certain
40        bracketed expressions with quantifiers. This may lead to exponential
41        backtracking, instead of returning with PCRE_ERROR_MATCHLIMIT. This
42        issue should be resolved now.
43    
44    5.  Fixed an issue, which occures when nested alternatives are optimized
45        with table jumps.
46    
47    6.  Inserted two casts and changed some ints to size_t in the light of some
48        reported 64-bit compiler warnings (Bugzilla 1477).
49    
50    7.  Fixed a bug concerned with zero-minimum possessive groups that could match
51        an empty string, which sometimes were behaving incorrectly in the
52        interpreter (though correctly in the JIT matcher). This pcretest input is
53        an example:
54    
55          '\A(?:[^"]++|"(?:[^"]*+|"")*+")++'
56          NON QUOTED "QUOT""ED" AFTER "NOT MATCHED
57    
58        the interpreter was reporting a match of 'NON QUOTED ' only, whereas the
59        JIT matcher and Perl both matched 'NON QUOTED "QUOT""ED" AFTER '. The test
60        for an empty string was breaking the inner loop and carrying on at a lower
61        level, when possessive repeated groups should always return to a higher
62        level as they have no backtrack points in them. The empty string test now
63        occurs at the outer level.
64    
65    8.  Fixed a bug that was incorrectly auto-possessifying \w+ in the pattern
66        ^\w+(?>\s*)(?<=\w) which caused it not to match "test test".
67    
68    9.  Give a compile-time error for \o{} (as Perl does) and for \x{} (which Perl
69        doesn't).
70    
71    10. Change 8.34/15 introduced a bug that caused the amount of memory needed
72        to hold a pattern to be incorrectly computed (too small) when there were
73        named back references to duplicated names. This could cause "internal
74        error: code overflow" or "double free or corruption" or other memory
75        handling errors.
76    
77    11. When named subpatterns had the same prefixes, back references could be
78        confused. For example, in this pattern:
79    
80          /(?P<Name>a)?(?P<Name2>b)?(?(<Name>)c|d)*l/
81    
82        the reference to 'Name' was incorrectly treated as a reference to a
83        duplicate name.
84    
85    12. A pattern such as /^s?c/mi8 where the optional character has more than
86        one "other case" was incorrectly compiled such that it would only try to
87        match starting at "c".
88    
89    13. When a pattern starting with \s was studied, VT was not included in the
90        list of possible starting characters; this should have been part of the
91        8.34/18 patch.
92    
93    14. If a character class started [\Qx]... where x is any character, the class
94        was incorrectly terminated at the ].
95    
96    15. If a pattern that started with a caseless match for a character with more
97        than one "other case" was studied, PCRE did not set up the starting code
98        unit bit map for the list of possible characters. Now it does. This is an
99        optimization improvement, not a bug fix.
100    
101    16. The Unicode data tables have been updated to Unicode 7.0.0.
102    
103    17. Fixed a number of memory leaks in pcregrep.
104    
105    18. Avoid a compiler warning (from some compilers) for a function call with
106        a cast that removes "const" from an lvalue by using an intermediate
107        variable (to which the compiler does not object).
108    
109    19. Incorrect code was compiled if a group that contained an internal recursive
110        back reference was optional (had quantifier with a minimum of zero). This
111        example compiled incorrect code: /(((a\2)|(a*)\g<-1>))*/ and other examples
112        caused segmentation faults because of stack overflows at compile time.
113    
114    20. A pattern such as /((?(R)a|(?1)))+/, which contains a recursion within a
115        group that is quantified with an indefinite repeat, caused a compile-time
116        loop which used up all the system stack and provoked a segmentation fault.
117        This was not the same bug as 19 above.
118    
119    21. Add PCRECPP_EXP_DECL declaration to operator<< in pcre_stringpiece.h.
120        Patch by Mike Frysinger.
121    
122    
123    Version 8.35 04-April-2014
124    --------------------------
125    
126    1.  A new flag is set, when property checks are present in an XCLASS.
127        When this flag is not set, PCRE can perform certain optimizations
128        such as studying these XCLASS-es.
129    
130    2.  The auto-possessification of character sets were improved: a normal
131        and an extended character set can be compared now. Furthermore
132        the JIT compiler optimizes more character set checks.
133    
134    3.  Got rid of some compiler warnings for potentially uninitialized variables
135        that show up only when compiled with -O2.
136    
137    4.  A pattern such as (?=ab\K) that uses \K in an assertion can set the start
138        of a match later then the end of the match. The pcretest program was not
139        handling the case sensibly - it was outputting from the start to the next
140        binary zero. It now reports this situation in a message, and outputs the
141        text from the end to the start.
142    
143    5.  Fast forward search is improved in JIT. Instead of the first three
144        characters, any three characters with fixed position can be searched.
145        Search order: first, last, middle.
146    
147    6.  Improve character range checks in JIT. Characters are read by an inprecise
148        function now, which returns with an unknown value if the character code is
149        above a certain threshold (e.g: 256). The only limitation is that the value
150        must be bigger than the threshold as well. This function is useful when
151        the characters above the threshold are handled in the same way.
152    
153    7.  The macros whose names start with RAWUCHAR are placeholders for a future
154        mode in which only the bottom 21 bits of 32-bit data items are used. To
155        make this more memorable for those maintaining the code, the names have
156        been changed to start with UCHAR21, and an extensive comment has been added
157        to their definition.
158    
159    8.  Add missing (new) files sljitNativeTILEGX.c and sljitNativeTILEGX-encoder.c
160        to the export list in Makefile.am (they were accidentally omitted from the
161        8.34 tarball).
162    
163    9.  The informational output from pcretest used the phrase "starting byte set"
164        which is inappropriate for the 16-bit and 32-bit libraries. As the output
165        for "first char" and "need char" really means "non-UTF-char", I've changed
166        "byte" to "char", and slightly reworded the output. The documentation about
167        these values has also been (I hope) clarified.
168    
169    10. Another JIT related optimization: use table jumps for selecting the correct
170        backtracking path, when more than four alternatives are present inside a
171        bracket.
172    
173    11. Empty match is not possible, when the minimum length is greater than zero,
174        and there is no \K in the pattern. JIT should avoid empty match checks in
175        such cases.
176    
177    12. In a caseless character class with UCP support, when a character with more
178        than one alternative case was not the first character of a range, not all
179        the alternative cases were added to the class. For example, s and \x{17f}
180        are both alternative cases for S: the class [RST] was handled correctly,
181        but [R-T] was not.
182    
183    13. The configure.ac file always checked for pthread support when JIT was
184        enabled. This is not used in Windows, so I have put this test inside a
185        check for the presence of windows.h (which was already tested for).
186    
187    14. Improve pattern prefix search by a simplified Boyer-Moore algorithm in JIT.
188        The algorithm provides a way to skip certain starting offsets, and usually
189        faster than linear prefix searches.
190    
191    15. Change 13 for 8.20 updated RunTest to check for the 'fr' locale as well
192        as for 'fr_FR' and 'french'. For some reason, however, it then used the
193        Windows-specific input and output files, which have 'french' screwed in.
194        So this could never have worked. One of the problems with locales is that
195        they aren't always the same. I have now updated RunTest so that it checks
196        the output of the locale test (test 3) against three different output
197        files, and it allows the test to pass if any one of them matches. With luck
198        this should make the test pass on some versions of Solaris where it was
199        failing. Because of the uncertainty, the script did not used to stop if
200        test 3 failed; it now does. If further versions of a French locale ever
201        come to light, they can now easily be added.
202    
203    16. If --with-pcregrep-bufsize was given a non-integer value such as "50K",
204        there was a message during ./configure, but it did not stop. This now
205        provokes an error. The invalid example in README has been corrected.
206        If a value less than the minimum is given, the minimum value has always
207        been used, but now a warning is given.
208    
209    17. If --enable-bsr-anycrlf was set, the special 16/32-bit test failed. This
210        was a bug in the test system, which is now fixed. Also, the list of various
211        configurations that are tested for each release did not have one with both
212        16/32 bits and --enable-bar-anycrlf. It now does.
213    
214    18. pcretest was missing "-C bsr" for displaying the \R default setting.
215    
216    19. Little endian PowerPC systems are supported now by the JIT compiler.
217    
218    20. The fast forward newline mechanism could enter to an infinite loop on
219        certain invalid UTF-8 input. Although we don't support these cases
220        this issue can be fixed by a performance optimization.
221    
222    21. Change 33 of 8.34 is not sufficient to ensure stack safety because it does
223        not take account if existing stack usage. There is now a new global
224        variable called pcre_stack_guard that can be set to point to an external
225        function to check stack availability. It is called at the start of
226        processing every parenthesized group.
227    
228    22. A typo in the code meant that in ungreedy mode the max/min qualifier
229        behaved like a min-possessive qualifier, and, for example, /a{1,3}b/U did
230        not match "ab".
231    
232    23. When UTF was disabled, the JIT program reported some incorrect compile
233        errors. These messages are silenced now.
234    
235    24. Experimental support for ARM-64 and MIPS-64 has been added to the JIT
236        compiler.
237    
238    25. Change all the temporary files used in RunGrepTest to be different to those
239        used by RunTest so that the tests can be run simultaneously, for example by
240        "make -j check".
241    
242    
243    Version 8.34 15-December-2013
244    -----------------------------
245    
246    1.  Add pcre[16|32]_jit_free_unused_memory to forcibly free unused JIT
247        executable memory. Patch inspired by Carsten Klein.
248    
249    2.  ./configure --enable-coverage defined SUPPORT_GCOV in config.h, although
250        this macro is never tested and has no effect, because the work to support
251        coverage involves only compiling and linking options and special targets in
252        the Makefile. The comment in config.h implied that defining the macro would
253        enable coverage support, which is totally false. There was also support for
254        setting this macro in the CMake files (my fault, I just copied it from
255        configure). SUPPORT_GCOV has now been removed.
256    
257    3.  Make a small performance improvement in strlen16() and strlen32() in
258        pcretest.
259    
260    4.  Change 36 for 8.33 left some unreachable statements in pcre_exec.c,
261        detected by the Solaris compiler (gcc doesn't seem to be able to diagnose
262        these cases). There was also one in pcretest.c.
263    
264    5.  Cleaned up a "may be uninitialized" compiler warning in pcre_exec.c.
265    
266    6.  In UTF mode, the code for checking whether a group could match an empty
267        string (which is used for indefinitely repeated groups to allow for
268        breaking an infinite loop) was broken when the group contained a repeated
269        negated single-character class with a character that occupied more than one
270        data item and had a minimum repetition of zero (for example, [^\x{100}]* in
271        UTF-8 mode). The effect was undefined: the group might or might not be
272        deemed as matching an empty string, or the program might have crashed.
273    
274    7.  The code for checking whether a group could match an empty string was not
275        recognizing that \h, \H, \v, \V, and \R must match a character.
276    
277    8.  Implemented PCRE_INFO_MATCH_EMPTY, which yields 1 if the pattern can match
278        an empty string. If it can, pcretest shows this in its information output.
279    
280    9.  Fixed two related bugs that applied to Unicode extended grapheme clusters
281        that were repeated with a maximizing qualifier (e.g. \X* or \X{2,5}) when
282        matched by pcre_exec() without using JIT:
283    
284        (a) If the rest of the pattern did not match after a maximal run of
285            grapheme clusters, the code for backing up to try with fewer of them
286            did not always back up over a full grapheme when characters that do not
287            have the modifier quality were involved, e.g. Hangul syllables.
288    
289        (b) If the match point in a subject started with modifier character, and
290            there was no match, the code could incorrectly back up beyond the match
291            point, and potentially beyond the first character in the subject,
292            leading to a segfault or an incorrect match result.
293    
294    10. A conditional group with an assertion condition could lead to PCRE
295        recording an incorrect first data item for a match if no other first data
296        item was recorded. For example, the pattern (?(?=ab)ab) recorded "a" as a
297        first data item, and therefore matched "ca" after "c" instead of at the
298        start.
299    
300    11. Change 40 for 8.33 (allowing pcregrep to find empty strings) showed up a
301        bug that caused the command "echo a | ./pcregrep -M '|a'" to loop.
302    
303    12. The source of pcregrep now includes z/OS-specific code so that it can be
304        compiled for z/OS as part of the special z/OS distribution.
305    
306    13. Added the -T and -TM options to pcretest.
307    
308    14. The code in pcre_compile.c for creating the table of named capturing groups
309        has been refactored. Instead of creating the table dynamically during the
310        actual compiling pass, the information is remembered during the pre-compile
311        pass (on the stack unless there are more than 20 named groups, in which
312        case malloc() is used) and the whole table is created before the actual
313        compile happens. This has simplified the code (it is now nearly 150 lines
314        shorter) and prepared the way for better handling of references to groups
315        with duplicate names.
316    
317    15. A back reference to a named subpattern when there is more than one of the
318        same name now checks them in the order in which they appear in the pattern.
319        The first one that is set is used for the reference. Previously only the
320        first one was inspected. This change makes PCRE more compatible with Perl.
321    
322    16. Unicode character properties were updated from Unicode 6.3.0.
323    
324    17. The compile-time code for auto-possessification has been refactored, based
325        on a patch by Zoltan Herczeg. It now happens after instead of during
326        compilation. The code is cleaner, and more cases are handled. The option
327        PCRE_NO_AUTO_POSSESS is added for testing purposes, and the -O and /O
328        options in pcretest are provided to set it. It can also be set by
329        (*NO_AUTO_POSSESS) at the start of a pattern.
330    
331    18. The character VT has been added to the default ("C" locale) set of
332        characters that match \s and are generally treated as white space,
333        following this same change in Perl 5.18. There is now no difference between
334        "Perl space" and "POSIX space". Whether VT is treated as white space in
335        other locales depends on the locale.
336    
337    19. The code for checking named groups as conditions, either for being set or
338        for being recursed, has been refactored (this is related to 14 and 15
339        above). Processing unduplicated named groups should now be as fast at
340        numerical groups, and processing duplicated groups should be faster than
341        before.
342    
343    20. Two patches to the CMake build system, by Alexander Barkov:
344    
345          (1) Replace the "source" command by "." in CMakeLists.txt because
346              "source" is a bash-ism.
347    
348          (2) Add missing HAVE_STDINT_H and HAVE_INTTYPES_H to config-cmake.h.in;
349              without these the CMake build does not work on Solaris.
350    
351    21. Perl has changed its handling of \8 and \9. If there is no previously
352        encountered capturing group of those numbers, they are treated as the
353        literal characters 8 and 9 instead of a binary zero followed by the
354        literals. PCRE now does the same.
355    
356    22. Following Perl, added \o{} to specify codepoints in octal, making it
357        possible to specify values greater than 0777 and also making them
358        unambiguous.
359    
360    23. Perl now gives an error for missing closing braces after \x{... instead of
361        treating the string as literal. PCRE now does the same.
362    
363    24. RunTest used to grumble if an inappropriate test was selected explicitly,
364        but just skip it when running all tests. This make it awkward to run ranges
365        of tests when one of them was inappropriate. Now it just skips any
366        inappropriate tests, as it always did when running all tests.
367    
368    25. If PCRE_AUTO_CALLOUT and PCRE_UCP were set for a pattern that contained
369        character types such as \d or \w, too many callouts were inserted, and the
370        data that they returned was rubbish.
371    
372    26. In UCP mode, \s was not matching two of the characters that Perl matches,
373        namely NEL (U+0085) and MONGOLIAN VOWEL SEPARATOR (U+180E), though they
374        were matched by \h. The code has now been refactored so that the lists of
375        the horizontal and vertical whitespace characters used for \h and \v (which
376        are defined only in one place) are now also used for \s.
377    
378    27. Add JIT support for the 64 bit TileGX architecture.
379        Patch by Jiong Wang (Tilera Corporation).
380    
381    28. Possessive quantifiers for classes (both explicit and automatically
382        generated) now use special opcodes instead of wrapping in ONCE brackets.
383    
384    29. Whereas an item such as A{4}+ ignored the possessivenes of the quantifier
385        (because it's meaningless), this was not happening when PCRE_CASELESS was
386        set. Not wrong, but inefficient.
387    
388    30. Updated perltest.pl to add /u (force Unicode mode) when /W (use Unicode
389        properties for \w, \d, etc) is present in a test regex. Otherwise if the
390        test contains no characters greater than 255, Perl doesn't realise it
391        should be using Unicode semantics.
392    
393    31. Upgraded the handling of the POSIX classes [:graph:], [:print:], and
394        [:punct:] when PCRE_UCP is set so as to include the same characters as Perl
395        does in Unicode mode.
396    
397    32. Added the "forbid" facility to pcretest so that putting tests into the
398        wrong test files can sometimes be quickly detected.
399    
400    33. There is now a limit (default 250) on the depth of nesting of parentheses.
401        This limit is imposed to control the amount of system stack used at compile
402        time. It can be changed at build time by --with-parens-nest-limit=xxx or
403        the equivalent in CMake.
404    
405    34. Character classes such as [A-\d] or [a-[:digit:]] now cause compile-time
406        errors. Perl warns for these when in warning mode, but PCRE has no facility
407        for giving warnings.
408    
409    35. Change 34 for 8.13 allowed quantifiers on assertions, because Perl does.
410        However, this was not working for (?!) because it is optimized to (*FAIL),
411        for which PCRE does not allow quantifiers. The optimization is now disabled
412        when a quantifier follows (?!). I can't see any use for this, but it makes
413        things uniform.
414    
415    36. Perl no longer allows group names to start with digits, so I have made this
416        change also in PCRE. It simplifies the code a bit.
417    
418    37. In extended mode, Perl ignores spaces before a + that indicates a
419        possessive quantifier. PCRE allowed a space before the quantifier, but not
420        before the possessive +. It now does.
421    
422    38. The use of \K (reset reported match start) within a repeated possessive
423        group such as (a\Kb)*+ was not working.
424    
425    40. Document that the same character tables must be used at compile time and
426        run time, and that the facility to pass tables to pcre_exec() and
427        pcre_dfa_exec() is for use only with saved/restored patterns.
428    
429    41. Applied Jeff Trawick's patch CMakeLists.txt, which "provides two new
430        features for Builds with MSVC:
431    
432        1. Support pcre.rc and/or pcreposix.rc (as is already done for MinGW
433           builds). The .rc files can be used to set FileDescription and many other
434           attributes.
435    
436        2. Add an option (-DINSTALL_MSVC_PDB) to enable installation of .pdb files.
437           This allows higher-level build scripts which want .pdb files to avoid
438           hard-coding the exact files needed."
439    
440    42. Added support for [[:<:]] and [[:>:]] as used in the BSD POSIX library to
441        mean "start of word" and "end of word", respectively, as a transition aid.
442    
443    43. A minimizing repeat of a class containing codepoints greater than 255 in
444        non-UTF 16-bit or 32-bit modes caused an internal error when PCRE was
445        compiled to use the heap for recursion.
446    
447    44. Got rid of some compiler warnings for unused variables when UTF but not UCP
448        is configured.
449    
450    
451    Version 8.33 28-May-2013
452    ------------------------
453    
454    1.  Added 'U' to some constants that are compared to unsigned integers, to
455        avoid compiler signed/unsigned warnings. Added (int) casts to unsigned
456        variables that are added to signed variables, to ensure the result is
457        signed and can be negated.
458    
459    2.  Applied patch by Daniel Richard G for quashing MSVC warnings to the
460        CMake config files.
461    
462    3.  Revise the creation of config.h.generic so that all boolean macros are
463        #undefined, whereas non-boolean macros are #ifndef/#endif-ed. This makes
464        overriding via -D on the command line possible.
465    
466    4.  Changing the definition of the variable "op" in pcre_exec.c from pcre_uchar
467        to unsigned int is reported to make a quite noticeable speed difference in
468        a specific Windows environment. Testing on Linux did also appear to show
469        some benefit (and it is clearly not harmful). Also fixed the definition of
470        Xop which should be unsigned.
471    
472    5.  Related to (4), changing the definition of the intermediate variable cc
473        in repeated character loops from pcre_uchar to pcre_uint32 also gave speed
474        improvements.
475    
476    6.  Fix forward search in JIT when link size is 3 or greater. Also removed some
477        unnecessary spaces.
478    
479    7.  Adjust autogen.sh and configure.ac to lose warnings given by automake 1.12
480        and later.
481    
482    8.  Fix two buffer over read issues in 16 and 32 bit modes. Affects JIT only.
483    
484    9.  Optimizing fast_forward_start_bits in JIT.
485    
486    10. Adding support for callouts in JIT, and fixing some issues revealed
487        during this work. Namely:
488    
489        (a) Unoptimized capturing brackets incorrectly reset on backtrack.
490    
491        (b) Minimum length was not checked before the matching is started.
492    
493    11. The value of capture_last that is passed to callouts was incorrect in some
494        cases when there was a capture on one path that was subsequently abandoned
495        after a backtrack. Also, the capture_last value is now reset after a
496        recursion, since all captures are also reset in this case.
497    
498    12. The interpreter no longer returns the "too many substrings" error in the
499        case when an overflowing capture is in a branch that is subsequently
500        abandoned after a backtrack.
501    
502    13. In the pathological case when an offset vector of size 2 is used, pcretest
503        now prints out the matched string after a yield of 0 or 1.
504    
505    14. Inlining subpatterns in recursions, when certain conditions are fulfilled.
506        Only supported by the JIT compiler at the moment.
507    
508    15. JIT compiler now supports 32 bit Macs thanks to Lawrence Velazquez.
509    
510    16. Partial matches now set offsets[2] to the "bumpalong" value, that is, the
511        offset of the starting point of the matching process, provided the offsets
512        vector is large enough.
513    
514    17. The \A escape now records a lookbehind value of 1, though its execution
515        does not actually inspect the previous character. This is to ensure that,
516        in partial multi-segment matching, at least one character from the old
517        segment is retained when a new segment is processed. Otherwise, if there
518        are no lookbehinds in the pattern, \A might match incorrectly at the start
519        of a new segment.
520    
521    18. Added some #ifdef __VMS code into pcretest.c to help VMS implementations.
522    
523    19. Redefined some pcre_uchar variables in pcre_exec.c as pcre_uint32; this
524        gives some modest performance improvement in 8-bit mode.
525    
526    20. Added the PCRE-specific property \p{Xuc} for matching characters that can
527        be expressed in certain programming languages using Universal Character
528        Names.
529    
530    21. Unicode validation has been updated in the light of Unicode Corrigendum #9,
531        which points out that "non characters" are not "characters that may not
532        appear in Unicode strings" but rather "characters that are reserved for
533        internal use and have only local meaning".
534    
535    22. When a pattern was compiled with automatic callouts (PCRE_AUTO_CALLOUT) and
536        there was a conditional group that depended on an assertion, if the
537        assertion was false, the callout that immediately followed the alternation
538        in the condition was skipped when pcre_exec() was used for matching.
539    
540    23. Allow an explicit callout to be inserted before an assertion that is the
541        condition for a conditional group, for compatibility with automatic
542        callouts, which always insert a callout at this point.
543    
544    24. In 8.31, (*COMMIT) was confined to within a recursive subpattern. Perl also
545        confines (*SKIP) and (*PRUNE) in the same way, and this has now been done.
546    
547    25. (*PRUNE) is now supported by the JIT compiler.
548    
549    26. Fix infinite loop when /(?<=(*SKIP)ac)a/ is matched against aa.
550    
551    27. Fix the case where there are two or more SKIPs with arguments that may be
552        ignored.
553    
554    28. (*SKIP) is now supported by the JIT compiler.
555    
556    29. (*THEN) is now supported by the JIT compiler.
557    
558    30. Update RunTest with additional test selector options.
559    
560    31. The way PCRE handles backtracking verbs has been changed in two ways.
561    
562        (1) Previously, in something like (*COMMIT)(*SKIP), COMMIT would override
563        SKIP. Now, PCRE acts on whichever backtracking verb is reached first by
564        backtracking. In some cases this makes it more Perl-compatible, but Perl's
565        rather obscure rules do not always do the same thing.
566    
567        (2) Previously, backtracking verbs were confined within assertions. This is
568        no longer the case for positive assertions, except for (*ACCEPT). Again,
569        this sometimes improves Perl compatibility, and sometimes does not.
570    
571    32. A number of tests that were in test 2 because Perl did things differently
572        have been moved to test 1, because either Perl or PCRE has changed, and
573        these tests are now compatible.
574    
575    32. Backtracking control verbs are now handled in the same way in JIT and
576        interpreter.
577    
578    33. An opening parenthesis in a MARK/PRUNE/SKIP/THEN name in a pattern that
579        contained a forward subroutine reference caused a compile error.
580    
581    34. Auto-detect and optimize limited repetitions in JIT.
582    
583    35. Implement PCRE_NEVER_UTF to lock out the use of UTF, in particular,
584        blocking (*UTF) etc.
585    
586    36. In the interpreter, maximizing pattern repetitions for characters and
587        character types now use tail recursion, which reduces stack usage.
588    
589    37. The value of the max lookbehind was not correctly preserved if a compiled
590        and saved regex was reloaded on a host of different endianness.
591    
592    38. Implemented (*LIMIT_MATCH) and (*LIMIT_RECURSION). As part of the extension
593        of the compiled pattern block, expand the flags field from 16 to 32 bits
594        because it was almost full.
595    
596    39. Try madvise first before posix_madvise.
597    
598    40. Change 7 for PCRE 7.9 made it impossible for pcregrep to find empty lines
599        with a pattern such as ^$. It has taken 4 years for anybody to notice! The
600        original change locked out all matches of empty strings. This has been
601        changed so that one match of an empty string per line is recognized.
602        Subsequent searches on the same line (for colouring or for --only-matching,
603        for example) do not recognize empty strings.
604    
605    41. Applied a user patch to fix a number of spelling mistakes in comments.
606    
607    42. Data lines longer than 65536 caused pcretest to crash.
608    
609    43. Clarified the data type for length and startoffset arguments for pcre_exec
610        and pcre_dfa_exec in the function-specific man pages, where they were
611        explicitly stated to be in bytes, never having been updated. I also added
612        some clarification to the pcreapi man page.
613    
614    44. A call to pcre_dfa_exec() with an output vector size less than 2 caused
615        a segmentation fault.
616    
617    
618    Version 8.32 30-November-2012
619    -----------------------------
620    
621  1.  Improved JIT compiler optimizations for first character search and single  1.  Improved JIT compiler optimizations for first character search and single
622      character iterators.      character iterators.
# Line 16  Version 8.32 Line 630  Version 8.32
630    
631  5.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.  5.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.
632      Reported by Giuseppe D'Angelo.      Reported by Giuseppe D'Angelo.
633    
634  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
635      of a line, was being set incorrectly in cases where .* appeared inside      of a line, was being set incorrectly in cases where .* appeared inside
636      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
637      *PRUNE or *SKIP.      *PRUNE or *SKIP.
638    
639  7.  Improved instruction cache flush for POWER/PowerPC.  7.  Improved instruction cache flush for POWER/PowerPC.
640      Patch by Daniel Richard G.      Patch by Daniel Richard G.
641    
642  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
643      grep:      grep:
644    
645      (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.
646    
647      (b) An error is given if a pattern is too long.      (b) An error is given if a pattern is too long.
648    
649      (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir      (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir
650          are now supported.          are now supported.
651    
652      (d) --exclude-from and --include-from (multiple use) have been added.      (d) --exclude-from and --include-from (multiple use) have been added.
653    
654      (e) Exclusions and inclusions now apply to all files and directories, not      (e) Exclusions and inclusions now apply to all files and directories, not
655          just to those obtained from scanning a directory recursively.          just to those obtained from scanning a directory recursively.
656    
657      (f) Multiple uses of -f and --file-list are now supported.      (f) Multiple uses of -f and --file-list are now supported.
658    
659      (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
660          "read" (the GNU grep default) to "skip", because otherwise the presence          "read" (the GNU grep default) to "skip", because otherwise the presence
661          of a directory in the file list provokes an error.          of a directory in the file list provokes an error.
662    
663      (h) The documentation has been revised and clarified in places.      (h) The documentation has been revised and clarified in places.
664    
665  9.  Improve the matching speed of capturing brackets.  9.  Improve the matching speed of capturing brackets.
666    
667  10. Changed the meaning of \X in the interpreters so that it now matches a  10. Changed the meaning of \X so that it now matches a Unicode extended
668      Unicode extended grapheme cluster.      grapheme cluster.
669    
670    11. Patch by Daniel Richard G to the autoconf files to add a macro for sorting
671        out POSIX threads when JIT support is configured.
672    
673    12. Added support for PCRE_STUDY_EXTRA_NEEDED.
674    
675    13. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg
676        structure could go wrong in environments where size_t is not the same size
677        as int.
678    
679    14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be
680        set.
681    
682    15. The EBCDIC support had decayed; later updates to the code had included
683        explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a
684        general tidy up of EBCDIC-related issues, and the documentation was also
685        not quite right. There is now a test that can be run on ASCII systems to
686        check some of the EBCDIC-related things (but is it not a full test).
687    
688    16. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting
689        in a small tidy to the code.
690    
691    17. Fix JIT tests when UTF is disabled and both 8 and 16 bit mode are enabled.
692    
693    18. If the --only-matching (-o) option in pcregrep is specified multiple
694        times, each one causes appropriate output. For example, -o1 -o2 outputs the
695        substrings matched by the 1st and 2nd capturing parentheses. A separating
696        string can be specified by --om-separator (default empty).
697    
698    19. Improving the first n character searches.
699    
700    20. Turn case lists for horizontal and vertical white space into macros so that
701        they are defined only once.
702    
703    21. This set of changes together give more compatible Unicode case-folding
704        behaviour for characters that have more than one other case when UCP
705        support is available.
706    
707        (a) The Unicode property table now has offsets into a new table of sets of
708            three or more characters that are case-equivalent. The MultiStage2.py
709            script that generates these tables (the pcre_ucd.c file) now scans
710            CaseFolding.txt instead of UnicodeData.txt for character case
711            information.
712    
713        (b) The code for adding characters or ranges of characters to a character
714            class has been abstracted into a generalized function that also handles
715            case-independence. In UTF-mode with UCP support, this uses the new data
716            to handle characters with more than one other case.
717    
718        (c) A bug that is fixed as a result of (b) is that codepoints less than 256
719            whose other case is greater than 256 are now correctly matched
720            caselessly. Previously, the high codepoint matched the low one, but not
721            vice versa.
722    
723        (d) The processing of \h, \H, \v, and \ in character classes now makes use
724            of the new class addition function, using character lists defined as
725            macros alongside the case definitions of 20 above.
726    
727        (e) Caseless back references now work with characters that have more than
728            one other case.
729    
730        (f) General caseless matching of characters with more than one other case
731            is supported.
732    
733    22. Unicode character properties were updated from Unicode 6.2.0
734    
735    23. Improved CMake support under Windows. Patch by Daniel Richard G.
736    
737    24. Add support for 32-bit character strings, and UTF-32
738    
739    25. Major JIT compiler update (code refactoring and bugfixing).
740        Experimental Sparc 32 support is added.
741    
742    26. Applied a modified version of Daniel Richard G's patch to create
743        pcre.h.generic and config.h.generic by "make" instead of in the
744        PrepareRelease script.
745    
746    27. Added a definition for CHAR_NULL (helpful for the z/OS port), and use it in
747        pcre_compile.c when checking for a zero character.
748    
749    28. Introducing a native interface for JIT. Through this interface, the compiled
750        machine code can be directly executed. The purpose of this interface is to
751        provide fast pattern matching, so several sanity checks are not performed.
752        However, feature tests are still performed. The new interface provides
753        1.4x speedup compared to the old one.
754    
755    29. If pcre_exec() or pcre_dfa_exec() was called with a negative value for
756        the subject string length, the error given was PCRE_ERROR_BADOFFSET, which
757        was confusing. There is now a new error PCRE_ERROR_BADLENGTH for this case.
758    
759    30. In 8-bit UTF-8 mode, pcretest failed to give an error for data codepoints
760        greater than 0x7fffffff (which cannot be represented in UTF-8, even under
761        the "old" RFC 2279). Instead, it ended up passing a negative length to
762        pcre_exec().
763    
764    31. Add support for GCC's visibility feature to hide internal functions.
765    
766    32. Running "pcretest -C pcre8" or "pcretest -C pcre16" gave a spurious error
767        "unknown -C option" after outputting 0 or 1.
768    
769    33. There is now support for generating a code coverage report for the test
770        suite in environments where gcc is the compiler and lcov is installed. This
771        is mainly for the benefit of the developers.
772    
773    34. If PCRE is built with --enable-valgrind, certain memory regions are marked
774        unaddressable using valgrind annotations, allowing valgrind to detect
775        invalid memory accesses. This is mainly for the benefit of the developers.
776    
777    25. (*UTF) can now be used to start a pattern in any of the three libraries.
778    
779    26. Give configure error if --enable-cpp but no C++ compiler found.
780    
781    
782  Version 8.31 06-July-2012  Version 8.31 06-July-2012
# Line 1398  Version 7.9 11-Apr-09 Line 2122  Version 7.9 11-Apr-09
2122  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
2123      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
2124      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
2125      seems to be how GNU grep behaves.      seems to be how GNU grep behaves. [But see later change 40 for release
2126        8.33.]
2127    
2128  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
2129      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 1641  Version 7.7 07-May-08 Line 2366  Version 7.7 07-May-08
2366      containing () gave an internal compiling error instead of "reference to      containing () gave an internal compiling error instead of "reference to
2367      non-existent subpattern". Fortunately, when the pattern did exist, the      non-existent subpattern". Fortunately, when the pattern did exist, the
2368      compiled code was correct. (When scanning forwards to check for the      compiled code was correct. (When scanning forwards to check for the
2369      existencd of the subpattern, it was treating the data ']' as terminating      existence of the subpattern, it was treating the data ']' as terminating
2370      the class, so got the count wrong. When actually compiling, the reference      the class, so got the count wrong. When actually compiling, the reference
2371      was subsequently set up correctly.)      was subsequently set up correctly.)
2372    

Legend:
Removed from v.1011  
changed lines
  Added in v.1515

  ViewVC Help
Powered by ViewVC 1.1.5