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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.265  
changed lines
  Added in v.1011

  ViewVC Help
Powered by ViewVC 1.1.5