ViewVC logotype

Diff of /code/trunk/ChangeLog

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

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

Removed from v.989  
changed lines
  Added in v.1480

  ViewVC Help
Powered by ViewVC 1.1.5