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

Diff of /code/trunk/ChangeLog

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

revision 576 by ph10, Sun Nov 21 18:45:10 2010 UTC revision 987 by zherczeg, Sat Jul 7 04:11:29 2012 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.11 10-Oct-2010  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    
14    Version 8.31 06-July-2012
15    -------------------------
16    
17    1.  Fixing a wrong JIT test case and some compiler warnings.
18    
19    2.  Removed a bashism from the RunTest script.
20    
21    3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied
22        to unsigned type, result still unsigned" that was given by an MS compiler
23        on encountering the code "-sizeof(xxx)".
24    
25    4.  Partial matching support is added to the JIT compiler.
26    
27    5.  Fixed several bugs concerned with partial matching of items that consist
28        of more than one character:
29    
30        (a) /^(..)\1/ did not partially match "aba" because checking references was
31            done on an "all or nothing" basis. This also applied to repeated
32            references.
33    
34        (b) \R did not give a hard partial match if \r was found at the end of the
35            subject.
36    
37        (c) \X did not give a hard partial match after matching one or more
38            characters at the end of the subject.
39    
40        (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize
41            a partial match for the string "\r".
42    
43        (e) When newline was set to CRLF, the metacharacter "." did not recognize
44            a partial match for a CR character at the end of the subject string.
45    
46    6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when
47        running pcretest, the text "(JIT)" added to the output whenever JIT is
48        actually used to run the match.
49    
50    7.  Individual JIT compile options can be set in pcretest by following -s+[+]
51        or /S+[+] with a digit between 1 and 7.
52    
53    8.  OP_NOT now supports any UTF character not just single-byte ones.
54    
55    9.  (*MARK) control verb is now supported by the JIT compiler.
56    
57    10. The command "./RunTest list" lists the available tests without actually
58        running any of them. (Because I keep forgetting what they all are.)
59    
60    11. Add PCRE_INFO_MAXLOOKBEHIND.
61    
62    12. Applied a (slightly modified) user-supplied patch that improves performance
63        when the heap is used for recursion (compiled with --disable-stack-for-
64        recursion). Instead of malloc and free for each heap frame each time a
65        logical recursion happens, frames are retained on a chain and re-used where
66        possible. This sometimes gives as much as 30% improvement.
67    
68    13. As documented, (*COMMIT) is now confined to within a recursive subpattern
69        call.
70    
71    14. As documented, (*COMMIT) is now confined to within a positive assertion.
72    
73    15. It is now possible to link pcretest with libedit as an alternative to
74        libreadline.
75    
76    16. (*COMMIT) control verb is now supported by the JIT compiler.
77    
78    17. The Unicode data tables have been updated to Unicode 6.1.0.
79    
80    18. Added --file-list option to pcregrep.
81    
82    19. Added binary file support to pcregrep, including the -a, --binary-files,
83        -I, and --text options.
84    
85    20. The madvise function is renamed for posix_madvise for QNX compatibility
86        reasons. Fixed by Giuseppe D'Angelo.
87    
88    21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
89    
90    22. Changed the option for creating symbolic links for 16-bit man pages from
91        -s to -sf so that re-installing does not cause issues.
92    
93    23. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it.
94    
95    24. Fixed a very old bug in pcretest that caused errors with restarted DFA
96        matches in certain environments (the workspace was not being correctly
97        retained). Also added to pcre_dfa_exec() a simple plausibility check on
98        some of the workspace data at the beginning of a restart.
99    
100    25. \s*\R was auto-possessifying the \s* when it should not, whereas \S*\R
101        was not doing so when it should - probably a typo introduced by SVN 528
102        (change 8.10/14).
103    
104    26. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the
105        \w+ when the character tables indicated that \x{c4} was a word character.
106        There were several related cases, all because the tests for doing a table
107        lookup were testing for characters less than 127 instead of 255.
108    
109    27. If a pattern contains capturing parentheses that are not used in a match,
110        their slots in the ovector are set to -1. For those that are higher than
111        any matched groups, this happens at the end of processing. In the case when
112        there were back references that the ovector was too small to contain
113        (causing temporary malloc'd memory to be used during matching), and the
114        highest capturing number was not used, memory off the end of the ovector
115        was incorrectly being set to -1. (It was using the size of the temporary
116        memory instead of the true size.)
117    
118    28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
119        ovector size, it uses memory at the end of the block that it has got.
120    
121    29. Check for an overlong MARK name and give an error at compile time. The
122        limit is 255 for the 8-bit library and 65535 for the 16-bit library.
123    
124    30. JIT compiler update.
125    
126    31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
127        Rill for the patch.
128    
129    32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
130    
131    33. Variable renamings in the PCRE-JIT compiler. No functionality change.
132    
133    34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
134        SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
135        was enabled.
136    
137    35. Improve JIT code generation for greedy plus quantifier.
138    
139    36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
140        1 to "aa" instead of to an empty string. The bug affected repeated groups
141        that could potentially match an empty string.
142    
143    37. Optimizing single character iterators in JIT.
144    
145    38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
146        the same checks as \x{...} characters in non-JavaScript mode. Specifically,
147        codepoints that are too big for the mode are faulted, and in a UTF mode,
148        disallowed codepoints are also faulted.
149    
150    39. If PCRE was compiled with UTF support, in three places in the DFA
151        matcher there was code that should only have been obeyed in UTF mode, but
152        was being obeyed unconditionally. In 8-bit mode this could cause incorrect
153        processing when bytes with values greater than 127 were present. In 16-bit
154        mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
155        both cases the values are those that cannot be the first data item in a UTF
156        character. The three items that might have provoked this were recursions,
157        possessively repeated groups, and atomic groups.
158    
159    40. Ensure that libpcre is explicitly listed in the link commands for pcretest
160        and pcregrep, because some OS require shared objects to be explicitly
161        passed to ld, causing the link step to fail if they are not.
162    
163    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
164        mode, patterns that started with \h* or \R* might be incorrectly matched.
165    
166    
167    Version 8.30 04-February-2012
168    -----------------------------
169    
170    1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
171        name is defined in ctype.h.
172    
173    2.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
174        only in quite long subpatterns.
175    
176    3.  Removed the function pcre_info(), which has been obsolete and deprecated
177        since it was replaced by pcre_fullinfo() in February 2000.
178    
179    4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
180        match a (*MARK), and the match failed at the start of the subject, a
181        reference to memory before the start of the subject could occur. This bug
182        was introduced by fix 17 of release 8.21.
183    
184    5.  A reference to an unset group with zero minimum repetition was giving
185        totally wrong answers (in non-JavaScript-compatibility mode). For example,
186        /(another)?(\1?)test/ matched against "hello world test". This bug was
187        introduced in release 8.13.
188    
189    6.  Add support for 16-bit character strings (a large amount of work involving
190        many changes and refactorings).
191    
192    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
193        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
194        from a file.
195    
196    8.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
197        rounding is not applied in this particular case).
198    
199    9.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
200        if they appear, or are escaped, in patterns.
201    
202    10. Get rid of a number of -Wunused-but-set-variable warnings.
203    
204    11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
205        "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
206        Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
207        also returns the mark "x". This bug applied to capturing parentheses,
208        non-capturing parentheses, and atomic parentheses. It also applied to some
209        assertions.
210    
211    12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
212        information out of configure.ac instead of relying on pcre.h.generic, which
213        is not stored in the repository.
214    
215    13. Applied Dmitry V. Levin's patch for a more portable method for linking with
216        -lreadline.
217    
218    14. ZH added PCRE_CONFIG_JITTARGET; added its output to pcretest -C.
219    
220    15. Applied Graycode's patch to put the top-level frame on the stack rather
221        than the heap when not using the stack for recursion. This gives a
222        performance improvement in many cases when recursion is not deep.
223    
224    16. Experimental code added to "pcretest -C" to output the stack frame size.
225    
226    
227    Version 8.21 12-Dec-2011
228    ------------------------
229    
230    1.  Updating the JIT compiler.
231    
232    2.  JIT compiler now supports OP_NCREF, OP_RREF and OP_NRREF. New test cases
233        are added as well.
234    
235    3.  Fix cache-flush issue on PowerPC (It is still an experimental JIT port).
236        PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before
237        calling _pcre_jit_exec. Some extra comments are added.
238    
239    4.  (*MARK) settings inside atomic groups that do not contain any capturing
240        parentheses, for example, (?>a(*:m)), were not being passed out. This bug
241        was introduced by change 18 for 8.20.
242    
243    5.  Supporting of \x, \U and \u in JavaScript compatibility mode based on the
244        ECMA-262 standard.
245    
246    6.  Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were
247        erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
248        This bug was probably introduced by change 9 of 8.13.
249    
250    7.  While fixing 6 above, I noticed that a number of other items were being
251        incorrectly rejected as "not fixed length". This arose partly because newer
252        opcodes had not been added to the fixed-length checking code. I have (a)
253        corrected the bug and added tests for these items, and (b) arranged for an
254        error to occur if an unknown opcode is encountered while checking for fixed
255        length instead of just assuming "not fixed length". The items that were
256        rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
257        (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
258        repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
259    
260    8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
261        being incorrectly compiled and would have given unpredicatble results.
262    
263    9.  A possessively repeated subpattern with minimum repeat count greater than
264        one behaved incorrectly. For example, (A){2,}+ behaved as if it was
265        (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
266        the first (A) could occur when it should not.
267    
268    10. Add a cast and remove a redundant test from the code.
269    
270    11. JIT should use pcre_malloc/pcre_free for allocation.
271    
272    12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems
273        best practice nowadays, and helps with cross-compiling. (If the exec_prefix
274        is anything other than /usr, -L is still shown).
275    
276    13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.
277    
278    14. Perl does not support \N without a following name in a [] class; PCRE now
279        also gives an error.
280    
281    15. If a forward reference was repeated with an upper limit of around 2000,
282        it caused the error "internal error: overran compiling workspace". The
283        maximum number of forward references (including repeats) was limited by the
284        internal workspace, and dependent on the LINK_SIZE. The code has been
285        rewritten so that the workspace expands (via pcre_malloc) if necessary, and
286        the default depends on LINK_SIZE. There is a new upper limit (for safety)
287        of around 200,000 forward references. While doing this, I also speeded up
288        the filling in of repeated forward references.
289    
290    16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
291        incorrectly expecting the subject to contain another "a" after the start.
292    
293    17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
294        in the match, the SKIP should be ignored. This was not happening; instead
295        the SKIP was being treated as NOMATCH. For patterns such as
296        /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
297        tested.
298    
299    18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
300        now much more compatible with Perl, in particular in cases where the result
301        is a non-match for a non-anchored pattern. For example, if
302        /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
303        "m", where previously it did not return a name. A side effect of this
304        change is that for partial matches, the last encountered mark name is
305        returned, as for non matches. A number of tests that were previously not
306        Perl-compatible have been moved into the Perl-compatible test files. The
307        refactoring has had the pleasing side effect of removing one argument from
308        the match() function, thus reducing its stack requirements.
309    
310    19. If the /S+ option was used in pcretest to study a pattern using JIT,
311        subsequent uses of /S (without +) incorrectly behaved like /S+.
312    
313    21. Retrieve executable code size support for the JIT compiler and fixing
314        some warnings.
315    
316    22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
317        not work when the shorter character appeared right at the end of the
318        subject string.
319    
320    23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
321        systems.
322    
323    24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
324        output it when the /M option is used in pcretest.
325    
326    25. The CheckMan script was not being included in the distribution. Also, added
327        an explicit "perl" to run Perl scripts from the PrepareRelease script
328        because this is reportedly needed in Windows.
329    
330    26. If study data was being save in a file and studying had not found a set of
331        "starts with" bytes for the pattern, the data written to the file (though
332        never used) was taken from uninitialized memory and so caused valgrind to
333        complain.
334    
335    27. Updated RunTest.bat as provided by Sheri Pierce.
336    
337    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
338    
339    29. Computation of memory usage for the table of capturing group names was
340        giving an unnecessarily large value.
341    
342    
343    Version 8.20 21-Oct-2011
344    ------------------------
345    
346    1.  Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had
347        a POSIX class. After further experiments with Perl, which convinced me that
348        Perl has bugs and confusions, a closing square bracket is no longer allowed
349        in a POSIX name. This bug also affected patterns with classes that started
350        with full stops.
351    
352    2.  If a pattern such as /(a)b|ac/ is matched against "ac", there is no
353        captured substring, but while checking the failing first alternative,
354        substring 1 is temporarily captured. If the output vector supplied to
355        pcre_exec() was not big enough for this capture, the yield of the function
356        was still zero ("insufficient space for captured substrings"). This cannot
357        be totally fixed without adding another stack variable, which seems a lot
358        of expense for a edge case. However, I have improved the situation in cases
359        such as /(a)(b)x|abc/ matched against "abc", where the return code
360        indicates that fewer than the maximum number of slots in the ovector have
361        been set.
362    
363    3.  Related to (2) above: when there are more back references in a pattern than
364        slots in the output vector, pcre_exec() uses temporary memory during
365        matching, and copies in the captures as far as possible afterwards. It was
366        using the entire output vector, but this conflicts with the specification
367        that only 2/3 is used for passing back captured substrings. Now it uses
368        only the first 2/3, for compatibility. This is, of course, another edge
369        case.
370    
371    4.  Zoltan Herczeg's just-in-time compiler support has been integrated into the
372        main code base, and can be used by building with --enable-jit. When this is
373        done, pcregrep automatically uses it unless --disable-pcregrep-jit or the
374        runtime --no-jit option is given.
375    
376    5.  When the number of matches in a pcre_dfa_exec() run exactly filled the
377        ovector, the return from the function was zero, implying that there were
378        other matches that did not fit. The correct "exactly full" value is now
379        returned.
380    
381    6.  If a subpattern that was called recursively or as a subroutine contained
382        (*PRUNE) or any other control that caused it to give a non-standard return,
383        invalid errors such as "Error -26 (nested recursion at the same subject
384        position)" or even infinite loops could occur.
385    
386    7.  If a pattern such as /a(*SKIP)c|b(*ACCEPT)|/ was studied, it stopped
387        computing the minimum length on reaching *ACCEPT, and so ended up with the
388        wrong value of 1 rather than 0. Further investigation indicates that
389        computing a minimum subject length in the presence of *ACCEPT is difficult
390        (think back references, subroutine calls), and so I have changed the code
391        so that no minimum is registered for a pattern that contains *ACCEPT.
392    
393    8.  If (*THEN) was present in the first (true) branch of a conditional group,
394        it was not handled as intended. [But see 16 below.]
395    
396    9.  Replaced RunTest.bat and CMakeLists.txt with improved versions provided by
397        Sheri Pierce.
398    
399    10. A pathological pattern such as /(*ACCEPT)a/ was miscompiled, thinking that
400        the first byte in a match must be "a".
401    
402    11. Change 17 for 8.13 increased the recursion depth for patterns like
403        /a(?:.)*?a/ drastically. I've improved things by remembering whether a
404        pattern contains any instances of (*THEN). If it does not, the old
405        optimizations are restored. It would be nice to do this on a per-group
406        basis, but at the moment that is not feasible.
407    
408    12. In some environments, the output of pcretest -C is CRLF terminated. This
409        broke RunTest's code that checks for the link size. A single white space
410        character after the value is now allowed for.
411    
412    13. RunTest now checks for the "fr" locale as well as for "fr_FR" and "french".
413        For "fr", it uses the Windows-specific input and output files.
414    
415    14. If (*THEN) appeared in a group that was called recursively or as a
416        subroutine, it did not work as intended. [But see next item.]
417    
418    15. Consider the pattern /A (B(*THEN)C) | D/ where A, B, C, and D are complex
419        pattern fragments (but not containing any | characters). If A and B are
420        matched, but there is a failure in C so that it backtracks to (*THEN), PCRE
421        was behaving differently to Perl. PCRE backtracked into A, but Perl goes to
422        D. In other words, Perl considers parentheses that do not contain any |
423        characters to be part of a surrounding alternative, whereas PCRE was
424        treading (B(*THEN)C) the same as (B(*THEN)C|(*FAIL)) -- which Perl handles
425        differently. PCRE now behaves in the same way as Perl, except in the case
426        of subroutine/recursion calls such as (?1) which have in any case always
427        been different (but PCRE had them first :-).
428    
429    16. Related to 15 above: Perl does not treat the | in a conditional group as
430        creating alternatives. Such a group is treated in the same way as an
431        ordinary group without any | characters when processing (*THEN). PCRE has
432        been changed to match Perl's behaviour.
433    
434    17. If a user had set PCREGREP_COLO(U)R to something other than 1:31, the
435        RunGrepTest script failed.
436    
437    18. Change 22 for version 13 caused atomic groups to use more stack. This is
438        inevitable for groups that contain captures, but it can lead to a lot of
439        stack use in large patterns. The old behaviour has been restored for atomic
440        groups that do not contain any capturing parentheses.
441    
442    19. If the PCRE_NO_START_OPTIMIZE option was set for pcre_compile(), it did not
443        suppress the check for a minimum subject length at run time. (If it was
444        given to pcre_exec() or pcre_dfa_exec() it did work.)
445    
446    20. Fixed an ASCII-dependent infelicity in pcretest that would have made it
447        fail to work when decoding hex characters in data strings in EBCDIC
448        environments.
449    
450    21. It appears that in at least one Mac OS environment, the isxdigit() function
451        is implemented as a macro that evaluates to its argument more than once,
452        contravening the C 90 Standard (I haven't checked a later standard). There
453        was an instance in pcretest which caused it to go wrong when processing
454        \x{...} escapes in subject strings. The has been rewritten to avoid using
455        things like p++ in the argument of isxdigit().
456    
457    
458    Version 8.13 16-Aug-2011
459    ------------------------
460    
461    1.  The Unicode data tables have been updated to Unicode 6.0.0.
462    
463    2.  Two minor typos in pcre_internal.h have been fixed.
464    
465    3.  Added #include <string.h> to pcre_scanner_unittest.cc, pcrecpp.cc, and
466        pcrecpp_unittest.cc. They are needed for strcmp(), memset(), and strchr()
467        in some environments (e.g. Solaris 10/SPARC using Sun Studio 12U2).
468    
469    4.  There were a number of related bugs in the code for matching backrefences
470        caselessly in UTF-8 mode when codes for the characters concerned were
471        different numbers of bytes. For example, U+023A and U+2C65 are an upper
472        and lower case pair, using 2 and 3 bytes, respectively. The main bugs were:
473        (a) A reference to 3 copies of a 2-byte code matched only 2 of a 3-byte
474        code. (b) A reference to 2 copies of a 3-byte code would not match 2 of a
475        2-byte code at the end of the subject (it thought there wasn't enough data
476        left).
477    
478    5.  Comprehensive information about what went wrong is now returned by
479        pcre_exec() and pcre_dfa_exec() when the UTF-8 string check fails, as long
480        as the output vector has at least 2 elements. The offset of the start of
481        the failing character and a reason code are placed in the vector.
482    
483    6.  When the UTF-8 string check fails for pcre_compile(), the offset that is
484        now returned is for the first byte of the failing character, instead of the
485        last byte inspected. This is an incompatible change, but I hope it is small
486        enough not to be a problem. It makes the returned offset consistent with
487        pcre_exec() and pcre_dfa_exec().
488    
489    7.  pcretest now gives a text phrase as well as the error number when
490        pcre_exec() or pcre_dfa_exec() fails; if the error is a UTF-8 check
491        failure, the offset and reason code are output.
492    
493    8.  When \R was used with a maximizing quantifier it failed to skip backwards
494        over a \r\n pair if the subsequent match failed. Instead, it just skipped
495        back over a single character (\n). This seems wrong (because it treated the
496        two characters as a single entity when going forwards), conflicts with the
497        documentation that \R is equivalent to (?>\r\n|\n|...etc), and makes the
498        behaviour of \R* different to (\R)*, which also seems wrong. The behaviour
499        has been changed.
500    
501    9.  Some internal refactoring has changed the processing so that the handling
502        of the PCRE_CASELESS and PCRE_MULTILINE options is done entirely at compile
503        time (the PCRE_DOTALL option was changed this way some time ago: version
504        7.7 change 16). This has made it possible to abolish the OP_OPT op code,
505        which was always a bit of a fudge. It also means that there is one less
506        argument for the match() function, which reduces its stack requirements
507        slightly. This change also fixes an incompatibility with Perl: the pattern
508        (?i:([^b]))(?1) should not match "ab", but previously PCRE gave a match.
509    
510    10. More internal refactoring has drastically reduced the number of recursive
511        calls to match() for possessively repeated groups such as (abc)++ when
512        using pcre_exec().
513    
514    11. While implementing 10, a number of bugs in the handling of groups were
515        discovered and fixed:
516    
517        (?<=(a)+) was not diagnosed as invalid (non-fixed-length lookbehind).
518        (a|)*(?1) gave a compile-time internal error.
519        ((a|)+)+  did not notice that the outer group could match an empty string.
520        (^a|^)+   was not marked as anchored.
521        (.*a|.*)+ was not marked as matching at start or after a newline.
522    
523    12. Yet more internal refactoring has removed another argument from the match()
524        function. Special calls to this function are now indicated by setting a
525        value in a variable in the "match data" data block.
526    
527    13. Be more explicit in pcre_study() instead of relying on "default" for
528        opcodes that mean there is no starting character; this means that when new
529        ones are added and accidentally left out of pcre_study(), testing should
530        pick them up.
531    
532    14. The -s option of pcretest has been documented for ages as being an old
533        synonym of -m (show memory usage). I have changed it to mean "force study
534        for every regex", that is, assume /S for every regex. This is similar to -i
535        and -d etc. It's slightly incompatible, but I'm hoping nobody is still
536        using it. It makes it easier to run collections of tests with and without
537        study enabled, and thereby test pcre_study() more easily. All the standard
538        tests are now run with and without -s (but some patterns can be marked as
539        "never study" - see 20 below).
540    
541    15. When (*ACCEPT) was used in a subpattern that was called recursively, the
542        restoration of the capturing data to the outer values was not happening
543        correctly.
544    
545    16. If a recursively called subpattern ended with (*ACCEPT) and matched an
546        empty string, and PCRE_NOTEMPTY was set, pcre_exec() thought the whole
547        pattern had matched an empty string, and so incorrectly returned a no
548        match.
549    
550    17. There was optimizing code for the last branch of non-capturing parentheses,
551        and also for the obeyed branch of a conditional subexpression, which used
552        tail recursion to cut down on stack usage. Unfortunately, now that there is
553        the possibility of (*THEN) occurring in these branches, tail recursion is
554        no longer possible because the return has to be checked for (*THEN). These
555        two optimizations have therefore been removed. [But see 8.20/11 above.]
556    
557    18. If a pattern containing \R was studied, it was assumed that \R always
558        matched two bytes, thus causing the minimum subject length to be
559        incorrectly computed because \R can also match just one byte.
560    
561    19. If a pattern containing (*ACCEPT) was studied, the minimum subject length
562        was incorrectly computed.
563    
564    20. If /S is present twice on a test pattern in pcretest input, it now
565        *disables* studying, thereby overriding the use of -s on the command line
566        (see 14 above). This is necessary for one or two tests to keep the output
567        identical in both cases.
568    
569    21. When (*ACCEPT) was used in an assertion that matched an empty string and
570        PCRE_NOTEMPTY was set, PCRE applied the non-empty test to the assertion.
571    
572    22. When an atomic group that contained a capturing parenthesis was
573        successfully matched, but the branch in which it appeared failed, the
574        capturing was not being forgotten if a higher numbered group was later
575        captured. For example, /(?>(a))b|(a)c/ when matching "ac" set capturing
576        group 1 to "a", when in fact it should be unset. This applied to multi-
577        branched capturing and non-capturing groups, repeated or not, and also to
578        positive assertions (capturing in negative assertions does not happen
579        in PCRE) and also to nested atomic groups.
580    
581    23. Add the ++ qualifier feature to pcretest, to show the remainder of the
582        subject after a captured substring, to make it easier to tell which of a
583        number of identical substrings has been captured.
584    
585    24. The way atomic groups are processed by pcre_exec() has been changed so that
586        if they are repeated, backtracking one repetition now resets captured
587        values correctly. For example, if ((?>(a+)b)+aabab) is matched against
588        "aaaabaaabaabab" the value of captured group 2 is now correctly recorded as
589        "aaa". Previously, it would have been "a". As part of this code
590        refactoring, the way recursive calls are handled has also been changed.
591    
592    25. If an assertion condition captured any substrings, they were not passed
593        back unless some other capturing happened later. For example, if
594        (?(?=(a))a) was matched against "a", no capturing was returned.
595    
596    26. When studying a pattern that contained subroutine calls or assertions,
597        the code for finding the minimum length of a possible match was handling
598        direct recursions such as (xxx(?1)|yyy) but not mutual recursions (where
599        group 1 called group 2 while simultaneously a separate group 2 called group
600        1). A stack overflow occurred in this case. I have fixed this by limiting
601        the recursion depth to 10.
602    
603    27. Updated RunTest.bat in the distribution to the version supplied by Tom
604        Fortmann. This supports explicit test numbers on the command line, and has
605        argument validation and error reporting.
606    
607    28. An instance of \X with an unlimited repeat could fail if at any point the
608        first character it looked at was a mark character.
609    
610    29. Some minor code refactoring concerning Unicode properties and scripts
611        should reduce the stack requirement of match() slightly.
612    
613    30. Added the '=' option to pcretest to check the setting of unused capturing
614        slots at the end of the pattern, which are documented as being -1, but are
615        not included in the return count.
616    
617    31. If \k was not followed by a braced, angle-bracketed, or quoted name, PCRE
618        compiled something random. Now it gives a compile-time error (as does
619        Perl).
620    
621    32. A *MARK encountered during the processing of a positive assertion is now
622        recorded and passed back (compatible with Perl).
623    
624    33. If --only-matching or --colour was set on a pcregrep call whose pattern
625        had alternative anchored branches, the search for a second match in a line
626        was done as if at the line start. Thus, for example, /^01|^02/ incorrectly
627        matched the line "0102" twice. The same bug affected patterns that started
628        with a backwards assertion. For example /\b01|\b02/ also matched "0102"
629        twice.
630    
631    34. Previously, PCRE did not allow quantification of assertions. However, Perl
632        does, and because of capturing effects, quantifying parenthesized
633        assertions may at times be useful. Quantifiers are now allowed for
634        parenthesized assertions.
635    
636    35. A minor code tidy in pcre_compile() when checking options for \R usage.
637    
638    36. \g was being checked for fancy things in a character class, when it should
639        just be a literal "g".
640    
641    37. PCRE was rejecting [:a[:digit:]] whereas Perl was not. It seems that the
642        appearance of a nested POSIX class supersedes an apparent external class.
643        For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,
644        unescaped square brackets may also appear as part of class names. For
645        example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves
646        more like Perl. (But see 8.20/1 above.)
647    
648    38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this
649        was because it thought it was \N{name}, which is not supported).
650    
651    39. Add minix to OS list not supporting the -S option in pcretest.
652    
653    40. PCRE tries to detect cases of infinite recursion at compile time, but it
654        cannot analyze patterns in sufficient detail to catch mutual recursions
655        such as ((?1))((?2)). There is now a runtime test that gives an error if a
656        subgroup is called recursively as a subpattern for a second time at the
657        same position in the subject string. In previous releases this might have
658        been caught by the recursion limit, or it might have run out of stack.
659    
660    41. A pattern such as /(?(R)a+|(?R)b)/ is quite safe, as the recursion can
661        happen only once. PCRE was, however incorrectly giving a compile time error
662        "recursive call could loop indefinitely" because it cannot analyze the
663        pattern in sufficient detail. The compile time test no longer happens when
664        PCRE is compiling a conditional subpattern, but actual runaway loops are
665        now caught at runtime (see 40 above).
666    
667    42. It seems that Perl allows any characters other than a closing parenthesis
668        to be part of the NAME in (*MARK:NAME) and other backtracking verbs. PCRE
669        has been changed to be the same.
670    
671    43. Updated configure.ac to put in more quoting round AC_LANG_PROGRAM etc. so
672        as not to get warnings when autogen.sh is called. Also changed
673        AC_PROG_LIBTOOL (deprecated) to LT_INIT (the current macro).
674    
675    44. To help people who use pcregrep to scan files containing exceedingly long
676        lines, the following changes have been made:
677    
678        (a) The default value of the buffer size parameter has been increased from
679            8K to 20K. (The actual buffer used is three times this size.)
680    
681        (b) The default can be changed by ./configure --with-pcregrep-bufsize when
682            PCRE is built.
683    
684        (c) A --buffer-size=n option has been added to pcregrep, to allow the size
685            to be set at run time.
686    
687        (d) Numerical values in pcregrep options can be followed by K or M, for
688            example --buffer-size=50K.
689    
690        (e) If a line being scanned overflows pcregrep's buffer, an error is now
691            given and the return code is set to 2.
692    
693    45. Add a pointer to the latest mark to the callout data block.
694    
695    46. The pattern /.(*F)/, when applied to "abc" with PCRE_PARTIAL_HARD, gave a
696        partial match of an empty string instead of no match. This was specific to
697        the use of ".".
698    
699    47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a
700        complete match instead of a partial match. This bug was dependent on both
701        the PCRE_UTF8 and PCRE_DOTALL options being set.
702    
703    48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the
704        starting byte set, because \b was not being ignored.
705    
706    
707    Version 8.12 15-Jan-2011
708    ------------------------
709    
710    1.  Fixed some typos in the markup of the man pages, and wrote a script that
711        checks for such things as part of the documentation building process.
712    
713    2.  On a big-endian 64-bit system, pcregrep did not correctly process the
714        --match-limit and --recursion-limit options (added for 8.11). In
715        particular, this made one of the standard tests fail. (The integer value
716        went into the wrong half of a long int.)
717    
718    3.  If the --colour option was given to pcregrep with -v (invert match), it
719        did strange things, either producing crazy output, or crashing. It should,
720        of course, ignore a request for colour when reporting lines that do not
721        match.
722    
723    4.  Another pcregrep bug caused similar problems if --colour was specified with
724        -M (multiline) and the pattern match finished with a line ending.
725    
726    5.  In pcregrep, when a pattern that ended with a literal newline sequence was
727        matched in multiline mode, the following line was shown as part of the
728        match. This seems wrong, so I have changed it.
729    
730    6.  Another pcregrep bug in multiline mode, when --colour was specified, caused
731        the check for further matches in the same line (so they could be coloured)
732        to overrun the end of the current line. If another match was found, it was
733        incorrectly shown (and then shown again when found in the next line).
734    
735    7.  If pcregrep was compiled under Windows, there was a reference to the
736        function pcregrep_exit() before it was defined. I am assuming this was
737        the cause of the "error C2371: 'pcregrep_exit' : redefinition;" that was
738        reported by a user. I've moved the definition above the reference.
739    
740    
741    Version 8.11 10-Dec-2010
742  ------------------------  ------------------------
743    
744  1.  (*THEN) was not working properly if there were untried alternatives prior  1.  (*THEN) was not working properly if there were untried alternatives prior
745      to it in the current branch. For example, in ((a|b)(*THEN)(*F)|c..) it      to it in the current branch. For example, in ((a|b)(*THEN)(*F)|c..) it
746      backtracked to try for "b" instead of moving to the next alternative branch      backtracked to try for "b" instead of moving to the next alternative branch
747      at the same level (in this case, to look for "c"). The Perl documentation      at the same level (in this case, to look for "c"). The Perl documentation
748      is clear that when (*THEN) is backtracked onto, it goes to the "next      is clear that when (*THEN) is backtracked onto, it goes to the "next
749      alternative in the innermost enclosing group".      alternative in the innermost enclosing group".
750    
751  2.  (*COMMIT) was not overriding (*THEN), as it does in Perl. In a pattern  2.  (*COMMIT) was not overriding (*THEN), as it does in Perl. In a pattern
752      such as   (A(*COMMIT)B(*THEN)C|D)  any failure after matching A should      such as   (A(*COMMIT)B(*THEN)C|D)  any failure after matching A should
753      result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and      result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and
754      (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides      (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides
755      (*THEN).      (*THEN).
756    
757  3.  If \s appeared in a character class, it removed the VT character from  3.  If \s appeared in a character class, it removed the VT character from
758      the class, even if it had been included by some previous item, for example      the class, even if it had been included by some previous item, for example
759      in [\x00-\xff\s]. (This was a bug related to the fact that VT is not part      in [\x00-\xff\s]. (This was a bug related to the fact that VT is not part
760      of \s, but is part of the POSIX "space" class.)      of \s, but is part of the POSIX "space" class.)
761    
762  4.  A partial match never returns an empty string (because you can always  4.  A partial match never returns an empty string (because you can always
763      match an empty string at the end of the subject); however the checking for      match an empty string at the end of the subject); however the checking for
764      an empty string was starting at the "start of match" point. This has been      an empty string was starting at the "start of match" point. This has been
# Line 31  Version 8.11 10-Oct-2010 Line 768  Version 8.11 10-Oct-2010
768      (previously it gave "no match").      (previously it gave "no match").
769    
770  5.  Changes have been made to the way PCRE_PARTIAL_HARD affects the matching  5.  Changes have been made to the way PCRE_PARTIAL_HARD affects the matching
771      of $, \z, \Z, \b, and \B. If the match point is at the end of the string,      of $, \z, \Z, \b, and \B. If the match point is at the end of the string,
772      previously a full match would be given. However, setting PCRE_PARTIAL_HARD      previously a full match would be given. However, setting PCRE_PARTIAL_HARD
773      has an implication that the given string is incomplete (because a partial      has an implication that the given string is incomplete (because a partial
774      match is preferred over a full match). For this reason, these items now      match is preferred over a full match). For this reason, these items now
775      give a partial match in this situation. [Aside: previously, the one case      give a partial match in this situation. [Aside: previously, the one case
776      /t\b/ matched against "cat" with PCRE_PARTIAL_HARD set did return a partial      /t\b/ matched against "cat" with PCRE_PARTIAL_HARD set did return a partial
777      match rather than a full match, which was wrong by the old rules, but is      match rather than a full match, which was wrong by the old rules, but is
778      now correct.]      now correct.]
779    
780  6.  There was a bug in the handling of #-introduced comments, recognized when  6.  There was a bug in the handling of #-introduced comments, recognized when
781      PCRE_EXTENDED is set, when PCRE_NEWLINE_ANY and PCRE_UTF8 were also set.      PCRE_EXTENDED is set, when PCRE_NEWLINE_ANY and PCRE_UTF8 were also set.
782      If a UTF-8 multi-byte character included the byte 0x85 (e.g. +U0445, whose      If a UTF-8 multi-byte character included the byte 0x85 (e.g. +U0445, whose
783      UTF-8 encoding is 0xd1,0x85), this was misinterpreted as a newline when      UTF-8 encoding is 0xd1,0x85), this was misinterpreted as a newline when
784      scanning for the end of the comment. (*Character* 0x85 is an "any" newline,      scanning for the end of the comment. (*Character* 0x85 is an "any" newline,
785      but *byte* 0x85 is not, in UTF-8 mode). This bug was present in several      but *byte* 0x85 is not, in UTF-8 mode). This bug was present in several
786      places in pcre_compile().      places in pcre_compile().
787    
788  7.  Related to (6) above, when pcre_compile() was skipping #-introduced  7.  Related to (6) above, when pcre_compile() was skipping #-introduced
789      comments when looking ahead for named forward references to subpatterns,      comments when looking ahead for named forward references to subpatterns,
790      the only newline sequence it recognized was NL. It now handles newlines      the only newline sequence it recognized was NL. It now handles newlines
791      according to the set newline convention.      according to the set newline convention.
792    
793  8.  SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the  8.  SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the
794      former, but used strtoul(), whereas pcretest avoided strtoul() but did not      former, but used strtoul(), whereas pcretest avoided strtoul() but did not
795      cater for a lack of strerror(). These oversights have been fixed.      cater for a lack of strerror(). These oversights have been fixed.
796    
797  9.  Added --match-limit and --recursion-limit to pcregrep.  9.  Added --match-limit and --recursion-limit to pcregrep.
798    
799  10. Added two casts needed to build with Visual Studio when NO_RECURSE is set.  10. Added two casts needed to build with Visual Studio when NO_RECURSE is set.
800    
801  11. When the -o option was used, pcregrep was setting a return code of 1, even  11. When the -o option was used, pcregrep was setting a return code of 1, even
802      when matches were found, and --line-buffered was not being honoured.      when matches were found, and --line-buffered was not being honoured.
803    
804  12. Added an optional parentheses number to the -o and --only-matching options  12. Added an optional parentheses number to the -o and --only-matching options
805      of pcregrep.      of pcregrep.
806    
807  13. Imitating Perl's /g action for multiple matches is tricky when the pattern  13. Imitating Perl's /g action for multiple matches is tricky when the pattern
808      can match an empty string. The code to do it in pcretest and pcredemo      can match an empty string. The code to do it in pcretest and pcredemo
809      needed fixing:      needed fixing:
810    
811      (a) When the newline convention was "crlf", pcretest got it wrong, skipping      (a) When the newline convention was "crlf", pcretest got it wrong, skipping
812          only one byte after an empty string match just before CRLF (this case          only one byte after an empty string match just before CRLF (this case
813          just got forgotten; "any" and "anycrlf" were OK).          just got forgotten; "any" and "anycrlf" were OK).
814    
815      (b) The pcretest code also had a bug, causing it to loop forever in UTF-8      (b) The pcretest code also had a bug, causing it to loop forever in UTF-8
816          mode when an empty string match preceded an ASCII character followed by          mode when an empty string match preceded an ASCII character followed by
817          a non-ASCII character. (The code for advancing by one character rather          a non-ASCII character. (The code for advancing by one character rather
818          than one byte was nonsense.)          than one byte was nonsense.)
819    
820      (c) The pcredemo.c sample program did not have any code at all to handle      (c) The pcredemo.c sample program did not have any code at all to handle
821          the cases when CRLF is a valid newline sequence.          the cases when CRLF is a valid newline sequence.
822    
823  14. Neither pcre_exec() nor pcre_dfa_exec() was checking that the value given  14. Neither pcre_exec() nor pcre_dfa_exec() was checking that the value given
824      as a starting offset was within the subject string. There is now a new      as a starting offset was within the subject string. There is now a new
825      error, PCRE_ERROR_BADOFFSET, which is returned if the starting offset is      error, PCRE_ERROR_BADOFFSET, which is returned if the starting offset is
826      negative or greater than the length of the string. In order to test this,      negative or greater than the length of the string. In order to test this,
827      pcretest is extended to allow the setting of negative starting offsets.      pcretest is extended to allow the setting of negative starting offsets.
828    
829  15. In both pcre_exec() and pcre_dfa_exec() the code for checking that the  15. In both pcre_exec() and pcre_dfa_exec() the code for checking that the
830      starting offset points to the beginning of a UTF-8 character was      starting offset points to the beginning of a UTF-8 character was
831      unnecessarily clumsy. I tidied it up.      unnecessarily clumsy. I tidied it up.
832    
833  16. Added PCRE_ERROR_SHORTUTF8 to make it possible to distinguish between a  16. Added PCRE_ERROR_SHORTUTF8 to make it possible to distinguish between a
834      bad UTF-8 sequence and one that is incomplete.      bad UTF-8 sequence and one that is incomplete when using PCRE_PARTIAL_HARD.
835    
836  17. Nobody had reported that the --include_dir option, which was added in  17. Nobody had reported that the --include_dir option, which was added in
837      release 7.7 should have been called --include-dir (hyphen, not underscore)      release 7.7 should have been called --include-dir (hyphen, not underscore)
838      for compatibility with GNU grep. I have changed it to --include-dir, but      for compatibility with GNU grep. I have changed it to --include-dir, but
839      left --include_dir as an undocumented synonym, and the same for      left --include_dir as an undocumented synonym, and the same for
840      --exclude-dir, though that is not available in GNU grep, at least as of      --exclude-dir, though that is not available in GNU grep, at least as of
841      release 2.5.4.      release 2.5.4.
842    
843  18. At a user's suggestion, the macros GETCHAR and friends (which pick up UTF-8  18. At a user's suggestion, the macros GETCHAR and friends (which pick up UTF-8
844      characters from a string of bytes) have been redefined so as not to use      characters from a string of bytes) have been redefined so as not to use
845      loops, in order to improve performance in some environments. At the same      loops, in order to improve performance in some environments. At the same
846      time, I abstracted some of the common code into auxiliary macros to save      time, I abstracted some of the common code into auxiliary macros to save
847      repetition (this should not affect the compiled code).      repetition (this should not affect the compiled code).
848    
849  19. If \c was followed by a multibyte UTF-8 character, bad things happened. A  19. If \c was followed by a multibyte UTF-8 character, bad things happened. A
850      compile-time error is now given if \c is not followed by an ASCII      compile-time error is now given if \c is not followed by an ASCII
851      character, that is, a byte less than 128. (In EBCDIC mode, the code is      character, that is, a byte less than 128. (In EBCDIC mode, the code is
852      different, and any byte value is allowed.)      different, and any byte value is allowed.)
853    
854  20. Recognize (*NO_START_OPT) at the start of a pattern to set the PCRE_NO_  20. Recognize (*NO_START_OPT) at the start of a pattern to set the PCRE_NO_
855      START_OPTIMIZE option, which is now allowed at compile time - but just      START_OPTIMIZE option, which is now allowed at compile time - but just
856      passed through to pcre_exec() or pcre_dfa_exec(). This makes it available      passed through to pcre_exec() or pcre_dfa_exec(). This makes it available
857      to pcregrep and other applications that have no direct access to PCRE      to pcregrep and other applications that have no direct access to PCRE
858      options. The new /Y option in pcretest sets this option when calling      options. The new /Y option in pcretest sets this option when calling
859      pcre_compile().      pcre_compile().
860    
861    21. Change 18 of release 8.01 broke the use of named subpatterns for recursive
862        back references. Groups containing recursive back references were forced to
863        be atomic by that change, but in the case of named groups, the amount of
864        memory required was incorrectly computed, leading to "Failed: internal
865        error: code overflow". This has been fixed.
866    
867    22. Some patches to pcre_stringpiece.h, pcre_stringpiece_unittest.cc, and
868        pcretest.c, to avoid build problems in some Borland environments.
869    
870    
871  Version 8.10 25-Jun-2010  Version 8.10 25-Jun-2010

Legend:
Removed from v.576  
changed lines
  Added in v.987

  ViewVC Help
Powered by ViewVC 1.1.5