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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.328  
changed lines
  Added in v.1454

  ViewVC Help
Powered by ViewVC 1.1.5