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

Diff of /code/trunk/ChangeLog

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

revision 1392 by ph10, Wed Nov 6 18:00:09 2013 UTC revision 1510 by ph10, Wed Nov 5 15:08:03 2014 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.34 xx-xxxx-201x  Version 8.37 xx-xxx-201x
5    ------------------------
6    
7    1.  When an (*ACCEPT) is triggered inside capturing parentheses, it arranges
8        for those parentheses to be closed with whatever has been captured so far.
9        However, it was failing to mark any other groups between the hightest
10        capture so far and the currrent group as "unset". Thus, the ovector for
11        those groups contained whatever was previously there. An example is the
12        pattern /(x)|((*ACCEPT))/ when matched against "abcd".
13    
14    
15    
16    Version 8.36 26-September-2014
17    ------------------------------
18    
19    1.  Got rid of some compiler warnings in the C++ modules that were shown up by
20        -Wmissing-field-initializers and -Wunused-parameter.
21    
22    2.  The tests for quantifiers being too big (greater than 65535) were being
23        applied after reading the number, and stupidly assuming that integer
24        overflow would give a negative number. The tests are now applied as the
25        numbers are read.
26    
27    3.  Tidy code in pcre_exec.c where two branches that used to be different are
28        now the same.
29    
30    4.  The JIT compiler did not generate match limit checks for certain
31        bracketed expressions with quantifiers. This may lead to exponential
32        backtracking, instead of returning with PCRE_ERROR_MATCHLIMIT. This
33        issue should be resolved now.
34    
35    5.  Fixed an issue, which occures when nested alternatives are optimized
36        with table jumps.
37    
38    6.  Inserted two casts and changed some ints to size_t in the light of some
39        reported 64-bit compiler warnings (Bugzilla 1477).
40    
41    7.  Fixed a bug concerned with zero-minimum possessive groups that could match
42        an empty string, which sometimes were behaving incorrectly in the
43        interpreter (though correctly in the JIT matcher). This pcretest input is
44        an example:
45    
46          '\A(?:[^"]++|"(?:[^"]*+|"")*+")++'
47          NON QUOTED "QUOT""ED" AFTER "NOT MATCHED
48    
49        the interpreter was reporting a match of 'NON QUOTED ' only, whereas the
50        JIT matcher and Perl both matched 'NON QUOTED "QUOT""ED" AFTER '. The test
51        for an empty string was breaking the inner loop and carrying on at a lower
52        level, when possessive repeated groups should always return to a higher
53        level as they have no backtrack points in them. The empty string test now
54        occurs at the outer level.
55    
56    8.  Fixed a bug that was incorrectly auto-possessifying \w+ in the pattern
57        ^\w+(?>\s*)(?<=\w) which caused it not to match "test test".
58    
59    9.  Give a compile-time error for \o{} (as Perl does) and for \x{} (which Perl
60        doesn't).
61    
62    10. Change 8.34/15 introduced a bug that caused the amount of memory needed
63        to hold a pattern to be incorrectly computed (too small) when there were
64        named back references to duplicated names. This could cause "internal
65        error: code overflow" or "double free or corruption" or other memory
66        handling errors.
67    
68    11. When named subpatterns had the same prefixes, back references could be
69        confused. For example, in this pattern:
70    
71          /(?P<Name>a)?(?P<Name2>b)?(?(<Name>)c|d)*l/
72    
73        the reference to 'Name' was incorrectly treated as a reference to a
74        duplicate name.
75    
76    12. A pattern such as /^s?c/mi8 where the optional character has more than
77        one "other case" was incorrectly compiled such that it would only try to
78        match starting at "c".
79    
80    13. When a pattern starting with \s was studied, VT was not included in the
81        list of possible starting characters; this should have been part of the
82        8.34/18 patch.
83    
84    14. If a character class started [\Qx]... where x is any character, the class
85        was incorrectly terminated at the ].
86    
87    15. If a pattern that started with a caseless match for a character with more
88        than one "other case" was studied, PCRE did not set up the starting code
89        unit bit map for the list of possible characters. Now it does. This is an
90        optimization improvement, not a bug fix.
91    
92    16. The Unicode data tables have been updated to Unicode 7.0.0.
93    
94    17. Fixed a number of memory leaks in pcregrep.
95    
96    18. Avoid a compiler warning (from some compilers) for a function call with
97        a cast that removes "const" from an lvalue by using an intermediate
98        variable (to which the compiler does not object).
99    
100    19. Incorrect code was compiled if a group that contained an internal recursive
101        back reference was optional (had quantifier with a minimum of zero). This
102        example compiled incorrect code: /(((a\2)|(a*)\g<-1>))*/ and other examples
103        caused segmentation faults because of stack overflows at compile time.
104    
105    20. A pattern such as /((?(R)a|(?1)))+/, which contains a recursion within a
106        group that is quantified with an indefinite repeat, caused a compile-time
107        loop which used up all the system stack and provoked a segmentation fault.
108        This was not the same bug as 19 above.
109    
110    21. Add PCRECPP_EXP_DECL declaration to operator<< in pcre_stringpiece.h.
111        Patch by Mike Frysinger.
112    
113    
114    Version 8.35 04-April-2014
115  --------------------------  --------------------------
116    
117    1.  A new flag is set, when property checks are present in an XCLASS.
118        When this flag is not set, PCRE can perform certain optimizations
119        such as studying these XCLASS-es.
120    
121    2.  The auto-possessification of character sets were improved: a normal
122        and an extended character set can be compared now. Furthermore
123        the JIT compiler optimizes more character set checks.
124    
125    3.  Got rid of some compiler warnings for potentially uninitialized variables
126        that show up only when compiled with -O2.
127    
128    4.  A pattern such as (?=ab\K) that uses \K in an assertion can set the start
129        of a match later then the end of the match. The pcretest program was not
130        handling the case sensibly - it was outputting from the start to the next
131        binary zero. It now reports this situation in a message, and outputs the
132        text from the end to the start.
133    
134    5.  Fast forward search is improved in JIT. Instead of the first three
135        characters, any three characters with fixed position can be searched.
136        Search order: first, last, middle.
137    
138    6.  Improve character range checks in JIT. Characters are read by an inprecise
139        function now, which returns with an unknown value if the character code is
140        above a certain threshold (e.g: 256). The only limitation is that the value
141        must be bigger than the threshold as well. This function is useful when
142        the characters above the threshold are handled in the same way.
143    
144    7.  The macros whose names start with RAWUCHAR are placeholders for a future
145        mode in which only the bottom 21 bits of 32-bit data items are used. To
146        make this more memorable for those maintaining the code, the names have
147        been changed to start with UCHAR21, and an extensive comment has been added
148        to their definition.
149    
150    8.  Add missing (new) files sljitNativeTILEGX.c and sljitNativeTILEGX-encoder.c
151        to the export list in Makefile.am (they were accidentally omitted from the
152        8.34 tarball).
153    
154    9.  The informational output from pcretest used the phrase "starting byte set"
155        which is inappropriate for the 16-bit and 32-bit libraries. As the output
156        for "first char" and "need char" really means "non-UTF-char", I've changed
157        "byte" to "char", and slightly reworded the output. The documentation about
158        these values has also been (I hope) clarified.
159    
160    10. Another JIT related optimization: use table jumps for selecting the correct
161        backtracking path, when more than four alternatives are present inside a
162        bracket.
163    
164    11. Empty match is not possible, when the minimum length is greater than zero,
165        and there is no \K in the pattern. JIT should avoid empty match checks in
166        such cases.
167    
168    12. In a caseless character class with UCP support, when a character with more
169        than one alternative case was not the first character of a range, not all
170        the alternative cases were added to the class. For example, s and \x{17f}
171        are both alternative cases for S: the class [RST] was handled correctly,
172        but [R-T] was not.
173    
174    13. The configure.ac file always checked for pthread support when JIT was
175        enabled. This is not used in Windows, so I have put this test inside a
176        check for the presence of windows.h (which was already tested for).
177    
178    14. Improve pattern prefix search by a simplified Boyer-Moore algorithm in JIT.
179        The algorithm provides a way to skip certain starting offsets, and usually
180        faster than linear prefix searches.
181    
182    15. Change 13 for 8.20 updated RunTest to check for the 'fr' locale as well
183        as for 'fr_FR' and 'french'. For some reason, however, it then used the
184        Windows-specific input and output files, which have 'french' screwed in.
185        So this could never have worked. One of the problems with locales is that
186        they aren't always the same. I have now updated RunTest so that it checks
187        the output of the locale test (test 3) against three different output
188        files, and it allows the test to pass if any one of them matches. With luck
189        this should make the test pass on some versions of Solaris where it was
190        failing. Because of the uncertainty, the script did not used to stop if
191        test 3 failed; it now does. If further versions of a French locale ever
192        come to light, they can now easily be added.
193    
194    16. If --with-pcregrep-bufsize was given a non-integer value such as "50K",
195        there was a message during ./configure, but it did not stop. This now
196        provokes an error. The invalid example in README has been corrected.
197        If a value less than the minimum is given, the minimum value has always
198        been used, but now a warning is given.
199    
200    17. If --enable-bsr-anycrlf was set, the special 16/32-bit test failed. This
201        was a bug in the test system, which is now fixed. Also, the list of various
202        configurations that are tested for each release did not have one with both
203        16/32 bits and --enable-bar-anycrlf. It now does.
204    
205    18. pcretest was missing "-C bsr" for displaying the \R default setting.
206    
207    19. Little endian PowerPC systems are supported now by the JIT compiler.
208    
209    20. The fast forward newline mechanism could enter to an infinite loop on
210        certain invalid UTF-8 input. Although we don't support these cases
211        this issue can be fixed by a performance optimization.
212    
213    21. Change 33 of 8.34 is not sufficient to ensure stack safety because it does
214        not take account if existing stack usage. There is now a new global
215        variable called pcre_stack_guard that can be set to point to an external
216        function to check stack availability. It is called at the start of
217        processing every parenthesized group.
218    
219    22. A typo in the code meant that in ungreedy mode the max/min qualifier
220        behaved like a min-possessive qualifier, and, for example, /a{1,3}b/U did
221        not match "ab".
222    
223    23. When UTF was disabled, the JIT program reported some incorrect compile
224        errors. These messages are silenced now.
225    
226    24. Experimental support for ARM-64 and MIPS-64 has been added to the JIT
227        compiler.
228    
229    25. Change all the temporary files used in RunGrepTest to be different to those
230        used by RunTest so that the tests can be run simultaneously, for example by
231        "make -j check".
232    
233    
234    Version 8.34 15-December-2013
235    -----------------------------
236    
237  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
238      executable memory. Patch inspired by Carsten Klein.      executable memory. Patch inspired by Carsten Klein.
239    
240  2.  ./configure --enable-coverage defined SUPPORT_GCOV in config.h, although  2.  ./configure --enable-coverage defined SUPPORT_GCOV in config.h, although
241      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
242      coverage involves only compiling and linking options and special targets in      coverage involves only compiling and linking options and special targets in
243      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
244      enable coverage support, which is totally false. There was also support for      enable coverage support, which is totally false. There was also support for
245      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
246      configure). SUPPORT_GCOV has now been removed.      configure). SUPPORT_GCOV has now been removed.
247    
248  3.  Make a small performance improvement in strlen16() and strlen32() in  3.  Make a small performance improvement in strlen16() and strlen32() in
249      pcretest.      pcretest.
250    
251  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,
252      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
253      these cases). There was also one in pcretest.c.      these cases). There was also one in pcretest.c.
254    
255  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.
256    
257  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
258      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 261  Version 8.34 xx-xxxx-201x
261      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
262      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
263      deemed as matching an empty string, or the program might have crashed.      deemed as matching an empty string, or the program might have crashed.
264    
265  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
266      recognizing that \h, \H, \v, \V, and \R must match a character.      recognizing that \h, \H, \v, \V, and \R must match a character.
267    
268  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
269      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.
270    
271  9.  Fixed two related bugs that applied to Unicode extended grapheme clusters  9.  Fixed two related bugs that applied to Unicode extended grapheme clusters
272      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
273      matched by pcre_exec() without using JIT:      matched by pcre_exec() without using JIT:
274    
275      (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
276          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
277          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
278          have the modifier quality were involved, e.g. Hangul syllables.          have the modifier quality were involved, e.g. Hangul syllables.
279    
280      (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
281          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
282          point, and potentially beyond the first character in the subject,          point, and potentially beyond the first character in the subject,
283          leading to a segfault or an incorrect match result.          leading to a segfault or an incorrect match result.
284    
285  10. A conditional group with an assertion condition could lead to PCRE  10. A conditional group with an assertion condition could lead to PCRE
286      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
287      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
288      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
289      start.      start.
290    
291  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
292      bug that caused the command "echo a | ./pcregrep -M '|a'" to loop.      bug that caused the command "echo a | ./pcregrep -M '|a'" to loop.
293    
294  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
295      compiled for z/OS as part of the special z/OS distribution.      compiled for z/OS as part of the special z/OS distribution.
296    
297  13. Added the -T and -TM options to pcretest.  13. Added the -T and -TM options to pcretest.
298    
299  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
300      has been refactored. Instead of creating the table dynamically during the      has been refactored. Instead of creating the table dynamically during the
301      actual compiling pass, the information is remembered during the pre-compile      actual compiling pass, the information is remembered during the pre-compile
302      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
303      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
304      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
305      shorter) and prepared the way for better handling of references to groups      shorter) and prepared the way for better handling of references to groups
306      with duplicate names.      with duplicate names.
307    
308  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
309      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.
310      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
311      first one was inspected. This change makes PCRE more compatible with Perl.      first one was inspected. This change makes PCRE more compatible with Perl.
312    
313  16. Unicode character properties were updated from Unicode 6.3.0.  16. Unicode character properties were updated from Unicode 6.3.0.
314    
315  17. The compile-time code for auto-possessification has been refactored, based  17. The compile-time code for auto-possessification has been refactored, based
316      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
317      compilation. The code is cleaner, and more cases are handled. The option      compilation. The code is cleaner, and more cases are handled. The option
318      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
319      options in pcretest are provided to set it.      options in pcretest are provided to set it. It can also be set by
320        (*NO_AUTO_POSSESS) at the start of a pattern.
321  18. The character VT has been added to the set of characters that match \s and  
322      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
323      5.18. There is now no difference between "Perl space" and "POSIX space".      characters that match \s and are generally treated as white space,
324        following this same change in Perl 5.18. There is now no difference between
325  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
326        other locales depends on the locale.
327    
328    19. The code for checking named groups as conditions, either for being set or
329      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
330      above). Processing unduplicated named groups should now be as fast at      above). Processing unduplicated named groups should now be as fast at
331      numerical groups, and processing duplicated groups should be faster than      numerical groups, and processing duplicated groups should be faster than
332      before.      before.
333    
334  20. Two patches to the CMake build system, by Alexander Barkov:  20. Two patches to the CMake build system, by Alexander Barkov:
335    
336        (1) Replace the "source" command by "." in CMakeLists.txt because        (1) Replace the "source" command by "." in CMakeLists.txt because
337            "source" is a bash-ism.            "source" is a bash-ism.
338    
339        (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;
340            without these the CMake build does not work on Solaris.            without these the CMake build does not work on Solaris.
341    
342  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
343      encountered capturing group of those numbers, they are treated as the      encountered capturing group of those numbers, they are treated as the
344      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
345      literals. PCRE now does the same.      literals. PCRE now does the same.
346    
347  22. Following Perl, added \o{} to specify codepoints in octal, making it  22. Following Perl, added \o{} to specify codepoints in octal, making it
348      possible to specify values greater than 0777 and also making them      possible to specify values greater than 0777 and also making them
349      unambiguous.      unambiguous.
350    
351  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
352      treating the string as literal. PCRE now does the same.      treating the string as literal. PCRE now does the same.
353    
354  24. RunTest used to grumble if an inappropriate test was selected explicitly,  24. RunTest used to grumble if an inappropriate test was selected explicitly,
355      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
356      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
357      inappropriate tests, as it always did when running all tests.      inappropriate tests, as it always did when running all tests.
358    
359  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
360      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
361      data that they returned was rubbish.      data that they returned was rubbish.
362    
363  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,
364      namely NEL (U+0085) and MONGOLIAN VOWEL SEPARATOR (U+180E), though they      namely NEL (U+0085) and MONGOLIAN VOWEL SEPARATOR (U+180E), though they
365      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
366      the horizontal and vertical whitespace characters used for \h and \v (which      the horizontal and vertical whitespace characters used for \h and \v (which
367      are defined only in one place) are now also used for \s.      are defined only in one place) are now also used for \s.
368    
369  27. Add JIT support for the 64 bit TileGX architecture.  27. Add JIT support for the 64 bit TileGX architecture.
370      Patch by Jiong Wang (Tilera Corporation).      Patch by Jiong Wang (Tilera Corporation).
371    
372  28. Possessive quantifiers for classes (both explicit and automatically  28. Possessive quantifiers for classes (both explicit and automatically
373      generated) now use special opcodes instead of wrapping in ONCE brackets.      generated) now use special opcodes instead of wrapping in ONCE brackets.
374    
375  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
376      (because it's meaningless), this was not happening when PCRE_CASELESS was      (because it's meaningless), this was not happening when PCRE_CASELESS was
377      set. Not wrong, but inefficient.      set. Not wrong, but inefficient.
378    
379  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
380      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
381      test contains no characters greater than 255, Perl doesn't realise it      test contains no characters greater than 255, Perl doesn't realise it
382      should be using Unicode semantics.      should be using Unicode semantics.
383    
384  31. Upgraded the handling of the POSIX classes [:graph:], [:print:], and  31. Upgraded the handling of the POSIX classes [:graph:], [:print:], and
385      [: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
386      does in Unicode mode.      does in Unicode mode.
387    
388  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
389      wrong test files can sometimes be quickly detected.      wrong test files can sometimes be quickly detected.
390    
391  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.
392      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
393      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
394      the equivalent in CMake.      the equivalent in CMake.
395    
396  34. Character classes such as [A-\d] or [a-[:digit:]] now cause compile-time  34. Character classes such as [A-\d] or [a-[:digit:]] now cause compile-time
397      errors. Perl warns for these when in warning mode, but PCRE has no facility      errors. Perl warns for these when in warning mode, but PCRE has no facility
398      for giving warnings.      for giving warnings.
399    
400    35. Change 34 for 8.13 allowed quantifiers on assertions, because Perl does.
401        However, this was not working for (?!) because it is optimized to (*FAIL),
402        for which PCRE does not allow quantifiers. The optimization is now disabled
403        when a quantifier follows (?!). I can't see any use for this, but it makes
404        things uniform.
405    
406    36. Perl no longer allows group names to start with digits, so I have made this
407        change also in PCRE. It simplifies the code a bit.
408    
409    37. In extended mode, Perl ignores spaces before a + that indicates a
410        possessive quantifier. PCRE allowed a space before the quantifier, but not
411        before the possessive +. It now does.
412    
413    38. The use of \K (reset reported match start) within a repeated possessive
414        group such as (a\Kb)*+ was not working.
415    
416    40. Document that the same character tables must be used at compile time and
417        run time, and that the facility to pass tables to pcre_exec() and
418        pcre_dfa_exec() is for use only with saved/restored patterns.
419    
420    41. Applied Jeff Trawick's patch CMakeLists.txt, which "provides two new
421        features for Builds with MSVC:
422    
423        1. Support pcre.rc and/or pcreposix.rc (as is already done for MinGW
424           builds). The .rc files can be used to set FileDescription and many other
425           attributes.
426    
427        2. Add an option (-DINSTALL_MSVC_PDB) to enable installation of .pdb files.
428           This allows higher-level build scripts which want .pdb files to avoid
429           hard-coding the exact files needed."
430    
431    42. Added support for [[:<:]] and [[:>:]] as used in the BSD POSIX library to
432        mean "start of word" and "end of word", respectively, as a transition aid.
433    
434    43. A minimizing repeat of a class containing codepoints greater than 255 in
435        non-UTF 16-bit or 32-bit modes caused an internal error when PCRE was
436        compiled to use the heap for recursion.
437    
438    44. Got rid of some compiler warnings for unused variables when UTF but not UCP
439        is configured.
440    
441    
442  Version 8.33 28-May-2013  Version 8.33 28-May-2013

Legend:
Removed from v.1392  
changed lines
  Added in v.1510

  ViewVC Help
Powered by ViewVC 1.1.5