/[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 949 by zherczeg, Thu Mar 8 10:28:49 2012 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.21 05-Dec-2011  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 recognize
31            a partial match for the string "\r".
32    
33        (e) When newline was set to CRLF, the metacharacter "." did not recognize
34            a partial match for a CR character at the end of the subject string.
35    
36    6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when
37        running pcretest, the text "(JIT)" added to the output whenever JIT is
38        actually used to run the match.
39    
40    7.  Individual JIT compile options can be set in pcretest by following -s+[+]
41        or /S+[+] with a digit between 1 and 7.
42    
43    8.  OP_NOT now supports any UTF character not just single-byte ones.
44    
45    9.  (*MARK) control verb is now supported by the JIT compiler.
46    
47    10. The command "./RunTest list" lists the available tests without actually
48        running any of them. (Because I keep forgetting what they all are.)
49    
50    11. Add PCRE_INFO_MAXLOOKBEHIND.
51    
52    12. Applied a (slightly modified) user-supplied patch that improves performance
53        when the heap is used for recursion (compiled with --disable-stack-for-
54        recursion). Instead of malloc and free for each heap frame each time a
55        logical recursion happens, frames are retained on a chain and re-used where
56        possible. This sometimes gives as much as 30% improvement.
57    
58    13. As documented, (*COMMIT) is now confined to within a recursive subpattern
59        call.
60    
61    14. As documented, (*COMMIT) is now confined to within a positive assertion.
62    
63    15. It is now possible to link pcretest with libedit as an alternative to
64        libreadline.
65    
66    16. (*COMMIT) control verb is now supported by the JIT compiler.
67    
68    17. The Unicode data tables have been updated to Unicode 6.1.0.
69    
70    18. Added --file-list option to pcregrep.
71    
72    19. Added binary file support to pcregrep, including the -a, --binary-files,
73        -I, and --text options.
74    
75    20. The madvise function is renamed for posix_madvise for QNX compatibility
76        reasons. Fixed by Giuseppe D'Angelo.
77    
78    
79    Version 8.30 04-February-2012
80    -----------------------------
81    
82    1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
83        name is defined in ctype.h.
84    
85    2.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
86        only in quite long subpatterns.
87    
88    3.  Removed the function pcre_info(), which has been obsolete and deprecated
89        since it was replaced by pcre_fullinfo() in February 2000.
90    
91    4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
92        match a (*MARK), and the match failed at the start of the subject, a
93        reference to memory before the start of the subject could occur. This bug
94        was introduced by fix 17 of release 8.21.
95    
96    5.  A reference to an unset group with zero minimum repetition was giving
97        totally wrong answers (in non-JavaScript-compatibility mode). For example,
98        /(another)?(\1?)test/ matched against "hello world test". This bug was
99        introduced in release 8.13.
100    
101    6.  Add support for 16-bit character strings (a large amount of work involving
102        many changes and refactorings).
103    
104    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
105        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
106        from a file.
107    
108    8.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
109        rounding is not applied in this particular case).
110    
111    9.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
112        if they appear, or are escaped, in patterns.
113    
114    10. Get rid of a number of -Wunused-but-set-variable warnings.
115    
116    11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
117        "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
118        Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
119        also returns the mark "x". This bug applied to capturing parentheses,
120        non-capturing parentheses, and atomic parentheses. It also applied to some
121        assertions.
122    
123    12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
124        information out of configure.ac instead of relying on pcre.h.generic, which
125        is not stored in the repository.
126    
127    13. Applied Dmitry V. Levin's patch for a more portable method for linking with
128        -lreadline.
129    
130    14. ZH added PCRE_CONFIG_JITTARGET; added its output to pcretest -C.
131    
132    15. Applied Graycode's patch to put the top-level frame on the stack rather
133        than the heap when not using the stack for recursion. This gives a
134        performance improvement in many cases when recursion is not deep.
135    
136    16. Experimental code added to "pcretest -C" to output the stack frame size.
137    
138    
139    Version 8.21 12-Dec-2011
140  ------------------------  ------------------------
141    
142  1.  Updating the JIT compiler.  1.  Updating the JIT compiler.
# Line 22  Version 8.21 05-Dec-2011 Line 157  Version 8.21 05-Dec-2011
157    
158  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
159      erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.      erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
160      This bug was probably introduced by change 9 of 8.13.      This bug was probably introduced by change 9 of 8.13.
161    
162  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
163      incorrectly rejected as "not fixed length". This arose partly because newer      incorrectly rejected as "not fixed length". This arose partly because newer
164      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)
165      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
166      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
167      length instead of just assuming "not fixed length". The items that were      length instead of just assuming "not fixed length". The items that were
168      rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),      rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
169      (*THEN), \h, \H, \v, \V, and single character negative classes with fixed      (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
170      repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.      repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
171    
172  8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was  8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
173      being incorrectly compiled and would have given unpredicatble results.      being incorrectly compiled and would have given unpredicatble results.
174    
175  9.  A possessively repeated subpattern with minimum repeat count greater than  9.  A possessively repeated subpattern with minimum repeat count greater than
176      one behaved incorrectly. For example, (A){2,}+ behaved as if it was      one behaved incorrectly. For example, (A){2,}+ behaved as if it was
177      (A)(A)++ which meant that, after a subsequent mismatch, backtracking into      (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
178      the first (A) could occur when it should not.      the first (A) could occur when it should not.
179    
180  10. Add a cast and remove a redundant test from the code.  10. Add a cast and remove a redundant test from the code.
181    
182  11. JIT should use pcre_malloc/pcre_free for allocation.  11. JIT should use pcre_malloc/pcre_free for allocation.
183    
184  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
185      best practice nowadays, and helps with cross-compiling. (If the exec_prefix      best practice nowadays, and helps with cross-compiling. (If the exec_prefix
186      is anything other than /usr, -L is still shown).      is anything other than /usr, -L is still shown).
187    
188  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.
189    
190  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
191      also gives an error.      also gives an error.
192    
193  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,
194      it caused the error "internal error: overran compiling workspace". The      it caused the error "internal error: overran compiling workspace". The
195      maximum number of forward references (including repeats) was limited by the      maximum number of forward references (including repeats) was limited by the
196      internal workspace, and dependent on the LINK_SIZE. The code has been      internal workspace, and dependent on the LINK_SIZE. The code has been
197      rewritten so that the workspace expands (via pcre_malloc) if necessary, and      rewritten so that the workspace expands (via pcre_malloc) if necessary, and
198      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)
199      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
200      the filling in of repeated forward references.      the filling in of repeated forward references.
201    
202  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
203      incorrectly expecting the subject to contain another "a" after the start.      incorrectly expecting the subject to contain another "a" after the start.
204    
205  17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier  17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
206      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
207      the SKIP was being treated as NOMATCH. For patterns such as      the SKIP was being treated as NOMATCH. For patterns such as
208      /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
209      tested.      tested.
210    
211  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
212      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
213      is a non-match for a non-anchored pattern. For example, if      is a non-match for a non-anchored pattern. For example, if
214      /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
215      "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
216      change is that for partial matches, the last encountered mark name is      change is that for partial matches, the last encountered mark name is
217      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
218      Perl-compatible have been moved into the Perl-compatible test files. The      Perl-compatible have been moved into the Perl-compatible test files. The
219      refactoring has had the pleasing side effect of removing one argument from      refactoring has had the pleasing side effect of removing one argument from
220      the match() function, thus reducing its stack requirements.      the match() function, thus reducing its stack requirements.
221    
222  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,
223      subsequent uses of /S (without +) incorrectly behaved like /S+.      subsequent uses of /S (without +) incorrectly behaved like /S+.
224    
225  21. Retrieve executable code size support for the JIT compiler and fixing  21. Retrieve executable code size support for the JIT compiler and fixing
226      some warnings.      some warnings.
227    
228  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
229      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
230      subject string.      subject string.
231    
232  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
233      systems.      systems.
234    
235  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
236      output it when the /M option is used in pcretest.      output it when the /M option is used in pcretest.
237    
238  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
239      an explicit "perl" to run Perl scripts from the PrepareRelease script      an explicit "perl" to run Perl scripts from the PrepareRelease script
240      because this is reportedly needed in Windows.      because this is reportedly needed in Windows.
241    
242    26. If study data was being save in a file and studying had not found a set of
243        "starts with" bytes for the pattern, the data written to the file (though
244        never used) was taken from uninitialized memory and so caused valgrind to
245        complain.
246    
247    27. Updated RunTest.bat as provided by Sheri Pierce.
248    
249    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
250    
251    29. Computation of memory usage for the table of capturing group names was
252        giving an unnecessarily large value.
253    
254    
255  Version 8.20 21-Oct-2011  Version 8.20 21-Oct-2011
Legend:
Removed from v.784  
changed lines
  Added in v.949
webmaster@exim.org
 ViewVC Help
Powered by ViewVC 1.1.12