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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.335  
changed lines
  Added in v.1003

  ViewVC Help
Powered by ViewVC 1.1.5