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

Diff of /code/trunk/ChangeLog

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

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

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

  ViewVC Help
Powered by ViewVC 1.1.5