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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.1353  
changed lines
  Added in v.1523

  ViewVC Help
Powered by ViewVC 1.1.5