ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 105 by ph10, Tue Mar 6 16:32:53 2007 UTC revision 593 by ph10, Sun May 1 08:14:24 2011 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 7.1 05-Mar-07  Version 8.13 30-Apr-2011
5    ------------------------
7    1.  The Unicode data tables have been updated to Unicode 6.0.0.
9    2.  Two minor typos in pcre_internal.h have been fixed.
12    Version 8.12 15-Jan-2011
13    ------------------------
15    1.  Fixed some typos in the markup of the man pages, and wrote a script that
16        checks for such things as part of the documentation building process.
18    2.  On a big-endian 64-bit system, pcregrep did not correctly process the
19        --match-limit and --recursion-limit options (added for 8.11). In
20        particular, this made one of the standard tests fail. (The integer value
21        went into the wrong half of a long int.)
23    3.  If the --colour option was given to pcregrep with -v (invert match), it
24        did strange things, either producing crazy output, or crashing. It should,
25        of course, ignore a request for colour when reporting lines that do not
26        match.
28    4.  Another pcregrep bug caused similar problems if --colour was specified with
29        -M (multiline) and the pattern match finished with a line ending.
31    5.  In pcregrep, when a pattern that ended with a literal newline sequence was
32        matched in multiline mode, the following line was shown as part of the
33        match. This seems wrong, so I have changed it.
35    6.  Another pcregrep bug in multiline mode, when --colour was specified, caused
36        the check for further matches in the same line (so they could be coloured)
37        to overrun the end of the current line. If another match was found, it was
38        incorrectly shown (and then shown again when found in the next line).
40    7.  If pcregrep was compiled under Windows, there was a reference to the
41        function pcregrep_exit() before it was defined. I am assuming this was
42        the cause of the "error C2371: 'pcregrep_exit' : redefinition;" that was
43        reported by a user. I've moved the definition above the reference.
46    Version 8.11 10-Dec-2010
47    ------------------------
49    1.  (*THEN) was not working properly if there were untried alternatives prior
50        to it in the current branch. For example, in ((a|b)(*THEN)(*F)|c..) it
51        backtracked to try for "b" instead of moving to the next alternative branch
52        at the same level (in this case, to look for "c"). The Perl documentation
53        is clear that when (*THEN) is backtracked onto, it goes to the "next
54        alternative in the innermost enclosing group".
56    2.  (*COMMIT) was not overriding (*THEN), as it does in Perl. In a pattern
57        such as   (A(*COMMIT)B(*THEN)C|D)  any failure after matching A should
58        result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and
59        (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides
60        (*THEN).
62    3.  If \s appeared in a character class, it removed the VT character from
63        the class, even if it had been included by some previous item, for example
64        in [\x00-\xff\s]. (This was a bug related to the fact that VT is not part
65        of \s, but is part of the POSIX "space" class.)
67    4.  A partial match never returns an empty string (because you can always
68        match an empty string at the end of the subject); however the checking for
69        an empty string was starting at the "start of match" point. This has been
70        changed to the "earliest inspected character" point, because the returned
71        data for a partial match starts at this character. This means that, for
72        example, /(?<=abc)def/ gives a partial match for the subject "abc"
73        (previously it gave "no match").
75    5.  Changes have been made to the way PCRE_PARTIAL_HARD affects the matching
76        of $, \z, \Z, \b, and \B. If the match point is at the end of the string,
77        previously a full match would be given. However, setting PCRE_PARTIAL_HARD
78        has an implication that the given string is incomplete (because a partial
79        match is preferred over a full match). For this reason, these items now
80        give a partial match in this situation. [Aside: previously, the one case
81        /t\b/ matched against "cat" with PCRE_PARTIAL_HARD set did return a partial
82        match rather than a full match, which was wrong by the old rules, but is
83        now correct.]
85    6.  There was a bug in the handling of #-introduced comments, recognized when
86        PCRE_EXTENDED is set, when PCRE_NEWLINE_ANY and PCRE_UTF8 were also set.
87        If a UTF-8 multi-byte character included the byte 0x85 (e.g. +U0445, whose
88        UTF-8 encoding is 0xd1,0x85), this was misinterpreted as a newline when
89        scanning for the end of the comment. (*Character* 0x85 is an "any" newline,
90        but *byte* 0x85 is not, in UTF-8 mode). This bug was present in several
91        places in pcre_compile().
93    7.  Related to (6) above, when pcre_compile() was skipping #-introduced
94        comments when looking ahead for named forward references to subpatterns,
95        the only newline sequence it recognized was NL. It now handles newlines
96        according to the set newline convention.
98    8.  SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the
99        former, but used strtoul(), whereas pcretest avoided strtoul() but did not
100        cater for a lack of strerror(). These oversights have been fixed.
102    9.  Added --match-limit and --recursion-limit to pcregrep.
104    10. Added two casts needed to build with Visual Studio when NO_RECURSE is set.
106    11. When the -o option was used, pcregrep was setting a return code of 1, even
107        when matches were found, and --line-buffered was not being honoured.
109    12. Added an optional parentheses number to the -o and --only-matching options
110        of pcregrep.
112    13. Imitating Perl's /g action for multiple matches is tricky when the pattern
113        can match an empty string. The code to do it in pcretest and pcredemo
114        needed fixing:
116        (a) When the newline convention was "crlf", pcretest got it wrong, skipping
117            only one byte after an empty string match just before CRLF (this case
118            just got forgotten; "any" and "anycrlf" were OK).
120        (b) The pcretest code also had a bug, causing it to loop forever in UTF-8
121            mode when an empty string match preceded an ASCII character followed by
122            a non-ASCII character. (The code for advancing by one character rather
123            than one byte was nonsense.)
125        (c) The pcredemo.c sample program did not have any code at all to handle
126            the cases when CRLF is a valid newline sequence.
128    14. Neither pcre_exec() nor pcre_dfa_exec() was checking that the value given
129        as a starting offset was within the subject string. There is now a new
130        error, PCRE_ERROR_BADOFFSET, which is returned if the starting offset is
131        negative or greater than the length of the string. In order to test this,
132        pcretest is extended to allow the setting of negative starting offsets.
134    15. In both pcre_exec() and pcre_dfa_exec() the code for checking that the
135        starting offset points to the beginning of a UTF-8 character was
136        unnecessarily clumsy. I tidied it up.
138    16. Added PCRE_ERROR_SHORTUTF8 to make it possible to distinguish between a
139        bad UTF-8 sequence and one that is incomplete when using PCRE_PARTIAL_HARD.
141    17. Nobody had reported that the --include_dir option, which was added in
142        release 7.7 should have been called --include-dir (hyphen, not underscore)
143        for compatibility with GNU grep. I have changed it to --include-dir, but
144        left --include_dir as an undocumented synonym, and the same for
145        --exclude-dir, though that is not available in GNU grep, at least as of
146        release 2.5.4.
148    18. At a user's suggestion, the macros GETCHAR and friends (which pick up UTF-8
149        characters from a string of bytes) have been redefined so as not to use
150        loops, in order to improve performance in some environments. At the same
151        time, I abstracted some of the common code into auxiliary macros to save
152        repetition (this should not affect the compiled code).
154    19. If \c was followed by a multibyte UTF-8 character, bad things happened. A
155        compile-time error is now given if \c is not followed by an ASCII
156        character, that is, a byte less than 128. (In EBCDIC mode, the code is
157        different, and any byte value is allowed.)
159    20. Recognize (*NO_START_OPT) at the start of a pattern to set the PCRE_NO_
160        START_OPTIMIZE option, which is now allowed at compile time - but just
161        passed through to pcre_exec() or pcre_dfa_exec(). This makes it available
162        to pcregrep and other applications that have no direct access to PCRE
163        options. The new /Y option in pcretest sets this option when calling
164        pcre_compile().
166    21. Change 18 of release 8.01 broke the use of named subpatterns for recursive
167        back references. Groups containing recursive back references were forced to
168        be atomic by that change, but in the case of named groups, the amount of
169        memory required was incorrectly computed, leading to "Failed: internal
170        error: code overflow". This has been fixed.
172    22. Some patches to pcre_stringpiece.h, pcre_stringpiece_unittest.cc, and
173        pcretest.c, to avoid build problems in some Borland environments.
176    Version 8.10 25-Jun-2010
177    ------------------------
179    1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and
180        THEN.
182    2.  (*ACCEPT) was not working when inside an atomic group.
184    3.  Inside a character class, \B is treated as a literal by default, but
185        faulted if PCRE_EXTRA is set. This mimics Perl's behaviour (the -w option
186        causes the error). The code is unchanged, but I tidied the documentation.
188    4.  Inside a character class, PCRE always treated \R and \X as literals,
189        whereas Perl faults them if its -w option is set. I have changed PCRE so
190        that it faults them when PCRE_EXTRA is set.
192    5.  Added support for \N, which always matches any character other than
193        newline. (It is the same as "." when PCRE_DOTALL is not set.)
195    6.  When compiling pcregrep with newer versions of gcc which may have
196        FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',
197        declared with attribute warn_unused_result" were given. Just casting the
198        result to (void) does not stop the warnings; a more elaborate fudge is
199        needed. I've used a macro to implement this.
201    7.  Minor change to pcretest.c to avoid a compiler warning.
203    8.  Added four artifical Unicode properties to help with an option to make
204        \s etc use properties (see next item). The new properties are: Xan
205        (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).
207    9.  Added PCRE_UCP to make \b, \d, \s, \w, and certain POSIX character classes
208        use Unicode properties. (*UCP) at the start of a pattern can be used to set
209        this option. Modified pcretest to add /W to test this facility. Added
210        REG_UCP to make it available via the POSIX interface.
212    10. Added --line-buffered to pcregrep.
214    11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was
215        studied, and the match started with a letter with a code point greater than
216        127 whose first byte was different to the first byte of the other case of
217        the letter, the other case of this starting letter was not recognized
218        (#976).
220    12. If a pattern that was studied started with a repeated Unicode property
221        test, for example, \p{Nd}+, there was the theoretical possibility of
222        setting up an incorrect bitmap of starting bytes, but fortunately it could
223        not have actually happened in practice until change 8 above was made (it
224        added property types that matched character-matching opcodes).
226    13. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
227        possible starting bytes for non-anchored patterns.
229    14. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes
230        \R, and also a number of cases that involve Unicode properties, both
231        explicit and implicit when PCRE_UCP is set.
233    15. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8
234        input, it could crash or give wrong results if characters with values
235        greater than 0xc0 were present in the subject string. (Detail: it assumed
236        UTF-8 input when processing these items.)
238    16. Added a lot of (int) casts to avoid compiler warnings in systems where
239        size_t is 64-bit (#991).
241    17. Added a check for running out of memory when PCRE is compiled with
242        --disable-stack-for-recursion (#990).
244    18. If the last data line in a file for pcretest does not have a newline on
245        the end, a newline was missing in the output.
247    19. The default pcre_chartables.c file recognizes only ASCII characters (values
248        less than 128) in its various bitmaps. However, there is a facility for
249        generating tables according to the current locale when PCRE is compiled. It
250        turns out that in some environments, 0x85 and 0xa0, which are Unicode space
251        characters, are recognized by isspace() and therefore were getting set in
252        these tables, and indeed these tables seem to approximate to ISO 8859. This
253        caused a problem in UTF-8 mode when pcre_study() was used to create a list
254        of bytes that can start a match. For \s, it was including 0x85 and 0xa0,
255        which of course cannot start UTF-8 characters. I have changed the code so
256        that only real ASCII characters (less than 128) and the correct starting
257        bytes for UTF-8 encodings are set for characters greater than 127 when in
258        UTF-8 mode. (When PCRE_UCP is set - see 9 above - the code is different
259        altogether.)
261    20. Added the /T option to pcretest so as to be able to run tests with non-
262        standard character tables, thus making it possible to include the tests
263        used for 19 above in the standard set of tests.
265    21. A pattern such as (?&t)(?#()(?(DEFINE)(?<t>a)) which has a forward
266        reference to a subpattern the other side of a comment that contains an
267        opening parenthesis caused either an internal compiling error, or a
268        reference to the wrong subpattern.
271    Version 8.02 19-Mar-2010
272    ------------------------
274    1.  The Unicode data tables have been updated to Unicode 5.2.0.
276    2.  Added the option --libs-cpp to pcre-config, but only when C++ support is
277        configured.
279    3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the
280        original author of that file, following a query about its status.
282    4.  On systems that do not have stdint.h (e.g. Solaris), check for and include
283        inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
285    5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
286        quantifier applied to a forward-referencing subroutine call, could compile
287        incorrect code or give the error "internal error: previously-checked
288        referenced subpattern not found".
290    6.  Both MS Visual Studio and Symbian OS have problems with initializing
291        variables to point to external functions. For these systems, therefore,
292        pcre_malloc etc. are now initialized to local functions that call the
293        relevant global functions.
295    7.  There were two entries missing in the vectors called coptable and poptable
296        in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.
297        I've fixed the data, and added a kludgy way of testing at compile time that
298        the lengths are correct (equal to the number of opcodes).
300    8.  Following on from 7, I added a similar kludge to check the length of the
301        eint vector in pcreposix.c.
303    9.  Error texts for pcre_compile() are held as one long string to avoid too
304        much relocation at load time. To find a text, the string is searched,
305        counting zeros. There was no check for running off the end of the string,
306        which could happen if a new error number was added without updating the
307        string.
309    10. \K gave a compile-time error if it appeared in a lookbehind assersion.
311    11. \K was not working if it appeared in an atomic group or in a group that
312        was called as a "subroutine", or in an assertion. Perl 5.11 documents that
313        \K is "not well defined" if used in an assertion. PCRE now accepts it if
314        the assertion is positive, but not if it is negative.
316    12. Change 11 fortuitously reduced the size of the stack frame used in the
317        "match()" function of pcre_exec.c by one pointer. Forthcoming
318        implementation of support for (*MARK) will need an extra pointer on the
319        stack; I have reserved it now, so that the stack frame size does not
320        decrease.
322    13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other
323        item in branch that calls a recursion is a subroutine call - as in the
324        second branch in the above example - was incorrectly given the compile-
325        time error "recursive call could loop indefinitely" because pcre_compile()
326        was not correctly checking the subroutine for matching a non-empty string.
328    14. The checks for overrunning compiling workspace could trigger after an
329        overrun had occurred. This is a "should never occur" error, but it can be
330        triggered by pathological patterns such as hundreds of nested parentheses.
331        The checks now trigger 100 bytes before the end of the workspace.
333    15. Fix typo in configure.ac: "srtoq" should be "strtoq".
336    Version 8.01 19-Jan-2010
337    ------------------------
339    1.  If a pattern contained a conditional subpattern with only one branch (in
340        particular, this includes all (*DEFINE) patterns), a call to pcre_study()
341        computed the wrong minimum data length (which is of course zero for such
342        subpatterns). This could cause incorrect "no match" results.
344    2.  For patterns such as (?i)a(?-i)b|c where an option setting at the start of
345        the pattern is reset in the first branch, pcre_compile() failed with
346        "internal error: code overflow at offset...". This happened only when
347        the reset was to the original external option setting. (An optimization
348        abstracts leading options settings into an external setting, which was the
349        cause of this.)
351    3.  A pattern such as ^(?!a(*SKIP)b) where a negative assertion contained one
352        of the verbs SKIP, PRUNE, or COMMIT, did not work correctly. When the
353        assertion pattern did not match (meaning that the assertion was true), it
354        was incorrectly treated as false if the SKIP had been reached during the
355        matching. This also applied to assertions used as conditions.
357    4.  If an item that is not supported by pcre_dfa_exec() was encountered in an
358        assertion subpattern, including such a pattern used as a condition,
359        unpredictable results occurred, instead of the error return
362    5.  The C++ GlobalReplace function was not working like Perl for the special
363        situation when an empty string is matched. It now does the fancy magic
364        stuff that is necessary.
366    6.  In pcre_internal.h, obsolete includes to setjmp.h and stdarg.h have been
367        removed. (These were left over from very, very early versions of PCRE.)
369    7.  Some cosmetic changes to the code to make life easier when compiling it
370        as part of something else:
372        (a) Change DEBUG to PCRE_DEBUG.
374        (b) In pcre_compile(), rename the member of the "branch_chain" structure
375            called "current" as "current_branch", to prevent a collision with the
376            Linux macro when compiled as a kernel module.
378        (c) In pcre_study(), rename the function set_bit() as set_table_bit(), to
379            prevent a collision with the Linux macro when compiled as a kernel
380            module.
382    8.  In pcre_compile() there are some checks for integer overflows that used to
383        cast potentially large values to (double). This has been changed to that
384        when building, a check for int64_t is made, and if it is found, it is used
385        instead, thus avoiding the use of floating point arithmetic. (There is no
386        other use of FP in PCRE.) If int64_t is not found, the fallback is to
387        double.
389    9.  Added two casts to avoid signed/unsigned warnings from VS Studio Express
390        2005 (difference between two addresses compared to an unsigned value).
392    10. Change the standard AC_CHECK_LIB test for libbz2 in configure.ac to a
393        custom one, because of the following reported problem in Windows:
395          - libbz2 uses the Pascal calling convention (WINAPI) for the functions
396              under Win32.
397          - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",
398              therefore missing the function definition.
399          - The compiler thus generates a "C" signature for the test function.
400          - The linker fails to find the "C" function.
401          - PCRE fails to configure if asked to do so against libbz2.
403    11. When running libtoolize from libtool-2.2.6b as part of autogen.sh, these
404        messages were output:
406          Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
407          rerunning libtoolize, to keep the correct libtool macros in-tree.
408          Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
410        I have done both of these things.
412    12. Although pcre_dfa_exec() does not use nearly as much stack as pcre_exec()
413        most of the time, it *can* run out if it is given a pattern that contains a
414        runaway infinite recursion. I updated the discussion in the pcrestack man
415        page.
417    13. Now that we have gone to the x.xx style of version numbers, the minor
418        version may start with zero. Using 08 or 09 is a bad idea because users
419        might check the value of PCRE_MINOR in their code, and 08 or 09 may be
420        interpreted as invalid octal numbers. I've updated the previous comment in
421        configure.ac, and also added a check that gives an error if 08 or 09 are
422        used.
424    14. Change 8.00/11 was not quite complete: code had been accidentally omitted,
425        causing partial matching to fail when the end of the subject matched \W
426        in a UTF-8 pattern where \W was quantified with a minimum of 3.
428    15. There were some discrepancies between the declarations in pcre_internal.h
429        of _pcre_is_newline(), _pcre_was_newline(), and _pcre_valid_utf8() and
430        their definitions. The declarations used "const uschar *" and the
431        definitions used USPTR. Even though USPTR is normally defined as "const
432        unsigned char *" (and uschar is typedeffed as "unsigned char"), it was
433        reported that: "This difference in casting confuses some C++ compilers, for
434        example, SunCC recognizes above declarations as different functions and
435        generates broken code for hbpcre." I have changed the declarations to use
436        USPTR.
438    16. GNU libtool is named differently on some systems. The autogen.sh script now
439        tries several variants such as glibtoolize (MacOSX) and libtoolize1x
440        (FreeBSD).
442    17. Applied Craig's patch that fixes an HP aCC compile error in pcre 8.00
443        (strtoXX undefined when compiling pcrecpp.cc). The patch contains this
444        comment: "Figure out how to create a longlong from a string: strtoll and
445        equivalent. It's not enough to call AC_CHECK_FUNCS: hpux has a strtoll, for
446        instance, but it only takes 2 args instead of 3!"
448    18. A subtle bug concerned with back references has been fixed by a change of
449        specification, with a corresponding code fix. A pattern such as
450        ^(xa|=?\1a)+$ which contains a back reference inside the group to which it
451        refers, was giving matches when it shouldn't. For example, xa=xaaa would
452        match that pattern. Interestingly, Perl (at least up to 5.11.3) has the
453        same bug. Such groups have to be quantified to be useful, or contained
454        inside another quantified group. (If there's no repetition, the reference
455        can never match.) The problem arises because, having left the group and
456        moved on to the rest of the pattern, a later failure that backtracks into
457        the group uses the captured value from the final iteration of the group
458        rather than the correct earlier one. I have fixed this in PCRE by forcing
459        any group that contains a reference to itself to be an atomic group; that
460        is, there cannot be any backtracking into it once it has completed. This is
461        similar to recursive and subroutine calls.
464    Version 8.00 19-Oct-09
465    ----------------------
467    1.  The table for translating pcre_compile() error codes into POSIX error codes
468        was out-of-date, and there was no check on the pcre_compile() error code
469        being within the table. This could lead to an OK return being given in
470        error.
472    2.  Changed the call to open a subject file in pcregrep from fopen(pathname,
473        "r") to fopen(pathname, "rb"), which fixed a problem with some of the tests
474        in a Windows environment.
476    3.  The pcregrep --count option prints the count for each file even when it is
477        zero, as does GNU grep. However, pcregrep was also printing all files when
478        --files-with-matches was added. Now, when both options are given, it prints
479        counts only for those files that have at least one match. (GNU grep just
480        prints the file name in this circumstance, but including the count seems
481        more useful - otherwise, why use --count?) Also ensured that the
482        combination -clh just lists non-zero counts, with no names.
484    4.  The long form of the pcregrep -F option was incorrectly implemented as
485        --fixed_strings instead of --fixed-strings. This is an incompatible change,
486        but it seems right to fix it, and I didn't think it was worth preserving
487        the old behaviour.
489    5.  The command line items --regex=pattern and --regexp=pattern were not
490        recognized by pcregrep, which required --regex pattern or --regexp pattern
491        (with a space rather than an '='). The man page documented the '=' forms,
492        which are compatible with GNU grep; these now work.
494    6.  No libpcreposix.pc file was created for pkg-config; there was just
495        libpcre.pc and libpcrecpp.pc. The omission has been rectified.
497    7.  Added #ifndef SUPPORT_UCP into the pcre_ucd.c module, to reduce its size
498        when UCP support is not needed, by modifying the Python script that
499        generates it from Unicode data files. This should not matter if the module
500        is correctly used as a library, but I received one complaint about 50K of
501        unwanted data. My guess is that the person linked everything into his
502        program rather than using a library. Anyway, it does no harm.
504    8.  A pattern such as /\x{123}{2,2}+/8 was incorrectly compiled; the trigger
505        was a minimum greater than 1 for a wide character in a possessive
506        repetition. The same bug could also affect patterns like /(\x{ff}{0,2})*/8
507        which had an unlimited repeat of a nested, fixed maximum repeat of a wide
508        character. Chaos in the form of incorrect output or a compiling loop could
509        result.
511    9.  The restrictions on what a pattern can contain when partial matching is
512        requested for pcre_exec() have been removed. All patterns can now be
513        partially matched by this function. In addition, if there are at least two
514        slots in the offset vector, the offset of the earliest inspected character
515        for the match and the offset of the end of the subject are set in them when
516        PCRE_ERROR_PARTIAL is returned.
518    10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is
519        synonymous with PCRE_PARTIAL, for backwards compatibility, and
520        PCRE_PARTIAL_HARD, which causes a partial match to supersede a full match,
521        and may be more useful for multi-segment matching.
523    11. Partial matching with pcre_exec() is now more intuitive. A partial match
524        used to be given if ever the end of the subject was reached; now it is
525        given only if matching could not proceed because another character was
526        needed. This makes a difference in some odd cases such as Z(*FAIL) with the
527        string "Z", which now yields "no match" instead of "partial match". In the
528        case of pcre_dfa_exec(), "no match" is given if every matching path for the
529        final character ended with (*FAIL).
531    12. Restarting a match using pcre_dfa_exec() after a partial match did not work
532        if the pattern had a "must contain" character that was already found in the
533        earlier partial match, unless partial matching was again requested. For
534        example, with the pattern /dog.(body)?/, the "must contain" character is
535        "g". If the first part-match was for the string "dog", restarting with
536        "sbody" failed. This bug has been fixed.
538    13. The string returned by pcre_dfa_exec() after a partial match has been
539        changed so that it starts at the first inspected character rather than the
540        first character of the match. This makes a difference only if the pattern
541        starts with a lookbehind assertion or \b or \B (\K is not supported by
542        pcre_dfa_exec()). It's an incompatible change, but it makes the two
543        matching functions compatible, and I think it's the right thing to do.
545    14. Added a pcredemo man page, created automatically from the pcredemo.c file,
546        so that the demonstration program is easily available in environments where
547        PCRE has not been installed from source.
549    15. Arranged to add -DPCRE_STATIC to cflags in libpcre.pc, libpcreposix.cp,
550        libpcrecpp.pc and pcre-config when PCRE is not compiled as a shared
551        library.
553    16. Added REG_UNGREEDY to the pcreposix interface, at the request of a user.
554        It maps to PCRE_UNGREEDY. It is not, of course, POSIX-compatible, but it
555        is not the first non-POSIX option to be added. Clearly some people find
556        these options useful.
558    17. If a caller to the POSIX matching function regexec() passes a non-zero
559        value for nmatch with a NULL value for pmatch, the value of
560        nmatch is forced to zero.
562    18. RunGrepTest did not have a test for the availability of the -u option of
563        the diff command, as RunTest does. It now checks in the same way as
564        RunTest, and also checks for the -b option.
566    19. If an odd number of negated classes containing just a single character
567        interposed, within parentheses, between a forward reference to a named
568        subpattern and the definition of the subpattern, compilation crashed with
569        an internal error, complaining that it could not find the referenced
570        subpattern. An example of a crashing pattern is /(?&A)(([^m])(?<A>))/.
571        [The bug was that it was starting one character too far in when skipping
572        over the character class, thus treating the ] as data rather than
573        terminating the class. This meant it could skip too much.]
575    20. Added PCRE_NOTEMPTY_ATSTART in order to be able to correctly implement the
576        /g option in pcretest when the pattern contains \K, which makes it possible
577        to have an empty string match not at the start, even when the pattern is
578        anchored. Updated pcretest and pcredemo to use this option.
580    21. If the maximum number of capturing subpatterns in a recursion was greater
581        than the maximum at the outer level, the higher number was returned, but
582        with unset values at the outer level. The correct (outer level) value is
583        now given.
585    22. If (*ACCEPT) appeared inside capturing parentheses, previous releases of
586        PCRE did not set those parentheses (unlike Perl). I have now found a way to
587        make it do so. The string so far is captured, making this feature
588        compatible with Perl.
590    23. The tests have been re-organized, adding tests 11 and 12, to make it
591        possible to check the Perl 5.10 features against Perl 5.10.
593    24. Perl 5.10 allows subroutine calls in lookbehinds, as long as the subroutine
594        pattern matches a fixed length string. PCRE did not allow this; now it
595        does. Neither allows recursion.
597    25. I finally figured out how to implement a request to provide the minimum
598        length of subject string that was needed in order to match a given pattern.
599        (It was back references and recursion that I had previously got hung up
600        on.) This code has now been added to pcre_study(); it finds a lower bound
601        to the length of subject needed. It is not necessarily the greatest lower
602        bound, but using it to avoid searching strings that are too short does give
603        some useful speed-ups. The value is available to calling programs via
604        pcre_fullinfo().
606    26. While implementing 25, I discovered to my embarrassment that pcretest had
607        not been passing the result of pcre_study() to pcre_dfa_exec(), so the
608        study optimizations had never been tested with that matching function.
609        Oops. What is worse, even when it was passed study data, there was a bug in
610        pcre_dfa_exec() that meant it never actually used it. Double oops. There
611        were also very few tests of studied patterns with pcre_dfa_exec().
613    27. If (?| is used to create subpatterns with duplicate numbers, they are now
614        allowed to have the same name, even if PCRE_DUPNAMES is not set. However,
615        on the other side of the coin, they are no longer allowed to have different
616        names, because these cannot be distinguished in PCRE, and this has caused
617        confusion. (This is a difference from Perl.)
619    28. When duplicate subpattern names are present (necessarily with different
620        numbers, as required by 27 above), and a test is made by name in a
621        conditional pattern, either for a subpattern having been matched, or for
622        recursion in such a pattern, all the associated numbered subpatterns are
623        tested, and the overall condition is true if the condition is true for any
624        one of them. This is the way Perl works, and is also more like the way
625        testing by number works.
628    Version 7.9 11-Apr-09
629  ---------------------  ---------------------
631   1. Applied Bob Rossi and Daniel G's patches to convert the build system to one  1.  When building with support for bzlib/zlib (pcregrep) and/or readline
632      that is more "standard", making use of automake and other autotools. There      (pcretest), all targets were linked against these libraries. This included
633        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
634        libraries. This caused unwanted dependencies to be created. This problem
635        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
636        pcretest is linked with readline.
638    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
639        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
640        moved outside it again, because FALSE and TRUE are already defined in AIX,
641        but BOOL is not.
643    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
644        PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
646    4.  The pcregrep documentation said spaces were inserted as well as colons (or
647        hyphens) following file names and line numbers when outputting matching
648        lines. This is not true; no spaces are inserted. I have also clarified the
649        wording for the --colour (or --color) option.
651    5.  In pcregrep, when --colour was used with -o, the list of matching strings
652        was not coloured; this is different to GNU grep, so I have changed it to be
653        the same.
655    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
656        each matching line was coloured. Now it goes on to look for further matches
657        of any of the test patterns, which is the same behaviour as GNU grep.
659    7.  A pattern that could match an empty string could cause pcregrep to loop; it
660        doesn't make sense to accept an empty string match in pcregrep, so I have
661        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
662        seems to be how GNU grep behaves.
664    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
665        start or after a newline", because the conditional assertion was not being
666        correctly handled. The rule now is that both the assertion and what follows
667        in the first alternative must satisfy the test.
669    9.  If auto-callout was enabled in a pattern with a conditional group whose
670        condition was an assertion, PCRE could crash during matching, both with
671        pcre_exec() and pcre_dfa_exec().
673    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
674        used for matching.
676    11. Unicode property support in character classes was not working for
677        characters (bytes) greater than 127 when not in UTF-8 mode.
679    12. Added the -M command line option to pcretest.
681    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
683    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
685    16. Added comments and documentation about mis-use of no_arg in the C++
686        wrapper.
688    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
689        from Martin Jerabek that uses macro names for all relevant character and
690        string constants.
692    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
693        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
694        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
695        these, but not everybody uses configure.
697    19. A conditional group that had only one branch was not being correctly
698        recognized as an item that could match an empty string. This meant that an
699        enclosing group might also not be so recognized, causing infinite looping
700        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
701        with the subject "ab", where knowledge that the repeated group can match
702        nothing is needed in order to break the loop.
704    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
705        exec(), but without supplying a callout function, matching went wrong.
707    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
708        leak if the size of the offset vector was greater than 30. When the vector
709        is smaller, the saved offsets during recursion go onto a local stack
710        vector, but for larger vectors malloc() is used. It was failing to free
711        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
712        error, in fact).
714    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
715        heapframe that is used only when UTF-8 support is enabled. This caused no
716        problem, but was untidy.
718    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
719        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
720        included within another project.
722    24. Steven Van Ingelgem's patches to add more options to the CMake support,
723        slightly modified by me:
725          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
726              not building pcregrep.
728          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
729              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
731    25. Forward references, both numeric and by name, in patterns that made use of
732        duplicate group numbers, could behave incorrectly or give incorrect errors,
733        because when scanning forward to find the reference group, PCRE was not
734        taking into account the duplicate group numbers. A pattern such as
735        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
737    26. Changed a few more instances of "const unsigned char *" to USPTR, making
738        the feature of a custom pointer more persuasive (as requested by a user).
740    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
741        pcretest.c, inside #ifndefs, because it seems they are sometimes already
742        pre-defined.
744    28. Added support for (*UTF8) at the start of a pattern.
746    29. Arrange for flags added by the "release type" setting in CMake to be shown
747        in the configuration summary.
750    Version 7.8 05-Sep-08
751    ---------------------
753    1.  Replaced UCP searching code with optimized version as implemented for Ad
754        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
755        stage table and inline lookup instead of a function, giving speed ups of 2
756        to 5 times on some simple patterns that I tested. Permission was given to
757        distribute the MultiStage2.py script that generates the tables (it's not in
758        the tarball, but is in the Subversion repository).
760    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
761        scripts.
763    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
764        a group with a zero qualifier. The result of the study could be incorrect,
765        or the function might crash, depending on the pattern.
767    4.  Caseless matching was not working for non-ASCII characters in back
768        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
769        It now works when Unicode Property Support is available.
771    5.  In pcretest, an escape such as \x{de} in the data was always generating
772        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
773        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
774        truncation.
776    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
778    7.  Added two (int) casts to pcregrep when printing the difference of two
779        pointers, in case they are 64-bit values.
781    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
782        test 2 if it fails.
784    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
785        and a #define of that name to empty if it is not externally set. This is to
786        allow users of MSVC to set it if necessary.
788    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
789        the convenience functions in the pcre_get.c source file.
791    11. An option change at the start of a pattern that had top-level alternatives
792        could cause overwriting and/or a crash. This command provoked a crash in
793        some environments:
795          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
797        This potential security problem was recorded as CVE-2008-2371.
799    12. For a pattern where the match had to start at the beginning or immediately
800        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
801        pcre_dfa_exec() could read past the end of the passed subject if there was
802        no match. To help with detecting such bugs (e.g. with valgrind), I modified
803        pcretest so that it places the subject at the end of its malloc-ed buffer.
805    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
806        exec() might read past the end of the data buffer in UTF-8 mode.
808    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
809        the data contained the byte 0x85 as part of a UTF-8 character within its
810        first line. This applied both to normal and DFA matching.
812    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
813        /^[^d]*?$/8 failed to match "abc".
815    16. Added a missing copyright notice to pcrecpp_internal.h.
817    17. Make it more clear in the documentation that values returned from
818        pcre_exec() in ovector are byte offsets, not character counts.
820    18. Tidied a few places to stop certain compilers from issuing warnings.
822    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
823        supplied by Stefan Weber. I made a further small update for 7.8 because
824        there is a change of source arrangements: the pcre_searchfuncs.c module is
825        replaced by pcre_ucd.c.
828    Version 7.7 07-May-08
829    ---------------------
831    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
832        a string to a long long, pretend we don't even have a long long." This is
833        done by checking for the strtoq, strtoll, and _strtoi64 functions.
835    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
836        pre-7.6 versions, which defined a global no_arg variable instead of putting
837        it in the RE class. (See also #8 below.)
839    3.  Remove a line of dead code, identified by coverity and reported by Nuno
840        Lopes.
842    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
844        (1) The include/exclude patterns were being applied to the whole pathnames
845            of files, instead of just to the final components.
847        (2) If there was more than one level of directory, the subdirectories were
848            skipped unless they satisfied the include/exclude conditions. This is
849            inconsistent with GNU grep (and could even be seen as contrary to the
850            pcregrep specification - which I improved to make it absolutely clear).
851            The action now is always to scan all levels of directory, and just
852            apply the include/exclude patterns to regular files.
854    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
855        --exclude_dir in the tests to avoid scanning .svn directories.
857    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
858        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
859        doesn't support NULs in patterns.
861    7.  Added some missing "const"s to declarations of static tables in
862        pcre_compile.c and pcre_dfa_exec.c.
864    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
865        caused by fix #2  above. (Subsequently also a second patch to fix the
866        first patch. And a third patch - this was a messy problem.)
868    9.  Applied Craig's patch to remove the use of push_back().
870    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
871        matching function regexec().
873    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
874        which, however, unlike Perl's \g{...}, are subroutine calls, not back
875        references. PCRE supports relative numbers with this syntax (I don't think
876        Oniguruma does).
878    12. Previously, a group with a zero repeat such as (...){0} was completely
879        omitted from the compiled regex. However, this means that if the group
880        was called as a subroutine from elsewhere in the pattern, things went wrong
881        (an internal error was given). Such groups are now left in the compiled
882        pattern, with a new opcode that causes them to be skipped at execution
883        time.
885    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
886        to the way PCRE behaves:
888        (a) A lone ] character is dis-allowed (Perl treats it as data).
890        (b) A back reference to an unmatched subpattern matches an empty string
891            (Perl fails the current match path).
893        (c) A data ] in a character class must be notated as \] because if the
894            first data character in a class is ], it defines an empty class. (In
895            Perl it is not possible to have an empty class.) The empty class []
896            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
897            The negative empty class [^] matches any one character, independently
898            of the DOTALL setting.
900    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
901        non-existent subpattern following a character class starting with ']' and
902        containing () gave an internal compiling error instead of "reference to
903        non-existent subpattern". Fortunately, when the pattern did exist, the
904        compiled code was correct. (When scanning forwards to check for the
905        existencd of the subpattern, it was treating the data ']' as terminating
906        the class, so got the count wrong. When actually compiling, the reference
907        was subsequently set up correctly.)
909    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
910        it was being rejected as not supported by pcre_dfa_exec(), even though
911        other assertions are supported. I have made pcre_dfa_exec() support
912        (*FAIL).
914    16. The implementation of 13c above involved the invention of a new opcode,
915        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
916        cannot be changed at match time, I realized I could make a small
917        improvement to matching performance by compiling OP_ALLANY instead of
918        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
919        on the OP_ANY path.
921    17. Compiling pcretest on Windows with readline support failed without the
922        following two fixes: (1) Make the unistd.h include conditional on
923        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
925    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
926        ncurses library to be included for pcretest when ReadLine support is
927        requested, but also to allow for it to be overridden. This patch came from
928        Daniel Bergström.
930    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
931        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
932        any errors with the current Unicode tables. Thanks to Peter Kankowski for
933        spotting this.
936    Version 7.6 28-Jan-08
937    ---------------------
939    1.  A character class containing a very large number of characters with
940        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
941        overflow.
943    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
944        HAVE_LONG_LONG is not defined.
946    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
947        bring them up to date and include new features. This patch includes:
949        - Fixed PH's badly added libz and libbz2 support.
950        - Fixed a problem with static linking.
951        - Added pcredemo. [But later removed - see 7 below.]
952        - Fixed dftables problem and added an option.
953        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
954            HAVE_LONG_LONG.
955        - Added readline support for pcretest.
956        - Added an listing of the option settings after cmake has run.
958    4.  A user submitted a patch to Makefile that makes it easy to create
959        "pcre.dll" under mingw when using Configure/Make. I added stuff to
960        Makefile.am that cause it to include this special target, without
961        affecting anything else. Note that the same mingw target plus all
962        the other distribution libraries and programs are now supported
963        when configuring with CMake (see 6 below) instead of with
964        Configure/Make.
966    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
967        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
968        exported in the Windows port". It has not yet been confirmed that the patch
969        solves the problem, but it does no harm.
971    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
972        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
973        with CMake, and also correct the comment about stack recursion.
975    7.  Remove the automatic building of pcredemo from the ./configure system and
976        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
977        of a program that users should build themselves after PCRE is installed, so
978        building it automatically is not really right. What is more, it gave
979        trouble in some build environments.
981    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
984    Version 7.5 10-Jan-08
985    ---------------------
987    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
988        values in parens when parsing an RE using the C++ wrapper."
990    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
991        Characters greater than 255 were excluded from the class instead of being
992        included.
994    3.  The same bug as (2) above applied to negated POSIX classes such as
995        [:^space:].
997    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
998        defined or documented. It seems to have been a typo for PCRE_STATIC, so
999        I have changed it.
1001    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
1002        first named subpattern) and a construct such as (?&a) would reference the
1003        first named subpattern whose name started with "a" (in other words, the
1004        length check was missing). Both these problems are fixed. "Subpattern name
1005        expected" is now given for (?&) (a zero-length name), and this patch also
1006        makes it give the same error for \k'' (previously it complained that that
1007        was a reference to a non-existent subpattern).
1009    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
1010        this is right because (?- can be followed by option settings as well as by
1011        digits. I have, however, made the messages clearer.
1013    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
1014        than the number used in the conditional) now cause a compile-time error.
1015        This is actually not compatible with Perl, which accepts such patterns, but
1016        treats the conditional as always being FALSE (as PCRE used to), but it
1017        seems to me that giving a diagnostic is better.
1019    8.  Change "alphameric" to the more common word "alphanumeric" in comments
1020        and messages.
1022    9.  Fix two occurrences of "backslash" in comments that should have been
1023        "backspace".
1025    10. Remove two redundant lines of code that can never be obeyed (their function
1026        was moved elsewhere).
1028    11. The program that makes PCRE's Unicode character property table had a bug
1029        which caused it to generate incorrect table entries for sequences of
1030        characters that have the same character type, but are in different scripts.
1031        It amalgamated them into a single range, with the script of the first of
1032        them. In other words, some characters were in the wrong script. There were
1033        thirteen such cases, affecting characters in the following ranges:
1035          U+002b0 - U+002c1
1036          U+0060c - U+0060d
1037          U+0061e - U+00612
1038          U+0064b - U+0065e
1039          U+0074d - U+0076d
1040          U+01800 - U+01805
1041          U+01d00 - U+01d77
1042          U+01d9b - U+01dbf
1043          U+0200b - U+0200f
1044          U+030fc - U+030fe
1045          U+03260 - U+0327f
1046          U+0fb46 - U+0fbb1
1047          U+10450 - U+1049d
1049    12. The -o option (show only the matching part of a line) for pcregrep was not
1050        compatible with GNU grep in that, if there was more than one match in a
1051        line, it showed only the first of them. It now behaves in the same way as
1052        GNU grep.
1054    13. If the -o and -v options were combined for pcregrep, it printed a blank
1055        line for every non-matching line. GNU grep prints nothing, and pcregrep now
1056        does the same. The return code can be used to tell if there were any
1057        non-matching lines.
1059    14. Added --file-offsets and --line-offsets to pcregrep.
1061    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
1062        infinitely looping recursion. The bug was that positive lookaheads were not
1063        being skipped when checking for a possible empty match (negative lookaheads
1064        and both kinds of lookbehind were skipped).
1066    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
1067        inclusion of <windows.h> to before rather than after the definition of
1068        INVALID_FILE_ATTRIBUTES (patch from David Byron).
1070    17. Specifying a possessive quantifier with a specific limit for a Unicode
1071        character property caused pcre_compile() to compile bad code, which led at
1072        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
1073        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
1074        caused the error; without that there was no problem.
1076    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
1078    19. Added --enable-pcretest-libreadline.
1080    20. In pcrecpp.cc, the variable 'count' was incremented twice in
1081        RE::GlobalReplace(). As a result, the number of replacements returned was
1082        double what it should be. I removed one of the increments, but Craig sent a
1083        later patch that removed the other one (the right fix) and added unit tests
1084        that check the return values (which was not done before).
1086    21. Several CMake things:
1088        (1) Arranged that, when cmake is used on Unix, the libraries end up with
1089            the names libpcre and libpcreposix, not just pcre and pcreposix.
1091        (2) The above change means that pcretest and pcregrep are now correctly
1092            linked with the newly-built libraries, not previously installed ones.
1096    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
1097        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
1098        UTF-8 newline character). The key issue is that the pattern starts .*;
1099        this means that the match must be either at the beginning, or after a
1100        newline. The bug was in the code for advancing after a failed match and
1101        checking that the new position followed a newline. It was not taking
1102        account of UTF-8 characters correctly.
1104    23. PCRE was behaving differently from Perl in the way it recognized POSIX
1105        character classes. PCRE was not treating the sequence [:...:] as a
1106        character class unless the ... were all letters. Perl, however, seems to
1107        allow any characters between [: and :], though of course it rejects as
1108        unknown any "names" that contain non-letters, because all the known class
1109        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
1110        for example, whereas PCRE did not - it did not recognize a POSIX character
1111        class. This seemed a bit dangerous, so the code has been changed to be
1112        closer to Perl. The behaviour is not identical to Perl, because PCRE will
1113        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
1114        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
1115        Perl does, and where it didn't before.
1117    24. Rewrite so as to remove the single use of %n from pcregrep because in some
1118        Windows environments %n is disabled by default.
1121    Version 7.4 21-Sep-07
1122    ---------------------
1124    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
1125        means that a class such as [\s] counted as "explicit reference to CR or
1126        LF". That isn't really right - the whole point of the change was to try to
1127        help when there was an actual mention of one of the two characters. So now
1128        the change happens only if \r or \n (or a literal CR or LF) character is
1129        encountered.
1131    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
1132        of both had grown to the point where there were only 3 bits left.
1133        Fortunately, there was spare space in the data structure, and so I have
1134        moved the internal flags into a new 16-bit field to free up more option
1135        bits.
1137    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
1138        but did not set the internal JCHANGED flag - either of these is enough to
1139        control the way the "get" function works - but the PCRE_INFO_JCHANGED
1140        facility is supposed to tell if (?J) was ever used, so now (?J) at the
1141        start sets both bits.
1143    4.  Added options (at build time, compile time, exec time) to change \R from
1144        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
1146    5.  doc/pcresyntax.html was missing from the distribution.
1148    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
1149        compatibility, even though it is no longer used.
1151    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
1152        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
1153        windows.h file is present (where different names are used). [This was
1154        reversed later after testing - see 16 below.]
1156    8.  Changed all #include <config.h> to #include "config.h". There were also
1157        some further <pcre.h> cases that I changed to "pcre.h".
1159    9.  When pcregrep was used with the --colour option, it missed the line ending
1160        sequence off the lines that it output.
1162    10. It was pointed out to me that arrays of string pointers cause lots of
1163        relocations when a shared library is dynamically loaded. A technique of
1164        using a single long string with a table of offsets can drastically reduce
1165        these. I have refactored PCRE in four places to do this. The result is
1166        dramatic:
1168          Originally:                          290
1169          After changing UCP table:            187
1170          After changing error message table:   43
1171          After changing table of "verbs"       36
1172          After changing table of Posix names   22
1174        Thanks to the folks working on Gregex for glib for this insight.
1176    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
1177        unicode-properties was also set.
1179    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
1181    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
1182        checked only for CRLF.
1184    14. Added casts to pcretest.c to avoid compiler warnings.
1186    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
1188    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
1189        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
1190        entirely. This removes changes made in 7 above.
1192    17. The CMake files have been updated, and there is now more information about
1193        building with CMake in the NON-UNIX-USE document.
1196    Version 7.3 28-Aug-07
1197    ---------------------
1199     1. In the rejigging of the build system that eventually resulted in 7.1, the
1200        line "#include <pcre.h>" was included in pcre_internal.h. The use of angle
1201        brackets there is not right, since it causes compilers to look for an
1202        installed pcre.h, not the version that is in the source that is being
1203        compiled (which of course may be different). I have changed it back to:
1205          #include "pcre.h"
1207        I have a vague recollection that the change was concerned with compiling in
1208        different directories, but in the new build system, that is taken care of
1209        by the VPATH setting the Makefile.
1211     2. The pattern .*$ when run in not-DOTALL UTF-8 mode with newline=any failed
1212        when the subject happened to end in the byte 0x85 (e.g. if the last
1213        character was \x{1ec5}). *Character* 0x85 is one of the "any" newline
1214        characters but of course it shouldn't be taken as a newline when it is part
1215        of another character. The bug was that, for an unlimited repeat of . in
1216        not-DOTALL UTF-8 mode, PCRE was advancing by bytes rather than by
1217        characters when looking for a newline.
1219     3. A small performance improvement in the DOTALL UTF-8 mode .* case.
1221     4. Debugging: adjusted the names of opcodes for different kinds of parentheses
1222        in debug output.
1224     5. Arrange to use "%I64d" instead of "%lld" and "%I64u" instead of "%llu" for
1225        long printing in the pcrecpp unittest when running under MinGW.
1227     6. ESC_K was left out of the EBCDIC table.
1229     7. Change 7.0/38 introduced a new limit on the number of nested non-capturing
1230        parentheses; I made it 1000, which seemed large enough. Unfortunately, the
1231        limit also applies to "virtual nesting" when a pattern is recursive, and in
1232        this case 1000 isn't so big. I have been able to remove this limit at the
1233        expense of backing off one optimization in certain circumstances. Normally,
1234        when pcre_exec() would call its internal match() function recursively and
1235        immediately return the result unconditionally, it uses a "tail recursion"
1236        feature to save stack. However, when a subpattern that can match an empty
1237        string has an unlimited repetition quantifier, it no longer makes this
1238        optimization. That gives it a stack frame in which to save the data for
1239        checking that an empty string has been matched. Previously this was taken
1240        from the 1000-entry workspace that had been reserved. So now there is no
1241        explicit limit, but more stack is used.
1243     8. Applied Daniel's patches to solve problems with the import/export magic
1244        syntax that is required for Windows, and which was going wrong for the
1245        pcreposix and pcrecpp parts of the library. These were overlooked when this
1246        problem was solved for the main library.
1248     9. There were some crude static tests to avoid integer overflow when computing
1249        the size of patterns that contain repeated groups with explicit upper
1250        limits. As the maximum quantifier is 65535, the maximum group length was
1251        set at 30,000 so that the product of these two numbers did not overflow a
1252        32-bit integer. However, it turns out that people want to use groups that
1253        are longer than 30,000 bytes (though not repeat them that many times).
1254        Change 7.0/17 (the refactoring of the way the pattern size is computed) has
1255        made it possible to implement the integer overflow checks in a much more
1256        dynamic way, which I have now done. The artificial limitation on group
1257        length has been removed - we now have only the limit on the total length of
1258        the compiled pattern, which depends on the LINK_SIZE setting.
1260    10. Fixed a bug in the documentation for get/copy named substring when
1261        duplicate names are permitted. If none of the named substrings are set, the
1262        functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an
1263        empty string.
1265    11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E
1266        instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,
1267        because the ] is interpreted as the first data character and the
1268        terminating ] is not found. PCRE has been made compatible with Perl in this
1269        regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could
1270        cause memory overwriting.
1272    10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty
1273        string has been matched (to stop an infinite loop). It was not recognizing
1274        a conditional subpattern that could match an empty string if that
1275        subpattern was within another subpattern. For example, it looped when
1276        trying to match  (((?(1)X|))*)  but it was OK with  ((?(1)X|)*)  where the
1277        condition was not nested. This bug has been fixed.
1279    12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack
1280        past the start of the subject in the presence of bytes with the top bit
1281        set, for example "\x8aBCD".
1283    13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
1284        (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
1286    14. Optimized (?!) to (*FAIL).
1288    15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
1289        This restricts code points to be within the range 0 to 0x10FFFF, excluding
1290        the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
1291        full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
1292        does: it's just the validity check that is more restrictive.
1294    16. Inserted checks for integer overflows during escape sequence (backslash)
1295        processing, and also fixed erroneous offset values for syntax errors during
1296        backslash processing.
1298    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
1299        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
1301    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
1302        caused an overrun.
1304    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
1305        something other than just ASCII characters) inside a group that had an
1306        unlimited repeat caused a loop at compile time (while checking to see
1307        whether the group could match an empty string).
1309    20. Debugging a pattern containing \p or \P could cause a crash. For example,
1310        [\P{Any}] did so. (Error in the code for printing property names.)
1312    21. An orphan \E inside a character class could cause a crash.
1314    22. A repeated capturing bracket such as (A)? could cause a wild memory
1315        reference during compilation.
1317    23. There are several functions in pcre_compile() that scan along a compiled
1318        expression for various reasons (e.g. to see if it's fixed length for look
1319        behind). There were bugs in these functions when a repeated \p or \P was
1320        present in the pattern. These operators have additional parameters compared
1321        with \d, etc, and these were not being taken into account when moving along
1322        the compiled data. Specifically:
1324        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
1325            length.
1327        (b) An item such as \pL+ within a repeated group could cause crashes or
1328            loops.
1330        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
1331            "reference to non-existent subpattern" error.
1333        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
1335    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
1336        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
1338    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
1340    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
1341        character were causing crashes (broken optimization).
1343    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
1344        \p or \P) caused a compile-time loop.
1346    28. More problems have arisen in unanchored patterns when CRLF is a valid line
1347        break. For example, the unstudied pattern [\r\n]A does not match the string
1348        "\r\nA" because change 7.0/46 below moves the current point on by two
1349        characters after failing to match at the start. However, the pattern \nA
1350        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
1351        the same is true. There doesn't seem any very clean way out of this, but
1352        what I have chosen to do makes the common cases work: PCRE now takes note
1353        of whether there can be an explicit match for \r or \n anywhere in the
1354        pattern, and if so, 7.0/46 no longer applies. As part of this change,
1355        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
1356        pattern has explicit CR or LF references.
1358    29. Added (*CR) etc for changing newline setting at start of pattern.
1361    Version 7.2 19-Jun-07
1362    ---------------------
1364     1. If the fr_FR locale cannot be found for test 3, try the "french" locale,
1365        which is apparently normally available under Windows.
1367     2. Re-jig the pcregrep tests with different newline settings in an attempt
1368        to make them independent of the local environment's newline setting.
1370     3. Add code to configure.ac to remove -g from the CFLAGS default settings.
1372     4. Some of the "internals" tests were previously cut out when the link size
1373        was not 2, because the output contained actual offsets. The recent new
1374        "Z" feature of pcretest means that these can be cut out, making the tests
1375        usable with all link sizes.
1377     5. Implemented Stan Switzer's goto replacement for longjmp() when not using
1378        stack recursion. This gives a massive performance boost under BSD, but just
1379        a small improvement under Linux. However, it saves one field in the frame
1380        in all cases.
1382     6. Added more features from the forthcoming Perl 5.10:
1384        (a) (?-n) (where n is a string of digits) is a relative subroutine or
1385            recursion call. It refers to the nth most recently opened parentheses.
1387        (b) (?+n) is also a relative subroutine call; it refers to the nth next
1388            to be opened parentheses.
1390        (c) Conditions that refer to capturing parentheses can be specified
1391            relatively, for example, (?(-2)... or (?(+3)...
1393        (d) \K resets the start of the current match so that everything before
1394            is not part of it.
1396        (e) \k{name} is synonymous with \k<name> and \k'name' (.NET compatible).
1398        (f) \g{name} is another synonym - part of Perl 5.10's unification of
1399            reference syntax.
1401        (g) (?| introduces a group in which the numbering of parentheses in each
1402            alternative starts with the same number.
1404        (h) \h, \H, \v, and \V match horizontal and vertical whitespace.
1406     7. Added two new calls to pcre_fullinfo(): PCRE_INFO_OKPARTIAL and
1409     8. A pattern such as  (.*(.)?)*  caused pcre_exec() to fail by either not
1410        terminating or by crashing. Diagnosed by Viktor Griph; it was in the code
1411        for detecting groups that can match an empty string.
1413     9. A pattern with a very large number of alternatives (more than several
1414        hundred) was running out of internal workspace during the pre-compile
1415        phase, where pcre_compile() figures out how much memory will be needed. A
1416        bit of new cunning has reduced the workspace needed for groups with
1417        alternatives. The 1000-alternative test pattern now uses 12 bytes of
1418        workspace instead of running out of the 4096 that are available.
1420    10. Inserted some missing (unsigned int) casts to get rid of compiler warnings.
1422    11. Applied patch from Google to remove an optimization that didn't quite work.
1423        The report of the bug said:
1425          pcrecpp::RE("a*").FullMatch("aaa") matches, while
1426          pcrecpp::RE("a*?").FullMatch("aaa") does not, and
1427          pcrecpp::RE("a*?\\z").FullMatch("aaa") does again.
1429    12. If \p or \P was used in non-UTF-8 mode on a character greater than 127
1430        it matched the wrong number of bytes.
1433    Version 7.1 24-Apr-07
1434    ---------------------
1436     1. Applied Bob Rossi and Daniel G's patches to convert the build system to one
1437        that is more "standard", making use of automake and other Autotools. There
1438      is some re-arrangement of the files and adjustment of comments consequent      is some re-arrangement of the files and adjustment of comments consequent
1439      on this.      on this.
1441   2. Part of the patch fixed a problem with the pcregrep tests. The test of -r   2. Part of the patch fixed a problem with the pcregrep tests. The test of -r
1442      for recursive directory scanning broke on some systems because the files      for recursive directory scanning broke on some systems because the files
1443      are not scanned in any specific order and on different systems the order      are not scanned in any specific order and on different systems the order
1444      was different. A call to "sort" has been inserted into RunGrepTest for the      was different. A call to "sort" has been inserted into RunGrepTest for the
1445      approprate test as a short-term fix. In the longer term there may be an      approprate test as a short-term fix. In the longer term there may be an
1446      alternative.      alternative.
1448   3. I had an email from Eric Raymond about problems translating some of PCRE's   3. I had an email from Eric Raymond about problems translating some of PCRE's
1449      man pages to HTML (despite the fact that I distribute HTML pages, some      man pages to HTML (despite the fact that I distribute HTML pages, some
1450      people do their own conversions for various reasons). The problems      people do their own conversions for various reasons). The problems
1451      concerned the use of low-level troff macros .br and .in. I have therefore      concerned the use of low-level troff macros .br and .in. I have therefore
1452      removed all such uses from the man pages (some were redundant, some could      removed all such uses from the man pages (some were redundant, some could
1453      be replaced by .nf/.fi pairs). The maintain/132html script that I use to      be replaced by .nf/.fi pairs). The 132html script that I use to generate
1454      generate HTML has been updated to handle .nf/.fi and to complain if it      HTML has been updated to handle .nf/.fi and to complain if it encounters
1455      encounters .br or .in.      .br or .in.
1457   4. Updated comments in configure.ac that get placed in config.h.in and also   4. Updated comments in configure.ac that get placed in config.h.in and also
1458      arranged for config.h to be included in the distribution, for the benefit      arranged for config.h to be included in the distribution, with the name
1459      of those who have to compile without Autotools (compare pcre.h).      config.h.generic, for the benefit of those who have to compile without
1460        Autotools (compare pcre.h, which is now distributed as pcre.h.generic).
1461   5. Updated the support (such as it is) for Virtual Pascal, thanks to Stefan  
1462      Weber: (1) pcre_internal.h was missing some function renames; (2) updated   5. Updated the support (such as it is) for Virtual Pascal, thanks to Stefan
1463      makevp.bat for the current PCRE, using the additional files !compile.txt,      Weber: (1) pcre_internal.h was missing some function renames; (2) updated
1464      !linklib.txt, and pcregexp.pas.      makevp.bat for the current PCRE, using the additional files
1465        makevp_c.txt, makevp_l.txt, and pcregexp.pas.
1466   6. A Windows user reported a minor discrepancy with test 2, which turned out  
1467      to be caused by a trailing space on an input line that had got lost in his   6. A Windows user reported a minor discrepancy with test 2, which turned out
1468        to be caused by a trailing space on an input line that had got lost in his
1469      copy. The trailing space was an accident, so I've just removed it.      copy. The trailing space was an accident, so I've just removed it.
1471   7. Add -Wl,-R... flags in pcre-config.in for *BSD* systems, as I'm told   7. Add -Wl,-R... flags in pcre-config.in for *BSD* systems, as I'm told
1472      that is needed.      that is needed.
1474   8. Mark ucp_table (in ucptable.h) and ucp_gentype (in pcre_ucp_searchfuncs.c)   8. Mark ucp_table (in ucptable.h) and ucp_gentype (in pcre_ucp_searchfuncs.c)
1475      as "const" (a) because they are and (b) because it helps the PHP      as "const" (a) because they are and (b) because it helps the PHP
1476      maintainers who have recently made a script to detect big data structures      maintainers who have recently made a script to detect big data structures
1477      in the php code that should be moved to the .rodata section. I remembered      in the php code that should be moved to the .rodata section. I remembered
1478      to update Builducptable as well, so it won't revert if ucptable.h is ever      to update Builducptable as well, so it won't revert if ucptable.h is ever
1479      re-created.      re-created.
1481     9. Added some extra #ifdef SUPPORT_UTF8 conditionals into pcretest.c,
1482        pcre_printint.src, pcre_compile.c, pcre_study.c, and pcre_tables.c, in
1483        order to be able to cut out the UTF-8 tables in the latter when UTF-8
1484        support is not required. This saves 1.5-2K of code, which is important in
1485        some applications.
1487        Later: more #ifdefs are needed in pcre_ord2utf8.c and pcre_valid_utf8.c
1488        so as not to refer to the tables, even though these functions will never be
1489        called when UTF-8 support is disabled. Otherwise there are problems with a
1490        shared library.
1492    10. Fixed two bugs in the emulated memmove() function in pcre_internal.h:
1494        (a) It was defining its arguments as char * instead of void *.
1496        (b) It was assuming that all moves were upwards in memory; this was true
1497            a long time ago when I wrote it, but is no longer the case.
1499        The emulated memove() is provided for those environments that have neither
1500        memmove() nor bcopy(). I didn't think anyone used it these days, but that
1501        is clearly not the case, as these two bugs were recently reported.
1503    11. The script PrepareRelease is now distributed: it calls 132html, CleanTxt,
1504        and Detrail to create the HTML documentation, the .txt form of the man
1505        pages, and it removes trailing spaces from listed files. It also creates
1506        pcre.h.generic and config.h.generic from pcre.h and config.h. In the latter
1507        case, it wraps all the #defines with #ifndefs. This script should be run
1508        before "make dist".
1510    12. Fixed two fairly obscure bugs concerned with quantified caseless matching
1511        with Unicode property support.
1513        (a) For a maximizing quantifier, if the two different cases of the
1514            character were of different lengths in their UTF-8 codings (there are
1515            some cases like this - I found 11), and the matching function had to
1516            back up over a mixture of the two cases, it incorrectly assumed they
1517            were both the same length.
1519        (b) When PCRE was configured to use the heap rather than the stack for
1520            recursion during matching, it was not correctly preserving the data for
1521            the other case of a UTF-8 character when checking ahead for a match
1522            while processing a minimizing repeat. If the check also involved
1523            matching a wide character, but failed, corruption could cause an
1524            erroneous result when trying to check for a repeat of the original
1525            character.
1527    13. Some tidying changes to the testing mechanism:
1529        (a) The RunTest script now detects the internal link size and whether there
1530            is UTF-8 and UCP support by running ./pcretest -C instead of relying on
1531            values substituted by "configure". (The RunGrepTest script already did
1532            this for UTF-8.) The configure.ac script no longer substitutes the
1533            relevant variables.
1535        (b) The debugging options /B and /D in pcretest show the compiled bytecode
1536            with length and offset values. This means that the output is different
1537            for different internal link sizes. Test 2 is skipped for link sizes
1538            other than 2 because of this, bypassing the problem. Unfortunately,
1539            there was also a test in test 3 (the locale tests) that used /B and
1540            failed for link sizes other than 2. Rather than cut the whole test out,
1541            I have added a new /Z option to pcretest that replaces the length and
1542            offset values with spaces. This is now used to make test 3 independent
1543            of link size. (Test 2 will be tidied up later.)
1545    14. If erroroffset was passed as NULL to pcre_compile, it provoked a
1546        segmentation fault instead of returning the appropriate error message.
1548    15. In multiline mode when the newline sequence was set to "any", the pattern
1549        ^$ would give a match between the \r and \n of a subject such as "A\r\nB".
1550        This doesn't seem right; it now treats the CRLF combination as the line
1551        ending, and so does not match in that case. It's only a pattern such as ^$
1552        that would hit this one: something like ^ABC$ would have failed after \r
1553        and then tried again after \r\n.
1555    16. Changed the comparison command for RunGrepTest from "diff -u" to "diff -ub"
1556        in an attempt to make files that differ only in their line terminators
1557        compare equal. This works on Linux.
1559    17. Under certain error circumstances pcregrep might try to free random memory
1560        as it exited. This is now fixed, thanks to valgrind.
1562    19. In pcretest, if the pattern /(?m)^$/g<any> was matched against the string
1563        "abc\r\n\r\n", it found an unwanted second match after the second \r. This
1564        was because its rules for how to advance for /g after matching an empty
1565        string at the end of a line did not allow for this case. They now check for
1566        it specially.
1568    20. pcretest is supposed to handle patterns and data of any length, by
1569        extending its buffers when necessary. It was getting this wrong when the
1570        buffer for a data line had to be extended.
1572    21. Added PCRE_NEWLINE_ANYCRLF which is like ANY, but matches only CR, LF, or
1573        CRLF as a newline sequence.
1575    22. Code for handling Unicode properties in pcre_dfa_exec() wasn't being cut
1576        out by #ifdef SUPPORT_UCP. This did no harm, as it could never be used, but
1577        I have nevertheless tidied it up.
1579    23. Added some casts to kill warnings from HP-UX ia64 compiler.
1581    24. Added a man page for pcre-config.
1584  Version 7.0 19-Dec-06  Version 7.0 19-Dec-06
1585  ---------------------  ---------------------

Removed from v.105  
changed lines
  Added in v.593

  ViewVC Help
Powered by ViewVC 1.1.5