ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 980 by ph10, Mon Jun 18 16:47:14 2012 UTC revision 1441 by zherczeg, Sat Jan 11 21:56:18 2014 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 8.31 02-June-2012  Version 8.35-RC1 xx-xxxx-201x
5    -----------------------------
7    1.  A new flag is set, when property checks are present in an XCLASS.
8        When this flag is not set, PCRE can perform certain optimizations
9        such as studying these XCLASS-es.
11    2.  The auto-possessification of character sets were improved: a normal
12        and an extended character set can be compared now. Furthermore
13        the JIT compiler optimizes more character set checks.
15    3.  Got rid of some compiler warnings for potentially uninitialized variables
16        that show up only when compiled with -O2.
18    4.  A pattern such as (?=ab\K) that uses \K in an assertion can set the start
19        of a match later then the end of the match. The pcretest program was not
20        handling the case sensibly - it was outputting from the start to the next
21        binary zero. It now reports this situation in a message, and outputs the
22        text from the end to the start.
24    5.  Fast forward search is improved in JIT. Instead of the first three
25        characters, any three characters with fixed position can be searched.
26        Search order: first, last, middle.
28    6.  Improve character range checks in JIT. Characters are read by an inprecise
29        function now, which returns with an unknown value if the character code is
30        above a certain treshold (e.g: 256). The only limitation is that the value
31        must be bigger than the treshold as well. This function is useful, when
32        the characters above the treshold are handled in the same way.
34    7.  The macros whose names start with RAWUCHAR are placeholders for a future
35        mode in which only the bottom 21 bits of 32-bit data items are used. To
36        make this more memorable for those maintaining the code, the names have
37        been changed to start with UCHAR21, and an extensive comment has been added
38        to their definition.
40    8.  Add missing (new) files sljitNativeTILEGX.c and sljitNativeTILEGX-encoder.c
41        to the export list in Makefile.am (they were accidentally omitted from the
42        8.34 tarball).
44    9.  The informational output from pcretest used the phrase "starting byte set"
45        which is inappropriate for the 16-bit and 32-bit libraries. As the output
46        for "first char" and "need char" really means "non-UTF-char", I've changed
47        "byte" to "char", and slightly reworded the output. The documentation about
48        these values has also been (I hope) clarified.
50    10. Another JIT related optimization: use table jumps for selecting the correct
51        backtracking path, when more than four alternatives are present inside a
52        bracket.
54    11. Empty match is not possible, when the minimum length is greater than zero,
55        and there is no \K in the pattern. JIT should avoid empty match checks in
56        such cases.
58    12. In a caseless character class with UCP support, when a character with more
59        than one alternative case was not the first character of a range, not all
60        the alternative cases were added to the class. For example, s and \x{17f}
61        are both alternative cases for S: the class [RST] was handled correctly,
62        but [R-T] was not.
64    13. The configure.ac file always checked for pthread support when JIT was
65        enabled. This is not used in Windows, so I have put this test inside a
66        check for the presence of windows.h (which was already tested for).
68    14. Improve pattern prefix search by a simplified Boyer-Moore algorithm in JIT.
69        The algorithm provides a way to skip certain starting offsets, and usually
70        faster than linear prefix searches.
73    Version 8.34 15-December-2013
74    -----------------------------
76    1.  Add pcre[16|32]_jit_free_unused_memory to forcibly free unused JIT
77        executable memory. Patch inspired by Carsten Klein.
79    2.  ./configure --enable-coverage defined SUPPORT_GCOV in config.h, although
80        this macro is never tested and has no effect, because the work to support
81        coverage involves only compiling and linking options and special targets in
82        the Makefile. The comment in config.h implied that defining the macro would
83        enable coverage support, which is totally false. There was also support for
84        setting this macro in the CMake files (my fault, I just copied it from
85        configure). SUPPORT_GCOV has now been removed.
87    3.  Make a small performance improvement in strlen16() and strlen32() in
88        pcretest.
90    4.  Change 36 for 8.33 left some unreachable statements in pcre_exec.c,
91        detected by the Solaris compiler (gcc doesn't seem to be able to diagnose
92        these cases). There was also one in pcretest.c.
94    5.  Cleaned up a "may be uninitialized" compiler warning in pcre_exec.c.
96    6.  In UTF mode, the code for checking whether a group could match an empty
97        string (which is used for indefinitely repeated groups to allow for
98        breaking an infinite loop) was broken when the group contained a repeated
99        negated single-character class with a character that occupied more than one
100        data item and had a minimum repetition of zero (for example, [^\x{100}]* in
101        UTF-8 mode). The effect was undefined: the group might or might not be
102        deemed as matching an empty string, or the program might have crashed.
104    7.  The code for checking whether a group could match an empty string was not
105        recognizing that \h, \H, \v, \V, and \R must match a character.
107    8.  Implemented PCRE_INFO_MATCH_EMPTY, which yields 1 if the pattern can match
108        an empty string. If it can, pcretest shows this in its information output.
110    9.  Fixed two related bugs that applied to Unicode extended grapheme clusters
111        that were repeated with a maximizing qualifier (e.g. \X* or \X{2,5}) when
112        matched by pcre_exec() without using JIT:
114        (a) If the rest of the pattern did not match after a maximal run of
115            grapheme clusters, the code for backing up to try with fewer of them
116            did not always back up over a full grapheme when characters that do not
117            have the modifier quality were involved, e.g. Hangul syllables.
119        (b) If the match point in a subject started with modifier character, and
120            there was no match, the code could incorrectly back up beyond the match
121            point, and potentially beyond the first character in the subject,
122            leading to a segfault or an incorrect match result.
124    10. A conditional group with an assertion condition could lead to PCRE
125        recording an incorrect first data item for a match if no other first data
126        item was recorded. For example, the pattern (?(?=ab)ab) recorded "a" as a
127        first data item, and therefore matched "ca" after "c" instead of at the
128        start.
130    11. Change 40 for 8.33 (allowing pcregrep to find empty strings) showed up a
131        bug that caused the command "echo a | ./pcregrep -M '|a'" to loop.
133    12. The source of pcregrep now includes z/OS-specific code so that it can be
134        compiled for z/OS as part of the special z/OS distribution.
136    13. Added the -T and -TM options to pcretest.
138    14. The code in pcre_compile.c for creating the table of named capturing groups
139        has been refactored. Instead of creating the table dynamically during the
140        actual compiling pass, the information is remembered during the pre-compile
141        pass (on the stack unless there are more than 20 named groups, in which
142        case malloc() is used) and the whole table is created before the actual
143        compile happens. This has simplified the code (it is now nearly 150 lines
144        shorter) and prepared the way for better handling of references to groups
145        with duplicate names.
147    15. A back reference to a named subpattern when there is more than one of the
148        same name now checks them in the order in which they appear in the pattern.
149        The first one that is set is used for the reference. Previously only the
150        first one was inspected. This change makes PCRE more compatible with Perl.
152    16. Unicode character properties were updated from Unicode 6.3.0.
154    17. The compile-time code for auto-possessification has been refactored, based
155        on a patch by Zoltan Herczeg. It now happens after instead of during
156        compilation. The code is cleaner, and more cases are handled. The option
157        PCRE_NO_AUTO_POSSESS is added for testing purposes, and the -O and /O
158        options in pcretest are provided to set it. It can also be set by
159        (*NO_AUTO_POSSESS) at the start of a pattern.
161    18. The character VT has been added to the default ("C" locale) set of
162        characters that match \s and are generally treated as white space,
163        following this same change in Perl 5.18. There is now no difference between
164        "Perl space" and "POSIX space". Whether VT is treated as white space in
165        other locales depends on the locale.
167    19. The code for checking named groups as conditions, either for being set or
168        for being recursed, has been refactored (this is related to 14 and 15
169        above). Processing unduplicated named groups should now be as fast at
170        numerical groups, and processing duplicated groups should be faster than
171        before.
173    20. Two patches to the CMake build system, by Alexander Barkov:
175          (1) Replace the "source" command by "." in CMakeLists.txt because
176              "source" is a bash-ism.
178          (2) Add missing HAVE_STDINT_H and HAVE_INTTYPES_H to config-cmake.h.in;
179              without these the CMake build does not work on Solaris.
181    21. Perl has changed its handling of \8 and \9. If there is no previously
182        encountered capturing group of those numbers, they are treated as the
183        literal characters 8 and 9 instead of a binary zero followed by the
184        literals. PCRE now does the same.
186    22. Following Perl, added \o{} to specify codepoints in octal, making it
187        possible to specify values greater than 0777 and also making them
188        unambiguous.
190    23. Perl now gives an error for missing closing braces after \x{... instead of
191        treating the string as literal. PCRE now does the same.
193    24. RunTest used to grumble if an inappropriate test was selected explicitly,
194        but just skip it when running all tests. This make it awkward to run ranges
195        of tests when one of them was inappropriate. Now it just skips any
196        inappropriate tests, as it always did when running all tests.
198    25. If PCRE_AUTO_CALLOUT and PCRE_UCP were set for a pattern that contained
199        character types such as \d or \w, too many callouts were inserted, and the
200        data that they returned was rubbish.
202    26. In UCP mode, \s was not matching two of the characters that Perl matches,
203        namely NEL (U+0085) and MONGOLIAN VOWEL SEPARATOR (U+180E), though they
204        were matched by \h. The code has now been refactored so that the lists of
205        the horizontal and vertical whitespace characters used for \h and \v (which
206        are defined only in one place) are now also used for \s.
208    27. Add JIT support for the 64 bit TileGX architecture.
209        Patch by Jiong Wang (Tilera Corporation).
211    28. Possessive quantifiers for classes (both explicit and automatically
212        generated) now use special opcodes instead of wrapping in ONCE brackets.
214    29. Whereas an item such as A{4}+ ignored the possessivenes of the quantifier
215        (because it's meaningless), this was not happening when PCRE_CASELESS was
216        set. Not wrong, but inefficient.
218    30. Updated perltest.pl to add /u (force Unicode mode) when /W (use Unicode
219        properties for \w, \d, etc) is present in a test regex. Otherwise if the
220        test contains no characters greater than 255, Perl doesn't realise it
221        should be using Unicode semantics.
223    31. Upgraded the handling of the POSIX classes [:graph:], [:print:], and
224        [:punct:] when PCRE_UCP is set so as to include the same characters as Perl
225        does in Unicode mode.
227    32. Added the "forbid" facility to pcretest so that putting tests into the
228        wrong test files can sometimes be quickly detected.
230    33. There is now a limit (default 250) on the depth of nesting of parentheses.
231        This limit is imposed to control the amount of system stack used at compile
232        time. It can be changed at build time by --with-parens-nest-limit=xxx or
233        the equivalent in CMake.
235    34. Character classes such as [A-\d] or [a-[:digit:]] now cause compile-time
236        errors. Perl warns for these when in warning mode, but PCRE has no facility
237        for giving warnings.
239    35. Change 34 for 8.13 allowed quantifiers on assertions, because Perl does.
240        However, this was not working for (?!) because it is optimized to (*FAIL),
241        for which PCRE does not allow quantifiers. The optimization is now disabled
242        when a quantifier follows (?!). I can't see any use for this, but it makes
243        things uniform.
245    36. Perl no longer allows group names to start with digits, so I have made this
246        change also in PCRE. It simplifies the code a bit.
248    37. In extended mode, Perl ignores spaces before a + that indicates a
249        possessive quantifier. PCRE allowed a space before the quantifier, but not
250        before the possessive +. It now does.
252    38. The use of \K (reset reported match start) within a repeated possessive
253        group such as (a\Kb)*+ was not working.
255    40. Document that the same character tables must be used at compile time and
256        run time, and that the facility to pass tables to pcre_exec() and
257        pcre_dfa_exec() is for use only with saved/restored patterns.
259    41. Applied Jeff Trawick's patch CMakeLists.txt, which "provides two new
260        features for Builds with MSVC:
262        1. Support pcre.rc and/or pcreposix.rc (as is already done for MinGW
263           builds). The .rc files can be used to set FileDescription and many other
264           attributes.
266        2. Add an option (-DINSTALL_MSVC_PDB) to enable installation of .pdb files.
267           This allows higher-level build scripts which want .pdb files to avoid
268           hard-coding the exact files needed."
270    42. Added support for [[:<:]] and [[:>:]] as used in the BSD POSIX library to
271        mean "start of word" and "end of word", respectively, as a transition aid.
273    43. A minimizing repeat of a class containing codepoints greater than 255 in
274        non-UTF 16-bit or 32-bit modes caused an internal error when PCRE was
275        compiled to use the heap for recursion.
277    44. Got rid of some compiler warnings for unused variables when UTF but not UCP
278        is configured.
281    Version 8.33 28-May-2013
282    ------------------------
284    1.  Added 'U' to some constants that are compared to unsigned integers, to
285        avoid compiler signed/unsigned warnings. Added (int) casts to unsigned
286        variables that are added to signed variables, to ensure the result is
287        signed and can be negated.
289    2.  Applied patch by Daniel Richard G for quashing MSVC warnings to the
290        CMake config files.
292    3.  Revise the creation of config.h.generic so that all boolean macros are
293        #undefined, whereas non-boolean macros are #ifndef/#endif-ed. This makes
294        overriding via -D on the command line possible.
296    4.  Changing the definition of the variable "op" in pcre_exec.c from pcre_uchar
297        to unsigned int is reported to make a quite noticeable speed difference in
298        a specific Windows environment. Testing on Linux did also appear to show
299        some benefit (and it is clearly not harmful). Also fixed the definition of
300        Xop which should be unsigned.
302    5.  Related to (4), changing the definition of the intermediate variable cc
303        in repeated character loops from pcre_uchar to pcre_uint32 also gave speed
304        improvements.
306    6.  Fix forward search in JIT when link size is 3 or greater. Also removed some
307        unnecessary spaces.
309    7.  Adjust autogen.sh and configure.ac to lose warnings given by automake 1.12
310        and later.
312    8.  Fix two buffer over read issues in 16 and 32 bit modes. Affects JIT only.
314    9.  Optimizing fast_forward_start_bits in JIT.
316    10. Adding support for callouts in JIT, and fixing some issues revealed
317        during this work. Namely:
319        (a) Unoptimized capturing brackets incorrectly reset on backtrack.
321        (b) Minimum length was not checked before the matching is started.
323    11. The value of capture_last that is passed to callouts was incorrect in some
324        cases when there was a capture on one path that was subsequently abandoned
325        after a backtrack. Also, the capture_last value is now reset after a
326        recursion, since all captures are also reset in this case.
328    12. The interpreter no longer returns the "too many substrings" error in the
329        case when an overflowing capture is in a branch that is subsequently
330        abandoned after a backtrack.
332    13. In the pathological case when an offset vector of size 2 is used, pcretest
333        now prints out the matched string after a yield of 0 or 1.
335    14. Inlining subpatterns in recursions, when certain conditions are fulfilled.
336        Only supported by the JIT compiler at the moment.
338    15. JIT compiler now supports 32 bit Macs thanks to Lawrence Velazquez.
340    16. Partial matches now set offsets[2] to the "bumpalong" value, that is, the
341        offset of the starting point of the matching process, provided the offsets
342        vector is large enough.
344    17. The \A escape now records a lookbehind value of 1, though its execution
345        does not actually inspect the previous character. This is to ensure that,
346        in partial multi-segment matching, at least one character from the old
347        segment is retained when a new segment is processed. Otherwise, if there
348        are no lookbehinds in the pattern, \A might match incorrectly at the start
349        of a new segment.
351    18. Added some #ifdef __VMS code into pcretest.c to help VMS implementations.
353    19. Redefined some pcre_uchar variables in pcre_exec.c as pcre_uint32; this
354        gives some modest performance improvement in 8-bit mode.
356    20. Added the PCRE-specific property \p{Xuc} for matching characters that can
357        be expressed in certain programming languages using Universal Character
358        Names.
360    21. Unicode validation has been updated in the light of Unicode Corrigendum #9,
361        which points out that "non characters" are not "characters that may not
362        appear in Unicode strings" but rather "characters that are reserved for
363        internal use and have only local meaning".
365    22. When a pattern was compiled with automatic callouts (PCRE_AUTO_CALLOUT) and
366        there was a conditional group that depended on an assertion, if the
367        assertion was false, the callout that immediately followed the alternation
368        in the condition was skipped when pcre_exec() was used for matching.
370    23. Allow an explicit callout to be inserted before an assertion that is the
371        condition for a conditional group, for compatibility with automatic
372        callouts, which always insert a callout at this point.
374    24. In 8.31, (*COMMIT) was confined to within a recursive subpattern. Perl also
375        confines (*SKIP) and (*PRUNE) in the same way, and this has now been done.
377    25. (*PRUNE) is now supported by the JIT compiler.
379    26. Fix infinite loop when /(?<=(*SKIP)ac)a/ is matched against aa.
381    27. Fix the case where there are two or more SKIPs with arguments that may be
382        ignored.
384    28. (*SKIP) is now supported by the JIT compiler.
386    29. (*THEN) is now supported by the JIT compiler.
388    30. Update RunTest with additional test selector options.
390    31. The way PCRE handles backtracking verbs has been changed in two ways.
392        (1) Previously, in something like (*COMMIT)(*SKIP), COMMIT would override
393        SKIP. Now, PCRE acts on whichever backtracking verb is reached first by
394        backtracking. In some cases this makes it more Perl-compatible, but Perl's
395        rather obscure rules do not always do the same thing.
397        (2) Previously, backtracking verbs were confined within assertions. This is
398        no longer the case for positive assertions, except for (*ACCEPT). Again,
399        this sometimes improves Perl compatibility, and sometimes does not.
401    32. A number of tests that were in test 2 because Perl did things differently
402        have been moved to test 1, because either Perl or PCRE has changed, and
403        these tests are now compatible.
405    32. Backtracking control verbs are now handled in the same way in JIT and
406        interpreter.
408    33. An opening parenthesis in a MARK/PRUNE/SKIP/THEN name in a pattern that
409        contained a forward subroutine reference caused a compile error.
411    34. Auto-detect and optimize limited repetitions in JIT.
413    35. Implement PCRE_NEVER_UTF to lock out the use of UTF, in particular,
414        blocking (*UTF) etc.
416    36. In the interpreter, maximizing pattern repetitions for characters and
417        character types now use tail recursion, which reduces stack usage.
419    37. The value of the max lookbehind was not correctly preserved if a compiled
420        and saved regex was reloaded on a host of different endianness.
422    38. Implemented (*LIMIT_MATCH) and (*LIMIT_RECURSION). As part of the extension
423        of the compiled pattern block, expand the flags field from 16 to 32 bits
424        because it was almost full.
426    39. Try madvise first before posix_madvise.
428    40. Change 7 for PCRE 7.9 made it impossible for pcregrep to find empty lines
429        with a pattern such as ^$. It has taken 4 years for anybody to notice! The
430        original change locked out all matches of empty strings. This has been
431        changed so that one match of an empty string per line is recognized.
432        Subsequent searches on the same line (for colouring or for --only-matching,
433        for example) do not recognize empty strings.
435    41. Applied a user patch to fix a number of spelling mistakes in comments.
437    42. Data lines longer than 65536 caused pcretest to crash.
439    43. Clarified the data type for length and startoffset arguments for pcre_exec
440        and pcre_dfa_exec in the function-specific man pages, where they were
441        explicitly stated to be in bytes, never having been updated. I also added
442        some clarification to the pcreapi man page.
444    44. A call to pcre_dfa_exec() with an output vector size less than 2 caused
445        a segmentation fault.
448    Version 8.32 30-November-2012
449    -----------------------------
451    1.  Improved JIT compiler optimizations for first character search and single
452        character iterators.
454    2.  Supporting IBM XL C compilers for PPC architectures in the JIT compiler.
455        Patch by Daniel Richard G.
457    3.  Single character iterator optimizations in the JIT compiler.
459    4.  Improved JIT compiler optimizations for character ranges.
461    5.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.
462        Reported by Giuseppe D'Angelo.
464    6.  The PCRE_STARTLINE bit, indicating that a match can occur only at the start
465        of a line, was being set incorrectly in cases where .* appeared inside
466        atomic brackets at the start of a pattern, or where there was a subsequent
467        *PRUNE or *SKIP.
469    7.  Improved instruction cache flush for POWER/PowerPC.
470        Patch by Daniel Richard G.
472    8.  Fixed a number of issues in pcregrep, making it more compatible with GNU
473        grep:
475        (a) There is now no limit to the number of patterns to be matched.
477        (b) An error is given if a pattern is too long.
479        (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir
480            are now supported.
482        (d) --exclude-from and --include-from (multiple use) have been added.
484        (e) Exclusions and inclusions now apply to all files and directories, not
485            just to those obtained from scanning a directory recursively.
487        (f) Multiple uses of -f and --file-list are now supported.
489        (g) In a Windows environment, the default for -d has been changed from
490            "read" (the GNU grep default) to "skip", because otherwise the presence
491            of a directory in the file list provokes an error.
493        (h) The documentation has been revised and clarified in places.
495    9.  Improve the matching speed of capturing brackets.
497    10. Changed the meaning of \X so that it now matches a Unicode extended
498        grapheme cluster.
500    11. Patch by Daniel Richard G to the autoconf files to add a macro for sorting
501        out POSIX threads when JIT support is configured.
503    12. Added support for PCRE_STUDY_EXTRA_NEEDED.
505    13. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg
506        structure could go wrong in environments where size_t is not the same size
507        as int.
509    14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be
510        set.
512    15. The EBCDIC support had decayed; later updates to the code had included
513        explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a
514        general tidy up of EBCDIC-related issues, and the documentation was also
515        not quite right. There is now a test that can be run on ASCII systems to
516        check some of the EBCDIC-related things (but is it not a full test).
518    16. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting
519        in a small tidy to the code.
521    17. Fix JIT tests when UTF is disabled and both 8 and 16 bit mode are enabled.
523    18. If the --only-matching (-o) option in pcregrep is specified multiple
524        times, each one causes appropriate output. For example, -o1 -o2 outputs the
525        substrings matched by the 1st and 2nd capturing parentheses. A separating
526        string can be specified by --om-separator (default empty).
528    19. Improving the first n character searches.
530    20. Turn case lists for horizontal and vertical white space into macros so that
531        they are defined only once.
533    21. This set of changes together give more compatible Unicode case-folding
534        behaviour for characters that have more than one other case when UCP
535        support is available.
537        (a) The Unicode property table now has offsets into a new table of sets of
538            three or more characters that are case-equivalent. The MultiStage2.py
539            script that generates these tables (the pcre_ucd.c file) now scans
540            CaseFolding.txt instead of UnicodeData.txt for character case
541            information.
543        (b) The code for adding characters or ranges of characters to a character
544            class has been abstracted into a generalized function that also handles
545            case-independence. In UTF-mode with UCP support, this uses the new data
546            to handle characters with more than one other case.
548        (c) A bug that is fixed as a result of (b) is that codepoints less than 256
549            whose other case is greater than 256 are now correctly matched
550            caselessly. Previously, the high codepoint matched the low one, but not
551            vice versa.
553        (d) The processing of \h, \H, \v, and \ in character classes now makes use
554            of the new class addition function, using character lists defined as
555            macros alongside the case definitions of 20 above.
557        (e) Caseless back references now work with characters that have more than
558            one other case.
560        (f) General caseless matching of characters with more than one other case
561            is supported.
563    22. Unicode character properties were updated from Unicode 6.2.0
565    23. Improved CMake support under Windows. Patch by Daniel Richard G.
567    24. Add support for 32-bit character strings, and UTF-32
569    25. Major JIT compiler update (code refactoring and bugfixing).
570        Experimental Sparc 32 support is added.
572    26. Applied a modified version of Daniel Richard G's patch to create
573        pcre.h.generic and config.h.generic by "make" instead of in the
574        PrepareRelease script.
576    27. Added a definition for CHAR_NULL (helpful for the z/OS port), and use it in
577        pcre_compile.c when checking for a zero character.
579    28. Introducing a native interface for JIT. Through this interface, the compiled
580        machine code can be directly executed. The purpose of this interface is to
581        provide fast pattern matching, so several sanity checks are not performed.
582        However, feature tests are still performed. The new interface provides
583        1.4x speedup compared to the old one.
585    29. If pcre_exec() or pcre_dfa_exec() was called with a negative value for
586        the subject string length, the error given was PCRE_ERROR_BADOFFSET, which
587        was confusing. There is now a new error PCRE_ERROR_BADLENGTH for this case.
589    30. In 8-bit UTF-8 mode, pcretest failed to give an error for data codepoints
590        greater than 0x7fffffff (which cannot be represented in UTF-8, even under
591        the "old" RFC 2279). Instead, it ended up passing a negative length to
592        pcre_exec().
594    31. Add support for GCC's visibility feature to hide internal functions.
596    32. Running "pcretest -C pcre8" or "pcretest -C pcre16" gave a spurious error
597        "unknown -C option" after outputting 0 or 1.
599    33. There is now support for generating a code coverage report for the test
600        suite in environments where gcc is the compiler and lcov is installed. This
601        is mainly for the benefit of the developers.
603    34. If PCRE is built with --enable-valgrind, certain memory regions are marked
604        unaddressable using valgrind annotations, allowing valgrind to detect
605        invalid memory accesses. This is mainly for the benefit of the developers.
607    25. (*UTF) can now be used to start a pattern in any of the three libraries.
609    26. Give configure error if --enable-cpp but no C++ compiler found.
612    Version 8.31 06-July-2012
613  -------------------------  -------------------------
615  1.  Fixing a wrong JIT test case and some compiler warnings.  1.  Fixing a wrong JIT test case and some compiler warnings.
# Line 133  Version 8.31 02-June-2012 Line 741  Version 8.31 02-June-2012
741  37. Optimizing single character iterators in JIT.  37. Optimizing single character iterators in JIT.
743  38. Wide characters specified with \uxxxx in JavaScript mode are now subject to  38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
744      the same checks as \x{...} characters in non-JavaScript mode. Specifically,      the same checks as \x{...} characters in non-JavaScript mode. Specifically,
745      codepoints that are too big for the mode are faulted, and in a UTF mode,      codepoints that are too big for the mode are faulted, and in a UTF mode,
746      disallowed codepoints are also faulted.      disallowed codepoints are also faulted.
748  39. If PCRE was compiled with UTF support, in three places in the DFA  39. If PCRE was compiled with UTF support, in three places in the DFA
749      matcher there was code that should only have been obeyed in UTF mode, but      matcher there was code that should only have been obeyed in UTF mode, but
750      was being obeyed unconditionally. In 8-bit mode this could cause incorrect      was being obeyed unconditionally. In 8-bit mode this could cause incorrect
# Line 145  Version 8.31 02-June-2012 Line 753  Version 8.31 02-June-2012
753      both cases the values are those that cannot be the first data item in a UTF      both cases the values are those that cannot be the first data item in a UTF
754      character. The three items that might have provoked this were recursions,      character. The three items that might have provoked this were recursions,
755      possessively repeated groups, and atomic groups.      possessively repeated groups, and atomic groups.
757  40. Ensure that libpcre is explicitly listed in the link commands for pcretest  40. Ensure that libpcre is explicitly listed in the link commands for pcretest
758      and pcregrep, because some OS require shared objects to be explicitly      and pcregrep, because some OS require shared objects to be explicitly
759      passed to ld, causing the link step to fail if they are not.      passed to ld, causing the link step to fail if they are not.
761    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
762        mode, patterns that started with \h* or \R* might be incorrectly matched.
765  Version 8.30 04-February-2012  Version 8.30 04-February-2012
766  -----------------------------  -----------------------------
# Line 1341  Version 7.9 11-Apr-09 Line 1952  Version 7.9 11-Apr-09
1952  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
1953      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
1954      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
1955      seems to be how GNU grep behaves.      seems to be how GNU grep behaves. [But see later change 40 for release
1956        8.33.]
1958  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
1959      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 1584  Version 7.7 07-May-08 Line 2196  Version 7.7 07-May-08
2196      containing () gave an internal compiling error instead of "reference to      containing () gave an internal compiling error instead of "reference to
2197      non-existent subpattern". Fortunately, when the pattern did exist, the      non-existent subpattern". Fortunately, when the pattern did exist, the
2198      compiled code was correct. (When scanning forwards to check for the      compiled code was correct. (When scanning forwards to check for the
2199      existencd of the subpattern, it was treating the data ']' as terminating      existence of the subpattern, it was treating the data ']' as terminating
2200      the class, so got the count wrong. When actually compiling, the reference      the class, so got the count wrong. When actually compiling, the reference
2201      was subsequently set up correctly.)      was subsequently set up correctly.)

Removed from v.980  
changed lines
  Added in v.1441

  ViewVC Help
Powered by ViewVC 1.1.5