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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.326  
changed lines
  Added in v.1039

  ViewVC Help
Powered by ViewVC 1.1.5