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

Diff of /code/trunk/ChangeLog

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

revision 341 by ph10, Sat Apr 19 16:41:04 2008 UTC revision 1537 by ph10, Fri Mar 27 17:48:28 2015 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 7.7 05-Mar-08  Version 8.37 xx-xxx-2015
5    ------------------------
6    
7    1.  When an (*ACCEPT) is triggered inside capturing parentheses, it arranges
8        for those parentheses to be closed with whatever has been captured so far.
9        However, it was failing to mark any other groups between the hightest
10        capture so far and the currrent group as "unset". Thus, the ovector for
11        those groups contained whatever was previously there. An example is the
12        pattern /(x)|((*ACCEPT))/ when matched against "abcd".
13    
14    2.  If an assertion condition was quantified with a minimum of zero (an odd
15        thing to do, but it happened), SIGSEGV or other misbehaviour could occur.
16    
17    3.  If a pattern in pcretest input had the P (POSIX) modifier followed by an
18        unrecognized modifier, a crash could occur.
19    
20    4.  An attempt to do global matching in pcretest with a zero-length ovector
21        caused a crash.
22    
23    5.  Fixed a memory leak during matching that could occur for a subpattern
24        subroutine call (recursive or otherwise) if the number of captured groups
25        that had to be saved was greater than ten.
26    
27    6.  Catch a bad opcode during auto-possessification after compiling a bad UTF
28        string with NO_UTF_CHECK. This is a tidyup, not a bug fix, as passing bad
29        UTF with NO_UTF_CHECK is documented as having an undefined outcome.
30    
31    7.  A UTF pattern containing a "not" match of a non-ASCII character and a
32        subroutine reference could loop at compile time. Example: /[^\xff]((?1))/.
33    
34    8. When a pattern is compiled, it remembers the highest back reference so that
35       when matching, if the ovector is too small, extra memory can be obtained to
36       use instead. A conditional subpattern whose condition is a check on a
37       capture having happened, such as, for example in the pattern
38       /^(?:(a)|b)(?(1)A|B)/, is another kind of back reference, but it was not
39       setting the highest backreference number. This mattered only if pcre_exec()
40       was called with an ovector that was too small to hold the capture, and there
41       was no other kind of back reference (a situation which is probably quite
42       rare). The effect of the bug was that the condition was always treated as
43       FALSE when the capture could not be consulted, leading to a incorrect
44       behaviour by pcre2_match(). This bug has been fixed.
45    
46    9. A reference to a duplicated named group (either a back reference or a test
47       for being set in a conditional) that occurred in a part of the pattern where
48       PCRE_DUPNAMES was not set caused the amount of memory needed for the pattern
49       to be incorrectly calculated, leading to overwriting.
50    
51    10. A mutually recursive set of back references such as (\2)(\1) caused a
52        segfault at study time (while trying to find the minimum matching length).
53        The infinite loop is now broken (with the minimum length unset, that is,
54        zero).
55    
56    11. If an assertion that was used as a condition was quantified with a minimum
57        of zero, matching went wrong. In particular, if the whole group had
58        unlimited repetition and could match an empty string, a segfault was
59        likely. The pattern (?(?=0)?)+ is an example that caused this. Perl allows
60        assertions to be quantified, but not if they are being used as conditions,
61        so the above pattern is faulted by Perl. PCRE has now been changed so that
62        it also rejects such patterns.
63    
64    12. A possessive capturing group such as (a)*+ with a minimum repeat of zero
65        failed to allow the zero-repeat case if pcre2_exec() was called with an
66        ovector too small to capture the group.
67    
68    13. Fixed two bugs in pcretest that were discovered by fuzzing and reported by
69        Red Hat Product Security:
70    
71        (a) A crash if /K and /F were both set with the option to save the compiled
72        pattern.
73    
74        (b) Another crash if the option to print captured substrings in a callout
75        was combined with setting a null ovector, for example \O\C+ as a subject
76        string.
77    
78    14. A pattern such as "((?2){0,1999}())?", which has a group containing a
79        forward reference repeated a large (but limited) number of times within a
80        repeated outer group that has a zero minimum quantifier, caused incorrect
81        code to be compiled, leading to the error "internal error:
82        previously-checked referenced subpattern not found" when an incorrect
83        memory address was read. This bug was reported as "heap overflow",
84        discovered by Kai Lu of Fortinet's FortiGuard Labs and given the CVE number
85        CVE-2015-2325.
86    
87    23. A pattern such as "((?+1)(\1))/" containing a forward reference subroutine
88        call within a group that also contained a recursive back reference caused
89        incorrect code to be compiled. This bug was reported as "heap overflow",
90        discovered by Kai Lu of Fortinet's FortiGuard Labs, and given the CVE
91        number CVE-2015-2326.
92    
93    24. Computing the size of the JIT read-only data in advance has been a source
94        of various issues, and new ones are still appear unfortunately. To fix
95        existing and future issues, size computation is eliminated from the code,
96        and replaced by on-demand memory allocation.
97    
98    25. A pattern such as /(?i)[A-`]/, where characters in the other case are
99        adjacent to the end of the range, and the range contained characters with
100        more than one other case, caused incorrect behaviour when compiled in UTF
101        mode. In that example, the range a-j was left out of the class.
102    
103    26. Fix JIT compilation of conditional blocks, which assertion
104        is converted to (*FAIL). E.g: /(?(?!))/.
105    
106    27. The pattern /(?(?!)^)/ caused references to random memory. This bug was
107        discovered by the LLVM fuzzer.
108    
109    28. The assertion (?!) is optimized to (*FAIL). This was not handled correctly
110        when this assertion was used as a condition, for example (?(?!)a|b). In
111        pcre2_match() it worked by luck; in pcre2_dfa_match() it gave an incorrect
112        error about an unsupported item.
113    
114    29. For some types of pattern, for example /Z*(|d*){216}/, the auto-
115        possessification code could take exponential time to complete. A recursion
116        depth limit of 1000 has been imposed to limit the resources used by this
117        optimization.
118    
119    30. A pattern such as /(*UTF)[\S\V\H]/, which contains a negated special class
120        such as \S in non-UCP mode, explicit wide characters (> 255) can be ignored
121        because \S ensures they are all in the class. The code for doing this was
122        interacting badly with the code for computing the amount of space needed to
123        compile the pattern, leading to a buffer overflow. This bug was discovered
124        by the LLVM fuzzer.
125    
126    31. A pattern such as /((?2)+)((?1))/ which has mutual recursion nested inside
127        other kinds of group caused stack overflow at compile time. This bug was
128        discovered by the LLVM fuzzer.
129    
130    
131    Version 8.36 26-September-2014
132    ------------------------------
133    
134    1.  Got rid of some compiler warnings in the C++ modules that were shown up by
135        -Wmissing-field-initializers and -Wunused-parameter.
136    
137    2.  The tests for quantifiers being too big (greater than 65535) were being
138        applied after reading the number, and stupidly assuming that integer
139        overflow would give a negative number. The tests are now applied as the
140        numbers are read.
141    
142    3.  Tidy code in pcre_exec.c where two branches that used to be different are
143        now the same.
144    
145    4.  The JIT compiler did not generate match limit checks for certain
146        bracketed expressions with quantifiers. This may lead to exponential
147        backtracking, instead of returning with PCRE_ERROR_MATCHLIMIT. This
148        issue should be resolved now.
149    
150    5.  Fixed an issue, which occures when nested alternatives are optimized
151        with table jumps.
152    
153    6.  Inserted two casts and changed some ints to size_t in the light of some
154        reported 64-bit compiler warnings (Bugzilla 1477).
155    
156    7.  Fixed a bug concerned with zero-minimum possessive groups that could match
157        an empty string, which sometimes were behaving incorrectly in the
158        interpreter (though correctly in the JIT matcher). This pcretest input is
159        an example:
160    
161          '\A(?:[^"]++|"(?:[^"]*+|"")*+")++'
162          NON QUOTED "QUOT""ED" AFTER "NOT MATCHED
163    
164        the interpreter was reporting a match of 'NON QUOTED ' only, whereas the
165        JIT matcher and Perl both matched 'NON QUOTED "QUOT""ED" AFTER '. The test
166        for an empty string was breaking the inner loop and carrying on at a lower
167        level, when possessive repeated groups should always return to a higher
168        level as they have no backtrack points in them. The empty string test now
169        occurs at the outer level.
170    
171    8.  Fixed a bug that was incorrectly auto-possessifying \w+ in the pattern
172        ^\w+(?>\s*)(?<=\w) which caused it not to match "test test".
173    
174    9.  Give a compile-time error for \o{} (as Perl does) and for \x{} (which Perl
175        doesn't).
176    
177    10. Change 8.34/15 introduced a bug that caused the amount of memory needed
178        to hold a pattern to be incorrectly computed (too small) when there were
179        named back references to duplicated names. This could cause "internal
180        error: code overflow" or "double free or corruption" or other memory
181        handling errors.
182    
183    11. When named subpatterns had the same prefixes, back references could be
184        confused. For example, in this pattern:
185    
186          /(?P<Name>a)?(?P<Name2>b)?(?(<Name>)c|d)*l/
187    
188        the reference to 'Name' was incorrectly treated as a reference to a
189        duplicate name.
190    
191    12. A pattern such as /^s?c/mi8 where the optional character has more than
192        one "other case" was incorrectly compiled such that it would only try to
193        match starting at "c".
194    
195    13. When a pattern starting with \s was studied, VT was not included in the
196        list of possible starting characters; this should have been part of the
197        8.34/18 patch.
198    
199    14. If a character class started [\Qx]... where x is any character, the class
200        was incorrectly terminated at the ].
201    
202    15. If a pattern that started with a caseless match for a character with more
203        than one "other case" was studied, PCRE did not set up the starting code
204        unit bit map for the list of possible characters. Now it does. This is an
205        optimization improvement, not a bug fix.
206    
207    16. The Unicode data tables have been updated to Unicode 7.0.0.
208    
209    17. Fixed a number of memory leaks in pcregrep.
210    
211    18. Avoid a compiler warning (from some compilers) for a function call with
212        a cast that removes "const" from an lvalue by using an intermediate
213        variable (to which the compiler does not object).
214    
215    19. Incorrect code was compiled if a group that contained an internal recursive
216        back reference was optional (had quantifier with a minimum of zero). This
217        example compiled incorrect code: /(((a\2)|(a*)\g<-1>))*/ and other examples
218        caused segmentation faults because of stack overflows at compile time.
219    
220    20. A pattern such as /((?(R)a|(?1)))+/, which contains a recursion within a
221        group that is quantified with an indefinite repeat, caused a compile-time
222        loop which used up all the system stack and provoked a segmentation fault.
223        This was not the same bug as 19 above.
224    
225    21. Add PCRECPP_EXP_DECL declaration to operator<< in pcre_stringpiece.h.
226        Patch by Mike Frysinger.
227    
228    
229    Version 8.35 04-April-2014
230    --------------------------
231    
232    1.  A new flag is set, when property checks are present in an XCLASS.
233        When this flag is not set, PCRE can perform certain optimizations
234        such as studying these XCLASS-es.
235    
236    2.  The auto-possessification of character sets were improved: a normal
237        and an extended character set can be compared now. Furthermore
238        the JIT compiler optimizes more character set checks.
239    
240    3.  Got rid of some compiler warnings for potentially uninitialized variables
241        that show up only when compiled with -O2.
242    
243    4.  A pattern such as (?=ab\K) that uses \K in an assertion can set the start
244        of a match later then the end of the match. The pcretest program was not
245        handling the case sensibly - it was outputting from the start to the next
246        binary zero. It now reports this situation in a message, and outputs the
247        text from the end to the start.
248    
249    5.  Fast forward search is improved in JIT. Instead of the first three
250        characters, any three characters with fixed position can be searched.
251        Search order: first, last, middle.
252    
253    6.  Improve character range checks in JIT. Characters are read by an inprecise
254        function now, which returns with an unknown value if the character code is
255        above a certain threshold (e.g: 256). The only limitation is that the value
256        must be bigger than the threshold as well. This function is useful when
257        the characters above the threshold are handled in the same way.
258    
259    7.  The macros whose names start with RAWUCHAR are placeholders for a future
260        mode in which only the bottom 21 bits of 32-bit data items are used. To
261        make this more memorable for those maintaining the code, the names have
262        been changed to start with UCHAR21, and an extensive comment has been added
263        to their definition.
264    
265    8.  Add missing (new) files sljitNativeTILEGX.c and sljitNativeTILEGX-encoder.c
266        to the export list in Makefile.am (they were accidentally omitted from the
267        8.34 tarball).
268    
269    9.  The informational output from pcretest used the phrase "starting byte set"
270        which is inappropriate for the 16-bit and 32-bit libraries. As the output
271        for "first char" and "need char" really means "non-UTF-char", I've changed
272        "byte" to "char", and slightly reworded the output. The documentation about
273        these values has also been (I hope) clarified.
274    
275    10. Another JIT related optimization: use table jumps for selecting the correct
276        backtracking path, when more than four alternatives are present inside a
277        bracket.
278    
279    11. Empty match is not possible, when the minimum length is greater than zero,
280        and there is no \K in the pattern. JIT should avoid empty match checks in
281        such cases.
282    
283    12. In a caseless character class with UCP support, when a character with more
284        than one alternative case was not the first character of a range, not all
285        the alternative cases were added to the class. For example, s and \x{17f}
286        are both alternative cases for S: the class [RST] was handled correctly,
287        but [R-T] was not.
288    
289    13. The configure.ac file always checked for pthread support when JIT was
290        enabled. This is not used in Windows, so I have put this test inside a
291        check for the presence of windows.h (which was already tested for).
292    
293    14. Improve pattern prefix search by a simplified Boyer-Moore algorithm in JIT.
294        The algorithm provides a way to skip certain starting offsets, and usually
295        faster than linear prefix searches.
296    
297    15. Change 13 for 8.20 updated RunTest to check for the 'fr' locale as well
298        as for 'fr_FR' and 'french'. For some reason, however, it then used the
299        Windows-specific input and output files, which have 'french' screwed in.
300        So this could never have worked. One of the problems with locales is that
301        they aren't always the same. I have now updated RunTest so that it checks
302        the output of the locale test (test 3) against three different output
303        files, and it allows the test to pass if any one of them matches. With luck
304        this should make the test pass on some versions of Solaris where it was
305        failing. Because of the uncertainty, the script did not used to stop if
306        test 3 failed; it now does. If further versions of a French locale ever
307        come to light, they can now easily be added.
308    
309    16. If --with-pcregrep-bufsize was given a non-integer value such as "50K",
310        there was a message during ./configure, but it did not stop. This now
311        provokes an error. The invalid example in README has been corrected.
312        If a value less than the minimum is given, the minimum value has always
313        been used, but now a warning is given.
314    
315    17. If --enable-bsr-anycrlf was set, the special 16/32-bit test failed. This
316        was a bug in the test system, which is now fixed. Also, the list of various
317        configurations that are tested for each release did not have one with both
318        16/32 bits and --enable-bar-anycrlf. It now does.
319    
320    18. pcretest was missing "-C bsr" for displaying the \R default setting.
321    
322    19. Little endian PowerPC systems are supported now by the JIT compiler.
323    
324    20. The fast forward newline mechanism could enter to an infinite loop on
325        certain invalid UTF-8 input. Although we don't support these cases
326        this issue can be fixed by a performance optimization.
327    
328    21. Change 33 of 8.34 is not sufficient to ensure stack safety because it does
329        not take account if existing stack usage. There is now a new global
330        variable called pcre_stack_guard that can be set to point to an external
331        function to check stack availability. It is called at the start of
332        processing every parenthesized group.
333    
334    22. A typo in the code meant that in ungreedy mode the max/min qualifier
335        behaved like a min-possessive qualifier, and, for example, /a{1,3}b/U did
336        not match "ab".
337    
338    23. When UTF was disabled, the JIT program reported some incorrect compile
339        errors. These messages are silenced now.
340    
341    24. Experimental support for ARM-64 and MIPS-64 has been added to the JIT
342        compiler.
343    
344    25. Change all the temporary files used in RunGrepTest to be different to those
345        used by RunTest so that the tests can be run simultaneously, for example by
346        "make -j check".
347    
348    
349    Version 8.34 15-December-2013
350    -----------------------------
351    
352    1.  Add pcre[16|32]_jit_free_unused_memory to forcibly free unused JIT
353        executable memory. Patch inspired by Carsten Klein.
354    
355    2.  ./configure --enable-coverage defined SUPPORT_GCOV in config.h, although
356        this macro is never tested and has no effect, because the work to support
357        coverage involves only compiling and linking options and special targets in
358        the Makefile. The comment in config.h implied that defining the macro would
359        enable coverage support, which is totally false. There was also support for
360        setting this macro in the CMake files (my fault, I just copied it from
361        configure). SUPPORT_GCOV has now been removed.
362    
363    3.  Make a small performance improvement in strlen16() and strlen32() in
364        pcretest.
365    
366    4.  Change 36 for 8.33 left some unreachable statements in pcre_exec.c,
367        detected by the Solaris compiler (gcc doesn't seem to be able to diagnose
368        these cases). There was also one in pcretest.c.
369    
370    5.  Cleaned up a "may be uninitialized" compiler warning in pcre_exec.c.
371    
372    6.  In UTF mode, the code for checking whether a group could match an empty
373        string (which is used for indefinitely repeated groups to allow for
374        breaking an infinite loop) was broken when the group contained a repeated
375        negated single-character class with a character that occupied more than one
376        data item and had a minimum repetition of zero (for example, [^\x{100}]* in
377        UTF-8 mode). The effect was undefined: the group might or might not be
378        deemed as matching an empty string, or the program might have crashed.
379    
380    7.  The code for checking whether a group could match an empty string was not
381        recognizing that \h, \H, \v, \V, and \R must match a character.
382    
383    8.  Implemented PCRE_INFO_MATCH_EMPTY, which yields 1 if the pattern can match
384        an empty string. If it can, pcretest shows this in its information output.
385    
386    9.  Fixed two related bugs that applied to Unicode extended grapheme clusters
387        that were repeated with a maximizing qualifier (e.g. \X* or \X{2,5}) when
388        matched by pcre_exec() without using JIT:
389    
390        (a) If the rest of the pattern did not match after a maximal run of
391            grapheme clusters, the code for backing up to try with fewer of them
392            did not always back up over a full grapheme when characters that do not
393            have the modifier quality were involved, e.g. Hangul syllables.
394    
395        (b) If the match point in a subject started with modifier character, and
396            there was no match, the code could incorrectly back up beyond the match
397            point, and potentially beyond the first character in the subject,
398            leading to a segfault or an incorrect match result.
399    
400    10. A conditional group with an assertion condition could lead to PCRE
401        recording an incorrect first data item for a match if no other first data
402        item was recorded. For example, the pattern (?(?=ab)ab) recorded "a" as a
403        first data item, and therefore matched "ca" after "c" instead of at the
404        start.
405    
406    11. Change 40 for 8.33 (allowing pcregrep to find empty strings) showed up a
407        bug that caused the command "echo a | ./pcregrep -M '|a'" to loop.
408    
409    12. The source of pcregrep now includes z/OS-specific code so that it can be
410        compiled for z/OS as part of the special z/OS distribution.
411    
412    13. Added the -T and -TM options to pcretest.
413    
414    14. The code in pcre_compile.c for creating the table of named capturing groups
415        has been refactored. Instead of creating the table dynamically during the
416        actual compiling pass, the information is remembered during the pre-compile
417        pass (on the stack unless there are more than 20 named groups, in which
418        case malloc() is used) and the whole table is created before the actual
419        compile happens. This has simplified the code (it is now nearly 150 lines
420        shorter) and prepared the way for better handling of references to groups
421        with duplicate names.
422    
423    15. A back reference to a named subpattern when there is more than one of the
424        same name now checks them in the order in which they appear in the pattern.
425        The first one that is set is used for the reference. Previously only the
426        first one was inspected. This change makes PCRE more compatible with Perl.
427    
428    16. Unicode character properties were updated from Unicode 6.3.0.
429    
430    17. The compile-time code for auto-possessification has been refactored, based
431        on a patch by Zoltan Herczeg. It now happens after instead of during
432        compilation. The code is cleaner, and more cases are handled. The option
433        PCRE_NO_AUTO_POSSESS is added for testing purposes, and the -O and /O
434        options in pcretest are provided to set it. It can also be set by
435        (*NO_AUTO_POSSESS) at the start of a pattern.
436    
437    18. The character VT has been added to the default ("C" locale) set of
438        characters that match \s and are generally treated as white space,
439        following this same change in Perl 5.18. There is now no difference between
440        "Perl space" and "POSIX space". Whether VT is treated as white space in
441        other locales depends on the locale.
442    
443    19. The code for checking named groups as conditions, either for being set or
444        for being recursed, has been refactored (this is related to 14 and 15
445        above). Processing unduplicated named groups should now be as fast at
446        numerical groups, and processing duplicated groups should be faster than
447        before.
448    
449    20. Two patches to the CMake build system, by Alexander Barkov:
450    
451          (1) Replace the "source" command by "." in CMakeLists.txt because
452              "source" is a bash-ism.
453    
454          (2) Add missing HAVE_STDINT_H and HAVE_INTTYPES_H to config-cmake.h.in;
455              without these the CMake build does not work on Solaris.
456    
457    21. Perl has changed its handling of \8 and \9. If there is no previously
458        encountered capturing group of those numbers, they are treated as the
459        literal characters 8 and 9 instead of a binary zero followed by the
460        literals. PCRE now does the same.
461    
462    22. Following Perl, added \o{} to specify codepoints in octal, making it
463        possible to specify values greater than 0777 and also making them
464        unambiguous.
465    
466    23. Perl now gives an error for missing closing braces after \x{... instead of
467        treating the string as literal. PCRE now does the same.
468    
469    24. RunTest used to grumble if an inappropriate test was selected explicitly,
470        but just skip it when running all tests. This make it awkward to run ranges
471        of tests when one of them was inappropriate. Now it just skips any
472        inappropriate tests, as it always did when running all tests.
473    
474    25. If PCRE_AUTO_CALLOUT and PCRE_UCP were set for a pattern that contained
475        character types such as \d or \w, too many callouts were inserted, and the
476        data that they returned was rubbish.
477    
478    26. In UCP mode, \s was not matching two of the characters that Perl matches,
479        namely NEL (U+0085) and MONGOLIAN VOWEL SEPARATOR (U+180E), though they
480        were matched by \h. The code has now been refactored so that the lists of
481        the horizontal and vertical whitespace characters used for \h and \v (which
482        are defined only in one place) are now also used for \s.
483    
484    27. Add JIT support for the 64 bit TileGX architecture.
485        Patch by Jiong Wang (Tilera Corporation).
486    
487    28. Possessive quantifiers for classes (both explicit and automatically
488        generated) now use special opcodes instead of wrapping in ONCE brackets.
489    
490    29. Whereas an item such as A{4}+ ignored the possessivenes of the quantifier
491        (because it's meaningless), this was not happening when PCRE_CASELESS was
492        set. Not wrong, but inefficient.
493    
494    30. Updated perltest.pl to add /u (force Unicode mode) when /W (use Unicode
495        properties for \w, \d, etc) is present in a test regex. Otherwise if the
496        test contains no characters greater than 255, Perl doesn't realise it
497        should be using Unicode semantics.
498    
499    31. Upgraded the handling of the POSIX classes [:graph:], [:print:], and
500        [:punct:] when PCRE_UCP is set so as to include the same characters as Perl
501        does in Unicode mode.
502    
503    32. Added the "forbid" facility to pcretest so that putting tests into the
504        wrong test files can sometimes be quickly detected.
505    
506    33. There is now a limit (default 250) on the depth of nesting of parentheses.
507        This limit is imposed to control the amount of system stack used at compile
508        time. It can be changed at build time by --with-parens-nest-limit=xxx or
509        the equivalent in CMake.
510    
511    34. Character classes such as [A-\d] or [a-[:digit:]] now cause compile-time
512        errors. Perl warns for these when in warning mode, but PCRE has no facility
513        for giving warnings.
514    
515    35. Change 34 for 8.13 allowed quantifiers on assertions, because Perl does.
516        However, this was not working for (?!) because it is optimized to (*FAIL),
517        for which PCRE does not allow quantifiers. The optimization is now disabled
518        when a quantifier follows (?!). I can't see any use for this, but it makes
519        things uniform.
520    
521    36. Perl no longer allows group names to start with digits, so I have made this
522        change also in PCRE. It simplifies the code a bit.
523    
524    37. In extended mode, Perl ignores spaces before a + that indicates a
525        possessive quantifier. PCRE allowed a space before the quantifier, but not
526        before the possessive +. It now does.
527    
528    38. The use of \K (reset reported match start) within a repeated possessive
529        group such as (a\Kb)*+ was not working.
530    
531    40. Document that the same character tables must be used at compile time and
532        run time, and that the facility to pass tables to pcre_exec() and
533        pcre_dfa_exec() is for use only with saved/restored patterns.
534    
535    41. Applied Jeff Trawick's patch CMakeLists.txt, which "provides two new
536        features for Builds with MSVC:
537    
538        1. Support pcre.rc and/or pcreposix.rc (as is already done for MinGW
539           builds). The .rc files can be used to set FileDescription and many other
540           attributes.
541    
542        2. Add an option (-DINSTALL_MSVC_PDB) to enable installation of .pdb files.
543           This allows higher-level build scripts which want .pdb files to avoid
544           hard-coding the exact files needed."
545    
546    42. Added support for [[:<:]] and [[:>:]] as used in the BSD POSIX library to
547        mean "start of word" and "end of word", respectively, as a transition aid.
548    
549    43. A minimizing repeat of a class containing codepoints greater than 255 in
550        non-UTF 16-bit or 32-bit modes caused an internal error when PCRE was
551        compiled to use the heap for recursion.
552    
553    44. Got rid of some compiler warnings for unused variables when UTF but not UCP
554        is configured.
555    
556    
557    Version 8.33 28-May-2013
558    ------------------------
559    
560    1.  Added 'U' to some constants that are compared to unsigned integers, to
561        avoid compiler signed/unsigned warnings. Added (int) casts to unsigned
562        variables that are added to signed variables, to ensure the result is
563        signed and can be negated.
564    
565    2.  Applied patch by Daniel Richard G for quashing MSVC warnings to the
566        CMake config files.
567    
568    3.  Revise the creation of config.h.generic so that all boolean macros are
569        #undefined, whereas non-boolean macros are #ifndef/#endif-ed. This makes
570        overriding via -D on the command line possible.
571    
572    4.  Changing the definition of the variable "op" in pcre_exec.c from pcre_uchar
573        to unsigned int is reported to make a quite noticeable speed difference in
574        a specific Windows environment. Testing on Linux did also appear to show
575        some benefit (and it is clearly not harmful). Also fixed the definition of
576        Xop which should be unsigned.
577    
578    5.  Related to (4), changing the definition of the intermediate variable cc
579        in repeated character loops from pcre_uchar to pcre_uint32 also gave speed
580        improvements.
581    
582    6.  Fix forward search in JIT when link size is 3 or greater. Also removed some
583        unnecessary spaces.
584    
585    7.  Adjust autogen.sh and configure.ac to lose warnings given by automake 1.12
586        and later.
587    
588    8.  Fix two buffer over read issues in 16 and 32 bit modes. Affects JIT only.
589    
590    9.  Optimizing fast_forward_start_bits in JIT.
591    
592    10. Adding support for callouts in JIT, and fixing some issues revealed
593        during this work. Namely:
594    
595        (a) Unoptimized capturing brackets incorrectly reset on backtrack.
596    
597        (b) Minimum length was not checked before the matching is started.
598    
599    11. The value of capture_last that is passed to callouts was incorrect in some
600        cases when there was a capture on one path that was subsequently abandoned
601        after a backtrack. Also, the capture_last value is now reset after a
602        recursion, since all captures are also reset in this case.
603    
604    12. The interpreter no longer returns the "too many substrings" error in the
605        case when an overflowing capture is in a branch that is subsequently
606        abandoned after a backtrack.
607    
608    13. In the pathological case when an offset vector of size 2 is used, pcretest
609        now prints out the matched string after a yield of 0 or 1.
610    
611    14. Inlining subpatterns in recursions, when certain conditions are fulfilled.
612        Only supported by the JIT compiler at the moment.
613    
614    15. JIT compiler now supports 32 bit Macs thanks to Lawrence Velazquez.
615    
616    16. Partial matches now set offsets[2] to the "bumpalong" value, that is, the
617        offset of the starting point of the matching process, provided the offsets
618        vector is large enough.
619    
620    17. The \A escape now records a lookbehind value of 1, though its execution
621        does not actually inspect the previous character. This is to ensure that,
622        in partial multi-segment matching, at least one character from the old
623        segment is retained when a new segment is processed. Otherwise, if there
624        are no lookbehinds in the pattern, \A might match incorrectly at the start
625        of a new segment.
626    
627    18. Added some #ifdef __VMS code into pcretest.c to help VMS implementations.
628    
629    19. Redefined some pcre_uchar variables in pcre_exec.c as pcre_uint32; this
630        gives some modest performance improvement in 8-bit mode.
631    
632    20. Added the PCRE-specific property \p{Xuc} for matching characters that can
633        be expressed in certain programming languages using Universal Character
634        Names.
635    
636    21. Unicode validation has been updated in the light of Unicode Corrigendum #9,
637        which points out that "non characters" are not "characters that may not
638        appear in Unicode strings" but rather "characters that are reserved for
639        internal use and have only local meaning".
640    
641    22. When a pattern was compiled with automatic callouts (PCRE_AUTO_CALLOUT) and
642        there was a conditional group that depended on an assertion, if the
643        assertion was false, the callout that immediately followed the alternation
644        in the condition was skipped when pcre_exec() was used for matching.
645    
646    23. Allow an explicit callout to be inserted before an assertion that is the
647        condition for a conditional group, for compatibility with automatic
648        callouts, which always insert a callout at this point.
649    
650    24. In 8.31, (*COMMIT) was confined to within a recursive subpattern. Perl also
651        confines (*SKIP) and (*PRUNE) in the same way, and this has now been done.
652    
653    25. (*PRUNE) is now supported by the JIT compiler.
654    
655    26. Fix infinite loop when /(?<=(*SKIP)ac)a/ is matched against aa.
656    
657    27. Fix the case where there are two or more SKIPs with arguments that may be
658        ignored.
659    
660    28. (*SKIP) is now supported by the JIT compiler.
661    
662    29. (*THEN) is now supported by the JIT compiler.
663    
664    30. Update RunTest with additional test selector options.
665    
666    31. The way PCRE handles backtracking verbs has been changed in two ways.
667    
668        (1) Previously, in something like (*COMMIT)(*SKIP), COMMIT would override
669        SKIP. Now, PCRE acts on whichever backtracking verb is reached first by
670        backtracking. In some cases this makes it more Perl-compatible, but Perl's
671        rather obscure rules do not always do the same thing.
672    
673        (2) Previously, backtracking verbs were confined within assertions. This is
674        no longer the case for positive assertions, except for (*ACCEPT). Again,
675        this sometimes improves Perl compatibility, and sometimes does not.
676    
677    32. A number of tests that were in test 2 because Perl did things differently
678        have been moved to test 1, because either Perl or PCRE has changed, and
679        these tests are now compatible.
680    
681    32. Backtracking control verbs are now handled in the same way in JIT and
682        interpreter.
683    
684    33. An opening parenthesis in a MARK/PRUNE/SKIP/THEN name in a pattern that
685        contained a forward subroutine reference caused a compile error.
686    
687    34. Auto-detect and optimize limited repetitions in JIT.
688    
689    35. Implement PCRE_NEVER_UTF to lock out the use of UTF, in particular,
690        blocking (*UTF) etc.
691    
692    36. In the interpreter, maximizing pattern repetitions for characters and
693        character types now use tail recursion, which reduces stack usage.
694    
695    37. The value of the max lookbehind was not correctly preserved if a compiled
696        and saved regex was reloaded on a host of different endianness.
697    
698    38. Implemented (*LIMIT_MATCH) and (*LIMIT_RECURSION). As part of the extension
699        of the compiled pattern block, expand the flags field from 16 to 32 bits
700        because it was almost full.
701    
702    39. Try madvise first before posix_madvise.
703    
704    40. Change 7 for PCRE 7.9 made it impossible for pcregrep to find empty lines
705        with a pattern such as ^$. It has taken 4 years for anybody to notice! The
706        original change locked out all matches of empty strings. This has been
707        changed so that one match of an empty string per line is recognized.
708        Subsequent searches on the same line (for colouring or for --only-matching,
709        for example) do not recognize empty strings.
710    
711    41. Applied a user patch to fix a number of spelling mistakes in comments.
712    
713    42. Data lines longer than 65536 caused pcretest to crash.
714    
715    43. Clarified the data type for length and startoffset arguments for pcre_exec
716        and pcre_dfa_exec in the function-specific man pages, where they were
717        explicitly stated to be in bytes, never having been updated. I also added
718        some clarification to the pcreapi man page.
719    
720    44. A call to pcre_dfa_exec() with an output vector size less than 2 caused
721        a segmentation fault.
722    
723    
724    Version 8.32 30-November-2012
725    -----------------------------
726    
727    1.  Improved JIT compiler optimizations for first character search and single
728        character iterators.
729    
730    2.  Supporting IBM XL C compilers for PPC architectures in the JIT compiler.
731        Patch by Daniel Richard G.
732    
733    3.  Single character iterator optimizations in the JIT compiler.
734    
735    4.  Improved JIT compiler optimizations for character ranges.
736    
737    5.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.
738        Reported by Giuseppe D'Angelo.
739    
740    6.  The PCRE_STARTLINE bit, indicating that a match can occur only at the start
741        of a line, was being set incorrectly in cases where .* appeared inside
742        atomic brackets at the start of a pattern, or where there was a subsequent
743        *PRUNE or *SKIP.
744    
745    7.  Improved instruction cache flush for POWER/PowerPC.
746        Patch by Daniel Richard G.
747    
748    8.  Fixed a number of issues in pcregrep, making it more compatible with GNU
749        grep:
750    
751        (a) There is now no limit to the number of patterns to be matched.
752    
753        (b) An error is given if a pattern is too long.
754    
755        (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir
756            are now supported.
757    
758        (d) --exclude-from and --include-from (multiple use) have been added.
759    
760        (e) Exclusions and inclusions now apply to all files and directories, not
761            just to those obtained from scanning a directory recursively.
762    
763        (f) Multiple uses of -f and --file-list are now supported.
764    
765        (g) In a Windows environment, the default for -d has been changed from
766            "read" (the GNU grep default) to "skip", because otherwise the presence
767            of a directory in the file list provokes an error.
768    
769        (h) The documentation has been revised and clarified in places.
770    
771    9.  Improve the matching speed of capturing brackets.
772    
773    10. Changed the meaning of \X so that it now matches a Unicode extended
774        grapheme cluster.
775    
776    11. Patch by Daniel Richard G to the autoconf files to add a macro for sorting
777        out POSIX threads when JIT support is configured.
778    
779    12. Added support for PCRE_STUDY_EXTRA_NEEDED.
780    
781    13. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg
782        structure could go wrong in environments where size_t is not the same size
783        as int.
784    
785    14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be
786        set.
787    
788    15. The EBCDIC support had decayed; later updates to the code had included
789        explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a
790        general tidy up of EBCDIC-related issues, and the documentation was also
791        not quite right. There is now a test that can be run on ASCII systems to
792        check some of the EBCDIC-related things (but is it not a full test).
793    
794    16. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting
795        in a small tidy to the code.
796    
797    17. Fix JIT tests when UTF is disabled and both 8 and 16 bit mode are enabled.
798    
799    18. If the --only-matching (-o) option in pcregrep is specified multiple
800        times, each one causes appropriate output. For example, -o1 -o2 outputs the
801        substrings matched by the 1st and 2nd capturing parentheses. A separating
802        string can be specified by --om-separator (default empty).
803    
804    19. Improving the first n character searches.
805    
806    20. Turn case lists for horizontal and vertical white space into macros so that
807        they are defined only once.
808    
809    21. This set of changes together give more compatible Unicode case-folding
810        behaviour for characters that have more than one other case when UCP
811        support is available.
812    
813        (a) The Unicode property table now has offsets into a new table of sets of
814            three or more characters that are case-equivalent. The MultiStage2.py
815            script that generates these tables (the pcre_ucd.c file) now scans
816            CaseFolding.txt instead of UnicodeData.txt for character case
817            information.
818    
819        (b) The code for adding characters or ranges of characters to a character
820            class has been abstracted into a generalized function that also handles
821            case-independence. In UTF-mode with UCP support, this uses the new data
822            to handle characters with more than one other case.
823    
824        (c) A bug that is fixed as a result of (b) is that codepoints less than 256
825            whose other case is greater than 256 are now correctly matched
826            caselessly. Previously, the high codepoint matched the low one, but not
827            vice versa.
828    
829        (d) The processing of \h, \H, \v, and \ in character classes now makes use
830            of the new class addition function, using character lists defined as
831            macros alongside the case definitions of 20 above.
832    
833        (e) Caseless back references now work with characters that have more than
834            one other case.
835    
836        (f) General caseless matching of characters with more than one other case
837            is supported.
838    
839    22. Unicode character properties were updated from Unicode 6.2.0
840    
841    23. Improved CMake support under Windows. Patch by Daniel Richard G.
842    
843    24. Add support for 32-bit character strings, and UTF-32
844    
845    25. Major JIT compiler update (code refactoring and bugfixing).
846        Experimental Sparc 32 support is added.
847    
848    26. Applied a modified version of Daniel Richard G's patch to create
849        pcre.h.generic and config.h.generic by "make" instead of in the
850        PrepareRelease script.
851    
852    27. Added a definition for CHAR_NULL (helpful for the z/OS port), and use it in
853        pcre_compile.c when checking for a zero character.
854    
855    28. Introducing a native interface for JIT. Through this interface, the compiled
856        machine code can be directly executed. The purpose of this interface is to
857        provide fast pattern matching, so several sanity checks are not performed.
858        However, feature tests are still performed. The new interface provides
859        1.4x speedup compared to the old one.
860    
861    29. If pcre_exec() or pcre_dfa_exec() was called with a negative value for
862        the subject string length, the error given was PCRE_ERROR_BADOFFSET, which
863        was confusing. There is now a new error PCRE_ERROR_BADLENGTH for this case.
864    
865    30. In 8-bit UTF-8 mode, pcretest failed to give an error for data codepoints
866        greater than 0x7fffffff (which cannot be represented in UTF-8, even under
867        the "old" RFC 2279). Instead, it ended up passing a negative length to
868        pcre_exec().
869    
870    31. Add support for GCC's visibility feature to hide internal functions.
871    
872    32. Running "pcretest -C pcre8" or "pcretest -C pcre16" gave a spurious error
873        "unknown -C option" after outputting 0 or 1.
874    
875    33. There is now support for generating a code coverage report for the test
876        suite in environments where gcc is the compiler and lcov is installed. This
877        is mainly for the benefit of the developers.
878    
879    34. If PCRE is built with --enable-valgrind, certain memory regions are marked
880        unaddressable using valgrind annotations, allowing valgrind to detect
881        invalid memory accesses. This is mainly for the benefit of the developers.
882    
883    25. (*UTF) can now be used to start a pattern in any of the three libraries.
884    
885    26. Give configure error if --enable-cpp but no C++ compiler found.
886    
887    
888    Version 8.31 06-July-2012
889    -------------------------
890    
891    1.  Fixing a wrong JIT test case and some compiler warnings.
892    
893    2.  Removed a bashism from the RunTest script.
894    
895    3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied
896        to unsigned type, result still unsigned" that was given by an MS compiler
897        on encountering the code "-sizeof(xxx)".
898    
899    4.  Partial matching support is added to the JIT compiler.
900    
901    5.  Fixed several bugs concerned with partial matching of items that consist
902        of more than one character:
903    
904        (a) /^(..)\1/ did not partially match "aba" because checking references was
905            done on an "all or nothing" basis. This also applied to repeated
906            references.
907    
908        (b) \R did not give a hard partial match if \r was found at the end of the
909            subject.
910    
911        (c) \X did not give a hard partial match after matching one or more
912            characters at the end of the subject.
913    
914        (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize
915            a partial match for the string "\r".
916    
917        (e) When newline was set to CRLF, the metacharacter "." did not recognize
918            a partial match for a CR character at the end of the subject string.
919    
920    6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when
921        running pcretest, the text "(JIT)" added to the output whenever JIT is
922        actually used to run the match.
923    
924    7.  Individual JIT compile options can be set in pcretest by following -s+[+]
925        or /S+[+] with a digit between 1 and 7.
926    
927    8.  OP_NOT now supports any UTF character not just single-byte ones.
928    
929    9.  (*MARK) control verb is now supported by the JIT compiler.
930    
931    10. The command "./RunTest list" lists the available tests without actually
932        running any of them. (Because I keep forgetting what they all are.)
933    
934    11. Add PCRE_INFO_MAXLOOKBEHIND.
935    
936    12. Applied a (slightly modified) user-supplied patch that improves performance
937        when the heap is used for recursion (compiled with --disable-stack-for-
938        recursion). Instead of malloc and free for each heap frame each time a
939        logical recursion happens, frames are retained on a chain and re-used where
940        possible. This sometimes gives as much as 30% improvement.
941    
942    13. As documented, (*COMMIT) is now confined to within a recursive subpattern
943        call.
944    
945    14. As documented, (*COMMIT) is now confined to within a positive assertion.
946    
947    15. It is now possible to link pcretest with libedit as an alternative to
948        libreadline.
949    
950    16. (*COMMIT) control verb is now supported by the JIT compiler.
951    
952    17. The Unicode data tables have been updated to Unicode 6.1.0.
953    
954    18. Added --file-list option to pcregrep.
955    
956    19. Added binary file support to pcregrep, including the -a, --binary-files,
957        -I, and --text options.
958    
959    20. The madvise function is renamed for posix_madvise for QNX compatibility
960        reasons. Fixed by Giuseppe D'Angelo.
961    
962    21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
963    
964    22. Changed the option for creating symbolic links for 16-bit man pages from
965        -s to -sf so that re-installing does not cause issues.
966    
967    23. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it.
968    
969    24. Fixed a very old bug in pcretest that caused errors with restarted DFA
970        matches in certain environments (the workspace was not being correctly
971        retained). Also added to pcre_dfa_exec() a simple plausibility check on
972        some of the workspace data at the beginning of a restart.
973    
974    25. \s*\R was auto-possessifying the \s* when it should not, whereas \S*\R
975        was not doing so when it should - probably a typo introduced by SVN 528
976        (change 8.10/14).
977    
978    26. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the
979        \w+ when the character tables indicated that \x{c4} was a word character.
980        There were several related cases, all because the tests for doing a table
981        lookup were testing for characters less than 127 instead of 255.
982    
983    27. If a pattern contains capturing parentheses that are not used in a match,
984        their slots in the ovector are set to -1. For those that are higher than
985        any matched groups, this happens at the end of processing. In the case when
986        there were back references that the ovector was too small to contain
987        (causing temporary malloc'd memory to be used during matching), and the
988        highest capturing number was not used, memory off the end of the ovector
989        was incorrectly being set to -1. (It was using the size of the temporary
990        memory instead of the true size.)
991    
992    28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
993        ovector size, it uses memory at the end of the block that it has got.
994    
995    29. Check for an overlong MARK name and give an error at compile time. The
996        limit is 255 for the 8-bit library and 65535 for the 16-bit library.
997    
998    30. JIT compiler update.
999    
1000    31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
1001        Rill for the patch.
1002    
1003    32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
1004    
1005    33. Variable renamings in the PCRE-JIT compiler. No functionality change.
1006    
1007    34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
1008        SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
1009        was enabled.
1010    
1011    35. Improve JIT code generation for greedy plus quantifier.
1012    
1013    36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
1014        1 to "aa" instead of to an empty string. The bug affected repeated groups
1015        that could potentially match an empty string.
1016    
1017    37. Optimizing single character iterators in JIT.
1018    
1019    38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
1020        the same checks as \x{...} characters in non-JavaScript mode. Specifically,
1021        codepoints that are too big for the mode are faulted, and in a UTF mode,
1022        disallowed codepoints are also faulted.
1023    
1024    39. If PCRE was compiled with UTF support, in three places in the DFA
1025        matcher there was code that should only have been obeyed in UTF mode, but
1026        was being obeyed unconditionally. In 8-bit mode this could cause incorrect
1027        processing when bytes with values greater than 127 were present. In 16-bit
1028        mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
1029        both cases the values are those that cannot be the first data item in a UTF
1030        character. The three items that might have provoked this were recursions,
1031        possessively repeated groups, and atomic groups.
1032    
1033    40. Ensure that libpcre is explicitly listed in the link commands for pcretest
1034        and pcregrep, because some OS require shared objects to be explicitly
1035        passed to ld, causing the link step to fail if they are not.
1036    
1037    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
1038        mode, patterns that started with \h* or \R* might be incorrectly matched.
1039    
1040    
1041    Version 8.30 04-February-2012
1042    -----------------------------
1043    
1044    1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
1045        name is defined in ctype.h.
1046    
1047    2.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
1048        only in quite long subpatterns.
1049    
1050    3.  Removed the function pcre_info(), which has been obsolete and deprecated
1051        since it was replaced by pcre_fullinfo() in February 2000.
1052    
1053    4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
1054        match a (*MARK), and the match failed at the start of the subject, a
1055        reference to memory before the start of the subject could occur. This bug
1056        was introduced by fix 17 of release 8.21.
1057    
1058    5.  A reference to an unset group with zero minimum repetition was giving
1059        totally wrong answers (in non-JavaScript-compatibility mode). For example,
1060        /(another)?(\1?)test/ matched against "hello world test". This bug was
1061        introduced in release 8.13.
1062    
1063    6.  Add support for 16-bit character strings (a large amount of work involving
1064        many changes and refactorings).
1065    
1066    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
1067        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
1068        from a file.
1069    
1070    8.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
1071        rounding is not applied in this particular case).
1072    
1073    9.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
1074        if they appear, or are escaped, in patterns.
1075    
1076    10. Get rid of a number of -Wunused-but-set-variable warnings.
1077    
1078    11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
1079        "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
1080        Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
1081        also returns the mark "x". This bug applied to capturing parentheses,
1082        non-capturing parentheses, and atomic parentheses. It also applied to some
1083        assertions.
1084    
1085    12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
1086        information out of configure.ac instead of relying on pcre.h.generic, which
1087        is not stored in the repository.
1088    
1089    13. Applied Dmitry V. Levin's patch for a more portable method for linking with
1090        -lreadline.
1091    
1092    14. ZH added PCRE_CONFIG_JITTARGET; added its output to pcretest -C.
1093    
1094    15. Applied Graycode's patch to put the top-level frame on the stack rather
1095        than the heap when not using the stack for recursion. This gives a
1096        performance improvement in many cases when recursion is not deep.
1097    
1098    16. Experimental code added to "pcretest -C" to output the stack frame size.
1099    
1100    
1101    Version 8.21 12-Dec-2011
1102    ------------------------
1103    
1104    1.  Updating the JIT compiler.
1105    
1106    2.  JIT compiler now supports OP_NCREF, OP_RREF and OP_NRREF. New test cases
1107        are added as well.
1108    
1109    3.  Fix cache-flush issue on PowerPC (It is still an experimental JIT port).
1110        PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before
1111        calling _pcre_jit_exec. Some extra comments are added.
1112    
1113    4.  (*MARK) settings inside atomic groups that do not contain any capturing
1114        parentheses, for example, (?>a(*:m)), were not being passed out. This bug
1115        was introduced by change 18 for 8.20.
1116    
1117    5.  Supporting of \x, \U and \u in JavaScript compatibility mode based on the
1118        ECMA-262 standard.
1119    
1120    6.  Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were
1121        erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
1122        This bug was probably introduced by change 9 of 8.13.
1123    
1124    7.  While fixing 6 above, I noticed that a number of other items were being
1125        incorrectly rejected as "not fixed length". This arose partly because newer
1126        opcodes had not been added to the fixed-length checking code. I have (a)
1127        corrected the bug and added tests for these items, and (b) arranged for an
1128        error to occur if an unknown opcode is encountered while checking for fixed
1129        length instead of just assuming "not fixed length". The items that were
1130        rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
1131        (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
1132        repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
1133    
1134    8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
1135        being incorrectly compiled and would have given unpredicatble results.
1136    
1137    9.  A possessively repeated subpattern with minimum repeat count greater than
1138        one behaved incorrectly. For example, (A){2,}+ behaved as if it was
1139        (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
1140        the first (A) could occur when it should not.
1141    
1142    10. Add a cast and remove a redundant test from the code.
1143    
1144    11. JIT should use pcre_malloc/pcre_free for allocation.
1145    
1146    12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems
1147        best practice nowadays, and helps with cross-compiling. (If the exec_prefix
1148        is anything other than /usr, -L is still shown).
1149    
1150    13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.
1151    
1152    14. Perl does not support \N without a following name in a [] class; PCRE now
1153        also gives an error.
1154    
1155    15. If a forward reference was repeated with an upper limit of around 2000,
1156        it caused the error "internal error: overran compiling workspace". The
1157        maximum number of forward references (including repeats) was limited by the
1158        internal workspace, and dependent on the LINK_SIZE. The code has been
1159        rewritten so that the workspace expands (via pcre_malloc) if necessary, and
1160        the default depends on LINK_SIZE. There is a new upper limit (for safety)
1161        of around 200,000 forward references. While doing this, I also speeded up
1162        the filling in of repeated forward references.
1163    
1164    16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
1165        incorrectly expecting the subject to contain another "a" after the start.
1166    
1167    17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
1168        in the match, the SKIP should be ignored. This was not happening; instead
1169        the SKIP was being treated as NOMATCH. For patterns such as
1170        /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
1171        tested.
1172    
1173    18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
1174        now much more compatible with Perl, in particular in cases where the result
1175        is a non-match for a non-anchored pattern. For example, if
1176        /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
1177        "m", where previously it did not return a name. A side effect of this
1178        change is that for partial matches, the last encountered mark name is
1179        returned, as for non matches. A number of tests that were previously not
1180        Perl-compatible have been moved into the Perl-compatible test files. The
1181        refactoring has had the pleasing side effect of removing one argument from
1182        the match() function, thus reducing its stack requirements.
1183    
1184    19. If the /S+ option was used in pcretest to study a pattern using JIT,
1185        subsequent uses of /S (without +) incorrectly behaved like /S+.
1186    
1187    21. Retrieve executable code size support for the JIT compiler and fixing
1188        some warnings.
1189    
1190    22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
1191        not work when the shorter character appeared right at the end of the
1192        subject string.
1193    
1194    23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
1195        systems.
1196    
1197    24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
1198        output it when the /M option is used in pcretest.
1199    
1200    25. The CheckMan script was not being included in the distribution. Also, added
1201        an explicit "perl" to run Perl scripts from the PrepareRelease script
1202        because this is reportedly needed in Windows.
1203    
1204    26. If study data was being save in a file and studying had not found a set of
1205        "starts with" bytes for the pattern, the data written to the file (though
1206        never used) was taken from uninitialized memory and so caused valgrind to
1207        complain.
1208    
1209    27. Updated RunTest.bat as provided by Sheri Pierce.
1210    
1211    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
1212    
1213    29. Computation of memory usage for the table of capturing group names was
1214        giving an unnecessarily large value.
1215    
1216    
1217    Version 8.20 21-Oct-2011
1218    ------------------------
1219    
1220    1.  Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had
1221        a POSIX class. After further experiments with Perl, which convinced me that
1222        Perl has bugs and confusions, a closing square bracket is no longer allowed
1223        in a POSIX name. This bug also affected patterns with classes that started
1224        with full stops.
1225    
1226    2.  If a pattern such as /(a)b|ac/ is matched against "ac", there is no
1227        captured substring, but while checking the failing first alternative,
1228        substring 1 is temporarily captured. If the output vector supplied to
1229        pcre_exec() was not big enough for this capture, the yield of the function
1230        was still zero ("insufficient space for captured substrings"). This cannot
1231        be totally fixed without adding another stack variable, which seems a lot
1232        of expense for a edge case. However, I have improved the situation in cases
1233        such as /(a)(b)x|abc/ matched against "abc", where the return code
1234        indicates that fewer than the maximum number of slots in the ovector have
1235        been set.
1236    
1237    3.  Related to (2) above: when there are more back references in a pattern than
1238        slots in the output vector, pcre_exec() uses temporary memory during
1239        matching, and copies in the captures as far as possible afterwards. It was
1240        using the entire output vector, but this conflicts with the specification
1241        that only 2/3 is used for passing back captured substrings. Now it uses
1242        only the first 2/3, for compatibility. This is, of course, another edge
1243        case.
1244    
1245    4.  Zoltan Herczeg's just-in-time compiler support has been integrated into the
1246        main code base, and can be used by building with --enable-jit. When this is
1247        done, pcregrep automatically uses it unless --disable-pcregrep-jit or the
1248        runtime --no-jit option is given.
1249    
1250    5.  When the number of matches in a pcre_dfa_exec() run exactly filled the
1251        ovector, the return from the function was zero, implying that there were
1252        other matches that did not fit. The correct "exactly full" value is now
1253        returned.
1254    
1255    6.  If a subpattern that was called recursively or as a subroutine contained
1256        (*PRUNE) or any other control that caused it to give a non-standard return,
1257        invalid errors such as "Error -26 (nested recursion at the same subject
1258        position)" or even infinite loops could occur.
1259    
1260    7.  If a pattern such as /a(*SKIP)c|b(*ACCEPT)|/ was studied, it stopped
1261        computing the minimum length on reaching *ACCEPT, and so ended up with the
1262        wrong value of 1 rather than 0. Further investigation indicates that
1263        computing a minimum subject length in the presence of *ACCEPT is difficult
1264        (think back references, subroutine calls), and so I have changed the code
1265        so that no minimum is registered for a pattern that contains *ACCEPT.
1266    
1267    8.  If (*THEN) was present in the first (true) branch of a conditional group,
1268        it was not handled as intended. [But see 16 below.]
1269    
1270    9.  Replaced RunTest.bat and CMakeLists.txt with improved versions provided by
1271        Sheri Pierce.
1272    
1273    10. A pathological pattern such as /(*ACCEPT)a/ was miscompiled, thinking that
1274        the first byte in a match must be "a".
1275    
1276    11. Change 17 for 8.13 increased the recursion depth for patterns like
1277        /a(?:.)*?a/ drastically. I've improved things by remembering whether a
1278        pattern contains any instances of (*THEN). If it does not, the old
1279        optimizations are restored. It would be nice to do this on a per-group
1280        basis, but at the moment that is not feasible.
1281    
1282    12. In some environments, the output of pcretest -C is CRLF terminated. This
1283        broke RunTest's code that checks for the link size. A single white space
1284        character after the value is now allowed for.
1285    
1286    13. RunTest now checks for the "fr" locale as well as for "fr_FR" and "french".
1287        For "fr", it uses the Windows-specific input and output files.
1288    
1289    14. If (*THEN) appeared in a group that was called recursively or as a
1290        subroutine, it did not work as intended. [But see next item.]
1291    
1292    15. Consider the pattern /A (B(*THEN)C) | D/ where A, B, C, and D are complex
1293        pattern fragments (but not containing any | characters). If A and B are
1294        matched, but there is a failure in C so that it backtracks to (*THEN), PCRE
1295        was behaving differently to Perl. PCRE backtracked into A, but Perl goes to
1296        D. In other words, Perl considers parentheses that do not contain any |
1297        characters to be part of a surrounding alternative, whereas PCRE was
1298        treading (B(*THEN)C) the same as (B(*THEN)C|(*FAIL)) -- which Perl handles
1299        differently. PCRE now behaves in the same way as Perl, except in the case
1300        of subroutine/recursion calls such as (?1) which have in any case always
1301        been different (but PCRE had them first :-).
1302    
1303    16. Related to 15 above: Perl does not treat the | in a conditional group as
1304        creating alternatives. Such a group is treated in the same way as an
1305        ordinary group without any | characters when processing (*THEN). PCRE has
1306        been changed to match Perl's behaviour.
1307    
1308    17. If a user had set PCREGREP_COLO(U)R to something other than 1:31, the
1309        RunGrepTest script failed.
1310    
1311    18. Change 22 for version 13 caused atomic groups to use more stack. This is
1312        inevitable for groups that contain captures, but it can lead to a lot of
1313        stack use in large patterns. The old behaviour has been restored for atomic
1314        groups that do not contain any capturing parentheses.
1315    
1316    19. If the PCRE_NO_START_OPTIMIZE option was set for pcre_compile(), it did not
1317        suppress the check for a minimum subject length at run time. (If it was
1318        given to pcre_exec() or pcre_dfa_exec() it did work.)
1319    
1320    20. Fixed an ASCII-dependent infelicity in pcretest that would have made it
1321        fail to work when decoding hex characters in data strings in EBCDIC
1322        environments.
1323    
1324    21. It appears that in at least one Mac OS environment, the isxdigit() function
1325        is implemented as a macro that evaluates to its argument more than once,
1326        contravening the C 90 Standard (I haven't checked a later standard). There
1327        was an instance in pcretest which caused it to go wrong when processing
1328        \x{...} escapes in subject strings. The has been rewritten to avoid using
1329        things like p++ in the argument of isxdigit().
1330    
1331    
1332    Version 8.13 16-Aug-2011
1333    ------------------------
1334    
1335    1.  The Unicode data tables have been updated to Unicode 6.0.0.
1336    
1337    2.  Two minor typos in pcre_internal.h have been fixed.
1338    
1339    3.  Added #include <string.h> to pcre_scanner_unittest.cc, pcrecpp.cc, and
1340        pcrecpp_unittest.cc. They are needed for strcmp(), memset(), and strchr()
1341        in some environments (e.g. Solaris 10/SPARC using Sun Studio 12U2).
1342    
1343    4.  There were a number of related bugs in the code for matching backrefences
1344        caselessly in UTF-8 mode when codes for the characters concerned were
1345        different numbers of bytes. For example, U+023A and U+2C65 are an upper
1346        and lower case pair, using 2 and 3 bytes, respectively. The main bugs were:
1347        (a) A reference to 3 copies of a 2-byte code matched only 2 of a 3-byte
1348        code. (b) A reference to 2 copies of a 3-byte code would not match 2 of a
1349        2-byte code at the end of the subject (it thought there wasn't enough data
1350        left).
1351    
1352    5.  Comprehensive information about what went wrong is now returned by
1353        pcre_exec() and pcre_dfa_exec() when the UTF-8 string check fails, as long
1354        as the output vector has at least 2 elements. The offset of the start of
1355        the failing character and a reason code are placed in the vector.
1356    
1357    6.  When the UTF-8 string check fails for pcre_compile(), the offset that is
1358        now returned is for the first byte of the failing character, instead of the
1359        last byte inspected. This is an incompatible change, but I hope it is small
1360        enough not to be a problem. It makes the returned offset consistent with
1361        pcre_exec() and pcre_dfa_exec().
1362    
1363    7.  pcretest now gives a text phrase as well as the error number when
1364        pcre_exec() or pcre_dfa_exec() fails; if the error is a UTF-8 check
1365        failure, the offset and reason code are output.
1366    
1367    8.  When \R was used with a maximizing quantifier it failed to skip backwards
1368        over a \r\n pair if the subsequent match failed. Instead, it just skipped
1369        back over a single character (\n). This seems wrong (because it treated the
1370        two characters as a single entity when going forwards), conflicts with the
1371        documentation that \R is equivalent to (?>\r\n|\n|...etc), and makes the
1372        behaviour of \R* different to (\R)*, which also seems wrong. The behaviour
1373        has been changed.
1374    
1375    9.  Some internal refactoring has changed the processing so that the handling
1376        of the PCRE_CASELESS and PCRE_MULTILINE options is done entirely at compile
1377        time (the PCRE_DOTALL option was changed this way some time ago: version
1378        7.7 change 16). This has made it possible to abolish the OP_OPT op code,
1379        which was always a bit of a fudge. It also means that there is one less
1380        argument for the match() function, which reduces its stack requirements
1381        slightly. This change also fixes an incompatibility with Perl: the pattern
1382        (?i:([^b]))(?1) should not match "ab", but previously PCRE gave a match.
1383    
1384    10. More internal refactoring has drastically reduced the number of recursive
1385        calls to match() for possessively repeated groups such as (abc)++ when
1386        using pcre_exec().
1387    
1388    11. While implementing 10, a number of bugs in the handling of groups were
1389        discovered and fixed:
1390    
1391        (?<=(a)+) was not diagnosed as invalid (non-fixed-length lookbehind).
1392        (a|)*(?1) gave a compile-time internal error.
1393        ((a|)+)+  did not notice that the outer group could match an empty string.
1394        (^a|^)+   was not marked as anchored.
1395        (.*a|.*)+ was not marked as matching at start or after a newline.
1396    
1397    12. Yet more internal refactoring has removed another argument from the match()
1398        function. Special calls to this function are now indicated by setting a
1399        value in a variable in the "match data" data block.
1400    
1401    13. Be more explicit in pcre_study() instead of relying on "default" for
1402        opcodes that mean there is no starting character; this means that when new
1403        ones are added and accidentally left out of pcre_study(), testing should
1404        pick them up.
1405    
1406    14. The -s option of pcretest has been documented for ages as being an old
1407        synonym of -m (show memory usage). I have changed it to mean "force study
1408        for every regex", that is, assume /S for every regex. This is similar to -i
1409        and -d etc. It's slightly incompatible, but I'm hoping nobody is still
1410        using it. It makes it easier to run collections of tests with and without
1411        study enabled, and thereby test pcre_study() more easily. All the standard
1412        tests are now run with and without -s (but some patterns can be marked as
1413        "never study" - see 20 below).
1414    
1415    15. When (*ACCEPT) was used in a subpattern that was called recursively, the
1416        restoration of the capturing data to the outer values was not happening
1417        correctly.
1418    
1419    16. If a recursively called subpattern ended with (*ACCEPT) and matched an
1420        empty string, and PCRE_NOTEMPTY was set, pcre_exec() thought the whole
1421        pattern had matched an empty string, and so incorrectly returned a no
1422        match.
1423    
1424    17. There was optimizing code for the last branch of non-capturing parentheses,
1425        and also for the obeyed branch of a conditional subexpression, which used
1426        tail recursion to cut down on stack usage. Unfortunately, now that there is
1427        the possibility of (*THEN) occurring in these branches, tail recursion is
1428        no longer possible because the return has to be checked for (*THEN). These
1429        two optimizations have therefore been removed. [But see 8.20/11 above.]
1430    
1431    18. If a pattern containing \R was studied, it was assumed that \R always
1432        matched two bytes, thus causing the minimum subject length to be
1433        incorrectly computed because \R can also match just one byte.
1434    
1435    19. If a pattern containing (*ACCEPT) was studied, the minimum subject length
1436        was incorrectly computed.
1437    
1438    20. If /S is present twice on a test pattern in pcretest input, it now
1439        *disables* studying, thereby overriding the use of -s on the command line
1440        (see 14 above). This is necessary for one or two tests to keep the output
1441        identical in both cases.
1442    
1443    21. When (*ACCEPT) was used in an assertion that matched an empty string and
1444        PCRE_NOTEMPTY was set, PCRE applied the non-empty test to the assertion.
1445    
1446    22. When an atomic group that contained a capturing parenthesis was
1447        successfully matched, but the branch in which it appeared failed, the
1448        capturing was not being forgotten if a higher numbered group was later
1449        captured. For example, /(?>(a))b|(a)c/ when matching "ac" set capturing
1450        group 1 to "a", when in fact it should be unset. This applied to multi-
1451        branched capturing and non-capturing groups, repeated or not, and also to
1452        positive assertions (capturing in negative assertions does not happen
1453        in PCRE) and also to nested atomic groups.
1454    
1455    23. Add the ++ qualifier feature to pcretest, to show the remainder of the
1456        subject after a captured substring, to make it easier to tell which of a
1457        number of identical substrings has been captured.
1458    
1459    24. The way atomic groups are processed by pcre_exec() has been changed so that
1460        if they are repeated, backtracking one repetition now resets captured
1461        values correctly. For example, if ((?>(a+)b)+aabab) is matched against
1462        "aaaabaaabaabab" the value of captured group 2 is now correctly recorded as
1463        "aaa". Previously, it would have been "a". As part of this code
1464        refactoring, the way recursive calls are handled has also been changed.
1465    
1466    25. If an assertion condition captured any substrings, they were not passed
1467        back unless some other capturing happened later. For example, if
1468        (?(?=(a))a) was matched against "a", no capturing was returned.
1469    
1470    26. When studying a pattern that contained subroutine calls or assertions,
1471        the code for finding the minimum length of a possible match was handling
1472        direct recursions such as (xxx(?1)|yyy) but not mutual recursions (where
1473        group 1 called group 2 while simultaneously a separate group 2 called group
1474        1). A stack overflow occurred in this case. I have fixed this by limiting
1475        the recursion depth to 10.
1476    
1477    27. Updated RunTest.bat in the distribution to the version supplied by Tom
1478        Fortmann. This supports explicit test numbers on the command line, and has
1479        argument validation and error reporting.
1480    
1481    28. An instance of \X with an unlimited repeat could fail if at any point the
1482        first character it looked at was a mark character.
1483    
1484    29. Some minor code refactoring concerning Unicode properties and scripts
1485        should reduce the stack requirement of match() slightly.
1486    
1487    30. Added the '=' option to pcretest to check the setting of unused capturing
1488        slots at the end of the pattern, which are documented as being -1, but are
1489        not included in the return count.
1490    
1491    31. If \k was not followed by a braced, angle-bracketed, or quoted name, PCRE
1492        compiled something random. Now it gives a compile-time error (as does
1493        Perl).
1494    
1495    32. A *MARK encountered during the processing of a positive assertion is now
1496        recorded and passed back (compatible with Perl).
1497    
1498    33. If --only-matching or --colour was set on a pcregrep call whose pattern
1499        had alternative anchored branches, the search for a second match in a line
1500        was done as if at the line start. Thus, for example, /^01|^02/ incorrectly
1501        matched the line "0102" twice. The same bug affected patterns that started
1502        with a backwards assertion. For example /\b01|\b02/ also matched "0102"
1503        twice.
1504    
1505    34. Previously, PCRE did not allow quantification of assertions. However, Perl
1506        does, and because of capturing effects, quantifying parenthesized
1507        assertions may at times be useful. Quantifiers are now allowed for
1508        parenthesized assertions.
1509    
1510    35. A minor code tidy in pcre_compile() when checking options for \R usage.
1511    
1512    36. \g was being checked for fancy things in a character class, when it should
1513        just be a literal "g".
1514    
1515    37. PCRE was rejecting [:a[:digit:]] whereas Perl was not. It seems that the
1516        appearance of a nested POSIX class supersedes an apparent external class.
1517        For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,
1518        unescaped square brackets may also appear as part of class names. For
1519        example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves
1520        more like Perl. (But see 8.20/1 above.)
1521    
1522    38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this
1523        was because it thought it was \N{name}, which is not supported).
1524    
1525    39. Add minix to OS list not supporting the -S option in pcretest.
1526    
1527    40. PCRE tries to detect cases of infinite recursion at compile time, but it
1528        cannot analyze patterns in sufficient detail to catch mutual recursions
1529        such as ((?1))((?2)). There is now a runtime test that gives an error if a
1530        subgroup is called recursively as a subpattern for a second time at the
1531        same position in the subject string. In previous releases this might have
1532        been caught by the recursion limit, or it might have run out of stack.
1533    
1534    41. A pattern such as /(?(R)a+|(?R)b)/ is quite safe, as the recursion can
1535        happen only once. PCRE was, however incorrectly giving a compile time error
1536        "recursive call could loop indefinitely" because it cannot analyze the
1537        pattern in sufficient detail. The compile time test no longer happens when
1538        PCRE is compiling a conditional subpattern, but actual runaway loops are
1539        now caught at runtime (see 40 above).
1540    
1541    42. It seems that Perl allows any characters other than a closing parenthesis
1542        to be part of the NAME in (*MARK:NAME) and other backtracking verbs. PCRE
1543        has been changed to be the same.
1544    
1545    43. Updated configure.ac to put in more quoting round AC_LANG_PROGRAM etc. so
1546        as not to get warnings when autogen.sh is called. Also changed
1547        AC_PROG_LIBTOOL (deprecated) to LT_INIT (the current macro).
1548    
1549    44. To help people who use pcregrep to scan files containing exceedingly long
1550        lines, the following changes have been made:
1551    
1552        (a) The default value of the buffer size parameter has been increased from
1553            8K to 20K. (The actual buffer used is three times this size.)
1554    
1555        (b) The default can be changed by ./configure --with-pcregrep-bufsize when
1556            PCRE is built.
1557    
1558        (c) A --buffer-size=n option has been added to pcregrep, to allow the size
1559            to be set at run time.
1560    
1561        (d) Numerical values in pcregrep options can be followed by K or M, for
1562            example --buffer-size=50K.
1563    
1564        (e) If a line being scanned overflows pcregrep's buffer, an error is now
1565            given and the return code is set to 2.
1566    
1567    45. Add a pointer to the latest mark to the callout data block.
1568    
1569    46. The pattern /.(*F)/, when applied to "abc" with PCRE_PARTIAL_HARD, gave a
1570        partial match of an empty string instead of no match. This was specific to
1571        the use of ".".
1572    
1573    47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a
1574        complete match instead of a partial match. This bug was dependent on both
1575        the PCRE_UTF8 and PCRE_DOTALL options being set.
1576    
1577    48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the
1578        starting byte set, because \b was not being ignored.
1579    
1580    
1581    Version 8.12 15-Jan-2011
1582    ------------------------
1583    
1584    1.  Fixed some typos in the markup of the man pages, and wrote a script that
1585        checks for such things as part of the documentation building process.
1586    
1587    2.  On a big-endian 64-bit system, pcregrep did not correctly process the
1588        --match-limit and --recursion-limit options (added for 8.11). In
1589        particular, this made one of the standard tests fail. (The integer value
1590        went into the wrong half of a long int.)
1591    
1592    3.  If the --colour option was given to pcregrep with -v (invert match), it
1593        did strange things, either producing crazy output, or crashing. It should,
1594        of course, ignore a request for colour when reporting lines that do not
1595        match.
1596    
1597    4.  Another pcregrep bug caused similar problems if --colour was specified with
1598        -M (multiline) and the pattern match finished with a line ending.
1599    
1600    5.  In pcregrep, when a pattern that ended with a literal newline sequence was
1601        matched in multiline mode, the following line was shown as part of the
1602        match. This seems wrong, so I have changed it.
1603    
1604    6.  Another pcregrep bug in multiline mode, when --colour was specified, caused
1605        the check for further matches in the same line (so they could be coloured)
1606        to overrun the end of the current line. If another match was found, it was
1607        incorrectly shown (and then shown again when found in the next line).
1608    
1609    7.  If pcregrep was compiled under Windows, there was a reference to the
1610        function pcregrep_exit() before it was defined. I am assuming this was
1611        the cause of the "error C2371: 'pcregrep_exit' : redefinition;" that was
1612        reported by a user. I've moved the definition above the reference.
1613    
1614    
1615    Version 8.11 10-Dec-2010
1616    ------------------------
1617    
1618    1.  (*THEN) was not working properly if there were untried alternatives prior
1619        to it in the current branch. For example, in ((a|b)(*THEN)(*F)|c..) it
1620        backtracked to try for "b" instead of moving to the next alternative branch
1621        at the same level (in this case, to look for "c"). The Perl documentation
1622        is clear that when (*THEN) is backtracked onto, it goes to the "next
1623        alternative in the innermost enclosing group".
1624    
1625    2.  (*COMMIT) was not overriding (*THEN), as it does in Perl. In a pattern
1626        such as   (A(*COMMIT)B(*THEN)C|D)  any failure after matching A should
1627        result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and
1628        (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides
1629        (*THEN).
1630    
1631    3.  If \s appeared in a character class, it removed the VT character from
1632        the class, even if it had been included by some previous item, for example
1633        in [\x00-\xff\s]. (This was a bug related to the fact that VT is not part
1634        of \s, but is part of the POSIX "space" class.)
1635    
1636    4.  A partial match never returns an empty string (because you can always
1637        match an empty string at the end of the subject); however the checking for
1638        an empty string was starting at the "start of match" point. This has been
1639        changed to the "earliest inspected character" point, because the returned
1640        data for a partial match starts at this character. This means that, for
1641        example, /(?<=abc)def/ gives a partial match for the subject "abc"
1642        (previously it gave "no match").
1643    
1644    5.  Changes have been made to the way PCRE_PARTIAL_HARD affects the matching
1645        of $, \z, \Z, \b, and \B. If the match point is at the end of the string,
1646        previously a full match would be given. However, setting PCRE_PARTIAL_HARD
1647        has an implication that the given string is incomplete (because a partial
1648        match is preferred over a full match). For this reason, these items now
1649        give a partial match in this situation. [Aside: previously, the one case
1650        /t\b/ matched against "cat" with PCRE_PARTIAL_HARD set did return a partial
1651        match rather than a full match, which was wrong by the old rules, but is
1652        now correct.]
1653    
1654    6.  There was a bug in the handling of #-introduced comments, recognized when
1655        PCRE_EXTENDED is set, when PCRE_NEWLINE_ANY and PCRE_UTF8 were also set.
1656        If a UTF-8 multi-byte character included the byte 0x85 (e.g. +U0445, whose
1657        UTF-8 encoding is 0xd1,0x85), this was misinterpreted as a newline when
1658        scanning for the end of the comment. (*Character* 0x85 is an "any" newline,
1659        but *byte* 0x85 is not, in UTF-8 mode). This bug was present in several
1660        places in pcre_compile().
1661    
1662    7.  Related to (6) above, when pcre_compile() was skipping #-introduced
1663        comments when looking ahead for named forward references to subpatterns,
1664        the only newline sequence it recognized was NL. It now handles newlines
1665        according to the set newline convention.
1666    
1667    8.  SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the
1668        former, but used strtoul(), whereas pcretest avoided strtoul() but did not
1669        cater for a lack of strerror(). These oversights have been fixed.
1670    
1671    9.  Added --match-limit and --recursion-limit to pcregrep.
1672    
1673    10. Added two casts needed to build with Visual Studio when NO_RECURSE is set.
1674    
1675    11. When the -o option was used, pcregrep was setting a return code of 1, even
1676        when matches were found, and --line-buffered was not being honoured.
1677    
1678    12. Added an optional parentheses number to the -o and --only-matching options
1679        of pcregrep.
1680    
1681    13. Imitating Perl's /g action for multiple matches is tricky when the pattern
1682        can match an empty string. The code to do it in pcretest and pcredemo
1683        needed fixing:
1684    
1685        (a) When the newline convention was "crlf", pcretest got it wrong, skipping
1686            only one byte after an empty string match just before CRLF (this case
1687            just got forgotten; "any" and "anycrlf" were OK).
1688    
1689        (b) The pcretest code also had a bug, causing it to loop forever in UTF-8
1690            mode when an empty string match preceded an ASCII character followed by
1691            a non-ASCII character. (The code for advancing by one character rather
1692            than one byte was nonsense.)
1693    
1694        (c) The pcredemo.c sample program did not have any code at all to handle
1695            the cases when CRLF is a valid newline sequence.
1696    
1697    14. Neither pcre_exec() nor pcre_dfa_exec() was checking that the value given
1698        as a starting offset was within the subject string. There is now a new
1699        error, PCRE_ERROR_BADOFFSET, which is returned if the starting offset is
1700        negative or greater than the length of the string. In order to test this,
1701        pcretest is extended to allow the setting of negative starting offsets.
1702    
1703    15. In both pcre_exec() and pcre_dfa_exec() the code for checking that the
1704        starting offset points to the beginning of a UTF-8 character was
1705        unnecessarily clumsy. I tidied it up.
1706    
1707    16. Added PCRE_ERROR_SHORTUTF8 to make it possible to distinguish between a
1708        bad UTF-8 sequence and one that is incomplete when using PCRE_PARTIAL_HARD.
1709    
1710    17. Nobody had reported that the --include_dir option, which was added in
1711        release 7.7 should have been called --include-dir (hyphen, not underscore)
1712        for compatibility with GNU grep. I have changed it to --include-dir, but
1713        left --include_dir as an undocumented synonym, and the same for
1714        --exclude-dir, though that is not available in GNU grep, at least as of
1715        release 2.5.4.
1716    
1717    18. At a user's suggestion, the macros GETCHAR and friends (which pick up UTF-8
1718        characters from a string of bytes) have been redefined so as not to use
1719        loops, in order to improve performance in some environments. At the same
1720        time, I abstracted some of the common code into auxiliary macros to save
1721        repetition (this should not affect the compiled code).
1722    
1723    19. If \c was followed by a multibyte UTF-8 character, bad things happened. A
1724        compile-time error is now given if \c is not followed by an ASCII
1725        character, that is, a byte less than 128. (In EBCDIC mode, the code is
1726        different, and any byte value is allowed.)
1727    
1728    20. Recognize (*NO_START_OPT) at the start of a pattern to set the PCRE_NO_
1729        START_OPTIMIZE option, which is now allowed at compile time - but just
1730        passed through to pcre_exec() or pcre_dfa_exec(). This makes it available
1731        to pcregrep and other applications that have no direct access to PCRE
1732        options. The new /Y option in pcretest sets this option when calling
1733        pcre_compile().
1734    
1735    21. Change 18 of release 8.01 broke the use of named subpatterns for recursive
1736        back references. Groups containing recursive back references were forced to
1737        be atomic by that change, but in the case of named groups, the amount of
1738        memory required was incorrectly computed, leading to "Failed: internal
1739        error: code overflow". This has been fixed.
1740    
1741    22. Some patches to pcre_stringpiece.h, pcre_stringpiece_unittest.cc, and
1742        pcretest.c, to avoid build problems in some Borland environments.
1743    
1744    
1745    Version 8.10 25-Jun-2010
1746    ------------------------
1747    
1748    1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and
1749        THEN.
1750    
1751    2.  (*ACCEPT) was not working when inside an atomic group.
1752    
1753    3.  Inside a character class, \B is treated as a literal by default, but
1754        faulted if PCRE_EXTRA is set. This mimics Perl's behaviour (the -w option
1755        causes the error). The code is unchanged, but I tidied the documentation.
1756    
1757    4.  Inside a character class, PCRE always treated \R and \X as literals,
1758        whereas Perl faults them if its -w option is set. I have changed PCRE so
1759        that it faults them when PCRE_EXTRA is set.
1760    
1761    5.  Added support for \N, which always matches any character other than
1762        newline. (It is the same as "." when PCRE_DOTALL is not set.)
1763    
1764    6.  When compiling pcregrep with newer versions of gcc which may have
1765        FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',
1766        declared with attribute warn_unused_result" were given. Just casting the
1767        result to (void) does not stop the warnings; a more elaborate fudge is
1768        needed. I've used a macro to implement this.
1769    
1770    7.  Minor change to pcretest.c to avoid a compiler warning.
1771    
1772    8.  Added four artifical Unicode properties to help with an option to make
1773        \s etc use properties (see next item). The new properties are: Xan
1774        (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).
1775    
1776    9.  Added PCRE_UCP to make \b, \d, \s, \w, and certain POSIX character classes
1777        use Unicode properties. (*UCP) at the start of a pattern can be used to set
1778        this option. Modified pcretest to add /W to test this facility. Added
1779        REG_UCP to make it available via the POSIX interface.
1780    
1781    10. Added --line-buffered to pcregrep.
1782    
1783    11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was
1784        studied, and the match started with a letter with a code point greater than
1785        127 whose first byte was different to the first byte of the other case of
1786        the letter, the other case of this starting letter was not recognized
1787        (#976).
1788    
1789    12. If a pattern that was studied started with a repeated Unicode property
1790        test, for example, \p{Nd}+, there was the theoretical possibility of
1791        setting up an incorrect bitmap of starting bytes, but fortunately it could
1792        not have actually happened in practice until change 8 above was made (it
1793        added property types that matched character-matching opcodes).
1794    
1795    13. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
1796        possible starting bytes for non-anchored patterns.
1797    
1798    14. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes
1799        \R, and also a number of cases that involve Unicode properties, both
1800        explicit and implicit when PCRE_UCP is set.
1801    
1802    15. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8
1803        input, it could crash or give wrong results if characters with values
1804        greater than 0xc0 were present in the subject string. (Detail: it assumed
1805        UTF-8 input when processing these items.)
1806    
1807    16. Added a lot of (int) casts to avoid compiler warnings in systems where
1808        size_t is 64-bit (#991).
1809    
1810    17. Added a check for running out of memory when PCRE is compiled with
1811        --disable-stack-for-recursion (#990).
1812    
1813    18. If the last data line in a file for pcretest does not have a newline on
1814        the end, a newline was missing in the output.
1815    
1816    19. The default pcre_chartables.c file recognizes only ASCII characters (values
1817        less than 128) in its various bitmaps. However, there is a facility for
1818        generating tables according to the current locale when PCRE is compiled. It
1819        turns out that in some environments, 0x85 and 0xa0, which are Unicode space
1820        characters, are recognized by isspace() and therefore were getting set in
1821        these tables, and indeed these tables seem to approximate to ISO 8859. This
1822        caused a problem in UTF-8 mode when pcre_study() was used to create a list
1823        of bytes that can start a match. For \s, it was including 0x85 and 0xa0,
1824        which of course cannot start UTF-8 characters. I have changed the code so
1825        that only real ASCII characters (less than 128) and the correct starting
1826        bytes for UTF-8 encodings are set for characters greater than 127 when in
1827        UTF-8 mode. (When PCRE_UCP is set - see 9 above - the code is different
1828        altogether.)
1829    
1830    20. Added the /T option to pcretest so as to be able to run tests with non-
1831        standard character tables, thus making it possible to include the tests
1832        used for 19 above in the standard set of tests.
1833    
1834    21. A pattern such as (?&t)(?#()(?(DEFINE)(?<t>a)) which has a forward
1835        reference to a subpattern the other side of a comment that contains an
1836        opening parenthesis caused either an internal compiling error, or a
1837        reference to the wrong subpattern.
1838    
1839    
1840    Version 8.02 19-Mar-2010
1841    ------------------------
1842    
1843    1.  The Unicode data tables have been updated to Unicode 5.2.0.
1844    
1845    2.  Added the option --libs-cpp to pcre-config, but only when C++ support is
1846        configured.
1847    
1848    3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the
1849        original author of that file, following a query about its status.
1850    
1851    4.  On systems that do not have stdint.h (e.g. Solaris), check for and include
1852        inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
1853    
1854    5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
1855        quantifier applied to a forward-referencing subroutine call, could compile
1856        incorrect code or give the error "internal error: previously-checked
1857        referenced subpattern not found".
1858    
1859    6.  Both MS Visual Studio and Symbian OS have problems with initializing
1860        variables to point to external functions. For these systems, therefore,
1861        pcre_malloc etc. are now initialized to local functions that call the
1862        relevant global functions.
1863    
1864    7.  There were two entries missing in the vectors called coptable and poptable
1865        in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.
1866        I've fixed the data, and added a kludgy way of testing at compile time that
1867        the lengths are correct (equal to the number of opcodes).
1868    
1869    8.  Following on from 7, I added a similar kludge to check the length of the
1870        eint vector in pcreposix.c.
1871    
1872    9.  Error texts for pcre_compile() are held as one long string to avoid too
1873        much relocation at load time. To find a text, the string is searched,
1874        counting zeros. There was no check for running off the end of the string,
1875        which could happen if a new error number was added without updating the
1876        string.
1877    
1878    10. \K gave a compile-time error if it appeared in a lookbehind assersion.
1879    
1880    11. \K was not working if it appeared in an atomic group or in a group that
1881        was called as a "subroutine", or in an assertion. Perl 5.11 documents that
1882        \K is "not well defined" if used in an assertion. PCRE now accepts it if
1883        the assertion is positive, but not if it is negative.
1884    
1885    12. Change 11 fortuitously reduced the size of the stack frame used in the
1886        "match()" function of pcre_exec.c by one pointer. Forthcoming
1887        implementation of support for (*MARK) will need an extra pointer on the
1888        stack; I have reserved it now, so that the stack frame size does not
1889        decrease.
1890    
1891    13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other
1892        item in branch that calls a recursion is a subroutine call - as in the
1893        second branch in the above example - was incorrectly given the compile-
1894        time error "recursive call could loop indefinitely" because pcre_compile()
1895        was not correctly checking the subroutine for matching a non-empty string.
1896    
1897    14. The checks for overrunning compiling workspace could trigger after an
1898        overrun had occurred. This is a "should never occur" error, but it can be
1899        triggered by pathological patterns such as hundreds of nested parentheses.
1900        The checks now trigger 100 bytes before the end of the workspace.
1901    
1902    15. Fix typo in configure.ac: "srtoq" should be "strtoq".
1903    
1904    
1905    Version 8.01 19-Jan-2010
1906    ------------------------
1907    
1908    1.  If a pattern contained a conditional subpattern with only one branch (in
1909        particular, this includes all (*DEFINE) patterns), a call to pcre_study()
1910        computed the wrong minimum data length (which is of course zero for such
1911        subpatterns). This could cause incorrect "no match" results.
1912    
1913    2.  For patterns such as (?i)a(?-i)b|c where an option setting at the start of
1914        the pattern is reset in the first branch, pcre_compile() failed with
1915        "internal error: code overflow at offset...". This happened only when
1916        the reset was to the original external option setting. (An optimization
1917        abstracts leading options settings into an external setting, which was the
1918        cause of this.)
1919    
1920    3.  A pattern such as ^(?!a(*SKIP)b) where a negative assertion contained one
1921        of the verbs SKIP, PRUNE, or COMMIT, did not work correctly. When the
1922        assertion pattern did not match (meaning that the assertion was true), it
1923        was incorrectly treated as false if the SKIP had been reached during the
1924        matching. This also applied to assertions used as conditions.
1925    
1926    4.  If an item that is not supported by pcre_dfa_exec() was encountered in an
1927        assertion subpattern, including such a pattern used as a condition,
1928        unpredictable results occurred, instead of the error return
1929        PCRE_ERROR_DFA_UITEM.
1930    
1931    5.  The C++ GlobalReplace function was not working like Perl for the special
1932        situation when an empty string is matched. It now does the fancy magic
1933        stuff that is necessary.
1934    
1935    6.  In pcre_internal.h, obsolete includes to setjmp.h and stdarg.h have been
1936        removed. (These were left over from very, very early versions of PCRE.)
1937    
1938    7.  Some cosmetic changes to the code to make life easier when compiling it
1939        as part of something else:
1940    
1941        (a) Change DEBUG to PCRE_DEBUG.
1942    
1943        (b) In pcre_compile(), rename the member of the "branch_chain" structure
1944            called "current" as "current_branch", to prevent a collision with the
1945            Linux macro when compiled as a kernel module.
1946    
1947        (c) In pcre_study(), rename the function set_bit() as set_table_bit(), to
1948            prevent a collision with the Linux macro when compiled as a kernel
1949            module.
1950    
1951    8.  In pcre_compile() there are some checks for integer overflows that used to
1952        cast potentially large values to (double). This has been changed to that
1953        when building, a check for int64_t is made, and if it is found, it is used
1954        instead, thus avoiding the use of floating point arithmetic. (There is no
1955        other use of FP in PCRE.) If int64_t is not found, the fallback is to
1956        double.
1957    
1958    9.  Added two casts to avoid signed/unsigned warnings from VS Studio Express
1959        2005 (difference between two addresses compared to an unsigned value).
1960    
1961    10. Change the standard AC_CHECK_LIB test for libbz2 in configure.ac to a
1962        custom one, because of the following reported problem in Windows:
1963    
1964          - libbz2 uses the Pascal calling convention (WINAPI) for the functions
1965              under Win32.
1966          - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",
1967              therefore missing the function definition.
1968          - The compiler thus generates a "C" signature for the test function.
1969          - The linker fails to find the "C" function.
1970          - PCRE fails to configure if asked to do so against libbz2.
1971    
1972    11. When running libtoolize from libtool-2.2.6b as part of autogen.sh, these
1973        messages were output:
1974    
1975          Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
1976          rerunning libtoolize, to keep the correct libtool macros in-tree.
1977          Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
1978    
1979        I have done both of these things.
1980    
1981    12. Although pcre_dfa_exec() does not use nearly as much stack as pcre_exec()
1982        most of the time, it *can* run out if it is given a pattern that contains a
1983        runaway infinite recursion. I updated the discussion in the pcrestack man
1984        page.
1985    
1986    13. Now that we have gone to the x.xx style of version numbers, the minor
1987        version may start with zero. Using 08 or 09 is a bad idea because users
1988        might check the value of PCRE_MINOR in their code, and 08 or 09 may be
1989        interpreted as invalid octal numbers. I've updated the previous comment in
1990        configure.ac, and also added a check that gives an error if 08 or 09 are
1991        used.
1992    
1993    14. Change 8.00/11 was not quite complete: code had been accidentally omitted,
1994        causing partial matching to fail when the end of the subject matched \W
1995        in a UTF-8 pattern where \W was quantified with a minimum of 3.
1996    
1997    15. There were some discrepancies between the declarations in pcre_internal.h
1998        of _pcre_is_newline(), _pcre_was_newline(), and _pcre_valid_utf8() and
1999        their definitions. The declarations used "const uschar *" and the
2000        definitions used USPTR. Even though USPTR is normally defined as "const
2001        unsigned char *" (and uschar is typedeffed as "unsigned char"), it was
2002        reported that: "This difference in casting confuses some C++ compilers, for
2003        example, SunCC recognizes above declarations as different functions and
2004        generates broken code for hbpcre." I have changed the declarations to use
2005        USPTR.
2006    
2007    16. GNU libtool is named differently on some systems. The autogen.sh script now
2008        tries several variants such as glibtoolize (MacOSX) and libtoolize1x
2009        (FreeBSD).
2010    
2011    17. Applied Craig's patch that fixes an HP aCC compile error in pcre 8.00
2012        (strtoXX undefined when compiling pcrecpp.cc). The patch contains this
2013        comment: "Figure out how to create a longlong from a string: strtoll and
2014        equivalent. It's not enough to call AC_CHECK_FUNCS: hpux has a strtoll, for
2015        instance, but it only takes 2 args instead of 3!"
2016    
2017    18. A subtle bug concerned with back references has been fixed by a change of
2018        specification, with a corresponding code fix. A pattern such as
2019        ^(xa|=?\1a)+$ which contains a back reference inside the group to which it
2020        refers, was giving matches when it shouldn't. For example, xa=xaaa would
2021        match that pattern. Interestingly, Perl (at least up to 5.11.3) has the
2022        same bug. Such groups have to be quantified to be useful, or contained
2023        inside another quantified group. (If there's no repetition, the reference
2024        can never match.) The problem arises because, having left the group and
2025        moved on to the rest of the pattern, a later failure that backtracks into
2026        the group uses the captured value from the final iteration of the group
2027        rather than the correct earlier one. I have fixed this in PCRE by forcing
2028        any group that contains a reference to itself to be an atomic group; that
2029        is, there cannot be any backtracking into it once it has completed. This is
2030        similar to recursive and subroutine calls.
2031    
2032    
2033    Version 8.00 19-Oct-09
2034    ----------------------
2035    
2036    1.  The table for translating pcre_compile() error codes into POSIX error codes
2037        was out-of-date, and there was no check on the pcre_compile() error code
2038        being within the table. This could lead to an OK return being given in
2039        error.
2040    
2041    2.  Changed the call to open a subject file in pcregrep from fopen(pathname,
2042        "r") to fopen(pathname, "rb"), which fixed a problem with some of the tests
2043        in a Windows environment.
2044    
2045    3.  The pcregrep --count option prints the count for each file even when it is
2046        zero, as does GNU grep. However, pcregrep was also printing all files when
2047        --files-with-matches was added. Now, when both options are given, it prints
2048        counts only for those files that have at least one match. (GNU grep just
2049        prints the file name in this circumstance, but including the count seems
2050        more useful - otherwise, why use --count?) Also ensured that the
2051        combination -clh just lists non-zero counts, with no names.
2052    
2053    4.  The long form of the pcregrep -F option was incorrectly implemented as
2054        --fixed_strings instead of --fixed-strings. This is an incompatible change,
2055        but it seems right to fix it, and I didn't think it was worth preserving
2056        the old behaviour.
2057    
2058    5.  The command line items --regex=pattern and --regexp=pattern were not
2059        recognized by pcregrep, which required --regex pattern or --regexp pattern
2060        (with a space rather than an '='). The man page documented the '=' forms,
2061        which are compatible with GNU grep; these now work.
2062    
2063    6.  No libpcreposix.pc file was created for pkg-config; there was just
2064        libpcre.pc and libpcrecpp.pc. The omission has been rectified.
2065    
2066    7.  Added #ifndef SUPPORT_UCP into the pcre_ucd.c module, to reduce its size
2067        when UCP support is not needed, by modifying the Python script that
2068        generates it from Unicode data files. This should not matter if the module
2069        is correctly used as a library, but I received one complaint about 50K of
2070        unwanted data. My guess is that the person linked everything into his
2071        program rather than using a library. Anyway, it does no harm.
2072    
2073    8.  A pattern such as /\x{123}{2,2}+/8 was incorrectly compiled; the trigger
2074        was a minimum greater than 1 for a wide character in a possessive
2075        repetition. The same bug could also affect patterns like /(\x{ff}{0,2})*/8
2076        which had an unlimited repeat of a nested, fixed maximum repeat of a wide
2077        character. Chaos in the form of incorrect output or a compiling loop could
2078        result.
2079    
2080    9.  The restrictions on what a pattern can contain when partial matching is
2081        requested for pcre_exec() have been removed. All patterns can now be
2082        partially matched by this function. In addition, if there are at least two
2083        slots in the offset vector, the offset of the earliest inspected character
2084        for the match and the offset of the end of the subject are set in them when
2085        PCRE_ERROR_PARTIAL is returned.
2086    
2087    10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is
2088        synonymous with PCRE_PARTIAL, for backwards compatibility, and
2089        PCRE_PARTIAL_HARD, which causes a partial match to supersede a full match,
2090        and may be more useful for multi-segment matching.
2091    
2092    11. Partial matching with pcre_exec() is now more intuitive. A partial match
2093        used to be given if ever the end of the subject was reached; now it is
2094        given only if matching could not proceed because another character was
2095        needed. This makes a difference in some odd cases such as Z(*FAIL) with the
2096        string "Z", which now yields "no match" instead of "partial match". In the
2097        case of pcre_dfa_exec(), "no match" is given if every matching path for the
2098        final character ended with (*FAIL).
2099    
2100    12. Restarting a match using pcre_dfa_exec() after a partial match did not work
2101        if the pattern had a "must contain" character that was already found in the
2102        earlier partial match, unless partial matching was again requested. For
2103        example, with the pattern /dog.(body)?/, the "must contain" character is
2104        "g". If the first part-match was for the string "dog", restarting with
2105        "sbody" failed. This bug has been fixed.
2106    
2107    13. The string returned by pcre_dfa_exec() after a partial match has been
2108        changed so that it starts at the first inspected character rather than the
2109        first character of the match. This makes a difference only if the pattern
2110        starts with a lookbehind assertion or \b or \B (\K is not supported by
2111        pcre_dfa_exec()). It's an incompatible change, but it makes the two
2112        matching functions compatible, and I think it's the right thing to do.
2113    
2114    14. Added a pcredemo man page, created automatically from the pcredemo.c file,
2115        so that the demonstration program is easily available in environments where
2116        PCRE has not been installed from source.
2117    
2118    15. Arranged to add -DPCRE_STATIC to cflags in libpcre.pc, libpcreposix.cp,
2119        libpcrecpp.pc and pcre-config when PCRE is not compiled as a shared
2120        library.
2121    
2122    16. Added REG_UNGREEDY to the pcreposix interface, at the request of a user.
2123        It maps to PCRE_UNGREEDY. It is not, of course, POSIX-compatible, but it
2124        is not the first non-POSIX option to be added. Clearly some people find
2125        these options useful.
2126    
2127    17. If a caller to the POSIX matching function regexec() passes a non-zero
2128        value for nmatch with a NULL value for pmatch, the value of
2129        nmatch is forced to zero.
2130    
2131    18. RunGrepTest did not have a test for the availability of the -u option of
2132        the diff command, as RunTest does. It now checks in the same way as
2133        RunTest, and also checks for the -b option.
2134    
2135    19. If an odd number of negated classes containing just a single character
2136        interposed, within parentheses, between a forward reference to a named
2137        subpattern and the definition of the subpattern, compilation crashed with
2138        an internal error, complaining that it could not find the referenced
2139        subpattern. An example of a crashing pattern is /(?&A)(([^m])(?<A>))/.
2140        [The bug was that it was starting one character too far in when skipping
2141        over the character class, thus treating the ] as data rather than
2142        terminating the class. This meant it could skip too much.]
2143    
2144    20. Added PCRE_NOTEMPTY_ATSTART in order to be able to correctly implement the
2145        /g option in pcretest when the pattern contains \K, which makes it possible
2146        to have an empty string match not at the start, even when the pattern is
2147        anchored. Updated pcretest and pcredemo to use this option.
2148    
2149    21. If the maximum number of capturing subpatterns in a recursion was greater
2150        than the maximum at the outer level, the higher number was returned, but
2151        with unset values at the outer level. The correct (outer level) value is
2152        now given.
2153    
2154    22. If (*ACCEPT) appeared inside capturing parentheses, previous releases of
2155        PCRE did not set those parentheses (unlike Perl). I have now found a way to
2156        make it do so. The string so far is captured, making this feature
2157        compatible with Perl.
2158    
2159    23. The tests have been re-organized, adding tests 11 and 12, to make it
2160        possible to check the Perl 5.10 features against Perl 5.10.
2161    
2162    24. Perl 5.10 allows subroutine calls in lookbehinds, as long as the subroutine
2163        pattern matches a fixed length string. PCRE did not allow this; now it
2164        does. Neither allows recursion.
2165    
2166    25. I finally figured out how to implement a request to provide the minimum
2167        length of subject string that was needed in order to match a given pattern.
2168        (It was back references and recursion that I had previously got hung up
2169        on.) This code has now been added to pcre_study(); it finds a lower bound
2170        to the length of subject needed. It is not necessarily the greatest lower
2171        bound, but using it to avoid searching strings that are too short does give
2172        some useful speed-ups. The value is available to calling programs via
2173        pcre_fullinfo().
2174    
2175    26. While implementing 25, I discovered to my embarrassment that pcretest had
2176        not been passing the result of pcre_study() to pcre_dfa_exec(), so the
2177        study optimizations had never been tested with that matching function.
2178        Oops. What is worse, even when it was passed study data, there was a bug in
2179        pcre_dfa_exec() that meant it never actually used it. Double oops. There
2180        were also very few tests of studied patterns with pcre_dfa_exec().
2181    
2182    27. If (?| is used to create subpatterns with duplicate numbers, they are now
2183        allowed to have the same name, even if PCRE_DUPNAMES is not set. However,
2184        on the other side of the coin, they are no longer allowed to have different
2185        names, because these cannot be distinguished in PCRE, and this has caused
2186        confusion. (This is a difference from Perl.)
2187    
2188    28. When duplicate subpattern names are present (necessarily with different
2189        numbers, as required by 27 above), and a test is made by name in a
2190        conditional pattern, either for a subpattern having been matched, or for
2191        recursion in such a pattern, all the associated numbered subpatterns are
2192        tested, and the overall condition is true if the condition is true for any
2193        one of them. This is the way Perl works, and is also more like the way
2194        testing by number works.
2195    
2196    
2197    Version 7.9 11-Apr-09
2198    ---------------------
2199    
2200    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
2201        (pcretest), all targets were linked against these libraries. This included
2202        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
2203        libraries. This caused unwanted dependencies to be created. This problem
2204        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
2205        pcretest is linked with readline.
2206    
2207    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
2208        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
2209        moved outside it again, because FALSE and TRUE are already defined in AIX,
2210        but BOOL is not.
2211    
2212    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
2213        PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
2214    
2215    4.  The pcregrep documentation said spaces were inserted as well as colons (or
2216        hyphens) following file names and line numbers when outputting matching
2217        lines. This is not true; no spaces are inserted. I have also clarified the
2218        wording for the --colour (or --color) option.
2219    
2220    5.  In pcregrep, when --colour was used with -o, the list of matching strings
2221        was not coloured; this is different to GNU grep, so I have changed it to be
2222        the same.
2223    
2224    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
2225        each matching line was coloured. Now it goes on to look for further matches
2226        of any of the test patterns, which is the same behaviour as GNU grep.
2227    
2228    7.  A pattern that could match an empty string could cause pcregrep to loop; it
2229        doesn't make sense to accept an empty string match in pcregrep, so I have
2230        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
2231        seems to be how GNU grep behaves. [But see later change 40 for release
2232        8.33.]
2233    
2234    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
2235        start or after a newline", because the conditional assertion was not being
2236        correctly handled. The rule now is that both the assertion and what follows
2237        in the first alternative must satisfy the test.
2238    
2239    9.  If auto-callout was enabled in a pattern with a conditional group whose
2240        condition was an assertion, PCRE could crash during matching, both with
2241        pcre_exec() and pcre_dfa_exec().
2242    
2243    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
2244        used for matching.
2245    
2246    11. Unicode property support in character classes was not working for
2247        characters (bytes) greater than 127 when not in UTF-8 mode.
2248    
2249    12. Added the -M command line option to pcretest.
2250    
2251    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
2252    
2253    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
2254    
2255    16. Added comments and documentation about mis-use of no_arg in the C++
2256        wrapper.
2257    
2258    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
2259        from Martin Jerabek that uses macro names for all relevant character and
2260        string constants.
2261    
2262    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
2263        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
2264        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
2265        these, but not everybody uses configure.
2266    
2267    19. A conditional group that had only one branch was not being correctly
2268        recognized as an item that could match an empty string. This meant that an
2269        enclosing group might also not be so recognized, causing infinite looping
2270        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
2271        with the subject "ab", where knowledge that the repeated group can match
2272        nothing is needed in order to break the loop.
2273    
2274    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
2275        exec(), but without supplying a callout function, matching went wrong.
2276    
2277    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
2278        leak if the size of the offset vector was greater than 30. When the vector
2279        is smaller, the saved offsets during recursion go onto a local stack
2280        vector, but for larger vectors malloc() is used. It was failing to free
2281        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
2282        error, in fact).
2283    
2284    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
2285        heapframe that is used only when UTF-8 support is enabled. This caused no
2286        problem, but was untidy.
2287    
2288    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
2289        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
2290        included within another project.
2291    
2292    24. Steven Van Ingelgem's patches to add more options to the CMake support,
2293        slightly modified by me:
2294    
2295          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
2296              not building pcregrep.
2297    
2298          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
2299              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
2300    
2301    25. Forward references, both numeric and by name, in patterns that made use of
2302        duplicate group numbers, could behave incorrectly or give incorrect errors,
2303        because when scanning forward to find the reference group, PCRE was not
2304        taking into account the duplicate group numbers. A pattern such as
2305        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
2306    
2307    26. Changed a few more instances of "const unsigned char *" to USPTR, making
2308        the feature of a custom pointer more persuasive (as requested by a user).
2309    
2310    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
2311        pcretest.c, inside #ifndefs, because it seems they are sometimes already
2312        pre-defined.
2313    
2314    28. Added support for (*UTF8) at the start of a pattern.
2315    
2316    29. Arrange for flags added by the "release type" setting in CMake to be shown
2317        in the configuration summary.
2318    
2319    
2320    Version 7.8 05-Sep-08
2321    ---------------------
2322    
2323    1.  Replaced UCP searching code with optimized version as implemented for Ad
2324        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
2325        stage table and inline lookup instead of a function, giving speed ups of 2
2326        to 5 times on some simple patterns that I tested. Permission was given to
2327        distribute the MultiStage2.py script that generates the tables (it's not in
2328        the tarball, but is in the Subversion repository).
2329    
2330    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
2331        scripts.
2332    
2333    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
2334        a group with a zero qualifier. The result of the study could be incorrect,
2335        or the function might crash, depending on the pattern.
2336    
2337    4.  Caseless matching was not working for non-ASCII characters in back
2338        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
2339        It now works when Unicode Property Support is available.
2340    
2341    5.  In pcretest, an escape such as \x{de} in the data was always generating
2342        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
2343        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
2344        truncation.
2345    
2346    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
2347    
2348    7.  Added two (int) casts to pcregrep when printing the difference of two
2349        pointers, in case they are 64-bit values.
2350    
2351    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
2352        test 2 if it fails.
2353    
2354    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
2355        and a #define of that name to empty if it is not externally set. This is to
2356        allow users of MSVC to set it if necessary.
2357    
2358    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
2359        the convenience functions in the pcre_get.c source file.
2360    
2361    11. An option change at the start of a pattern that had top-level alternatives
2362        could cause overwriting and/or a crash. This command provoked a crash in
2363        some environments:
2364    
2365          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
2366    
2367        This potential security problem was recorded as CVE-2008-2371.
2368    
2369    12. For a pattern where the match had to start at the beginning or immediately
2370        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
2371        pcre_dfa_exec() could read past the end of the passed subject if there was
2372        no match. To help with detecting such bugs (e.g. with valgrind), I modified
2373        pcretest so that it places the subject at the end of its malloc-ed buffer.
2374    
2375    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
2376        exec() might read past the end of the data buffer in UTF-8 mode.
2377    
2378    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
2379        the data contained the byte 0x85 as part of a UTF-8 character within its
2380        first line. This applied both to normal and DFA matching.
2381    
2382    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
2383        /^[^d]*?$/8 failed to match "abc".
2384    
2385    16. Added a missing copyright notice to pcrecpp_internal.h.
2386    
2387    17. Make it more clear in the documentation that values returned from
2388        pcre_exec() in ovector are byte offsets, not character counts.
2389    
2390    18. Tidied a few places to stop certain compilers from issuing warnings.
2391    
2392    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
2393        supplied by Stefan Weber. I made a further small update for 7.8 because
2394        there is a change of source arrangements: the pcre_searchfuncs.c module is
2395        replaced by pcre_ucd.c.
2396    
2397    
2398    Version 7.7 07-May-08
2399  ---------------------  ---------------------
2400    
2401  1.  Applied Craig's patch to sort out a long long problem: "If we can't convert  1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
2402      a string to a long long, pretend we don't even have a long long." This is      a string to a long long, pretend we don't even have a long long." This is
2403      done by checking for the strtoq, strtoll, and _strtoi64 functions.      done by checking for the strtoq, strtoll, and _strtoi64 functions.
2404    
2405  2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with  2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
2406      pre-7.6 versions, which defined a global no_arg variable instead of putting      pre-7.6 versions, which defined a global no_arg variable instead of putting
2407      it in the RE class. (See also #8 below.)      it in the RE class. (See also #8 below.)
2408    
2409  3.  Remove a line of dead code, identified by coverity and reported by Nuno  3.  Remove a line of dead code, identified by coverity and reported by Nuno
2410      Lopes.      Lopes.
2411    
2412  4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:  4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
2413    
2414      (1) The include/exclude patterns were being applied to the whole pathnames      (1) The include/exclude patterns were being applied to the whole pathnames
2415          of files, instead of just to the final components.          of files, instead of just to the final components.
2416    
2417      (2) If there was more than one level of directory, the subdirectories were      (2) If there was more than one level of directory, the subdirectories were
2418          skipped unless they satisfied the include/exclude conditions. This is          skipped unless they satisfied the include/exclude conditions. This is
2419          inconsistent with GNU grep (and could even be seen as contrary to the          inconsistent with GNU grep (and could even be seen as contrary to the
2420          pcregrep specification - which I improved to make it absolutely clear).          pcregrep specification - which I improved to make it absolutely clear).
2421          The action now is always to scan all levels of directory, and just          The action now is always to scan all levels of directory, and just
2422          apply the include/exclude patterns to regular files.          apply the include/exclude patterns to regular files.
2423    
2424  5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used  5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
2425      --exclude_dir in the tests to avoid scanning .svn directories.      --exclude_dir in the tests to avoid scanning .svn directories.
2426    
2427  6.  Applied Craig's patch to the QuoteMeta function so that it escapes the  6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
2428      NUL character as backslash + 0 rather than backslash + NUL, because PCRE      NUL character as backslash + 0 rather than backslash + NUL, because PCRE
2429      doesn't support NULs in patterns.      doesn't support NULs in patterns.
2430    
2431  7.  Added some missing "const"s to declarations of static tables in  7.  Added some missing "const"s to declarations of static tables in
2432      pcre_compile.c and pcre_dfa_exec.c.      pcre_compile.c and pcre_dfa_exec.c.
2433    
2434  8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was  8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
2435      caused by fix #2  above. (Subsequently also a second patch to fix the      caused by fix #2  above. (Subsequently also a second patch to fix the
2436      first patch. And a third patch - this was a messy problem.)      first patch. And a third patch - this was a messy problem.)
2437    
2438  9.  Applied Craig's patch to remove the use of push_back().  9.  Applied Craig's patch to remove the use of push_back().
2439    
2440  10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX  10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
2441      matching function regexec().      matching function regexec().
2442    
2443  11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',  11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
2444      which, however, unlike Perl's \g{...}, are subroutine calls, not back      which, however, unlike Perl's \g{...}, are subroutine calls, not back
2445      references. PCRE supports relative numbers with this syntax (I don't think      references. PCRE supports relative numbers with this syntax (I don't think
2446      Oniguruma does).      Oniguruma does).
2447    
2448  12. Previously, a group with a zero repeat such as (...){0} was completely  12. Previously, a group with a zero repeat such as (...){0} was completely
2449      omitted from the compiled regex. However, this means that if the group      omitted from the compiled regex. However, this means that if the group
2450      was called as a subroutine from elsewhere in the pattern, things went wrong      was called as a subroutine from elsewhere in the pattern, things went wrong
2451      (an internal error was given). Such groups are now left in the compiled      (an internal error was given). Such groups are now left in the compiled
2452      pattern, with a new opcode that causes them to be skipped at execution      pattern, with a new opcode that causes them to be skipped at execution
2453      time.      time.
2454    
2455  13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes  13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
2456      to the way PCRE behaves:      to the way PCRE behaves:
2457    
2458      (a) A lone ] character is dis-allowed (Perl treats it as data).      (a) A lone ] character is dis-allowed (Perl treats it as data).
2459    
2460      (b) A back reference to an unmatched subpattern matches an empty string      (b) A back reference to an unmatched subpattern matches an empty string
2461          (Perl fails the current match path).          (Perl fails the current match path).
2462    
2463      (c) A data ] in a character class must be notated as \] because if the      (c) A data ] in a character class must be notated as \] because if the
2464          first data character in a class is ], it defines an empty class. (In          first data character in a class is ], it defines an empty class. (In
2465          Perl it is not possible to have an empty class.) The empty class []          Perl it is not possible to have an empty class.) The empty class []
2466          never matches; it forces failure and is equivalent to (*FAIL) or (?!).          never matches; it forces failure and is equivalent to (*FAIL) or (?!).
2467          The negative empty class [^] matches any one character, independently          The negative empty class [^] matches any one character, independently
2468          of the DOTALL setting.          of the DOTALL setting.
2469    
2470  14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a  14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
2471      non-existent subpattern following a character class starting with ']' and      non-existent subpattern following a character class starting with ']' and
2472      containing () gave an internal compiling error instead of "reference to      containing () gave an internal compiling error instead of "reference to
2473      non-existent subpattern". Fortunately, when the pattern did exist, the      non-existent subpattern". Fortunately, when the pattern did exist, the
2474      compiled code was correct. (When scanning forwards to check for the      compiled code was correct. (When scanning forwards to check for the
2475      existencd of the subpattern, it was treating the data ']' as terminating      existence of the subpattern, it was treating the data ']' as terminating
2476      the class, so got the count wrong. When actually compiling, the reference      the class, so got the count wrong. When actually compiling, the reference
2477      was subsequently set up correctly.)      was subsequently set up correctly.)
2478    
2479  15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;  15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
2480      it was being rejected as not supported by pcre_dfa_exec(), even though      it was being rejected as not supported by pcre_dfa_exec(), even though
2481      other assertions are supported. I have made pcre_dfa_exec() support      other assertions are supported. I have made pcre_dfa_exec() support
2482      (*FAIL).      (*FAIL).
2483    
2484    16. The implementation of 13c above involved the invention of a new opcode,
2485        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
2486        cannot be changed at match time, I realized I could make a small
2487        improvement to matching performance by compiling OP_ALLANY instead of
2488        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
2489        on the OP_ANY path.
2490    
2491    17. Compiling pcretest on Windows with readline support failed without the
2492        following two fixes: (1) Make the unistd.h include conditional on
2493        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
2494    
2495    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
2496        ncurses library to be included for pcretest when ReadLine support is
2497        requested, but also to allow for it to be overridden. This patch came from
2498        Daniel Bergström.
2499    
2500    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
2501        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
2502        any errors with the current Unicode tables. Thanks to Peter Kankowski for
2503        spotting this.
2504    
2505    
2506  Version 7.6 28-Jan-08  Version 7.6 28-Jan-08

Legend:
Removed from v.341  
changed lines
  Added in v.1537

  ViewVC Help
Powered by ViewVC 1.1.5