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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.342  
changed lines
  Added in v.1041

  ViewVC Help
Powered by ViewVC 1.1.5