ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 149 by ph10, Mon Apr 16 15:28:08 2007 UTC revision 591 by ph10, Sat Jan 15 17:26:57 2011 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 7.1 12-Mar-07  Version 8.12 15-Jan-2011
5    ------------------------
7    1.  Fixed some typos in the markup of the man pages, and wrote a script that
8        checks for such things as part of the documentation building process.
10    2.  On a big-endian 64-bit system, pcregrep did not correctly process the
11        --match-limit and --recursion-limit options (added for 8.11). In
12        particular, this made one of the standard tests fail. (The integer value
13        went into the wrong half of a long int.)
15    3.  If the --colour option was given to pcregrep with -v (invert match), it
16        did strange things, either producing crazy output, or crashing. It should,
17        of course, ignore a request for colour when reporting lines that do not
18        match.
20    4.  Another pcregrep bug caused similar problems if --colour was specified with
21        -M (multiline) and the pattern match finished with a line ending.
23    5.  In pcregrep, when a pattern that ended with a literal newline sequence was
24        matched in multiline mode, the following line was shown as part of the
25        match. This seems wrong, so I have changed it.
27    6.  Another pcregrep bug in multiline mode, when --colour was specified, caused
28        the check for further matches in the same line (so they could be coloured)
29        to overrun the end of the current line. If another match was found, it was
30        incorrectly shown (and then shown again when found in the next line).
32    7.  If pcregrep was compiled under Windows, there was a reference to the
33        function pcregrep_exit() before it was defined. I am assuming this was
34        the cause of the "error C2371: 'pcregrep_exit' : redefinition;" that was
35        reported by a user. I've moved the definition above the reference.
38    Version 8.11 10-Dec-2010
39    ------------------------
41    1.  (*THEN) was not working properly if there were untried alternatives prior
42        to it in the current branch. For example, in ((a|b)(*THEN)(*F)|c..) it
43        backtracked to try for "b" instead of moving to the next alternative branch
44        at the same level (in this case, to look for "c"). The Perl documentation
45        is clear that when (*THEN) is backtracked onto, it goes to the "next
46        alternative in the innermost enclosing group".
48    2.  (*COMMIT) was not overriding (*THEN), as it does in Perl. In a pattern
49        such as   (A(*COMMIT)B(*THEN)C|D)  any failure after matching A should
50        result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and
51        (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides
52        (*THEN).
54    3.  If \s appeared in a character class, it removed the VT character from
55        the class, even if it had been included by some previous item, for example
56        in [\x00-\xff\s]. (This was a bug related to the fact that VT is not part
57        of \s, but is part of the POSIX "space" class.)
59    4.  A partial match never returns an empty string (because you can always
60        match an empty string at the end of the subject); however the checking for
61        an empty string was starting at the "start of match" point. This has been
62        changed to the "earliest inspected character" point, because the returned
63        data for a partial match starts at this character. This means that, for
64        example, /(?<=abc)def/ gives a partial match for the subject "abc"
65        (previously it gave "no match").
67    5.  Changes have been made to the way PCRE_PARTIAL_HARD affects the matching
68        of $, \z, \Z, \b, and \B. If the match point is at the end of the string,
69        previously a full match would be given. However, setting PCRE_PARTIAL_HARD
70        has an implication that the given string is incomplete (because a partial
71        match is preferred over a full match). For this reason, these items now
72        give a partial match in this situation. [Aside: previously, the one case
73        /t\b/ matched against "cat" with PCRE_PARTIAL_HARD set did return a partial
74        match rather than a full match, which was wrong by the old rules, but is
75        now correct.]
77    6.  There was a bug in the handling of #-introduced comments, recognized when
78        PCRE_EXTENDED is set, when PCRE_NEWLINE_ANY and PCRE_UTF8 were also set.
79        If a UTF-8 multi-byte character included the byte 0x85 (e.g. +U0445, whose
80        UTF-8 encoding is 0xd1,0x85), this was misinterpreted as a newline when
81        scanning for the end of the comment. (*Character* 0x85 is an "any" newline,
82        but *byte* 0x85 is not, in UTF-8 mode). This bug was present in several
83        places in pcre_compile().
85    7.  Related to (6) above, when pcre_compile() was skipping #-introduced
86        comments when looking ahead for named forward references to subpatterns,
87        the only newline sequence it recognized was NL. It now handles newlines
88        according to the set newline convention.
90    8.  SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the
91        former, but used strtoul(), whereas pcretest avoided strtoul() but did not
92        cater for a lack of strerror(). These oversights have been fixed.
94    9.  Added --match-limit and --recursion-limit to pcregrep.
96    10. Added two casts needed to build with Visual Studio when NO_RECURSE is set.
98    11. When the -o option was used, pcregrep was setting a return code of 1, even
99        when matches were found, and --line-buffered was not being honoured.
101    12. Added an optional parentheses number to the -o and --only-matching options
102        of pcregrep.
104    13. Imitating Perl's /g action for multiple matches is tricky when the pattern
105        can match an empty string. The code to do it in pcretest and pcredemo
106        needed fixing:
108        (a) When the newline convention was "crlf", pcretest got it wrong, skipping
109            only one byte after an empty string match just before CRLF (this case
110            just got forgotten; "any" and "anycrlf" were OK).
112        (b) The pcretest code also had a bug, causing it to loop forever in UTF-8
113            mode when an empty string match preceded an ASCII character followed by
114            a non-ASCII character. (The code for advancing by one character rather
115            than one byte was nonsense.)
117        (c) The pcredemo.c sample program did not have any code at all to handle
118            the cases when CRLF is a valid newline sequence.
120    14. Neither pcre_exec() nor pcre_dfa_exec() was checking that the value given
121        as a starting offset was within the subject string. There is now a new
122        error, PCRE_ERROR_BADOFFSET, which is returned if the starting offset is
123        negative or greater than the length of the string. In order to test this,
124        pcretest is extended to allow the setting of negative starting offsets.
126    15. In both pcre_exec() and pcre_dfa_exec() the code for checking that the
127        starting offset points to the beginning of a UTF-8 character was
128        unnecessarily clumsy. I tidied it up.
130    16. Added PCRE_ERROR_SHORTUTF8 to make it possible to distinguish between a
131        bad UTF-8 sequence and one that is incomplete when using PCRE_PARTIAL_HARD.
133    17. Nobody had reported that the --include_dir option, which was added in
134        release 7.7 should have been called --include-dir (hyphen, not underscore)
135        for compatibility with GNU grep. I have changed it to --include-dir, but
136        left --include_dir as an undocumented synonym, and the same for
137        --exclude-dir, though that is not available in GNU grep, at least as of
138        release 2.5.4.
140    18. At a user's suggestion, the macros GETCHAR and friends (which pick up UTF-8
141        characters from a string of bytes) have been redefined so as not to use
142        loops, in order to improve performance in some environments. At the same
143        time, I abstracted some of the common code into auxiliary macros to save
144        repetition (this should not affect the compiled code).
146    19. If \c was followed by a multibyte UTF-8 character, bad things happened. A
147        compile-time error is now given if \c is not followed by an ASCII
148        character, that is, a byte less than 128. (In EBCDIC mode, the code is
149        different, and any byte value is allowed.)
151    20. Recognize (*NO_START_OPT) at the start of a pattern to set the PCRE_NO_
152        START_OPTIMIZE option, which is now allowed at compile time - but just
153        passed through to pcre_exec() or pcre_dfa_exec(). This makes it available
154        to pcregrep and other applications that have no direct access to PCRE
155        options. The new /Y option in pcretest sets this option when calling
156        pcre_compile().
158    21. Change 18 of release 8.01 broke the use of named subpatterns for recursive
159        back references. Groups containing recursive back references were forced to
160        be atomic by that change, but in the case of named groups, the amount of
161        memory required was incorrectly computed, leading to "Failed: internal
162        error: code overflow". This has been fixed.
164    22. Some patches to pcre_stringpiece.h, pcre_stringpiece_unittest.cc, and
165        pcretest.c, to avoid build problems in some Borland environments.
168    Version 8.10 25-Jun-2010
169    ------------------------
171    1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and
172        THEN.
174    2.  (*ACCEPT) was not working when inside an atomic group.
176    3.  Inside a character class, \B is treated as a literal by default, but
177        faulted if PCRE_EXTRA is set. This mimics Perl's behaviour (the -w option
178        causes the error). The code is unchanged, but I tidied the documentation.
180    4.  Inside a character class, PCRE always treated \R and \X as literals,
181        whereas Perl faults them if its -w option is set. I have changed PCRE so
182        that it faults them when PCRE_EXTRA is set.
184    5.  Added support for \N, which always matches any character other than
185        newline. (It is the same as "." when PCRE_DOTALL is not set.)
187    6.  When compiling pcregrep with newer versions of gcc which may have
188        FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',
189        declared with attribute warn_unused_result" were given. Just casting the
190        result to (void) does not stop the warnings; a more elaborate fudge is
191        needed. I've used a macro to implement this.
193    7.  Minor change to pcretest.c to avoid a compiler warning.
195    8.  Added four artifical Unicode properties to help with an option to make
196        \s etc use properties (see next item). The new properties are: Xan
197        (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).
199    9.  Added PCRE_UCP to make \b, \d, \s, \w, and certain POSIX character classes
200        use Unicode properties. (*UCP) at the start of a pattern can be used to set
201        this option. Modified pcretest to add /W to test this facility. Added
202        REG_UCP to make it available via the POSIX interface.
204    10. Added --line-buffered to pcregrep.
206    11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was
207        studied, and the match started with a letter with a code point greater than
208        127 whose first byte was different to the first byte of the other case of
209        the letter, the other case of this starting letter was not recognized
210        (#976).
212    12. If a pattern that was studied started with a repeated Unicode property
213        test, for example, \p{Nd}+, there was the theoretical possibility of
214        setting up an incorrect bitmap of starting bytes, but fortunately it could
215        not have actually happened in practice until change 8 above was made (it
216        added property types that matched character-matching opcodes).
218    13. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
219        possible starting bytes for non-anchored patterns.
221    14. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes
222        \R, and also a number of cases that involve Unicode properties, both
223        explicit and implicit when PCRE_UCP is set.
225    15. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8
226        input, it could crash or give wrong results if characters with values
227        greater than 0xc0 were present in the subject string. (Detail: it assumed
228        UTF-8 input when processing these items.)
230    16. Added a lot of (int) casts to avoid compiler warnings in systems where
231        size_t is 64-bit (#991).
233    17. Added a check for running out of memory when PCRE is compiled with
234        --disable-stack-for-recursion (#990).
236    18. If the last data line in a file for pcretest does not have a newline on
237        the end, a newline was missing in the output.
239    19. The default pcre_chartables.c file recognizes only ASCII characters (values
240        less than 128) in its various bitmaps. However, there is a facility for
241        generating tables according to the current locale when PCRE is compiled. It
242        turns out that in some environments, 0x85 and 0xa0, which are Unicode space
243        characters, are recognized by isspace() and therefore were getting set in
244        these tables, and indeed these tables seem to approximate to ISO 8859. This
245        caused a problem in UTF-8 mode when pcre_study() was used to create a list
246        of bytes that can start a match. For \s, it was including 0x85 and 0xa0,
247        which of course cannot start UTF-8 characters. I have changed the code so
248        that only real ASCII characters (less than 128) and the correct starting
249        bytes for UTF-8 encodings are set for characters greater than 127 when in
250        UTF-8 mode. (When PCRE_UCP is set - see 9 above - the code is different
251        altogether.)
253    20. Added the /T option to pcretest so as to be able to run tests with non-
254        standard character tables, thus making it possible to include the tests
255        used for 19 above in the standard set of tests.
257    21. A pattern such as (?&t)(?#()(?(DEFINE)(?<t>a)) which has a forward
258        reference to a subpattern the other side of a comment that contains an
259        opening parenthesis caused either an internal compiling error, or a
260        reference to the wrong subpattern.
263    Version 8.02 19-Mar-2010
264    ------------------------
266    1.  The Unicode data tables have been updated to Unicode 5.2.0.
268    2.  Added the option --libs-cpp to pcre-config, but only when C++ support is
269        configured.
271    3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the
272        original author of that file, following a query about its status.
274    4.  On systems that do not have stdint.h (e.g. Solaris), check for and include
275        inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
277    5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
278        quantifier applied to a forward-referencing subroutine call, could compile
279        incorrect code or give the error "internal error: previously-checked
280        referenced subpattern not found".
282    6.  Both MS Visual Studio and Symbian OS have problems with initializing
283        variables to point to external functions. For these systems, therefore,
284        pcre_malloc etc. are now initialized to local functions that call the
285        relevant global functions.
287    7.  There were two entries missing in the vectors called coptable and poptable
288        in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.
289        I've fixed the data, and added a kludgy way of testing at compile time that
290        the lengths are correct (equal to the number of opcodes).
292    8.  Following on from 7, I added a similar kludge to check the length of the
293        eint vector in pcreposix.c.
295    9.  Error texts for pcre_compile() are held as one long string to avoid too
296        much relocation at load time. To find a text, the string is searched,
297        counting zeros. There was no check for running off the end of the string,
298        which could happen if a new error number was added without updating the
299        string.
301    10. \K gave a compile-time error if it appeared in a lookbehind assersion.
303    11. \K was not working if it appeared in an atomic group or in a group that
304        was called as a "subroutine", or in an assertion. Perl 5.11 documents that
305        \K is "not well defined" if used in an assertion. PCRE now accepts it if
306        the assertion is positive, but not if it is negative.
308    12. Change 11 fortuitously reduced the size of the stack frame used in the
309        "match()" function of pcre_exec.c by one pointer. Forthcoming
310        implementation of support for (*MARK) will need an extra pointer on the
311        stack; I have reserved it now, so that the stack frame size does not
312        decrease.
314    13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other
315        item in branch that calls a recursion is a subroutine call - as in the
316        second branch in the above example - was incorrectly given the compile-
317        time error "recursive call could loop indefinitely" because pcre_compile()
318        was not correctly checking the subroutine for matching a non-empty string.
320    14. The checks for overrunning compiling workspace could trigger after an
321        overrun had occurred. This is a "should never occur" error, but it can be
322        triggered by pathological patterns such as hundreds of nested parentheses.
323        The checks now trigger 100 bytes before the end of the workspace.
325    15. Fix typo in configure.ac: "srtoq" should be "strtoq".
328    Version 8.01 19-Jan-2010
329    ------------------------
331    1.  If a pattern contained a conditional subpattern with only one branch (in
332        particular, this includes all (*DEFINE) patterns), a call to pcre_study()
333        computed the wrong minimum data length (which is of course zero for such
334        subpatterns). This could cause incorrect "no match" results.
336    2.  For patterns such as (?i)a(?-i)b|c where an option setting at the start of
337        the pattern is reset in the first branch, pcre_compile() failed with
338        "internal error: code overflow at offset...". This happened only when
339        the reset was to the original external option setting. (An optimization
340        abstracts leading options settings into an external setting, which was the
341        cause of this.)
343    3.  A pattern such as ^(?!a(*SKIP)b) where a negative assertion contained one
344        of the verbs SKIP, PRUNE, or COMMIT, did not work correctly. When the
345        assertion pattern did not match (meaning that the assertion was true), it
346        was incorrectly treated as false if the SKIP had been reached during the
347        matching. This also applied to assertions used as conditions.
349    4.  If an item that is not supported by pcre_dfa_exec() was encountered in an
350        assertion subpattern, including such a pattern used as a condition,
351        unpredictable results occurred, instead of the error return
354    5.  The C++ GlobalReplace function was not working like Perl for the special
355        situation when an empty string is matched. It now does the fancy magic
356        stuff that is necessary.
358    6.  In pcre_internal.h, obsolete includes to setjmp.h and stdarg.h have been
359        removed. (These were left over from very, very early versions of PCRE.)
361    7.  Some cosmetic changes to the code to make life easier when compiling it
362        as part of something else:
364        (a) Change DEBUG to PCRE_DEBUG.
366        (b) In pcre_compile(), rename the member of the "branch_chain" structure
367            called "current" as "current_branch", to prevent a collision with the
368            Linux macro when compiled as a kernel module.
370        (c) In pcre_study(), rename the function set_bit() as set_table_bit(), to
371            prevent a collision with the Linux macro when compiled as a kernel
372            module.
374    8.  In pcre_compile() there are some checks for integer overflows that used to
375        cast potentially large values to (double). This has been changed to that
376        when building, a check for int64_t is made, and if it is found, it is used
377        instead, thus avoiding the use of floating point arithmetic. (There is no
378        other use of FP in PCRE.) If int64_t is not found, the fallback is to
379        double.
381    9.  Added two casts to avoid signed/unsigned warnings from VS Studio Express
382        2005 (difference between two addresses compared to an unsigned value).
384    10. Change the standard AC_CHECK_LIB test for libbz2 in configure.ac to a
385        custom one, because of the following reported problem in Windows:
387          - libbz2 uses the Pascal calling convention (WINAPI) for the functions
388              under Win32.
389          - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",
390              therefore missing the function definition.
391          - The compiler thus generates a "C" signature for the test function.
392          - The linker fails to find the "C" function.
393          - PCRE fails to configure if asked to do so against libbz2.
395    11. When running libtoolize from libtool-2.2.6b as part of autogen.sh, these
396        messages were output:
398          Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
399          rerunning libtoolize, to keep the correct libtool macros in-tree.
400          Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
402        I have done both of these things.
404    12. Although pcre_dfa_exec() does not use nearly as much stack as pcre_exec()
405        most of the time, it *can* run out if it is given a pattern that contains a
406        runaway infinite recursion. I updated the discussion in the pcrestack man
407        page.
409    13. Now that we have gone to the x.xx style of version numbers, the minor
410        version may start with zero. Using 08 or 09 is a bad idea because users
411        might check the value of PCRE_MINOR in their code, and 08 or 09 may be
412        interpreted as invalid octal numbers. I've updated the previous comment in
413        configure.ac, and also added a check that gives an error if 08 or 09 are
414        used.
416    14. Change 8.00/11 was not quite complete: code had been accidentally omitted,
417        causing partial matching to fail when the end of the subject matched \W
418        in a UTF-8 pattern where \W was quantified with a minimum of 3.
420    15. There were some discrepancies between the declarations in pcre_internal.h
421        of _pcre_is_newline(), _pcre_was_newline(), and _pcre_valid_utf8() and
422        their definitions. The declarations used "const uschar *" and the
423        definitions used USPTR. Even though USPTR is normally defined as "const
424        unsigned char *" (and uschar is typedeffed as "unsigned char"), it was
425        reported that: "This difference in casting confuses some C++ compilers, for
426        example, SunCC recognizes above declarations as different functions and
427        generates broken code for hbpcre." I have changed the declarations to use
428        USPTR.
430    16. GNU libtool is named differently on some systems. The autogen.sh script now
431        tries several variants such as glibtoolize (MacOSX) and libtoolize1x
432        (FreeBSD).
434    17. Applied Craig's patch that fixes an HP aCC compile error in pcre 8.00
435        (strtoXX undefined when compiling pcrecpp.cc). The patch contains this
436        comment: "Figure out how to create a longlong from a string: strtoll and
437        equivalent. It's not enough to call AC_CHECK_FUNCS: hpux has a strtoll, for
438        instance, but it only takes 2 args instead of 3!"
440    18. A subtle bug concerned with back references has been fixed by a change of
441        specification, with a corresponding code fix. A pattern such as
442        ^(xa|=?\1a)+$ which contains a back reference inside the group to which it
443        refers, was giving matches when it shouldn't. For example, xa=xaaa would
444        match that pattern. Interestingly, Perl (at least up to 5.11.3) has the
445        same bug. Such groups have to be quantified to be useful, or contained
446        inside another quantified group. (If there's no repetition, the reference
447        can never match.) The problem arises because, having left the group and
448        moved on to the rest of the pattern, a later failure that backtracks into
449        the group uses the captured value from the final iteration of the group
450        rather than the correct earlier one. I have fixed this in PCRE by forcing
451        any group that contains a reference to itself to be an atomic group; that
452        is, there cannot be any backtracking into it once it has completed. This is
453        similar to recursive and subroutine calls.
456    Version 8.00 19-Oct-09
457    ----------------------
459    1.  The table for translating pcre_compile() error codes into POSIX error codes
460        was out-of-date, and there was no check on the pcre_compile() error code
461        being within the table. This could lead to an OK return being given in
462        error.
464    2.  Changed the call to open a subject file in pcregrep from fopen(pathname,
465        "r") to fopen(pathname, "rb"), which fixed a problem with some of the tests
466        in a Windows environment.
468    3.  The pcregrep --count option prints the count for each file even when it is
469        zero, as does GNU grep. However, pcregrep was also printing all files when
470        --files-with-matches was added. Now, when both options are given, it prints
471        counts only for those files that have at least one match. (GNU grep just
472        prints the file name in this circumstance, but including the count seems
473        more useful - otherwise, why use --count?) Also ensured that the
474        combination -clh just lists non-zero counts, with no names.
476    4.  The long form of the pcregrep -F option was incorrectly implemented as
477        --fixed_strings instead of --fixed-strings. This is an incompatible change,
478        but it seems right to fix it, and I didn't think it was worth preserving
479        the old behaviour.
481    5.  The command line items --regex=pattern and --regexp=pattern were not
482        recognized by pcregrep, which required --regex pattern or --regexp pattern
483        (with a space rather than an '='). The man page documented the '=' forms,
484        which are compatible with GNU grep; these now work.
486    6.  No libpcreposix.pc file was created for pkg-config; there was just
487        libpcre.pc and libpcrecpp.pc. The omission has been rectified.
489    7.  Added #ifndef SUPPORT_UCP into the pcre_ucd.c module, to reduce its size
490        when UCP support is not needed, by modifying the Python script that
491        generates it from Unicode data files. This should not matter if the module
492        is correctly used as a library, but I received one complaint about 50K of
493        unwanted data. My guess is that the person linked everything into his
494        program rather than using a library. Anyway, it does no harm.
496    8.  A pattern such as /\x{123}{2,2}+/8 was incorrectly compiled; the trigger
497        was a minimum greater than 1 for a wide character in a possessive
498        repetition. The same bug could also affect patterns like /(\x{ff}{0,2})*/8
499        which had an unlimited repeat of a nested, fixed maximum repeat of a wide
500        character. Chaos in the form of incorrect output or a compiling loop could
501        result.
503    9.  The restrictions on what a pattern can contain when partial matching is
504        requested for pcre_exec() have been removed. All patterns can now be
505        partially matched by this function. In addition, if there are at least two
506        slots in the offset vector, the offset of the earliest inspected character
507        for the match and the offset of the end of the subject are set in them when
508        PCRE_ERROR_PARTIAL is returned.
510    10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is
511        synonymous with PCRE_PARTIAL, for backwards compatibility, and
512        PCRE_PARTIAL_HARD, which causes a partial match to supersede a full match,
513        and may be more useful for multi-segment matching.
515    11. Partial matching with pcre_exec() is now more intuitive. A partial match
516        used to be given if ever the end of the subject was reached; now it is
517        given only if matching could not proceed because another character was
518        needed. This makes a difference in some odd cases such as Z(*FAIL) with the
519        string "Z", which now yields "no match" instead of "partial match". In the
520        case of pcre_dfa_exec(), "no match" is given if every matching path for the
521        final character ended with (*FAIL).
523    12. Restarting a match using pcre_dfa_exec() after a partial match did not work
524        if the pattern had a "must contain" character that was already found in the
525        earlier partial match, unless partial matching was again requested. For
526        example, with the pattern /dog.(body)?/, the "must contain" character is
527        "g". If the first part-match was for the string "dog", restarting with
528        "sbody" failed. This bug has been fixed.
530    13. The string returned by pcre_dfa_exec() after a partial match has been
531        changed so that it starts at the first inspected character rather than the
532        first character of the match. This makes a difference only if the pattern
533        starts with a lookbehind assertion or \b or \B (\K is not supported by
534        pcre_dfa_exec()). It's an incompatible change, but it makes the two
535        matching functions compatible, and I think it's the right thing to do.
537    14. Added a pcredemo man page, created automatically from the pcredemo.c file,
538        so that the demonstration program is easily available in environments where
539        PCRE has not been installed from source.
541    15. Arranged to add -DPCRE_STATIC to cflags in libpcre.pc, libpcreposix.cp,
542        libpcrecpp.pc and pcre-config when PCRE is not compiled as a shared
543        library.
545    16. Added REG_UNGREEDY to the pcreposix interface, at the request of a user.
546        It maps to PCRE_UNGREEDY. It is not, of course, POSIX-compatible, but it
547        is not the first non-POSIX option to be added. Clearly some people find
548        these options useful.
550    17. If a caller to the POSIX matching function regexec() passes a non-zero
551        value for nmatch with a NULL value for pmatch, the value of
552        nmatch is forced to zero.
554    18. RunGrepTest did not have a test for the availability of the -u option of
555        the diff command, as RunTest does. It now checks in the same way as
556        RunTest, and also checks for the -b option.
558    19. If an odd number of negated classes containing just a single character
559        interposed, within parentheses, between a forward reference to a named
560        subpattern and the definition of the subpattern, compilation crashed with
561        an internal error, complaining that it could not find the referenced
562        subpattern. An example of a crashing pattern is /(?&A)(([^m])(?<A>))/.
563        [The bug was that it was starting one character too far in when skipping
564        over the character class, thus treating the ] as data rather than
565        terminating the class. This meant it could skip too much.]
567    20. Added PCRE_NOTEMPTY_ATSTART in order to be able to correctly implement the
568        /g option in pcretest when the pattern contains \K, which makes it possible
569        to have an empty string match not at the start, even when the pattern is
570        anchored. Updated pcretest and pcredemo to use this option.
572    21. If the maximum number of capturing subpatterns in a recursion was greater
573        than the maximum at the outer level, the higher number was returned, but
574        with unset values at the outer level. The correct (outer level) value is
575        now given.
577    22. If (*ACCEPT) appeared inside capturing parentheses, previous releases of
578        PCRE did not set those parentheses (unlike Perl). I have now found a way to
579        make it do so. The string so far is captured, making this feature
580        compatible with Perl.
582    23. The tests have been re-organized, adding tests 11 and 12, to make it
583        possible to check the Perl 5.10 features against Perl 5.10.
585    24. Perl 5.10 allows subroutine calls in lookbehinds, as long as the subroutine
586        pattern matches a fixed length string. PCRE did not allow this; now it
587        does. Neither allows recursion.
589    25. I finally figured out how to implement a request to provide the minimum
590        length of subject string that was needed in order to match a given pattern.
591        (It was back references and recursion that I had previously got hung up
592        on.) This code has now been added to pcre_study(); it finds a lower bound
593        to the length of subject needed. It is not necessarily the greatest lower
594        bound, but using it to avoid searching strings that are too short does give
595        some useful speed-ups. The value is available to calling programs via
596        pcre_fullinfo().
598    26. While implementing 25, I discovered to my embarrassment that pcretest had
599        not been passing the result of pcre_study() to pcre_dfa_exec(), so the
600        study optimizations had never been tested with that matching function.
601        Oops. What is worse, even when it was passed study data, there was a bug in
602        pcre_dfa_exec() that meant it never actually used it. Double oops. There
603        were also very few tests of studied patterns with pcre_dfa_exec().
605    27. If (?| is used to create subpatterns with duplicate numbers, they are now
606        allowed to have the same name, even if PCRE_DUPNAMES is not set. However,
607        on the other side of the coin, they are no longer allowed to have different
608        names, because these cannot be distinguished in PCRE, and this has caused
609        confusion. (This is a difference from Perl.)
611    28. When duplicate subpattern names are present (necessarily with different
612        numbers, as required by 27 above), and a test is made by name in a
613        conditional pattern, either for a subpattern having been matched, or for
614        recursion in such a pattern, all the associated numbered subpatterns are
615        tested, and the overall condition is true if the condition is true for any
616        one of them. This is the way Perl works, and is also more like the way
617        testing by number works.
620    Version 7.9 11-Apr-09
621    ---------------------
623    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
624        (pcretest), all targets were linked against these libraries. This included
625        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
626        libraries. This caused unwanted dependencies to be created. This problem
627        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
628        pcretest is linked with readline.
630    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
631        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
632        moved outside it again, because FALSE and TRUE are already defined in AIX,
633        but BOOL is not.
635    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
636        PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
638    4.  The pcregrep documentation said spaces were inserted as well as colons (or
639        hyphens) following file names and line numbers when outputting matching
640        lines. This is not true; no spaces are inserted. I have also clarified the
641        wording for the --colour (or --color) option.
643    5.  In pcregrep, when --colour was used with -o, the list of matching strings
644        was not coloured; this is different to GNU grep, so I have changed it to be
645        the same.
647    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
648        each matching line was coloured. Now it goes on to look for further matches
649        of any of the test patterns, which is the same behaviour as GNU grep.
651    7.  A pattern that could match an empty string could cause pcregrep to loop; it
652        doesn't make sense to accept an empty string match in pcregrep, so I have
653        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
654        seems to be how GNU grep behaves.
656    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
657        start or after a newline", because the conditional assertion was not being
658        correctly handled. The rule now is that both the assertion and what follows
659        in the first alternative must satisfy the test.
661    9.  If auto-callout was enabled in a pattern with a conditional group whose
662        condition was an assertion, PCRE could crash during matching, both with
663        pcre_exec() and pcre_dfa_exec().
665    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
666        used for matching.
668    11. Unicode property support in character classes was not working for
669        characters (bytes) greater than 127 when not in UTF-8 mode.
671    12. Added the -M command line option to pcretest.
673    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
675    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
677    16. Added comments and documentation about mis-use of no_arg in the C++
678        wrapper.
680    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
681        from Martin Jerabek that uses macro names for all relevant character and
682        string constants.
684    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
685        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
686        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
687        these, but not everybody uses configure.
689    19. A conditional group that had only one branch was not being correctly
690        recognized as an item that could match an empty string. This meant that an
691        enclosing group might also not be so recognized, causing infinite looping
692        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
693        with the subject "ab", where knowledge that the repeated group can match
694        nothing is needed in order to break the loop.
696    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
697        exec(), but without supplying a callout function, matching went wrong.
699    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
700        leak if the size of the offset vector was greater than 30. When the vector
701        is smaller, the saved offsets during recursion go onto a local stack
702        vector, but for larger vectors malloc() is used. It was failing to free
703        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
704        error, in fact).
706    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
707        heapframe that is used only when UTF-8 support is enabled. This caused no
708        problem, but was untidy.
710    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
711        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
712        included within another project.
714    24. Steven Van Ingelgem's patches to add more options to the CMake support,
715        slightly modified by me:
717          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
718              not building pcregrep.
720          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
721              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
723    25. Forward references, both numeric and by name, in patterns that made use of
724        duplicate group numbers, could behave incorrectly or give incorrect errors,
725        because when scanning forward to find the reference group, PCRE was not
726        taking into account the duplicate group numbers. A pattern such as
727        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
729    26. Changed a few more instances of "const unsigned char *" to USPTR, making
730        the feature of a custom pointer more persuasive (as requested by a user).
732    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
733        pcretest.c, inside #ifndefs, because it seems they are sometimes already
734        pre-defined.
736    28. Added support for (*UTF8) at the start of a pattern.
738    29. Arrange for flags added by the "release type" setting in CMake to be shown
739        in the configuration summary.
742    Version 7.8 05-Sep-08
743    ---------------------
745    1.  Replaced UCP searching code with optimized version as implemented for Ad
746        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
747        stage table and inline lookup instead of a function, giving speed ups of 2
748        to 5 times on some simple patterns that I tested. Permission was given to
749        distribute the MultiStage2.py script that generates the tables (it's not in
750        the tarball, but is in the Subversion repository).
752    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
753        scripts.
755    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
756        a group with a zero qualifier. The result of the study could be incorrect,
757        or the function might crash, depending on the pattern.
759    4.  Caseless matching was not working for non-ASCII characters in back
760        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
761        It now works when Unicode Property Support is available.
763    5.  In pcretest, an escape such as \x{de} in the data was always generating
764        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
765        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
766        truncation.
768    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
770    7.  Added two (int) casts to pcregrep when printing the difference of two
771        pointers, in case they are 64-bit values.
773    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
774        test 2 if it fails.
776    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
777        and a #define of that name to empty if it is not externally set. This is to
778        allow users of MSVC to set it if necessary.
780    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
781        the convenience functions in the pcre_get.c source file.
783    11. An option change at the start of a pattern that had top-level alternatives
784        could cause overwriting and/or a crash. This command provoked a crash in
785        some environments:
787          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
789        This potential security problem was recorded as CVE-2008-2371.
791    12. For a pattern where the match had to start at the beginning or immediately
792        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
793        pcre_dfa_exec() could read past the end of the passed subject if there was
794        no match. To help with detecting such bugs (e.g. with valgrind), I modified
795        pcretest so that it places the subject at the end of its malloc-ed buffer.
797    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
798        exec() might read past the end of the data buffer in UTF-8 mode.
800    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
801        the data contained the byte 0x85 as part of a UTF-8 character within its
802        first line. This applied both to normal and DFA matching.
804    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
805        /^[^d]*?$/8 failed to match "abc".
807    16. Added a missing copyright notice to pcrecpp_internal.h.
809    17. Make it more clear in the documentation that values returned from
810        pcre_exec() in ovector are byte offsets, not character counts.
812    18. Tidied a few places to stop certain compilers from issuing warnings.
814    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
815        supplied by Stefan Weber. I made a further small update for 7.8 because
816        there is a change of source arrangements: the pcre_searchfuncs.c module is
817        replaced by pcre_ucd.c.
820    Version 7.7 07-May-08
821    ---------------------
823    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
824        a string to a long long, pretend we don't even have a long long." This is
825        done by checking for the strtoq, strtoll, and _strtoi64 functions.
827    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
828        pre-7.6 versions, which defined a global no_arg variable instead of putting
829        it in the RE class. (See also #8 below.)
831    3.  Remove a line of dead code, identified by coverity and reported by Nuno
832        Lopes.
834    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
836        (1) The include/exclude patterns were being applied to the whole pathnames
837            of files, instead of just to the final components.
839        (2) If there was more than one level of directory, the subdirectories were
840            skipped unless they satisfied the include/exclude conditions. This is
841            inconsistent with GNU grep (and could even be seen as contrary to the
842            pcregrep specification - which I improved to make it absolutely clear).
843            The action now is always to scan all levels of directory, and just
844            apply the include/exclude patterns to regular files.
846    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
847        --exclude_dir in the tests to avoid scanning .svn directories.
849    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
850        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
851        doesn't support NULs in patterns.
853    7.  Added some missing "const"s to declarations of static tables in
854        pcre_compile.c and pcre_dfa_exec.c.
856    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
857        caused by fix #2  above. (Subsequently also a second patch to fix the
858        first patch. And a third patch - this was a messy problem.)
860    9.  Applied Craig's patch to remove the use of push_back().
862    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
863        matching function regexec().
865    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
866        which, however, unlike Perl's \g{...}, are subroutine calls, not back
867        references. PCRE supports relative numbers with this syntax (I don't think
868        Oniguruma does).
870    12. Previously, a group with a zero repeat such as (...){0} was completely
871        omitted from the compiled regex. However, this means that if the group
872        was called as a subroutine from elsewhere in the pattern, things went wrong
873        (an internal error was given). Such groups are now left in the compiled
874        pattern, with a new opcode that causes them to be skipped at execution
875        time.
877    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
878        to the way PCRE behaves:
880        (a) A lone ] character is dis-allowed (Perl treats it as data).
882        (b) A back reference to an unmatched subpattern matches an empty string
883            (Perl fails the current match path).
885        (c) A data ] in a character class must be notated as \] because if the
886            first data character in a class is ], it defines an empty class. (In
887            Perl it is not possible to have an empty class.) The empty class []
888            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
889            The negative empty class [^] matches any one character, independently
890            of the DOTALL setting.
892    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
893        non-existent subpattern following a character class starting with ']' and
894        containing () gave an internal compiling error instead of "reference to
895        non-existent subpattern". Fortunately, when the pattern did exist, the
896        compiled code was correct. (When scanning forwards to check for the
897        existencd of the subpattern, it was treating the data ']' as terminating
898        the class, so got the count wrong. When actually compiling, the reference
899        was subsequently set up correctly.)
901    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
902        it was being rejected as not supported by pcre_dfa_exec(), even though
903        other assertions are supported. I have made pcre_dfa_exec() support
904        (*FAIL).
906    16. The implementation of 13c above involved the invention of a new opcode,
907        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
908        cannot be changed at match time, I realized I could make a small
909        improvement to matching performance by compiling OP_ALLANY instead of
910        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
911        on the OP_ANY path.
913    17. Compiling pcretest on Windows with readline support failed without the
914        following two fixes: (1) Make the unistd.h include conditional on
915        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
917    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
918        ncurses library to be included for pcretest when ReadLine support is
919        requested, but also to allow for it to be overridden. This patch came from
920        Daniel Bergström.
922    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
923        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
924        any errors with the current Unicode tables. Thanks to Peter Kankowski for
925        spotting this.
928    Version 7.6 28-Jan-08
929    ---------------------
931    1.  A character class containing a very large number of characters with
932        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
933        overflow.
935    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
936        HAVE_LONG_LONG is not defined.
938    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
939        bring them up to date and include new features. This patch includes:
941        - Fixed PH's badly added libz and libbz2 support.
942        - Fixed a problem with static linking.
943        - Added pcredemo. [But later removed - see 7 below.]
944        - Fixed dftables problem and added an option.
945        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
946            HAVE_LONG_LONG.
947        - Added readline support for pcretest.
948        - Added an listing of the option settings after cmake has run.
950    4.  A user submitted a patch to Makefile that makes it easy to create
951        "pcre.dll" under mingw when using Configure/Make. I added stuff to
952        Makefile.am that cause it to include this special target, without
953        affecting anything else. Note that the same mingw target plus all
954        the other distribution libraries and programs are now supported
955        when configuring with CMake (see 6 below) instead of with
956        Configure/Make.
958    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
959        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
960        exported in the Windows port". It has not yet been confirmed that the patch
961        solves the problem, but it does no harm.
963    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
964        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
965        with CMake, and also correct the comment about stack recursion.
967    7.  Remove the automatic building of pcredemo from the ./configure system and
968        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
969        of a program that users should build themselves after PCRE is installed, so
970        building it automatically is not really right. What is more, it gave
971        trouble in some build environments.
973    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
976    Version 7.5 10-Jan-08
977    ---------------------
979    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
980        values in parens when parsing an RE using the C++ wrapper."
982    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
983        Characters greater than 255 were excluded from the class instead of being
984        included.
986    3.  The same bug as (2) above applied to negated POSIX classes such as
987        [:^space:].
989    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
990        defined or documented. It seems to have been a typo for PCRE_STATIC, so
991        I have changed it.
993    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
994        first named subpattern) and a construct such as (?&a) would reference the
995        first named subpattern whose name started with "a" (in other words, the
996        length check was missing). Both these problems are fixed. "Subpattern name
997        expected" is now given for (?&) (a zero-length name), and this patch also
998        makes it give the same error for \k'' (previously it complained that that
999        was a reference to a non-existent subpattern).
1001    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
1002        this is right because (?- can be followed by option settings as well as by
1003        digits. I have, however, made the messages clearer.
1005    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
1006        than the number used in the conditional) now cause a compile-time error.
1007        This is actually not compatible with Perl, which accepts such patterns, but
1008        treats the conditional as always being FALSE (as PCRE used to), but it
1009        seems to me that giving a diagnostic is better.
1011    8.  Change "alphameric" to the more common word "alphanumeric" in comments
1012        and messages.
1014    9.  Fix two occurrences of "backslash" in comments that should have been
1015        "backspace".
1017    10. Remove two redundant lines of code that can never be obeyed (their function
1018        was moved elsewhere).
1020    11. The program that makes PCRE's Unicode character property table had a bug
1021        which caused it to generate incorrect table entries for sequences of
1022        characters that have the same character type, but are in different scripts.
1023        It amalgamated them into a single range, with the script of the first of
1024        them. In other words, some characters were in the wrong script. There were
1025        thirteen such cases, affecting characters in the following ranges:
1027          U+002b0 - U+002c1
1028          U+0060c - U+0060d
1029          U+0061e - U+00612
1030          U+0064b - U+0065e
1031          U+0074d - U+0076d
1032          U+01800 - U+01805
1033          U+01d00 - U+01d77
1034          U+01d9b - U+01dbf
1035          U+0200b - U+0200f
1036          U+030fc - U+030fe
1037          U+03260 - U+0327f
1038          U+0fb46 - U+0fbb1
1039          U+10450 - U+1049d
1041    12. The -o option (show only the matching part of a line) for pcregrep was not
1042        compatible with GNU grep in that, if there was more than one match in a
1043        line, it showed only the first of them. It now behaves in the same way as
1044        GNU grep.
1046    13. If the -o and -v options were combined for pcregrep, it printed a blank
1047        line for every non-matching line. GNU grep prints nothing, and pcregrep now
1048        does the same. The return code can be used to tell if there were any
1049        non-matching lines.
1051    14. Added --file-offsets and --line-offsets to pcregrep.
1053    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
1054        infinitely looping recursion. The bug was that positive lookaheads were not
1055        being skipped when checking for a possible empty match (negative lookaheads
1056        and both kinds of lookbehind were skipped).
1058    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
1059        inclusion of <windows.h> to before rather than after the definition of
1060        INVALID_FILE_ATTRIBUTES (patch from David Byron).
1062    17. Specifying a possessive quantifier with a specific limit for a Unicode
1063        character property caused pcre_compile() to compile bad code, which led at
1064        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
1065        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
1066        caused the error; without that there was no problem.
1068    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
1070    19. Added --enable-pcretest-libreadline.
1072    20. In pcrecpp.cc, the variable 'count' was incremented twice in
1073        RE::GlobalReplace(). As a result, the number of replacements returned was
1074        double what it should be. I removed one of the increments, but Craig sent a
1075        later patch that removed the other one (the right fix) and added unit tests
1076        that check the return values (which was not done before).
1078    21. Several CMake things:
1080        (1) Arranged that, when cmake is used on Unix, the libraries end up with
1081            the names libpcre and libpcreposix, not just pcre and pcreposix.
1083        (2) The above change means that pcretest and pcregrep are now correctly
1084            linked with the newly-built libraries, not previously installed ones.
1088    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
1089        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
1090        UTF-8 newline character). The key issue is that the pattern starts .*;
1091        this means that the match must be either at the beginning, or after a
1092        newline. The bug was in the code for advancing after a failed match and
1093        checking that the new position followed a newline. It was not taking
1094        account of UTF-8 characters correctly.
1096    23. PCRE was behaving differently from Perl in the way it recognized POSIX
1097        character classes. PCRE was not treating the sequence [:...:] as a
1098        character class unless the ... were all letters. Perl, however, seems to
1099        allow any characters between [: and :], though of course it rejects as
1100        unknown any "names" that contain non-letters, because all the known class
1101        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
1102        for example, whereas PCRE did not - it did not recognize a POSIX character
1103        class. This seemed a bit dangerous, so the code has been changed to be
1104        closer to Perl. The behaviour is not identical to Perl, because PCRE will
1105        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
1106        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
1107        Perl does, and where it didn't before.
1109    24. Rewrite so as to remove the single use of %n from pcregrep because in some
1110        Windows environments %n is disabled by default.
1113    Version 7.4 21-Sep-07
1114    ---------------------
1116    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
1117        means that a class such as [\s] counted as "explicit reference to CR or
1118        LF". That isn't really right - the whole point of the change was to try to
1119        help when there was an actual mention of one of the two characters. So now
1120        the change happens only if \r or \n (or a literal CR or LF) character is
1121        encountered.
1123    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
1124        of both had grown to the point where there were only 3 bits left.
1125        Fortunately, there was spare space in the data structure, and so I have
1126        moved the internal flags into a new 16-bit field to free up more option
1127        bits.
1129    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
1130        but did not set the internal JCHANGED flag - either of these is enough to
1131        control the way the "get" function works - but the PCRE_INFO_JCHANGED
1132        facility is supposed to tell if (?J) was ever used, so now (?J) at the
1133        start sets both bits.
1135    4.  Added options (at build time, compile time, exec time) to change \R from
1136        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
1138    5.  doc/pcresyntax.html was missing from the distribution.
1140    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
1141        compatibility, even though it is no longer used.
1143    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
1144        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
1145        windows.h file is present (where different names are used). [This was
1146        reversed later after testing - see 16 below.]
1148    8.  Changed all #include <config.h> to #include "config.h". There were also
1149        some further <pcre.h> cases that I changed to "pcre.h".
1151    9.  When pcregrep was used with the --colour option, it missed the line ending
1152        sequence off the lines that it output.
1154    10. It was pointed out to me that arrays of string pointers cause lots of
1155        relocations when a shared library is dynamically loaded. A technique of
1156        using a single long string with a table of offsets can drastically reduce
1157        these. I have refactored PCRE in four places to do this. The result is
1158        dramatic:
1160          Originally:                          290
1161          After changing UCP table:            187
1162          After changing error message table:   43
1163          After changing table of "verbs"       36
1164          After changing table of Posix names   22
1166        Thanks to the folks working on Gregex for glib for this insight.
1168    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
1169        unicode-properties was also set.
1171    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
1173    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
1174        checked only for CRLF.
1176    14. Added casts to pcretest.c to avoid compiler warnings.
1178    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
1180    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
1181        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
1182        entirely. This removes changes made in 7 above.
1184    17. The CMake files have been updated, and there is now more information about
1185        building with CMake in the NON-UNIX-USE document.
1188    Version 7.3 28-Aug-07
1189    ---------------------
1191     1. In the rejigging of the build system that eventually resulted in 7.1, the
1192        line "#include <pcre.h>" was included in pcre_internal.h. The use of angle
1193        brackets there is not right, since it causes compilers to look for an
1194        installed pcre.h, not the version that is in the source that is being
1195        compiled (which of course may be different). I have changed it back to:
1197          #include "pcre.h"
1199        I have a vague recollection that the change was concerned with compiling in
1200        different directories, but in the new build system, that is taken care of
1201        by the VPATH setting the Makefile.
1203     2. The pattern .*$ when run in not-DOTALL UTF-8 mode with newline=any failed
1204        when the subject happened to end in the byte 0x85 (e.g. if the last
1205        character was \x{1ec5}). *Character* 0x85 is one of the "any" newline
1206        characters but of course it shouldn't be taken as a newline when it is part
1207        of another character. The bug was that, for an unlimited repeat of . in
1208        not-DOTALL UTF-8 mode, PCRE was advancing by bytes rather than by
1209        characters when looking for a newline.
1211     3. A small performance improvement in the DOTALL UTF-8 mode .* case.
1213     4. Debugging: adjusted the names of opcodes for different kinds of parentheses
1214        in debug output.
1216     5. Arrange to use "%I64d" instead of "%lld" and "%I64u" instead of "%llu" for
1217        long printing in the pcrecpp unittest when running under MinGW.
1219     6. ESC_K was left out of the EBCDIC table.
1221     7. Change 7.0/38 introduced a new limit on the number of nested non-capturing
1222        parentheses; I made it 1000, which seemed large enough. Unfortunately, the
1223        limit also applies to "virtual nesting" when a pattern is recursive, and in
1224        this case 1000 isn't so big. I have been able to remove this limit at the
1225        expense of backing off one optimization in certain circumstances. Normally,
1226        when pcre_exec() would call its internal match() function recursively and
1227        immediately return the result unconditionally, it uses a "tail recursion"
1228        feature to save stack. However, when a subpattern that can match an empty
1229        string has an unlimited repetition quantifier, it no longer makes this
1230        optimization. That gives it a stack frame in which to save the data for
1231        checking that an empty string has been matched. Previously this was taken
1232        from the 1000-entry workspace that had been reserved. So now there is no
1233        explicit limit, but more stack is used.
1235     8. Applied Daniel's patches to solve problems with the import/export magic
1236        syntax that is required for Windows, and which was going wrong for the
1237        pcreposix and pcrecpp parts of the library. These were overlooked when this
1238        problem was solved for the main library.
1240     9. There were some crude static tests to avoid integer overflow when computing
1241        the size of patterns that contain repeated groups with explicit upper
1242        limits. As the maximum quantifier is 65535, the maximum group length was
1243        set at 30,000 so that the product of these two numbers did not overflow a
1244        32-bit integer. However, it turns out that people want to use groups that
1245        are longer than 30,000 bytes (though not repeat them that many times).
1246        Change 7.0/17 (the refactoring of the way the pattern size is computed) has
1247        made it possible to implement the integer overflow checks in a much more
1248        dynamic way, which I have now done. The artificial limitation on group
1249        length has been removed - we now have only the limit on the total length of
1250        the compiled pattern, which depends on the LINK_SIZE setting.
1252    10. Fixed a bug in the documentation for get/copy named substring when
1253        duplicate names are permitted. If none of the named substrings are set, the
1254        functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an
1255        empty string.
1257    11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E
1258        instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,
1259        because the ] is interpreted as the first data character and the
1260        terminating ] is not found. PCRE has been made compatible with Perl in this
1261        regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could
1262        cause memory overwriting.
1264    10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty
1265        string has been matched (to stop an infinite loop). It was not recognizing
1266        a conditional subpattern that could match an empty string if that
1267        subpattern was within another subpattern. For example, it looped when
1268        trying to match  (((?(1)X|))*)  but it was OK with  ((?(1)X|)*)  where the
1269        condition was not nested. This bug has been fixed.
1271    12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack
1272        past the start of the subject in the presence of bytes with the top bit
1273        set, for example "\x8aBCD".
1275    13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
1276        (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
1278    14. Optimized (?!) to (*FAIL).
1280    15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
1281        This restricts code points to be within the range 0 to 0x10FFFF, excluding
1282        the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
1283        full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
1284        does: it's just the validity check that is more restrictive.
1286    16. Inserted checks for integer overflows during escape sequence (backslash)
1287        processing, and also fixed erroneous offset values for syntax errors during
1288        backslash processing.
1290    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
1291        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
1293    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
1294        caused an overrun.
1296    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
1297        something other than just ASCII characters) inside a group that had an
1298        unlimited repeat caused a loop at compile time (while checking to see
1299        whether the group could match an empty string).
1301    20. Debugging a pattern containing \p or \P could cause a crash. For example,
1302        [\P{Any}] did so. (Error in the code for printing property names.)
1304    21. An orphan \E inside a character class could cause a crash.
1306    22. A repeated capturing bracket such as (A)? could cause a wild memory
1307        reference during compilation.
1309    23. There are several functions in pcre_compile() that scan along a compiled
1310        expression for various reasons (e.g. to see if it's fixed length for look
1311        behind). There were bugs in these functions when a repeated \p or \P was
1312        present in the pattern. These operators have additional parameters compared
1313        with \d, etc, and these were not being taken into account when moving along
1314        the compiled data. Specifically:
1316        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
1317            length.
1319        (b) An item such as \pL+ within a repeated group could cause crashes or
1320            loops.
1322        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
1323            "reference to non-existent subpattern" error.
1325        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
1327    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
1328        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
1330    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
1332    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
1333        character were causing crashes (broken optimization).
1335    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
1336        \p or \P) caused a compile-time loop.
1338    28. More problems have arisen in unanchored patterns when CRLF is a valid line
1339        break. For example, the unstudied pattern [\r\n]A does not match the string
1340        "\r\nA" because change 7.0/46 below moves the current point on by two
1341        characters after failing to match at the start. However, the pattern \nA
1342        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
1343        the same is true. There doesn't seem any very clean way out of this, but
1344        what I have chosen to do makes the common cases work: PCRE now takes note
1345        of whether there can be an explicit match for \r or \n anywhere in the
1346        pattern, and if so, 7.0/46 no longer applies. As part of this change,
1347        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
1348        pattern has explicit CR or LF references.
1350    29. Added (*CR) etc for changing newline setting at start of pattern.
1353    Version 7.2 19-Jun-07
1354    ---------------------
1356     1. If the fr_FR locale cannot be found for test 3, try the "french" locale,
1357        which is apparently normally available under Windows.
1359     2. Re-jig the pcregrep tests with different newline settings in an attempt
1360        to make them independent of the local environment's newline setting.
1362     3. Add code to configure.ac to remove -g from the CFLAGS default settings.
1364     4. Some of the "internals" tests were previously cut out when the link size
1365        was not 2, because the output contained actual offsets. The recent new
1366        "Z" feature of pcretest means that these can be cut out, making the tests
1367        usable with all link sizes.
1369     5. Implemented Stan Switzer's goto replacement for longjmp() when not using
1370        stack recursion. This gives a massive performance boost under BSD, but just
1371        a small improvement under Linux. However, it saves one field in the frame
1372        in all cases.
1374     6. Added more features from the forthcoming Perl 5.10:
1376        (a) (?-n) (where n is a string of digits) is a relative subroutine or
1377            recursion call. It refers to the nth most recently opened parentheses.
1379        (b) (?+n) is also a relative subroutine call; it refers to the nth next
1380            to be opened parentheses.
1382        (c) Conditions that refer to capturing parentheses can be specified
1383            relatively, for example, (?(-2)... or (?(+3)...
1385        (d) \K resets the start of the current match so that everything before
1386            is not part of it.
1388        (e) \k{name} is synonymous with \k<name> and \k'name' (.NET compatible).
1390        (f) \g{name} is another synonym - part of Perl 5.10's unification of
1391            reference syntax.
1393        (g) (?| introduces a group in which the numbering of parentheses in each
1394            alternative starts with the same number.
1396        (h) \h, \H, \v, and \V match horizontal and vertical whitespace.
1398     7. Added two new calls to pcre_fullinfo(): PCRE_INFO_OKPARTIAL and
1401     8. A pattern such as  (.*(.)?)*  caused pcre_exec() to fail by either not
1402        terminating or by crashing. Diagnosed by Viktor Griph; it was in the code
1403        for detecting groups that can match an empty string.
1405     9. A pattern with a very large number of alternatives (more than several
1406        hundred) was running out of internal workspace during the pre-compile
1407        phase, where pcre_compile() figures out how much memory will be needed. A
1408        bit of new cunning has reduced the workspace needed for groups with
1409        alternatives. The 1000-alternative test pattern now uses 12 bytes of
1410        workspace instead of running out of the 4096 that are available.
1412    10. Inserted some missing (unsigned int) casts to get rid of compiler warnings.
1414    11. Applied patch from Google to remove an optimization that didn't quite work.
1415        The report of the bug said:
1417          pcrecpp::RE("a*").FullMatch("aaa") matches, while
1418          pcrecpp::RE("a*?").FullMatch("aaa") does not, and
1419          pcrecpp::RE("a*?\\z").FullMatch("aaa") does again.
1421    12. If \p or \P was used in non-UTF-8 mode on a character greater than 127
1422        it matched the wrong number of bytes.
1425    Version 7.1 24-Apr-07
1426  ---------------------  ---------------------
1428   1. Applied Bob Rossi and Daniel G's patches to convert the build system to one   1. Applied Bob Rossi and Daniel G's patches to convert the build system to one
# Line 135  Version 7.1 12-Mar-07 Line 1556  Version 7.1 12-Mar-07
1556      was because its rules for how to advance for /g after matching an empty      was because its rules for how to advance for /g after matching an empty
1557      string at the end of a line did not allow for this case. They now check for      string at the end of a line did not allow for this case. They now check for
1558      it specially.      it specially.
1560  20. pcretest is supposed to handle patterns and data of any length, by  20. pcretest is supposed to handle patterns and data of any length, by
1561      extending its buffers when necessary. It was getting this wrong when the      extending its buffers when necessary. It was getting this wrong when the
1562      buffer for a data line had to be extended.      buffer for a data line had to be extended.
1564  21. Added PCRE_NEWLINE_ANYCRLF which is like ANY, but matches only CR, LF, or  21. Added PCRE_NEWLINE_ANYCRLF which is like ANY, but matches only CR, LF, or
1565      CRLF as a newline sequence.      CRLF as a newline sequence.
1567    22. Code for handling Unicode properties in pcre_dfa_exec() wasn't being cut
1568        out by #ifdef SUPPORT_UCP. This did no harm, as it could never be used, but
1569        I have nevertheless tidied it up.
1571    23. Added some casts to kill warnings from HP-UX ia64 compiler.
1573    24. Added a man page for pcre-config.
1576  Version 7.0 19-Dec-06  Version 7.0 19-Dec-06

Removed from v.149  
changed lines
  Added in v.591

  ViewVC Help
Powered by ViewVC 1.1.5