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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.1389  
changed lines
  Added in v.1431

  ViewVC Help
Powered by ViewVC 1.1.5