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

Diff of /code/trunk/ChangeLog

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

revision 505 by ph10, Tue Mar 9 16:50:47 2010 UTC revision 1487 by ph10, Wed Jun 18 17:17:03 2014 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.02 01-Mar-2010  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    14. If a character class started [\Qx]... where x is any character, the class
73        was incorrectly terminated at the ].
74    
75    
76    Version 8.35 04-April-2014
77    --------------------------
78    
79    1.  A new flag is set, when property checks are present in an XCLASS.
80        When this flag is not set, PCRE can perform certain optimizations
81        such as studying these XCLASS-es.
82    
83    2.  The auto-possessification of character sets were improved: a normal
84        and an extended character set can be compared now. Furthermore
85        the JIT compiler optimizes more character set checks.
86    
87    3.  Got rid of some compiler warnings for potentially uninitialized variables
88        that show up only when compiled with -O2.
89    
90    4.  A pattern such as (?=ab\K) that uses \K in an assertion can set the start
91        of a match later then the end of the match. The pcretest program was not
92        handling the case sensibly - it was outputting from the start to the next
93        binary zero. It now reports this situation in a message, and outputs the
94        text from the end to the start.
95    
96    5.  Fast forward search is improved in JIT. Instead of the first three
97        characters, any three characters with fixed position can be searched.
98        Search order: first, last, middle.
99    
100    6.  Improve character range checks in JIT. Characters are read by an inprecise
101        function now, which returns with an unknown value if the character code is
102        above a certain treshold (e.g: 256). The only limitation is that the value
103        must be bigger than the treshold as well. This function is useful, when
104        the characters above the treshold are handled in the same way.
105    
106    7.  The macros whose names start with RAWUCHAR are placeholders for a future
107        mode in which only the bottom 21 bits of 32-bit data items are used. To
108        make this more memorable for those maintaining the code, the names have
109        been changed to start with UCHAR21, and an extensive comment has been added
110        to their definition.
111    
112    8.  Add missing (new) files sljitNativeTILEGX.c and sljitNativeTILEGX-encoder.c
113        to the export list in Makefile.am (they were accidentally omitted from the
114        8.34 tarball).
115    
116    9.  The informational output from pcretest used the phrase "starting byte set"
117        which is inappropriate for the 16-bit and 32-bit libraries. As the output
118        for "first char" and "need char" really means "non-UTF-char", I've changed
119        "byte" to "char", and slightly reworded the output. The documentation about
120        these values has also been (I hope) clarified.
121    
122    10. Another JIT related optimization: use table jumps for selecting the correct
123        backtracking path, when more than four alternatives are present inside a
124        bracket.
125    
126    11. Empty match is not possible, when the minimum length is greater than zero,
127        and there is no \K in the pattern. JIT should avoid empty match checks in
128        such cases.
129    
130    12. In a caseless character class with UCP support, when a character with more
131        than one alternative case was not the first character of a range, not all
132        the alternative cases were added to the class. For example, s and \x{17f}
133        are both alternative cases for S: the class [RST] was handled correctly,
134        but [R-T] was not.
135    
136    13. The configure.ac file always checked for pthread support when JIT was
137        enabled. This is not used in Windows, so I have put this test inside a
138        check for the presence of windows.h (which was already tested for).
139    
140    14. Improve pattern prefix search by a simplified Boyer-Moore algorithm in JIT.
141        The algorithm provides a way to skip certain starting offsets, and usually
142        faster than linear prefix searches.
143    
144    15. Change 13 for 8.20 updated RunTest to check for the 'fr' locale as well
145        as for 'fr_FR' and 'french'. For some reason, however, it then used the
146        Windows-specific input and output files, which have 'french' screwed in.
147        So this could never have worked. One of the problems with locales is that
148        they aren't always the same. I have now updated RunTest so that it checks
149        the output of the locale test (test 3) against three different output
150        files, and it allows the test to pass if any one of them matches. With luck
151        this should make the test pass on some versions of Solaris where it was
152        failing. Because of the uncertainty, the script did not used to stop if
153        test 3 failed; it now does. If further versions of a French locale ever
154        come to light, they can now easily be added.
155    
156    16. If --with-pcregrep-bufsize was given a non-integer value such as "50K",
157        there was a message during ./configure, but it did not stop. This now
158        provokes an error. The invalid example in README has been corrected.
159        If a value less than the minimum is given, the minimum value has always
160        been used, but now a warning is given.
161    
162    17. If --enable-bsr-anycrlf was set, the special 16/32-bit test failed. This
163        was a bug in the test system, which is now fixed. Also, the list of various
164        configurations that are tested for each release did not have one with both
165        16/32 bits and --enable-bar-anycrlf. It now does.
166    
167    18. pcretest was missing "-C bsr" for displaying the \R default setting.
168    
169    19. Little endian PowerPC systems are supported now by the JIT compiler.
170    
171    20. The fast forward newline mechanism could enter to an infinite loop on
172        certain invalid UTF-8 input. Although we don't support these cases
173        this issue can be fixed by a performance optimization.
174    
175    21. Change 33 of 8.34 is not sufficient to ensure stack safety because it does
176        not take account if existing stack usage. There is now a new global
177        variable called pcre_stack_guard that can be set to point to an external
178        function to check stack availability. It is called at the start of
179        processing every parenthesized group.
180    
181    22. A typo in the code meant that in ungreedy mode the max/min qualifier
182        behaved like a min-possessive qualifier, and, for example, /a{1,3}b/U did
183        not match "ab".
184    
185    23. When UTF was disabled, the JIT program reported some incorrect compile
186        errors. These messages are silenced now.
187    
188    24. Experimental support for ARM-64 and MIPS-64 has been added to the JIT
189        compiler.
190    
191    25. Change all the temporary files used in RunGrepTest to be different to those
192        used by RunTest so that the tests can be run simultaneously, for example by
193        "make -j check".
194    
195    
196    Version 8.34 15-December-2013
197    -----------------------------
198    
199    1.  Add pcre[16|32]_jit_free_unused_memory to forcibly free unused JIT
200        executable memory. Patch inspired by Carsten Klein.
201    
202    2.  ./configure --enable-coverage defined SUPPORT_GCOV in config.h, although
203        this macro is never tested and has no effect, because the work to support
204        coverage involves only compiling and linking options and special targets in
205        the Makefile. The comment in config.h implied that defining the macro would
206        enable coverage support, which is totally false. There was also support for
207        setting this macro in the CMake files (my fault, I just copied it from
208        configure). SUPPORT_GCOV has now been removed.
209    
210    3.  Make a small performance improvement in strlen16() and strlen32() in
211        pcretest.
212    
213    4.  Change 36 for 8.33 left some unreachable statements in pcre_exec.c,
214        detected by the Solaris compiler (gcc doesn't seem to be able to diagnose
215        these cases). There was also one in pcretest.c.
216    
217    5.  Cleaned up a "may be uninitialized" compiler warning in pcre_exec.c.
218    
219    6.  In UTF mode, the code for checking whether a group could match an empty
220        string (which is used for indefinitely repeated groups to allow for
221        breaking an infinite loop) was broken when the group contained a repeated
222        negated single-character class with a character that occupied more than one
223        data item and had a minimum repetition of zero (for example, [^\x{100}]* in
224        UTF-8 mode). The effect was undefined: the group might or might not be
225        deemed as matching an empty string, or the program might have crashed.
226    
227    7.  The code for checking whether a group could match an empty string was not
228        recognizing that \h, \H, \v, \V, and \R must match a character.
229    
230    8.  Implemented PCRE_INFO_MATCH_EMPTY, which yields 1 if the pattern can match
231        an empty string. If it can, pcretest shows this in its information output.
232    
233    9.  Fixed two related bugs that applied to Unicode extended grapheme clusters
234        that were repeated with a maximizing qualifier (e.g. \X* or \X{2,5}) when
235        matched by pcre_exec() without using JIT:
236    
237        (a) If the rest of the pattern did not match after a maximal run of
238            grapheme clusters, the code for backing up to try with fewer of them
239            did not always back up over a full grapheme when characters that do not
240            have the modifier quality were involved, e.g. Hangul syllables.
241    
242        (b) If the match point in a subject started with modifier character, and
243            there was no match, the code could incorrectly back up beyond the match
244            point, and potentially beyond the first character in the subject,
245            leading to a segfault or an incorrect match result.
246    
247    10. A conditional group with an assertion condition could lead to PCRE
248        recording an incorrect first data item for a match if no other first data
249        item was recorded. For example, the pattern (?(?=ab)ab) recorded "a" as a
250        first data item, and therefore matched "ca" after "c" instead of at the
251        start.
252    
253    11. Change 40 for 8.33 (allowing pcregrep to find empty strings) showed up a
254        bug that caused the command "echo a | ./pcregrep -M '|a'" to loop.
255    
256    12. The source of pcregrep now includes z/OS-specific code so that it can be
257        compiled for z/OS as part of the special z/OS distribution.
258    
259    13. Added the -T and -TM options to pcretest.
260    
261    14. The code in pcre_compile.c for creating the table of named capturing groups
262        has been refactored. Instead of creating the table dynamically during the
263        actual compiling pass, the information is remembered during the pre-compile
264        pass (on the stack unless there are more than 20 named groups, in which
265        case malloc() is used) and the whole table is created before the actual
266        compile happens. This has simplified the code (it is now nearly 150 lines
267        shorter) and prepared the way for better handling of references to groups
268        with duplicate names.
269    
270    15. A back reference to a named subpattern when there is more than one of the
271        same name now checks them in the order in which they appear in the pattern.
272        The first one that is set is used for the reference. Previously only the
273        first one was inspected. This change makes PCRE more compatible with Perl.
274    
275    16. Unicode character properties were updated from Unicode 6.3.0.
276    
277    17. The compile-time code for auto-possessification has been refactored, based
278        on a patch by Zoltan Herczeg. It now happens after instead of during
279        compilation. The code is cleaner, and more cases are handled. The option
280        PCRE_NO_AUTO_POSSESS is added for testing purposes, and the -O and /O
281        options in pcretest are provided to set it. It can also be set by
282        (*NO_AUTO_POSSESS) at the start of a pattern.
283    
284    18. The character VT has been added to the default ("C" locale) set of
285        characters that match \s and are generally treated as white space,
286        following this same change in Perl 5.18. There is now no difference between
287        "Perl space" and "POSIX space". Whether VT is treated as white space in
288        other locales depends on the locale.
289    
290    19. The code for checking named groups as conditions, either for being set or
291        for being recursed, has been refactored (this is related to 14 and 15
292        above). Processing unduplicated named groups should now be as fast at
293        numerical groups, and processing duplicated groups should be faster than
294        before.
295    
296    20. Two patches to the CMake build system, by Alexander Barkov:
297    
298          (1) Replace the "source" command by "." in CMakeLists.txt because
299              "source" is a bash-ism.
300    
301          (2) Add missing HAVE_STDINT_H and HAVE_INTTYPES_H to config-cmake.h.in;
302              without these the CMake build does not work on Solaris.
303    
304    21. Perl has changed its handling of \8 and \9. If there is no previously
305        encountered capturing group of those numbers, they are treated as the
306        literal characters 8 and 9 instead of a binary zero followed by the
307        literals. PCRE now does the same.
308    
309    22. Following Perl, added \o{} to specify codepoints in octal, making it
310        possible to specify values greater than 0777 and also making them
311        unambiguous.
312    
313    23. Perl now gives an error for missing closing braces after \x{... instead of
314        treating the string as literal. PCRE now does the same.
315    
316    24. RunTest used to grumble if an inappropriate test was selected explicitly,
317        but just skip it when running all tests. This make it awkward to run ranges
318        of tests when one of them was inappropriate. Now it just skips any
319        inappropriate tests, as it always did when running all tests.
320    
321    25. If PCRE_AUTO_CALLOUT and PCRE_UCP were set for a pattern that contained
322        character types such as \d or \w, too many callouts were inserted, and the
323        data that they returned was rubbish.
324    
325    26. In UCP mode, \s was not matching two of the characters that Perl matches,
326        namely NEL (U+0085) and MONGOLIAN VOWEL SEPARATOR (U+180E), though they
327        were matched by \h. The code has now been refactored so that the lists of
328        the horizontal and vertical whitespace characters used for \h and \v (which
329        are defined only in one place) are now also used for \s.
330    
331    27. Add JIT support for the 64 bit TileGX architecture.
332        Patch by Jiong Wang (Tilera Corporation).
333    
334    28. Possessive quantifiers for classes (both explicit and automatically
335        generated) now use special opcodes instead of wrapping in ONCE brackets.
336    
337    29. Whereas an item such as A{4}+ ignored the possessivenes of the quantifier
338        (because it's meaningless), this was not happening when PCRE_CASELESS was
339        set. Not wrong, but inefficient.
340    
341    30. Updated perltest.pl to add /u (force Unicode mode) when /W (use Unicode
342        properties for \w, \d, etc) is present in a test regex. Otherwise if the
343        test contains no characters greater than 255, Perl doesn't realise it
344        should be using Unicode semantics.
345    
346    31. Upgraded the handling of the POSIX classes [:graph:], [:print:], and
347        [:punct:] when PCRE_UCP is set so as to include the same characters as Perl
348        does in Unicode mode.
349    
350    32. Added the "forbid" facility to pcretest so that putting tests into the
351        wrong test files can sometimes be quickly detected.
352    
353    33. There is now a limit (default 250) on the depth of nesting of parentheses.
354        This limit is imposed to control the amount of system stack used at compile
355        time. It can be changed at build time by --with-parens-nest-limit=xxx or
356        the equivalent in CMake.
357    
358    34. Character classes such as [A-\d] or [a-[:digit:]] now cause compile-time
359        errors. Perl warns for these when in warning mode, but PCRE has no facility
360        for giving warnings.
361    
362    35. Change 34 for 8.13 allowed quantifiers on assertions, because Perl does.
363        However, this was not working for (?!) because it is optimized to (*FAIL),
364        for which PCRE does not allow quantifiers. The optimization is now disabled
365        when a quantifier follows (?!). I can't see any use for this, but it makes
366        things uniform.
367    
368    36. Perl no longer allows group names to start with digits, so I have made this
369        change also in PCRE. It simplifies the code a bit.
370    
371    37. In extended mode, Perl ignores spaces before a + that indicates a
372        possessive quantifier. PCRE allowed a space before the quantifier, but not
373        before the possessive +. It now does.
374    
375    38. The use of \K (reset reported match start) within a repeated possessive
376        group such as (a\Kb)*+ was not working.
377    
378    40. Document that the same character tables must be used at compile time and
379        run time, and that the facility to pass tables to pcre_exec() and
380        pcre_dfa_exec() is for use only with saved/restored patterns.
381    
382    41. Applied Jeff Trawick's patch CMakeLists.txt, which "provides two new
383        features for Builds with MSVC:
384    
385        1. Support pcre.rc and/or pcreposix.rc (as is already done for MinGW
386           builds). The .rc files can be used to set FileDescription and many other
387           attributes.
388    
389        2. Add an option (-DINSTALL_MSVC_PDB) to enable installation of .pdb files.
390           This allows higher-level build scripts which want .pdb files to avoid
391           hard-coding the exact files needed."
392    
393    42. Added support for [[:<:]] and [[:>:]] as used in the BSD POSIX library to
394        mean "start of word" and "end of word", respectively, as a transition aid.
395    
396    43. A minimizing repeat of a class containing codepoints greater than 255 in
397        non-UTF 16-bit or 32-bit modes caused an internal error when PCRE was
398        compiled to use the heap for recursion.
399    
400    44. Got rid of some compiler warnings for unused variables when UTF but not UCP
401        is configured.
402    
403    
404    Version 8.33 28-May-2013
405    ------------------------
406    
407    1.  Added 'U' to some constants that are compared to unsigned integers, to
408        avoid compiler signed/unsigned warnings. Added (int) casts to unsigned
409        variables that are added to signed variables, to ensure the result is
410        signed and can be negated.
411    
412    2.  Applied patch by Daniel Richard G for quashing MSVC warnings to the
413        CMake config files.
414    
415    3.  Revise the creation of config.h.generic so that all boolean macros are
416        #undefined, whereas non-boolean macros are #ifndef/#endif-ed. This makes
417        overriding via -D on the command line possible.
418    
419    4.  Changing the definition of the variable "op" in pcre_exec.c from pcre_uchar
420        to unsigned int is reported to make a quite noticeable speed difference in
421        a specific Windows environment. Testing on Linux did also appear to show
422        some benefit (and it is clearly not harmful). Also fixed the definition of
423        Xop which should be unsigned.
424    
425    5.  Related to (4), changing the definition of the intermediate variable cc
426        in repeated character loops from pcre_uchar to pcre_uint32 also gave speed
427        improvements.
428    
429    6.  Fix forward search in JIT when link size is 3 or greater. Also removed some
430        unnecessary spaces.
431    
432    7.  Adjust autogen.sh and configure.ac to lose warnings given by automake 1.12
433        and later.
434    
435    8.  Fix two buffer over read issues in 16 and 32 bit modes. Affects JIT only.
436    
437    9.  Optimizing fast_forward_start_bits in JIT.
438    
439    10. Adding support for callouts in JIT, and fixing some issues revealed
440        during this work. Namely:
441    
442        (a) Unoptimized capturing brackets incorrectly reset on backtrack.
443    
444        (b) Minimum length was not checked before the matching is started.
445    
446    11. The value of capture_last that is passed to callouts was incorrect in some
447        cases when there was a capture on one path that was subsequently abandoned
448        after a backtrack. Also, the capture_last value is now reset after a
449        recursion, since all captures are also reset in this case.
450    
451    12. The interpreter no longer returns the "too many substrings" error in the
452        case when an overflowing capture is in a branch that is subsequently
453        abandoned after a backtrack.
454    
455    13. In the pathological case when an offset vector of size 2 is used, pcretest
456        now prints out the matched string after a yield of 0 or 1.
457    
458    14. Inlining subpatterns in recursions, when certain conditions are fulfilled.
459        Only supported by the JIT compiler at the moment.
460    
461    15. JIT compiler now supports 32 bit Macs thanks to Lawrence Velazquez.
462    
463    16. Partial matches now set offsets[2] to the "bumpalong" value, that is, the
464        offset of the starting point of the matching process, provided the offsets
465        vector is large enough.
466    
467    17. The \A escape now records a lookbehind value of 1, though its execution
468        does not actually inspect the previous character. This is to ensure that,
469        in partial multi-segment matching, at least one character from the old
470        segment is retained when a new segment is processed. Otherwise, if there
471        are no lookbehinds in the pattern, \A might match incorrectly at the start
472        of a new segment.
473    
474    18. Added some #ifdef __VMS code into pcretest.c to help VMS implementations.
475    
476    19. Redefined some pcre_uchar variables in pcre_exec.c as pcre_uint32; this
477        gives some modest performance improvement in 8-bit mode.
478    
479    20. Added the PCRE-specific property \p{Xuc} for matching characters that can
480        be expressed in certain programming languages using Universal Character
481        Names.
482    
483    21. Unicode validation has been updated in the light of Unicode Corrigendum #9,
484        which points out that "non characters" are not "characters that may not
485        appear in Unicode strings" but rather "characters that are reserved for
486        internal use and have only local meaning".
487    
488    22. When a pattern was compiled with automatic callouts (PCRE_AUTO_CALLOUT) and
489        there was a conditional group that depended on an assertion, if the
490        assertion was false, the callout that immediately followed the alternation
491        in the condition was skipped when pcre_exec() was used for matching.
492    
493    23. Allow an explicit callout to be inserted before an assertion that is the
494        condition for a conditional group, for compatibility with automatic
495        callouts, which always insert a callout at this point.
496    
497    24. In 8.31, (*COMMIT) was confined to within a recursive subpattern. Perl also
498        confines (*SKIP) and (*PRUNE) in the same way, and this has now been done.
499    
500    25. (*PRUNE) is now supported by the JIT compiler.
501    
502    26. Fix infinite loop when /(?<=(*SKIP)ac)a/ is matched against aa.
503    
504    27. Fix the case where there are two or more SKIPs with arguments that may be
505        ignored.
506    
507    28. (*SKIP) is now supported by the JIT compiler.
508    
509    29. (*THEN) is now supported by the JIT compiler.
510    
511    30. Update RunTest with additional test selector options.
512    
513    31. The way PCRE handles backtracking verbs has been changed in two ways.
514    
515        (1) Previously, in something like (*COMMIT)(*SKIP), COMMIT would override
516        SKIP. Now, PCRE acts on whichever backtracking verb is reached first by
517        backtracking. In some cases this makes it more Perl-compatible, but Perl's
518        rather obscure rules do not always do the same thing.
519    
520        (2) Previously, backtracking verbs were confined within assertions. This is
521        no longer the case for positive assertions, except for (*ACCEPT). Again,
522        this sometimes improves Perl compatibility, and sometimes does not.
523    
524    32. A number of tests that were in test 2 because Perl did things differently
525        have been moved to test 1, because either Perl or PCRE has changed, and
526        these tests are now compatible.
527    
528    32. Backtracking control verbs are now handled in the same way in JIT and
529        interpreter.
530    
531    33. An opening parenthesis in a MARK/PRUNE/SKIP/THEN name in a pattern that
532        contained a forward subroutine reference caused a compile error.
533    
534    34. Auto-detect and optimize limited repetitions in JIT.
535    
536    35. Implement PCRE_NEVER_UTF to lock out the use of UTF, in particular,
537        blocking (*UTF) etc.
538    
539    36. In the interpreter, maximizing pattern repetitions for characters and
540        character types now use tail recursion, which reduces stack usage.
541    
542    37. The value of the max lookbehind was not correctly preserved if a compiled
543        and saved regex was reloaded on a host of different endianness.
544    
545    38. Implemented (*LIMIT_MATCH) and (*LIMIT_RECURSION). As part of the extension
546        of the compiled pattern block, expand the flags field from 16 to 32 bits
547        because it was almost full.
548    
549    39. Try madvise first before posix_madvise.
550    
551    40. Change 7 for PCRE 7.9 made it impossible for pcregrep to find empty lines
552        with a pattern such as ^$. It has taken 4 years for anybody to notice! The
553        original change locked out all matches of empty strings. This has been
554        changed so that one match of an empty string per line is recognized.
555        Subsequent searches on the same line (for colouring or for --only-matching,
556        for example) do not recognize empty strings.
557    
558    41. Applied a user patch to fix a number of spelling mistakes in comments.
559    
560    42. Data lines longer than 65536 caused pcretest to crash.
561    
562    43. Clarified the data type for length and startoffset arguments for pcre_exec
563        and pcre_dfa_exec in the function-specific man pages, where they were
564        explicitly stated to be in bytes, never having been updated. I also added
565        some clarification to the pcreapi man page.
566    
567    44. A call to pcre_dfa_exec() with an output vector size less than 2 caused
568        a segmentation fault.
569    
570    
571    Version 8.32 30-November-2012
572    -----------------------------
573    
574    1.  Improved JIT compiler optimizations for first character search and single
575        character iterators.
576    
577    2.  Supporting IBM XL C compilers for PPC architectures in the JIT compiler.
578        Patch by Daniel Richard G.
579    
580    3.  Single character iterator optimizations in the JIT compiler.
581    
582    4.  Improved JIT compiler optimizations for character ranges.
583    
584    5.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.
585        Reported by Giuseppe D'Angelo.
586    
587    6.  The PCRE_STARTLINE bit, indicating that a match can occur only at the start
588        of a line, was being set incorrectly in cases where .* appeared inside
589        atomic brackets at the start of a pattern, or where there was a subsequent
590        *PRUNE or *SKIP.
591    
592    7.  Improved instruction cache flush for POWER/PowerPC.
593        Patch by Daniel Richard G.
594    
595    8.  Fixed a number of issues in pcregrep, making it more compatible with GNU
596        grep:
597    
598        (a) There is now no limit to the number of patterns to be matched.
599    
600        (b) An error is given if a pattern is too long.
601    
602        (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir
603            are now supported.
604    
605        (d) --exclude-from and --include-from (multiple use) have been added.
606    
607        (e) Exclusions and inclusions now apply to all files and directories, not
608            just to those obtained from scanning a directory recursively.
609    
610        (f) Multiple uses of -f and --file-list are now supported.
611    
612        (g) In a Windows environment, the default for -d has been changed from
613            "read" (the GNU grep default) to "skip", because otherwise the presence
614            of a directory in the file list provokes an error.
615    
616        (h) The documentation has been revised and clarified in places.
617    
618    9.  Improve the matching speed of capturing brackets.
619    
620    10. Changed the meaning of \X so that it now matches a Unicode extended
621        grapheme cluster.
622    
623    11. Patch by Daniel Richard G to the autoconf files to add a macro for sorting
624        out POSIX threads when JIT support is configured.
625    
626    12. Added support for PCRE_STUDY_EXTRA_NEEDED.
627    
628    13. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg
629        structure could go wrong in environments where size_t is not the same size
630        as int.
631    
632    14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be
633        set.
634    
635    15. The EBCDIC support had decayed; later updates to the code had included
636        explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a
637        general tidy up of EBCDIC-related issues, and the documentation was also
638        not quite right. There is now a test that can be run on ASCII systems to
639        check some of the EBCDIC-related things (but is it not a full test).
640    
641    16. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting
642        in a small tidy to the code.
643    
644    17. Fix JIT tests when UTF is disabled and both 8 and 16 bit mode are enabled.
645    
646    18. If the --only-matching (-o) option in pcregrep is specified multiple
647        times, each one causes appropriate output. For example, -o1 -o2 outputs the
648        substrings matched by the 1st and 2nd capturing parentheses. A separating
649        string can be specified by --om-separator (default empty).
650    
651    19. Improving the first n character searches.
652    
653    20. Turn case lists for horizontal and vertical white space into macros so that
654        they are defined only once.
655    
656    21. This set of changes together give more compatible Unicode case-folding
657        behaviour for characters that have more than one other case when UCP
658        support is available.
659    
660        (a) The Unicode property table now has offsets into a new table of sets of
661            three or more characters that are case-equivalent. The MultiStage2.py
662            script that generates these tables (the pcre_ucd.c file) now scans
663            CaseFolding.txt instead of UnicodeData.txt for character case
664            information.
665    
666        (b) The code for adding characters or ranges of characters to a character
667            class has been abstracted into a generalized function that also handles
668            case-independence. In UTF-mode with UCP support, this uses the new data
669            to handle characters with more than one other case.
670    
671        (c) A bug that is fixed as a result of (b) is that codepoints less than 256
672            whose other case is greater than 256 are now correctly matched
673            caselessly. Previously, the high codepoint matched the low one, but not
674            vice versa.
675    
676        (d) The processing of \h, \H, \v, and \ in character classes now makes use
677            of the new class addition function, using character lists defined as
678            macros alongside the case definitions of 20 above.
679    
680        (e) Caseless back references now work with characters that have more than
681            one other case.
682    
683        (f) General caseless matching of characters with more than one other case
684            is supported.
685    
686    22. Unicode character properties were updated from Unicode 6.2.0
687    
688    23. Improved CMake support under Windows. Patch by Daniel Richard G.
689    
690    24. Add support for 32-bit character strings, and UTF-32
691    
692    25. Major JIT compiler update (code refactoring and bugfixing).
693        Experimental Sparc 32 support is added.
694    
695    26. Applied a modified version of Daniel Richard G's patch to create
696        pcre.h.generic and config.h.generic by "make" instead of in the
697        PrepareRelease script.
698    
699    27. Added a definition for CHAR_NULL (helpful for the z/OS port), and use it in
700        pcre_compile.c when checking for a zero character.
701    
702    28. Introducing a native interface for JIT. Through this interface, the compiled
703        machine code can be directly executed. The purpose of this interface is to
704        provide fast pattern matching, so several sanity checks are not performed.
705        However, feature tests are still performed. The new interface provides
706        1.4x speedup compared to the old one.
707    
708    29. If pcre_exec() or pcre_dfa_exec() was called with a negative value for
709        the subject string length, the error given was PCRE_ERROR_BADOFFSET, which
710        was confusing. There is now a new error PCRE_ERROR_BADLENGTH for this case.
711    
712    30. In 8-bit UTF-8 mode, pcretest failed to give an error for data codepoints
713        greater than 0x7fffffff (which cannot be represented in UTF-8, even under
714        the "old" RFC 2279). Instead, it ended up passing a negative length to
715        pcre_exec().
716    
717    31. Add support for GCC's visibility feature to hide internal functions.
718    
719    32. Running "pcretest -C pcre8" or "pcretest -C pcre16" gave a spurious error
720        "unknown -C option" after outputting 0 or 1.
721    
722    33. There is now support for generating a code coverage report for the test
723        suite in environments where gcc is the compiler and lcov is installed. This
724        is mainly for the benefit of the developers.
725    
726    34. If PCRE is built with --enable-valgrind, certain memory regions are marked
727        unaddressable using valgrind annotations, allowing valgrind to detect
728        invalid memory accesses. This is mainly for the benefit of the developers.
729    
730    25. (*UTF) can now be used to start a pattern in any of the three libraries.
731    
732    26. Give configure error if --enable-cpp but no C++ compiler found.
733    
734    
735    Version 8.31 06-July-2012
736    -------------------------
737    
738    1.  Fixing a wrong JIT test case and some compiler warnings.
739    
740    2.  Removed a bashism from the RunTest script.
741    
742    3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied
743        to unsigned type, result still unsigned" that was given by an MS compiler
744        on encountering the code "-sizeof(xxx)".
745    
746    4.  Partial matching support is added to the JIT compiler.
747    
748    5.  Fixed several bugs concerned with partial matching of items that consist
749        of more than one character:
750    
751        (a) /^(..)\1/ did not partially match "aba" because checking references was
752            done on an "all or nothing" basis. This also applied to repeated
753            references.
754    
755        (b) \R did not give a hard partial match if \r was found at the end of the
756            subject.
757    
758        (c) \X did not give a hard partial match after matching one or more
759            characters at the end of the subject.
760    
761        (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize
762            a partial match for the string "\r".
763    
764        (e) When newline was set to CRLF, the metacharacter "." did not recognize
765            a partial match for a CR character at the end of the subject string.
766    
767    6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when
768        running pcretest, the text "(JIT)" added to the output whenever JIT is
769        actually used to run the match.
770    
771    7.  Individual JIT compile options can be set in pcretest by following -s+[+]
772        or /S+[+] with a digit between 1 and 7.
773    
774    8.  OP_NOT now supports any UTF character not just single-byte ones.
775    
776    9.  (*MARK) control verb is now supported by the JIT compiler.
777    
778    10. The command "./RunTest list" lists the available tests without actually
779        running any of them. (Because I keep forgetting what they all are.)
780    
781    11. Add PCRE_INFO_MAXLOOKBEHIND.
782    
783    12. Applied a (slightly modified) user-supplied patch that improves performance
784        when the heap is used for recursion (compiled with --disable-stack-for-
785        recursion). Instead of malloc and free for each heap frame each time a
786        logical recursion happens, frames are retained on a chain and re-used where
787        possible. This sometimes gives as much as 30% improvement.
788    
789    13. As documented, (*COMMIT) is now confined to within a recursive subpattern
790        call.
791    
792    14. As documented, (*COMMIT) is now confined to within a positive assertion.
793    
794    15. It is now possible to link pcretest with libedit as an alternative to
795        libreadline.
796    
797    16. (*COMMIT) control verb is now supported by the JIT compiler.
798    
799    17. The Unicode data tables have been updated to Unicode 6.1.0.
800    
801    18. Added --file-list option to pcregrep.
802    
803    19. Added binary file support to pcregrep, including the -a, --binary-files,
804        -I, and --text options.
805    
806    20. The madvise function is renamed for posix_madvise for QNX compatibility
807        reasons. Fixed by Giuseppe D'Angelo.
808    
809    21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
810    
811    22. Changed the option for creating symbolic links for 16-bit man pages from
812        -s to -sf so that re-installing does not cause issues.
813    
814    23. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it.
815    
816    24. Fixed a very old bug in pcretest that caused errors with restarted DFA
817        matches in certain environments (the workspace was not being correctly
818        retained). Also added to pcre_dfa_exec() a simple plausibility check on
819        some of the workspace data at the beginning of a restart.
820    
821    25. \s*\R was auto-possessifying the \s* when it should not, whereas \S*\R
822        was not doing so when it should - probably a typo introduced by SVN 528
823        (change 8.10/14).
824    
825    26. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the
826        \w+ when the character tables indicated that \x{c4} was a word character.
827        There were several related cases, all because the tests for doing a table
828        lookup were testing for characters less than 127 instead of 255.
829    
830    27. If a pattern contains capturing parentheses that are not used in a match,
831        their slots in the ovector are set to -1. For those that are higher than
832        any matched groups, this happens at the end of processing. In the case when
833        there were back references that the ovector was too small to contain
834        (causing temporary malloc'd memory to be used during matching), and the
835        highest capturing number was not used, memory off the end of the ovector
836        was incorrectly being set to -1. (It was using the size of the temporary
837        memory instead of the true size.)
838    
839    28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
840        ovector size, it uses memory at the end of the block that it has got.
841    
842    29. Check for an overlong MARK name and give an error at compile time. The
843        limit is 255 for the 8-bit library and 65535 for the 16-bit library.
844    
845    30. JIT compiler update.
846    
847    31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
848        Rill for the patch.
849    
850    32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
851    
852    33. Variable renamings in the PCRE-JIT compiler. No functionality change.
853    
854    34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
855        SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
856        was enabled.
857    
858    35. Improve JIT code generation for greedy plus quantifier.
859    
860    36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
861        1 to "aa" instead of to an empty string. The bug affected repeated groups
862        that could potentially match an empty string.
863    
864    37. Optimizing single character iterators in JIT.
865    
866    38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
867        the same checks as \x{...} characters in non-JavaScript mode. Specifically,
868        codepoints that are too big for the mode are faulted, and in a UTF mode,
869        disallowed codepoints are also faulted.
870    
871    39. If PCRE was compiled with UTF support, in three places in the DFA
872        matcher there was code that should only have been obeyed in UTF mode, but
873        was being obeyed unconditionally. In 8-bit mode this could cause incorrect
874        processing when bytes with values greater than 127 were present. In 16-bit
875        mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
876        both cases the values are those that cannot be the first data item in a UTF
877        character. The three items that might have provoked this were recursions,
878        possessively repeated groups, and atomic groups.
879    
880    40. Ensure that libpcre is explicitly listed in the link commands for pcretest
881        and pcregrep, because some OS require shared objects to be explicitly
882        passed to ld, causing the link step to fail if they are not.
883    
884    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
885        mode, patterns that started with \h* or \R* might be incorrectly matched.
886    
887    
888    Version 8.30 04-February-2012
889    -----------------------------
890    
891    1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
892        name is defined in ctype.h.
893    
894    2.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
895        only in quite long subpatterns.
896    
897    3.  Removed the function pcre_info(), which has been obsolete and deprecated
898        since it was replaced by pcre_fullinfo() in February 2000.
899    
900    4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
901        match a (*MARK), and the match failed at the start of the subject, a
902        reference to memory before the start of the subject could occur. This bug
903        was introduced by fix 17 of release 8.21.
904    
905    5.  A reference to an unset group with zero minimum repetition was giving
906        totally wrong answers (in non-JavaScript-compatibility mode). For example,
907        /(another)?(\1?)test/ matched against "hello world test". This bug was
908        introduced in release 8.13.
909    
910    6.  Add support for 16-bit character strings (a large amount of work involving
911        many changes and refactorings).
912    
913    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
914        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
915        from a file.
916    
917    8.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
918        rounding is not applied in this particular case).
919    
920    9.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
921        if they appear, or are escaped, in patterns.
922    
923    10. Get rid of a number of -Wunused-but-set-variable warnings.
924    
925    11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
926        "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
927        Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
928        also returns the mark "x". This bug applied to capturing parentheses,
929        non-capturing parentheses, and atomic parentheses. It also applied to some
930        assertions.
931    
932    12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
933        information out of configure.ac instead of relying on pcre.h.generic, which
934        is not stored in the repository.
935    
936    13. Applied Dmitry V. Levin's patch for a more portable method for linking with
937        -lreadline.
938    
939    14. ZH added PCRE_CONFIG_JITTARGET; added its output to pcretest -C.
940    
941    15. Applied Graycode's patch to put the top-level frame on the stack rather
942        than the heap when not using the stack for recursion. This gives a
943        performance improvement in many cases when recursion is not deep.
944    
945    16. Experimental code added to "pcretest -C" to output the stack frame size.
946    
947    
948    Version 8.21 12-Dec-2011
949    ------------------------
950    
951    1.  Updating the JIT compiler.
952    
953    2.  JIT compiler now supports OP_NCREF, OP_RREF and OP_NRREF. New test cases
954        are added as well.
955    
956    3.  Fix cache-flush issue on PowerPC (It is still an experimental JIT port).
957        PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before
958        calling _pcre_jit_exec. Some extra comments are added.
959    
960    4.  (*MARK) settings inside atomic groups that do not contain any capturing
961        parentheses, for example, (?>a(*:m)), were not being passed out. This bug
962        was introduced by change 18 for 8.20.
963    
964    5.  Supporting of \x, \U and \u in JavaScript compatibility mode based on the
965        ECMA-262 standard.
966    
967    6.  Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were
968        erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
969        This bug was probably introduced by change 9 of 8.13.
970    
971    7.  While fixing 6 above, I noticed that a number of other items were being
972        incorrectly rejected as "not fixed length". This arose partly because newer
973        opcodes had not been added to the fixed-length checking code. I have (a)
974        corrected the bug and added tests for these items, and (b) arranged for an
975        error to occur if an unknown opcode is encountered while checking for fixed
976        length instead of just assuming "not fixed length". The items that were
977        rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
978        (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
979        repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
980    
981    8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
982        being incorrectly compiled and would have given unpredicatble results.
983    
984    9.  A possessively repeated subpattern with minimum repeat count greater than
985        one behaved incorrectly. For example, (A){2,}+ behaved as if it was
986        (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
987        the first (A) could occur when it should not.
988    
989    10. Add a cast and remove a redundant test from the code.
990    
991    11. JIT should use pcre_malloc/pcre_free for allocation.
992    
993    12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems
994        best practice nowadays, and helps with cross-compiling. (If the exec_prefix
995        is anything other than /usr, -L is still shown).
996    
997    13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.
998    
999    14. Perl does not support \N without a following name in a [] class; PCRE now
1000        also gives an error.
1001    
1002    15. If a forward reference was repeated with an upper limit of around 2000,
1003        it caused the error "internal error: overran compiling workspace". The
1004        maximum number of forward references (including repeats) was limited by the
1005        internal workspace, and dependent on the LINK_SIZE. The code has been
1006        rewritten so that the workspace expands (via pcre_malloc) if necessary, and
1007        the default depends on LINK_SIZE. There is a new upper limit (for safety)
1008        of around 200,000 forward references. While doing this, I also speeded up
1009        the filling in of repeated forward references.
1010    
1011    16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
1012        incorrectly expecting the subject to contain another "a" after the start.
1013    
1014    17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
1015        in the match, the SKIP should be ignored. This was not happening; instead
1016        the SKIP was being treated as NOMATCH. For patterns such as
1017        /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
1018        tested.
1019    
1020    18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
1021        now much more compatible with Perl, in particular in cases where the result
1022        is a non-match for a non-anchored pattern. For example, if
1023        /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
1024        "m", where previously it did not return a name. A side effect of this
1025        change is that for partial matches, the last encountered mark name is
1026        returned, as for non matches. A number of tests that were previously not
1027        Perl-compatible have been moved into the Perl-compatible test files. The
1028        refactoring has had the pleasing side effect of removing one argument from
1029        the match() function, thus reducing its stack requirements.
1030    
1031    19. If the /S+ option was used in pcretest to study a pattern using JIT,
1032        subsequent uses of /S (without +) incorrectly behaved like /S+.
1033    
1034    21. Retrieve executable code size support for the JIT compiler and fixing
1035        some warnings.
1036    
1037    22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
1038        not work when the shorter character appeared right at the end of the
1039        subject string.
1040    
1041    23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
1042        systems.
1043    
1044    24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
1045        output it when the /M option is used in pcretest.
1046    
1047    25. The CheckMan script was not being included in the distribution. Also, added
1048        an explicit "perl" to run Perl scripts from the PrepareRelease script
1049        because this is reportedly needed in Windows.
1050    
1051    26. If study data was being save in a file and studying had not found a set of
1052        "starts with" bytes for the pattern, the data written to the file (though
1053        never used) was taken from uninitialized memory and so caused valgrind to
1054        complain.
1055    
1056    27. Updated RunTest.bat as provided by Sheri Pierce.
1057    
1058    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
1059    
1060    29. Computation of memory usage for the table of capturing group names was
1061        giving an unnecessarily large value.
1062    
1063    
1064    Version 8.20 21-Oct-2011
1065    ------------------------
1066    
1067    1.  Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had
1068        a POSIX class. After further experiments with Perl, which convinced me that
1069        Perl has bugs and confusions, a closing square bracket is no longer allowed
1070        in a POSIX name. This bug also affected patterns with classes that started
1071        with full stops.
1072    
1073    2.  If a pattern such as /(a)b|ac/ is matched against "ac", there is no
1074        captured substring, but while checking the failing first alternative,
1075        substring 1 is temporarily captured. If the output vector supplied to
1076        pcre_exec() was not big enough for this capture, the yield of the function
1077        was still zero ("insufficient space for captured substrings"). This cannot
1078        be totally fixed without adding another stack variable, which seems a lot
1079        of expense for a edge case. However, I have improved the situation in cases
1080        such as /(a)(b)x|abc/ matched against "abc", where the return code
1081        indicates that fewer than the maximum number of slots in the ovector have
1082        been set.
1083    
1084    3.  Related to (2) above: when there are more back references in a pattern than
1085        slots in the output vector, pcre_exec() uses temporary memory during
1086        matching, and copies in the captures as far as possible afterwards. It was
1087        using the entire output vector, but this conflicts with the specification
1088        that only 2/3 is used for passing back captured substrings. Now it uses
1089        only the first 2/3, for compatibility. This is, of course, another edge
1090        case.
1091    
1092    4.  Zoltan Herczeg's just-in-time compiler support has been integrated into the
1093        main code base, and can be used by building with --enable-jit. When this is
1094        done, pcregrep automatically uses it unless --disable-pcregrep-jit or the
1095        runtime --no-jit option is given.
1096    
1097    5.  When the number of matches in a pcre_dfa_exec() run exactly filled the
1098        ovector, the return from the function was zero, implying that there were
1099        other matches that did not fit. The correct "exactly full" value is now
1100        returned.
1101    
1102    6.  If a subpattern that was called recursively or as a subroutine contained
1103        (*PRUNE) or any other control that caused it to give a non-standard return,
1104        invalid errors such as "Error -26 (nested recursion at the same subject
1105        position)" or even infinite loops could occur.
1106    
1107    7.  If a pattern such as /a(*SKIP)c|b(*ACCEPT)|/ was studied, it stopped
1108        computing the minimum length on reaching *ACCEPT, and so ended up with the
1109        wrong value of 1 rather than 0. Further investigation indicates that
1110        computing a minimum subject length in the presence of *ACCEPT is difficult
1111        (think back references, subroutine calls), and so I have changed the code
1112        so that no minimum is registered for a pattern that contains *ACCEPT.
1113    
1114    8.  If (*THEN) was present in the first (true) branch of a conditional group,
1115        it was not handled as intended. [But see 16 below.]
1116    
1117    9.  Replaced RunTest.bat and CMakeLists.txt with improved versions provided by
1118        Sheri Pierce.
1119    
1120    10. A pathological pattern such as /(*ACCEPT)a/ was miscompiled, thinking that
1121        the first byte in a match must be "a".
1122    
1123    11. Change 17 for 8.13 increased the recursion depth for patterns like
1124        /a(?:.)*?a/ drastically. I've improved things by remembering whether a
1125        pattern contains any instances of (*THEN). If it does not, the old
1126        optimizations are restored. It would be nice to do this on a per-group
1127        basis, but at the moment that is not feasible.
1128    
1129    12. In some environments, the output of pcretest -C is CRLF terminated. This
1130        broke RunTest's code that checks for the link size. A single white space
1131        character after the value is now allowed for.
1132    
1133    13. RunTest now checks for the "fr" locale as well as for "fr_FR" and "french".
1134        For "fr", it uses the Windows-specific input and output files.
1135    
1136    14. If (*THEN) appeared in a group that was called recursively or as a
1137        subroutine, it did not work as intended. [But see next item.]
1138    
1139    15. Consider the pattern /A (B(*THEN)C) | D/ where A, B, C, and D are complex
1140        pattern fragments (but not containing any | characters). If A and B are
1141        matched, but there is a failure in C so that it backtracks to (*THEN), PCRE
1142        was behaving differently to Perl. PCRE backtracked into A, but Perl goes to
1143        D. In other words, Perl considers parentheses that do not contain any |
1144        characters to be part of a surrounding alternative, whereas PCRE was
1145        treading (B(*THEN)C) the same as (B(*THEN)C|(*FAIL)) -- which Perl handles
1146        differently. PCRE now behaves in the same way as Perl, except in the case
1147        of subroutine/recursion calls such as (?1) which have in any case always
1148        been different (but PCRE had them first :-).
1149    
1150    16. Related to 15 above: Perl does not treat the | in a conditional group as
1151        creating alternatives. Such a group is treated in the same way as an
1152        ordinary group without any | characters when processing (*THEN). PCRE has
1153        been changed to match Perl's behaviour.
1154    
1155    17. If a user had set PCREGREP_COLO(U)R to something other than 1:31, the
1156        RunGrepTest script failed.
1157    
1158    18. Change 22 for version 13 caused atomic groups to use more stack. This is
1159        inevitable for groups that contain captures, but it can lead to a lot of
1160        stack use in large patterns. The old behaviour has been restored for atomic
1161        groups that do not contain any capturing parentheses.
1162    
1163    19. If the PCRE_NO_START_OPTIMIZE option was set for pcre_compile(), it did not
1164        suppress the check for a minimum subject length at run time. (If it was
1165        given to pcre_exec() or pcre_dfa_exec() it did work.)
1166    
1167    20. Fixed an ASCII-dependent infelicity in pcretest that would have made it
1168        fail to work when decoding hex characters in data strings in EBCDIC
1169        environments.
1170    
1171    21. It appears that in at least one Mac OS environment, the isxdigit() function
1172        is implemented as a macro that evaluates to its argument more than once,
1173        contravening the C 90 Standard (I haven't checked a later standard). There
1174        was an instance in pcretest which caused it to go wrong when processing
1175        \x{...} escapes in subject strings. The has been rewritten to avoid using
1176        things like p++ in the argument of isxdigit().
1177    
1178    
1179    Version 8.13 16-Aug-2011
1180    ------------------------
1181    
1182    1.  The Unicode data tables have been updated to Unicode 6.0.0.
1183    
1184    2.  Two minor typos in pcre_internal.h have been fixed.
1185    
1186    3.  Added #include <string.h> to pcre_scanner_unittest.cc, pcrecpp.cc, and
1187        pcrecpp_unittest.cc. They are needed for strcmp(), memset(), and strchr()
1188        in some environments (e.g. Solaris 10/SPARC using Sun Studio 12U2).
1189    
1190    4.  There were a number of related bugs in the code for matching backrefences
1191        caselessly in UTF-8 mode when codes for the characters concerned were
1192        different numbers of bytes. For example, U+023A and U+2C65 are an upper
1193        and lower case pair, using 2 and 3 bytes, respectively. The main bugs were:
1194        (a) A reference to 3 copies of a 2-byte code matched only 2 of a 3-byte
1195        code. (b) A reference to 2 copies of a 3-byte code would not match 2 of a
1196        2-byte code at the end of the subject (it thought there wasn't enough data
1197        left).
1198    
1199    5.  Comprehensive information about what went wrong is now returned by
1200        pcre_exec() and pcre_dfa_exec() when the UTF-8 string check fails, as long
1201        as the output vector has at least 2 elements. The offset of the start of
1202        the failing character and a reason code are placed in the vector.
1203    
1204    6.  When the UTF-8 string check fails for pcre_compile(), the offset that is
1205        now returned is for the first byte of the failing character, instead of the
1206        last byte inspected. This is an incompatible change, but I hope it is small
1207        enough not to be a problem. It makes the returned offset consistent with
1208        pcre_exec() and pcre_dfa_exec().
1209    
1210    7.  pcretest now gives a text phrase as well as the error number when
1211        pcre_exec() or pcre_dfa_exec() fails; if the error is a UTF-8 check
1212        failure, the offset and reason code are output.
1213    
1214    8.  When \R was used with a maximizing quantifier it failed to skip backwards
1215        over a \r\n pair if the subsequent match failed. Instead, it just skipped
1216        back over a single character (\n). This seems wrong (because it treated the
1217        two characters as a single entity when going forwards), conflicts with the
1218        documentation that \R is equivalent to (?>\r\n|\n|...etc), and makes the
1219        behaviour of \R* different to (\R)*, which also seems wrong. The behaviour
1220        has been changed.
1221    
1222    9.  Some internal refactoring has changed the processing so that the handling
1223        of the PCRE_CASELESS and PCRE_MULTILINE options is done entirely at compile
1224        time (the PCRE_DOTALL option was changed this way some time ago: version
1225        7.7 change 16). This has made it possible to abolish the OP_OPT op code,
1226        which was always a bit of a fudge. It also means that there is one less
1227        argument for the match() function, which reduces its stack requirements
1228        slightly. This change also fixes an incompatibility with Perl: the pattern
1229        (?i:([^b]))(?1) should not match "ab", but previously PCRE gave a match.
1230    
1231    10. More internal refactoring has drastically reduced the number of recursive
1232        calls to match() for possessively repeated groups such as (abc)++ when
1233        using pcre_exec().
1234    
1235    11. While implementing 10, a number of bugs in the handling of groups were
1236        discovered and fixed:
1237    
1238        (?<=(a)+) was not diagnosed as invalid (non-fixed-length lookbehind).
1239        (a|)*(?1) gave a compile-time internal error.
1240        ((a|)+)+  did not notice that the outer group could match an empty string.
1241        (^a|^)+   was not marked as anchored.
1242        (.*a|.*)+ was not marked as matching at start or after a newline.
1243    
1244    12. Yet more internal refactoring has removed another argument from the match()
1245        function. Special calls to this function are now indicated by setting a
1246        value in a variable in the "match data" data block.
1247    
1248    13. Be more explicit in pcre_study() instead of relying on "default" for
1249        opcodes that mean there is no starting character; this means that when new
1250        ones are added and accidentally left out of pcre_study(), testing should
1251        pick them up.
1252    
1253    14. The -s option of pcretest has been documented for ages as being an old
1254        synonym of -m (show memory usage). I have changed it to mean "force study
1255        for every regex", that is, assume /S for every regex. This is similar to -i
1256        and -d etc. It's slightly incompatible, but I'm hoping nobody is still
1257        using it. It makes it easier to run collections of tests with and without
1258        study enabled, and thereby test pcre_study() more easily. All the standard
1259        tests are now run with and without -s (but some patterns can be marked as
1260        "never study" - see 20 below).
1261    
1262    15. When (*ACCEPT) was used in a subpattern that was called recursively, the
1263        restoration of the capturing data to the outer values was not happening
1264        correctly.
1265    
1266    16. If a recursively called subpattern ended with (*ACCEPT) and matched an
1267        empty string, and PCRE_NOTEMPTY was set, pcre_exec() thought the whole
1268        pattern had matched an empty string, and so incorrectly returned a no
1269        match.
1270    
1271    17. There was optimizing code for the last branch of non-capturing parentheses,
1272        and also for the obeyed branch of a conditional subexpression, which used
1273        tail recursion to cut down on stack usage. Unfortunately, now that there is
1274        the possibility of (*THEN) occurring in these branches, tail recursion is
1275        no longer possible because the return has to be checked for (*THEN). These
1276        two optimizations have therefore been removed. [But see 8.20/11 above.]
1277    
1278    18. If a pattern containing \R was studied, it was assumed that \R always
1279        matched two bytes, thus causing the minimum subject length to be
1280        incorrectly computed because \R can also match just one byte.
1281    
1282    19. If a pattern containing (*ACCEPT) was studied, the minimum subject length
1283        was incorrectly computed.
1284    
1285    20. If /S is present twice on a test pattern in pcretest input, it now
1286        *disables* studying, thereby overriding the use of -s on the command line
1287        (see 14 above). This is necessary for one or two tests to keep the output
1288        identical in both cases.
1289    
1290    21. When (*ACCEPT) was used in an assertion that matched an empty string and
1291        PCRE_NOTEMPTY was set, PCRE applied the non-empty test to the assertion.
1292    
1293    22. When an atomic group that contained a capturing parenthesis was
1294        successfully matched, but the branch in which it appeared failed, the
1295        capturing was not being forgotten if a higher numbered group was later
1296        captured. For example, /(?>(a))b|(a)c/ when matching "ac" set capturing
1297        group 1 to "a", when in fact it should be unset. This applied to multi-
1298        branched capturing and non-capturing groups, repeated or not, and also to
1299        positive assertions (capturing in negative assertions does not happen
1300        in PCRE) and also to nested atomic groups.
1301    
1302    23. Add the ++ qualifier feature to pcretest, to show the remainder of the
1303        subject after a captured substring, to make it easier to tell which of a
1304        number of identical substrings has been captured.
1305    
1306    24. The way atomic groups are processed by pcre_exec() has been changed so that
1307        if they are repeated, backtracking one repetition now resets captured
1308        values correctly. For example, if ((?>(a+)b)+aabab) is matched against
1309        "aaaabaaabaabab" the value of captured group 2 is now correctly recorded as
1310        "aaa". Previously, it would have been "a". As part of this code
1311        refactoring, the way recursive calls are handled has also been changed.
1312    
1313    25. If an assertion condition captured any substrings, they were not passed
1314        back unless some other capturing happened later. For example, if
1315        (?(?=(a))a) was matched against "a", no capturing was returned.
1316    
1317    26. When studying a pattern that contained subroutine calls or assertions,
1318        the code for finding the minimum length of a possible match was handling
1319        direct recursions such as (xxx(?1)|yyy) but not mutual recursions (where
1320        group 1 called group 2 while simultaneously a separate group 2 called group
1321        1). A stack overflow occurred in this case. I have fixed this by limiting
1322        the recursion depth to 10.
1323    
1324    27. Updated RunTest.bat in the distribution to the version supplied by Tom
1325        Fortmann. This supports explicit test numbers on the command line, and has
1326        argument validation and error reporting.
1327    
1328    28. An instance of \X with an unlimited repeat could fail if at any point the
1329        first character it looked at was a mark character.
1330    
1331    29. Some minor code refactoring concerning Unicode properties and scripts
1332        should reduce the stack requirement of match() slightly.
1333    
1334    30. Added the '=' option to pcretest to check the setting of unused capturing
1335        slots at the end of the pattern, which are documented as being -1, but are
1336        not included in the return count.
1337    
1338    31. If \k was not followed by a braced, angle-bracketed, or quoted name, PCRE
1339        compiled something random. Now it gives a compile-time error (as does
1340        Perl).
1341    
1342    32. A *MARK encountered during the processing of a positive assertion is now
1343        recorded and passed back (compatible with Perl).
1344    
1345    33. If --only-matching or --colour was set on a pcregrep call whose pattern
1346        had alternative anchored branches, the search for a second match in a line
1347        was done as if at the line start. Thus, for example, /^01|^02/ incorrectly
1348        matched the line "0102" twice. The same bug affected patterns that started
1349        with a backwards assertion. For example /\b01|\b02/ also matched "0102"
1350        twice.
1351    
1352    34. Previously, PCRE did not allow quantification of assertions. However, Perl
1353        does, and because of capturing effects, quantifying parenthesized
1354        assertions may at times be useful. Quantifiers are now allowed for
1355        parenthesized assertions.
1356    
1357    35. A minor code tidy in pcre_compile() when checking options for \R usage.
1358    
1359    36. \g was being checked for fancy things in a character class, when it should
1360        just be a literal "g".
1361    
1362    37. PCRE was rejecting [:a[:digit:]] whereas Perl was not. It seems that the
1363        appearance of a nested POSIX class supersedes an apparent external class.
1364        For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,
1365        unescaped square brackets may also appear as part of class names. For
1366        example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves
1367        more like Perl. (But see 8.20/1 above.)
1368    
1369    38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this
1370        was because it thought it was \N{name}, which is not supported).
1371    
1372    39. Add minix to OS list not supporting the -S option in pcretest.
1373    
1374    40. PCRE tries to detect cases of infinite recursion at compile time, but it
1375        cannot analyze patterns in sufficient detail to catch mutual recursions
1376        such as ((?1))((?2)). There is now a runtime test that gives an error if a
1377        subgroup is called recursively as a subpattern for a second time at the
1378        same position in the subject string. In previous releases this might have
1379        been caught by the recursion limit, or it might have run out of stack.
1380    
1381    41. A pattern such as /(?(R)a+|(?R)b)/ is quite safe, as the recursion can
1382        happen only once. PCRE was, however incorrectly giving a compile time error
1383        "recursive call could loop indefinitely" because it cannot analyze the
1384        pattern in sufficient detail. The compile time test no longer happens when
1385        PCRE is compiling a conditional subpattern, but actual runaway loops are
1386        now caught at runtime (see 40 above).
1387    
1388    42. It seems that Perl allows any characters other than a closing parenthesis
1389        to be part of the NAME in (*MARK:NAME) and other backtracking verbs. PCRE
1390        has been changed to be the same.
1391    
1392    43. Updated configure.ac to put in more quoting round AC_LANG_PROGRAM etc. so
1393        as not to get warnings when autogen.sh is called. Also changed
1394        AC_PROG_LIBTOOL (deprecated) to LT_INIT (the current macro).
1395    
1396    44. To help people who use pcregrep to scan files containing exceedingly long
1397        lines, the following changes have been made:
1398    
1399        (a) The default value of the buffer size parameter has been increased from
1400            8K to 20K. (The actual buffer used is three times this size.)
1401    
1402        (b) The default can be changed by ./configure --with-pcregrep-bufsize when
1403            PCRE is built.
1404    
1405        (c) A --buffer-size=n option has been added to pcregrep, to allow the size
1406            to be set at run time.
1407    
1408        (d) Numerical values in pcregrep options can be followed by K or M, for
1409            example --buffer-size=50K.
1410    
1411        (e) If a line being scanned overflows pcregrep's buffer, an error is now
1412            given and the return code is set to 2.
1413    
1414    45. Add a pointer to the latest mark to the callout data block.
1415    
1416    46. The pattern /.(*F)/, when applied to "abc" with PCRE_PARTIAL_HARD, gave a
1417        partial match of an empty string instead of no match. This was specific to
1418        the use of ".".
1419    
1420    47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a
1421        complete match instead of a partial match. This bug was dependent on both
1422        the PCRE_UTF8 and PCRE_DOTALL options being set.
1423    
1424    48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the
1425        starting byte set, because \b was not being ignored.
1426    
1427    
1428    Version 8.12 15-Jan-2011
1429    ------------------------
1430    
1431    1.  Fixed some typos in the markup of the man pages, and wrote a script that
1432        checks for such things as part of the documentation building process.
1433    
1434    2.  On a big-endian 64-bit system, pcregrep did not correctly process the
1435        --match-limit and --recursion-limit options (added for 8.11). In
1436        particular, this made one of the standard tests fail. (The integer value
1437        went into the wrong half of a long int.)
1438    
1439    3.  If the --colour option was given to pcregrep with -v (invert match), it
1440        did strange things, either producing crazy output, or crashing. It should,
1441        of course, ignore a request for colour when reporting lines that do not
1442        match.
1443    
1444    4.  Another pcregrep bug caused similar problems if --colour was specified with
1445        -M (multiline) and the pattern match finished with a line ending.
1446    
1447    5.  In pcregrep, when a pattern that ended with a literal newline sequence was
1448        matched in multiline mode, the following line was shown as part of the
1449        match. This seems wrong, so I have changed it.
1450    
1451    6.  Another pcregrep bug in multiline mode, when --colour was specified, caused
1452        the check for further matches in the same line (so they could be coloured)
1453        to overrun the end of the current line. If another match was found, it was
1454        incorrectly shown (and then shown again when found in the next line).
1455    
1456    7.  If pcregrep was compiled under Windows, there was a reference to the
1457        function pcregrep_exit() before it was defined. I am assuming this was
1458        the cause of the "error C2371: 'pcregrep_exit' : redefinition;" that was
1459        reported by a user. I've moved the definition above the reference.
1460    
1461    
1462    Version 8.11 10-Dec-2010
1463    ------------------------
1464    
1465    1.  (*THEN) was not working properly if there were untried alternatives prior
1466        to it in the current branch. For example, in ((a|b)(*THEN)(*F)|c..) it
1467        backtracked to try for "b" instead of moving to the next alternative branch
1468        at the same level (in this case, to look for "c"). The Perl documentation
1469        is clear that when (*THEN) is backtracked onto, it goes to the "next
1470        alternative in the innermost enclosing group".
1471    
1472    2.  (*COMMIT) was not overriding (*THEN), as it does in Perl. In a pattern
1473        such as   (A(*COMMIT)B(*THEN)C|D)  any failure after matching A should
1474        result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and
1475        (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides
1476        (*THEN).
1477    
1478    3.  If \s appeared in a character class, it removed the VT character from
1479        the class, even if it had been included by some previous item, for example
1480        in [\x00-\xff\s]. (This was a bug related to the fact that VT is not part
1481        of \s, but is part of the POSIX "space" class.)
1482    
1483    4.  A partial match never returns an empty string (because you can always
1484        match an empty string at the end of the subject); however the checking for
1485        an empty string was starting at the "start of match" point. This has been
1486        changed to the "earliest inspected character" point, because the returned
1487        data for a partial match starts at this character. This means that, for
1488        example, /(?<=abc)def/ gives a partial match for the subject "abc"
1489        (previously it gave "no match").
1490    
1491    5.  Changes have been made to the way PCRE_PARTIAL_HARD affects the matching
1492        of $, \z, \Z, \b, and \B. If the match point is at the end of the string,
1493        previously a full match would be given. However, setting PCRE_PARTIAL_HARD
1494        has an implication that the given string is incomplete (because a partial
1495        match is preferred over a full match). For this reason, these items now
1496        give a partial match in this situation. [Aside: previously, the one case
1497        /t\b/ matched against "cat" with PCRE_PARTIAL_HARD set did return a partial
1498        match rather than a full match, which was wrong by the old rules, but is
1499        now correct.]
1500    
1501    6.  There was a bug in the handling of #-introduced comments, recognized when
1502        PCRE_EXTENDED is set, when PCRE_NEWLINE_ANY and PCRE_UTF8 were also set.
1503        If a UTF-8 multi-byte character included the byte 0x85 (e.g. +U0445, whose
1504        UTF-8 encoding is 0xd1,0x85), this was misinterpreted as a newline when
1505        scanning for the end of the comment. (*Character* 0x85 is an "any" newline,
1506        but *byte* 0x85 is not, in UTF-8 mode). This bug was present in several
1507        places in pcre_compile().
1508    
1509    7.  Related to (6) above, when pcre_compile() was skipping #-introduced
1510        comments when looking ahead for named forward references to subpatterns,
1511        the only newline sequence it recognized was NL. It now handles newlines
1512        according to the set newline convention.
1513    
1514    8.  SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the
1515        former, but used strtoul(), whereas pcretest avoided strtoul() but did not
1516        cater for a lack of strerror(). These oversights have been fixed.
1517    
1518    9.  Added --match-limit and --recursion-limit to pcregrep.
1519    
1520    10. Added two casts needed to build with Visual Studio when NO_RECURSE is set.
1521    
1522    11. When the -o option was used, pcregrep was setting a return code of 1, even
1523        when matches were found, and --line-buffered was not being honoured.
1524    
1525    12. Added an optional parentheses number to the -o and --only-matching options
1526        of pcregrep.
1527    
1528    13. Imitating Perl's /g action for multiple matches is tricky when the pattern
1529        can match an empty string. The code to do it in pcretest and pcredemo
1530        needed fixing:
1531    
1532        (a) When the newline convention was "crlf", pcretest got it wrong, skipping
1533            only one byte after an empty string match just before CRLF (this case
1534            just got forgotten; "any" and "anycrlf" were OK).
1535    
1536        (b) The pcretest code also had a bug, causing it to loop forever in UTF-8
1537            mode when an empty string match preceded an ASCII character followed by
1538            a non-ASCII character. (The code for advancing by one character rather
1539            than one byte was nonsense.)
1540    
1541        (c) The pcredemo.c sample program did not have any code at all to handle
1542            the cases when CRLF is a valid newline sequence.
1543    
1544    14. Neither pcre_exec() nor pcre_dfa_exec() was checking that the value given
1545        as a starting offset was within the subject string. There is now a new
1546        error, PCRE_ERROR_BADOFFSET, which is returned if the starting offset is
1547        negative or greater than the length of the string. In order to test this,
1548        pcretest is extended to allow the setting of negative starting offsets.
1549    
1550    15. In both pcre_exec() and pcre_dfa_exec() the code for checking that the
1551        starting offset points to the beginning of a UTF-8 character was
1552        unnecessarily clumsy. I tidied it up.
1553    
1554    16. Added PCRE_ERROR_SHORTUTF8 to make it possible to distinguish between a
1555        bad UTF-8 sequence and one that is incomplete when using PCRE_PARTIAL_HARD.
1556    
1557    17. Nobody had reported that the --include_dir option, which was added in
1558        release 7.7 should have been called --include-dir (hyphen, not underscore)
1559        for compatibility with GNU grep. I have changed it to --include-dir, but
1560        left --include_dir as an undocumented synonym, and the same for
1561        --exclude-dir, though that is not available in GNU grep, at least as of
1562        release 2.5.4.
1563    
1564    18. At a user's suggestion, the macros GETCHAR and friends (which pick up UTF-8
1565        characters from a string of bytes) have been redefined so as not to use
1566        loops, in order to improve performance in some environments. At the same
1567        time, I abstracted some of the common code into auxiliary macros to save
1568        repetition (this should not affect the compiled code).
1569    
1570    19. If \c was followed by a multibyte UTF-8 character, bad things happened. A
1571        compile-time error is now given if \c is not followed by an ASCII
1572        character, that is, a byte less than 128. (In EBCDIC mode, the code is
1573        different, and any byte value is allowed.)
1574    
1575    20. Recognize (*NO_START_OPT) at the start of a pattern to set the PCRE_NO_
1576        START_OPTIMIZE option, which is now allowed at compile time - but just
1577        passed through to pcre_exec() or pcre_dfa_exec(). This makes it available
1578        to pcregrep and other applications that have no direct access to PCRE
1579        options. The new /Y option in pcretest sets this option when calling
1580        pcre_compile().
1581    
1582    21. Change 18 of release 8.01 broke the use of named subpatterns for recursive
1583        back references. Groups containing recursive back references were forced to
1584        be atomic by that change, but in the case of named groups, the amount of
1585        memory required was incorrectly computed, leading to "Failed: internal
1586        error: code overflow". This has been fixed.
1587    
1588    22. Some patches to pcre_stringpiece.h, pcre_stringpiece_unittest.cc, and
1589        pcretest.c, to avoid build problems in some Borland environments.
1590    
1591    
1592    Version 8.10 25-Jun-2010
1593    ------------------------
1594    
1595    1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and
1596        THEN.
1597    
1598    2.  (*ACCEPT) was not working when inside an atomic group.
1599    
1600    3.  Inside a character class, \B is treated as a literal by default, but
1601        faulted if PCRE_EXTRA is set. This mimics Perl's behaviour (the -w option
1602        causes the error). The code is unchanged, but I tidied the documentation.
1603    
1604    4.  Inside a character class, PCRE always treated \R and \X as literals,
1605        whereas Perl faults them if its -w option is set. I have changed PCRE so
1606        that it faults them when PCRE_EXTRA is set.
1607    
1608    5.  Added support for \N, which always matches any character other than
1609        newline. (It is the same as "." when PCRE_DOTALL is not set.)
1610    
1611    6.  When compiling pcregrep with newer versions of gcc which may have
1612        FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',
1613        declared with attribute warn_unused_result" were given. Just casting the
1614        result to (void) does not stop the warnings; a more elaborate fudge is
1615        needed. I've used a macro to implement this.
1616    
1617    7.  Minor change to pcretest.c to avoid a compiler warning.
1618    
1619    8.  Added four artifical Unicode properties to help with an option to make
1620        \s etc use properties (see next item). The new properties are: Xan
1621        (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).
1622    
1623    9.  Added PCRE_UCP to make \b, \d, \s, \w, and certain POSIX character classes
1624        use Unicode properties. (*UCP) at the start of a pattern can be used to set
1625        this option. Modified pcretest to add /W to test this facility. Added
1626        REG_UCP to make it available via the POSIX interface.
1627    
1628    10. Added --line-buffered to pcregrep.
1629    
1630    11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was
1631        studied, and the match started with a letter with a code point greater than
1632        127 whose first byte was different to the first byte of the other case of
1633        the letter, the other case of this starting letter was not recognized
1634        (#976).
1635    
1636    12. If a pattern that was studied started with a repeated Unicode property
1637        test, for example, \p{Nd}+, there was the theoretical possibility of
1638        setting up an incorrect bitmap of starting bytes, but fortunately it could
1639        not have actually happened in practice until change 8 above was made (it
1640        added property types that matched character-matching opcodes).
1641    
1642    13. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
1643        possible starting bytes for non-anchored patterns.
1644    
1645    14. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes
1646        \R, and also a number of cases that involve Unicode properties, both
1647        explicit and implicit when PCRE_UCP is set.
1648    
1649    15. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8
1650        input, it could crash or give wrong results if characters with values
1651        greater than 0xc0 were present in the subject string. (Detail: it assumed
1652        UTF-8 input when processing these items.)
1653    
1654    16. Added a lot of (int) casts to avoid compiler warnings in systems where
1655        size_t is 64-bit (#991).
1656    
1657    17. Added a check for running out of memory when PCRE is compiled with
1658        --disable-stack-for-recursion (#990).
1659    
1660    18. If the last data line in a file for pcretest does not have a newline on
1661        the end, a newline was missing in the output.
1662    
1663    19. The default pcre_chartables.c file recognizes only ASCII characters (values
1664        less than 128) in its various bitmaps. However, there is a facility for
1665        generating tables according to the current locale when PCRE is compiled. It
1666        turns out that in some environments, 0x85 and 0xa0, which are Unicode space
1667        characters, are recognized by isspace() and therefore were getting set in
1668        these tables, and indeed these tables seem to approximate to ISO 8859. This
1669        caused a problem in UTF-8 mode when pcre_study() was used to create a list
1670        of bytes that can start a match. For \s, it was including 0x85 and 0xa0,
1671        which of course cannot start UTF-8 characters. I have changed the code so
1672        that only real ASCII characters (less than 128) and the correct starting
1673        bytes for UTF-8 encodings are set for characters greater than 127 when in
1674        UTF-8 mode. (When PCRE_UCP is set - see 9 above - the code is different
1675        altogether.)
1676    
1677    20. Added the /T option to pcretest so as to be able to run tests with non-
1678        standard character tables, thus making it possible to include the tests
1679        used for 19 above in the standard set of tests.
1680    
1681    21. A pattern such as (?&t)(?#()(?(DEFINE)(?<t>a)) which has a forward
1682        reference to a subpattern the other side of a comment that contains an
1683        opening parenthesis caused either an internal compiling error, or a
1684        reference to the wrong subpattern.
1685    
1686    
1687    Version 8.02 19-Mar-2010
1688  ------------------------  ------------------------
1689    
1690  1.  The Unicode data tables have been updated to Unicode 5.2.0.  1.  The Unicode data tables have been updated to Unicode 5.2.0.
1691    
1692  2.  Added the option --libs-cpp to pcre-config, but only when C++ support is  2.  Added the option --libs-cpp to pcre-config, but only when C++ support is
1693      configured.      configured.
1694    
1695  3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the  3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the
1696      original author of that file, following a query about its status.      original author of that file, following a query about its status.
1697    
1698  4.  On systems that do not have stdint.h (e.g. Solaris), check for and include  4.  On systems that do not have stdint.h (e.g. Solaris), check for and include
1699      inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.      inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
1700    
1701  5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive  5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
1702      quantifier applied to a forward-referencing subroutine call, could compile      quantifier applied to a forward-referencing subroutine call, could compile
1703      incorrect code or give the error "internal error: previously-checked      incorrect code or give the error "internal error: previously-checked
1704      referenced subpattern not found".      referenced subpattern not found".
1705    
1706  6.  Both MS Visual Studio and Symbian OS have problems with initializing  6.  Both MS Visual Studio and Symbian OS have problems with initializing
1707      variables to point to external functions. For these systems, therefore,      variables to point to external functions. For these systems, therefore,
1708      pcre_malloc etc. are now initialized to local functions that call the      pcre_malloc etc. are now initialized to local functions that call the
1709      relevant global functions.      relevant global functions.
1710    
1711  7.  There were two entries missing in the vectors called coptable and poptable  7.  There were two entries missing in the vectors called coptable and poptable
1712      in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.      in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.
1713      I've fixed the data, and added a kludgy way of testing at compile time that      I've fixed the data, and added a kludgy way of testing at compile time that
1714      the lengths are correct (equal to the number of opcodes).      the lengths are correct (equal to the number of opcodes).
1715    
1716  8.  Following on from 7, I added a similar kludge to check the length of the  8.  Following on from 7, I added a similar kludge to check the length of the
1717      eint vector in pcreposix.c.      eint vector in pcreposix.c.
1718    
1719  9.  Error texts for pcre_compile() are held as one long string to avoid too  9.  Error texts for pcre_compile() are held as one long string to avoid too
1720      much relocation at load time. To find a text, the string is searched,      much relocation at load time. To find a text, the string is searched,
1721      counting zeros. There was no check for running off the end of the string,      counting zeros. There was no check for running off the end of the string,
1722      which could happen if a new error number was added without updating the      which could happen if a new error number was added without updating the
1723      string.      string.
1724    
1725  10. \K gave a compile-time error if it appeared in a lookbehind assersion.  10. \K gave a compile-time error if it appeared in a lookbehind assersion.
1726    
1727  11. \K was not working if it appeared in an atomic group or in a group that  11. \K was not working if it appeared in an atomic group or in a group that
1728      was called as a "subroutine", or in an assertion. Perl 5.11 documents that      was called as a "subroutine", or in an assertion. Perl 5.11 documents that
1729      \K is "not well defined" if used in an assertion. PCRE now accepts it if      \K is "not well defined" if used in an assertion. PCRE now accepts it if
1730      the assertion is positive, but not if it is negative.      the assertion is positive, but not if it is negative.
1731    
1732  12. Change 11 fortuitously reduced the size of the stack frame used in the  12. Change 11 fortuitously reduced the size of the stack frame used in the
1733      "match()" function of pcre_exec.c by one pointer. Forthcoming      "match()" function of pcre_exec.c by one pointer. Forthcoming
1734      implementation of support for (*MARK) will need an extra pointer on the      implementation of support for (*MARK) will need an extra pointer on the
1735      stack; I have reserved it now, so that the stack frame size does not      stack; I have reserved it now, so that the stack frame size does not
1736      decrease.      decrease.
1737    
1738  13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other  13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other
1739      item in branch that calls a recursion is a subroutine call - as in the      item in branch that calls a recursion is a subroutine call - as in the
1740      second branch in the above example - was incorrectly given the compile-      second branch in the above example - was incorrectly given the compile-
1741      time error "recursive call could loop indefinitely" because pcre_compile()      time error "recursive call could loop indefinitely" because pcre_compile()
1742      was not correctly checking the subroutine for matching a non-empty string.      was not correctly checking the subroutine for matching a non-empty string.
1743    
1744  14. The checks for overrunning compiling workspace could trigger after an  14. The checks for overrunning compiling workspace could trigger after an
1745      overrun had occurred. This is a "should never occur" error, but it can be      overrun had occurred. This is a "should never occur" error, but it can be
1746      triggered by pathological patterns such as hundreds of nested parentheses.      triggered by pathological patterns such as hundreds of nested parentheses.
1747      The checks now trigger 100 bytes before the end of the workspace.      The checks now trigger 100 bytes before the end of the workspace.
1748    
1749    15. Fix typo in configure.ac: "srtoq" should be "strtoq".
1750    
1751    
1752  Version 8.01 19-Jan-2010  Version 8.01 19-Jan-2010
# Line 390  Version 7.9 11-Apr-09 Line 2075  Version 7.9 11-Apr-09
2075  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
2076      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
2077      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
2078      seems to be how GNU grep behaves.      seems to be how GNU grep behaves. [But see later change 40 for release
2079        8.33.]
2080    
2081  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
2082      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 633  Version 7.7 07-May-08 Line 2319  Version 7.7 07-May-08
2319      containing () gave an internal compiling error instead of "reference to      containing () gave an internal compiling error instead of "reference to
2320      non-existent subpattern". Fortunately, when the pattern did exist, the      non-existent subpattern". Fortunately, when the pattern did exist, the
2321      compiled code was correct. (When scanning forwards to check for the      compiled code was correct. (When scanning forwards to check for the
2322      existencd of the subpattern, it was treating the data ']' as terminating      existence of the subpattern, it was treating the data ']' as terminating
2323      the class, so got the count wrong. When actually compiling, the reference      the class, so got the count wrong. When actually compiling, the reference
2324      was subsequently set up correctly.)      was subsequently set up correctly.)
2325    

Legend:
Removed from v.505  
changed lines
  Added in v.1487

  ViewVC Help
Powered by ViewVC 1.1.5