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

Diff of /code/trunk/ChangeLog

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

revision 784 by ph10, Mon Dec 5 12:33:44 2011 UTC revision 787 by ph10, Tue Dec 6 15:37:24 2011 UTC
# Line 22  Version 8.21 05-Dec-2011 Line 22  Version 8.21 05-Dec-2011
22    
23  6.  Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were  6.  Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were
24      erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.      erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
25      This bug was probably introduced by change 9 of 8.13.      This bug was probably introduced by change 9 of 8.13.
26    
27  7.  While fixing 6 above, I noticed that a number of other items were being  7.  While fixing 6 above, I noticed that a number of other items were being
28      incorrectly rejected as "not fixed length". This arose partly because newer      incorrectly rejected as "not fixed length". This arose partly because newer
29      opcodes had not been added to the fixed-length checking code. I have (a)      opcodes had not been added to the fixed-length checking code. I have (a)
30      corrected the bug and added tests for these items, and (b) arranged for an      corrected the bug and added tests for these items, and (b) arranged for an
31      error to occur if an unknown opcode is encountered while checking for fixed      error to occur if an unknown opcode is encountered while checking for fixed
32      length instead of just assuming "not fixed length". The items that were      length instead of just assuming "not fixed length". The items that were
33      rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),      rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
34      (*THEN), \h, \H, \v, \V, and single character negative classes with fixed      (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
35      repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.      repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
36    
37  8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was  8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
38      being incorrectly compiled and would have given unpredicatble results.      being incorrectly compiled and would have given unpredicatble results.
39    
40  9.  A possessively repeated subpattern with minimum repeat count greater than  9.  A possessively repeated subpattern with minimum repeat count greater than
41      one behaved incorrectly. For example, (A){2,}+ behaved as if it was      one behaved incorrectly. For example, (A){2,}+ behaved as if it was
42      (A)(A)++ which meant that, after a subsequent mismatch, backtracking into      (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
43      the first (A) could occur when it should not.      the first (A) could occur when it should not.
44    
45  10. Add a cast and remove a redundant test from the code.  10. Add a cast and remove a redundant test from the code.
46    
47  11. JIT should use pcre_malloc/pcre_free for allocation.  11. JIT should use pcre_malloc/pcre_free for allocation.
48    
49  12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems  12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems
50      best practice nowadays, and helps with cross-compiling. (If the exec_prefix      best practice nowadays, and helps with cross-compiling. (If the exec_prefix
51      is anything other than /usr, -L is still shown).      is anything other than /usr, -L is still shown).
52    
53  13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.  13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.
54    
55  14. Perl does not support \N without a following name in a [] class; PCRE now  14. Perl does not support \N without a following name in a [] class; PCRE now
56      also gives an error.      also gives an error.
57    
58  15. If a forward reference was repeated with an upper limit of around 2000,  15. If a forward reference was repeated with an upper limit of around 2000,
59      it caused the error "internal error: overran compiling workspace". The      it caused the error "internal error: overran compiling workspace". The
60      maximum number of forward references (including repeats) was limited by the      maximum number of forward references (including repeats) was limited by the
61      internal workspace, and dependent on the LINK_SIZE. The code has been      internal workspace, and dependent on the LINK_SIZE. The code has been
62      rewritten so that the workspace expands (via pcre_malloc) if necessary, and      rewritten so that the workspace expands (via pcre_malloc) if necessary, and
63      the default depends on LINK_SIZE. There is a new upper limit (for safety)      the default depends on LINK_SIZE. There is a new upper limit (for safety)
64      of around 200,000 forward references. While doing this, I also speeded up      of around 200,000 forward references. While doing this, I also speeded up
65      the filling in of repeated forward references.      the filling in of repeated forward references.
66    
67  16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was  16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
68      incorrectly expecting the subject to contain another "a" after the start.      incorrectly expecting the subject to contain another "a" after the start.
69    
70  17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier  17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
71      in the match, the SKIP should be ignored. This was not happening; instead      in the match, the SKIP should be ignored. This was not happening; instead
72      the SKIP was being treated as NOMATCH. For patterns such as      the SKIP was being treated as NOMATCH. For patterns such as
73      /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never      /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
74      tested.      tested.
75    
76  18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is  18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
77      now much more compatible with Perl, in particular in cases where the result      now much more compatible with Perl, in particular in cases where the result
78      is a non-match for a non-anchored pattern. For example, if      is a non-match for a non-anchored pattern. For example, if
79      /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name      /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
80      "m", where previously it did not return a name. A side effect of this      "m", where previously it did not return a name. A side effect of this
81      change is that for partial matches, the last encountered mark name is      change is that for partial matches, the last encountered mark name is
82      returned, as for non matches. A number of tests that were previously not      returned, as for non matches. A number of tests that were previously not
83      Perl-compatible have been moved into the Perl-compatible test files. The      Perl-compatible have been moved into the Perl-compatible test files. The
84      refactoring has had the pleasing side effect of removing one argument from      refactoring has had the pleasing side effect of removing one argument from
85      the match() function, thus reducing its stack requirements.      the match() function, thus reducing its stack requirements.
86    
87  19. If the /S+ option was used in pcretest to study a pattern using JIT,  19. If the /S+ option was used in pcretest to study a pattern using JIT,
88      subsequent uses of /S (without +) incorrectly behaved like /S+.      subsequent uses of /S (without +) incorrectly behaved like /S+.
89    
90  21. Retrieve executable code size support for the JIT compiler and fixing  21. Retrieve executable code size support for the JIT compiler and fixing
91      some warnings.      some warnings.
92    
93  22. A caseless match of a UTF-8 character whose other case uses fewer bytes did  22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
94      not work when the shorter character appeared right at the end of the      not work when the shorter character appeared right at the end of the
95      subject string.      subject string.
96    
97  23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit  23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
98      systems.      systems.
99    
100  24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also  24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
101      output it when the /M option is used in pcretest.      output it when the /M option is used in pcretest.
102    
103  25. The CheckMan script was not being included in the distribution. Also, added  25. The CheckMan script was not being included in the distribution. Also, added
104      an explicit "perl" to run Perl scripts from the PrepareRelease script      an explicit "perl" to run Perl scripts from the PrepareRelease script
105      because this is reportedly needed in Windows.      because this is reportedly needed in Windows.
106    
107    26. If study data was being save in a file and studying had not found a set of
108        "starts with" bytes for the pattern, the data written to the file (though
109        never used) was taken from uninitialized memory and so caused valgrind to
110        complain.
111    
112    
113  Version 8.20 21-Oct-2011  Version 8.20 21-Oct-2011

Legend:
Removed from v.784  
changed lines
  Added in v.787

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12