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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.349  
changed lines
  Added in v.1251

  ViewVC Help
Powered by ViewVC 1.1.5