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

Diff of /code/trunk/ChangeLog

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

revision 836 by ph10, Wed Dec 28 17:16:11 2011 UTC revision 1451 by zherczeg, Tue Jan 21 01:49:14 2014 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.30  Version 8.35-RC1 xx-xxxx-201x
5  ------------  -----------------------------
6    
7  1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this  1.  A new flag is set, when property checks are present in an XCLASS.
8      name is defined in ctype.h.      When this flag is not set, PCRE can perform certain optimizations
9        such as studying these XCLASS-es.
10    
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.
14    
15    3.  Got rid of some compiler warnings for potentially uninitialized variables
16        that show up only when compiled with -O2.
17    
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.
23    
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.
27    
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.
33    
34  2.  Fixed a bug in the code for calculating the fixed length of lookbehind  7.  The macros whose names start with RAWUCHAR are placeholders for a future
35      assertions.      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.
39    
40  3.  Removed the function pcre_info(), which has been obsolete and deprecated  8.  Add missing (new) files sljitNativeTILEGX.c and sljitNativeTILEGX-encoder.c
41      since it was replaced by pcre_fullinfo() in February 2000.      to the export list in Makefile.am (they were accidentally omitted from the
42        8.34 tarball).
43    
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.
49    
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.
53    
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.
57    
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.
63    
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).
67    
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.
71    
72    15. Change 13 for 8.20 updated RunTest to check for the 'fr' locale as well
73        as for 'fr_FR' and 'french'. For some reason, however, it then used the
74        Windows-specific input and output files, which have 'french' screwed in.
75        So this could never have worked. One of the problems with locales is that
76        they aren't always the same. I have now updated RunTest so that it checks
77        the output of the locale test (test 3) against three different output
78        files, and it allows the test to pass if any one of them matches. With luck
79        this should make the test pass on some versions of Solaris where it was
80        failing. Because of the uncertainty, the script did not used to stop if
81        test 3 failed; it now does. If further versions of a French locale ever
82        come to light, they can now easily be added.
83    
84    16. If --with-pcregrep-bufsize was given a non-integer value such as "50K",
85        there was a message during ./configure, but it did not stop. This now
86        provokes an error. The invalid example in README has been corrected.
87        If a value less than the minimum is given, the minimum value has always
88        been used, but now a warning is given.
89    
90    17. If --enable-bsr-anycrlf was set, the special 16/32-bit test failed. This
91        was a bug in the test system, which is now fixed. Also, the list of various
92        configurations that are tested for each release did not have one with both
93        16/32 bits and --enable-bar-anycrlf. It now does.
94    
95    18. pcretest was missing "-C bsr" for displaying the \R default setting.
96    
97    19. Little endian PowerPC systems are supported now by the JIT compiler.
98    
99    
100    Version 8.34 15-December-2013
101    -----------------------------
102    
103    1.  Add pcre[16|32]_jit_free_unused_memory to forcibly free unused JIT
104        executable memory. Patch inspired by Carsten Klein.
105    
106    2.  ./configure --enable-coverage defined SUPPORT_GCOV in config.h, although
107        this macro is never tested and has no effect, because the work to support
108        coverage involves only compiling and linking options and special targets in
109        the Makefile. The comment in config.h implied that defining the macro would
110        enable coverage support, which is totally false. There was also support for
111        setting this macro in the CMake files (my fault, I just copied it from
112        configure). SUPPORT_GCOV has now been removed.
113    
114    3.  Make a small performance improvement in strlen16() and strlen32() in
115        pcretest.
116    
117    4.  Change 36 for 8.33 left some unreachable statements in pcre_exec.c,
118        detected by the Solaris compiler (gcc doesn't seem to be able to diagnose
119        these cases). There was also one in pcretest.c.
120    
121    5.  Cleaned up a "may be uninitialized" compiler warning in pcre_exec.c.
122    
123    6.  In UTF mode, the code for checking whether a group could match an empty
124        string (which is used for indefinitely repeated groups to allow for
125        breaking an infinite loop) was broken when the group contained a repeated
126        negated single-character class with a character that occupied more than one
127        data item and had a minimum repetition of zero (for example, [^\x{100}]* in
128        UTF-8 mode). The effect was undefined: the group might or might not be
129        deemed as matching an empty string, or the program might have crashed.
130    
131    7.  The code for checking whether a group could match an empty string was not
132        recognizing that \h, \H, \v, \V, and \R must match a character.
133    
134    8.  Implemented PCRE_INFO_MATCH_EMPTY, which yields 1 if the pattern can match
135        an empty string. If it can, pcretest shows this in its information output.
136    
137    9.  Fixed two related bugs that applied to Unicode extended grapheme clusters
138        that were repeated with a maximizing qualifier (e.g. \X* or \X{2,5}) when
139        matched by pcre_exec() without using JIT:
140    
141        (a) If the rest of the pattern did not match after a maximal run of
142            grapheme clusters, the code for backing up to try with fewer of them
143            did not always back up over a full grapheme when characters that do not
144            have the modifier quality were involved, e.g. Hangul syllables.
145    
146        (b) If the match point in a subject started with modifier character, and
147            there was no match, the code could incorrectly back up beyond the match
148            point, and potentially beyond the first character in the subject,
149            leading to a segfault or an incorrect match result.
150    
151    10. A conditional group with an assertion condition could lead to PCRE
152        recording an incorrect first data item for a match if no other first data
153        item was recorded. For example, the pattern (?(?=ab)ab) recorded "a" as a
154        first data item, and therefore matched "ca" after "c" instead of at the
155        start.
156    
157    11. Change 40 for 8.33 (allowing pcregrep to find empty strings) showed up a
158        bug that caused the command "echo a | ./pcregrep -M '|a'" to loop.
159    
160    12. The source of pcregrep now includes z/OS-specific code so that it can be
161        compiled for z/OS as part of the special z/OS distribution.
162    
163    13. Added the -T and -TM options to pcretest.
164    
165    14. The code in pcre_compile.c for creating the table of named capturing groups
166        has been refactored. Instead of creating the table dynamically during the
167        actual compiling pass, the information is remembered during the pre-compile
168        pass (on the stack unless there are more than 20 named groups, in which
169        case malloc() is used) and the whole table is created before the actual
170        compile happens. This has simplified the code (it is now nearly 150 lines
171        shorter) and prepared the way for better handling of references to groups
172        with duplicate names.
173    
174    15. A back reference to a named subpattern when there is more than one of the
175        same name now checks them in the order in which they appear in the pattern.
176        The first one that is set is used for the reference. Previously only the
177        first one was inspected. This change makes PCRE more compatible with Perl.
178    
179    16. Unicode character properties were updated from Unicode 6.3.0.
180    
181    17. The compile-time code for auto-possessification has been refactored, based
182        on a patch by Zoltan Herczeg. It now happens after instead of during
183        compilation. The code is cleaner, and more cases are handled. The option
184        PCRE_NO_AUTO_POSSESS is added for testing purposes, and the -O and /O
185        options in pcretest are provided to set it. It can also be set by
186        (*NO_AUTO_POSSESS) at the start of a pattern.
187    
188    18. The character VT has been added to the default ("C" locale) set of
189        characters that match \s and are generally treated as white space,
190        following this same change in Perl 5.18. There is now no difference between
191        "Perl space" and "POSIX space". Whether VT is treated as white space in
192        other locales depends on the locale.
193    
194    19. The code for checking named groups as conditions, either for being set or
195        for being recursed, has been refactored (this is related to 14 and 15
196        above). Processing unduplicated named groups should now be as fast at
197        numerical groups, and processing duplicated groups should be faster than
198        before.
199    
200    20. Two patches to the CMake build system, by Alexander Barkov:
201    
202          (1) Replace the "source" command by "." in CMakeLists.txt because
203              "source" is a bash-ism.
204    
205          (2) Add missing HAVE_STDINT_H and HAVE_INTTYPES_H to config-cmake.h.in;
206              without these the CMake build does not work on Solaris.
207    
208    21. Perl has changed its handling of \8 and \9. If there is no previously
209        encountered capturing group of those numbers, they are treated as the
210        literal characters 8 and 9 instead of a binary zero followed by the
211        literals. PCRE now does the same.
212    
213    22. Following Perl, added \o{} to specify codepoints in octal, making it
214        possible to specify values greater than 0777 and also making them
215        unambiguous.
216    
217    23. Perl now gives an error for missing closing braces after \x{... instead of
218        treating the string as literal. PCRE now does the same.
219    
220    24. RunTest used to grumble if an inappropriate test was selected explicitly,
221        but just skip it when running all tests. This make it awkward to run ranges
222        of tests when one of them was inappropriate. Now it just skips any
223        inappropriate tests, as it always did when running all tests.
224    
225    25. If PCRE_AUTO_CALLOUT and PCRE_UCP were set for a pattern that contained
226        character types such as \d or \w, too many callouts were inserted, and the
227        data that they returned was rubbish.
228    
229    26. In UCP mode, \s was not matching two of the characters that Perl matches,
230        namely NEL (U+0085) and MONGOLIAN VOWEL SEPARATOR (U+180E), though they
231        were matched by \h. The code has now been refactored so that the lists of
232        the horizontal and vertical whitespace characters used for \h and \v (which
233        are defined only in one place) are now also used for \s.
234    
235    27. Add JIT support for the 64 bit TileGX architecture.
236        Patch by Jiong Wang (Tilera Corporation).
237    
238    28. Possessive quantifiers for classes (both explicit and automatically
239        generated) now use special opcodes instead of wrapping in ONCE brackets.
240    
241    29. Whereas an item such as A{4}+ ignored the possessivenes of the quantifier
242        (because it's meaningless), this was not happening when PCRE_CASELESS was
243        set. Not wrong, but inefficient.
244    
245    30. Updated perltest.pl to add /u (force Unicode mode) when /W (use Unicode
246        properties for \w, \d, etc) is present in a test regex. Otherwise if the
247        test contains no characters greater than 255, Perl doesn't realise it
248        should be using Unicode semantics.
249    
250    31. Upgraded the handling of the POSIX classes [:graph:], [:print:], and
251        [:punct:] when PCRE_UCP is set so as to include the same characters as Perl
252        does in Unicode mode.
253    
254    32. Added the "forbid" facility to pcretest so that putting tests into the
255        wrong test files can sometimes be quickly detected.
256    
257    33. There is now a limit (default 250) on the depth of nesting of parentheses.
258        This limit is imposed to control the amount of system stack used at compile
259        time. It can be changed at build time by --with-parens-nest-limit=xxx or
260        the equivalent in CMake.
261    
262    34. Character classes such as [A-\d] or [a-[:digit:]] now cause compile-time
263        errors. Perl warns for these when in warning mode, but PCRE has no facility
264        for giving warnings.
265    
266    35. Change 34 for 8.13 allowed quantifiers on assertions, because Perl does.
267        However, this was not working for (?!) because it is optimized to (*FAIL),
268        for which PCRE does not allow quantifiers. The optimization is now disabled
269        when a quantifier follows (?!). I can't see any use for this, but it makes
270        things uniform.
271    
272    36. Perl no longer allows group names to start with digits, so I have made this
273        change also in PCRE. It simplifies the code a bit.
274    
275    37. In extended mode, Perl ignores spaces before a + that indicates a
276        possessive quantifier. PCRE allowed a space before the quantifier, but not
277        before the possessive +. It now does.
278    
279    38. The use of \K (reset reported match start) within a repeated possessive
280        group such as (a\Kb)*+ was not working.
281    
282    40. Document that the same character tables must be used at compile time and
283        run time, and that the facility to pass tables to pcre_exec() and
284        pcre_dfa_exec() is for use only with saved/restored patterns.
285    
286    41. Applied Jeff Trawick's patch CMakeLists.txt, which "provides two new
287        features for Builds with MSVC:
288    
289        1. Support pcre.rc and/or pcreposix.rc (as is already done for MinGW
290           builds). The .rc files can be used to set FileDescription and many other
291           attributes.
292    
293        2. Add an option (-DINSTALL_MSVC_PDB) to enable installation of .pdb files.
294           This allows higher-level build scripts which want .pdb files to avoid
295           hard-coding the exact files needed."
296    
297    42. Added support for [[:<:]] and [[:>:]] as used in the BSD POSIX library to
298        mean "start of word" and "end of word", respectively, as a transition aid.
299    
300    43. A minimizing repeat of a class containing codepoints greater than 255 in
301        non-UTF 16-bit or 32-bit modes caused an internal error when PCRE was
302        compiled to use the heap for recursion.
303    
304    44. Got rid of some compiler warnings for unused variables when UTF but not UCP
305        is configured.
306    
307    
308    Version 8.33 28-May-2013
309    ------------------------
310    
311    1.  Added 'U' to some constants that are compared to unsigned integers, to
312        avoid compiler signed/unsigned warnings. Added (int) casts to unsigned
313        variables that are added to signed variables, to ensure the result is
314        signed and can be negated.
315    
316    2.  Applied patch by Daniel Richard G for quashing MSVC warnings to the
317        CMake config files.
318    
319    3.  Revise the creation of config.h.generic so that all boolean macros are
320        #undefined, whereas non-boolean macros are #ifndef/#endif-ed. This makes
321        overriding via -D on the command line possible.
322    
323    4.  Changing the definition of the variable "op" in pcre_exec.c from pcre_uchar
324        to unsigned int is reported to make a quite noticeable speed difference in
325        a specific Windows environment. Testing on Linux did also appear to show
326        some benefit (and it is clearly not harmful). Also fixed the definition of
327        Xop which should be unsigned.
328    
329    5.  Related to (4), changing the definition of the intermediate variable cc
330        in repeated character loops from pcre_uchar to pcre_uint32 also gave speed
331        improvements.
332    
333    6.  Fix forward search in JIT when link size is 3 or greater. Also removed some
334        unnecessary spaces.
335    
336    7.  Adjust autogen.sh and configure.ac to lose warnings given by automake 1.12
337        and later.
338    
339    8.  Fix two buffer over read issues in 16 and 32 bit modes. Affects JIT only.
340    
341    9.  Optimizing fast_forward_start_bits in JIT.
342    
343    10. Adding support for callouts in JIT, and fixing some issues revealed
344        during this work. Namely:
345    
346        (a) Unoptimized capturing brackets incorrectly reset on backtrack.
347    
348        (b) Minimum length was not checked before the matching is started.
349    
350    11. The value of capture_last that is passed to callouts was incorrect in some
351        cases when there was a capture on one path that was subsequently abandoned
352        after a backtrack. Also, the capture_last value is now reset after a
353        recursion, since all captures are also reset in this case.
354    
355    12. The interpreter no longer returns the "too many substrings" error in the
356        case when an overflowing capture is in a branch that is subsequently
357        abandoned after a backtrack.
358    
359    13. In the pathological case when an offset vector of size 2 is used, pcretest
360        now prints out the matched string after a yield of 0 or 1.
361    
362    14. Inlining subpatterns in recursions, when certain conditions are fulfilled.
363        Only supported by the JIT compiler at the moment.
364    
365    15. JIT compiler now supports 32 bit Macs thanks to Lawrence Velazquez.
366    
367    16. Partial matches now set offsets[2] to the "bumpalong" value, that is, the
368        offset of the starting point of the matching process, provided the offsets
369        vector is large enough.
370    
371    17. The \A escape now records a lookbehind value of 1, though its execution
372        does not actually inspect the previous character. This is to ensure that,
373        in partial multi-segment matching, at least one character from the old
374        segment is retained when a new segment is processed. Otherwise, if there
375        are no lookbehinds in the pattern, \A might match incorrectly at the start
376        of a new segment.
377    
378    18. Added some #ifdef __VMS code into pcretest.c to help VMS implementations.
379    
380    19. Redefined some pcre_uchar variables in pcre_exec.c as pcre_uint32; this
381        gives some modest performance improvement in 8-bit mode.
382    
383    20. Added the PCRE-specific property \p{Xuc} for matching characters that can
384        be expressed in certain programming languages using Universal Character
385        Names.
386    
387    21. Unicode validation has been updated in the light of Unicode Corrigendum #9,
388        which points out that "non characters" are not "characters that may not
389        appear in Unicode strings" but rather "characters that are reserved for
390        internal use and have only local meaning".
391    
392    22. When a pattern was compiled with automatic callouts (PCRE_AUTO_CALLOUT) and
393        there was a conditional group that depended on an assertion, if the
394        assertion was false, the callout that immediately followed the alternation
395        in the condition was skipped when pcre_exec() was used for matching.
396    
397    23. Allow an explicit callout to be inserted before an assertion that is the
398        condition for a conditional group, for compatibility with automatic
399        callouts, which always insert a callout at this point.
400    
401    24. In 8.31, (*COMMIT) was confined to within a recursive subpattern. Perl also
402        confines (*SKIP) and (*PRUNE) in the same way, and this has now been done.
403    
404    25. (*PRUNE) is now supported by the JIT compiler.
405    
406    26. Fix infinite loop when /(?<=(*SKIP)ac)a/ is matched against aa.
407    
408    27. Fix the case where there are two or more SKIPs with arguments that may be
409        ignored.
410    
411    28. (*SKIP) is now supported by the JIT compiler.
412    
413    29. (*THEN) is now supported by the JIT compiler.
414    
415    30. Update RunTest with additional test selector options.
416    
417    31. The way PCRE handles backtracking verbs has been changed in two ways.
418    
419        (1) Previously, in something like (*COMMIT)(*SKIP), COMMIT would override
420        SKIP. Now, PCRE acts on whichever backtracking verb is reached first by
421        backtracking. In some cases this makes it more Perl-compatible, but Perl's
422        rather obscure rules do not always do the same thing.
423    
424        (2) Previously, backtracking verbs were confined within assertions. This is
425        no longer the case for positive assertions, except for (*ACCEPT). Again,
426        this sometimes improves Perl compatibility, and sometimes does not.
427    
428    32. A number of tests that were in test 2 because Perl did things differently
429        have been moved to test 1, because either Perl or PCRE has changed, and
430        these tests are now compatible.
431    
432    32. Backtracking control verbs are now handled in the same way in JIT and
433        interpreter.
434    
435    33. An opening parenthesis in a MARK/PRUNE/SKIP/THEN name in a pattern that
436        contained a forward subroutine reference caused a compile error.
437    
438    34. Auto-detect and optimize limited repetitions in JIT.
439    
440    35. Implement PCRE_NEVER_UTF to lock out the use of UTF, in particular,
441        blocking (*UTF) etc.
442    
443    36. In the interpreter, maximizing pattern repetitions for characters and
444        character types now use tail recursion, which reduces stack usage.
445    
446    37. The value of the max lookbehind was not correctly preserved if a compiled
447        and saved regex was reloaded on a host of different endianness.
448    
449    38. Implemented (*LIMIT_MATCH) and (*LIMIT_RECURSION). As part of the extension
450        of the compiled pattern block, expand the flags field from 16 to 32 bits
451        because it was almost full.
452    
453    39. Try madvise first before posix_madvise.
454    
455    40. Change 7 for PCRE 7.9 made it impossible for pcregrep to find empty lines
456        with a pattern such as ^$. It has taken 4 years for anybody to notice! The
457        original change locked out all matches of empty strings. This has been
458        changed so that one match of an empty string per line is recognized.
459        Subsequent searches on the same line (for colouring or for --only-matching,
460        for example) do not recognize empty strings.
461    
462    41. Applied a user patch to fix a number of spelling mistakes in comments.
463    
464    42. Data lines longer than 65536 caused pcretest to crash.
465    
466    43. Clarified the data type for length and startoffset arguments for pcre_exec
467        and pcre_dfa_exec in the function-specific man pages, where they were
468        explicitly stated to be in bytes, never having been updated. I also added
469        some clarification to the pcreapi man page.
470    
471    44. A call to pcre_dfa_exec() with an output vector size less than 2 caused
472        a segmentation fault.
473    
474    
475    Version 8.32 30-November-2012
476    -----------------------------
477    
478    1.  Improved JIT compiler optimizations for first character search and single
479        character iterators.
480    
481    2.  Supporting IBM XL C compilers for PPC architectures in the JIT compiler.
482        Patch by Daniel Richard G.
483    
484    3.  Single character iterator optimizations in the JIT compiler.
485    
486    4.  Improved JIT compiler optimizations for character ranges.
487    
488    5.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.
489        Reported by Giuseppe D'Angelo.
490    
491    6.  The PCRE_STARTLINE bit, indicating that a match can occur only at the start
492        of a line, was being set incorrectly in cases where .* appeared inside
493        atomic brackets at the start of a pattern, or where there was a subsequent
494        *PRUNE or *SKIP.
495    
496    7.  Improved instruction cache flush for POWER/PowerPC.
497        Patch by Daniel Richard G.
498    
499    8.  Fixed a number of issues in pcregrep, making it more compatible with GNU
500        grep:
501    
502        (a) There is now no limit to the number of patterns to be matched.
503    
504        (b) An error is given if a pattern is too long.
505    
506        (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir
507            are now supported.
508    
509        (d) --exclude-from and --include-from (multiple use) have been added.
510    
511        (e) Exclusions and inclusions now apply to all files and directories, not
512            just to those obtained from scanning a directory recursively.
513    
514        (f) Multiple uses of -f and --file-list are now supported.
515    
516        (g) In a Windows environment, the default for -d has been changed from
517            "read" (the GNU grep default) to "skip", because otherwise the presence
518            of a directory in the file list provokes an error.
519    
520        (h) The documentation has been revised and clarified in places.
521    
522    9.  Improve the matching speed of capturing brackets.
523    
524    10. Changed the meaning of \X so that it now matches a Unicode extended
525        grapheme cluster.
526    
527    11. Patch by Daniel Richard G to the autoconf files to add a macro for sorting
528        out POSIX threads when JIT support is configured.
529    
530    12. Added support for PCRE_STUDY_EXTRA_NEEDED.
531    
532    13. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg
533        structure could go wrong in environments where size_t is not the same size
534        as int.
535    
536    14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be
537        set.
538    
539    15. The EBCDIC support had decayed; later updates to the code had included
540        explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a
541        general tidy up of EBCDIC-related issues, and the documentation was also
542        not quite right. There is now a test that can be run on ASCII systems to
543        check some of the EBCDIC-related things (but is it not a full test).
544    
545    16. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting
546        in a small tidy to the code.
547    
548    17. Fix JIT tests when UTF is disabled and both 8 and 16 bit mode are enabled.
549    
550    18. If the --only-matching (-o) option in pcregrep is specified multiple
551        times, each one causes appropriate output. For example, -o1 -o2 outputs the
552        substrings matched by the 1st and 2nd capturing parentheses. A separating
553        string can be specified by --om-separator (default empty).
554    
555    19. Improving the first n character searches.
556    
557    20. Turn case lists for horizontal and vertical white space into macros so that
558        they are defined only once.
559    
560    21. This set of changes together give more compatible Unicode case-folding
561        behaviour for characters that have more than one other case when UCP
562        support is available.
563    
564        (a) The Unicode property table now has offsets into a new table of sets of
565            three or more characters that are case-equivalent. The MultiStage2.py
566            script that generates these tables (the pcre_ucd.c file) now scans
567            CaseFolding.txt instead of UnicodeData.txt for character case
568            information.
569    
570        (b) The code for adding characters or ranges of characters to a character
571            class has been abstracted into a generalized function that also handles
572            case-independence. In UTF-mode with UCP support, this uses the new data
573            to handle characters with more than one other case.
574    
575        (c) A bug that is fixed as a result of (b) is that codepoints less than 256
576            whose other case is greater than 256 are now correctly matched
577            caselessly. Previously, the high codepoint matched the low one, but not
578            vice versa.
579    
580        (d) The processing of \h, \H, \v, and \ in character classes now makes use
581            of the new class addition function, using character lists defined as
582            macros alongside the case definitions of 20 above.
583    
584        (e) Caseless back references now work with characters that have more than
585            one other case.
586    
587        (f) General caseless matching of characters with more than one other case
588            is supported.
589    
590    22. Unicode character properties were updated from Unicode 6.2.0
591    
592    23. Improved CMake support under Windows. Patch by Daniel Richard G.
593    
594    24. Add support for 32-bit character strings, and UTF-32
595    
596    25. Major JIT compiler update (code refactoring and bugfixing).
597        Experimental Sparc 32 support is added.
598    
599    26. Applied a modified version of Daniel Richard G's patch to create
600        pcre.h.generic and config.h.generic by "make" instead of in the
601        PrepareRelease script.
602    
603    27. Added a definition for CHAR_NULL (helpful for the z/OS port), and use it in
604        pcre_compile.c when checking for a zero character.
605    
606    28. Introducing a native interface for JIT. Through this interface, the compiled
607        machine code can be directly executed. The purpose of this interface is to
608        provide fast pattern matching, so several sanity checks are not performed.
609        However, feature tests are still performed. The new interface provides
610        1.4x speedup compared to the old one.
611    
612    29. If pcre_exec() or pcre_dfa_exec() was called with a negative value for
613        the subject string length, the error given was PCRE_ERROR_BADOFFSET, which
614        was confusing. There is now a new error PCRE_ERROR_BADLENGTH for this case.
615    
616    30. In 8-bit UTF-8 mode, pcretest failed to give an error for data codepoints
617        greater than 0x7fffffff (which cannot be represented in UTF-8, even under
618        the "old" RFC 2279). Instead, it ended up passing a negative length to
619        pcre_exec().
620    
621    31. Add support for GCC's visibility feature to hide internal functions.
622    
623    32. Running "pcretest -C pcre8" or "pcretest -C pcre16" gave a spurious error
624        "unknown -C option" after outputting 0 or 1.
625    
626    33. There is now support for generating a code coverage report for the test
627        suite in environments where gcc is the compiler and lcov is installed. This
628        is mainly for the benefit of the developers.
629    
630    34. If PCRE is built with --enable-valgrind, certain memory regions are marked
631        unaddressable using valgrind annotations, allowing valgrind to detect
632        invalid memory accesses. This is mainly for the benefit of the developers.
633    
634    25. (*UTF) can now be used to start a pattern in any of the three libraries.
635    
636    26. Give configure error if --enable-cpp but no C++ compiler found.
637    
638    
639    Version 8.31 06-July-2012
640    -------------------------
641    
642    1.  Fixing a wrong JIT test case and some compiler warnings.
643    
644    2.  Removed a bashism from the RunTest script.
645    
646    3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied
647        to unsigned type, result still unsigned" that was given by an MS compiler
648        on encountering the code "-sizeof(xxx)".
649    
650    4.  Partial matching support is added to the JIT compiler.
651    
652    5.  Fixed several bugs concerned with partial matching of items that consist
653        of more than one character:
654    
655        (a) /^(..)\1/ did not partially match "aba" because checking references was
656            done on an "all or nothing" basis. This also applied to repeated
657            references.
658    
659        (b) \R did not give a hard partial match if \r was found at the end of the
660            subject.
661    
662        (c) \X did not give a hard partial match after matching one or more
663            characters at the end of the subject.
664    
665        (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize
666            a partial match for the string "\r".
667    
668        (e) When newline was set to CRLF, the metacharacter "." did not recognize
669            a partial match for a CR character at the end of the subject string.
670    
671    6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when
672        running pcretest, the text "(JIT)" added to the output whenever JIT is
673        actually used to run the match.
674    
675    7.  Individual JIT compile options can be set in pcretest by following -s+[+]
676        or /S+[+] with a digit between 1 and 7.
677    
678    8.  OP_NOT now supports any UTF character not just single-byte ones.
679    
680    9.  (*MARK) control verb is now supported by the JIT compiler.
681    
682    10. The command "./RunTest list" lists the available tests without actually
683        running any of them. (Because I keep forgetting what they all are.)
684    
685    11. Add PCRE_INFO_MAXLOOKBEHIND.
686    
687    12. Applied a (slightly modified) user-supplied patch that improves performance
688        when the heap is used for recursion (compiled with --disable-stack-for-
689        recursion). Instead of malloc and free for each heap frame each time a
690        logical recursion happens, frames are retained on a chain and re-used where
691        possible. This sometimes gives as much as 30% improvement.
692    
693    13. As documented, (*COMMIT) is now confined to within a recursive subpattern
694        call.
695    
696    14. As documented, (*COMMIT) is now confined to within a positive assertion.
697    
698    15. It is now possible to link pcretest with libedit as an alternative to
699        libreadline.
700    
701    16. (*COMMIT) control verb is now supported by the JIT compiler.
702    
703    17. The Unicode data tables have been updated to Unicode 6.1.0.
704    
705    18. Added --file-list option to pcregrep.
706    
707    19. Added binary file support to pcregrep, including the -a, --binary-files,
708        -I, and --text options.
709    
710    20. The madvise function is renamed for posix_madvise for QNX compatibility
711        reasons. Fixed by Giuseppe D'Angelo.
712    
713    21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
714    
715    22. Changed the option for creating symbolic links for 16-bit man pages from
716        -s to -sf so that re-installing does not cause issues.
717    
718    23. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it.
719    
720    24. Fixed a very old bug in pcretest that caused errors with restarted DFA
721        matches in certain environments (the workspace was not being correctly
722        retained). Also added to pcre_dfa_exec() a simple plausibility check on
723        some of the workspace data at the beginning of a restart.
724    
725    25. \s*\R was auto-possessifying the \s* when it should not, whereas \S*\R
726        was not doing so when it should - probably a typo introduced by SVN 528
727        (change 8.10/14).
728    
729    26. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the
730        \w+ when the character tables indicated that \x{c4} was a word character.
731        There were several related cases, all because the tests for doing a table
732        lookup were testing for characters less than 127 instead of 255.
733    
734    27. If a pattern contains capturing parentheses that are not used in a match,
735        their slots in the ovector are set to -1. For those that are higher than
736        any matched groups, this happens at the end of processing. In the case when
737        there were back references that the ovector was too small to contain
738        (causing temporary malloc'd memory to be used during matching), and the
739        highest capturing number was not used, memory off the end of the ovector
740        was incorrectly being set to -1. (It was using the size of the temporary
741        memory instead of the true size.)
742    
743    28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
744        ovector size, it uses memory at the end of the block that it has got.
745    
746    29. Check for an overlong MARK name and give an error at compile time. The
747        limit is 255 for the 8-bit library and 65535 for the 16-bit library.
748    
749    30. JIT compiler update.
750    
751    31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
752        Rill for the patch.
753    
754    32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
755    
756    33. Variable renamings in the PCRE-JIT compiler. No functionality change.
757    
758    34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
759        SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
760        was enabled.
761    
762    35. Improve JIT code generation for greedy plus quantifier.
763    
764    36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
765        1 to "aa" instead of to an empty string. The bug affected repeated groups
766        that could potentially match an empty string.
767    
768    37. Optimizing single character iterators in JIT.
769    
770    38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
771        the same checks as \x{...} characters in non-JavaScript mode. Specifically,
772        codepoints that are too big for the mode are faulted, and in a UTF mode,
773        disallowed codepoints are also faulted.
774    
775    39. If PCRE was compiled with UTF support, in three places in the DFA
776        matcher there was code that should only have been obeyed in UTF mode, but
777        was being obeyed unconditionally. In 8-bit mode this could cause incorrect
778        processing when bytes with values greater than 127 were present. In 16-bit
779        mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
780        both cases the values are those that cannot be the first data item in a UTF
781        character. The three items that might have provoked this were recursions,
782        possessively repeated groups, and atomic groups.
783    
784    40. Ensure that libpcre is explicitly listed in the link commands for pcretest
785        and pcregrep, because some OS require shared objects to be explicitly
786        passed to ld, causing the link step to fail if they are not.
787    
788    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
789        mode, patterns that started with \h* or \R* might be incorrectly matched.
790    
791    
792    Version 8.30 04-February-2012
793    -----------------------------
794    
795    1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
796        name is defined in ctype.h.
797    
798    2.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
799        only in quite long subpatterns.
800    
801    3.  Removed the function pcre_info(), which has been obsolete and deprecated
802        since it was replaced by pcre_fullinfo() in February 2000.
803    
804  4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not  4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
805      match a (*MARK), and the match failed at the start of the subject, a      match a (*MARK), and the match failed at the start of the subject, a
806      reference to memory before the start of the subject could occur. This bug      reference to memory before the start of the subject could occur. This bug
807      was introduced by fix 17 of release 8.21.      was introduced by fix 17 of release 8.21.
808    
809  5.  A reference to an unset group with zero minimum repetition was giving  5.  A reference to an unset group with zero minimum repetition was giving
810      totally wrong answers (in non-JavaScript-compatibility mode). For example,      totally wrong answers (in non-JavaScript-compatibility mode). For example,
811      /(another)?(\1?)test/ matched against "hello world test". This bug was      /(another)?(\1?)test/ matched against "hello world test". This bug was
812      introduced in release 8.13.      introduced in release 8.13.
813    
814  6.  Add support for 16-bit character strings (a large amount of work involving  6.  Add support for 16-bit character strings (a large amount of work involving
815      many changes and refactorings).      many changes and refactorings).
816    
817    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
818        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
819        from a file.
820    
821    8.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
822        rounding is not applied in this particular case).
823    
824    9.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
825        if they appear, or are escaped, in patterns.
826    
827    10. Get rid of a number of -Wunused-but-set-variable warnings.
828    
829    11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
830        "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
831        Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
832        also returns the mark "x". This bug applied to capturing parentheses,
833        non-capturing parentheses, and atomic parentheses. It also applied to some
834        assertions.
835    
836    12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
837        information out of configure.ac instead of relying on pcre.h.generic, which
838        is not stored in the repository.
839    
840    13. Applied Dmitry V. Levin's patch for a more portable method for linking with
841        -lreadline.
842    
843    14. ZH added PCRE_CONFIG_JITTARGET; added its output to pcretest -C.
844    
845    15. Applied Graycode's patch to put the top-level frame on the stack rather
846        than the heap when not using the stack for recursion. This gives a
847        performance improvement in many cases when recursion is not deep.
848    
849    16. Experimental code added to "pcretest -C" to output the stack frame size.
850    
851    
852  Version 8.21 12-Dec-2011  Version 8.21 12-Dec-2011
853  ------------------------  ------------------------
# Line 1157  Version 7.9 11-Apr-09 Line 1979  Version 7.9 11-Apr-09
1979  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
1980      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
1981      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
1982      seems to be how GNU grep behaves.      seems to be how GNU grep behaves. [But see later change 40 for release
1983        8.33.]
1984    
1985  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
1986      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 1400  Version 7.7 07-May-08 Line 2223  Version 7.7 07-May-08
2223      containing () gave an internal compiling error instead of "reference to      containing () gave an internal compiling error instead of "reference to
2224      non-existent subpattern". Fortunately, when the pattern did exist, the      non-existent subpattern". Fortunately, when the pattern did exist, the
2225      compiled code was correct. (When scanning forwards to check for the      compiled code was correct. (When scanning forwards to check for the
2226      existencd of the subpattern, it was treating the data ']' as terminating      existence of the subpattern, it was treating the data ']' as terminating
2227      the class, so got the count wrong. When actually compiling, the reference      the class, so got the count wrong. When actually compiling, the reference
2228      was subsequently set up correctly.)      was subsequently set up correctly.)
2229    

Legend:
Removed from v.836  
changed lines
  Added in v.1451

  ViewVC Help
Powered by ViewVC 1.1.5