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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.573  
changed lines
  Added in v.974

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12