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

Diff of /code/trunk/ChangeLog

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

revision 657 by ph10, Mon Aug 15 17:39:09 2011 UTC revision 1464 by zherczeg, Fri Mar 14 11:45:56 2014 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.13 02-Aug-2011  Version 8.35-RC1 04-March-2014
5    ------------------------------
6    
7    1.  A new flag is set, when property checks are present in an XCLASS.
8        When this flag is not set, PCRE can perform certain optimizations
9        such as studying these XCLASS-es.
10    
11    2.  The auto-possessification of character sets were improved: a normal
12        and an extended character set can be compared now. Furthermore
13        the JIT compiler optimizes more character set checks.
14    
15    3.  Got rid of some compiler warnings for potentially uninitialized variables
16        that show up only when compiled with -O2.
17    
18    4.  A pattern such as (?=ab\K) that uses \K in an assertion can set the start
19        of a match later then the end of the match. The pcretest program was not
20        handling the case sensibly - it was outputting from the start to the next
21        binary zero. It now reports this situation in a message, and outputs the
22        text from the end to the start.
23    
24    5.  Fast forward search is improved in JIT. Instead of the first three
25        characters, any three characters with fixed position can be searched.
26        Search order: first, last, middle.
27    
28    6.  Improve character range checks in JIT. Characters are read by an inprecise
29        function now, which returns with an unknown value if the character code is
30        above a certain treshold (e.g: 256). The only limitation is that the value
31        must be bigger than the treshold as well. This function is useful, when
32        the characters above the treshold are handled in the same way.
33    
34    7.  The macros whose names start with RAWUCHAR are placeholders for a future
35        mode in which only the bottom 21 bits of 32-bit data items are used. To
36        make this more memorable for those maintaining the code, the names have
37        been changed to start with UCHAR21, and an extensive comment has been added
38        to their definition.
39    
40    8.  Add missing (new) files sljitNativeTILEGX.c and sljitNativeTILEGX-encoder.c
41        to the export list in Makefile.am (they were accidentally omitted from the
42        8.34 tarball).
43    
44    9.  The informational output from pcretest used the phrase "starting byte set"
45        which is inappropriate for the 16-bit and 32-bit libraries. As the output
46        for "first char" and "need char" really means "non-UTF-char", I've changed
47        "byte" to "char", and slightly reworded the output. The documentation about
48        these values has also been (I hope) clarified.
49    
50    10. Another JIT related optimization: use table jumps for selecting the correct
51        backtracking path, when more than four alternatives are present inside a
52        bracket.
53    
54    11. Empty match is not possible, when the minimum length is greater than zero,
55        and there is no \K in the pattern. JIT should avoid empty match checks in
56        such cases.
57    
58    12. In a caseless character class with UCP support, when a character with more
59        than one alternative case was not the first character of a range, not all
60        the alternative cases were added to the class. For example, s and \x{17f}
61        are both alternative cases for S: the class [RST] was handled correctly,
62        but [R-T] was not.
63    
64    13. The configure.ac file always checked for pthread support when JIT was
65        enabled. This is not used in Windows, so I have put this test inside a
66        check for the presence of windows.h (which was already tested for).
67    
68    14. Improve pattern prefix search by a simplified Boyer-Moore algorithm in JIT.
69        The algorithm provides a way to skip certain starting offsets, and usually
70        faster than linear prefix searches.
71    
72    15. Change 13 for 8.20 updated RunTest to check for the 'fr' locale as well
73        as for 'fr_FR' and 'french'. For some reason, however, it then used the
74        Windows-specific input and output files, which have 'french' screwed in.
75        So this could never have worked. One of the problems with locales is that
76        they aren't always the same. I have now updated RunTest so that it checks
77        the output of the locale test (test 3) against three different output
78        files, and it allows the test to pass if any one of them matches. With luck
79        this should make the test pass on some versions of Solaris where it was
80        failing. Because of the uncertainty, the script did not used to stop if
81        test 3 failed; it now does. If further versions of a French locale ever
82        come to light, they can now easily be added.
83    
84    16. If --with-pcregrep-bufsize was given a non-integer value such as "50K",
85        there was a message during ./configure, but it did not stop. This now
86        provokes an error. The invalid example in README has been corrected.
87        If a value less than the minimum is given, the minimum value has always
88        been used, but now a warning is given.
89    
90    17. If --enable-bsr-anycrlf was set, the special 16/32-bit test failed. This
91        was a bug in the test system, which is now fixed. Also, the list of various
92        configurations that are tested for each release did not have one with both
93        16/32 bits and --enable-bar-anycrlf. It now does.
94    
95    18. pcretest was missing "-C bsr" for displaying the \R default setting.
96    
97    19. Little endian PowerPC systems are supported now by the JIT compiler.
98    
99    20. The fast forward newline mechanism could enter to an infinite loop on
100        certain invalid UTF-8 input. Although we don't support these cases
101        this issue can be fixed by a performance optimization.
102    
103    21. Change 33 of 8.34 is not sufficient to ensure stack safety because it does
104        not take account if existing stack usage. There is now a new global
105        variable called pcre_stack_guard that can be set to point to an external
106        function to check stack availability. It is called at the start of
107        processing every parenthesized group.
108    
109    22. A typo in the code meant that in ungreedy mode the max/min qualifier
110        behaved like a min-possessive qualifier, and, for example, /a{1,3}b/U did
111        not match "ab".
112    
113    23. When UTF was disabled, the JIT program reported some incorrect compile
114        errors. These messages are silenced now.
115    
116    
117    Version 8.34 15-December-2013
118    -----------------------------
119    
120    1.  Add pcre[16|32]_jit_free_unused_memory to forcibly free unused JIT
121        executable memory. Patch inspired by Carsten Klein.
122    
123    2.  ./configure --enable-coverage defined SUPPORT_GCOV in config.h, although
124        this macro is never tested and has no effect, because the work to support
125        coverage involves only compiling and linking options and special targets in
126        the Makefile. The comment in config.h implied that defining the macro would
127        enable coverage support, which is totally false. There was also support for
128        setting this macro in the CMake files (my fault, I just copied it from
129        configure). SUPPORT_GCOV has now been removed.
130    
131    3.  Make a small performance improvement in strlen16() and strlen32() in
132        pcretest.
133    
134    4.  Change 36 for 8.33 left some unreachable statements in pcre_exec.c,
135        detected by the Solaris compiler (gcc doesn't seem to be able to diagnose
136        these cases). There was also one in pcretest.c.
137    
138    5.  Cleaned up a "may be uninitialized" compiler warning in pcre_exec.c.
139    
140    6.  In UTF mode, the code for checking whether a group could match an empty
141        string (which is used for indefinitely repeated groups to allow for
142        breaking an infinite loop) was broken when the group contained a repeated
143        negated single-character class with a character that occupied more than one
144        data item and had a minimum repetition of zero (for example, [^\x{100}]* in
145        UTF-8 mode). The effect was undefined: the group might or might not be
146        deemed as matching an empty string, or the program might have crashed.
147    
148    7.  The code for checking whether a group could match an empty string was not
149        recognizing that \h, \H, \v, \V, and \R must match a character.
150    
151    8.  Implemented PCRE_INFO_MATCH_EMPTY, which yields 1 if the pattern can match
152        an empty string. If it can, pcretest shows this in its information output.
153    
154    9.  Fixed two related bugs that applied to Unicode extended grapheme clusters
155        that were repeated with a maximizing qualifier (e.g. \X* or \X{2,5}) when
156        matched by pcre_exec() without using JIT:
157    
158        (a) If the rest of the pattern did not match after a maximal run of
159            grapheme clusters, the code for backing up to try with fewer of them
160            did not always back up over a full grapheme when characters that do not
161            have the modifier quality were involved, e.g. Hangul syllables.
162    
163        (b) If the match point in a subject started with modifier character, and
164            there was no match, the code could incorrectly back up beyond the match
165            point, and potentially beyond the first character in the subject,
166            leading to a segfault or an incorrect match result.
167    
168    10. A conditional group with an assertion condition could lead to PCRE
169        recording an incorrect first data item for a match if no other first data
170        item was recorded. For example, the pattern (?(?=ab)ab) recorded "a" as a
171        first data item, and therefore matched "ca" after "c" instead of at the
172        start.
173    
174    11. Change 40 for 8.33 (allowing pcregrep to find empty strings) showed up a
175        bug that caused the command "echo a | ./pcregrep -M '|a'" to loop.
176    
177    12. The source of pcregrep now includes z/OS-specific code so that it can be
178        compiled for z/OS as part of the special z/OS distribution.
179    
180    13. Added the -T and -TM options to pcretest.
181    
182    14. The code in pcre_compile.c for creating the table of named capturing groups
183        has been refactored. Instead of creating the table dynamically during the
184        actual compiling pass, the information is remembered during the pre-compile
185        pass (on the stack unless there are more than 20 named groups, in which
186        case malloc() is used) and the whole table is created before the actual
187        compile happens. This has simplified the code (it is now nearly 150 lines
188        shorter) and prepared the way for better handling of references to groups
189        with duplicate names.
190    
191    15. A back reference to a named subpattern when there is more than one of the
192        same name now checks them in the order in which they appear in the pattern.
193        The first one that is set is used for the reference. Previously only the
194        first one was inspected. This change makes PCRE more compatible with Perl.
195    
196    16. Unicode character properties were updated from Unicode 6.3.0.
197    
198    17. The compile-time code for auto-possessification has been refactored, based
199        on a patch by Zoltan Herczeg. It now happens after instead of during
200        compilation. The code is cleaner, and more cases are handled. The option
201        PCRE_NO_AUTO_POSSESS is added for testing purposes, and the -O and /O
202        options in pcretest are provided to set it. It can also be set by
203        (*NO_AUTO_POSSESS) at the start of a pattern.
204    
205    18. The character VT has been added to the default ("C" locale) set of
206        characters that match \s and are generally treated as white space,
207        following this same change in Perl 5.18. There is now no difference between
208        "Perl space" and "POSIX space". Whether VT is treated as white space in
209        other locales depends on the locale.
210    
211    19. The code for checking named groups as conditions, either for being set or
212        for being recursed, has been refactored (this is related to 14 and 15
213        above). Processing unduplicated named groups should now be as fast at
214        numerical groups, and processing duplicated groups should be faster than
215        before.
216    
217    20. Two patches to the CMake build system, by Alexander Barkov:
218    
219          (1) Replace the "source" command by "." in CMakeLists.txt because
220              "source" is a bash-ism.
221    
222          (2) Add missing HAVE_STDINT_H and HAVE_INTTYPES_H to config-cmake.h.in;
223              without these the CMake build does not work on Solaris.
224    
225    21. Perl has changed its handling of \8 and \9. If there is no previously
226        encountered capturing group of those numbers, they are treated as the
227        literal characters 8 and 9 instead of a binary zero followed by the
228        literals. PCRE now does the same.
229    
230    22. Following Perl, added \o{} to specify codepoints in octal, making it
231        possible to specify values greater than 0777 and also making them
232        unambiguous.
233    
234    23. Perl now gives an error for missing closing braces after \x{... instead of
235        treating the string as literal. PCRE now does the same.
236    
237    24. RunTest used to grumble if an inappropriate test was selected explicitly,
238        but just skip it when running all tests. This make it awkward to run ranges
239        of tests when one of them was inappropriate. Now it just skips any
240        inappropriate tests, as it always did when running all tests.
241    
242    25. If PCRE_AUTO_CALLOUT and PCRE_UCP were set for a pattern that contained
243        character types such as \d or \w, too many callouts were inserted, and the
244        data that they returned was rubbish.
245    
246    26. In UCP mode, \s was not matching two of the characters that Perl matches,
247        namely NEL (U+0085) and MONGOLIAN VOWEL SEPARATOR (U+180E), though they
248        were matched by \h. The code has now been refactored so that the lists of
249        the horizontal and vertical whitespace characters used for \h and \v (which
250        are defined only in one place) are now also used for \s.
251    
252    27. Add JIT support for the 64 bit TileGX architecture.
253        Patch by Jiong Wang (Tilera Corporation).
254    
255    28. Possessive quantifiers for classes (both explicit and automatically
256        generated) now use special opcodes instead of wrapping in ONCE brackets.
257    
258    29. Whereas an item such as A{4}+ ignored the possessivenes of the quantifier
259        (because it's meaningless), this was not happening when PCRE_CASELESS was
260        set. Not wrong, but inefficient.
261    
262    30. Updated perltest.pl to add /u (force Unicode mode) when /W (use Unicode
263        properties for \w, \d, etc) is present in a test regex. Otherwise if the
264        test contains no characters greater than 255, Perl doesn't realise it
265        should be using Unicode semantics.
266    
267    31. Upgraded the handling of the POSIX classes [:graph:], [:print:], and
268        [:punct:] when PCRE_UCP is set so as to include the same characters as Perl
269        does in Unicode mode.
270    
271    32. Added the "forbid" facility to pcretest so that putting tests into the
272        wrong test files can sometimes be quickly detected.
273    
274    33. There is now a limit (default 250) on the depth of nesting of parentheses.
275        This limit is imposed to control the amount of system stack used at compile
276        time. It can be changed at build time by --with-parens-nest-limit=xxx or
277        the equivalent in CMake.
278    
279    34. Character classes such as [A-\d] or [a-[:digit:]] now cause compile-time
280        errors. Perl warns for these when in warning mode, but PCRE has no facility
281        for giving warnings.
282    
283    35. Change 34 for 8.13 allowed quantifiers on assertions, because Perl does.
284        However, this was not working for (?!) because it is optimized to (*FAIL),
285        for which PCRE does not allow quantifiers. The optimization is now disabled
286        when a quantifier follows (?!). I can't see any use for this, but it makes
287        things uniform.
288    
289    36. Perl no longer allows group names to start with digits, so I have made this
290        change also in PCRE. It simplifies the code a bit.
291    
292    37. In extended mode, Perl ignores spaces before a + that indicates a
293        possessive quantifier. PCRE allowed a space before the quantifier, but not
294        before the possessive +. It now does.
295    
296    38. The use of \K (reset reported match start) within a repeated possessive
297        group such as (a\Kb)*+ was not working.
298    
299    40. Document that the same character tables must be used at compile time and
300        run time, and that the facility to pass tables to pcre_exec() and
301        pcre_dfa_exec() is for use only with saved/restored patterns.
302    
303    41. Applied Jeff Trawick's patch CMakeLists.txt, which "provides two new
304        features for Builds with MSVC:
305    
306        1. Support pcre.rc and/or pcreposix.rc (as is already done for MinGW
307           builds). The .rc files can be used to set FileDescription and many other
308           attributes.
309    
310        2. Add an option (-DINSTALL_MSVC_PDB) to enable installation of .pdb files.
311           This allows higher-level build scripts which want .pdb files to avoid
312           hard-coding the exact files needed."
313    
314    42. Added support for [[:<:]] and [[:>:]] as used in the BSD POSIX library to
315        mean "start of word" and "end of word", respectively, as a transition aid.
316    
317    43. A minimizing repeat of a class containing codepoints greater than 255 in
318        non-UTF 16-bit or 32-bit modes caused an internal error when PCRE was
319        compiled to use the heap for recursion.
320    
321    44. Got rid of some compiler warnings for unused variables when UTF but not UCP
322        is configured.
323    
324    
325    Version 8.33 28-May-2013
326    ------------------------
327    
328    1.  Added 'U' to some constants that are compared to unsigned integers, to
329        avoid compiler signed/unsigned warnings. Added (int) casts to unsigned
330        variables that are added to signed variables, to ensure the result is
331        signed and can be negated.
332    
333    2.  Applied patch by Daniel Richard G for quashing MSVC warnings to the
334        CMake config files.
335    
336    3.  Revise the creation of config.h.generic so that all boolean macros are
337        #undefined, whereas non-boolean macros are #ifndef/#endif-ed. This makes
338        overriding via -D on the command line possible.
339    
340    4.  Changing the definition of the variable "op" in pcre_exec.c from pcre_uchar
341        to unsigned int is reported to make a quite noticeable speed difference in
342        a specific Windows environment. Testing on Linux did also appear to show
343        some benefit (and it is clearly not harmful). Also fixed the definition of
344        Xop which should be unsigned.
345    
346    5.  Related to (4), changing the definition of the intermediate variable cc
347        in repeated character loops from pcre_uchar to pcre_uint32 also gave speed
348        improvements.
349    
350    6.  Fix forward search in JIT when link size is 3 or greater. Also removed some
351        unnecessary spaces.
352    
353    7.  Adjust autogen.sh and configure.ac to lose warnings given by automake 1.12
354        and later.
355    
356    8.  Fix two buffer over read issues in 16 and 32 bit modes. Affects JIT only.
357    
358    9.  Optimizing fast_forward_start_bits in JIT.
359    
360    10. Adding support for callouts in JIT, and fixing some issues revealed
361        during this work. Namely:
362    
363        (a) Unoptimized capturing brackets incorrectly reset on backtrack.
364    
365        (b) Minimum length was not checked before the matching is started.
366    
367    11. The value of capture_last that is passed to callouts was incorrect in some
368        cases when there was a capture on one path that was subsequently abandoned
369        after a backtrack. Also, the capture_last value is now reset after a
370        recursion, since all captures are also reset in this case.
371    
372    12. The interpreter no longer returns the "too many substrings" error in the
373        case when an overflowing capture is in a branch that is subsequently
374        abandoned after a backtrack.
375    
376    13. In the pathological case when an offset vector of size 2 is used, pcretest
377        now prints out the matched string after a yield of 0 or 1.
378    
379    14. Inlining subpatterns in recursions, when certain conditions are fulfilled.
380        Only supported by the JIT compiler at the moment.
381    
382    15. JIT compiler now supports 32 bit Macs thanks to Lawrence Velazquez.
383    
384    16. Partial matches now set offsets[2] to the "bumpalong" value, that is, the
385        offset of the starting point of the matching process, provided the offsets
386        vector is large enough.
387    
388    17. The \A escape now records a lookbehind value of 1, though its execution
389        does not actually inspect the previous character. This is to ensure that,
390        in partial multi-segment matching, at least one character from the old
391        segment is retained when a new segment is processed. Otherwise, if there
392        are no lookbehinds in the pattern, \A might match incorrectly at the start
393        of a new segment.
394    
395    18. Added some #ifdef __VMS code into pcretest.c to help VMS implementations.
396    
397    19. Redefined some pcre_uchar variables in pcre_exec.c as pcre_uint32; this
398        gives some modest performance improvement in 8-bit mode.
399    
400    20. Added the PCRE-specific property \p{Xuc} for matching characters that can
401        be expressed in certain programming languages using Universal Character
402        Names.
403    
404    21. Unicode validation has been updated in the light of Unicode Corrigendum #9,
405        which points out that "non characters" are not "characters that may not
406        appear in Unicode strings" but rather "characters that are reserved for
407        internal use and have only local meaning".
408    
409    22. When a pattern was compiled with automatic callouts (PCRE_AUTO_CALLOUT) and
410        there was a conditional group that depended on an assertion, if the
411        assertion was false, the callout that immediately followed the alternation
412        in the condition was skipped when pcre_exec() was used for matching.
413    
414    23. Allow an explicit callout to be inserted before an assertion that is the
415        condition for a conditional group, for compatibility with automatic
416        callouts, which always insert a callout at this point.
417    
418    24. In 8.31, (*COMMIT) was confined to within a recursive subpattern. Perl also
419        confines (*SKIP) and (*PRUNE) in the same way, and this has now been done.
420    
421    25. (*PRUNE) is now supported by the JIT compiler.
422    
423    26. Fix infinite loop when /(?<=(*SKIP)ac)a/ is matched against aa.
424    
425    27. Fix the case where there are two or more SKIPs with arguments that may be
426        ignored.
427    
428    28. (*SKIP) is now supported by the JIT compiler.
429    
430    29. (*THEN) is now supported by the JIT compiler.
431    
432    30. Update RunTest with additional test selector options.
433    
434    31. The way PCRE handles backtracking verbs has been changed in two ways.
435    
436        (1) Previously, in something like (*COMMIT)(*SKIP), COMMIT would override
437        SKIP. Now, PCRE acts on whichever backtracking verb is reached first by
438        backtracking. In some cases this makes it more Perl-compatible, but Perl's
439        rather obscure rules do not always do the same thing.
440    
441        (2) Previously, backtracking verbs were confined within assertions. This is
442        no longer the case for positive assertions, except for (*ACCEPT). Again,
443        this sometimes improves Perl compatibility, and sometimes does not.
444    
445    32. A number of tests that were in test 2 because Perl did things differently
446        have been moved to test 1, because either Perl or PCRE has changed, and
447        these tests are now compatible.
448    
449    32. Backtracking control verbs are now handled in the same way in JIT and
450        interpreter.
451    
452    33. An opening parenthesis in a MARK/PRUNE/SKIP/THEN name in a pattern that
453        contained a forward subroutine reference caused a compile error.
454    
455    34. Auto-detect and optimize limited repetitions in JIT.
456    
457    35. Implement PCRE_NEVER_UTF to lock out the use of UTF, in particular,
458        blocking (*UTF) etc.
459    
460    36. In the interpreter, maximizing pattern repetitions for characters and
461        character types now use tail recursion, which reduces stack usage.
462    
463    37. The value of the max lookbehind was not correctly preserved if a compiled
464        and saved regex was reloaded on a host of different endianness.
465    
466    38. Implemented (*LIMIT_MATCH) and (*LIMIT_RECURSION). As part of the extension
467        of the compiled pattern block, expand the flags field from 16 to 32 bits
468        because it was almost full.
469    
470    39. Try madvise first before posix_madvise.
471    
472    40. Change 7 for PCRE 7.9 made it impossible for pcregrep to find empty lines
473        with a pattern such as ^$. It has taken 4 years for anybody to notice! The
474        original change locked out all matches of empty strings. This has been
475        changed so that one match of an empty string per line is recognized.
476        Subsequent searches on the same line (for colouring or for --only-matching,
477        for example) do not recognize empty strings.
478    
479    41. Applied a user patch to fix a number of spelling mistakes in comments.
480    
481    42. Data lines longer than 65536 caused pcretest to crash.
482    
483    43. Clarified the data type for length and startoffset arguments for pcre_exec
484        and pcre_dfa_exec in the function-specific man pages, where they were
485        explicitly stated to be in bytes, never having been updated. I also added
486        some clarification to the pcreapi man page.
487    
488    44. A call to pcre_dfa_exec() with an output vector size less than 2 caused
489        a segmentation fault.
490    
491    
492    Version 8.32 30-November-2012
493    -----------------------------
494    
495    1.  Improved JIT compiler optimizations for first character search and single
496        character iterators.
497    
498    2.  Supporting IBM XL C compilers for PPC architectures in the JIT compiler.
499        Patch by Daniel Richard G.
500    
501    3.  Single character iterator optimizations in the JIT compiler.
502    
503    4.  Improved JIT compiler optimizations for character ranges.
504    
505    5.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.
506        Reported by Giuseppe D'Angelo.
507    
508    6.  The PCRE_STARTLINE bit, indicating that a match can occur only at the start
509        of a line, was being set incorrectly in cases where .* appeared inside
510        atomic brackets at the start of a pattern, or where there was a subsequent
511        *PRUNE or *SKIP.
512    
513    7.  Improved instruction cache flush for POWER/PowerPC.
514        Patch by Daniel Richard G.
515    
516    8.  Fixed a number of issues in pcregrep, making it more compatible with GNU
517        grep:
518    
519        (a) There is now no limit to the number of patterns to be matched.
520    
521        (b) An error is given if a pattern is too long.
522    
523        (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir
524            are now supported.
525    
526        (d) --exclude-from and --include-from (multiple use) have been added.
527    
528        (e) Exclusions and inclusions now apply to all files and directories, not
529            just to those obtained from scanning a directory recursively.
530    
531        (f) Multiple uses of -f and --file-list are now supported.
532    
533        (g) In a Windows environment, the default for -d has been changed from
534            "read" (the GNU grep default) to "skip", because otherwise the presence
535            of a directory in the file list provokes an error.
536    
537        (h) The documentation has been revised and clarified in places.
538    
539    9.  Improve the matching speed of capturing brackets.
540    
541    10. Changed the meaning of \X so that it now matches a Unicode extended
542        grapheme cluster.
543    
544    11. Patch by Daniel Richard G to the autoconf files to add a macro for sorting
545        out POSIX threads when JIT support is configured.
546    
547    12. Added support for PCRE_STUDY_EXTRA_NEEDED.
548    
549    13. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg
550        structure could go wrong in environments where size_t is not the same size
551        as int.
552    
553    14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be
554        set.
555    
556    15. The EBCDIC support had decayed; later updates to the code had included
557        explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a
558        general tidy up of EBCDIC-related issues, and the documentation was also
559        not quite right. There is now a test that can be run on ASCII systems to
560        check some of the EBCDIC-related things (but is it not a full test).
561    
562    16. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting
563        in a small tidy to the code.
564    
565    17. Fix JIT tests when UTF is disabled and both 8 and 16 bit mode are enabled.
566    
567    18. If the --only-matching (-o) option in pcregrep is specified multiple
568        times, each one causes appropriate output. For example, -o1 -o2 outputs the
569        substrings matched by the 1st and 2nd capturing parentheses. A separating
570        string can be specified by --om-separator (default empty).
571    
572    19. Improving the first n character searches.
573    
574    20. Turn case lists for horizontal and vertical white space into macros so that
575        they are defined only once.
576    
577    21. This set of changes together give more compatible Unicode case-folding
578        behaviour for characters that have more than one other case when UCP
579        support is available.
580    
581        (a) The Unicode property table now has offsets into a new table of sets of
582            three or more characters that are case-equivalent. The MultiStage2.py
583            script that generates these tables (the pcre_ucd.c file) now scans
584            CaseFolding.txt instead of UnicodeData.txt for character case
585            information.
586    
587        (b) The code for adding characters or ranges of characters to a character
588            class has been abstracted into a generalized function that also handles
589            case-independence. In UTF-mode with UCP support, this uses the new data
590            to handle characters with more than one other case.
591    
592        (c) A bug that is fixed as a result of (b) is that codepoints less than 256
593            whose other case is greater than 256 are now correctly matched
594            caselessly. Previously, the high codepoint matched the low one, but not
595            vice versa.
596    
597        (d) The processing of \h, \H, \v, and \ in character classes now makes use
598            of the new class addition function, using character lists defined as
599            macros alongside the case definitions of 20 above.
600    
601        (e) Caseless back references now work with characters that have more than
602            one other case.
603    
604        (f) General caseless matching of characters with more than one other case
605            is supported.
606    
607    22. Unicode character properties were updated from Unicode 6.2.0
608    
609    23. Improved CMake support under Windows. Patch by Daniel Richard G.
610    
611    24. Add support for 32-bit character strings, and UTF-32
612    
613    25. Major JIT compiler update (code refactoring and bugfixing).
614        Experimental Sparc 32 support is added.
615    
616    26. Applied a modified version of Daniel Richard G's patch to create
617        pcre.h.generic and config.h.generic by "make" instead of in the
618        PrepareRelease script.
619    
620    27. Added a definition for CHAR_NULL (helpful for the z/OS port), and use it in
621        pcre_compile.c when checking for a zero character.
622    
623    28. Introducing a native interface for JIT. Through this interface, the compiled
624        machine code can be directly executed. The purpose of this interface is to
625        provide fast pattern matching, so several sanity checks are not performed.
626        However, feature tests are still performed. The new interface provides
627        1.4x speedup compared to the old one.
628    
629    29. If pcre_exec() or pcre_dfa_exec() was called with a negative value for
630        the subject string length, the error given was PCRE_ERROR_BADOFFSET, which
631        was confusing. There is now a new error PCRE_ERROR_BADLENGTH for this case.
632    
633    30. In 8-bit UTF-8 mode, pcretest failed to give an error for data codepoints
634        greater than 0x7fffffff (which cannot be represented in UTF-8, even under
635        the "old" RFC 2279). Instead, it ended up passing a negative length to
636        pcre_exec().
637    
638    31. Add support for GCC's visibility feature to hide internal functions.
639    
640    32. Running "pcretest -C pcre8" or "pcretest -C pcre16" gave a spurious error
641        "unknown -C option" after outputting 0 or 1.
642    
643    33. There is now support for generating a code coverage report for the test
644        suite in environments where gcc is the compiler and lcov is installed. This
645        is mainly for the benefit of the developers.
646    
647    34. If PCRE is built with --enable-valgrind, certain memory regions are marked
648        unaddressable using valgrind annotations, allowing valgrind to detect
649        invalid memory accesses. This is mainly for the benefit of the developers.
650    
651    25. (*UTF) can now be used to start a pattern in any of the three libraries.
652    
653    26. Give configure error if --enable-cpp but no C++ compiler found.
654    
655    
656    Version 8.31 06-July-2012
657    -------------------------
658    
659    1.  Fixing a wrong JIT test case and some compiler warnings.
660    
661    2.  Removed a bashism from the RunTest script.
662    
663    3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied
664        to unsigned type, result still unsigned" that was given by an MS compiler
665        on encountering the code "-sizeof(xxx)".
666    
667    4.  Partial matching support is added to the JIT compiler.
668    
669    5.  Fixed several bugs concerned with partial matching of items that consist
670        of more than one character:
671    
672        (a) /^(..)\1/ did not partially match "aba" because checking references was
673            done on an "all or nothing" basis. This also applied to repeated
674            references.
675    
676        (b) \R did not give a hard partial match if \r was found at the end of the
677            subject.
678    
679        (c) \X did not give a hard partial match after matching one or more
680            characters at the end of the subject.
681    
682        (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize
683            a partial match for the string "\r".
684    
685        (e) When newline was set to CRLF, the metacharacter "." did not recognize
686            a partial match for a CR character at the end of the subject string.
687    
688    6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when
689        running pcretest, the text "(JIT)" added to the output whenever JIT is
690        actually used to run the match.
691    
692    7.  Individual JIT compile options can be set in pcretest by following -s+[+]
693        or /S+[+] with a digit between 1 and 7.
694    
695    8.  OP_NOT now supports any UTF character not just single-byte ones.
696    
697    9.  (*MARK) control verb is now supported by the JIT compiler.
698    
699    10. The command "./RunTest list" lists the available tests without actually
700        running any of them. (Because I keep forgetting what they all are.)
701    
702    11. Add PCRE_INFO_MAXLOOKBEHIND.
703    
704    12. Applied a (slightly modified) user-supplied patch that improves performance
705        when the heap is used for recursion (compiled with --disable-stack-for-
706        recursion). Instead of malloc and free for each heap frame each time a
707        logical recursion happens, frames are retained on a chain and re-used where
708        possible. This sometimes gives as much as 30% improvement.
709    
710    13. As documented, (*COMMIT) is now confined to within a recursive subpattern
711        call.
712    
713    14. As documented, (*COMMIT) is now confined to within a positive assertion.
714    
715    15. It is now possible to link pcretest with libedit as an alternative to
716        libreadline.
717    
718    16. (*COMMIT) control verb is now supported by the JIT compiler.
719    
720    17. The Unicode data tables have been updated to Unicode 6.1.0.
721    
722    18. Added --file-list option to pcregrep.
723    
724    19. Added binary file support to pcregrep, including the -a, --binary-files,
725        -I, and --text options.
726    
727    20. The madvise function is renamed for posix_madvise for QNX compatibility
728        reasons. Fixed by Giuseppe D'Angelo.
729    
730    21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
731    
732    22. Changed the option for creating symbolic links for 16-bit man pages from
733        -s to -sf so that re-installing does not cause issues.
734    
735    23. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it.
736    
737    24. Fixed a very old bug in pcretest that caused errors with restarted DFA
738        matches in certain environments (the workspace was not being correctly
739        retained). Also added to pcre_dfa_exec() a simple plausibility check on
740        some of the workspace data at the beginning of a restart.
741    
742    25. \s*\R was auto-possessifying the \s* when it should not, whereas \S*\R
743        was not doing so when it should - probably a typo introduced by SVN 528
744        (change 8.10/14).
745    
746    26. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the
747        \w+ when the character tables indicated that \x{c4} was a word character.
748        There were several related cases, all because the tests for doing a table
749        lookup were testing for characters less than 127 instead of 255.
750    
751    27. If a pattern contains capturing parentheses that are not used in a match,
752        their slots in the ovector are set to -1. For those that are higher than
753        any matched groups, this happens at the end of processing. In the case when
754        there were back references that the ovector was too small to contain
755        (causing temporary malloc'd memory to be used during matching), and the
756        highest capturing number was not used, memory off the end of the ovector
757        was incorrectly being set to -1. (It was using the size of the temporary
758        memory instead of the true size.)
759    
760    28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
761        ovector size, it uses memory at the end of the block that it has got.
762    
763    29. Check for an overlong MARK name and give an error at compile time. The
764        limit is 255 for the 8-bit library and 65535 for the 16-bit library.
765    
766    30. JIT compiler update.
767    
768    31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
769        Rill for the patch.
770    
771    32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
772    
773    33. Variable renamings in the PCRE-JIT compiler. No functionality change.
774    
775    34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
776        SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
777        was enabled.
778    
779    35. Improve JIT code generation for greedy plus quantifier.
780    
781    36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
782        1 to "aa" instead of to an empty string. The bug affected repeated groups
783        that could potentially match an empty string.
784    
785    37. Optimizing single character iterators in JIT.
786    
787    38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
788        the same checks as \x{...} characters in non-JavaScript mode. Specifically,
789        codepoints that are too big for the mode are faulted, and in a UTF mode,
790        disallowed codepoints are also faulted.
791    
792    39. If PCRE was compiled with UTF support, in three places in the DFA
793        matcher there was code that should only have been obeyed in UTF mode, but
794        was being obeyed unconditionally. In 8-bit mode this could cause incorrect
795        processing when bytes with values greater than 127 were present. In 16-bit
796        mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
797        both cases the values are those that cannot be the first data item in a UTF
798        character. The three items that might have provoked this were recursions,
799        possessively repeated groups, and atomic groups.
800    
801    40. Ensure that libpcre is explicitly listed in the link commands for pcretest
802        and pcregrep, because some OS require shared objects to be explicitly
803        passed to ld, causing the link step to fail if they are not.
804    
805    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
806        mode, patterns that started with \h* or \R* might be incorrectly matched.
807    
808    
809    Version 8.30 04-February-2012
810    -----------------------------
811    
812    1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
813        name is defined in ctype.h.
814    
815    2.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
816        only in quite long subpatterns.
817    
818    3.  Removed the function pcre_info(), which has been obsolete and deprecated
819        since it was replaced by pcre_fullinfo() in February 2000.
820    
821    4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
822        match a (*MARK), and the match failed at the start of the subject, a
823        reference to memory before the start of the subject could occur. This bug
824        was introduced by fix 17 of release 8.21.
825    
826    5.  A reference to an unset group with zero minimum repetition was giving
827        totally wrong answers (in non-JavaScript-compatibility mode). For example,
828        /(another)?(\1?)test/ matched against "hello world test". This bug was
829        introduced in release 8.13.
830    
831    6.  Add support for 16-bit character strings (a large amount of work involving
832        many changes and refactorings).
833    
834    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
835        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
836        from a file.
837    
838    8.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
839        rounding is not applied in this particular case).
840    
841    9.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
842        if they appear, or are escaped, in patterns.
843    
844    10. Get rid of a number of -Wunused-but-set-variable warnings.
845    
846    11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
847        "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
848        Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
849        also returns the mark "x". This bug applied to capturing parentheses,
850        non-capturing parentheses, and atomic parentheses. It also applied to some
851        assertions.
852    
853    12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
854        information out of configure.ac instead of relying on pcre.h.generic, which
855        is not stored in the repository.
856    
857    13. Applied Dmitry V. Levin's patch for a more portable method for linking with
858        -lreadline.
859    
860    14. ZH added PCRE_CONFIG_JITTARGET; added its output to pcretest -C.
861    
862    15. Applied Graycode's patch to put the top-level frame on the stack rather
863        than the heap when not using the stack for recursion. This gives a
864        performance improvement in many cases when recursion is not deep.
865    
866    16. Experimental code added to "pcretest -C" to output the stack frame size.
867    
868    
869    Version 8.21 12-Dec-2011
870    ------------------------
871    
872    1.  Updating the JIT compiler.
873    
874    2.  JIT compiler now supports OP_NCREF, OP_RREF and OP_NRREF. New test cases
875        are added as well.
876    
877    3.  Fix cache-flush issue on PowerPC (It is still an experimental JIT port).
878        PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before
879        calling _pcre_jit_exec. Some extra comments are added.
880    
881    4.  (*MARK) settings inside atomic groups that do not contain any capturing
882        parentheses, for example, (?>a(*:m)), were not being passed out. This bug
883        was introduced by change 18 for 8.20.
884    
885    5.  Supporting of \x, \U and \u in JavaScript compatibility mode based on the
886        ECMA-262 standard.
887    
888    6.  Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were
889        erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
890        This bug was probably introduced by change 9 of 8.13.
891    
892    7.  While fixing 6 above, I noticed that a number of other items were being
893        incorrectly rejected as "not fixed length". This arose partly because newer
894        opcodes had not been added to the fixed-length checking code. I have (a)
895        corrected the bug and added tests for these items, and (b) arranged for an
896        error to occur if an unknown opcode is encountered while checking for fixed
897        length instead of just assuming "not fixed length". The items that were
898        rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
899        (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
900        repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
901    
902    8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
903        being incorrectly compiled and would have given unpredicatble results.
904    
905    9.  A possessively repeated subpattern with minimum repeat count greater than
906        one behaved incorrectly. For example, (A){2,}+ behaved as if it was
907        (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
908        the first (A) could occur when it should not.
909    
910    10. Add a cast and remove a redundant test from the code.
911    
912    11. JIT should use pcre_malloc/pcre_free for allocation.
913    
914    12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems
915        best practice nowadays, and helps with cross-compiling. (If the exec_prefix
916        is anything other than /usr, -L is still shown).
917    
918    13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.
919    
920    14. Perl does not support \N without a following name in a [] class; PCRE now
921        also gives an error.
922    
923    15. If a forward reference was repeated with an upper limit of around 2000,
924        it caused the error "internal error: overran compiling workspace". The
925        maximum number of forward references (including repeats) was limited by the
926        internal workspace, and dependent on the LINK_SIZE. The code has been
927        rewritten so that the workspace expands (via pcre_malloc) if necessary, and
928        the default depends on LINK_SIZE. There is a new upper limit (for safety)
929        of around 200,000 forward references. While doing this, I also speeded up
930        the filling in of repeated forward references.
931    
932    16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
933        incorrectly expecting the subject to contain another "a" after the start.
934    
935    17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
936        in the match, the SKIP should be ignored. This was not happening; instead
937        the SKIP was being treated as NOMATCH. For patterns such as
938        /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
939        tested.
940    
941    18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
942        now much more compatible with Perl, in particular in cases where the result
943        is a non-match for a non-anchored pattern. For example, if
944        /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
945        "m", where previously it did not return a name. A side effect of this
946        change is that for partial matches, the last encountered mark name is
947        returned, as for non matches. A number of tests that were previously not
948        Perl-compatible have been moved into the Perl-compatible test files. The
949        refactoring has had the pleasing side effect of removing one argument from
950        the match() function, thus reducing its stack requirements.
951    
952    19. If the /S+ option was used in pcretest to study a pattern using JIT,
953        subsequent uses of /S (without +) incorrectly behaved like /S+.
954    
955    21. Retrieve executable code size support for the JIT compiler and fixing
956        some warnings.
957    
958    22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
959        not work when the shorter character appeared right at the end of the
960        subject string.
961    
962    23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
963        systems.
964    
965    24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
966        output it when the /M option is used in pcretest.
967    
968    25. The CheckMan script was not being included in the distribution. Also, added
969        an explicit "perl" to run Perl scripts from the PrepareRelease script
970        because this is reportedly needed in Windows.
971    
972    26. If study data was being save in a file and studying had not found a set of
973        "starts with" bytes for the pattern, the data written to the file (though
974        never used) was taken from uninitialized memory and so caused valgrind to
975        complain.
976    
977    27. Updated RunTest.bat as provided by Sheri Pierce.
978    
979    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
980    
981    29. Computation of memory usage for the table of capturing group names was
982        giving an unnecessarily large value.
983    
984    
985    Version 8.20 21-Oct-2011
986    ------------------------
987    
988    1.  Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had
989        a POSIX class. After further experiments with Perl, which convinced me that
990        Perl has bugs and confusions, a closing square bracket is no longer allowed
991        in a POSIX name. This bug also affected patterns with classes that started
992        with full stops.
993    
994    2.  If a pattern such as /(a)b|ac/ is matched against "ac", there is no
995        captured substring, but while checking the failing first alternative,
996        substring 1 is temporarily captured. If the output vector supplied to
997        pcre_exec() was not big enough for this capture, the yield of the function
998        was still zero ("insufficient space for captured substrings"). This cannot
999        be totally fixed without adding another stack variable, which seems a lot
1000        of expense for a edge case. However, I have improved the situation in cases
1001        such as /(a)(b)x|abc/ matched against "abc", where the return code
1002        indicates that fewer than the maximum number of slots in the ovector have
1003        been set.
1004    
1005    3.  Related to (2) above: when there are more back references in a pattern than
1006        slots in the output vector, pcre_exec() uses temporary memory during
1007        matching, and copies in the captures as far as possible afterwards. It was
1008        using the entire output vector, but this conflicts with the specification
1009        that only 2/3 is used for passing back captured substrings. Now it uses
1010        only the first 2/3, for compatibility. This is, of course, another edge
1011        case.
1012    
1013    4.  Zoltan Herczeg's just-in-time compiler support has been integrated into the
1014        main code base, and can be used by building with --enable-jit. When this is
1015        done, pcregrep automatically uses it unless --disable-pcregrep-jit or the
1016        runtime --no-jit option is given.
1017    
1018    5.  When the number of matches in a pcre_dfa_exec() run exactly filled the
1019        ovector, the return from the function was zero, implying that there were
1020        other matches that did not fit. The correct "exactly full" value is now
1021        returned.
1022    
1023    6.  If a subpattern that was called recursively or as a subroutine contained
1024        (*PRUNE) or any other control that caused it to give a non-standard return,
1025        invalid errors such as "Error -26 (nested recursion at the same subject
1026        position)" or even infinite loops could occur.
1027    
1028    7.  If a pattern such as /a(*SKIP)c|b(*ACCEPT)|/ was studied, it stopped
1029        computing the minimum length on reaching *ACCEPT, and so ended up with the
1030        wrong value of 1 rather than 0. Further investigation indicates that
1031        computing a minimum subject length in the presence of *ACCEPT is difficult
1032        (think back references, subroutine calls), and so I have changed the code
1033        so that no minimum is registered for a pattern that contains *ACCEPT.
1034    
1035    8.  If (*THEN) was present in the first (true) branch of a conditional group,
1036        it was not handled as intended. [But see 16 below.]
1037    
1038    9.  Replaced RunTest.bat and CMakeLists.txt with improved versions provided by
1039        Sheri Pierce.
1040    
1041    10. A pathological pattern such as /(*ACCEPT)a/ was miscompiled, thinking that
1042        the first byte in a match must be "a".
1043    
1044    11. Change 17 for 8.13 increased the recursion depth for patterns like
1045        /a(?:.)*?a/ drastically. I've improved things by remembering whether a
1046        pattern contains any instances of (*THEN). If it does not, the old
1047        optimizations are restored. It would be nice to do this on a per-group
1048        basis, but at the moment that is not feasible.
1049    
1050    12. In some environments, the output of pcretest -C is CRLF terminated. This
1051        broke RunTest's code that checks for the link size. A single white space
1052        character after the value is now allowed for.
1053    
1054    13. RunTest now checks for the "fr" locale as well as for "fr_FR" and "french".
1055        For "fr", it uses the Windows-specific input and output files.
1056    
1057    14. If (*THEN) appeared in a group that was called recursively or as a
1058        subroutine, it did not work as intended. [But see next item.]
1059    
1060    15. Consider the pattern /A (B(*THEN)C) | D/ where A, B, C, and D are complex
1061        pattern fragments (but not containing any | characters). If A and B are
1062        matched, but there is a failure in C so that it backtracks to (*THEN), PCRE
1063        was behaving differently to Perl. PCRE backtracked into A, but Perl goes to
1064        D. In other words, Perl considers parentheses that do not contain any |
1065        characters to be part of a surrounding alternative, whereas PCRE was
1066        treading (B(*THEN)C) the same as (B(*THEN)C|(*FAIL)) -- which Perl handles
1067        differently. PCRE now behaves in the same way as Perl, except in the case
1068        of subroutine/recursion calls such as (?1) which have in any case always
1069        been different (but PCRE had them first :-).
1070    
1071    16. Related to 15 above: Perl does not treat the | in a conditional group as
1072        creating alternatives. Such a group is treated in the same way as an
1073        ordinary group without any | characters when processing (*THEN). PCRE has
1074        been changed to match Perl's behaviour.
1075    
1076    17. If a user had set PCREGREP_COLO(U)R to something other than 1:31, the
1077        RunGrepTest script failed.
1078    
1079    18. Change 22 for version 13 caused atomic groups to use more stack. This is
1080        inevitable for groups that contain captures, but it can lead to a lot of
1081        stack use in large patterns. The old behaviour has been restored for atomic
1082        groups that do not contain any capturing parentheses.
1083    
1084    19. If the PCRE_NO_START_OPTIMIZE option was set for pcre_compile(), it did not
1085        suppress the check for a minimum subject length at run time. (If it was
1086        given to pcre_exec() or pcre_dfa_exec() it did work.)
1087    
1088    20. Fixed an ASCII-dependent infelicity in pcretest that would have made it
1089        fail to work when decoding hex characters in data strings in EBCDIC
1090        environments.
1091    
1092    21. It appears that in at least one Mac OS environment, the isxdigit() function
1093        is implemented as a macro that evaluates to its argument more than once,
1094        contravening the C 90 Standard (I haven't checked a later standard). There
1095        was an instance in pcretest which caused it to go wrong when processing
1096        \x{...} escapes in subject strings. The has been rewritten to avoid using
1097        things like p++ in the argument of isxdigit().
1098    
1099    
1100    Version 8.13 16-Aug-2011
1101  ------------------------  ------------------------
1102    
1103  1.  The Unicode data tables have been updated to Unicode 6.0.0.  1.  The Unicode data tables have been updated to Unicode 6.0.0.
# Line 98  Version 8.13 02-Aug-2011 Line 1194  Version 8.13 02-Aug-2011
1194      tail recursion to cut down on stack usage. Unfortunately, now that there is      tail recursion to cut down on stack usage. Unfortunately, now that there is
1195      the possibility of (*THEN) occurring in these branches, tail recursion is      the possibility of (*THEN) occurring in these branches, tail recursion is
1196      no longer possible because the return has to be checked for (*THEN). These      no longer possible because the return has to be checked for (*THEN). These
1197      two optimizations have therefore been removed.      two optimizations have therefore been removed. [But see 8.20/11 above.]
1198    
1199  18. If a pattern containing \R was studied, it was assumed that \R always  18. If a pattern containing \R was studied, it was assumed that \R always
1200      matched two bytes, thus causing the minimum subject length to be      matched two bytes, thus causing the minimum subject length to be
# Line 189  Version 8.13 02-Aug-2011 Line 1285  Version 8.13 02-Aug-2011
1285      For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,      For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,
1286      unescaped square brackets may also appear as part of class names. For      unescaped square brackets may also appear as part of class names. For
1287      example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves      example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves
1288      more like Perl.      more like Perl. (But see 8.20/1 above.)
1289    
1290  38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this  38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this
1291      was because it thought it was \N{name}, which is not supported).      was because it thought it was \N{name}, which is not supported).
# Line 224  Version 8.13 02-Aug-2011 Line 1320  Version 8.13 02-Aug-2011
1320      (a) The default value of the buffer size parameter has been increased from      (a) The default value of the buffer size parameter has been increased from
1321          8K to 20K. (The actual buffer used is three times this size.)          8K to 20K. (The actual buffer used is three times this size.)
1322    
1323      (b) The default can be changed by ./configure --with-pcregrep-bufsiz when      (b) The default can be changed by ./configure --with-pcregrep-bufsize when
1324          PCRE is built.          PCRE is built.
1325    
1326      (c) A --buffer-size=n option has been added to pcregrep, to allow the size      (c) A --buffer-size=n option has been added to pcregrep, to allow the size
# Line 245  Version 8.13 02-Aug-2011 Line 1341  Version 8.13 02-Aug-2011
1341  47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a  47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a
1342      complete match instead of a partial match. This bug was dependent on both      complete match instead of a partial match. This bug was dependent on both
1343      the PCRE_UTF8 and PCRE_DOTALL options being set.      the PCRE_UTF8 and PCRE_DOTALL options being set.
1344    
1345  48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the  48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the
1346      starting byte set, because \b was not being ignored.      starting byte set, because \b was not being ignored.
1347    
1348    
1349  Version 8.12 15-Jan-2011  Version 8.12 15-Jan-2011
# Line 900  Version 7.9 11-Apr-09 Line 1996  Version 7.9 11-Apr-09
1996  7.  A pattern that could match an empty string could cause pcregrep to loop; it  7.  A pattern that could match an empty string could cause pcregrep to loop; it
1997      doesn't make sense to accept an empty string match in pcregrep, so I have      doesn't make sense to accept an empty string match in pcregrep, so I have
1998      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
1999      seems to be how GNU grep behaves.      seems to be how GNU grep behaves. [But see later change 40 for release
2000        8.33.]
2001    
2002  8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at  8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
2003      start or after a newline", because the conditional assertion was not being      start or after a newline", because the conditional assertion was not being
# Line 1143  Version 7.7 07-May-08 Line 2240  Version 7.7 07-May-08
2240      containing () gave an internal compiling error instead of "reference to      containing () gave an internal compiling error instead of "reference to
2241      non-existent subpattern". Fortunately, when the pattern did exist, the      non-existent subpattern". Fortunately, when the pattern did exist, the
2242      compiled code was correct. (When scanning forwards to check for the      compiled code was correct. (When scanning forwards to check for the
2243      existencd of the subpattern, it was treating the data ']' as terminating      existence of the subpattern, it was treating the data ']' as terminating
2244      the class, so got the count wrong. When actually compiling, the reference      the class, so got the count wrong. When actually compiling, the reference
2245      was subsequently set up correctly.)      was subsequently set up correctly.)
2246    

Legend:
Removed from v.657  
changed lines
  Added in v.1464

  ViewVC Help
Powered by ViewVC 1.1.5