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

Diff of /code/trunk/ChangeLog

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

revision 1322 by zherczeg, Wed May 1 19:42:31 2013 UTC revision 1418 by ph10, Fri Dec 27 12:23:25 2013 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.33 28-April-2013  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    
25    Version 8.34 15-December-2013
26    -----------------------------
27    
28    1.  Add pcre[16|32]_jit_free_unused_memory to forcibly free unused JIT
29        executable memory. Patch inspired by Carsten Klein.
30    
31    2.  ./configure --enable-coverage defined SUPPORT_GCOV in config.h, although
32        this macro is never tested and has no effect, because the work to support
33        coverage involves only compiling and linking options and special targets in
34        the Makefile. The comment in config.h implied that defining the macro would
35        enable coverage support, which is totally false. There was also support for
36        setting this macro in the CMake files (my fault, I just copied it from
37        configure). SUPPORT_GCOV has now been removed.
38    
39    3.  Make a small performance improvement in strlen16() and strlen32() in
40        pcretest.
41    
42    4.  Change 36 for 8.33 left some unreachable statements in pcre_exec.c,
43        detected by the Solaris compiler (gcc doesn't seem to be able to diagnose
44        these cases). There was also one in pcretest.c.
45    
46    5.  Cleaned up a "may be uninitialized" compiler warning in pcre_exec.c.
47    
48    6.  In UTF mode, the code for checking whether a group could match an empty
49        string (which is used for indefinitely repeated groups to allow for
50        breaking an infinite loop) was broken when the group contained a repeated
51        negated single-character class with a character that occupied more than one
52        data item and had a minimum repetition of zero (for example, [^\x{100}]* in
53        UTF-8 mode). The effect was undefined: the group might or might not be
54        deemed as matching an empty string, or the program might have crashed.
55    
56    7.  The code for checking whether a group could match an empty string was not
57        recognizing that \h, \H, \v, \V, and \R must match a character.
58    
59    8.  Implemented PCRE_INFO_MATCH_EMPTY, which yields 1 if the pattern can match
60        an empty string. If it can, pcretest shows this in its information output.
61    
62    9.  Fixed two related bugs that applied to Unicode extended grapheme clusters
63        that were repeated with a maximizing qualifier (e.g. \X* or \X{2,5}) when
64        matched by pcre_exec() without using JIT:
65    
66        (a) If the rest of the pattern did not match after a maximal run of
67            grapheme clusters, the code for backing up to try with fewer of them
68            did not always back up over a full grapheme when characters that do not
69            have the modifier quality were involved, e.g. Hangul syllables.
70    
71        (b) If the match point in a subject started with modifier character, and
72            there was no match, the code could incorrectly back up beyond the match
73            point, and potentially beyond the first character in the subject,
74            leading to a segfault or an incorrect match result.
75    
76    10. A conditional group with an assertion condition could lead to PCRE
77        recording an incorrect first data item for a match if no other first data
78        item was recorded. For example, the pattern (?(?=ab)ab) recorded "a" as a
79        first data item, and therefore matched "ca" after "c" instead of at the
80        start.
81    
82    11. Change 40 for 8.33 (allowing pcregrep to find empty strings) showed up a
83        bug that caused the command "echo a | ./pcregrep -M '|a'" to loop.
84    
85    12. The source of pcregrep now includes z/OS-specific code so that it can be
86        compiled for z/OS as part of the special z/OS distribution.
87    
88    13. Added the -T and -TM options to pcretest.
89    
90    14. The code in pcre_compile.c for creating the table of named capturing groups
91        has been refactored. Instead of creating the table dynamically during the
92        actual compiling pass, the information is remembered during the pre-compile
93        pass (on the stack unless there are more than 20 named groups, in which
94        case malloc() is used) and the whole table is created before the actual
95        compile happens. This has simplified the code (it is now nearly 150 lines
96        shorter) and prepared the way for better handling of references to groups
97        with duplicate names.
98    
99    15. A back reference to a named subpattern when there is more than one of the
100        same name now checks them in the order in which they appear in the pattern.
101        The first one that is set is used for the reference. Previously only the
102        first one was inspected. This change makes PCRE more compatible with Perl.
103    
104    16. Unicode character properties were updated from Unicode 6.3.0.
105    
106    17. The compile-time code for auto-possessification has been refactored, based
107        on a patch by Zoltan Herczeg. It now happens after instead of during
108        compilation. The code is cleaner, and more cases are handled. The option
109        PCRE_NO_AUTO_POSSESS is added for testing purposes, and the -O and /O
110        options in pcretest are provided to set it. It can also be set by
111        (*NO_AUTO_POSSESS) at the start of a pattern.
112    
113    18. The character VT has been added to the default ("C" locale) set of
114        characters that match \s and are generally treated as white space,
115        following this same change in Perl 5.18. There is now no difference between
116        "Perl space" and "POSIX space". Whether VT is treated as white space in
117        other locales depends on the locale.
118    
119    19. The code for checking named groups as conditions, either for being set or
120        for being recursed, has been refactored (this is related to 14 and 15
121        above). Processing unduplicated named groups should now be as fast at
122        numerical groups, and processing duplicated groups should be faster than
123        before.
124    
125    20. Two patches to the CMake build system, by Alexander Barkov:
126    
127          (1) Replace the "source" command by "." in CMakeLists.txt because
128              "source" is a bash-ism.
129    
130          (2) Add missing HAVE_STDINT_H and HAVE_INTTYPES_H to config-cmake.h.in;
131              without these the CMake build does not work on Solaris.
132    
133    21. Perl has changed its handling of \8 and \9. If there is no previously
134        encountered capturing group of those numbers, they are treated as the
135        literal characters 8 and 9 instead of a binary zero followed by the
136        literals. PCRE now does the same.
137    
138    22. Following Perl, added \o{} to specify codepoints in octal, making it
139        possible to specify values greater than 0777 and also making them
140        unambiguous.
141    
142    23. Perl now gives an error for missing closing braces after \x{... instead of
143        treating the string as literal. PCRE now does the same.
144    
145    24. RunTest used to grumble if an inappropriate test was selected explicitly,
146        but just skip it when running all tests. This make it awkward to run ranges
147        of tests when one of them was inappropriate. Now it just skips any
148        inappropriate tests, as it always did when running all tests.
149    
150    25. If PCRE_AUTO_CALLOUT and PCRE_UCP were set for a pattern that contained
151        character types such as \d or \w, too many callouts were inserted, and the
152        data that they returned was rubbish.
153    
154    26. In UCP mode, \s was not matching two of the characters that Perl matches,
155        namely NEL (U+0085) and MONGOLIAN VOWEL SEPARATOR (U+180E), though they
156        were matched by \h. The code has now been refactored so that the lists of
157        the horizontal and vertical whitespace characters used for \h and \v (which
158        are defined only in one place) are now also used for \s.
159    
160    27. Add JIT support for the 64 bit TileGX architecture.
161        Patch by Jiong Wang (Tilera Corporation).
162    
163    28. Possessive quantifiers for classes (both explicit and automatically
164        generated) now use special opcodes instead of wrapping in ONCE brackets.
165    
166    29. Whereas an item such as A{4}+ ignored the possessivenes of the quantifier
167        (because it's meaningless), this was not happening when PCRE_CASELESS was
168        set. Not wrong, but inefficient.
169    
170    30. Updated perltest.pl to add /u (force Unicode mode) when /W (use Unicode
171        properties for \w, \d, etc) is present in a test regex. Otherwise if the
172        test contains no characters greater than 255, Perl doesn't realise it
173        should be using Unicode semantics.
174    
175    31. Upgraded the handling of the POSIX classes [:graph:], [:print:], and
176        [:punct:] when PCRE_UCP is set so as to include the same characters as Perl
177        does in Unicode mode.
178    
179    32. Added the "forbid" facility to pcretest so that putting tests into the
180        wrong test files can sometimes be quickly detected.
181    
182    33. There is now a limit (default 250) on the depth of nesting of parentheses.
183        This limit is imposed to control the amount of system stack used at compile
184        time. It can be changed at build time by --with-parens-nest-limit=xxx or
185        the equivalent in CMake.
186    
187    34. Character classes such as [A-\d] or [a-[:digit:]] now cause compile-time
188        errors. Perl warns for these when in warning mode, but PCRE has no facility
189        for giving warnings.
190    
191    35. Change 34 for 8.13 allowed quantifiers on assertions, because Perl does.
192        However, this was not working for (?!) because it is optimized to (*FAIL),
193        for which PCRE does not allow quantifiers. The optimization is now disabled
194        when a quantifier follows (?!). I can't see any use for this, but it makes
195        things uniform.
196    
197    36. Perl no longer allows group names to start with digits, so I have made this
198        change also in PCRE. It simplifies the code a bit.
199    
200    37. In extended mode, Perl ignores spaces before a + that indicates a
201        possessive quantifier. PCRE allowed a space before the quantifier, but not
202        before the possessive +. It now does.
203    
204    38. The use of \K (reset reported match start) within a repeated possessive
205        group such as (a\Kb)*+ was not working.
206    
207    40. Document that the same character tables must be used at compile time and
208        run time, and that the facility to pass tables to pcre_exec() and
209        pcre_dfa_exec() is for use only with saved/restored patterns.
210    
211    41. Applied Jeff Trawick's patch CMakeLists.txt, which "provides two new
212        features for Builds with MSVC:
213    
214        1. Support pcre.rc and/or pcreposix.rc (as is already done for MinGW
215           builds). The .rc files can be used to set FileDescription and many other
216           attributes.
217    
218        2. Add an option (-DINSTALL_MSVC_PDB) to enable installation of .pdb files.
219           This allows higher-level build scripts which want .pdb files to avoid
220           hard-coding the exact files needed."
221    
222    42. Added support for [[:<:]] and [[:>:]] as used in the BSD POSIX library to
223        mean "start of word" and "end of word", respectively, as a transition aid.
224    
225    43. A minimizing repeat of a class containing codepoints greater than 255 in
226        non-UTF 16-bit or 32-bit modes caused an internal error when PCRE was
227        compiled to use the heap for recursion.
228    
229    44. Got rid of some compiler warnings for unused variables when UTF but not UCP
230        is configured.
231    
232    
233    Version 8.33 28-May-2013
234    ------------------------
235    
236  1.  Added 'U' to some constants that are compared to unsigned integers, to  1.  Added 'U' to some constants that are compared to unsigned integers, to
237      avoid compiler signed/unsigned warnings. Added (int) casts to unsigned      avoid compiler signed/unsigned warnings. Added (int) casts to unsigned
# Line 36  Version 8.33 28-April-2013 Line 265  Version 8.33 28-April-2013
265    
266  9.  Optimizing fast_forward_start_bits in JIT.  9.  Optimizing fast_forward_start_bits in JIT.
267    
268  10. Adding experimental support for callouts in JIT, and fixing some  10. Adding support for callouts in JIT, and fixing some issues revealed
269      issues revealed during this work. Namely:      during this work. Namely:
270    
271      (a) Unoptimized capturing brackets incorrectly reset on backtrack.      (a) Unoptimized capturing brackets incorrectly reset on backtrack.
272    
# Line 125  Version 8.33 28-April-2013 Line 354  Version 8.33 28-April-2013
354      have been moved to test 1, because either Perl or PCRE has changed, and      have been moved to test 1, because either Perl or PCRE has changed, and
355      these tests are now compatible.      these tests are now compatible.
356    
357  32. Control verbs are handled in the same way in JIT and interpreter.  32. Backtracking control verbs are now handled in the same way in JIT and
358        interpreter.
359    
360  33. An opening parenthesis in a MARK/PRUNE/SKIP/THEN name in a pattern that  33. An opening parenthesis in a MARK/PRUNE/SKIP/THEN name in a pattern that
361      contained a forward subroutine reference caused a compile error.      contained a forward subroutine reference caused a compile error.
# Line 147  Version 8.33 28-April-2013 Line 377  Version 8.33 28-April-2013
377    
378  39. Try madvise first before posix_madvise.  39. Try madvise first before posix_madvise.
379    
380    40. Change 7 for PCRE 7.9 made it impossible for pcregrep to find empty lines
381        with a pattern such as ^$. It has taken 4 years for anybody to notice! The
382        original change locked out all matches of empty strings. This has been
383        changed so that one match of an empty string per line is recognized.
384        Subsequent searches on the same line (for colouring or for --only-matching,
385        for example) do not recognize empty strings.
386    
387    41. Applied a user patch to fix a number of spelling mistakes in comments.
388    
389    42. Data lines longer than 65536 caused pcretest to crash.
390    
391    43. Clarified the data type for length and startoffset arguments for pcre_exec
392        and pcre_dfa_exec in the function-specific man pages, where they were
393        explicitly stated to be in bytes, never having been updated. I also added
394        some clarification to the pcreapi man page.
395    
396    44. A call to pcre_dfa_exec() with an output vector size less than 2 caused
397        a segmentation fault.
398    
399    
400  Version 8.32 30-November-2012  Version 8.32 30-November-2012
401  -----------------------------  -----------------------------
# Line 1655  Version 7.9 11-Apr-09 Line 1904  Version 7.9 11-Apr-09
1904  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
1905      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
1906      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
1907      seems to be how GNU grep behaves.      seems to be how GNU grep behaves. [But see later change 40 for release
1908        8.33.]
1909    
1910  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
1911      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 1898  Version 7.7 07-May-08 Line 2148  Version 7.7 07-May-08
2148      containing () gave an internal compiling error instead of "reference to      containing () gave an internal compiling error instead of "reference to
2149      non-existent subpattern". Fortunately, when the pattern did exist, the      non-existent subpattern". Fortunately, when the pattern did exist, the
2150      compiled code was correct. (When scanning forwards to check for the      compiled code was correct. (When scanning forwards to check for the
2151      existencd of the subpattern, it was treating the data ']' as terminating      existence of the subpattern, it was treating the data ']' as terminating
2152      the class, so got the count wrong. When actually compiling, the reference      the class, so got the count wrong. When actually compiling, the reference
2153      was subsequently set up correctly.)      was subsequently set up correctly.)
2154    

Legend:
Removed from v.1322  
changed lines
  Added in v.1418

  ViewVC Help
Powered by ViewVC 1.1.5