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

Diff of /code/trunk/ChangeLog

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

revision 716 by ph10, Tue Oct 4 16:38:05 2011 UTC revision 915 by zherczeg, Tue Feb 14 13:05:39 2012 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.20 23-Sep-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.  Improved \X and back reference partial matching.
18    
19    
20    Version 8.30 04-February-2012
21    -----------------------------
22    
23    1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
24        name is defined in ctype.h.
25    
26    2.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
27        only in quite long subpatterns.
28    
29    3.  Removed the function pcre_info(), which has been obsolete and deprecated
30        since it was replaced by pcre_fullinfo() in February 2000.
31    
32    4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
33        match a (*MARK), and the match failed at the start of the subject, a
34        reference to memory before the start of the subject could occur. This bug
35        was introduced by fix 17 of release 8.21.
36    
37    5.  A reference to an unset group with zero minimum repetition was giving
38        totally wrong answers (in non-JavaScript-compatibility mode). For example,
39        /(another)?(\1?)test/ matched against "hello world test". This bug was
40        introduced in release 8.13.
41    
42    6.  Add support for 16-bit character strings (a large amount of work involving
43        many changes and refactorings).
44    
45    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
46        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
47        from a file.
48    
49    8.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
50        rounding is not applied in this particular case).
51    
52    9.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
53        if they appear, or are escaped, in patterns.
54    
55    10. Get rid of a number of -Wunused-but-set-variable warnings.
56    
57    11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
58        "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
59        Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
60        also returns the mark "x". This bug applied to capturing parentheses,
61        non-capturing parentheses, and atomic parentheses. It also applied to some
62        assertions.
63    
64    12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
65        information out of configure.ac instead of relying on pcre.h.generic, which
66        is not stored in the repository.
67    
68    13. Applied Dmitry V. Levin's patch for a more portable method for linking with
69        -lreadline.
70    
71    14. ZH added PCRE_CONFIG_JITTARGET; added its output to pcretest -C.
72    
73    15. Applied Graycode's patch to put the top-level frame on the stack rather
74        than the heap when not using the stack for recursion. This gives a
75        performance improvement in many cases when recursion is not deep.
76    
77    16. Experimental code added to "pcretest -C" to output the stack frame size.
78    
79    
80    Version 8.21 12-Dec-2011
81    ------------------------
82    
83    1.  Updating the JIT compiler.
84    
85    2.  JIT compiler now supports OP_NCREF, OP_RREF and OP_NRREF. New test cases
86        are added as well.
87    
88    3.  Fix cache-flush issue on PowerPC (It is still an experimental JIT port).
89        PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before
90        calling _pcre_jit_exec. Some extra comments are added.
91    
92    4.  (*MARK) settings inside atomic groups that do not contain any capturing
93        parentheses, for example, (?>a(*:m)), were not being passed out. This bug
94        was introduced by change 18 for 8.20.
95    
96    5.  Supporting of \x, \U and \u in JavaScript compatibility mode based on the
97        ECMA-262 standard.
98    
99    6.  Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were
100        erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
101        This bug was probably introduced by change 9 of 8.13.
102    
103    7.  While fixing 6 above, I noticed that a number of other items were being
104        incorrectly rejected as "not fixed length". This arose partly because newer
105        opcodes had not been added to the fixed-length checking code. I have (a)
106        corrected the bug and added tests for these items, and (b) arranged for an
107        error to occur if an unknown opcode is encountered while checking for fixed
108        length instead of just assuming "not fixed length". The items that were
109        rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
110        (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
111        repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
112    
113    8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
114        being incorrectly compiled and would have given unpredicatble results.
115    
116    9.  A possessively repeated subpattern with minimum repeat count greater than
117        one behaved incorrectly. For example, (A){2,}+ behaved as if it was
118        (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
119        the first (A) could occur when it should not.
120    
121    10. Add a cast and remove a redundant test from the code.
122    
123    11. JIT should use pcre_malloc/pcre_free for allocation.
124    
125    12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems
126        best practice nowadays, and helps with cross-compiling. (If the exec_prefix
127        is anything other than /usr, -L is still shown).
128    
129    13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.
130    
131    14. Perl does not support \N without a following name in a [] class; PCRE now
132        also gives an error.
133    
134    15. If a forward reference was repeated with an upper limit of around 2000,
135        it caused the error "internal error: overran compiling workspace". The
136        maximum number of forward references (including repeats) was limited by the
137        internal workspace, and dependent on the LINK_SIZE. The code has been
138        rewritten so that the workspace expands (via pcre_malloc) if necessary, and
139        the default depends on LINK_SIZE. There is a new upper limit (for safety)
140        of around 200,000 forward references. While doing this, I also speeded up
141        the filling in of repeated forward references.
142    
143    16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
144        incorrectly expecting the subject to contain another "a" after the start.
145    
146    17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
147        in the match, the SKIP should be ignored. This was not happening; instead
148        the SKIP was being treated as NOMATCH. For patterns such as
149        /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
150        tested.
151    
152    18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
153        now much more compatible with Perl, in particular in cases where the result
154        is a non-match for a non-anchored pattern. For example, if
155        /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
156        "m", where previously it did not return a name. A side effect of this
157        change is that for partial matches, the last encountered mark name is
158        returned, as for non matches. A number of tests that were previously not
159        Perl-compatible have been moved into the Perl-compatible test files. The
160        refactoring has had the pleasing side effect of removing one argument from
161        the match() function, thus reducing its stack requirements.
162    
163    19. If the /S+ option was used in pcretest to study a pattern using JIT,
164        subsequent uses of /S (without +) incorrectly behaved like /S+.
165    
166    21. Retrieve executable code size support for the JIT compiler and fixing
167        some warnings.
168    
169    22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
170        not work when the shorter character appeared right at the end of the
171        subject string.
172    
173    23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
174        systems.
175    
176    24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
177        output it when the /M option is used in pcretest.
178    
179    25. The CheckMan script was not being included in the distribution. Also, added
180        an explicit "perl" to run Perl scripts from the PrepareRelease script
181        because this is reportedly needed in Windows.
182    
183    26. If study data was being save in a file and studying had not found a set of
184        "starts with" bytes for the pattern, the data written to the file (though
185        never used) was taken from uninitialized memory and so caused valgrind to
186        complain.
187    
188    27. Updated RunTest.bat as provided by Sheri Pierce.
189    
190    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
191    
192    29. Computation of memory usage for the table of capturing group names was
193        giving an unnecessarily large value.
194    
195    
196    Version 8.20 21-Oct-2011
197  ------------------------  ------------------------
198    
199  1.  Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had  1.  Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had
# Line 54  Version 8.20 23-Sep-2011 Line 246  Version 8.20 23-Sep-2011
246  8.  If (*THEN) was present in the first (true) branch of a conditional group,  8.  If (*THEN) was present in the first (true) branch of a conditional group,
247      it was not handled as intended. [But see 16 below.]      it was not handled as intended. [But see 16 below.]
248    
249  9.  Replaced RunTest.bat with the much improved version provided by Sheri  9.  Replaced RunTest.bat and CMakeLists.txt with improved versions provided by
250      Pierce.      Sheri Pierce.
251    
252  10. A pathological pattern such as /(*ACCEPT)a/ was miscompiled, thinking that  10. A pathological pattern such as /(*ACCEPT)a/ was miscompiled, thinking that
253      the first byte in a match must be "a".      the first byte in a match must be "a".
# Line 65  Version 8.20 23-Sep-2011 Line 257  Version 8.20 23-Sep-2011
257      pattern contains any instances of (*THEN). If it does not, the old      pattern contains any instances of (*THEN). If it does not, the old
258      optimizations are restored. It would be nice to do this on a per-group      optimizations are restored. It would be nice to do this on a per-group
259      basis, but at the moment that is not feasible.      basis, but at the moment that is not feasible.
260    
261  12. In some environments, the output of pcretest -C is CRLF terminated. This  12. In some environments, the output of pcretest -C is CRLF terminated. This
262      broke RunTest's code that checks for the link size. A single white space      broke RunTest's code that checks for the link size. A single white space
263      after the value is now allowed for.      character after the value is now allowed for.
264    
265  13. RunTest now checks for the "fr" locale as well as for "fr_FR" and "french".  13. RunTest now checks for the "fr" locale as well as for "fr_FR" and "french".
266      For "fr", it uses the Windows-specific input and output files.      For "fr", it uses the Windows-specific input and output files.
267    
268  14. If (*THEN) appeared in a group that was called recursively or as a  14. If (*THEN) appeared in a group that was called recursively or as a
269      subroutine, it did not work as intended. [But see next item.]      subroutine, it did not work as intended. [But see next item.]
270    
271  15. Consider the pattern /A (B(*THEN)C) | D/ where A, B, C, and D are complex  15. Consider the pattern /A (B(*THEN)C) | D/ where A, B, C, and D are complex
272      pattern fragments (but not containing any | characters). If A and B are      pattern fragments (but not containing any | characters). If A and B are
273      matched, but there is a failure in C so that it backtracks to (*THEN), PCRE      matched, but there is a failure in C so that it backtracks to (*THEN), PCRE
274      was behaving differently to Perl. PCRE backtracked into A, but Perl goes to      was behaving differently to Perl. PCRE backtracked into A, but Perl goes to
275      D. In other words, Perl considers parentheses that do not contain any |      D. In other words, Perl considers parentheses that do not contain any |
276      characters to be part of a surrounding alternative, whereas PCRE was      characters to be part of a surrounding alternative, whereas PCRE was
277      treading (B(*THEN)C) the same as (B(*THEN)C|(*FAIL)) -- which Perl handles      treading (B(*THEN)C) the same as (B(*THEN)C|(*FAIL)) -- which Perl handles
278      differently. PCRE now behaves in the same way as Perl, except in the case      differently. PCRE now behaves in the same way as Perl, except in the case
279      of subroutine/recursion calls such as (?1) which have in any case always      of subroutine/recursion calls such as (?1) which have in any case always
280      been different (but PCRE had them first :-).      been different (but PCRE had them first :-).
281    
282  16. Related to 15 above: Perl does not treat the | in a conditional group as  16. Related to 15 above: Perl does not treat the | in a conditional group as
283      creating alternatives. Such a group is treated in the same way as an      creating alternatives. Such a group is treated in the same way as an
284      ordinary group without any | characters when processing (*THEN). PCRE has      ordinary group without any | characters when processing (*THEN). PCRE has
285      been changed to match Perl's behaviour.      been changed to match Perl's behaviour.
286    
287    17. If a user had set PCREGREP_COLO(U)R to something other than 1:31, the
288        RunGrepTest script failed.
289    
290    18. Change 22 for version 13 caused atomic groups to use more stack. This is
291        inevitable for groups that contain captures, but it can lead to a lot of
292        stack use in large patterns. The old behaviour has been restored for atomic
293        groups that do not contain any capturing parentheses.
294    
295    19. If the PCRE_NO_START_OPTIMIZE option was set for pcre_compile(), it did not
296        suppress the check for a minimum subject length at run time. (If it was
297        given to pcre_exec() or pcre_dfa_exec() it did work.)
298    
299    20. Fixed an ASCII-dependent infelicity in pcretest that would have made it
300        fail to work when decoding hex characters in data strings in EBCDIC
301        environments.
302    
303    21. It appears that in at least one Mac OS environment, the isxdigit() function
304        is implemented as a macro that evaluates to its argument more than once,
305        contravening the C 90 Standard (I haven't checked a later standard). There
306        was an instance in pcretest which caused it to go wrong when processing
307        \x{...} escapes in subject strings. The has been rewritten to avoid using
308        things like p++ in the argument of isxdigit().
309    
310    
311  Version 8.13 16-Aug-2011  Version 8.13 16-Aug-2011
312  ------------------------  ------------------------

Legend:
Removed from v.716  
changed lines
  Added in v.915

  ViewVC Help
Powered by ViewVC 1.1.5