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

Diff of /code/trunk/ChangeLog

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

revision 771 by ph10, Tue Nov 29 15:34:12 2011 UTC revision 916 by ph10, Wed Feb 15 09:50:53 2012 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.21  Version 8.31
5  ------------  -----------------------------
6    
7    1.  Fixing a wrong JIT test case and some compiler warnings.
8    
9    2.  Removed a bashism from the RunTest script.
10    
11    3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied
12        to unsigned type, result still unsigned" that was given by an MS compiler
13        on encountering the code "-sizeof(xxx)".
14    
15    4.  Partial matching support is added to the JIT compiler.
16    
17    5.  Fixed several bugs concerned with partial matching of items that consist
18        of more than one character:
19    
20        (a) /^(..)\1/ did not partially match "aba" because checking references was
21            done on an "all or nothing" basis. This also applied to repeated
22            references.
23    
24        (b) \R did not give a hard partial match if \r was found at the end of the
25            subject.
26    
27        (c) \X did not give a hard partial match after matching one or more
28            characters at the end of the subject.
29    
30        (d) When newline was set to CRLF, a pattern such as /a$/ did not give a
31            partial match for the string "\r".
32    
33    
34    Version 8.30 04-February-2012
35    -----------------------------
36    
37    1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
38        name is defined in ctype.h.
39    
40    2.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
41        only in quite long subpatterns.
42    
43    3.  Removed the function pcre_info(), which has been obsolete and deprecated
44        since it was replaced by pcre_fullinfo() in February 2000.
45    
46    4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
47        match a (*MARK), and the match failed at the start of the subject, a
48        reference to memory before the start of the subject could occur. This bug
49        was introduced by fix 17 of release 8.21.
50    
51    5.  A reference to an unset group with zero minimum repetition was giving
52        totally wrong answers (in non-JavaScript-compatibility mode). For example,
53        /(another)?(\1?)test/ matched against "hello world test". This bug was
54        introduced in release 8.13.
55    
56    6.  Add support for 16-bit character strings (a large amount of work involving
57        many changes and refactorings).
58    
59    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
60        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
61        from a file.
62    
63    8.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
64        rounding is not applied in this particular case).
65    
66    9.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
67        if they appear, or are escaped, in patterns.
68    
69    10. Get rid of a number of -Wunused-but-set-variable warnings.
70    
71    11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
72        "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
73        Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
74        also returns the mark "x". This bug applied to capturing parentheses,
75        non-capturing parentheses, and atomic parentheses. It also applied to some
76        assertions.
77    
78    12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
79        information out of configure.ac instead of relying on pcre.h.generic, which
80        is not stored in the repository.
81    
82    13. Applied Dmitry V. Levin's patch for a more portable method for linking with
83        -lreadline.
84    
85    14. ZH added PCRE_CONFIG_JITTARGET; added its output to pcretest -C.
86    
87    15. Applied Graycode's patch to put the top-level frame on the stack rather
88        than the heap when not using the stack for recursion. This gives a
89        performance improvement in many cases when recursion is not deep.
90    
91    16. Experimental code added to "pcretest -C" to output the stack frame size.
92    
93    
94    Version 8.21 12-Dec-2011
95    ------------------------
96    
97  1.  Updating the JIT compiler.  1.  Updating the JIT compiler.
98    
# Line 13  Version 8.21 Line 103  Version 8.21
103      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
104      calling _pcre_jit_exec. Some extra comments are added.      calling _pcre_jit_exec. Some extra comments are added.
105    
106  4.  Mark settings inside atomic groups that do not contain any capturing  4.  (*MARK) settings inside atomic groups that do not contain any capturing
107      parentheses, for example, (?>a(*:m)), were not being passed out. This bug      parentheses, for example, (?>a(*:m)), were not being passed out. This bug
108      was introduced by change 18 for 8.20.      was introduced by change 18 for 8.20.
109    
# Line 22  Version 8.21 Line 112  Version 8.21
112    
113  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
114      erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.      erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
115      This bug was probably introduced by change 9 of 8.13.      This bug was probably introduced by change 9 of 8.13.
116    
117  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
118      incorrectly rejected as "not fixed length". This arose partly because newer      incorrectly rejected as "not fixed length". This arose partly because newer
119      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)
120      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
121      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
122      length instead of just assuming "not fixed length". The items that were      length instead of just assuming "not fixed length". The items that were
123      rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),      rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
124      (*THEN), \h, \H, \v, \V, and single character negative classes with fixed      (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
125      repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.      repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
126    
127  8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was  8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
128      being incorrectly compiled and would have given unpredicatble results.      being incorrectly compiled and would have given unpredicatble results.
129    
130  9.  A possessively repeated subpattern with minimum repeat count greater than  9.  A possessively repeated subpattern with minimum repeat count greater than
131      one behaved incorrectly. For example, (A){2,}+ behaved as if it was      one behaved incorrectly. For example, (A){2,}+ behaved as if it was
132      (A)(A)++ which meant that, after a subsequent mismatch, backtracking into      (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
133      the first (A) could occur when it should not.      the first (A) could occur when it should not.
134    
135  10. Add a cast and remove a redundant test from the code.  10. Add a cast and remove a redundant test from the code.
136    
137  11. JIT should use pcre_malloc/pcre_free for allocation.  11. JIT should use pcre_malloc/pcre_free for allocation.
138    
139  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
140      best practice nowadays, and helps with cross-compiling. (If the exec_prefix      best practice nowadays, and helps with cross-compiling. (If the exec_prefix
141      is anything other than /usr, -L is still shown).      is anything other than /usr, -L is still shown).
142    
143  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.
144    
145  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
146      also gives an error.      also gives an error.
147    
148  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,
149      it caused the error "internal error: overran compiling workspace". This      it caused the error "internal error: overran compiling workspace". The
150      is now checked, and causes "too many forward references" instead.      maximum number of forward references (including repeats) was limited by the
151        internal workspace, and dependent on the LINK_SIZE. The code has been
152        rewritten so that the workspace expands (via pcre_malloc) if necessary, and
153        the default depends on LINK_SIZE. There is a new upper limit (for safety)
154        of around 200,000 forward references. While doing this, I also speeded up
155        the filling in of repeated forward references.
156    
157  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
158      incorrectly expecting the subject to contain another "a" after the start.      incorrectly expecting the subject to contain another "a" after the start.
159    
160  17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier  17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
161      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
162      the SKIP was being treated as NOMATCH. For patterns such as      the SKIP was being treated as NOMATCH. For patterns such as
163      /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
164      tested.      tested.
165    
166  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
167      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
168      is a non-match for a non-anchored pattern. For example, if      is a non-match for a non-anchored pattern. For example, if
169      /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
170      "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
171      change is that for partial matches, the last encountered mark name is      change is that for partial matches, the last encountered mark name is
172      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
173      Perl-compatible have been moved into the Perl-compatible test files. The      Perl-compatible have been moved into the Perl-compatible test files. The
174      refactoring has had the pleasing side effect of removing one argument from      refactoring has had the pleasing side effect of removing one argument from
175      the match() function, thus reducing its stack requirements.      the match() function, thus reducing its stack requirements.
176    
177    19. If the /S+ option was used in pcretest to study a pattern using JIT,
178        subsequent uses of /S (without +) incorrectly behaved like /S+.
179    
180    21. Retrieve executable code size support for the JIT compiler and fixing
181        some warnings.
182    
183    22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
184        not work when the shorter character appeared right at the end of the
185        subject string.
186    
187    23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
188        systems.
189    
190    24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
191        output it when the /M option is used in pcretest.
192    
193    25. The CheckMan script was not being included in the distribution. Also, added
194        an explicit "perl" to run Perl scripts from the PrepareRelease script
195        because this is reportedly needed in Windows.
196    
197    26. If study data was being save in a file and studying had not found a set of
198        "starts with" bytes for the pattern, the data written to the file (though
199        never used) was taken from uninitialized memory and so caused valgrind to
200        complain.
201    
202    27. Updated RunTest.bat as provided by Sheri Pierce.
203    
204    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
205    
206    29. Computation of memory usage for the table of capturing group names was
207        giving an unnecessarily large value.
208    
209    
210  Version 8.20 21-Oct-2011  Version 8.20 21-Oct-2011
211  ------------------------  ------------------------
Legend:
Removed from v.771  
changed lines
  Added in v.916
webmaster@exim.org
 ViewVC Help
Powered by ViewVC 1.1.12