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

Diff of /code/trunk/ChangeLog

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

revision 491 by ph10, Mon Mar 1 17:45:08 2010 UTC revision 893 by ph10, Thu Jan 19 17:15:11 2012 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.02 01-Mar-2010  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    16. Experimental code added to "pcretest -C" to output the stack frame size.
62    
63    
64    Version 8.21 12-Dec-2011
65    ------------------------
66    
67    1.  Updating the JIT compiler.
68    
69    2.  JIT compiler now supports OP_NCREF, OP_RREF and OP_NRREF. New test cases
70        are added as well.
71    
72    3.  Fix cache-flush issue on PowerPC (It is still an experimental JIT port).
73        PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before
74        calling _pcre_jit_exec. Some extra comments are added.
75    
76    4.  (*MARK) settings inside atomic groups that do not contain any capturing
77        parentheses, for example, (?>a(*:m)), were not being passed out. This bug
78        was introduced by change 18 for 8.20.
79    
80    5.  Supporting of \x, \U and \u in JavaScript compatibility mode based on the
81        ECMA-262 standard.
82    
83    6.  Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were
84        erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
85        This bug was probably introduced by change 9 of 8.13.
86    
87    7.  While fixing 6 above, I noticed that a number of other items were being
88        incorrectly rejected as "not fixed length". This arose partly because newer
89        opcodes had not been added to the fixed-length checking code. I have (a)
90        corrected the bug and added tests for these items, and (b) arranged for an
91        error to occur if an unknown opcode is encountered while checking for fixed
92        length instead of just assuming "not fixed length". The items that were
93        rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
94        (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
95        repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
96    
97    8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
98        being incorrectly compiled and would have given unpredicatble results.
99    
100    9.  A possessively repeated subpattern with minimum repeat count greater than
101        one behaved incorrectly. For example, (A){2,}+ behaved as if it was
102        (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
103        the first (A) could occur when it should not.
104    
105    10. Add a cast and remove a redundant test from the code.
106    
107    11. JIT should use pcre_malloc/pcre_free for allocation.
108    
109    12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems
110        best practice nowadays, and helps with cross-compiling. (If the exec_prefix
111        is anything other than /usr, -L is still shown).
112    
113    13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.
114    
115    14. Perl does not support \N without a following name in a [] class; PCRE now
116        also gives an error.
117    
118    15. If a forward reference was repeated with an upper limit of around 2000,
119        it caused the error "internal error: overran compiling workspace". The
120        maximum number of forward references (including repeats) was limited by the
121        internal workspace, and dependent on the LINK_SIZE. The code has been
122        rewritten so that the workspace expands (via pcre_malloc) if necessary, and
123        the default depends on LINK_SIZE. There is a new upper limit (for safety)
124        of around 200,000 forward references. While doing this, I also speeded up
125        the filling in of repeated forward references.
126    
127    16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
128        incorrectly expecting the subject to contain another "a" after the start.
129    
130    17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
131        in the match, the SKIP should be ignored. This was not happening; instead
132        the SKIP was being treated as NOMATCH. For patterns such as
133        /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
134        tested.
135    
136    18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
137        now much more compatible with Perl, in particular in cases where the result
138        is a non-match for a non-anchored pattern. For example, if
139        /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
140        "m", where previously it did not return a name. A side effect of this
141        change is that for partial matches, the last encountered mark name is
142        returned, as for non matches. A number of tests that were previously not
143        Perl-compatible have been moved into the Perl-compatible test files. The
144        refactoring has had the pleasing side effect of removing one argument from
145        the match() function, thus reducing its stack requirements.
146    
147    19. If the /S+ option was used in pcretest to study a pattern using JIT,
148        subsequent uses of /S (without +) incorrectly behaved like /S+.
149    
150    21. Retrieve executable code size support for the JIT compiler and fixing
151        some warnings.
152    
153    22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
154        not work when the shorter character appeared right at the end of the
155        subject string.
156    
157    23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
158        systems.
159    
160    24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
161        output it when the /M option is used in pcretest.
162    
163    25. The CheckMan script was not being included in the distribution. Also, added
164        an explicit "perl" to run Perl scripts from the PrepareRelease script
165        because this is reportedly needed in Windows.
166    
167    26. If study data was being save in a file and studying had not found a set of
168        "starts with" bytes for the pattern, the data written to the file (though
169        never used) was taken from uninitialized memory and so caused valgrind to
170        complain.
171    
172    27. Updated RunTest.bat as provided by Sheri Pierce.
173    
174    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
175    
176    29. Computation of memory usage for the table of capturing group names was
177        giving an unnecessarily large value.
178    
179    
180    Version 8.20 21-Oct-2011
181    ------------------------
182    
183    1.  Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had
184        a POSIX class. After further experiments with Perl, which convinced me that
185        Perl has bugs and confusions, a closing square bracket is no longer allowed
186        in a POSIX name. This bug also affected patterns with classes that started
187        with full stops.
188    
189    2.  If a pattern such as /(a)b|ac/ is matched against "ac", there is no
190        captured substring, but while checking the failing first alternative,
191        substring 1 is temporarily captured. If the output vector supplied to
192        pcre_exec() was not big enough for this capture, the yield of the function
193        was still zero ("insufficient space for captured substrings"). This cannot
194        be totally fixed without adding another stack variable, which seems a lot
195        of expense for a edge case. However, I have improved the situation in cases
196        such as /(a)(b)x|abc/ matched against "abc", where the return code
197        indicates that fewer than the maximum number of slots in the ovector have
198        been set.
199    
200    3.  Related to (2) above: when there are more back references in a pattern than
201        slots in the output vector, pcre_exec() uses temporary memory during
202        matching, and copies in the captures as far as possible afterwards. It was
203        using the entire output vector, but this conflicts with the specification
204        that only 2/3 is used for passing back captured substrings. Now it uses
205        only the first 2/3, for compatibility. This is, of course, another edge
206        case.
207    
208    4.  Zoltan Herczeg's just-in-time compiler support has been integrated into the
209        main code base, and can be used by building with --enable-jit. When this is
210        done, pcregrep automatically uses it unless --disable-pcregrep-jit or the
211        runtime --no-jit option is given.
212    
213    5.  When the number of matches in a pcre_dfa_exec() run exactly filled the
214        ovector, the return from the function was zero, implying that there were
215        other matches that did not fit. The correct "exactly full" value is now
216        returned.
217    
218    6.  If a subpattern that was called recursively or as a subroutine contained
219        (*PRUNE) or any other control that caused it to give a non-standard return,
220        invalid errors such as "Error -26 (nested recursion at the same subject
221        position)" or even infinite loops could occur.
222    
223    7.  If a pattern such as /a(*SKIP)c|b(*ACCEPT)|/ was studied, it stopped
224        computing the minimum length on reaching *ACCEPT, and so ended up with the
225        wrong value of 1 rather than 0. Further investigation indicates that
226        computing a minimum subject length in the presence of *ACCEPT is difficult
227        (think back references, subroutine calls), and so I have changed the code
228        so that no minimum is registered for a pattern that contains *ACCEPT.
229    
230    8.  If (*THEN) was present in the first (true) branch of a conditional group,
231        it was not handled as intended. [But see 16 below.]
232    
233    9.  Replaced RunTest.bat and CMakeLists.txt with improved versions provided by
234        Sheri Pierce.
235    
236    10. A pathological pattern such as /(*ACCEPT)a/ was miscompiled, thinking that
237        the first byte in a match must be "a".
238    
239    11. Change 17 for 8.13 increased the recursion depth for patterns like
240        /a(?:.)*?a/ drastically. I've improved things by remembering whether a
241        pattern contains any instances of (*THEN). If it does not, the old
242        optimizations are restored. It would be nice to do this on a per-group
243        basis, but at the moment that is not feasible.
244    
245    12. In some environments, the output of pcretest -C is CRLF terminated. This
246        broke RunTest's code that checks for the link size. A single white space
247        character after the value is now allowed for.
248    
249    13. RunTest now checks for the "fr" locale as well as for "fr_FR" and "french".
250        For "fr", it uses the Windows-specific input and output files.
251    
252    14. If (*THEN) appeared in a group that was called recursively or as a
253        subroutine, it did not work as intended. [But see next item.]
254    
255    15. Consider the pattern /A (B(*THEN)C) | D/ where A, B, C, and D are complex
256        pattern fragments (but not containing any | characters). If A and B are
257        matched, but there is a failure in C so that it backtracks to (*THEN), PCRE
258        was behaving differently to Perl. PCRE backtracked into A, but Perl goes to
259        D. In other words, Perl considers parentheses that do not contain any |
260        characters to be part of a surrounding alternative, whereas PCRE was
261        treading (B(*THEN)C) the same as (B(*THEN)C|(*FAIL)) -- which Perl handles
262        differently. PCRE now behaves in the same way as Perl, except in the case
263        of subroutine/recursion calls such as (?1) which have in any case always
264        been different (but PCRE had them first :-).
265    
266    16. Related to 15 above: Perl does not treat the | in a conditional group as
267        creating alternatives. Such a group is treated in the same way as an
268        ordinary group without any | characters when processing (*THEN). PCRE has
269        been changed to match Perl's behaviour.
270    
271    17. If a user had set PCREGREP_COLO(U)R to something other than 1:31, the
272        RunGrepTest script failed.
273    
274    18. Change 22 for version 13 caused atomic groups to use more stack. This is
275        inevitable for groups that contain captures, but it can lead to a lot of
276        stack use in large patterns. The old behaviour has been restored for atomic
277        groups that do not contain any capturing parentheses.
278    
279    19. If the PCRE_NO_START_OPTIMIZE option was set for pcre_compile(), it did not
280        suppress the check for a minimum subject length at run time. (If it was
281        given to pcre_exec() or pcre_dfa_exec() it did work.)
282    
283    20. Fixed an ASCII-dependent infelicity in pcretest that would have made it
284        fail to work when decoding hex characters in data strings in EBCDIC
285        environments.
286    
287    21. It appears that in at least one Mac OS environment, the isxdigit() function
288        is implemented as a macro that evaluates to its argument more than once,
289        contravening the C 90 Standard (I haven't checked a later standard). There
290        was an instance in pcretest which caused it to go wrong when processing
291        \x{...} escapes in subject strings. The has been rewritten to avoid using
292        things like p++ in the argument of isxdigit().
293    
294    
295    Version 8.13 16-Aug-2011
296    ------------------------
297    
298    1.  The Unicode data tables have been updated to Unicode 6.0.0.
299    
300    2.  Two minor typos in pcre_internal.h have been fixed.
301    
302    3.  Added #include <string.h> to pcre_scanner_unittest.cc, pcrecpp.cc, and
303        pcrecpp_unittest.cc. They are needed for strcmp(), memset(), and strchr()
304        in some environments (e.g. Solaris 10/SPARC using Sun Studio 12U2).
305    
306    4.  There were a number of related bugs in the code for matching backrefences
307        caselessly in UTF-8 mode when codes for the characters concerned were
308        different numbers of bytes. For example, U+023A and U+2C65 are an upper
309        and lower case pair, using 2 and 3 bytes, respectively. The main bugs were:
310        (a) A reference to 3 copies of a 2-byte code matched only 2 of a 3-byte
311        code. (b) A reference to 2 copies of a 3-byte code would not match 2 of a
312        2-byte code at the end of the subject (it thought there wasn't enough data
313        left).
314    
315    5.  Comprehensive information about what went wrong is now returned by
316        pcre_exec() and pcre_dfa_exec() when the UTF-8 string check fails, as long
317        as the output vector has at least 2 elements. The offset of the start of
318        the failing character and a reason code are placed in the vector.
319    
320    6.  When the UTF-8 string check fails for pcre_compile(), the offset that is
321        now returned is for the first byte of the failing character, instead of the
322        last byte inspected. This is an incompatible change, but I hope it is small
323        enough not to be a problem. It makes the returned offset consistent with
324        pcre_exec() and pcre_dfa_exec().
325    
326    7.  pcretest now gives a text phrase as well as the error number when
327        pcre_exec() or pcre_dfa_exec() fails; if the error is a UTF-8 check
328        failure, the offset and reason code are output.
329    
330    8.  When \R was used with a maximizing quantifier it failed to skip backwards
331        over a \r\n pair if the subsequent match failed. Instead, it just skipped
332        back over a single character (\n). This seems wrong (because it treated the
333        two characters as a single entity when going forwards), conflicts with the
334        documentation that \R is equivalent to (?>\r\n|\n|...etc), and makes the
335        behaviour of \R* different to (\R)*, which also seems wrong. The behaviour
336        has been changed.
337    
338    9.  Some internal refactoring has changed the processing so that the handling
339        of the PCRE_CASELESS and PCRE_MULTILINE options is done entirely at compile
340        time (the PCRE_DOTALL option was changed this way some time ago: version
341        7.7 change 16). This has made it possible to abolish the OP_OPT op code,
342        which was always a bit of a fudge. It also means that there is one less
343        argument for the match() function, which reduces its stack requirements
344        slightly. This change also fixes an incompatibility with Perl: the pattern
345        (?i:([^b]))(?1) should not match "ab", but previously PCRE gave a match.
346    
347    10. More internal refactoring has drastically reduced the number of recursive
348        calls to match() for possessively repeated groups such as (abc)++ when
349        using pcre_exec().
350    
351    11. While implementing 10, a number of bugs in the handling of groups were
352        discovered and fixed:
353    
354        (?<=(a)+) was not diagnosed as invalid (non-fixed-length lookbehind).
355        (a|)*(?1) gave a compile-time internal error.
356        ((a|)+)+  did not notice that the outer group could match an empty string.
357        (^a|^)+   was not marked as anchored.
358        (.*a|.*)+ was not marked as matching at start or after a newline.
359    
360    12. Yet more internal refactoring has removed another argument from the match()
361        function. Special calls to this function are now indicated by setting a
362        value in a variable in the "match data" data block.
363    
364    13. Be more explicit in pcre_study() instead of relying on "default" for
365        opcodes that mean there is no starting character; this means that when new
366        ones are added and accidentally left out of pcre_study(), testing should
367        pick them up.
368    
369    14. The -s option of pcretest has been documented for ages as being an old
370        synonym of -m (show memory usage). I have changed it to mean "force study
371        for every regex", that is, assume /S for every regex. This is similar to -i
372        and -d etc. It's slightly incompatible, but I'm hoping nobody is still
373        using it. It makes it easier to run collections of tests with and without
374        study enabled, and thereby test pcre_study() more easily. All the standard
375        tests are now run with and without -s (but some patterns can be marked as
376        "never study" - see 20 below).
377    
378    15. When (*ACCEPT) was used in a subpattern that was called recursively, the
379        restoration of the capturing data to the outer values was not happening
380        correctly.
381    
382    16. If a recursively called subpattern ended with (*ACCEPT) and matched an
383        empty string, and PCRE_NOTEMPTY was set, pcre_exec() thought the whole
384        pattern had matched an empty string, and so incorrectly returned a no
385        match.
386    
387    17. There was optimizing code for the last branch of non-capturing parentheses,
388        and also for the obeyed branch of a conditional subexpression, which used
389        tail recursion to cut down on stack usage. Unfortunately, now that there is
390        the possibility of (*THEN) occurring in these branches, tail recursion is
391        no longer possible because the return has to be checked for (*THEN). These
392        two optimizations have therefore been removed. [But see 8.20/11 above.]
393    
394    18. If a pattern containing \R was studied, it was assumed that \R always
395        matched two bytes, thus causing the minimum subject length to be
396        incorrectly computed because \R can also match just one byte.
397    
398    19. If a pattern containing (*ACCEPT) was studied, the minimum subject length
399        was incorrectly computed.
400    
401    20. If /S is present twice on a test pattern in pcretest input, it now
402        *disables* studying, thereby overriding the use of -s on the command line
403        (see 14 above). This is necessary for one or two tests to keep the output
404        identical in both cases.
405    
406    21. When (*ACCEPT) was used in an assertion that matched an empty string and
407        PCRE_NOTEMPTY was set, PCRE applied the non-empty test to the assertion.
408    
409    22. When an atomic group that contained a capturing parenthesis was
410        successfully matched, but the branch in which it appeared failed, the
411        capturing was not being forgotten if a higher numbered group was later
412        captured. For example, /(?>(a))b|(a)c/ when matching "ac" set capturing
413        group 1 to "a", when in fact it should be unset. This applied to multi-
414        branched capturing and non-capturing groups, repeated or not, and also to
415        positive assertions (capturing in negative assertions does not happen
416        in PCRE) and also to nested atomic groups.
417    
418    23. Add the ++ qualifier feature to pcretest, to show the remainder of the
419        subject after a captured substring, to make it easier to tell which of a
420        number of identical substrings has been captured.
421    
422    24. The way atomic groups are processed by pcre_exec() has been changed so that
423        if they are repeated, backtracking one repetition now resets captured
424        values correctly. For example, if ((?>(a+)b)+aabab) is matched against
425        "aaaabaaabaabab" the value of captured group 2 is now correctly recorded as
426        "aaa". Previously, it would have been "a". As part of this code
427        refactoring, the way recursive calls are handled has also been changed.
428    
429    25. If an assertion condition captured any substrings, they were not passed
430        back unless some other capturing happened later. For example, if
431        (?(?=(a))a) was matched against "a", no capturing was returned.
432    
433    26. When studying a pattern that contained subroutine calls or assertions,
434        the code for finding the minimum length of a possible match was handling
435        direct recursions such as (xxx(?1)|yyy) but not mutual recursions (where
436        group 1 called group 2 while simultaneously a separate group 2 called group
437        1). A stack overflow occurred in this case. I have fixed this by limiting
438        the recursion depth to 10.
439    
440    27. Updated RunTest.bat in the distribution to the version supplied by Tom
441        Fortmann. This supports explicit test numbers on the command line, and has
442        argument validation and error reporting.
443    
444    28. An instance of \X with an unlimited repeat could fail if at any point the
445        first character it looked at was a mark character.
446    
447    29. Some minor code refactoring concerning Unicode properties and scripts
448        should reduce the stack requirement of match() slightly.
449    
450    30. Added the '=' option to pcretest to check the setting of unused capturing
451        slots at the end of the pattern, which are documented as being -1, but are
452        not included in the return count.
453    
454    31. If \k was not followed by a braced, angle-bracketed, or quoted name, PCRE
455        compiled something random. Now it gives a compile-time error (as does
456        Perl).
457    
458    32. A *MARK encountered during the processing of a positive assertion is now
459        recorded and passed back (compatible with Perl).
460    
461    33. If --only-matching or --colour was set on a pcregrep call whose pattern
462        had alternative anchored branches, the search for a second match in a line
463        was done as if at the line start. Thus, for example, /^01|^02/ incorrectly
464        matched the line "0102" twice. The same bug affected patterns that started
465        with a backwards assertion. For example /\b01|\b02/ also matched "0102"
466        twice.
467    
468    34. Previously, PCRE did not allow quantification of assertions. However, Perl
469        does, and because of capturing effects, quantifying parenthesized
470        assertions may at times be useful. Quantifiers are now allowed for
471        parenthesized assertions.
472    
473    35. A minor code tidy in pcre_compile() when checking options for \R usage.
474    
475    36. \g was being checked for fancy things in a character class, when it should
476        just be a literal "g".
477    
478    37. PCRE was rejecting [:a[:digit:]] whereas Perl was not. It seems that the
479        appearance of a nested POSIX class supersedes an apparent external class.
480        For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,
481        unescaped square brackets may also appear as part of class names. For
482        example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves
483        more like Perl. (But see 8.20/1 above.)
484    
485    38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this
486        was because it thought it was \N{name}, which is not supported).
487    
488    39. Add minix to OS list not supporting the -S option in pcretest.
489    
490    40. PCRE tries to detect cases of infinite recursion at compile time, but it
491        cannot analyze patterns in sufficient detail to catch mutual recursions
492        such as ((?1))((?2)). There is now a runtime test that gives an error if a
493        subgroup is called recursively as a subpattern for a second time at the
494        same position in the subject string. In previous releases this might have
495        been caught by the recursion limit, or it might have run out of stack.
496    
497    41. A pattern such as /(?(R)a+|(?R)b)/ is quite safe, as the recursion can
498        happen only once. PCRE was, however incorrectly giving a compile time error
499        "recursive call could loop indefinitely" because it cannot analyze the
500        pattern in sufficient detail. The compile time test no longer happens when
501        PCRE is compiling a conditional subpattern, but actual runaway loops are
502        now caught at runtime (see 40 above).
503    
504    42. It seems that Perl allows any characters other than a closing parenthesis
505        to be part of the NAME in (*MARK:NAME) and other backtracking verbs. PCRE
506        has been changed to be the same.
507    
508    43. Updated configure.ac to put in more quoting round AC_LANG_PROGRAM etc. so
509        as not to get warnings when autogen.sh is called. Also changed
510        AC_PROG_LIBTOOL (deprecated) to LT_INIT (the current macro).
511    
512    44. To help people who use pcregrep to scan files containing exceedingly long
513        lines, the following changes have been made:
514    
515        (a) The default value of the buffer size parameter has been increased from
516            8K to 20K. (The actual buffer used is three times this size.)
517    
518        (b) The default can be changed by ./configure --with-pcregrep-bufsize when
519            PCRE is built.
520    
521        (c) A --buffer-size=n option has been added to pcregrep, to allow the size
522            to be set at run time.
523    
524        (d) Numerical values in pcregrep options can be followed by K or M, for
525            example --buffer-size=50K.
526    
527        (e) If a line being scanned overflows pcregrep's buffer, an error is now
528            given and the return code is set to 2.
529    
530    45. Add a pointer to the latest mark to the callout data block.
531    
532    46. The pattern /.(*F)/, when applied to "abc" with PCRE_PARTIAL_HARD, gave a
533        partial match of an empty string instead of no match. This was specific to
534        the use of ".".
535    
536    47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a
537        complete match instead of a partial match. This bug was dependent on both
538        the PCRE_UTF8 and PCRE_DOTALL options being set.
539    
540    48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the
541        starting byte set, because \b was not being ignored.
542    
543    
544    Version 8.12 15-Jan-2011
545    ------------------------
546    
547    1.  Fixed some typos in the markup of the man pages, and wrote a script that
548        checks for such things as part of the documentation building process.
549    
550    2.  On a big-endian 64-bit system, pcregrep did not correctly process the
551        --match-limit and --recursion-limit options (added for 8.11). In
552        particular, this made one of the standard tests fail. (The integer value
553        went into the wrong half of a long int.)
554    
555    3.  If the --colour option was given to pcregrep with -v (invert match), it
556        did strange things, either producing crazy output, or crashing. It should,
557        of course, ignore a request for colour when reporting lines that do not
558        match.
559    
560    4.  Another pcregrep bug caused similar problems if --colour was specified with
561        -M (multiline) and the pattern match finished with a line ending.
562    
563    5.  In pcregrep, when a pattern that ended with a literal newline sequence was
564        matched in multiline mode, the following line was shown as part of the
565        match. This seems wrong, so I have changed it.
566    
567    6.  Another pcregrep bug in multiline mode, when --colour was specified, caused
568        the check for further matches in the same line (so they could be coloured)
569        to overrun the end of the current line. If another match was found, it was
570        incorrectly shown (and then shown again when found in the next line).
571    
572    7.  If pcregrep was compiled under Windows, there was a reference to the
573        function pcregrep_exit() before it was defined. I am assuming this was
574        the cause of the "error C2371: 'pcregrep_exit' : redefinition;" that was
575        reported by a user. I've moved the definition above the reference.
576    
577    
578    Version 8.11 10-Dec-2010
579    ------------------------
580    
581    1.  (*THEN) was not working properly if there were untried alternatives prior
582        to it in the current branch. For example, in ((a|b)(*THEN)(*F)|c..) it
583        backtracked to try for "b" instead of moving to the next alternative branch
584        at the same level (in this case, to look for "c"). The Perl documentation
585        is clear that when (*THEN) is backtracked onto, it goes to the "next
586        alternative in the innermost enclosing group".
587    
588    2.  (*COMMIT) was not overriding (*THEN), as it does in Perl. In a pattern
589        such as   (A(*COMMIT)B(*THEN)C|D)  any failure after matching A should
590        result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and
591        (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides
592        (*THEN).
593    
594    3.  If \s appeared in a character class, it removed the VT character from
595        the class, even if it had been included by some previous item, for example
596        in [\x00-\xff\s]. (This was a bug related to the fact that VT is not part
597        of \s, but is part of the POSIX "space" class.)
598    
599    4.  A partial match never returns an empty string (because you can always
600        match an empty string at the end of the subject); however the checking for
601        an empty string was starting at the "start of match" point. This has been
602        changed to the "earliest inspected character" point, because the returned
603        data for a partial match starts at this character. This means that, for
604        example, /(?<=abc)def/ gives a partial match for the subject "abc"
605        (previously it gave "no match").
606    
607    5.  Changes have been made to the way PCRE_PARTIAL_HARD affects the matching
608        of $, \z, \Z, \b, and \B. If the match point is at the end of the string,
609        previously a full match would be given. However, setting PCRE_PARTIAL_HARD
610        has an implication that the given string is incomplete (because a partial
611        match is preferred over a full match). For this reason, these items now
612        give a partial match in this situation. [Aside: previously, the one case
613        /t\b/ matched against "cat" with PCRE_PARTIAL_HARD set did return a partial
614        match rather than a full match, which was wrong by the old rules, but is
615        now correct.]
616    
617    6.  There was a bug in the handling of #-introduced comments, recognized when
618        PCRE_EXTENDED is set, when PCRE_NEWLINE_ANY and PCRE_UTF8 were also set.
619        If a UTF-8 multi-byte character included the byte 0x85 (e.g. +U0445, whose
620        UTF-8 encoding is 0xd1,0x85), this was misinterpreted as a newline when
621        scanning for the end of the comment. (*Character* 0x85 is an "any" newline,
622        but *byte* 0x85 is not, in UTF-8 mode). This bug was present in several
623        places in pcre_compile().
624    
625    7.  Related to (6) above, when pcre_compile() was skipping #-introduced
626        comments when looking ahead for named forward references to subpatterns,
627        the only newline sequence it recognized was NL. It now handles newlines
628        according to the set newline convention.
629    
630    8.  SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the
631        former, but used strtoul(), whereas pcretest avoided strtoul() but did not
632        cater for a lack of strerror(). These oversights have been fixed.
633    
634    9.  Added --match-limit and --recursion-limit to pcregrep.
635    
636    10. Added two casts needed to build with Visual Studio when NO_RECURSE is set.
637    
638    11. When the -o option was used, pcregrep was setting a return code of 1, even
639        when matches were found, and --line-buffered was not being honoured.
640    
641    12. Added an optional parentheses number to the -o and --only-matching options
642        of pcregrep.
643    
644    13. Imitating Perl's /g action for multiple matches is tricky when the pattern
645        can match an empty string. The code to do it in pcretest and pcredemo
646        needed fixing:
647    
648        (a) When the newline convention was "crlf", pcretest got it wrong, skipping
649            only one byte after an empty string match just before CRLF (this case
650            just got forgotten; "any" and "anycrlf" were OK).
651    
652        (b) The pcretest code also had a bug, causing it to loop forever in UTF-8
653            mode when an empty string match preceded an ASCII character followed by
654            a non-ASCII character. (The code for advancing by one character rather
655            than one byte was nonsense.)
656    
657        (c) The pcredemo.c sample program did not have any code at all to handle
658            the cases when CRLF is a valid newline sequence.
659    
660    14. Neither pcre_exec() nor pcre_dfa_exec() was checking that the value given
661        as a starting offset was within the subject string. There is now a new
662        error, PCRE_ERROR_BADOFFSET, which is returned if the starting offset is
663        negative or greater than the length of the string. In order to test this,
664        pcretest is extended to allow the setting of negative starting offsets.
665    
666    15. In both pcre_exec() and pcre_dfa_exec() the code for checking that the
667        starting offset points to the beginning of a UTF-8 character was
668        unnecessarily clumsy. I tidied it up.
669    
670    16. Added PCRE_ERROR_SHORTUTF8 to make it possible to distinguish between a
671        bad UTF-8 sequence and one that is incomplete when using PCRE_PARTIAL_HARD.
672    
673    17. Nobody had reported that the --include_dir option, which was added in
674        release 7.7 should have been called --include-dir (hyphen, not underscore)
675        for compatibility with GNU grep. I have changed it to --include-dir, but
676        left --include_dir as an undocumented synonym, and the same for
677        --exclude-dir, though that is not available in GNU grep, at least as of
678        release 2.5.4.
679    
680    18. At a user's suggestion, the macros GETCHAR and friends (which pick up UTF-8
681        characters from a string of bytes) have been redefined so as not to use
682        loops, in order to improve performance in some environments. At the same
683        time, I abstracted some of the common code into auxiliary macros to save
684        repetition (this should not affect the compiled code).
685    
686    19. If \c was followed by a multibyte UTF-8 character, bad things happened. A
687        compile-time error is now given if \c is not followed by an ASCII
688        character, that is, a byte less than 128. (In EBCDIC mode, the code is
689        different, and any byte value is allowed.)
690    
691    20. Recognize (*NO_START_OPT) at the start of a pattern to set the PCRE_NO_
692        START_OPTIMIZE option, which is now allowed at compile time - but just
693        passed through to pcre_exec() or pcre_dfa_exec(). This makes it available
694        to pcregrep and other applications that have no direct access to PCRE
695        options. The new /Y option in pcretest sets this option when calling
696        pcre_compile().
697    
698    21. Change 18 of release 8.01 broke the use of named subpatterns for recursive
699        back references. Groups containing recursive back references were forced to
700        be atomic by that change, but in the case of named groups, the amount of
701        memory required was incorrectly computed, leading to "Failed: internal
702        error: code overflow". This has been fixed.
703    
704    22. Some patches to pcre_stringpiece.h, pcre_stringpiece_unittest.cc, and
705        pcretest.c, to avoid build problems in some Borland environments.
706    
707    
708    Version 8.10 25-Jun-2010
709    ------------------------
710    
711    1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and
712        THEN.
713    
714    2.  (*ACCEPT) was not working when inside an atomic group.
715    
716    3.  Inside a character class, \B is treated as a literal by default, but
717        faulted if PCRE_EXTRA is set. This mimics Perl's behaviour (the -w option
718        causes the error). The code is unchanged, but I tidied the documentation.
719    
720    4.  Inside a character class, PCRE always treated \R and \X as literals,
721        whereas Perl faults them if its -w option is set. I have changed PCRE so
722        that it faults them when PCRE_EXTRA is set.
723    
724    5.  Added support for \N, which always matches any character other than
725        newline. (It is the same as "." when PCRE_DOTALL is not set.)
726    
727    6.  When compiling pcregrep with newer versions of gcc which may have
728        FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',
729        declared with attribute warn_unused_result" were given. Just casting the
730        result to (void) does not stop the warnings; a more elaborate fudge is
731        needed. I've used a macro to implement this.
732    
733    7.  Minor change to pcretest.c to avoid a compiler warning.
734    
735    8.  Added four artifical Unicode properties to help with an option to make
736        \s etc use properties (see next item). The new properties are: Xan
737        (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).
738    
739    9.  Added PCRE_UCP to make \b, \d, \s, \w, and certain POSIX character classes
740        use Unicode properties. (*UCP) at the start of a pattern can be used to set
741        this option. Modified pcretest to add /W to test this facility. Added
742        REG_UCP to make it available via the POSIX interface.
743    
744    10. Added --line-buffered to pcregrep.
745    
746    11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was
747        studied, and the match started with a letter with a code point greater than
748        127 whose first byte was different to the first byte of the other case of
749        the letter, the other case of this starting letter was not recognized
750        (#976).
751    
752    12. If a pattern that was studied started with a repeated Unicode property
753        test, for example, \p{Nd}+, there was the theoretical possibility of
754        setting up an incorrect bitmap of starting bytes, but fortunately it could
755        not have actually happened in practice until change 8 above was made (it
756        added property types that matched character-matching opcodes).
757    
758    13. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
759        possible starting bytes for non-anchored patterns.
760    
761    14. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes
762        \R, and also a number of cases that involve Unicode properties, both
763        explicit and implicit when PCRE_UCP is set.
764    
765    15. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8
766        input, it could crash or give wrong results if characters with values
767        greater than 0xc0 were present in the subject string. (Detail: it assumed
768        UTF-8 input when processing these items.)
769    
770    16. Added a lot of (int) casts to avoid compiler warnings in systems where
771        size_t is 64-bit (#991).
772    
773    17. Added a check for running out of memory when PCRE is compiled with
774        --disable-stack-for-recursion (#990).
775    
776    18. If the last data line in a file for pcretest does not have a newline on
777        the end, a newline was missing in the output.
778    
779    19. The default pcre_chartables.c file recognizes only ASCII characters (values
780        less than 128) in its various bitmaps. However, there is a facility for
781        generating tables according to the current locale when PCRE is compiled. It
782        turns out that in some environments, 0x85 and 0xa0, which are Unicode space
783        characters, are recognized by isspace() and therefore were getting set in
784        these tables, and indeed these tables seem to approximate to ISO 8859. This
785        caused a problem in UTF-8 mode when pcre_study() was used to create a list
786        of bytes that can start a match. For \s, it was including 0x85 and 0xa0,
787        which of course cannot start UTF-8 characters. I have changed the code so
788        that only real ASCII characters (less than 128) and the correct starting
789        bytes for UTF-8 encodings are set for characters greater than 127 when in
790        UTF-8 mode. (When PCRE_UCP is set - see 9 above - the code is different
791        altogether.)
792    
793    20. Added the /T option to pcretest so as to be able to run tests with non-
794        standard character tables, thus making it possible to include the tests
795        used for 19 above in the standard set of tests.
796    
797    21. A pattern such as (?&t)(?#()(?(DEFINE)(?<t>a)) which has a forward
798        reference to a subpattern the other side of a comment that contains an
799        opening parenthesis caused either an internal compiling error, or a
800        reference to the wrong subpattern.
801    
802    
803    Version 8.02 19-Mar-2010
804  ------------------------  ------------------------
805    
806  1.  The Unicode data tables have been updated to Unicode 5.2.0.  1.  The Unicode data tables have been updated to Unicode 5.2.0.
807    
808    2.  Added the option --libs-cpp to pcre-config, but only when C++ support is
809        configured.
810    
811    3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the
812        original author of that file, following a query about its status.
813    
814    4.  On systems that do not have stdint.h (e.g. Solaris), check for and include
815        inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
816    
817    5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
818        quantifier applied to a forward-referencing subroutine call, could compile
819        incorrect code or give the error "internal error: previously-checked
820        referenced subpattern not found".
821    
822    6.  Both MS Visual Studio and Symbian OS have problems with initializing
823        variables to point to external functions. For these systems, therefore,
824        pcre_malloc etc. are now initialized to local functions that call the
825        relevant global functions.
826    
827    7.  There were two entries missing in the vectors called coptable and poptable
828        in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.
829        I've fixed the data, and added a kludgy way of testing at compile time that
830        the lengths are correct (equal to the number of opcodes).
831    
832    8.  Following on from 7, I added a similar kludge to check the length of the
833        eint vector in pcreposix.c.
834    
835    9.  Error texts for pcre_compile() are held as one long string to avoid too
836        much relocation at load time. To find a text, the string is searched,
837        counting zeros. There was no check for running off the end of the string,
838        which could happen if a new error number was added without updating the
839        string.
840    
841    10. \K gave a compile-time error if it appeared in a lookbehind assersion.
842    
843    11. \K was not working if it appeared in an atomic group or in a group that
844        was called as a "subroutine", or in an assertion. Perl 5.11 documents that
845        \K is "not well defined" if used in an assertion. PCRE now accepts it if
846        the assertion is positive, but not if it is negative.
847    
848    12. Change 11 fortuitously reduced the size of the stack frame used in the
849        "match()" function of pcre_exec.c by one pointer. Forthcoming
850        implementation of support for (*MARK) will need an extra pointer on the
851        stack; I have reserved it now, so that the stack frame size does not
852        decrease.
853    
854    13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other
855        item in branch that calls a recursion is a subroutine call - as in the
856        second branch in the above example - was incorrectly given the compile-
857        time error "recursive call could loop indefinitely" because pcre_compile()
858        was not correctly checking the subroutine for matching a non-empty string.
859    
860    14. The checks for overrunning compiling workspace could trigger after an
861        overrun had occurred. This is a "should never occur" error, but it can be
862        triggered by pathological patterns such as hundreds of nested parentheses.
863        The checks now trigger 100 bytes before the end of the workspace.
864    
865    15. Fix typo in configure.ac: "srtoq" should be "strtoq".
866    
867    
868  Version 8.01 19-Jan-2010  Version 8.01 19-Jan-2010
869  ------------------------  ------------------------

Legend:
Removed from v.491  
changed lines
  Added in v.893

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12