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

Diff of /code/trunk/ChangeLog

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

revision 807 by ph10, Sun Dec 18 10:03:38 2011 UTC revision 835 by ph10, Wed Dec 28 16:10:09 2011 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.22  Version 8.21
5  ------------  ------------
6    
 1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this  
     name is defined in ctype.h.  
   
 2.  Fixed a bug in the code for calculating the fixed length of lookbehind  
     assertions.  
   
   
 Version 8.21 12-Dec-2011  
 ------------------------  
   
7  1.  Updating the JIT compiler.  1.  Updating the JIT compiler.
8    
9  2.  JIT compiler now supports OP_NCREF, OP_RREF and OP_NRREF. New test cases  2.  JIT compiler now supports OP_NCREF, OP_RREF and OP_NRREF. New test cases
# Line 23  Version 8.21 12-Dec-2011 Line 13  Version 8.21 12-Dec-2011
13      PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before      PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before
14      calling _pcre_jit_exec. Some extra comments are added.      calling _pcre_jit_exec. Some extra comments are added.
15    
16  4.  (*MARK) settings inside atomic groups that do not contain any capturing  4.  Mark settings inside atomic groups that do not contain any capturing
17      parentheses, for example, (?>a(*:m)), were not being passed out. This bug      parentheses, for example, (?>a(*:m)), were not being passed out. This bug
18      was introduced by change 18 for 8.20.      was introduced by change 18 for 8.20.
19    
# Line 32  Version 8.21 12-Dec-2011 Line 22  Version 8.21 12-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    
 14. Perl does not support \N without a following name in a [] class; PCRE now  
     also gives an error.  
   
 15. If a forward reference was repeated with an upper limit of around 2000,  
     it caused the error "internal error: overran compiling workspace". The  
     maximum number of forward references (including repeats) was limited by the  
     internal workspace, and dependent on the LINK_SIZE. The code has been  
     rewritten so that the workspace expands (via pcre_malloc) if necessary, and  
     the default depends on LINK_SIZE. There is a new upper limit (for safety)  
     of around 200,000 forward references. While doing this, I also speeded up  
     the filling in of repeated forward references.  
   
 16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was  
     incorrectly expecting the subject to contain another "a" after the start.  
   
 17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier  
     in the match, the SKIP should be ignored. This was not happening; instead  
     the SKIP was being treated as NOMATCH. For patterns such as  
     /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never  
     tested.  
   
 18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is  
     now much more compatible with Perl, in particular in cases where the result  
     is a non-match for a non-anchored pattern. For example, if  
     /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name  
     "m", where previously it did not return a name. A side effect of this  
     change is that for partial matches, the last encountered mark name is  
     returned, as for non matches. A number of tests that were previously not  
     Perl-compatible have been moved into the Perl-compatible test files. The  
     refactoring has had the pleasing side effect of removing one argument from  
     the match() function, thus reducing its stack requirements.  
   
 19. If the /S+ option was used in pcretest to study a pattern using JIT,  
     subsequent uses of /S (without +) incorrectly behaved like /S+.  
   
 21. Retrieve executable code size support for the JIT compiler and fixing  
     some warnings.  
   
 22. A caseless match of a UTF-8 character whose other case uses fewer bytes did  
     not work when the shorter character appeared right at the end of the  
     subject string.  
   
 23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit  
     systems.  
   
 24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also  
     output it when the /M option is used in pcretest.  
   
 25. The CheckMan script was not being included in the distribution. Also, added  
     an explicit "perl" to run Perl scripts from the PrepareRelease script  
     because this is reportedly needed in Windows.  
   
 26. If study data was being save in a file and studying had not found a set of  
     "starts with" bytes for the pattern, the data written to the file (though  
     never used) was taken from uninitialized memory and so caused valgrind to  
     complain.  
   
 27. Updated RunTest.bat as provided by Sheri Pierce.  
   
 28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.  
   
 29. Computation of memory usage for the table of capturing group names was  
     giving an unnecessarily large value.  
   
55    
56  Version 8.20 21-Oct-2011  Version 8.20 21-Oct-2011
57  ------------------------  ------------------------
Legend:
Removed from v.807  
changed lines
  Added in v.835
  ViewVC Help
Powered by ViewVC 1.1.5