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

Diff of /code/trunk/ChangeLog

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

revision 773 by ph10, Wed Nov 30 18:10:27 2011 UTC revision 807 by ph10, Sun Dec 18 10:03:38 2011 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.21  Version 8.22
5  ------------  ------------
6    
7    1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
8        name is defined in ctype.h.
9    
10    2.  Fixed a bug in the code for calculating the fixed length of lookbehind
11        assertions.
12    
13    
14    Version 8.21 12-Dec-2011
15    ------------------------
16    
17  1.  Updating the JIT compiler.  1.  Updating the JIT compiler.
18    
19  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 13  Version 8.21 Line 23  Version 8.21
23      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
24      calling _pcre_jit_exec. Some extra comments are added.      calling _pcre_jit_exec. Some extra comments are added.
25    
26  4.  Mark settings inside atomic groups that do not contain any capturing  4.  (*MARK) settings inside atomic groups that do not contain any capturing
27      parentheses, for example, (?>a(*:m)), were not being passed out. This bug      parentheses, for example, (?>a(*:m)), were not being passed out. This bug
28      was introduced by change 18 for 8.20.      was introduced by change 18 for 8.20.
29    
# Line 22  Version 8.21 Line 32  Version 8.21
32    
33  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
34      erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.      erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
35      This bug was probably introduced by change 9 of 8.13.      This bug was probably introduced by change 9 of 8.13.
36    
37  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
38      incorrectly rejected as "not fixed length". This arose partly because newer      incorrectly rejected as "not fixed length". This arose partly because newer
39      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)
40      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
41      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
42      length instead of just assuming "not fixed length". The items that were      length instead of just assuming "not fixed length". The items that were
43      rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),      rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
44      (*THEN), \h, \H, \v, \V, and single character negative classes with fixed      (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
45      repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.      repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
46    
47  8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was  8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
48      being incorrectly compiled and would have given unpredicatble results.      being incorrectly compiled and would have given unpredicatble results.
49    
50  9.  A possessively repeated subpattern with minimum repeat count greater than  9.  A possessively repeated subpattern with minimum repeat count greater than
51      one behaved incorrectly. For example, (A){2,}+ behaved as if it was      one behaved incorrectly. For example, (A){2,}+ behaved as if it was
52      (A)(A)++ which meant that, after a subsequent mismatch, backtracking into      (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
53      the first (A) could occur when it should not.      the first (A) could occur when it should not.
54    
55  10. Add a cast and remove a redundant test from the code.  10. Add a cast and remove a redundant test from the code.
56    
57  11. JIT should use pcre_malloc/pcre_free for allocation.  11. JIT should use pcre_malloc/pcre_free for allocation.
58    
59  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
60      best practice nowadays, and helps with cross-compiling. (If the exec_prefix      best practice nowadays, and helps with cross-compiling. (If the exec_prefix
61      is anything other than /usr, -L is still shown).      is anything other than /usr, -L is still shown).
62    
63  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.
64    
65  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
66      also gives an error.      also gives an error.
67    
68  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,
69      it caused the error "internal error: overran compiling workspace". The      it caused the error "internal error: overran compiling workspace". The
70      maximum number of forward references (including repeats) was limited by the      maximum number of forward references (including repeats) was limited by the
71      internal workspace, and dependent on the LINK_SIZE. The code has been      internal workspace, and dependent on the LINK_SIZE. The code has been
72      rewritten so that the workspace expands (via pcre_malloc) if necessary, and      rewritten so that the workspace expands (via pcre_malloc) if necessary, and
73      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)
74      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
75      the filling in of repeated forward references.      the filling in of repeated forward references.
76    
77  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
78      incorrectly expecting the subject to contain another "a" after the start.      incorrectly expecting the subject to contain another "a" after the start.
79    
80  17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier  17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
81      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
82      the SKIP was being treated as NOMATCH. For patterns such as      the SKIP was being treated as NOMATCH. For patterns such as
83      /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
84      tested.      tested.
85    
86  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
87      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
88      is a non-match for a non-anchored pattern. For example, if      is a non-match for a non-anchored pattern. For example, if
89      /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
90      "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
91      change is that for partial matches, the last encountered mark name is      change is that for partial matches, the last encountered mark name is
92      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
93      Perl-compatible have been moved into the Perl-compatible test files. The      Perl-compatible have been moved into the Perl-compatible test files. The
94      refactoring has had the pleasing side effect of removing one argument from      refactoring has had the pleasing side effect of removing one argument from
95      the match() function, thus reducing its stack requirements.      the match() function, thus reducing its stack requirements.
96    
97    19. If the /S+ option was used in pcretest to study a pattern using JIT,
98        subsequent uses of /S (without +) incorrectly behaved like /S+.
99    
100    21. Retrieve executable code size support for the JIT compiler and fixing
101        some warnings.
102    
103    22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
104        not work when the shorter character appeared right at the end of the
105        subject string.
106    
107    23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
108        systems.
109    
110    24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
111        output it when the /M option is used in pcretest.
112    
113    25. The CheckMan script was not being included in the distribution. Also, added
114        an explicit "perl" to run Perl scripts from the PrepareRelease script
115        because this is reportedly needed in Windows.
116    
117    26. If study data was being save in a file and studying had not found a set of
118        "starts with" bytes for the pattern, the data written to the file (though
119        never used) was taken from uninitialized memory and so caused valgrind to
120        complain.
121    
122    27. Updated RunTest.bat as provided by Sheri Pierce.
123    
124    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
125    
126    29. Computation of memory usage for the table of capturing group names was
127        giving an unnecessarily large value.
128    
129    
130  Version 8.20 21-Oct-2011  Version 8.20 21-Oct-2011
131  ------------------------  ------------------------

Legend:
Removed from v.773  
changed lines
  Added in v.807

  ViewVC Help
Powered by ViewVC 1.1.5