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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.385  
changed lines
  Added in v.1441

  ViewVC Help
Powered by ViewVC 1.1.5