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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.565  
changed lines
  Added in v.964

  ViewVC Help
Powered by ViewVC 1.1.5