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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.1041  
changed lines
  Added in v.1472

  ViewVC Help
Powered by ViewVC 1.1.5