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

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

  ViewVC Help
Powered by ViewVC 1.1.5