ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 287 by ph10, Tue Dec 18 20:11:28 2007 UTC revision 740 by zherczeg, Mon Oct 31 06:10:14 2011 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 7.5 12-Nov-07  Version 8.21
5    ------------
7    1.  Updating the JIT compiler.
10    Version 8.20 21-Oct-2011
11    ------------------------
13    1.  Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had
14        a POSIX class. After further experiments with Perl, which convinced me that
15        Perl has bugs and confusions, a closing square bracket is no longer allowed
16        in a POSIX name. This bug also affected patterns with classes that started
17        with full stops.
19    2.  If a pattern such as /(a)b|ac/ is matched against "ac", there is no
20        captured substring, but while checking the failing first alternative,
21        substring 1 is temporarily captured. If the output vector supplied to
22        pcre_exec() was not big enough for this capture, the yield of the function
23        was still zero ("insufficient space for captured substrings"). This cannot
24        be totally fixed without adding another stack variable, which seems a lot
25        of expense for a edge case. However, I have improved the situation in cases
26        such as /(a)(b)x|abc/ matched against "abc", where the return code
27        indicates that fewer than the maximum number of slots in the ovector have
28        been set.
30    3.  Related to (2) above: when there are more back references in a pattern than
31        slots in the output vector, pcre_exec() uses temporary memory during
32        matching, and copies in the captures as far as possible afterwards. It was
33        using the entire output vector, but this conflicts with the specification
34        that only 2/3 is used for passing back captured substrings. Now it uses
35        only the first 2/3, for compatibility. This is, of course, another edge
36        case.
38    4.  Zoltan Herczeg's just-in-time compiler support has been integrated into the
39        main code base, and can be used by building with --enable-jit. When this is
40        done, pcregrep automatically uses it unless --disable-pcregrep-jit or the
41        runtime --no-jit option is given.
43    5.  When the number of matches in a pcre_dfa_exec() run exactly filled the
44        ovector, the return from the function was zero, implying that there were
45        other matches that did not fit. The correct "exactly full" value is now
46        returned.
48    6.  If a subpattern that was called recursively or as a subroutine contained
49        (*PRUNE) or any other control that caused it to give a non-standard return,
50        invalid errors such as "Error -26 (nested recursion at the same subject
51        position)" or even infinite loops could occur.
53    7.  If a pattern such as /a(*SKIP)c|b(*ACCEPT)|/ was studied, it stopped
54        computing the minimum length on reaching *ACCEPT, and so ended up with the
55        wrong value of 1 rather than 0. Further investigation indicates that
56        computing a minimum subject length in the presence of *ACCEPT is difficult
57        (think back references, subroutine calls), and so I have changed the code
58        so that no minimum is registered for a pattern that contains *ACCEPT.
60    8.  If (*THEN) was present in the first (true) branch of a conditional group,
61        it was not handled as intended. [But see 16 below.]
63    9.  Replaced RunTest.bat and CMakeLists.txt with improved versions provided by
64        Sheri Pierce.
66    10. A pathological pattern such as /(*ACCEPT)a/ was miscompiled, thinking that
67        the first byte in a match must be "a".
69    11. Change 17 for 8.13 increased the recursion depth for patterns like
70        /a(?:.)*?a/ drastically. I've improved things by remembering whether a
71        pattern contains any instances of (*THEN). If it does not, the old
72        optimizations are restored. It would be nice to do this on a per-group
73        basis, but at the moment that is not feasible.
75    12. In some environments, the output of pcretest -C is CRLF terminated. This
76        broke RunTest's code that checks for the link size. A single white space
77        character after the value is now allowed for.
79    13. RunTest now checks for the "fr" locale as well as for "fr_FR" and "french".
80        For "fr", it uses the Windows-specific input and output files.
82    14. If (*THEN) appeared in a group that was called recursively or as a
83        subroutine, it did not work as intended. [But see next item.]
85    15. Consider the pattern /A (B(*THEN)C) | D/ where A, B, C, and D are complex
86        pattern fragments (but not containing any | characters). If A and B are
87        matched, but there is a failure in C so that it backtracks to (*THEN), PCRE
88        was behaving differently to Perl. PCRE backtracked into A, but Perl goes to
89        D. In other words, Perl considers parentheses that do not contain any |
90        characters to be part of a surrounding alternative, whereas PCRE was
91        treading (B(*THEN)C) the same as (B(*THEN)C|(*FAIL)) -- which Perl handles
92        differently. PCRE now behaves in the same way as Perl, except in the case
93        of subroutine/recursion calls such as (?1) which have in any case always
94        been different (but PCRE had them first :-).
96    16. Related to 15 above: Perl does not treat the | in a conditional group as
97        creating alternatives. Such a group is treated in the same way as an
98        ordinary group without any | characters when processing (*THEN). PCRE has
99        been changed to match Perl's behaviour.
101    17. If a user had set PCREGREP_COLO(U)R to something other than 1:31, the
102        RunGrepTest script failed.
104    18. Change 22 for version 13 caused atomic groups to use more stack. This is
105        inevitable for groups that contain captures, but it can lead to a lot of
106        stack use in large patterns. The old behaviour has been restored for atomic
107        groups that do not contain any capturing parentheses.
109    19. If the PCRE_NO_START_OPTIMIZE option was set for pcre_compile(), it did not
110        suppress the check for a minimum subject length at run time. (If it was
111        given to pcre_exec() or pcre_dfa_exec() it did work.)
113    20. Fixed an ASCII-dependent infelicity in pcretest that would have made it
114        fail to work when decoding hex characters in data strings in EBCDIC
115        environments.
117    21. It appears that in at least one Mac OS environment, the isxdigit() function
118        is implemented as a macro that evaluates to its argument more than once,
119        contravening the C 90 Standard (I haven't checked a later standard). There
120        was an instance in pcretest which caused it to go wrong when processing
121        \x{...} escapes in subject strings. The has been rewritten to avoid using
122        things like p++ in the argument of isxdigit().
125    Version 8.13 16-Aug-2011
126    ------------------------
128    1.  The Unicode data tables have been updated to Unicode 6.0.0.
130    2.  Two minor typos in pcre_internal.h have been fixed.
132    3.  Added #include <string.h> to pcre_scanner_unittest.cc, pcrecpp.cc, and
133        pcrecpp_unittest.cc. They are needed for strcmp(), memset(), and strchr()
134        in some environments (e.g. Solaris 10/SPARC using Sun Studio 12U2).
136    4.  There were a number of related bugs in the code for matching backrefences
137        caselessly in UTF-8 mode when codes for the characters concerned were
138        different numbers of bytes. For example, U+023A and U+2C65 are an upper
139        and lower case pair, using 2 and 3 bytes, respectively. The main bugs were:
140        (a) A reference to 3 copies of a 2-byte code matched only 2 of a 3-byte
141        code. (b) A reference to 2 copies of a 3-byte code would not match 2 of a
142        2-byte code at the end of the subject (it thought there wasn't enough data
143        left).
145    5.  Comprehensive information about what went wrong is now returned by
146        pcre_exec() and pcre_dfa_exec() when the UTF-8 string check fails, as long
147        as the output vector has at least 2 elements. The offset of the start of
148        the failing character and a reason code are placed in the vector.
150    6.  When the UTF-8 string check fails for pcre_compile(), the offset that is
151        now returned is for the first byte of the failing character, instead of the
152        last byte inspected. This is an incompatible change, but I hope it is small
153        enough not to be a problem. It makes the returned offset consistent with
154        pcre_exec() and pcre_dfa_exec().
156    7.  pcretest now gives a text phrase as well as the error number when
157        pcre_exec() or pcre_dfa_exec() fails; if the error is a UTF-8 check
158        failure, the offset and reason code are output.
160    8.  When \R was used with a maximizing quantifier it failed to skip backwards
161        over a \r\n pair if the subsequent match failed. Instead, it just skipped
162        back over a single character (\n). This seems wrong (because it treated the
163        two characters as a single entity when going forwards), conflicts with the
164        documentation that \R is equivalent to (?>\r\n|\n|...etc), and makes the
165        behaviour of \R* different to (\R)*, which also seems wrong. The behaviour
166        has been changed.
168    9.  Some internal refactoring has changed the processing so that the handling
169        of the PCRE_CASELESS and PCRE_MULTILINE options is done entirely at compile
170        time (the PCRE_DOTALL option was changed this way some time ago: version
171        7.7 change 16). This has made it possible to abolish the OP_OPT op code,
172        which was always a bit of a fudge. It also means that there is one less
173        argument for the match() function, which reduces its stack requirements
174        slightly. This change also fixes an incompatibility with Perl: the pattern
175        (?i:([^b]))(?1) should not match "ab", but previously PCRE gave a match.
177    10. More internal refactoring has drastically reduced the number of recursive
178        calls to match() for possessively repeated groups such as (abc)++ when
179        using pcre_exec().
181    11. While implementing 10, a number of bugs in the handling of groups were
182        discovered and fixed:
184        (?<=(a)+) was not diagnosed as invalid (non-fixed-length lookbehind).
185        (a|)*(?1) gave a compile-time internal error.
186        ((a|)+)+  did not notice that the outer group could match an empty string.
187        (^a|^)+   was not marked as anchored.
188        (.*a|.*)+ was not marked as matching at start or after a newline.
190    12. Yet more internal refactoring has removed another argument from the match()
191        function. Special calls to this function are now indicated by setting a
192        value in a variable in the "match data" data block.
194    13. Be more explicit in pcre_study() instead of relying on "default" for
195        opcodes that mean there is no starting character; this means that when new
196        ones are added and accidentally left out of pcre_study(), testing should
197        pick them up.
199    14. The -s option of pcretest has been documented for ages as being an old
200        synonym of -m (show memory usage). I have changed it to mean "force study
201        for every regex", that is, assume /S for every regex. This is similar to -i
202        and -d etc. It's slightly incompatible, but I'm hoping nobody is still
203        using it. It makes it easier to run collections of tests with and without
204        study enabled, and thereby test pcre_study() more easily. All the standard
205        tests are now run with and without -s (but some patterns can be marked as
206        "never study" - see 20 below).
208    15. When (*ACCEPT) was used in a subpattern that was called recursively, the
209        restoration of the capturing data to the outer values was not happening
210        correctly.
212    16. If a recursively called subpattern ended with (*ACCEPT) and matched an
213        empty string, and PCRE_NOTEMPTY was set, pcre_exec() thought the whole
214        pattern had matched an empty string, and so incorrectly returned a no
215        match.
217    17. There was optimizing code for the last branch of non-capturing parentheses,
218        and also for the obeyed branch of a conditional subexpression, which used
219        tail recursion to cut down on stack usage. Unfortunately, now that there is
220        the possibility of (*THEN) occurring in these branches, tail recursion is
221        no longer possible because the return has to be checked for (*THEN). These
222        two optimizations have therefore been removed. [But see 8.20/11 above.]
224    18. If a pattern containing \R was studied, it was assumed that \R always
225        matched two bytes, thus causing the minimum subject length to be
226        incorrectly computed because \R can also match just one byte.
228    19. If a pattern containing (*ACCEPT) was studied, the minimum subject length
229        was incorrectly computed.
231    20. If /S is present twice on a test pattern in pcretest input, it now
232        *disables* studying, thereby overriding the use of -s on the command line
233        (see 14 above). This is necessary for one or two tests to keep the output
234        identical in both cases.
236    21. When (*ACCEPT) was used in an assertion that matched an empty string and
237        PCRE_NOTEMPTY was set, PCRE applied the non-empty test to the assertion.
239    22. When an atomic group that contained a capturing parenthesis was
240        successfully matched, but the branch in which it appeared failed, the
241        capturing was not being forgotten if a higher numbered group was later
242        captured. For example, /(?>(a))b|(a)c/ when matching "ac" set capturing
243        group 1 to "a", when in fact it should be unset. This applied to multi-
244        branched capturing and non-capturing groups, repeated or not, and also to
245        positive assertions (capturing in negative assertions does not happen
246        in PCRE) and also to nested atomic groups.
248    23. Add the ++ qualifier feature to pcretest, to show the remainder of the
249        subject after a captured substring, to make it easier to tell which of a
250        number of identical substrings has been captured.
252    24. The way atomic groups are processed by pcre_exec() has been changed so that
253        if they are repeated, backtracking one repetition now resets captured
254        values correctly. For example, if ((?>(a+)b)+aabab) is matched against
255        "aaaabaaabaabab" the value of captured group 2 is now correctly recorded as
256        "aaa". Previously, it would have been "a". As part of this code
257        refactoring, the way recursive calls are handled has also been changed.
259    25. If an assertion condition captured any substrings, they were not passed
260        back unless some other capturing happened later. For example, if
261        (?(?=(a))a) was matched against "a", no capturing was returned.
263    26. When studying a pattern that contained subroutine calls or assertions,
264        the code for finding the minimum length of a possible match was handling
265        direct recursions such as (xxx(?1)|yyy) but not mutual recursions (where
266        group 1 called group 2 while simultaneously a separate group 2 called group
267        1). A stack overflow occurred in this case. I have fixed this by limiting
268        the recursion depth to 10.
270    27. Updated RunTest.bat in the distribution to the version supplied by Tom
271        Fortmann. This supports explicit test numbers on the command line, and has
272        argument validation and error reporting.
274    28. An instance of \X with an unlimited repeat could fail if at any point the
275        first character it looked at was a mark character.
277    29. Some minor code refactoring concerning Unicode properties and scripts
278        should reduce the stack requirement of match() slightly.
280    30. Added the '=' option to pcretest to check the setting of unused capturing
281        slots at the end of the pattern, which are documented as being -1, but are
282        not included in the return count.
284    31. If \k was not followed by a braced, angle-bracketed, or quoted name, PCRE
285        compiled something random. Now it gives a compile-time error (as does
286        Perl).
288    32. A *MARK encountered during the processing of a positive assertion is now
289        recorded and passed back (compatible with Perl).
291    33. If --only-matching or --colour was set on a pcregrep call whose pattern
292        had alternative anchored branches, the search for a second match in a line
293        was done as if at the line start. Thus, for example, /^01|^02/ incorrectly
294        matched the line "0102" twice. The same bug affected patterns that started
295        with a backwards assertion. For example /\b01|\b02/ also matched "0102"
296        twice.
298    34. Previously, PCRE did not allow quantification of assertions. However, Perl
299        does, and because of capturing effects, quantifying parenthesized
300        assertions may at times be useful. Quantifiers are now allowed for
301        parenthesized assertions.
303    35. A minor code tidy in pcre_compile() when checking options for \R usage.
305    36. \g was being checked for fancy things in a character class, when it should
306        just be a literal "g".
308    37. PCRE was rejecting [:a[:digit:]] whereas Perl was not. It seems that the
309        appearance of a nested POSIX class supersedes an apparent external class.
310        For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,
311        unescaped square brackets may also appear as part of class names. For
312        example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves
313        more like Perl. (But see 8.20/1 above.)
315    38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this
316        was because it thought it was \N{name}, which is not supported).
318    39. Add minix to OS list not supporting the -S option in pcretest.
320    40. PCRE tries to detect cases of infinite recursion at compile time, but it
321        cannot analyze patterns in sufficient detail to catch mutual recursions
322        such as ((?1))((?2)). There is now a runtime test that gives an error if a
323        subgroup is called recursively as a subpattern for a second time at the
324        same position in the subject string. In previous releases this might have
325        been caught by the recursion limit, or it might have run out of stack.
327    41. A pattern such as /(?(R)a+|(?R)b)/ is quite safe, as the recursion can
328        happen only once. PCRE was, however incorrectly giving a compile time error
329        "recursive call could loop indefinitely" because it cannot analyze the
330        pattern in sufficient detail. The compile time test no longer happens when
331        PCRE is compiling a conditional subpattern, but actual runaway loops are
332        now caught at runtime (see 40 above).
334    42. It seems that Perl allows any characters other than a closing parenthesis
335        to be part of the NAME in (*MARK:NAME) and other backtracking verbs. PCRE
336        has been changed to be the same.
338    43. Updated configure.ac to put in more quoting round AC_LANG_PROGRAM etc. so
339        as not to get warnings when autogen.sh is called. Also changed
340        AC_PROG_LIBTOOL (deprecated) to LT_INIT (the current macro).
342    44. To help people who use pcregrep to scan files containing exceedingly long
343        lines, the following changes have been made:
345        (a) The default value of the buffer size parameter has been increased from
346            8K to 20K. (The actual buffer used is three times this size.)
348        (b) The default can be changed by ./configure --with-pcregrep-bufsize when
349            PCRE is built.
351        (c) A --buffer-size=n option has been added to pcregrep, to allow the size
352            to be set at run time.
354        (d) Numerical values in pcregrep options can be followed by K or M, for
355            example --buffer-size=50K.
357        (e) If a line being scanned overflows pcregrep's buffer, an error is now
358            given and the return code is set to 2.
360    45. Add a pointer to the latest mark to the callout data block.
362    46. The pattern /.(*F)/, when applied to "abc" with PCRE_PARTIAL_HARD, gave a
363        partial match of an empty string instead of no match. This was specific to
364        the use of ".".
366    47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a
367        complete match instead of a partial match. This bug was dependent on both
368        the PCRE_UTF8 and PCRE_DOTALL options being set.
370    48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the
371        starting byte set, because \b was not being ignored.
374    Version 8.12 15-Jan-2011
375    ------------------------
377    1.  Fixed some typos in the markup of the man pages, and wrote a script that
378        checks for such things as part of the documentation building process.
380    2.  On a big-endian 64-bit system, pcregrep did not correctly process the
381        --match-limit and --recursion-limit options (added for 8.11). In
382        particular, this made one of the standard tests fail. (The integer value
383        went into the wrong half of a long int.)
385    3.  If the --colour option was given to pcregrep with -v (invert match), it
386        did strange things, either producing crazy output, or crashing. It should,
387        of course, ignore a request for colour when reporting lines that do not
388        match.
390    4.  Another pcregrep bug caused similar problems if --colour was specified with
391        -M (multiline) and the pattern match finished with a line ending.
393    5.  In pcregrep, when a pattern that ended with a literal newline sequence was
394        matched in multiline mode, the following line was shown as part of the
395        match. This seems wrong, so I have changed it.
397    6.  Another pcregrep bug in multiline mode, when --colour was specified, caused
398        the check for further matches in the same line (so they could be coloured)
399        to overrun the end of the current line. If another match was found, it was
400        incorrectly shown (and then shown again when found in the next line).
402    7.  If pcregrep was compiled under Windows, there was a reference to the
403        function pcregrep_exit() before it was defined. I am assuming this was
404        the cause of the "error C2371: 'pcregrep_exit' : redefinition;" that was
405        reported by a user. I've moved the definition above the reference.
408    Version 8.11 10-Dec-2010
409    ------------------------
411    1.  (*THEN) was not working properly if there were untried alternatives prior
412        to it in the current branch. For example, in ((a|b)(*THEN)(*F)|c..) it
413        backtracked to try for "b" instead of moving to the next alternative branch
414        at the same level (in this case, to look for "c"). The Perl documentation
415        is clear that when (*THEN) is backtracked onto, it goes to the "next
416        alternative in the innermost enclosing group".
418    2.  (*COMMIT) was not overriding (*THEN), as it does in Perl. In a pattern
419        such as   (A(*COMMIT)B(*THEN)C|D)  any failure after matching A should
420        result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and
421        (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides
422        (*THEN).
424    3.  If \s appeared in a character class, it removed the VT character from
425        the class, even if it had been included by some previous item, for example
426        in [\x00-\xff\s]. (This was a bug related to the fact that VT is not part
427        of \s, but is part of the POSIX "space" class.)
429    4.  A partial match never returns an empty string (because you can always
430        match an empty string at the end of the subject); however the checking for
431        an empty string was starting at the "start of match" point. This has been
432        changed to the "earliest inspected character" point, because the returned
433        data for a partial match starts at this character. This means that, for
434        example, /(?<=abc)def/ gives a partial match for the subject "abc"
435        (previously it gave "no match").
437    5.  Changes have been made to the way PCRE_PARTIAL_HARD affects the matching
438        of $, \z, \Z, \b, and \B. If the match point is at the end of the string,
439        previously a full match would be given. However, setting PCRE_PARTIAL_HARD
440        has an implication that the given string is incomplete (because a partial
441        match is preferred over a full match). For this reason, these items now
442        give a partial match in this situation. [Aside: previously, the one case
443        /t\b/ matched against "cat" with PCRE_PARTIAL_HARD set did return a partial
444        match rather than a full match, which was wrong by the old rules, but is
445        now correct.]
447    6.  There was a bug in the handling of #-introduced comments, recognized when
448        PCRE_EXTENDED is set, when PCRE_NEWLINE_ANY and PCRE_UTF8 were also set.
449        If a UTF-8 multi-byte character included the byte 0x85 (e.g. +U0445, whose
450        UTF-8 encoding is 0xd1,0x85), this was misinterpreted as a newline when
451        scanning for the end of the comment. (*Character* 0x85 is an "any" newline,
452        but *byte* 0x85 is not, in UTF-8 mode). This bug was present in several
453        places in pcre_compile().
455    7.  Related to (6) above, when pcre_compile() was skipping #-introduced
456        comments when looking ahead for named forward references to subpatterns,
457        the only newline sequence it recognized was NL. It now handles newlines
458        according to the set newline convention.
460    8.  SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the
461        former, but used strtoul(), whereas pcretest avoided strtoul() but did not
462        cater for a lack of strerror(). These oversights have been fixed.
464    9.  Added --match-limit and --recursion-limit to pcregrep.
466    10. Added two casts needed to build with Visual Studio when NO_RECURSE is set.
468    11. When the -o option was used, pcregrep was setting a return code of 1, even
469        when matches were found, and --line-buffered was not being honoured.
471    12. Added an optional parentheses number to the -o and --only-matching options
472        of pcregrep.
474    13. Imitating Perl's /g action for multiple matches is tricky when the pattern
475        can match an empty string. The code to do it in pcretest and pcredemo
476        needed fixing:
478        (a) When the newline convention was "crlf", pcretest got it wrong, skipping
479            only one byte after an empty string match just before CRLF (this case
480            just got forgotten; "any" and "anycrlf" were OK).
482        (b) The pcretest code also had a bug, causing it to loop forever in UTF-8
483            mode when an empty string match preceded an ASCII character followed by
484            a non-ASCII character. (The code for advancing by one character rather
485            than one byte was nonsense.)
487        (c) The pcredemo.c sample program did not have any code at all to handle
488            the cases when CRLF is a valid newline sequence.
490    14. Neither pcre_exec() nor pcre_dfa_exec() was checking that the value given
491        as a starting offset was within the subject string. There is now a new
492        error, PCRE_ERROR_BADOFFSET, which is returned if the starting offset is
493        negative or greater than the length of the string. In order to test this,
494        pcretest is extended to allow the setting of negative starting offsets.
496    15. In both pcre_exec() and pcre_dfa_exec() the code for checking that the
497        starting offset points to the beginning of a UTF-8 character was
498        unnecessarily clumsy. I tidied it up.
500    16. Added PCRE_ERROR_SHORTUTF8 to make it possible to distinguish between a
501        bad UTF-8 sequence and one that is incomplete when using PCRE_PARTIAL_HARD.
503    17. Nobody had reported that the --include_dir option, which was added in
504        release 7.7 should have been called --include-dir (hyphen, not underscore)
505        for compatibility with GNU grep. I have changed it to --include-dir, but
506        left --include_dir as an undocumented synonym, and the same for
507        --exclude-dir, though that is not available in GNU grep, at least as of
508        release 2.5.4.
510    18. At a user's suggestion, the macros GETCHAR and friends (which pick up UTF-8
511        characters from a string of bytes) have been redefined so as not to use
512        loops, in order to improve performance in some environments. At the same
513        time, I abstracted some of the common code into auxiliary macros to save
514        repetition (this should not affect the compiled code).
516    19. If \c was followed by a multibyte UTF-8 character, bad things happened. A
517        compile-time error is now given if \c is not followed by an ASCII
518        character, that is, a byte less than 128. (In EBCDIC mode, the code is
519        different, and any byte value is allowed.)
521    20. Recognize (*NO_START_OPT) at the start of a pattern to set the PCRE_NO_
522        START_OPTIMIZE option, which is now allowed at compile time - but just
523        passed through to pcre_exec() or pcre_dfa_exec(). This makes it available
524        to pcregrep and other applications that have no direct access to PCRE
525        options. The new /Y option in pcretest sets this option when calling
526        pcre_compile().
528    21. Change 18 of release 8.01 broke the use of named subpatterns for recursive
529        back references. Groups containing recursive back references were forced to
530        be atomic by that change, but in the case of named groups, the amount of
531        memory required was incorrectly computed, leading to "Failed: internal
532        error: code overflow". This has been fixed.
534    22. Some patches to pcre_stringpiece.h, pcre_stringpiece_unittest.cc, and
535        pcretest.c, to avoid build problems in some Borland environments.
538    Version 8.10 25-Jun-2010
539    ------------------------
541    1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and
542        THEN.
544    2.  (*ACCEPT) was not working when inside an atomic group.
546    3.  Inside a character class, \B is treated as a literal by default, but
547        faulted if PCRE_EXTRA is set. This mimics Perl's behaviour (the -w option
548        causes the error). The code is unchanged, but I tidied the documentation.
550    4.  Inside a character class, PCRE always treated \R and \X as literals,
551        whereas Perl faults them if its -w option is set. I have changed PCRE so
552        that it faults them when PCRE_EXTRA is set.
554    5.  Added support for \N, which always matches any character other than
555        newline. (It is the same as "." when PCRE_DOTALL is not set.)
557    6.  When compiling pcregrep with newer versions of gcc which may have
558        FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',
559        declared with attribute warn_unused_result" were given. Just casting the
560        result to (void) does not stop the warnings; a more elaborate fudge is
561        needed. I've used a macro to implement this.
563    7.  Minor change to pcretest.c to avoid a compiler warning.
565    8.  Added four artifical Unicode properties to help with an option to make
566        \s etc use properties (see next item). The new properties are: Xan
567        (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).
569    9.  Added PCRE_UCP to make \b, \d, \s, \w, and certain POSIX character classes
570        use Unicode properties. (*UCP) at the start of a pattern can be used to set
571        this option. Modified pcretest to add /W to test this facility. Added
572        REG_UCP to make it available via the POSIX interface.
574    10. Added --line-buffered to pcregrep.
576    11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was
577        studied, and the match started with a letter with a code point greater than
578        127 whose first byte was different to the first byte of the other case of
579        the letter, the other case of this starting letter was not recognized
580        (#976).
582    12. If a pattern that was studied started with a repeated Unicode property
583        test, for example, \p{Nd}+, there was the theoretical possibility of
584        setting up an incorrect bitmap of starting bytes, but fortunately it could
585        not have actually happened in practice until change 8 above was made (it
586        added property types that matched character-matching opcodes).
588    13. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
589        possible starting bytes for non-anchored patterns.
591    14. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes
592        \R, and also a number of cases that involve Unicode properties, both
593        explicit and implicit when PCRE_UCP is set.
595    15. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8
596        input, it could crash or give wrong results if characters with values
597        greater than 0xc0 were present in the subject string. (Detail: it assumed
598        UTF-8 input when processing these items.)
600    16. Added a lot of (int) casts to avoid compiler warnings in systems where
601        size_t is 64-bit (#991).
603    17. Added a check for running out of memory when PCRE is compiled with
604        --disable-stack-for-recursion (#990).
606    18. If the last data line in a file for pcretest does not have a newline on
607        the end, a newline was missing in the output.
609    19. The default pcre_chartables.c file recognizes only ASCII characters (values
610        less than 128) in its various bitmaps. However, there is a facility for
611        generating tables according to the current locale when PCRE is compiled. It
612        turns out that in some environments, 0x85 and 0xa0, which are Unicode space
613        characters, are recognized by isspace() and therefore were getting set in
614        these tables, and indeed these tables seem to approximate to ISO 8859. This
615        caused a problem in UTF-8 mode when pcre_study() was used to create a list
616        of bytes that can start a match. For \s, it was including 0x85 and 0xa0,
617        which of course cannot start UTF-8 characters. I have changed the code so
618        that only real ASCII characters (less than 128) and the correct starting
619        bytes for UTF-8 encodings are set for characters greater than 127 when in
620        UTF-8 mode. (When PCRE_UCP is set - see 9 above - the code is different
621        altogether.)
623    20. Added the /T option to pcretest so as to be able to run tests with non-
624        standard character tables, thus making it possible to include the tests
625        used for 19 above in the standard set of tests.
627    21. A pattern such as (?&t)(?#()(?(DEFINE)(?<t>a)) which has a forward
628        reference to a subpattern the other side of a comment that contains an
629        opening parenthesis caused either an internal compiling error, or a
630        reference to the wrong subpattern.
633    Version 8.02 19-Mar-2010
634    ------------------------
636    1.  The Unicode data tables have been updated to Unicode 5.2.0.
638    2.  Added the option --libs-cpp to pcre-config, but only when C++ support is
639        configured.
641    3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the
642        original author of that file, following a query about its status.
644    4.  On systems that do not have stdint.h (e.g. Solaris), check for and include
645        inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
647    5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
648        quantifier applied to a forward-referencing subroutine call, could compile
649        incorrect code or give the error "internal error: previously-checked
650        referenced subpattern not found".
652    6.  Both MS Visual Studio and Symbian OS have problems with initializing
653        variables to point to external functions. For these systems, therefore,
654        pcre_malloc etc. are now initialized to local functions that call the
655        relevant global functions.
657    7.  There were two entries missing in the vectors called coptable and poptable
658        in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.
659        I've fixed the data, and added a kludgy way of testing at compile time that
660        the lengths are correct (equal to the number of opcodes).
662    8.  Following on from 7, I added a similar kludge to check the length of the
663        eint vector in pcreposix.c.
665    9.  Error texts for pcre_compile() are held as one long string to avoid too
666        much relocation at load time. To find a text, the string is searched,
667        counting zeros. There was no check for running off the end of the string,
668        which could happen if a new error number was added without updating the
669        string.
671    10. \K gave a compile-time error if it appeared in a lookbehind assersion.
673    11. \K was not working if it appeared in an atomic group or in a group that
674        was called as a "subroutine", or in an assertion. Perl 5.11 documents that
675        \K is "not well defined" if used in an assertion. PCRE now accepts it if
676        the assertion is positive, but not if it is negative.
678    12. Change 11 fortuitously reduced the size of the stack frame used in the
679        "match()" function of pcre_exec.c by one pointer. Forthcoming
680        implementation of support for (*MARK) will need an extra pointer on the
681        stack; I have reserved it now, so that the stack frame size does not
682        decrease.
684    13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other
685        item in branch that calls a recursion is a subroutine call - as in the
686        second branch in the above example - was incorrectly given the compile-
687        time error "recursive call could loop indefinitely" because pcre_compile()
688        was not correctly checking the subroutine for matching a non-empty string.
690    14. The checks for overrunning compiling workspace could trigger after an
691        overrun had occurred. This is a "should never occur" error, but it can be
692        triggered by pathological patterns such as hundreds of nested parentheses.
693        The checks now trigger 100 bytes before the end of the workspace.
695    15. Fix typo in configure.ac: "srtoq" should be "strtoq".
698    Version 8.01 19-Jan-2010
699    ------------------------
701    1.  If a pattern contained a conditional subpattern with only one branch (in
702        particular, this includes all (*DEFINE) patterns), a call to pcre_study()
703        computed the wrong minimum data length (which is of course zero for such
704        subpatterns). This could cause incorrect "no match" results.
706    2.  For patterns such as (?i)a(?-i)b|c where an option setting at the start of
707        the pattern is reset in the first branch, pcre_compile() failed with
708        "internal error: code overflow at offset...". This happened only when
709        the reset was to the original external option setting. (An optimization
710        abstracts leading options settings into an external setting, which was the
711        cause of this.)
713    3.  A pattern such as ^(?!a(*SKIP)b) where a negative assertion contained one
714        of the verbs SKIP, PRUNE, or COMMIT, did not work correctly. When the
715        assertion pattern did not match (meaning that the assertion was true), it
716        was incorrectly treated as false if the SKIP had been reached during the
717        matching. This also applied to assertions used as conditions.
719    4.  If an item that is not supported by pcre_dfa_exec() was encountered in an
720        assertion subpattern, including such a pattern used as a condition,
721        unpredictable results occurred, instead of the error return
724    5.  The C++ GlobalReplace function was not working like Perl for the special
725        situation when an empty string is matched. It now does the fancy magic
726        stuff that is necessary.
728    6.  In pcre_internal.h, obsolete includes to setjmp.h and stdarg.h have been
729        removed. (These were left over from very, very early versions of PCRE.)
731    7.  Some cosmetic changes to the code to make life easier when compiling it
732        as part of something else:
734        (a) Change DEBUG to PCRE_DEBUG.
736        (b) In pcre_compile(), rename the member of the "branch_chain" structure
737            called "current" as "current_branch", to prevent a collision with the
738            Linux macro when compiled as a kernel module.
740        (c) In pcre_study(), rename the function set_bit() as set_table_bit(), to
741            prevent a collision with the Linux macro when compiled as a kernel
742            module.
744    8.  In pcre_compile() there are some checks for integer overflows that used to
745        cast potentially large values to (double). This has been changed to that
746        when building, a check for int64_t is made, and if it is found, it is used
747        instead, thus avoiding the use of floating point arithmetic. (There is no
748        other use of FP in PCRE.) If int64_t is not found, the fallback is to
749        double.
751    9.  Added two casts to avoid signed/unsigned warnings from VS Studio Express
752        2005 (difference between two addresses compared to an unsigned value).
754    10. Change the standard AC_CHECK_LIB test for libbz2 in configure.ac to a
755        custom one, because of the following reported problem in Windows:
757          - libbz2 uses the Pascal calling convention (WINAPI) for the functions
758              under Win32.
759          - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",
760              therefore missing the function definition.
761          - The compiler thus generates a "C" signature for the test function.
762          - The linker fails to find the "C" function.
763          - PCRE fails to configure if asked to do so against libbz2.
765    11. When running libtoolize from libtool-2.2.6b as part of autogen.sh, these
766        messages were output:
768          Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
769          rerunning libtoolize, to keep the correct libtool macros in-tree.
770          Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
772        I have done both of these things.
774    12. Although pcre_dfa_exec() does not use nearly as much stack as pcre_exec()
775        most of the time, it *can* run out if it is given a pattern that contains a
776        runaway infinite recursion. I updated the discussion in the pcrestack man
777        page.
779    13. Now that we have gone to the x.xx style of version numbers, the minor
780        version may start with zero. Using 08 or 09 is a bad idea because users
781        might check the value of PCRE_MINOR in their code, and 08 or 09 may be
782        interpreted as invalid octal numbers. I've updated the previous comment in
783        configure.ac, and also added a check that gives an error if 08 or 09 are
784        used.
786    14. Change 8.00/11 was not quite complete: code had been accidentally omitted,
787        causing partial matching to fail when the end of the subject matched \W
788        in a UTF-8 pattern where \W was quantified with a minimum of 3.
790    15. There were some discrepancies between the declarations in pcre_internal.h
791        of _pcre_is_newline(), _pcre_was_newline(), and _pcre_valid_utf8() and
792        their definitions. The declarations used "const uschar *" and the
793        definitions used USPTR. Even though USPTR is normally defined as "const
794        unsigned char *" (and uschar is typedeffed as "unsigned char"), it was
795        reported that: "This difference in casting confuses some C++ compilers, for
796        example, SunCC recognizes above declarations as different functions and
797        generates broken code for hbpcre." I have changed the declarations to use
798        USPTR.
800    16. GNU libtool is named differently on some systems. The autogen.sh script now
801        tries several variants such as glibtoolize (MacOSX) and libtoolize1x
802        (FreeBSD).
804    17. Applied Craig's patch that fixes an HP aCC compile error in pcre 8.00
805        (strtoXX undefined when compiling pcrecpp.cc). The patch contains this
806        comment: "Figure out how to create a longlong from a string: strtoll and
807        equivalent. It's not enough to call AC_CHECK_FUNCS: hpux has a strtoll, for
808        instance, but it only takes 2 args instead of 3!"
810    18. A subtle bug concerned with back references has been fixed by a change of
811        specification, with a corresponding code fix. A pattern such as
812        ^(xa|=?\1a)+$ which contains a back reference inside the group to which it
813        refers, was giving matches when it shouldn't. For example, xa=xaaa would
814        match that pattern. Interestingly, Perl (at least up to 5.11.3) has the
815        same bug. Such groups have to be quantified to be useful, or contained
816        inside another quantified group. (If there's no repetition, the reference
817        can never match.) The problem arises because, having left the group and
818        moved on to the rest of the pattern, a later failure that backtracks into
819        the group uses the captured value from the final iteration of the group
820        rather than the correct earlier one. I have fixed this in PCRE by forcing
821        any group that contains a reference to itself to be an atomic group; that
822        is, there cannot be any backtracking into it once it has completed. This is
823        similar to recursive and subroutine calls.
826    Version 8.00 19-Oct-09
827    ----------------------
829    1.  The table for translating pcre_compile() error codes into POSIX error codes
830        was out-of-date, and there was no check on the pcre_compile() error code
831        being within the table. This could lead to an OK return being given in
832        error.
834    2.  Changed the call to open a subject file in pcregrep from fopen(pathname,
835        "r") to fopen(pathname, "rb"), which fixed a problem with some of the tests
836        in a Windows environment.
838    3.  The pcregrep --count option prints the count for each file even when it is
839        zero, as does GNU grep. However, pcregrep was also printing all files when
840        --files-with-matches was added. Now, when both options are given, it prints
841        counts only for those files that have at least one match. (GNU grep just
842        prints the file name in this circumstance, but including the count seems
843        more useful - otherwise, why use --count?) Also ensured that the
844        combination -clh just lists non-zero counts, with no names.
846    4.  The long form of the pcregrep -F option was incorrectly implemented as
847        --fixed_strings instead of --fixed-strings. This is an incompatible change,
848        but it seems right to fix it, and I didn't think it was worth preserving
849        the old behaviour.
851    5.  The command line items --regex=pattern and --regexp=pattern were not
852        recognized by pcregrep, which required --regex pattern or --regexp pattern
853        (with a space rather than an '='). The man page documented the '=' forms,
854        which are compatible with GNU grep; these now work.
856    6.  No libpcreposix.pc file was created for pkg-config; there was just
857        libpcre.pc and libpcrecpp.pc. The omission has been rectified.
859    7.  Added #ifndef SUPPORT_UCP into the pcre_ucd.c module, to reduce its size
860        when UCP support is not needed, by modifying the Python script that
861        generates it from Unicode data files. This should not matter if the module
862        is correctly used as a library, but I received one complaint about 50K of
863        unwanted data. My guess is that the person linked everything into his
864        program rather than using a library. Anyway, it does no harm.
866    8.  A pattern such as /\x{123}{2,2}+/8 was incorrectly compiled; the trigger
867        was a minimum greater than 1 for a wide character in a possessive
868        repetition. The same bug could also affect patterns like /(\x{ff}{0,2})*/8
869        which had an unlimited repeat of a nested, fixed maximum repeat of a wide
870        character. Chaos in the form of incorrect output or a compiling loop could
871        result.
873    9.  The restrictions on what a pattern can contain when partial matching is
874        requested for pcre_exec() have been removed. All patterns can now be
875        partially matched by this function. In addition, if there are at least two
876        slots in the offset vector, the offset of the earliest inspected character
877        for the match and the offset of the end of the subject are set in them when
878        PCRE_ERROR_PARTIAL is returned.
880    10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is
881        synonymous with PCRE_PARTIAL, for backwards compatibility, and
882        PCRE_PARTIAL_HARD, which causes a partial match to supersede a full match,
883        and may be more useful for multi-segment matching.
885    11. Partial matching with pcre_exec() is now more intuitive. A partial match
886        used to be given if ever the end of the subject was reached; now it is
887        given only if matching could not proceed because another character was
888        needed. This makes a difference in some odd cases such as Z(*FAIL) with the
889        string "Z", which now yields "no match" instead of "partial match". In the
890        case of pcre_dfa_exec(), "no match" is given if every matching path for the
891        final character ended with (*FAIL).
893    12. Restarting a match using pcre_dfa_exec() after a partial match did not work
894        if the pattern had a "must contain" character that was already found in the
895        earlier partial match, unless partial matching was again requested. For
896        example, with the pattern /dog.(body)?/, the "must contain" character is
897        "g". If the first part-match was for the string "dog", restarting with
898        "sbody" failed. This bug has been fixed.
900    13. The string returned by pcre_dfa_exec() after a partial match has been
901        changed so that it starts at the first inspected character rather than the
902        first character of the match. This makes a difference only if the pattern
903        starts with a lookbehind assertion or \b or \B (\K is not supported by
904        pcre_dfa_exec()). It's an incompatible change, but it makes the two
905        matching functions compatible, and I think it's the right thing to do.
907    14. Added a pcredemo man page, created automatically from the pcredemo.c file,
908        so that the demonstration program is easily available in environments where
909        PCRE has not been installed from source.
911    15. Arranged to add -DPCRE_STATIC to cflags in libpcre.pc, libpcreposix.cp,
912        libpcrecpp.pc and pcre-config when PCRE is not compiled as a shared
913        library.
915    16. Added REG_UNGREEDY to the pcreposix interface, at the request of a user.
916        It maps to PCRE_UNGREEDY. It is not, of course, POSIX-compatible, but it
917        is not the first non-POSIX option to be added. Clearly some people find
918        these options useful.
920    17. If a caller to the POSIX matching function regexec() passes a non-zero
921        value for nmatch with a NULL value for pmatch, the value of
922        nmatch is forced to zero.
924    18. RunGrepTest did not have a test for the availability of the -u option of
925        the diff command, as RunTest does. It now checks in the same way as
926        RunTest, and also checks for the -b option.
928    19. If an odd number of negated classes containing just a single character
929        interposed, within parentheses, between a forward reference to a named
930        subpattern and the definition of the subpattern, compilation crashed with
931        an internal error, complaining that it could not find the referenced
932        subpattern. An example of a crashing pattern is /(?&A)(([^m])(?<A>))/.
933        [The bug was that it was starting one character too far in when skipping
934        over the character class, thus treating the ] as data rather than
935        terminating the class. This meant it could skip too much.]
937    20. Added PCRE_NOTEMPTY_ATSTART in order to be able to correctly implement the
938        /g option in pcretest when the pattern contains \K, which makes it possible
939        to have an empty string match not at the start, even when the pattern is
940        anchored. Updated pcretest and pcredemo to use this option.
942    21. If the maximum number of capturing subpatterns in a recursion was greater
943        than the maximum at the outer level, the higher number was returned, but
944        with unset values at the outer level. The correct (outer level) value is
945        now given.
947    22. If (*ACCEPT) appeared inside capturing parentheses, previous releases of
948        PCRE did not set those parentheses (unlike Perl). I have now found a way to
949        make it do so. The string so far is captured, making this feature
950        compatible with Perl.
952    23. The tests have been re-organized, adding tests 11 and 12, to make it
953        possible to check the Perl 5.10 features against Perl 5.10.
955    24. Perl 5.10 allows subroutine calls in lookbehinds, as long as the subroutine
956        pattern matches a fixed length string. PCRE did not allow this; now it
957        does. Neither allows recursion.
959    25. I finally figured out how to implement a request to provide the minimum
960        length of subject string that was needed in order to match a given pattern.
961        (It was back references and recursion that I had previously got hung up
962        on.) This code has now been added to pcre_study(); it finds a lower bound
963        to the length of subject needed. It is not necessarily the greatest lower
964        bound, but using it to avoid searching strings that are too short does give
965        some useful speed-ups. The value is available to calling programs via
966        pcre_fullinfo().
968    26. While implementing 25, I discovered to my embarrassment that pcretest had
969        not been passing the result of pcre_study() to pcre_dfa_exec(), so the
970        study optimizations had never been tested with that matching function.
971        Oops. What is worse, even when it was passed study data, there was a bug in
972        pcre_dfa_exec() that meant it never actually used it. Double oops. There
973        were also very few tests of studied patterns with pcre_dfa_exec().
975    27. If (?| is used to create subpatterns with duplicate numbers, they are now
976        allowed to have the same name, even if PCRE_DUPNAMES is not set. However,
977        on the other side of the coin, they are no longer allowed to have different
978        names, because these cannot be distinguished in PCRE, and this has caused
979        confusion. (This is a difference from Perl.)
981    28. When duplicate subpattern names are present (necessarily with different
982        numbers, as required by 27 above), and a test is made by name in a
983        conditional pattern, either for a subpattern having been matched, or for
984        recursion in such a pattern, all the associated numbered subpatterns are
985        tested, and the overall condition is true if the condition is true for any
986        one of them. This is the way Perl works, and is also more like the way
987        testing by number works.
990    Version 7.9 11-Apr-09
991    ---------------------
993    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
994        (pcretest), all targets were linked against these libraries. This included
995        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
996        libraries. This caused unwanted dependencies to be created. This problem
997        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
998        pcretest is linked with readline.
1000    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
1001        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
1002        moved outside it again, because FALSE and TRUE are already defined in AIX,
1003        but BOOL is not.
1005    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
1006        PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
1008    4.  The pcregrep documentation said spaces were inserted as well as colons (or
1009        hyphens) following file names and line numbers when outputting matching
1010        lines. This is not true; no spaces are inserted. I have also clarified the
1011        wording for the --colour (or --color) option.
1013    5.  In pcregrep, when --colour was used with -o, the list of matching strings
1014        was not coloured; this is different to GNU grep, so I have changed it to be
1015        the same.
1017    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
1018        each matching line was coloured. Now it goes on to look for further matches
1019        of any of the test patterns, which is the same behaviour as GNU grep.
1021    7.  A pattern that could match an empty string could cause pcregrep to loop; it
1022        doesn't make sense to accept an empty string match in pcregrep, so I have
1023        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
1024        seems to be how GNU grep behaves.
1026    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
1027        start or after a newline", because the conditional assertion was not being
1028        correctly handled. The rule now is that both the assertion and what follows
1029        in the first alternative must satisfy the test.
1031    9.  If auto-callout was enabled in a pattern with a conditional group whose
1032        condition was an assertion, PCRE could crash during matching, both with
1033        pcre_exec() and pcre_dfa_exec().
1035    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
1036        used for matching.
1038    11. Unicode property support in character classes was not working for
1039        characters (bytes) greater than 127 when not in UTF-8 mode.
1041    12. Added the -M command line option to pcretest.
1043    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
1045    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
1047    16. Added comments and documentation about mis-use of no_arg in the C++
1048        wrapper.
1050    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
1051        from Martin Jerabek that uses macro names for all relevant character and
1052        string constants.
1054    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
1055        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
1056        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
1057        these, but not everybody uses configure.
1059    19. A conditional group that had only one branch was not being correctly
1060        recognized as an item that could match an empty string. This meant that an
1061        enclosing group might also not be so recognized, causing infinite looping
1062        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
1063        with the subject "ab", where knowledge that the repeated group can match
1064        nothing is needed in order to break the loop.
1066    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
1067        exec(), but without supplying a callout function, matching went wrong.
1069    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
1070        leak if the size of the offset vector was greater than 30. When the vector
1071        is smaller, the saved offsets during recursion go onto a local stack
1072        vector, but for larger vectors malloc() is used. It was failing to free
1073        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
1074        error, in fact).
1076    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
1077        heapframe that is used only when UTF-8 support is enabled. This caused no
1078        problem, but was untidy.
1080    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
1081        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
1082        included within another project.
1084    24. Steven Van Ingelgem's patches to add more options to the CMake support,
1085        slightly modified by me:
1087          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
1088              not building pcregrep.
1090          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
1091              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
1093    25. Forward references, both numeric and by name, in patterns that made use of
1094        duplicate group numbers, could behave incorrectly or give incorrect errors,
1095        because when scanning forward to find the reference group, PCRE was not
1096        taking into account the duplicate group numbers. A pattern such as
1097        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
1099    26. Changed a few more instances of "const unsigned char *" to USPTR, making
1100        the feature of a custom pointer more persuasive (as requested by a user).
1102    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
1103        pcretest.c, inside #ifndefs, because it seems they are sometimes already
1104        pre-defined.
1106    28. Added support for (*UTF8) at the start of a pattern.
1108    29. Arrange for flags added by the "release type" setting in CMake to be shown
1109        in the configuration summary.
1112    Version 7.8 05-Sep-08
1113    ---------------------
1115    1.  Replaced UCP searching code with optimized version as implemented for Ad
1116        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
1117        stage table and inline lookup instead of a function, giving speed ups of 2
1118        to 5 times on some simple patterns that I tested. Permission was given to
1119        distribute the MultiStage2.py script that generates the tables (it's not in
1120        the tarball, but is in the Subversion repository).
1122    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
1123        scripts.
1125    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
1126        a group with a zero qualifier. The result of the study could be incorrect,
1127        or the function might crash, depending on the pattern.
1129    4.  Caseless matching was not working for non-ASCII characters in back
1130        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
1131        It now works when Unicode Property Support is available.
1133    5.  In pcretest, an escape such as \x{de} in the data was always generating
1134        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
1135        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
1136        truncation.
1138    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
1140    7.  Added two (int) casts to pcregrep when printing the difference of two
1141        pointers, in case they are 64-bit values.
1143    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
1144        test 2 if it fails.
1146    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
1147        and a #define of that name to empty if it is not externally set. This is to
1148        allow users of MSVC to set it if necessary.
1150    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
1151        the convenience functions in the pcre_get.c source file.
1153    11. An option change at the start of a pattern that had top-level alternatives
1154        could cause overwriting and/or a crash. This command provoked a crash in
1155        some environments:
1157          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
1159        This potential security problem was recorded as CVE-2008-2371.
1161    12. For a pattern where the match had to start at the beginning or immediately
1162        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
1163        pcre_dfa_exec() could read past the end of the passed subject if there was
1164        no match. To help with detecting such bugs (e.g. with valgrind), I modified
1165        pcretest so that it places the subject at the end of its malloc-ed buffer.
1167    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
1168        exec() might read past the end of the data buffer in UTF-8 mode.
1170    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
1171        the data contained the byte 0x85 as part of a UTF-8 character within its
1172        first line. This applied both to normal and DFA matching.
1174    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
1175        /^[^d]*?$/8 failed to match "abc".
1177    16. Added a missing copyright notice to pcrecpp_internal.h.
1179    17. Make it more clear in the documentation that values returned from
1180        pcre_exec() in ovector are byte offsets, not character counts.
1182    18. Tidied a few places to stop certain compilers from issuing warnings.
1184    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
1185        supplied by Stefan Weber. I made a further small update for 7.8 because
1186        there is a change of source arrangements: the pcre_searchfuncs.c module is
1187        replaced by pcre_ucd.c.
1190    Version 7.7 07-May-08
1191    ---------------------
1193    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
1194        a string to a long long, pretend we don't even have a long long." This is
1195        done by checking for the strtoq, strtoll, and _strtoi64 functions.
1197    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
1198        pre-7.6 versions, which defined a global no_arg variable instead of putting
1199        it in the RE class. (See also #8 below.)
1201    3.  Remove a line of dead code, identified by coverity and reported by Nuno
1202        Lopes.
1204    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
1206        (1) The include/exclude patterns were being applied to the whole pathnames
1207            of files, instead of just to the final components.
1209        (2) If there was more than one level of directory, the subdirectories were
1210            skipped unless they satisfied the include/exclude conditions. This is
1211            inconsistent with GNU grep (and could even be seen as contrary to the
1212            pcregrep specification - which I improved to make it absolutely clear).
1213            The action now is always to scan all levels of directory, and just
1214            apply the include/exclude patterns to regular files.
1216    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
1217        --exclude_dir in the tests to avoid scanning .svn directories.
1219    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
1220        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
1221        doesn't support NULs in patterns.
1223    7.  Added some missing "const"s to declarations of static tables in
1224        pcre_compile.c and pcre_dfa_exec.c.
1226    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
1227        caused by fix #2  above. (Subsequently also a second patch to fix the
1228        first patch. And a third patch - this was a messy problem.)
1230    9.  Applied Craig's patch to remove the use of push_back().
1232    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
1233        matching function regexec().
1235    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
1236        which, however, unlike Perl's \g{...}, are subroutine calls, not back
1237        references. PCRE supports relative numbers with this syntax (I don't think
1238        Oniguruma does).
1240    12. Previously, a group with a zero repeat such as (...){0} was completely
1241        omitted from the compiled regex. However, this means that if the group
1242        was called as a subroutine from elsewhere in the pattern, things went wrong
1243        (an internal error was given). Such groups are now left in the compiled
1244        pattern, with a new opcode that causes them to be skipped at execution
1245        time.
1247    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
1248        to the way PCRE behaves:
1250        (a) A lone ] character is dis-allowed (Perl treats it as data).
1252        (b) A back reference to an unmatched subpattern matches an empty string
1253            (Perl fails the current match path).
1255        (c) A data ] in a character class must be notated as \] because if the
1256            first data character in a class is ], it defines an empty class. (In
1257            Perl it is not possible to have an empty class.) The empty class []
1258            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
1259            The negative empty class [^] matches any one character, independently
1260            of the DOTALL setting.
1262    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
1263        non-existent subpattern following a character class starting with ']' and
1264        containing () gave an internal compiling error instead of "reference to
1265        non-existent subpattern". Fortunately, when the pattern did exist, the
1266        compiled code was correct. (When scanning forwards to check for the
1267        existencd of the subpattern, it was treating the data ']' as terminating
1268        the class, so got the count wrong. When actually compiling, the reference
1269        was subsequently set up correctly.)
1271    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
1272        it was being rejected as not supported by pcre_dfa_exec(), even though
1273        other assertions are supported. I have made pcre_dfa_exec() support
1274        (*FAIL).
1276    16. The implementation of 13c above involved the invention of a new opcode,
1277        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
1278        cannot be changed at match time, I realized I could make a small
1279        improvement to matching performance by compiling OP_ALLANY instead of
1280        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
1281        on the OP_ANY path.
1283    17. Compiling pcretest on Windows with readline support failed without the
1284        following two fixes: (1) Make the unistd.h include conditional on
1285        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
1287    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
1288        ncurses library to be included for pcretest when ReadLine support is
1289        requested, but also to allow for it to be overridden. This patch came from
1290        Daniel Bergström.
1292    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
1293        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
1294        any errors with the current Unicode tables. Thanks to Peter Kankowski for
1295        spotting this.
1298    Version 7.6 28-Jan-08
1299    ---------------------
1301    1.  A character class containing a very large number of characters with
1302        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
1303        overflow.
1305    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
1306        HAVE_LONG_LONG is not defined.
1308    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
1309        bring them up to date and include new features. This patch includes:
1311        - Fixed PH's badly added libz and libbz2 support.
1312        - Fixed a problem with static linking.
1313        - Added pcredemo. [But later removed - see 7 below.]
1314        - Fixed dftables problem and added an option.
1315        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
1316            HAVE_LONG_LONG.
1317        - Added readline support for pcretest.
1318        - Added an listing of the option settings after cmake has run.
1320    4.  A user submitted a patch to Makefile that makes it easy to create
1321        "pcre.dll" under mingw when using Configure/Make. I added stuff to
1322        Makefile.am that cause it to include this special target, without
1323        affecting anything else. Note that the same mingw target plus all
1324        the other distribution libraries and programs are now supported
1325        when configuring with CMake (see 6 below) instead of with
1326        Configure/Make.
1328    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
1329        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
1330        exported in the Windows port". It has not yet been confirmed that the patch
1331        solves the problem, but it does no harm.
1333    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
1334        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
1335        with CMake, and also correct the comment about stack recursion.
1337    7.  Remove the automatic building of pcredemo from the ./configure system and
1338        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
1339        of a program that users should build themselves after PCRE is installed, so
1340        building it automatically is not really right. What is more, it gave
1341        trouble in some build environments.
1343    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
1346    Version 7.5 10-Jan-08
1347  ---------------------  ---------------------
1349  1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'  1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
# Line 76  Version 7.5 12-Nov-07 Line 1418  Version 7.5 12-Nov-07
1418      does the same. The return code can be used to tell if there were any      does the same. The return code can be used to tell if there were any
1419      non-matching lines.      non-matching lines.
1421  14. The pattern (?=something)(?R) was not being diagnosed as a potentially  14. Added --file-offsets and --line-offsets to pcregrep.
1423    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
1424      infinitely looping recursion. The bug was that positive lookaheads were not      infinitely looping recursion. The bug was that positive lookaheads were not
1425      being skipped when checking for a possible empty match (negative lookaheads      being skipped when checking for a possible empty match (negative lookaheads
1426      and both kinds of lookbehind were skipped).      and both kinds of lookbehind were skipped).
1428  15. Fixed two typos in the Windows-only code in pcregrep.c, and moved the  16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
1429      inclusion of <windows.h> to before rather than after the definition of      inclusion of <windows.h> to before rather than after the definition of
1430      INVALID_FILE_ATTRIBUTES (patch from David Byron).      INVALID_FILE_ATTRIBUTES (patch from David Byron).
1432  16. Specifying a possessive quantifier with a specific limit for a Unicode  17. Specifying a possessive quantifier with a specific limit for a Unicode
1433      character property caused pcre_compile() to compile bad code, which led at      character property caused pcre_compile() to compile bad code, which led at
1434      runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this      runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
1435      are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that      are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
1436      caused the error; without that there was no problem.      caused the error; without that there was no problem.
1438  17. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.  18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
1440    19. Added --enable-pcretest-libreadline.
1442    20. In pcrecpp.cc, the variable 'count' was incremented twice in
1443        RE::GlobalReplace(). As a result, the number of replacements returned was
1444        double what it should be. I removed one of the increments, but Craig sent a
1445        later patch that removed the other one (the right fix) and added unit tests
1446        that check the return values (which was not done before).
1448    21. Several CMake things:
1450        (1) Arranged that, when cmake is used on Unix, the libraries end up with
1451            the names libpcre and libpcreposix, not just pcre and pcreposix.
1453        (2) The above change means that pcretest and pcregrep are now correctly
1454            linked with the newly-built libraries, not previously installed ones.
1458    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
1459        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
1460        UTF-8 newline character). The key issue is that the pattern starts .*;
1461        this means that the match must be either at the beginning, or after a
1462        newline. The bug was in the code for advancing after a failed match and
1463        checking that the new position followed a newline. It was not taking
1464        account of UTF-8 characters correctly.
1466    23. PCRE was behaving differently from Perl in the way it recognized POSIX
1467        character classes. PCRE was not treating the sequence [:...:] as a
1468        character class unless the ... were all letters. Perl, however, seems to
1469        allow any characters between [: and :], though of course it rejects as
1470        unknown any "names" that contain non-letters, because all the known class
1471        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
1472        for example, whereas PCRE did not - it did not recognize a POSIX character
1473        class. This seemed a bit dangerous, so the code has been changed to be
1474        closer to Perl. The behaviour is not identical to Perl, because PCRE will
1475        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
1476        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
1477        Perl does, and where it didn't before.
1479  18. Added --enable-pcretest-libreadline.  24. Rewrite so as to remove the single use of %n from pcregrep because in some
1480        Windows environments %n is disabled by default.
1483  Version 7.4 21-Sep-07  Version 7.4 21-Sep-07

Removed from v.287  
changed lines
  Added in v.740

  ViewVC Help
Powered by ViewVC 1.1.5