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

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

  ViewVC Help
Powered by ViewVC 1.1.5