ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 422 by ph10, Fri Aug 14 16:42:55 2009 UTC revision 712 by ph10, Mon Sep 26 16:31:42 2011 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 8.00 ??-???-??  Version 8.20 23-Sep-2011
5    ------------------------
7    1.  Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had
8        a POSIX class. After further experiments with Perl, which convinced me that
9        Perl has bugs and confusions, a closing square bracket is no longer allowed
10        in a POSIX name. This bug also affected patterns with classes that started
11        with full stops.
13    2.  If a pattern such as /(a)b|ac/ is matched against "ac", there is no
14        captured substring, but while checking the failing first alternative,
15        substring 1 is temporarily captured. If the output vector supplied to
16        pcre_exec() was not big enough for this capture, the yield of the function
17        was still zero ("insufficient space for captured substrings"). This cannot
18        be totally fixed without adding another stack variable, which seems a lot
19        of expense for a edge case. However, I have improved the situation in cases
20        such as /(a)(b)x|abc/ matched against "abc", where the return code
21        indicates that fewer than the maximum number of slots in the ovector have
22        been set.
24    3.  Related to (2) above: when there are more back references in a pattern than
25        slots in the output vector, pcre_exec() uses temporary memory during
26        matching, and copies in the captures as far as possible afterwards. It was
27        using the entire output vector, but this conflicts with the specification
28        that only 2/3 is used for passing back captured substrings. Now it uses
29        only the first 2/3, for compatibility. This is, of course, another edge
30        case.
32    4.  Zoltan Herczeg's just-in-time compiler support has been integrated into the
33        main code base, and can be used by building with --enable-jit. When this is
34        done, pcregrep automatically uses it unless --disable-pcregrep-jit or the
35        runtime --no-jit option is given.
37    5.  When the number of matches in a pcre_dfa_exec() run exactly filled the
38        ovector, the return from the function was zero, implying that there were
39        other matches that did not fit. The correct "exactly full" value is now
40        returned.
42    6.  If a subpattern that was called recursively or as a subroutine contained
43        (*PRUNE) or any other control that caused it to give a non-standard return,
44        invalid errors such as "Error -26 (nested recursion at the same subject
45        position)" or even infinite loops could occur.
47    7.  If a pattern such as /a(*SKIP)c|b(*ACCEPT)|/ was studied, it stopped
48        computing the minimum length on reaching *ACCEPT, and so ended up with the
49        wrong value of 1 rather than 0. Further investigation indicates that
50        computing a minimum subject length in the presence of *ACCEPT is difficult
51        (think back references, subroutine calls), and so I have changed the code
52        so that no minimum is registered for a pattern that contains *ACCEPT.
54    8.  If (*THEN) was present in the first (true) branch of a conditional group,
55        it was not handled as intended.
57    9.  Replaced RunTest.bat with the much improved version provided by Sheri
58        Pierce.
60    10. A pathological pattern such as /(*ACCEPT)a/ was miscompiled, thinking that
61        the first byte in a match must be "a".
63    11. Change 17 for 8.13 increased the recursion depth for patterns like
64        /a(?:.)*?a/ drastically. I've improved things by remembering whether a
65        pattern contains any instances of (*THEN). If it does not, the old
66        optimizations are restored. It would be nice to do this on a per-group
67        basis, but at the moment that is not feasible.
69    12. In some environments, the output of pcretest -C is CRLF terminated. This
70        broke RunTest's code that checks for the link size. A single white space
71        after the value is now allowed for.
73    13. RunTest now checks for the "fr" locale as well as for "fr_FR" and "french".
74        For "fr", it uses the Windows-specific input and output files.
77    Version 8.13 16-Aug-2011
78    ------------------------
80    1.  The Unicode data tables have been updated to Unicode 6.0.0.
82    2.  Two minor typos in pcre_internal.h have been fixed.
84    3.  Added #include <string.h> to pcre_scanner_unittest.cc, pcrecpp.cc, and
85        pcrecpp_unittest.cc. They are needed for strcmp(), memset(), and strchr()
86        in some environments (e.g. Solaris 10/SPARC using Sun Studio 12U2).
88    4.  There were a number of related bugs in the code for matching backrefences
89        caselessly in UTF-8 mode when codes for the characters concerned were
90        different numbers of bytes. For example, U+023A and U+2C65 are an upper
91        and lower case pair, using 2 and 3 bytes, respectively. The main bugs were:
92        (a) A reference to 3 copies of a 2-byte code matched only 2 of a 3-byte
93        code. (b) A reference to 2 copies of a 3-byte code would not match 2 of a
94        2-byte code at the end of the subject (it thought there wasn't enough data
95        left).
97    5.  Comprehensive information about what went wrong is now returned by
98        pcre_exec() and pcre_dfa_exec() when the UTF-8 string check fails, as long
99        as the output vector has at least 2 elements. The offset of the start of
100        the failing character and a reason code are placed in the vector.
102    6.  When the UTF-8 string check fails for pcre_compile(), the offset that is
103        now returned is for the first byte of the failing character, instead of the
104        last byte inspected. This is an incompatible change, but I hope it is small
105        enough not to be a problem. It makes the returned offset consistent with
106        pcre_exec() and pcre_dfa_exec().
108    7.  pcretest now gives a text phrase as well as the error number when
109        pcre_exec() or pcre_dfa_exec() fails; if the error is a UTF-8 check
110        failure, the offset and reason code are output.
112    8.  When \R was used with a maximizing quantifier it failed to skip backwards
113        over a \r\n pair if the subsequent match failed. Instead, it just skipped
114        back over a single character (\n). This seems wrong (because it treated the
115        two characters as a single entity when going forwards), conflicts with the
116        documentation that \R is equivalent to (?>\r\n|\n|...etc), and makes the
117        behaviour of \R* different to (\R)*, which also seems wrong. The behaviour
118        has been changed.
120    9.  Some internal refactoring has changed the processing so that the handling
121        of the PCRE_CASELESS and PCRE_MULTILINE options is done entirely at compile
122        time (the PCRE_DOTALL option was changed this way some time ago: version
123        7.7 change 16). This has made it possible to abolish the OP_OPT op code,
124        which was always a bit of a fudge. It also means that there is one less
125        argument for the match() function, which reduces its stack requirements
126        slightly. This change also fixes an incompatibility with Perl: the pattern
127        (?i:([^b]))(?1) should not match "ab", but previously PCRE gave a match.
129    10. More internal refactoring has drastically reduced the number of recursive
130        calls to match() for possessively repeated groups such as (abc)++ when
131        using pcre_exec().
133    11. While implementing 10, a number of bugs in the handling of groups were
134        discovered and fixed:
136        (?<=(a)+) was not diagnosed as invalid (non-fixed-length lookbehind).
137        (a|)*(?1) gave a compile-time internal error.
138        ((a|)+)+  did not notice that the outer group could match an empty string.
139        (^a|^)+   was not marked as anchored.
140        (.*a|.*)+ was not marked as matching at start or after a newline.
142    12. Yet more internal refactoring has removed another argument from the match()
143        function. Special calls to this function are now indicated by setting a
144        value in a variable in the "match data" data block.
146    13. Be more explicit in pcre_study() instead of relying on "default" for
147        opcodes that mean there is no starting character; this means that when new
148        ones are added and accidentally left out of pcre_study(), testing should
149        pick them up.
151    14. The -s option of pcretest has been documented for ages as being an old
152        synonym of -m (show memory usage). I have changed it to mean "force study
153        for every regex", that is, assume /S for every regex. This is similar to -i
154        and -d etc. It's slightly incompatible, but I'm hoping nobody is still
155        using it. It makes it easier to run collections of tests with and without
156        study enabled, and thereby test pcre_study() more easily. All the standard
157        tests are now run with and without -s (but some patterns can be marked as
158        "never study" - see 20 below).
160    15. When (*ACCEPT) was used in a subpattern that was called recursively, the
161        restoration of the capturing data to the outer values was not happening
162        correctly.
164    16. If a recursively called subpattern ended with (*ACCEPT) and matched an
165        empty string, and PCRE_NOTEMPTY was set, pcre_exec() thought the whole
166        pattern had matched an empty string, and so incorrectly returned a no
167        match.
169    17. There was optimizing code for the last branch of non-capturing parentheses,
170        and also for the obeyed branch of a conditional subexpression, which used
171        tail recursion to cut down on stack usage. Unfortunately, now that there is
172        the possibility of (*THEN) occurring in these branches, tail recursion is
173        no longer possible because the return has to be checked for (*THEN). These
174        two optimizations have therefore been removed. [But see 8.20/11 above.]
176    18. If a pattern containing \R was studied, it was assumed that \R always
177        matched two bytes, thus causing the minimum subject length to be
178        incorrectly computed because \R can also match just one byte.
180    19. If a pattern containing (*ACCEPT) was studied, the minimum subject length
181        was incorrectly computed.
183    20. If /S is present twice on a test pattern in pcretest input, it now
184        *disables* studying, thereby overriding the use of -s on the command line
185        (see 14 above). This is necessary for one or two tests to keep the output
186        identical in both cases.
188    21. When (*ACCEPT) was used in an assertion that matched an empty string and
189        PCRE_NOTEMPTY was set, PCRE applied the non-empty test to the assertion.
191    22. When an atomic group that contained a capturing parenthesis was
192        successfully matched, but the branch in which it appeared failed, the
193        capturing was not being forgotten if a higher numbered group was later
194        captured. For example, /(?>(a))b|(a)c/ when matching "ac" set capturing
195        group 1 to "a", when in fact it should be unset. This applied to multi-
196        branched capturing and non-capturing groups, repeated or not, and also to
197        positive assertions (capturing in negative assertions does not happen
198        in PCRE) and also to nested atomic groups.
200    23. Add the ++ qualifier feature to pcretest, to show the remainder of the
201        subject after a captured substring, to make it easier to tell which of a
202        number of identical substrings has been captured.
204    24. The way atomic groups are processed by pcre_exec() has been changed so that
205        if they are repeated, backtracking one repetition now resets captured
206        values correctly. For example, if ((?>(a+)b)+aabab) is matched against
207        "aaaabaaabaabab" the value of captured group 2 is now correctly recorded as
208        "aaa". Previously, it would have been "a". As part of this code
209        refactoring, the way recursive calls are handled has also been changed.
211    25. If an assertion condition captured any substrings, they were not passed
212        back unless some other capturing happened later. For example, if
213        (?(?=(a))a) was matched against "a", no capturing was returned.
215    26. When studying a pattern that contained subroutine calls or assertions,
216        the code for finding the minimum length of a possible match was handling
217        direct recursions such as (xxx(?1)|yyy) but not mutual recursions (where
218        group 1 called group 2 while simultaneously a separate group 2 called group
219        1). A stack overflow occurred in this case. I have fixed this by limiting
220        the recursion depth to 10.
222    27. Updated RunTest.bat in the distribution to the version supplied by Tom
223        Fortmann. This supports explicit test numbers on the command line, and has
224        argument validation and error reporting.
226    28. An instance of \X with an unlimited repeat could fail if at any point the
227        first character it looked at was a mark character.
229    29. Some minor code refactoring concerning Unicode properties and scripts
230        should reduce the stack requirement of match() slightly.
232    30. Added the '=' option to pcretest to check the setting of unused capturing
233        slots at the end of the pattern, which are documented as being -1, but are
234        not included in the return count.
236    31. If \k was not followed by a braced, angle-bracketed, or quoted name, PCRE
237        compiled something random. Now it gives a compile-time error (as does
238        Perl).
240    32. A *MARK encountered during the processing of a positive assertion is now
241        recorded and passed back (compatible with Perl).
243    33. If --only-matching or --colour was set on a pcregrep call whose pattern
244        had alternative anchored branches, the search for a second match in a line
245        was done as if at the line start. Thus, for example, /^01|^02/ incorrectly
246        matched the line "0102" twice. The same bug affected patterns that started
247        with a backwards assertion. For example /\b01|\b02/ also matched "0102"
248        twice.
250    34. Previously, PCRE did not allow quantification of assertions. However, Perl
251        does, and because of capturing effects, quantifying parenthesized
252        assertions may at times be useful. Quantifiers are now allowed for
253        parenthesized assertions.
255    35. A minor code tidy in pcre_compile() when checking options for \R usage.
257    36. \g was being checked for fancy things in a character class, when it should
258        just be a literal "g".
260    37. PCRE was rejecting [:a[:digit:]] whereas Perl was not. It seems that the
261        appearance of a nested POSIX class supersedes an apparent external class.
262        For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,
263        unescaped square brackets may also appear as part of class names. For
264        example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves
265        more like Perl. (But see 8.20/1 above.)
267    38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this
268        was because it thought it was \N{name}, which is not supported).
270    39. Add minix to OS list not supporting the -S option in pcretest.
272    40. PCRE tries to detect cases of infinite recursion at compile time, but it
273        cannot analyze patterns in sufficient detail to catch mutual recursions
274        such as ((?1))((?2)). There is now a runtime test that gives an error if a
275        subgroup is called recursively as a subpattern for a second time at the
276        same position in the subject string. In previous releases this might have
277        been caught by the recursion limit, or it might have run out of stack.
279    41. A pattern such as /(?(R)a+|(?R)b)/ is quite safe, as the recursion can
280        happen only once. PCRE was, however incorrectly giving a compile time error
281        "recursive call could loop indefinitely" because it cannot analyze the
282        pattern in sufficient detail. The compile time test no longer happens when
283        PCRE is compiling a conditional subpattern, but actual runaway loops are
284        now caught at runtime (see 40 above).
286    42. It seems that Perl allows any characters other than a closing parenthesis
287        to be part of the NAME in (*MARK:NAME) and other backtracking verbs. PCRE
288        has been changed to be the same.
290    43. Updated configure.ac to put in more quoting round AC_LANG_PROGRAM etc. so
291        as not to get warnings when autogen.sh is called. Also changed
292        AC_PROG_LIBTOOL (deprecated) to LT_INIT (the current macro).
294    44. To help people who use pcregrep to scan files containing exceedingly long
295        lines, the following changes have been made:
297        (a) The default value of the buffer size parameter has been increased from
298            8K to 20K. (The actual buffer used is three times this size.)
300        (b) The default can be changed by ./configure --with-pcregrep-bufsize when
301            PCRE is built.
303        (c) A --buffer-size=n option has been added to pcregrep, to allow the size
304            to be set at run time.
306        (d) Numerical values in pcregrep options can be followed by K or M, for
307            example --buffer-size=50K.
309        (e) If a line being scanned overflows pcregrep's buffer, an error is now
310            given and the return code is set to 2.
312    45. Add a pointer to the latest mark to the callout data block.
314    46. The pattern /.(*F)/, when applied to "abc" with PCRE_PARTIAL_HARD, gave a
315        partial match of an empty string instead of no match. This was specific to
316        the use of ".".
318    47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a
319        complete match instead of a partial match. This bug was dependent on both
320        the PCRE_UTF8 and PCRE_DOTALL options being set.
322    48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the
323        starting byte set, because \b was not being ignored.
326    Version 8.12 15-Jan-2011
327    ------------------------
329    1.  Fixed some typos in the markup of the man pages, and wrote a script that
330        checks for such things as part of the documentation building process.
332    2.  On a big-endian 64-bit system, pcregrep did not correctly process the
333        --match-limit and --recursion-limit options (added for 8.11). In
334        particular, this made one of the standard tests fail. (The integer value
335        went into the wrong half of a long int.)
337    3.  If the --colour option was given to pcregrep with -v (invert match), it
338        did strange things, either producing crazy output, or crashing. It should,
339        of course, ignore a request for colour when reporting lines that do not
340        match.
342    4.  Another pcregrep bug caused similar problems if --colour was specified with
343        -M (multiline) and the pattern match finished with a line ending.
345    5.  In pcregrep, when a pattern that ended with a literal newline sequence was
346        matched in multiline mode, the following line was shown as part of the
347        match. This seems wrong, so I have changed it.
349    6.  Another pcregrep bug in multiline mode, when --colour was specified, caused
350        the check for further matches in the same line (so they could be coloured)
351        to overrun the end of the current line. If another match was found, it was
352        incorrectly shown (and then shown again when found in the next line).
354    7.  If pcregrep was compiled under Windows, there was a reference to the
355        function pcregrep_exit() before it was defined. I am assuming this was
356        the cause of the "error C2371: 'pcregrep_exit' : redefinition;" that was
357        reported by a user. I've moved the definition above the reference.
360    Version 8.11 10-Dec-2010
361    ------------------------
363    1.  (*THEN) was not working properly if there were untried alternatives prior
364        to it in the current branch. For example, in ((a|b)(*THEN)(*F)|c..) it
365        backtracked to try for "b" instead of moving to the next alternative branch
366        at the same level (in this case, to look for "c"). The Perl documentation
367        is clear that when (*THEN) is backtracked onto, it goes to the "next
368        alternative in the innermost enclosing group".
370    2.  (*COMMIT) was not overriding (*THEN), as it does in Perl. In a pattern
371        such as   (A(*COMMIT)B(*THEN)C|D)  any failure after matching A should
372        result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and
373        (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides
374        (*THEN).
376    3.  If \s appeared in a character class, it removed the VT character from
377        the class, even if it had been included by some previous item, for example
378        in [\x00-\xff\s]. (This was a bug related to the fact that VT is not part
379        of \s, but is part of the POSIX "space" class.)
381    4.  A partial match never returns an empty string (because you can always
382        match an empty string at the end of the subject); however the checking for
383        an empty string was starting at the "start of match" point. This has been
384        changed to the "earliest inspected character" point, because the returned
385        data for a partial match starts at this character. This means that, for
386        example, /(?<=abc)def/ gives a partial match for the subject "abc"
387        (previously it gave "no match").
389    5.  Changes have been made to the way PCRE_PARTIAL_HARD affects the matching
390        of $, \z, \Z, \b, and \B. If the match point is at the end of the string,
391        previously a full match would be given. However, setting PCRE_PARTIAL_HARD
392        has an implication that the given string is incomplete (because a partial
393        match is preferred over a full match). For this reason, these items now
394        give a partial match in this situation. [Aside: previously, the one case
395        /t\b/ matched against "cat" with PCRE_PARTIAL_HARD set did return a partial
396        match rather than a full match, which was wrong by the old rules, but is
397        now correct.]
399    6.  There was a bug in the handling of #-introduced comments, recognized when
400        PCRE_EXTENDED is set, when PCRE_NEWLINE_ANY and PCRE_UTF8 were also set.
401        If a UTF-8 multi-byte character included the byte 0x85 (e.g. +U0445, whose
402        UTF-8 encoding is 0xd1,0x85), this was misinterpreted as a newline when
403        scanning for the end of the comment. (*Character* 0x85 is an "any" newline,
404        but *byte* 0x85 is not, in UTF-8 mode). This bug was present in several
405        places in pcre_compile().
407    7.  Related to (6) above, when pcre_compile() was skipping #-introduced
408        comments when looking ahead for named forward references to subpatterns,
409        the only newline sequence it recognized was NL. It now handles newlines
410        according to the set newline convention.
412    8.  SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the
413        former, but used strtoul(), whereas pcretest avoided strtoul() but did not
414        cater for a lack of strerror(). These oversights have been fixed.
416    9.  Added --match-limit and --recursion-limit to pcregrep.
418    10. Added two casts needed to build with Visual Studio when NO_RECURSE is set.
420    11. When the -o option was used, pcregrep was setting a return code of 1, even
421        when matches were found, and --line-buffered was not being honoured.
423    12. Added an optional parentheses number to the -o and --only-matching options
424        of pcregrep.
426    13. Imitating Perl's /g action for multiple matches is tricky when the pattern
427        can match an empty string. The code to do it in pcretest and pcredemo
428        needed fixing:
430        (a) When the newline convention was "crlf", pcretest got it wrong, skipping
431            only one byte after an empty string match just before CRLF (this case
432            just got forgotten; "any" and "anycrlf" were OK).
434        (b) The pcretest code also had a bug, causing it to loop forever in UTF-8
435            mode when an empty string match preceded an ASCII character followed by
436            a non-ASCII character. (The code for advancing by one character rather
437            than one byte was nonsense.)
439        (c) The pcredemo.c sample program did not have any code at all to handle
440            the cases when CRLF is a valid newline sequence.
442    14. Neither pcre_exec() nor pcre_dfa_exec() was checking that the value given
443        as a starting offset was within the subject string. There is now a new
444        error, PCRE_ERROR_BADOFFSET, which is returned if the starting offset is
445        negative or greater than the length of the string. In order to test this,
446        pcretest is extended to allow the setting of negative starting offsets.
448    15. In both pcre_exec() and pcre_dfa_exec() the code for checking that the
449        starting offset points to the beginning of a UTF-8 character was
450        unnecessarily clumsy. I tidied it up.
452    16. Added PCRE_ERROR_SHORTUTF8 to make it possible to distinguish between a
453        bad UTF-8 sequence and one that is incomplete when using PCRE_PARTIAL_HARD.
455    17. Nobody had reported that the --include_dir option, which was added in
456        release 7.7 should have been called --include-dir (hyphen, not underscore)
457        for compatibility with GNU grep. I have changed it to --include-dir, but
458        left --include_dir as an undocumented synonym, and the same for
459        --exclude-dir, though that is not available in GNU grep, at least as of
460        release 2.5.4.
462    18. At a user's suggestion, the macros GETCHAR and friends (which pick up UTF-8
463        characters from a string of bytes) have been redefined so as not to use
464        loops, in order to improve performance in some environments. At the same
465        time, I abstracted some of the common code into auxiliary macros to save
466        repetition (this should not affect the compiled code).
468    19. If \c was followed by a multibyte UTF-8 character, bad things happened. A
469        compile-time error is now given if \c is not followed by an ASCII
470        character, that is, a byte less than 128. (In EBCDIC mode, the code is
471        different, and any byte value is allowed.)
473    20. Recognize (*NO_START_OPT) at the start of a pattern to set the PCRE_NO_
474        START_OPTIMIZE option, which is now allowed at compile time - but just
475        passed through to pcre_exec() or pcre_dfa_exec(). This makes it available
476        to pcregrep and other applications that have no direct access to PCRE
477        options. The new /Y option in pcretest sets this option when calling
478        pcre_compile().
480    21. Change 18 of release 8.01 broke the use of named subpatterns for recursive
481        back references. Groups containing recursive back references were forced to
482        be atomic by that change, but in the case of named groups, the amount of
483        memory required was incorrectly computed, leading to "Failed: internal
484        error: code overflow". This has been fixed.
486    22. Some patches to pcre_stringpiece.h, pcre_stringpiece_unittest.cc, and
487        pcretest.c, to avoid build problems in some Borland environments.
490    Version 8.10 25-Jun-2010
491    ------------------------
493    1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and
494        THEN.
496    2.  (*ACCEPT) was not working when inside an atomic group.
498    3.  Inside a character class, \B is treated as a literal by default, but
499        faulted if PCRE_EXTRA is set. This mimics Perl's behaviour (the -w option
500        causes the error). The code is unchanged, but I tidied the documentation.
502    4.  Inside a character class, PCRE always treated \R and \X as literals,
503        whereas Perl faults them if its -w option is set. I have changed PCRE so
504        that it faults them when PCRE_EXTRA is set.
506    5.  Added support for \N, which always matches any character other than
507        newline. (It is the same as "." when PCRE_DOTALL is not set.)
509    6.  When compiling pcregrep with newer versions of gcc which may have
510        FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',
511        declared with attribute warn_unused_result" were given. Just casting the
512        result to (void) does not stop the warnings; a more elaborate fudge is
513        needed. I've used a macro to implement this.
515    7.  Minor change to pcretest.c to avoid a compiler warning.
517    8.  Added four artifical Unicode properties to help with an option to make
518        \s etc use properties (see next item). The new properties are: Xan
519        (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).
521    9.  Added PCRE_UCP to make \b, \d, \s, \w, and certain POSIX character classes
522        use Unicode properties. (*UCP) at the start of a pattern can be used to set
523        this option. Modified pcretest to add /W to test this facility. Added
524        REG_UCP to make it available via the POSIX interface.
526    10. Added --line-buffered to pcregrep.
528    11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was
529        studied, and the match started with a letter with a code point greater than
530        127 whose first byte was different to the first byte of the other case of
531        the letter, the other case of this starting letter was not recognized
532        (#976).
534    12. If a pattern that was studied started with a repeated Unicode property
535        test, for example, \p{Nd}+, there was the theoretical possibility of
536        setting up an incorrect bitmap of starting bytes, but fortunately it could
537        not have actually happened in practice until change 8 above was made (it
538        added property types that matched character-matching opcodes).
540    13. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
541        possible starting bytes for non-anchored patterns.
543    14. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes
544        \R, and also a number of cases that involve Unicode properties, both
545        explicit and implicit when PCRE_UCP is set.
547    15. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8
548        input, it could crash or give wrong results if characters with values
549        greater than 0xc0 were present in the subject string. (Detail: it assumed
550        UTF-8 input when processing these items.)
552    16. Added a lot of (int) casts to avoid compiler warnings in systems where
553        size_t is 64-bit (#991).
555    17. Added a check for running out of memory when PCRE is compiled with
556        --disable-stack-for-recursion (#990).
558    18. If the last data line in a file for pcretest does not have a newline on
559        the end, a newline was missing in the output.
561    19. The default pcre_chartables.c file recognizes only ASCII characters (values
562        less than 128) in its various bitmaps. However, there is a facility for
563        generating tables according to the current locale when PCRE is compiled. It
564        turns out that in some environments, 0x85 and 0xa0, which are Unicode space
565        characters, are recognized by isspace() and therefore were getting set in
566        these tables, and indeed these tables seem to approximate to ISO 8859. This
567        caused a problem in UTF-8 mode when pcre_study() was used to create a list
568        of bytes that can start a match. For \s, it was including 0x85 and 0xa0,
569        which of course cannot start UTF-8 characters. I have changed the code so
570        that only real ASCII characters (less than 128) and the correct starting
571        bytes for UTF-8 encodings are set for characters greater than 127 when in
572        UTF-8 mode. (When PCRE_UCP is set - see 9 above - the code is different
573        altogether.)
575    20. Added the /T option to pcretest so as to be able to run tests with non-
576        standard character tables, thus making it possible to include the tests
577        used for 19 above in the standard set of tests.
579    21. A pattern such as (?&t)(?#()(?(DEFINE)(?<t>a)) which has a forward
580        reference to a subpattern the other side of a comment that contains an
581        opening parenthesis caused either an internal compiling error, or a
582        reference to the wrong subpattern.
585    Version 8.02 19-Mar-2010
586    ------------------------
588    1.  The Unicode data tables have been updated to Unicode 5.2.0.
590    2.  Added the option --libs-cpp to pcre-config, but only when C++ support is
591        configured.
593    3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the
594        original author of that file, following a query about its status.
596    4.  On systems that do not have stdint.h (e.g. Solaris), check for and include
597        inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
599    5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
600        quantifier applied to a forward-referencing subroutine call, could compile
601        incorrect code or give the error "internal error: previously-checked
602        referenced subpattern not found".
604    6.  Both MS Visual Studio and Symbian OS have problems with initializing
605        variables to point to external functions. For these systems, therefore,
606        pcre_malloc etc. are now initialized to local functions that call the
607        relevant global functions.
609    7.  There were two entries missing in the vectors called coptable and poptable
610        in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.
611        I've fixed the data, and added a kludgy way of testing at compile time that
612        the lengths are correct (equal to the number of opcodes).
614    8.  Following on from 7, I added a similar kludge to check the length of the
615        eint vector in pcreposix.c.
617    9.  Error texts for pcre_compile() are held as one long string to avoid too
618        much relocation at load time. To find a text, the string is searched,
619        counting zeros. There was no check for running off the end of the string,
620        which could happen if a new error number was added without updating the
621        string.
623    10. \K gave a compile-time error if it appeared in a lookbehind assersion.
625    11. \K was not working if it appeared in an atomic group or in a group that
626        was called as a "subroutine", or in an assertion. Perl 5.11 documents that
627        \K is "not well defined" if used in an assertion. PCRE now accepts it if
628        the assertion is positive, but not if it is negative.
630    12. Change 11 fortuitously reduced the size of the stack frame used in the
631        "match()" function of pcre_exec.c by one pointer. Forthcoming
632        implementation of support for (*MARK) will need an extra pointer on the
633        stack; I have reserved it now, so that the stack frame size does not
634        decrease.
636    13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other
637        item in branch that calls a recursion is a subroutine call - as in the
638        second branch in the above example - was incorrectly given the compile-
639        time error "recursive call could loop indefinitely" because pcre_compile()
640        was not correctly checking the subroutine for matching a non-empty string.
642    14. The checks for overrunning compiling workspace could trigger after an
643        overrun had occurred. This is a "should never occur" error, but it can be
644        triggered by pathological patterns such as hundreds of nested parentheses.
645        The checks now trigger 100 bytes before the end of the workspace.
647    15. Fix typo in configure.ac: "srtoq" should be "strtoq".
650    Version 8.01 19-Jan-2010
651    ------------------------
653    1.  If a pattern contained a conditional subpattern with only one branch (in
654        particular, this includes all (*DEFINE) patterns), a call to pcre_study()
655        computed the wrong minimum data length (which is of course zero for such
656        subpatterns). This could cause incorrect "no match" results.
658    2.  For patterns such as (?i)a(?-i)b|c where an option setting at the start of
659        the pattern is reset in the first branch, pcre_compile() failed with
660        "internal error: code overflow at offset...". This happened only when
661        the reset was to the original external option setting. (An optimization
662        abstracts leading options settings into an external setting, which was the
663        cause of this.)
665    3.  A pattern such as ^(?!a(*SKIP)b) where a negative assertion contained one
666        of the verbs SKIP, PRUNE, or COMMIT, did not work correctly. When the
667        assertion pattern did not match (meaning that the assertion was true), it
668        was incorrectly treated as false if the SKIP had been reached during the
669        matching. This also applied to assertions used as conditions.
671    4.  If an item that is not supported by pcre_dfa_exec() was encountered in an
672        assertion subpattern, including such a pattern used as a condition,
673        unpredictable results occurred, instead of the error return
676    5.  The C++ GlobalReplace function was not working like Perl for the special
677        situation when an empty string is matched. It now does the fancy magic
678        stuff that is necessary.
680    6.  In pcre_internal.h, obsolete includes to setjmp.h and stdarg.h have been
681        removed. (These were left over from very, very early versions of PCRE.)
683    7.  Some cosmetic changes to the code to make life easier when compiling it
684        as part of something else:
686        (a) Change DEBUG to PCRE_DEBUG.
688        (b) In pcre_compile(), rename the member of the "branch_chain" structure
689            called "current" as "current_branch", to prevent a collision with the
690            Linux macro when compiled as a kernel module.
692        (c) In pcre_study(), rename the function set_bit() as set_table_bit(), to
693            prevent a collision with the Linux macro when compiled as a kernel
694            module.
696    8.  In pcre_compile() there are some checks for integer overflows that used to
697        cast potentially large values to (double). This has been changed to that
698        when building, a check for int64_t is made, and if it is found, it is used
699        instead, thus avoiding the use of floating point arithmetic. (There is no
700        other use of FP in PCRE.) If int64_t is not found, the fallback is to
701        double.
703    9.  Added two casts to avoid signed/unsigned warnings from VS Studio Express
704        2005 (difference between two addresses compared to an unsigned value).
706    10. Change the standard AC_CHECK_LIB test for libbz2 in configure.ac to a
707        custom one, because of the following reported problem in Windows:
709          - libbz2 uses the Pascal calling convention (WINAPI) for the functions
710              under Win32.
711          - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",
712              therefore missing the function definition.
713          - The compiler thus generates a "C" signature for the test function.
714          - The linker fails to find the "C" function.
715          - PCRE fails to configure if asked to do so against libbz2.
717    11. When running libtoolize from libtool-2.2.6b as part of autogen.sh, these
718        messages were output:
720          Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
721          rerunning libtoolize, to keep the correct libtool macros in-tree.
722          Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
724        I have done both of these things.
726    12. Although pcre_dfa_exec() does not use nearly as much stack as pcre_exec()
727        most of the time, it *can* run out if it is given a pattern that contains a
728        runaway infinite recursion. I updated the discussion in the pcrestack man
729        page.
731    13. Now that we have gone to the x.xx style of version numbers, the minor
732        version may start with zero. Using 08 or 09 is a bad idea because users
733        might check the value of PCRE_MINOR in their code, and 08 or 09 may be
734        interpreted as invalid octal numbers. I've updated the previous comment in
735        configure.ac, and also added a check that gives an error if 08 or 09 are
736        used.
738    14. Change 8.00/11 was not quite complete: code had been accidentally omitted,
739        causing partial matching to fail when the end of the subject matched \W
740        in a UTF-8 pattern where \W was quantified with a minimum of 3.
742    15. There were some discrepancies between the declarations in pcre_internal.h
743        of _pcre_is_newline(), _pcre_was_newline(), and _pcre_valid_utf8() and
744        their definitions. The declarations used "const uschar *" and the
745        definitions used USPTR. Even though USPTR is normally defined as "const
746        unsigned char *" (and uschar is typedeffed as "unsigned char"), it was
747        reported that: "This difference in casting confuses some C++ compilers, for
748        example, SunCC recognizes above declarations as different functions and
749        generates broken code for hbpcre." I have changed the declarations to use
750        USPTR.
752    16. GNU libtool is named differently on some systems. The autogen.sh script now
753        tries several variants such as glibtoolize (MacOSX) and libtoolize1x
754        (FreeBSD).
756    17. Applied Craig's patch that fixes an HP aCC compile error in pcre 8.00
757        (strtoXX undefined when compiling pcrecpp.cc). The patch contains this
758        comment: "Figure out how to create a longlong from a string: strtoll and
759        equivalent. It's not enough to call AC_CHECK_FUNCS: hpux has a strtoll, for
760        instance, but it only takes 2 args instead of 3!"
762    18. A subtle bug concerned with back references has been fixed by a change of
763        specification, with a corresponding code fix. A pattern such as
764        ^(xa|=?\1a)+$ which contains a back reference inside the group to which it
765        refers, was giving matches when it shouldn't. For example, xa=xaaa would
766        match that pattern. Interestingly, Perl (at least up to 5.11.3) has the
767        same bug. Such groups have to be quantified to be useful, or contained
768        inside another quantified group. (If there's no repetition, the reference
769        can never match.) The problem arises because, having left the group and
770        moved on to the rest of the pattern, a later failure that backtracks into
771        the group uses the captured value from the final iteration of the group
772        rather than the correct earlier one. I have fixed this in PCRE by forcing
773        any group that contains a reference to itself to be an atomic group; that
774        is, there cannot be any backtracking into it once it has completed. This is
775        similar to recursive and subroutine calls.
778    Version 8.00 19-Oct-09
779  ----------------------  ----------------------
781  1.  The table for translating pcre_compile() error codes into POSIX error codes  1.  The table for translating pcre_compile() error codes into POSIX error codes
782      was out-of-date, and there was no check on the pcre_compile() error code      was out-of-date, and there was no check on the pcre_compile() error code
783      being within the table. This could lead to an OK return being given in      being within the table. This could lead to an OK return being given in
784      error.      error.
786  2.  Changed the call to open a subject file in pcregrep from fopen(pathname,  2.  Changed the call to open a subject file in pcregrep from fopen(pathname,
787      "r") to fopen(pathname, "rb"), which fixed a problem with some of the tests      "r") to fopen(pathname, "rb"), which fixed a problem with some of the tests
788      in a Windows environment.      in a Windows environment.
790  3.  The pcregrep --count option prints the count for each file even when it is  3.  The pcregrep --count option prints the count for each file even when it is
791      zero, as does GNU grep. However, pcregrep was also printing all files when      zero, as does GNU grep. However, pcregrep was also printing all files when
792      --files-with-matches was added. Now, when both options are given, it prints      --files-with-matches was added. Now, when both options are given, it prints
793      counts only for those files that have at least one match. (GNU grep just      counts only for those files that have at least one match. (GNU grep just
794      prints the file name in this circumstance, but including the count seems      prints the file name in this circumstance, but including the count seems
795      more useful - otherwise, why use --count?) Also ensured that the      more useful - otherwise, why use --count?) Also ensured that the
796      combination -clh just lists non-zero counts, with no names.      combination -clh just lists non-zero counts, with no names.
798  4.  The long form of the pcregrep -F option was incorrectly implemented as  4.  The long form of the pcregrep -F option was incorrectly implemented as
799      --fixed_strings instead of --fixed-strings. This is an incompatible change,      --fixed_strings instead of --fixed-strings. This is an incompatible change,
800      but it seems right to fix it, and I didn't think it was worth preserving      but it seems right to fix it, and I didn't think it was worth preserving
801      the old behaviour.      the old behaviour.
803  5.  The command line items --regex=pattern and --regexp=pattern were not  5.  The command line items --regex=pattern and --regexp=pattern were not
804      recognized by pcregrep, which required --regex pattern or --regexp pattern      recognized by pcregrep, which required --regex pattern or --regexp pattern
805      (with a space rather than an '='). The man page documented the '=' forms,      (with a space rather than an '='). The man page documented the '=' forms,
806      which are compatible with GNU grep; these now work.      which are compatible with GNU grep; these now work.
808    6.  No libpcreposix.pc file was created for pkg-config; there was just
809        libpcre.pc and libpcrecpp.pc. The omission has been rectified.
811    7.  Added #ifndef SUPPORT_UCP into the pcre_ucd.c module, to reduce its size
812        when UCP support is not needed, by modifying the Python script that
813        generates it from Unicode data files. This should not matter if the module
814        is correctly used as a library, but I received one complaint about 50K of
815        unwanted data. My guess is that the person linked everything into his
816        program rather than using a library. Anyway, it does no harm.
818    8.  A pattern such as /\x{123}{2,2}+/8 was incorrectly compiled; the trigger
819        was a minimum greater than 1 for a wide character in a possessive
820        repetition. The same bug could also affect patterns like /(\x{ff}{0,2})*/8
821        which had an unlimited repeat of a nested, fixed maximum repeat of a wide
822        character. Chaos in the form of incorrect output or a compiling loop could
823        result.
825    9.  The restrictions on what a pattern can contain when partial matching is
826        requested for pcre_exec() have been removed. All patterns can now be
827        partially matched by this function. In addition, if there are at least two
828        slots in the offset vector, the offset of the earliest inspected character
829        for the match and the offset of the end of the subject are set in them when
830        PCRE_ERROR_PARTIAL is returned.
832    10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is
833        synonymous with PCRE_PARTIAL, for backwards compatibility, and
834        PCRE_PARTIAL_HARD, which causes a partial match to supersede a full match,
835        and may be more useful for multi-segment matching.
837    11. Partial matching with pcre_exec() is now more intuitive. A partial match
838        used to be given if ever the end of the subject was reached; now it is
839        given only if matching could not proceed because another character was
840        needed. This makes a difference in some odd cases such as Z(*FAIL) with the
841        string "Z", which now yields "no match" instead of "partial match". In the
842        case of pcre_dfa_exec(), "no match" is given if every matching path for the
843        final character ended with (*FAIL).
845    12. Restarting a match using pcre_dfa_exec() after a partial match did not work
846        if the pattern had a "must contain" character that was already found in the
847        earlier partial match, unless partial matching was again requested. For
848        example, with the pattern /dog.(body)?/, the "must contain" character is
849        "g". If the first part-match was for the string "dog", restarting with
850        "sbody" failed. This bug has been fixed.
852    13. The string returned by pcre_dfa_exec() after a partial match has been
853        changed so that it starts at the first inspected character rather than the
854        first character of the match. This makes a difference only if the pattern
855        starts with a lookbehind assertion or \b or \B (\K is not supported by
856        pcre_dfa_exec()). It's an incompatible change, but it makes the two
857        matching functions compatible, and I think it's the right thing to do.
859    14. Added a pcredemo man page, created automatically from the pcredemo.c file,
860        so that the demonstration program is easily available in environments where
861        PCRE has not been installed from source.
863    15. Arranged to add -DPCRE_STATIC to cflags in libpcre.pc, libpcreposix.cp,
864        libpcrecpp.pc and pcre-config when PCRE is not compiled as a shared
865        library.
867    16. Added REG_UNGREEDY to the pcreposix interface, at the request of a user.
868        It maps to PCRE_UNGREEDY. It is not, of course, POSIX-compatible, but it
869        is not the first non-POSIX option to be added. Clearly some people find
870        these options useful.
872    17. If a caller to the POSIX matching function regexec() passes a non-zero
873        value for nmatch with a NULL value for pmatch, the value of
874        nmatch is forced to zero.
876    18. RunGrepTest did not have a test for the availability of the -u option of
877        the diff command, as RunTest does. It now checks in the same way as
878        RunTest, and also checks for the -b option.
880    19. If an odd number of negated classes containing just a single character
881        interposed, within parentheses, between a forward reference to a named
882        subpattern and the definition of the subpattern, compilation crashed with
883        an internal error, complaining that it could not find the referenced
884        subpattern. An example of a crashing pattern is /(?&A)(([^m])(?<A>))/.
885        [The bug was that it was starting one character too far in when skipping
886        over the character class, thus treating the ] as data rather than
887        terminating the class. This meant it could skip too much.]
889    20. Added PCRE_NOTEMPTY_ATSTART in order to be able to correctly implement the
890        /g option in pcretest when the pattern contains \K, which makes it possible
891        to have an empty string match not at the start, even when the pattern is
892        anchored. Updated pcretest and pcredemo to use this option.
894    21. If the maximum number of capturing subpatterns in a recursion was greater
895        than the maximum at the outer level, the higher number was returned, but
896        with unset values at the outer level. The correct (outer level) value is
897        now given.
899    22. If (*ACCEPT) appeared inside capturing parentheses, previous releases of
900        PCRE did not set those parentheses (unlike Perl). I have now found a way to
901        make it do so. The string so far is captured, making this feature
902        compatible with Perl.
904    23. The tests have been re-organized, adding tests 11 and 12, to make it
905        possible to check the Perl 5.10 features against Perl 5.10.
907    24. Perl 5.10 allows subroutine calls in lookbehinds, as long as the subroutine
908        pattern matches a fixed length string. PCRE did not allow this; now it
909        does. Neither allows recursion.
911    25. I finally figured out how to implement a request to provide the minimum
912        length of subject string that was needed in order to match a given pattern.
913        (It was back references and recursion that I had previously got hung up
914        on.) This code has now been added to pcre_study(); it finds a lower bound
915        to the length of subject needed. It is not necessarily the greatest lower
916        bound, but using it to avoid searching strings that are too short does give
917        some useful speed-ups. The value is available to calling programs via
918        pcre_fullinfo().
920    26. While implementing 25, I discovered to my embarrassment that pcretest had
921        not been passing the result of pcre_study() to pcre_dfa_exec(), so the
922        study optimizations had never been tested with that matching function.
923        Oops. What is worse, even when it was passed study data, there was a bug in
924        pcre_dfa_exec() that meant it never actually used it. Double oops. There
925        were also very few tests of studied patterns with pcre_dfa_exec().
927    27. If (?| is used to create subpatterns with duplicate numbers, they are now
928        allowed to have the same name, even if PCRE_DUPNAMES is not set. However,
929        on the other side of the coin, they are no longer allowed to have different
930        names, because these cannot be distinguished in PCRE, and this has caused
931        confusion. (This is a difference from Perl.)
933    28. When duplicate subpattern names are present (necessarily with different
934        numbers, as required by 27 above), and a test is made by name in a
935        conditional pattern, either for a subpattern having been matched, or for
936        recursion in such a pattern, all the associated numbered subpatterns are
937        tested, and the overall condition is true if the condition is true for any
938        one of them. This is the way Perl works, and is also more like the way
939        testing by number works.
942  Version 7.9 11-Apr-09  Version 7.9 11-Apr-09
943  ---------------------  ---------------------

Removed from v.422  
changed lines
  Added in v.712

  ViewVC Help
Powered by ViewVC 1.1.5