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

Diff of /code/trunk/ChangeLog

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

revision 659 by ph10, Tue Aug 16 09:48:29 2011 UTC revision 687 by ph10, Tue Sep 6 16:09:43 2011 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4    Version 8.20
5    ------------
6    
7    1. Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had
8       a POSIX class. After further experiments with Perl, which convinced me that
9       Perl has bugs and confusions, a closing square bracket is no longer allowed
10       in a POSIX name.
11    
12    2. If a pattern such as /(a)b|ac/ is matched against "ac", there is no captured
13       substring, but while checking the failing first alternative, substring 1 is
14       temporarily captured. If the output vector supplied to pcre_exec() was not
15       big enough for this capture, the yield of the function was still zero
16       ("insufficient space for captured substrings"). This cannot be totally fixed
17       without adding another stack variable, which seems a lot of expense for a
18       edge case. However, I have improved the situation in cases such as
19       /(a)(b)x|abc/ matched against "abc", where the return code indicates that
20       fewer than the maximum number of slots in the ovector have been set.
21    
22    3. Related to (2) above: when there are more back references in a pattern than
23       slots in the output vector, pcre_exec() uses temporary memory during
24       matching, and copies in the captures as far as possible afterwards. It was
25       using the entire output vector, but this conflicts with the specification
26       that only 2/3 is used for passing back captured substrings. Now it uses only
27       the first 2/3, for compatibility. This is, of course, another edge case.
28    
29    4. Zoltan Herczeg's just-in-time compiler support has been integrated into the
30       main code base, and can be used by building with --enable-jit. When this is
31       done, pcregrep automatically uses it unless --disable-pcregrep-jit or the
32       runtime --no-jit option is given.
33    
34    5. When the number of matches in a pcre_dfa_exec() run exactly filled the
35       ovector, the return from the function was zero, implying that there were
36       other matches that did not fit. The correct "exactly full" value is now
37       returned.
38    
39    6. If a subpattern that was called recursively or as a subroutine contained
40       (*PRUNE) or any other control that caused it to give a non-standard return,
41       invalid errors such as "Error -26 (nested recursion at the same subject
42       position)" or even infinite loops could occur.
43    
44    
45  Version 8.13 16-Aug-2011  Version 8.13 16-Aug-2011
46  ------------------------  ------------------------
47    
# Line 189  Version 8.13 16-Aug-2011 Line 230  Version 8.13 16-Aug-2011
230      For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,      For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,
231      unescaped square brackets may also appear as part of class names. For      unescaped square brackets may also appear as part of class names. For
232      example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves      example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves
233      more like Perl.      more like Perl. (But see 8.20/1 above.)
234    
235  38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this  38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this
236      was because it thought it was \N{name}, which is not supported).      was because it thought it was \N{name}, which is not supported).

Legend:
Removed from v.659  
changed lines
  Added in v.687

  ViewVC Help
Powered by ViewVC 1.1.5