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

Diff of /code/trunk/ChangeLog

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

revision 758 by ph10, Mon Nov 21 12:05:36 2011 UTC revision 882 by ph10, Sun Jan 15 18:45:27 2012 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.21  Version 8.30
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 fixed-length calculation for lookbehinds that would show up
11        only in quite long subpatterns.
12    
13    3.  Removed the function pcre_info(), which has been obsolete and deprecated
14        since it was replaced by pcre_fullinfo() in February 2000.
15    
16    4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
17        match a (*MARK), and the match failed at the start of the subject, a
18        reference to memory before the start of the subject could occur. This bug
19        was introduced by fix 17 of release 8.21.
20    
21    5.  A reference to an unset group with zero minimum repetition was giving
22        totally wrong answers (in non-JavaScript-compatibility mode). For example,
23        /(another)?(\1?)test/ matched against "hello world test". This bug was
24        introduced in release 8.13.
25    
26    6.  Add support for 16-bit character strings (a large amount of work involving
27        many changes and refactorings).
28    
29    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
30        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
31        from a file.
32    
33    8.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
34        rounding is not applied in this particular case).
35    
36    9.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
37        if they appear, or are escaped, in patterns.
38    
39    10. Get rid of a number of -Wunused-but-set-variable warnings.
40    
41    11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
42        "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
43        Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
44        also returns the mark "x". This bug applied to capturing parentheses,
45        non-capturing parentheses, and atomic parentheses.
46    
47    
48    Version 8.21 12-Dec-2011
49    ------------------------
50    
51  1.  Updating the JIT compiler.  1.  Updating the JIT compiler.
52    
53  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 57  Version 8.21
57      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
58      calling _pcre_jit_exec. Some extra comments are added.      calling _pcre_jit_exec. Some extra comments are added.
59    
60  4.  Mark settings inside atomic groups that do not contain any capturing  4.  (*MARK) settings inside atomic groups that do not contain any capturing
61      parentheses, for example, (?>a(*:m)), were not being passed out. This bug      parentheses, for example, (?>a(*:m)), were not being passed out. This bug
62      was introduced by change 18 for 8.20.      was introduced by change 18 for 8.20.
63    
# Line 22  Version 8.21 Line 66  Version 8.21
66    
67  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
68      erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.      erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
69      This bug was probably introduced by change 9 of 8.13.      This bug was probably introduced by change 9 of 8.13.
70    
71  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
72      incorrectly rejected as "not fixed length". This arose partly because newer      incorrectly rejected as "not fixed length". This arose partly because newer
73      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)
74      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
75      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
76      length instead of just assuming "not fixed length". The items that were      length instead of just assuming "not fixed length". The items that were
77      rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),      rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
78      (*THEN), \h, \H, \v, \V, and single character negative classes with fixed      (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
79      repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.      repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
80    
81  8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was  8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
82      being incorrectly compiled and would have given unpredicatble results.      being incorrectly compiled and would have given unpredicatble results.
83    
84  9.  A possessively repeated subpattern with minimum repeat count greater than  9.  A possessively repeated subpattern with minimum repeat count greater than
85      one behaved incorrectly. For example, (A){2,}+ behaved as if it was      one behaved incorrectly. For example, (A){2,}+ behaved as if it was
86      (A)(A)++ which meant that, after a subsequent mismatch, backtracking into      (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
87      the first (A) could occur when it should not.      the first (A) could occur when it should not.
88    
89  10. Add a cast and remove a redundant test from the code.  10. Add a cast and remove a redundant test from the code.
90    
91  11. JIT should use pcre_malloc/pcre_free for allocation.  11. JIT should use pcre_malloc/pcre_free for allocation.
92    
93  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
94      best practice nowadays, and helps with cross-compiling. (If the exec_prefix      best practice nowadays, and helps with cross-compiling. (If the exec_prefix
95      is anything other than /usr, -L is still shown).      is anything other than /usr, -L is still shown).
96    
97  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.
98    
99  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
100      also gives an error.      also gives an error.
101    
102    15. If a forward reference was repeated with an upper limit of around 2000,
103        it caused the error "internal error: overran compiling workspace". The
104        maximum number of forward references (including repeats) was limited by the
105        internal workspace, and dependent on the LINK_SIZE. The code has been
106        rewritten so that the workspace expands (via pcre_malloc) if necessary, and
107        the default depends on LINK_SIZE. There is a new upper limit (for safety)
108        of around 200,000 forward references. While doing this, I also speeded up
109        the filling in of repeated forward references.
110    
111    16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
112        incorrectly expecting the subject to contain another "a" after the start.
113    
114    17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
115        in the match, the SKIP should be ignored. This was not happening; instead
116        the SKIP was being treated as NOMATCH. For patterns such as
117        /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
118        tested.
119    
120    18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
121        now much more compatible with Perl, in particular in cases where the result
122        is a non-match for a non-anchored pattern. For example, if
123        /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
124        "m", where previously it did not return a name. A side effect of this
125        change is that for partial matches, the last encountered mark name is
126        returned, as for non matches. A number of tests that were previously not
127        Perl-compatible have been moved into the Perl-compatible test files. The
128        refactoring has had the pleasing side effect of removing one argument from
129        the match() function, thus reducing its stack requirements.
130    
131    19. If the /S+ option was used in pcretest to study a pattern using JIT,
132        subsequent uses of /S (without +) incorrectly behaved like /S+.
133    
134    21. Retrieve executable code size support for the JIT compiler and fixing
135        some warnings.
136    
137    22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
138        not work when the shorter character appeared right at the end of the
139        subject string.
140    
141    23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
142        systems.
143    
144    24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
145        output it when the /M option is used in pcretest.
146    
147    25. The CheckMan script was not being included in the distribution. Also, added
148        an explicit "perl" to run Perl scripts from the PrepareRelease script
149        because this is reportedly needed in Windows.
150    
151    26. If study data was being save in a file and studying had not found a set of
152        "starts with" bytes for the pattern, the data written to the file (though
153        never used) was taken from uninitialized memory and so caused valgrind to
154        complain.
155    
156    27. Updated RunTest.bat as provided by Sheri Pierce.
157    
158    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
159    
160    29. Computation of memory usage for the table of capturing group names was
161        giving an unnecessarily large value.
162    
163    
164  Version 8.20 21-Oct-2011  Version 8.20 21-Oct-2011
165  ------------------------  ------------------------
Legend:
Removed from v.758  
changed lines
  Added in v.882
webmaster@exim.org
 ViewVC Help
Powered by ViewVC 1.1.12