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

Diff of /code/trunk/ChangeLog

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

revision 657 by ph10, Mon Aug 15 17:39:09 2011 UTC revision 892 by ph10, Wed Jan 18 17:23:20 2012 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.13 02-Aug-2011  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. It also applied to some
46        assertions.
47    
48    12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
49        information out of configure.ac instead of relying on pcre.h.generic, which
50        is not stored in the repository.
51    
52    13. Applied Dmitry V. Levin's patch for a more portable method for linking with
53        -lreadline.
54    
55    14. ZH added PCRE_CONFIG_JITTARGET; added its output to pcretest -C.
56    
57    15. Applied Graycode's patch to put the top-level frame on the stack rather
58        than the heap when not using the stack for recursion. This gives a
59        performance improvement in many cases when recursion is not deep.
60    
61    
62    Version 8.21 12-Dec-2011
63    ------------------------
64    
65    1.  Updating the JIT compiler.
66    
67    2.  JIT compiler now supports OP_NCREF, OP_RREF and OP_NRREF. New test cases
68        are added as well.
69    
70    3.  Fix cache-flush issue on PowerPC (It is still an experimental JIT port).
71        PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before
72        calling _pcre_jit_exec. Some extra comments are added.
73    
74    4.  (*MARK) settings inside atomic groups that do not contain any capturing
75        parentheses, for example, (?>a(*:m)), were not being passed out. This bug
76        was introduced by change 18 for 8.20.
77    
78    5.  Supporting of \x, \U and \u in JavaScript compatibility mode based on the
79        ECMA-262 standard.
80    
81    6.  Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were
82        erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
83        This bug was probably introduced by change 9 of 8.13.
84    
85    7.  While fixing 6 above, I noticed that a number of other items were being
86        incorrectly rejected as "not fixed length". This arose partly because newer
87        opcodes had not been added to the fixed-length checking code. I have (a)
88        corrected the bug and added tests for these items, and (b) arranged for an
89        error to occur if an unknown opcode is encountered while checking for fixed
90        length instead of just assuming "not fixed length". The items that were
91        rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
92        (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
93        repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
94    
95    8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
96        being incorrectly compiled and would have given unpredicatble results.
97    
98    9.  A possessively repeated subpattern with minimum repeat count greater than
99        one behaved incorrectly. For example, (A){2,}+ behaved as if it was
100        (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
101        the first (A) could occur when it should not.
102    
103    10. Add a cast and remove a redundant test from the code.
104    
105    11. JIT should use pcre_malloc/pcre_free for allocation.
106    
107    12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems
108        best practice nowadays, and helps with cross-compiling. (If the exec_prefix
109        is anything other than /usr, -L is still shown).
110    
111    13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.
112    
113    14. Perl does not support \N without a following name in a [] class; PCRE now
114        also gives an error.
115    
116    15. If a forward reference was repeated with an upper limit of around 2000,
117        it caused the error "internal error: overran compiling workspace". The
118        maximum number of forward references (including repeats) was limited by the
119        internal workspace, and dependent on the LINK_SIZE. The code has been
120        rewritten so that the workspace expands (via pcre_malloc) if necessary, and
121        the default depends on LINK_SIZE. There is a new upper limit (for safety)
122        of around 200,000 forward references. While doing this, I also speeded up
123        the filling in of repeated forward references.
124    
125    16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
126        incorrectly expecting the subject to contain another "a" after the start.
127    
128    17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
129        in the match, the SKIP should be ignored. This was not happening; instead
130        the SKIP was being treated as NOMATCH. For patterns such as
131        /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
132        tested.
133    
134    18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
135        now much more compatible with Perl, in particular in cases where the result
136        is a non-match for a non-anchored pattern. For example, if
137        /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
138        "m", where previously it did not return a name. A side effect of this
139        change is that for partial matches, the last encountered mark name is
140        returned, as for non matches. A number of tests that were previously not
141        Perl-compatible have been moved into the Perl-compatible test files. The
142        refactoring has had the pleasing side effect of removing one argument from
143        the match() function, thus reducing its stack requirements.
144    
145    19. If the /S+ option was used in pcretest to study a pattern using JIT,
146        subsequent uses of /S (without +) incorrectly behaved like /S+.
147    
148    21. Retrieve executable code size support for the JIT compiler and fixing
149        some warnings.
150    
151    22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
152        not work when the shorter character appeared right at the end of the
153        subject string.
154    
155    23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
156        systems.
157    
158    24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
159        output it when the /M option is used in pcretest.
160    
161    25. The CheckMan script was not being included in the distribution. Also, added
162        an explicit "perl" to run Perl scripts from the PrepareRelease script
163        because this is reportedly needed in Windows.
164    
165    26. If study data was being save in a file and studying had not found a set of
166        "starts with" bytes for the pattern, the data written to the file (though
167        never used) was taken from uninitialized memory and so caused valgrind to
168        complain.
169    
170    27. Updated RunTest.bat as provided by Sheri Pierce.
171    
172    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
173    
174    29. Computation of memory usage for the table of capturing group names was
175        giving an unnecessarily large value.
176    
177    
178    Version 8.20 21-Oct-2011
179    ------------------------
180    
181    1.  Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had
182        a POSIX class. After further experiments with Perl, which convinced me that
183        Perl has bugs and confusions, a closing square bracket is no longer allowed
184        in a POSIX name. This bug also affected patterns with classes that started
185        with full stops.
186    
187    2.  If a pattern such as /(a)b|ac/ is matched against "ac", there is no
188        captured substring, but while checking the failing first alternative,
189        substring 1 is temporarily captured. If the output vector supplied to
190        pcre_exec() was not big enough for this capture, the yield of the function
191        was still zero ("insufficient space for captured substrings"). This cannot
192        be totally fixed without adding another stack variable, which seems a lot
193        of expense for a edge case. However, I have improved the situation in cases
194        such as /(a)(b)x|abc/ matched against "abc", where the return code
195        indicates that fewer than the maximum number of slots in the ovector have
196        been set.
197    
198    3.  Related to (2) above: when there are more back references in a pattern than
199        slots in the output vector, pcre_exec() uses temporary memory during
200        matching, and copies in the captures as far as possible afterwards. It was
201        using the entire output vector, but this conflicts with the specification
202        that only 2/3 is used for passing back captured substrings. Now it uses
203        only the first 2/3, for compatibility. This is, of course, another edge
204        case.
205    
206    4.  Zoltan Herczeg's just-in-time compiler support has been integrated into the
207        main code base, and can be used by building with --enable-jit. When this is
208        done, pcregrep automatically uses it unless --disable-pcregrep-jit or the
209        runtime --no-jit option is given.
210    
211    5.  When the number of matches in a pcre_dfa_exec() run exactly filled the
212        ovector, the return from the function was zero, implying that there were
213        other matches that did not fit. The correct "exactly full" value is now
214        returned.
215    
216    6.  If a subpattern that was called recursively or as a subroutine contained
217        (*PRUNE) or any other control that caused it to give a non-standard return,
218        invalid errors such as "Error -26 (nested recursion at the same subject
219        position)" or even infinite loops could occur.
220    
221    7.  If a pattern such as /a(*SKIP)c|b(*ACCEPT)|/ was studied, it stopped
222        computing the minimum length on reaching *ACCEPT, and so ended up with the
223        wrong value of 1 rather than 0. Further investigation indicates that
224        computing a minimum subject length in the presence of *ACCEPT is difficult
225        (think back references, subroutine calls), and so I have changed the code
226        so that no minimum is registered for a pattern that contains *ACCEPT.
227    
228    8.  If (*THEN) was present in the first (true) branch of a conditional group,
229        it was not handled as intended. [But see 16 below.]
230    
231    9.  Replaced RunTest.bat and CMakeLists.txt with improved versions provided by
232        Sheri Pierce.
233    
234    10. A pathological pattern such as /(*ACCEPT)a/ was miscompiled, thinking that
235        the first byte in a match must be "a".
236    
237    11. Change 17 for 8.13 increased the recursion depth for patterns like
238        /a(?:.)*?a/ drastically. I've improved things by remembering whether a
239        pattern contains any instances of (*THEN). If it does not, the old
240        optimizations are restored. It would be nice to do this on a per-group
241        basis, but at the moment that is not feasible.
242    
243    12. In some environments, the output of pcretest -C is CRLF terminated. This
244        broke RunTest's code that checks for the link size. A single white space
245        character after the value is now allowed for.
246    
247    13. RunTest now checks for the "fr" locale as well as for "fr_FR" and "french".
248        For "fr", it uses the Windows-specific input and output files.
249    
250    14. If (*THEN) appeared in a group that was called recursively or as a
251        subroutine, it did not work as intended. [But see next item.]
252    
253    15. Consider the pattern /A (B(*THEN)C) | D/ where A, B, C, and D are complex
254        pattern fragments (but not containing any | characters). If A and B are
255        matched, but there is a failure in C so that it backtracks to (*THEN), PCRE
256        was behaving differently to Perl. PCRE backtracked into A, but Perl goes to
257        D. In other words, Perl considers parentheses that do not contain any |
258        characters to be part of a surrounding alternative, whereas PCRE was
259        treading (B(*THEN)C) the same as (B(*THEN)C|(*FAIL)) -- which Perl handles
260        differently. PCRE now behaves in the same way as Perl, except in the case
261        of subroutine/recursion calls such as (?1) which have in any case always
262        been different (but PCRE had them first :-).
263    
264    16. Related to 15 above: Perl does not treat the | in a conditional group as
265        creating alternatives. Such a group is treated in the same way as an
266        ordinary group without any | characters when processing (*THEN). PCRE has
267        been changed to match Perl's behaviour.
268    
269    17. If a user had set PCREGREP_COLO(U)R to something other than 1:31, the
270        RunGrepTest script failed.
271    
272    18. Change 22 for version 13 caused atomic groups to use more stack. This is
273        inevitable for groups that contain captures, but it can lead to a lot of
274        stack use in large patterns. The old behaviour has been restored for atomic
275        groups that do not contain any capturing parentheses.
276    
277    19. If the PCRE_NO_START_OPTIMIZE option was set for pcre_compile(), it did not
278        suppress the check for a minimum subject length at run time. (If it was
279        given to pcre_exec() or pcre_dfa_exec() it did work.)
280    
281    20. Fixed an ASCII-dependent infelicity in pcretest that would have made it
282        fail to work when decoding hex characters in data strings in EBCDIC
283        environments.
284    
285    21. It appears that in at least one Mac OS environment, the isxdigit() function
286        is implemented as a macro that evaluates to its argument more than once,
287        contravening the C 90 Standard (I haven't checked a later standard). There
288        was an instance in pcretest which caused it to go wrong when processing
289        \x{...} escapes in subject strings. The has been rewritten to avoid using
290        things like p++ in the argument of isxdigit().
291    
292    
293    Version 8.13 16-Aug-2011
294  ------------------------  ------------------------
295    
296  1.  The Unicode data tables have been updated to Unicode 6.0.0.  1.  The Unicode data tables have been updated to Unicode 6.0.0.
# Line 98  Version 8.13 02-Aug-2011 Line 387  Version 8.13 02-Aug-2011
387      tail recursion to cut down on stack usage. Unfortunately, now that there is      tail recursion to cut down on stack usage. Unfortunately, now that there is
388      the possibility of (*THEN) occurring in these branches, tail recursion is      the possibility of (*THEN) occurring in these branches, tail recursion is
389      no longer possible because the return has to be checked for (*THEN). These      no longer possible because the return has to be checked for (*THEN). These
390      two optimizations have therefore been removed.      two optimizations have therefore been removed. [But see 8.20/11 above.]
391    
392  18. If a pattern containing \R was studied, it was assumed that \R always  18. If a pattern containing \R was studied, it was assumed that \R always
393      matched two bytes, thus causing the minimum subject length to be      matched two bytes, thus causing the minimum subject length to be
# Line 189  Version 8.13 02-Aug-2011 Line 478  Version 8.13 02-Aug-2011
478      For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,      For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,
479      unescaped square brackets may also appear as part of class names. For      unescaped square brackets may also appear as part of class names. For
480      example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves      example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves
481      more like Perl.      more like Perl. (But see 8.20/1 above.)
482    
483  38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this  38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this
484      was because it thought it was \N{name}, which is not supported).      was because it thought it was \N{name}, which is not supported).
# Line 224  Version 8.13 02-Aug-2011 Line 513  Version 8.13 02-Aug-2011
513      (a) The default value of the buffer size parameter has been increased from      (a) The default value of the buffer size parameter has been increased from
514          8K to 20K. (The actual buffer used is three times this size.)          8K to 20K. (The actual buffer used is three times this size.)
515    
516      (b) The default can be changed by ./configure --with-pcregrep-bufsiz when      (b) The default can be changed by ./configure --with-pcregrep-bufsize when
517          PCRE is built.          PCRE is built.
518    
519      (c) A --buffer-size=n option has been added to pcregrep, to allow the size      (c) A --buffer-size=n option has been added to pcregrep, to allow the size
# Line 245  Version 8.13 02-Aug-2011 Line 534  Version 8.13 02-Aug-2011
534  47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a  47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a
535      complete match instead of a partial match. This bug was dependent on both      complete match instead of a partial match. This bug was dependent on both
536      the PCRE_UTF8 and PCRE_DOTALL options being set.      the PCRE_UTF8 and PCRE_DOTALL options being set.
537    
538  48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the  48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the
539      starting byte set, because \b was not being ignored.      starting byte set, because \b was not being ignored.
540    
541    
542  Version 8.12 15-Jan-2011  Version 8.12 15-Jan-2011

Legend:
Removed from v.657  
changed lines
  Added in v.892

  ViewVC Help
Powered by ViewVC 1.1.5