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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.113  
changed lines
  Added in v.1305

  ViewVC Help
Powered by ViewVC 1.1.5