ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 223 by ph10, Mon Aug 20 11:07:53 2007 UTC revision 595 by ph10, Mon May 2 10:33:29 2011 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 7.3 20-Aug-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.
11    3.  Added #include <string.h> to pcre_scanner_unittest.cc, pcrecpp.cc, and
12        pcrecpp_unittest.cc. They are needed for strcmp(), memset(), and strchr()
13        in some environments (e.g. Solaris 10/SPARC using Sun Studio 12U2).
15    4.  There were a number of related bugs in the code for matching backrefences
16        caselessly in UTF-8 mode when codes for the characters concerned were
17        different numbers of bytes. For example, U+023A and U+2C65 are an upper
18        and lower case pair, using 2 and 3 bytes, respectively. The main bugs were:
19        (a) A reference to 3 copies of a 2-byte code matched only 2 of a 3-byte
20        code. (b) A reference to 2 copies of a 3-byte code would not match 2 of a
21        2-byte code at the end of the subject (it thought there wasn't enough data
22        left).
25    Version 8.12 15-Jan-2011
26    ------------------------
28    1.  Fixed some typos in the markup of the man pages, and wrote a script that
29        checks for such things as part of the documentation building process.
31    2.  On a big-endian 64-bit system, pcregrep did not correctly process the
32        --match-limit and --recursion-limit options (added for 8.11). In
33        particular, this made one of the standard tests fail. (The integer value
34        went into the wrong half of a long int.)
36    3.  If the --colour option was given to pcregrep with -v (invert match), it
37        did strange things, either producing crazy output, or crashing. It should,
38        of course, ignore a request for colour when reporting lines that do not
39        match.
41    4.  Another pcregrep bug caused similar problems if --colour was specified with
42        -M (multiline) and the pattern match finished with a line ending.
44    5.  In pcregrep, when a pattern that ended with a literal newline sequence was
45        matched in multiline mode, the following line was shown as part of the
46        match. This seems wrong, so I have changed it.
48    6.  Another pcregrep bug in multiline mode, when --colour was specified, caused
49        the check for further matches in the same line (so they could be coloured)
50        to overrun the end of the current line. If another match was found, it was
51        incorrectly shown (and then shown again when found in the next line).
53    7.  If pcregrep was compiled under Windows, there was a reference to the
54        function pcregrep_exit() before it was defined. I am assuming this was
55        the cause of the "error C2371: 'pcregrep_exit' : redefinition;" that was
56        reported by a user. I've moved the definition above the reference.
59    Version 8.11 10-Dec-2010
60    ------------------------
62    1.  (*THEN) was not working properly if there were untried alternatives prior
63        to it in the current branch. For example, in ((a|b)(*THEN)(*F)|c..) it
64        backtracked to try for "b" instead of moving to the next alternative branch
65        at the same level (in this case, to look for "c"). The Perl documentation
66        is clear that when (*THEN) is backtracked onto, it goes to the "next
67        alternative in the innermost enclosing group".
69    2.  (*COMMIT) was not overriding (*THEN), as it does in Perl. In a pattern
70        such as   (A(*COMMIT)B(*THEN)C|D)  any failure after matching A should
71        result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and
72        (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides
73        (*THEN).
75    3.  If \s appeared in a character class, it removed the VT character from
76        the class, even if it had been included by some previous item, for example
77        in [\x00-\xff\s]. (This was a bug related to the fact that VT is not part
78        of \s, but is part of the POSIX "space" class.)
80    4.  A partial match never returns an empty string (because you can always
81        match an empty string at the end of the subject); however the checking for
82        an empty string was starting at the "start of match" point. This has been
83        changed to the "earliest inspected character" point, because the returned
84        data for a partial match starts at this character. This means that, for
85        example, /(?<=abc)def/ gives a partial match for the subject "abc"
86        (previously it gave "no match").
88    5.  Changes have been made to the way PCRE_PARTIAL_HARD affects the matching
89        of $, \z, \Z, \b, and \B. If the match point is at the end of the string,
90        previously a full match would be given. However, setting PCRE_PARTIAL_HARD
91        has an implication that the given string is incomplete (because a partial
92        match is preferred over a full match). For this reason, these items now
93        give a partial match in this situation. [Aside: previously, the one case
94        /t\b/ matched against "cat" with PCRE_PARTIAL_HARD set did return a partial
95        match rather than a full match, which was wrong by the old rules, but is
96        now correct.]
98    6.  There was a bug in the handling of #-introduced comments, recognized when
99        PCRE_EXTENDED is set, when PCRE_NEWLINE_ANY and PCRE_UTF8 were also set.
100        If a UTF-8 multi-byte character included the byte 0x85 (e.g. +U0445, whose
101        UTF-8 encoding is 0xd1,0x85), this was misinterpreted as a newline when
102        scanning for the end of the comment. (*Character* 0x85 is an "any" newline,
103        but *byte* 0x85 is not, in UTF-8 mode). This bug was present in several
104        places in pcre_compile().
106    7.  Related to (6) above, when pcre_compile() was skipping #-introduced
107        comments when looking ahead for named forward references to subpatterns,
108        the only newline sequence it recognized was NL. It now handles newlines
109        according to the set newline convention.
111    8.  SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the
112        former, but used strtoul(), whereas pcretest avoided strtoul() but did not
113        cater for a lack of strerror(). These oversights have been fixed.
115    9.  Added --match-limit and --recursion-limit to pcregrep.
117    10. Added two casts needed to build with Visual Studio when NO_RECURSE is set.
119    11. When the -o option was used, pcregrep was setting a return code of 1, even
120        when matches were found, and --line-buffered was not being honoured.
122    12. Added an optional parentheses number to the -o and --only-matching options
123        of pcregrep.
125    13. Imitating Perl's /g action for multiple matches is tricky when the pattern
126        can match an empty string. The code to do it in pcretest and pcredemo
127        needed fixing:
129        (a) When the newline convention was "crlf", pcretest got it wrong, skipping
130            only one byte after an empty string match just before CRLF (this case
131            just got forgotten; "any" and "anycrlf" were OK).
133        (b) The pcretest code also had a bug, causing it to loop forever in UTF-8
134            mode when an empty string match preceded an ASCII character followed by
135            a non-ASCII character. (The code for advancing by one character rather
136            than one byte was nonsense.)
138        (c) The pcredemo.c sample program did not have any code at all to handle
139            the cases when CRLF is a valid newline sequence.
141    14. Neither pcre_exec() nor pcre_dfa_exec() was checking that the value given
142        as a starting offset was within the subject string. There is now a new
143        error, PCRE_ERROR_BADOFFSET, which is returned if the starting offset is
144        negative or greater than the length of the string. In order to test this,
145        pcretest is extended to allow the setting of negative starting offsets.
147    15. In both pcre_exec() and pcre_dfa_exec() the code for checking that the
148        starting offset points to the beginning of a UTF-8 character was
149        unnecessarily clumsy. I tidied it up.
151    16. Added PCRE_ERROR_SHORTUTF8 to make it possible to distinguish between a
152        bad UTF-8 sequence and one that is incomplete when using PCRE_PARTIAL_HARD.
154    17. Nobody had reported that the --include_dir option, which was added in
155        release 7.7 should have been called --include-dir (hyphen, not underscore)
156        for compatibility with GNU grep. I have changed it to --include-dir, but
157        left --include_dir as an undocumented synonym, and the same for
158        --exclude-dir, though that is not available in GNU grep, at least as of
159        release 2.5.4.
161    18. At a user's suggestion, the macros GETCHAR and friends (which pick up UTF-8
162        characters from a string of bytes) have been redefined so as not to use
163        loops, in order to improve performance in some environments. At the same
164        time, I abstracted some of the common code into auxiliary macros to save
165        repetition (this should not affect the compiled code).
167    19. If \c was followed by a multibyte UTF-8 character, bad things happened. A
168        compile-time error is now given if \c is not followed by an ASCII
169        character, that is, a byte less than 128. (In EBCDIC mode, the code is
170        different, and any byte value is allowed.)
172    20. Recognize (*NO_START_OPT) at the start of a pattern to set the PCRE_NO_
173        START_OPTIMIZE option, which is now allowed at compile time - but just
174        passed through to pcre_exec() or pcre_dfa_exec(). This makes it available
175        to pcregrep and other applications that have no direct access to PCRE
176        options. The new /Y option in pcretest sets this option when calling
177        pcre_compile().
179    21. Change 18 of release 8.01 broke the use of named subpatterns for recursive
180        back references. Groups containing recursive back references were forced to
181        be atomic by that change, but in the case of named groups, the amount of
182        memory required was incorrectly computed, leading to "Failed: internal
183        error: code overflow". This has been fixed.
185    22. Some patches to pcre_stringpiece.h, pcre_stringpiece_unittest.cc, and
186        pcretest.c, to avoid build problems in some Borland environments.
189    Version 8.10 25-Jun-2010
190    ------------------------
192    1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and
193        THEN.
195    2.  (*ACCEPT) was not working when inside an atomic group.
197    3.  Inside a character class, \B is treated as a literal by default, but
198        faulted if PCRE_EXTRA is set. This mimics Perl's behaviour (the -w option
199        causes the error). The code is unchanged, but I tidied the documentation.
201    4.  Inside a character class, PCRE always treated \R and \X as literals,
202        whereas Perl faults them if its -w option is set. I have changed PCRE so
203        that it faults them when PCRE_EXTRA is set.
205    5.  Added support for \N, which always matches any character other than
206        newline. (It is the same as "." when PCRE_DOTALL is not set.)
208    6.  When compiling pcregrep with newer versions of gcc which may have
209        FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',
210        declared with attribute warn_unused_result" were given. Just casting the
211        result to (void) does not stop the warnings; a more elaborate fudge is
212        needed. I've used a macro to implement this.
214    7.  Minor change to pcretest.c to avoid a compiler warning.
216    8.  Added four artifical Unicode properties to help with an option to make
217        \s etc use properties (see next item). The new properties are: Xan
218        (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).
220    9.  Added PCRE_UCP to make \b, \d, \s, \w, and certain POSIX character classes
221        use Unicode properties. (*UCP) at the start of a pattern can be used to set
222        this option. Modified pcretest to add /W to test this facility. Added
223        REG_UCP to make it available via the POSIX interface.
225    10. Added --line-buffered to pcregrep.
227    11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was
228        studied, and the match started with a letter with a code point greater than
229        127 whose first byte was different to the first byte of the other case of
230        the letter, the other case of this starting letter was not recognized
231        (#976).
233    12. If a pattern that was studied started with a repeated Unicode property
234        test, for example, \p{Nd}+, there was the theoretical possibility of
235        setting up an incorrect bitmap of starting bytes, but fortunately it could
236        not have actually happened in practice until change 8 above was made (it
237        added property types that matched character-matching opcodes).
239    13. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
240        possible starting bytes for non-anchored patterns.
242    14. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes
243        \R, and also a number of cases that involve Unicode properties, both
244        explicit and implicit when PCRE_UCP is set.
246    15. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8
247        input, it could crash or give wrong results if characters with values
248        greater than 0xc0 were present in the subject string. (Detail: it assumed
249        UTF-8 input when processing these items.)
251    16. Added a lot of (int) casts to avoid compiler warnings in systems where
252        size_t is 64-bit (#991).
254    17. Added a check for running out of memory when PCRE is compiled with
255        --disable-stack-for-recursion (#990).
257    18. If the last data line in a file for pcretest does not have a newline on
258        the end, a newline was missing in the output.
260    19. The default pcre_chartables.c file recognizes only ASCII characters (values
261        less than 128) in its various bitmaps. However, there is a facility for
262        generating tables according to the current locale when PCRE is compiled. It
263        turns out that in some environments, 0x85 and 0xa0, which are Unicode space
264        characters, are recognized by isspace() and therefore were getting set in
265        these tables, and indeed these tables seem to approximate to ISO 8859. This
266        caused a problem in UTF-8 mode when pcre_study() was used to create a list
267        of bytes that can start a match. For \s, it was including 0x85 and 0xa0,
268        which of course cannot start UTF-8 characters. I have changed the code so
269        that only real ASCII characters (less than 128) and the correct starting
270        bytes for UTF-8 encodings are set for characters greater than 127 when in
271        UTF-8 mode. (When PCRE_UCP is set - see 9 above - the code is different
272        altogether.)
274    20. Added the /T option to pcretest so as to be able to run tests with non-
275        standard character tables, thus making it possible to include the tests
276        used for 19 above in the standard set of tests.
278    21. A pattern such as (?&t)(?#()(?(DEFINE)(?<t>a)) which has a forward
279        reference to a subpattern the other side of a comment that contains an
280        opening parenthesis caused either an internal compiling error, or a
281        reference to the wrong subpattern.
284    Version 8.02 19-Mar-2010
285    ------------------------
287    1.  The Unicode data tables have been updated to Unicode 5.2.0.
289    2.  Added the option --libs-cpp to pcre-config, but only when C++ support is
290        configured.
292    3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the
293        original author of that file, following a query about its status.
295    4.  On systems that do not have stdint.h (e.g. Solaris), check for and include
296        inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
298    5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
299        quantifier applied to a forward-referencing subroutine call, could compile
300        incorrect code or give the error "internal error: previously-checked
301        referenced subpattern not found".
303    6.  Both MS Visual Studio and Symbian OS have problems with initializing
304        variables to point to external functions. For these systems, therefore,
305        pcre_malloc etc. are now initialized to local functions that call the
306        relevant global functions.
308    7.  There were two entries missing in the vectors called coptable and poptable
309        in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.
310        I've fixed the data, and added a kludgy way of testing at compile time that
311        the lengths are correct (equal to the number of opcodes).
313    8.  Following on from 7, I added a similar kludge to check the length of the
314        eint vector in pcreposix.c.
316    9.  Error texts for pcre_compile() are held as one long string to avoid too
317        much relocation at load time. To find a text, the string is searched,
318        counting zeros. There was no check for running off the end of the string,
319        which could happen if a new error number was added without updating the
320        string.
322    10. \K gave a compile-time error if it appeared in a lookbehind assersion.
324    11. \K was not working if it appeared in an atomic group or in a group that
325        was called as a "subroutine", or in an assertion. Perl 5.11 documents that
326        \K is "not well defined" if used in an assertion. PCRE now accepts it if
327        the assertion is positive, but not if it is negative.
329    12. Change 11 fortuitously reduced the size of the stack frame used in the
330        "match()" function of pcre_exec.c by one pointer. Forthcoming
331        implementation of support for (*MARK) will need an extra pointer on the
332        stack; I have reserved it now, so that the stack frame size does not
333        decrease.
335    13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other
336        item in branch that calls a recursion is a subroutine call - as in the
337        second branch in the above example - was incorrectly given the compile-
338        time error "recursive call could loop indefinitely" because pcre_compile()
339        was not correctly checking the subroutine for matching a non-empty string.
341    14. The checks for overrunning compiling workspace could trigger after an
342        overrun had occurred. This is a "should never occur" error, but it can be
343        triggered by pathological patterns such as hundreds of nested parentheses.
344        The checks now trigger 100 bytes before the end of the workspace.
346    15. Fix typo in configure.ac: "srtoq" should be "strtoq".
349    Version 8.01 19-Jan-2010
350    ------------------------
352    1.  If a pattern contained a conditional subpattern with only one branch (in
353        particular, this includes all (*DEFINE) patterns), a call to pcre_study()
354        computed the wrong minimum data length (which is of course zero for such
355        subpatterns). This could cause incorrect "no match" results.
357    2.  For patterns such as (?i)a(?-i)b|c where an option setting at the start of
358        the pattern is reset in the first branch, pcre_compile() failed with
359        "internal error: code overflow at offset...". This happened only when
360        the reset was to the original external option setting. (An optimization
361        abstracts leading options settings into an external setting, which was the
362        cause of this.)
364    3.  A pattern such as ^(?!a(*SKIP)b) where a negative assertion contained one
365        of the verbs SKIP, PRUNE, or COMMIT, did not work correctly. When the
366        assertion pattern did not match (meaning that the assertion was true), it
367        was incorrectly treated as false if the SKIP had been reached during the
368        matching. This also applied to assertions used as conditions.
370    4.  If an item that is not supported by pcre_dfa_exec() was encountered in an
371        assertion subpattern, including such a pattern used as a condition,
372        unpredictable results occurred, instead of the error return
375    5.  The C++ GlobalReplace function was not working like Perl for the special
376        situation when an empty string is matched. It now does the fancy magic
377        stuff that is necessary.
379    6.  In pcre_internal.h, obsolete includes to setjmp.h and stdarg.h have been
380        removed. (These were left over from very, very early versions of PCRE.)
382    7.  Some cosmetic changes to the code to make life easier when compiling it
383        as part of something else:
385        (a) Change DEBUG to PCRE_DEBUG.
387        (b) In pcre_compile(), rename the member of the "branch_chain" structure
388            called "current" as "current_branch", to prevent a collision with the
389            Linux macro when compiled as a kernel module.
391        (c) In pcre_study(), rename the function set_bit() as set_table_bit(), to
392            prevent a collision with the Linux macro when compiled as a kernel
393            module.
395    8.  In pcre_compile() there are some checks for integer overflows that used to
396        cast potentially large values to (double). This has been changed to that
397        when building, a check for int64_t is made, and if it is found, it is used
398        instead, thus avoiding the use of floating point arithmetic. (There is no
399        other use of FP in PCRE.) If int64_t is not found, the fallback is to
400        double.
402    9.  Added two casts to avoid signed/unsigned warnings from VS Studio Express
403        2005 (difference between two addresses compared to an unsigned value).
405    10. Change the standard AC_CHECK_LIB test for libbz2 in configure.ac to a
406        custom one, because of the following reported problem in Windows:
408          - libbz2 uses the Pascal calling convention (WINAPI) for the functions
409              under Win32.
410          - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",
411              therefore missing the function definition.
412          - The compiler thus generates a "C" signature for the test function.
413          - The linker fails to find the "C" function.
414          - PCRE fails to configure if asked to do so against libbz2.
416    11. When running libtoolize from libtool-2.2.6b as part of autogen.sh, these
417        messages were output:
419          Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
420          rerunning libtoolize, to keep the correct libtool macros in-tree.
421          Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
423        I have done both of these things.
425    12. Although pcre_dfa_exec() does not use nearly as much stack as pcre_exec()
426        most of the time, it *can* run out if it is given a pattern that contains a
427        runaway infinite recursion. I updated the discussion in the pcrestack man
428        page.
430    13. Now that we have gone to the x.xx style of version numbers, the minor
431        version may start with zero. Using 08 or 09 is a bad idea because users
432        might check the value of PCRE_MINOR in their code, and 08 or 09 may be
433        interpreted as invalid octal numbers. I've updated the previous comment in
434        configure.ac, and also added a check that gives an error if 08 or 09 are
435        used.
437    14. Change 8.00/11 was not quite complete: code had been accidentally omitted,
438        causing partial matching to fail when the end of the subject matched \W
439        in a UTF-8 pattern where \W was quantified with a minimum of 3.
441    15. There were some discrepancies between the declarations in pcre_internal.h
442        of _pcre_is_newline(), _pcre_was_newline(), and _pcre_valid_utf8() and
443        their definitions. The declarations used "const uschar *" and the
444        definitions used USPTR. Even though USPTR is normally defined as "const
445        unsigned char *" (and uschar is typedeffed as "unsigned char"), it was
446        reported that: "This difference in casting confuses some C++ compilers, for
447        example, SunCC recognizes above declarations as different functions and
448        generates broken code for hbpcre." I have changed the declarations to use
449        USPTR.
451    16. GNU libtool is named differently on some systems. The autogen.sh script now
452        tries several variants such as glibtoolize (MacOSX) and libtoolize1x
453        (FreeBSD).
455    17. Applied Craig's patch that fixes an HP aCC compile error in pcre 8.00
456        (strtoXX undefined when compiling pcrecpp.cc). The patch contains this
457        comment: "Figure out how to create a longlong from a string: strtoll and
458        equivalent. It's not enough to call AC_CHECK_FUNCS: hpux has a strtoll, for
459        instance, but it only takes 2 args instead of 3!"
461    18. A subtle bug concerned with back references has been fixed by a change of
462        specification, with a corresponding code fix. A pattern such as
463        ^(xa|=?\1a)+$ which contains a back reference inside the group to which it
464        refers, was giving matches when it shouldn't. For example, xa=xaaa would
465        match that pattern. Interestingly, Perl (at least up to 5.11.3) has the
466        same bug. Such groups have to be quantified to be useful, or contained
467        inside another quantified group. (If there's no repetition, the reference
468        can never match.) The problem arises because, having left the group and
469        moved on to the rest of the pattern, a later failure that backtracks into
470        the group uses the captured value from the final iteration of the group
471        rather than the correct earlier one. I have fixed this in PCRE by forcing
472        any group that contains a reference to itself to be an atomic group; that
473        is, there cannot be any backtracking into it once it has completed. This is
474        similar to recursive and subroutine calls.
477    Version 8.00 19-Oct-09
478    ----------------------
480    1.  The table for translating pcre_compile() error codes into POSIX error codes
481        was out-of-date, and there was no check on the pcre_compile() error code
482        being within the table. This could lead to an OK return being given in
483        error.
485    2.  Changed the call to open a subject file in pcregrep from fopen(pathname,
486        "r") to fopen(pathname, "rb"), which fixed a problem with some of the tests
487        in a Windows environment.
489    3.  The pcregrep --count option prints the count for each file even when it is
490        zero, as does GNU grep. However, pcregrep was also printing all files when
491        --files-with-matches was added. Now, when both options are given, it prints
492        counts only for those files that have at least one match. (GNU grep just
493        prints the file name in this circumstance, but including the count seems
494        more useful - otherwise, why use --count?) Also ensured that the
495        combination -clh just lists non-zero counts, with no names.
497    4.  The long form of the pcregrep -F option was incorrectly implemented as
498        --fixed_strings instead of --fixed-strings. This is an incompatible change,
499        but it seems right to fix it, and I didn't think it was worth preserving
500        the old behaviour.
502    5.  The command line items --regex=pattern and --regexp=pattern were not
503        recognized by pcregrep, which required --regex pattern or --regexp pattern
504        (with a space rather than an '='). The man page documented the '=' forms,
505        which are compatible with GNU grep; these now work.
507    6.  No libpcreposix.pc file was created for pkg-config; there was just
508        libpcre.pc and libpcrecpp.pc. The omission has been rectified.
510    7.  Added #ifndef SUPPORT_UCP into the pcre_ucd.c module, to reduce its size
511        when UCP support is not needed, by modifying the Python script that
512        generates it from Unicode data files. This should not matter if the module
513        is correctly used as a library, but I received one complaint about 50K of
514        unwanted data. My guess is that the person linked everything into his
515        program rather than using a library. Anyway, it does no harm.
517    8.  A pattern such as /\x{123}{2,2}+/8 was incorrectly compiled; the trigger
518        was a minimum greater than 1 for a wide character in a possessive
519        repetition. The same bug could also affect patterns like /(\x{ff}{0,2})*/8
520        which had an unlimited repeat of a nested, fixed maximum repeat of a wide
521        character. Chaos in the form of incorrect output or a compiling loop could
522        result.
524    9.  The restrictions on what a pattern can contain when partial matching is
525        requested for pcre_exec() have been removed. All patterns can now be
526        partially matched by this function. In addition, if there are at least two
527        slots in the offset vector, the offset of the earliest inspected character
528        for the match and the offset of the end of the subject are set in them when
529        PCRE_ERROR_PARTIAL is returned.
531    10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is
532        synonymous with PCRE_PARTIAL, for backwards compatibility, and
533        PCRE_PARTIAL_HARD, which causes a partial match to supersede a full match,
534        and may be more useful for multi-segment matching.
536    11. Partial matching with pcre_exec() is now more intuitive. A partial match
537        used to be given if ever the end of the subject was reached; now it is
538        given only if matching could not proceed because another character was
539        needed. This makes a difference in some odd cases such as Z(*FAIL) with the
540        string "Z", which now yields "no match" instead of "partial match". In the
541        case of pcre_dfa_exec(), "no match" is given if every matching path for the
542        final character ended with (*FAIL).
544    12. Restarting a match using pcre_dfa_exec() after a partial match did not work
545        if the pattern had a "must contain" character that was already found in the
546        earlier partial match, unless partial matching was again requested. For
547        example, with the pattern /dog.(body)?/, the "must contain" character is
548        "g". If the first part-match was for the string "dog", restarting with
549        "sbody" failed. This bug has been fixed.
551    13. The string returned by pcre_dfa_exec() after a partial match has been
552        changed so that it starts at the first inspected character rather than the
553        first character of the match. This makes a difference only if the pattern
554        starts with a lookbehind assertion or \b or \B (\K is not supported by
555        pcre_dfa_exec()). It's an incompatible change, but it makes the two
556        matching functions compatible, and I think it's the right thing to do.
558    14. Added a pcredemo man page, created automatically from the pcredemo.c file,
559        so that the demonstration program is easily available in environments where
560        PCRE has not been installed from source.
562    15. Arranged to add -DPCRE_STATIC to cflags in libpcre.pc, libpcreposix.cp,
563        libpcrecpp.pc and pcre-config when PCRE is not compiled as a shared
564        library.
566    16. Added REG_UNGREEDY to the pcreposix interface, at the request of a user.
567        It maps to PCRE_UNGREEDY. It is not, of course, POSIX-compatible, but it
568        is not the first non-POSIX option to be added. Clearly some people find
569        these options useful.
571    17. If a caller to the POSIX matching function regexec() passes a non-zero
572        value for nmatch with a NULL value for pmatch, the value of
573        nmatch is forced to zero.
575    18. RunGrepTest did not have a test for the availability of the -u option of
576        the diff command, as RunTest does. It now checks in the same way as
577        RunTest, and also checks for the -b option.
579    19. If an odd number of negated classes containing just a single character
580        interposed, within parentheses, between a forward reference to a named
581        subpattern and the definition of the subpattern, compilation crashed with
582        an internal error, complaining that it could not find the referenced
583        subpattern. An example of a crashing pattern is /(?&A)(([^m])(?<A>))/.
584        [The bug was that it was starting one character too far in when skipping
585        over the character class, thus treating the ] as data rather than
586        terminating the class. This meant it could skip too much.]
588    20. Added PCRE_NOTEMPTY_ATSTART in order to be able to correctly implement the
589        /g option in pcretest when the pattern contains \K, which makes it possible
590        to have an empty string match not at the start, even when the pattern is
591        anchored. Updated pcretest and pcredemo to use this option.
593    21. If the maximum number of capturing subpatterns in a recursion was greater
594        than the maximum at the outer level, the higher number was returned, but
595        with unset values at the outer level. The correct (outer level) value is
596        now given.
598    22. If (*ACCEPT) appeared inside capturing parentheses, previous releases of
599        PCRE did not set those parentheses (unlike Perl). I have now found a way to
600        make it do so. The string so far is captured, making this feature
601        compatible with Perl.
603    23. The tests have been re-organized, adding tests 11 and 12, to make it
604        possible to check the Perl 5.10 features against Perl 5.10.
606    24. Perl 5.10 allows subroutine calls in lookbehinds, as long as the subroutine
607        pattern matches a fixed length string. PCRE did not allow this; now it
608        does. Neither allows recursion.
610    25. I finally figured out how to implement a request to provide the minimum
611        length of subject string that was needed in order to match a given pattern.
612        (It was back references and recursion that I had previously got hung up
613        on.) This code has now been added to pcre_study(); it finds a lower bound
614        to the length of subject needed. It is not necessarily the greatest lower
615        bound, but using it to avoid searching strings that are too short does give
616        some useful speed-ups. The value is available to calling programs via
617        pcre_fullinfo().
619    26. While implementing 25, I discovered to my embarrassment that pcretest had
620        not been passing the result of pcre_study() to pcre_dfa_exec(), so the
621        study optimizations had never been tested with that matching function.
622        Oops. What is worse, even when it was passed study data, there was a bug in
623        pcre_dfa_exec() that meant it never actually used it. Double oops. There
624        were also very few tests of studied patterns with pcre_dfa_exec().
626    27. If (?| is used to create subpatterns with duplicate numbers, they are now
627        allowed to have the same name, even if PCRE_DUPNAMES is not set. However,
628        on the other side of the coin, they are no longer allowed to have different
629        names, because these cannot be distinguished in PCRE, and this has caused
630        confusion. (This is a difference from Perl.)
632    28. When duplicate subpattern names are present (necessarily with different
633        numbers, as required by 27 above), and a test is made by name in a
634        conditional pattern, either for a subpattern having been matched, or for
635        recursion in such a pattern, all the associated numbered subpatterns are
636        tested, and the overall condition is true if the condition is true for any
637        one of them. This is the way Perl works, and is also more like the way
638        testing by number works.
641    Version 7.9 11-Apr-09
642    ---------------------
644    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
645        (pcretest), all targets were linked against these libraries. This included
646        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
647        libraries. This caused unwanted dependencies to be created. This problem
648        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
649        pcretest is linked with readline.
651    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
652        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
653        moved outside it again, because FALSE and TRUE are already defined in AIX,
654        but BOOL is not.
656    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
657        PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
659    4.  The pcregrep documentation said spaces were inserted as well as colons (or
660        hyphens) following file names and line numbers when outputting matching
661        lines. This is not true; no spaces are inserted. I have also clarified the
662        wording for the --colour (or --color) option.
664    5.  In pcregrep, when --colour was used with -o, the list of matching strings
665        was not coloured; this is different to GNU grep, so I have changed it to be
666        the same.
668    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
669        each matching line was coloured. Now it goes on to look for further matches
670        of any of the test patterns, which is the same behaviour as GNU grep.
672    7.  A pattern that could match an empty string could cause pcregrep to loop; it
673        doesn't make sense to accept an empty string match in pcregrep, so I have
674        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
675        seems to be how GNU grep behaves.
677    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
678        start or after a newline", because the conditional assertion was not being
679        correctly handled. The rule now is that both the assertion and what follows
680        in the first alternative must satisfy the test.
682    9.  If auto-callout was enabled in a pattern with a conditional group whose
683        condition was an assertion, PCRE could crash during matching, both with
684        pcre_exec() and pcre_dfa_exec().
686    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
687        used for matching.
689    11. Unicode property support in character classes was not working for
690        characters (bytes) greater than 127 when not in UTF-8 mode.
692    12. Added the -M command line option to pcretest.
694    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
696    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
698    16. Added comments and documentation about mis-use of no_arg in the C++
699        wrapper.
701    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
702        from Martin Jerabek that uses macro names for all relevant character and
703        string constants.
705    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
706        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
707        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
708        these, but not everybody uses configure.
710    19. A conditional group that had only one branch was not being correctly
711        recognized as an item that could match an empty string. This meant that an
712        enclosing group might also not be so recognized, causing infinite looping
713        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
714        with the subject "ab", where knowledge that the repeated group can match
715        nothing is needed in order to break the loop.
717    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
718        exec(), but without supplying a callout function, matching went wrong.
720    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
721        leak if the size of the offset vector was greater than 30. When the vector
722        is smaller, the saved offsets during recursion go onto a local stack
723        vector, but for larger vectors malloc() is used. It was failing to free
724        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
725        error, in fact).
727    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
728        heapframe that is used only when UTF-8 support is enabled. This caused no
729        problem, but was untidy.
731    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
732        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
733        included within another project.
735    24. Steven Van Ingelgem's patches to add more options to the CMake support,
736        slightly modified by me:
738          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
739              not building pcregrep.
741          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
742              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
744    25. Forward references, both numeric and by name, in patterns that made use of
745        duplicate group numbers, could behave incorrectly or give incorrect errors,
746        because when scanning forward to find the reference group, PCRE was not
747        taking into account the duplicate group numbers. A pattern such as
748        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
750    26. Changed a few more instances of "const unsigned char *" to USPTR, making
751        the feature of a custom pointer more persuasive (as requested by a user).
753    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
754        pcretest.c, inside #ifndefs, because it seems they are sometimes already
755        pre-defined.
757    28. Added support for (*UTF8) at the start of a pattern.
759    29. Arrange for flags added by the "release type" setting in CMake to be shown
760        in the configuration summary.
763    Version 7.8 05-Sep-08
764    ---------------------
766    1.  Replaced UCP searching code with optimized version as implemented for Ad
767        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
768        stage table and inline lookup instead of a function, giving speed ups of 2
769        to 5 times on some simple patterns that I tested. Permission was given to
770        distribute the MultiStage2.py script that generates the tables (it's not in
771        the tarball, but is in the Subversion repository).
773    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
774        scripts.
776    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
777        a group with a zero qualifier. The result of the study could be incorrect,
778        or the function might crash, depending on the pattern.
780    4.  Caseless matching was not working for non-ASCII characters in back
781        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
782        It now works when Unicode Property Support is available.
784    5.  In pcretest, an escape such as \x{de} in the data was always generating
785        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
786        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
787        truncation.
789    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
791    7.  Added two (int) casts to pcregrep when printing the difference of two
792        pointers, in case they are 64-bit values.
794    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
795        test 2 if it fails.
797    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
798        and a #define of that name to empty if it is not externally set. This is to
799        allow users of MSVC to set it if necessary.
801    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
802        the convenience functions in the pcre_get.c source file.
804    11. An option change at the start of a pattern that had top-level alternatives
805        could cause overwriting and/or a crash. This command provoked a crash in
806        some environments:
808          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
810        This potential security problem was recorded as CVE-2008-2371.
812    12. For a pattern where the match had to start at the beginning or immediately
813        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
814        pcre_dfa_exec() could read past the end of the passed subject if there was
815        no match. To help with detecting such bugs (e.g. with valgrind), I modified
816        pcretest so that it places the subject at the end of its malloc-ed buffer.
818    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
819        exec() might read past the end of the data buffer in UTF-8 mode.
821    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
822        the data contained the byte 0x85 as part of a UTF-8 character within its
823        first line. This applied both to normal and DFA matching.
825    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
826        /^[^d]*?$/8 failed to match "abc".
828    16. Added a missing copyright notice to pcrecpp_internal.h.
830    17. Make it more clear in the documentation that values returned from
831        pcre_exec() in ovector are byte offsets, not character counts.
833    18. Tidied a few places to stop certain compilers from issuing warnings.
835    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
836        supplied by Stefan Weber. I made a further small update for 7.8 because
837        there is a change of source arrangements: the pcre_searchfuncs.c module is
838        replaced by pcre_ucd.c.
841    Version 7.7 07-May-08
842    ---------------------
844    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
845        a string to a long long, pretend we don't even have a long long." This is
846        done by checking for the strtoq, strtoll, and _strtoi64 functions.
848    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
849        pre-7.6 versions, which defined a global no_arg variable instead of putting
850        it in the RE class. (See also #8 below.)
852    3.  Remove a line of dead code, identified by coverity and reported by Nuno
853        Lopes.
855    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
857        (1) The include/exclude patterns were being applied to the whole pathnames
858            of files, instead of just to the final components.
860        (2) If there was more than one level of directory, the subdirectories were
861            skipped unless they satisfied the include/exclude conditions. This is
862            inconsistent with GNU grep (and could even be seen as contrary to the
863            pcregrep specification - which I improved to make it absolutely clear).
864            The action now is always to scan all levels of directory, and just
865            apply the include/exclude patterns to regular files.
867    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
868        --exclude_dir in the tests to avoid scanning .svn directories.
870    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
871        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
872        doesn't support NULs in patterns.
874    7.  Added some missing "const"s to declarations of static tables in
875        pcre_compile.c and pcre_dfa_exec.c.
877    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
878        caused by fix #2  above. (Subsequently also a second patch to fix the
879        first patch. And a third patch - this was a messy problem.)
881    9.  Applied Craig's patch to remove the use of push_back().
883    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
884        matching function regexec().
886    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
887        which, however, unlike Perl's \g{...}, are subroutine calls, not back
888        references. PCRE supports relative numbers with this syntax (I don't think
889        Oniguruma does).
891    12. Previously, a group with a zero repeat such as (...){0} was completely
892        omitted from the compiled regex. However, this means that if the group
893        was called as a subroutine from elsewhere in the pattern, things went wrong
894        (an internal error was given). Such groups are now left in the compiled
895        pattern, with a new opcode that causes them to be skipped at execution
896        time.
898    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
899        to the way PCRE behaves:
901        (a) A lone ] character is dis-allowed (Perl treats it as data).
903        (b) A back reference to an unmatched subpattern matches an empty string
904            (Perl fails the current match path).
906        (c) A data ] in a character class must be notated as \] because if the
907            first data character in a class is ], it defines an empty class. (In
908            Perl it is not possible to have an empty class.) The empty class []
909            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
910            The negative empty class [^] matches any one character, independently
911            of the DOTALL setting.
913    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
914        non-existent subpattern following a character class starting with ']' and
915        containing () gave an internal compiling error instead of "reference to
916        non-existent subpattern". Fortunately, when the pattern did exist, the
917        compiled code was correct. (When scanning forwards to check for the
918        existencd of the subpattern, it was treating the data ']' as terminating
919        the class, so got the count wrong. When actually compiling, the reference
920        was subsequently set up correctly.)
922    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
923        it was being rejected as not supported by pcre_dfa_exec(), even though
924        other assertions are supported. I have made pcre_dfa_exec() support
925        (*FAIL).
927    16. The implementation of 13c above involved the invention of a new opcode,
928        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
929        cannot be changed at match time, I realized I could make a small
930        improvement to matching performance by compiling OP_ALLANY instead of
931        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
932        on the OP_ANY path.
934    17. Compiling pcretest on Windows with readline support failed without the
935        following two fixes: (1) Make the unistd.h include conditional on
936        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
938    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
939        ncurses library to be included for pcretest when ReadLine support is
940        requested, but also to allow for it to be overridden. This patch came from
941        Daniel Bergström.
943    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
944        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
945        any errors with the current Unicode tables. Thanks to Peter Kankowski for
946        spotting this.
949    Version 7.6 28-Jan-08
950    ---------------------
952    1.  A character class containing a very large number of characters with
953        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
954        overflow.
956    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
957        HAVE_LONG_LONG is not defined.
959    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
960        bring them up to date and include new features. This patch includes:
962        - Fixed PH's badly added libz and libbz2 support.
963        - Fixed a problem with static linking.
964        - Added pcredemo. [But later removed - see 7 below.]
965        - Fixed dftables problem and added an option.
966        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
967            HAVE_LONG_LONG.
968        - Added readline support for pcretest.
969        - Added an listing of the option settings after cmake has run.
971    4.  A user submitted a patch to Makefile that makes it easy to create
972        "pcre.dll" under mingw when using Configure/Make. I added stuff to
973        Makefile.am that cause it to include this special target, without
974        affecting anything else. Note that the same mingw target plus all
975        the other distribution libraries and programs are now supported
976        when configuring with CMake (see 6 below) instead of with
977        Configure/Make.
979    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
980        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
981        exported in the Windows port". It has not yet been confirmed that the patch
982        solves the problem, but it does no harm.
984    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
985        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
986        with CMake, and also correct the comment about stack recursion.
988    7.  Remove the automatic building of pcredemo from the ./configure system and
989        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
990        of a program that users should build themselves after PCRE is installed, so
991        building it automatically is not really right. What is more, it gave
992        trouble in some build environments.
994    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
997    Version 7.5 10-Jan-08
998    ---------------------
1000    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
1001        values in parens when parsing an RE using the C++ wrapper."
1003    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
1004        Characters greater than 255 were excluded from the class instead of being
1005        included.
1007    3.  The same bug as (2) above applied to negated POSIX classes such as
1008        [:^space:].
1010    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
1011        defined or documented. It seems to have been a typo for PCRE_STATIC, so
1012        I have changed it.
1014    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
1015        first named subpattern) and a construct such as (?&a) would reference the
1016        first named subpattern whose name started with "a" (in other words, the
1017        length check was missing). Both these problems are fixed. "Subpattern name
1018        expected" is now given for (?&) (a zero-length name), and this patch also
1019        makes it give the same error for \k'' (previously it complained that that
1020        was a reference to a non-existent subpattern).
1022    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
1023        this is right because (?- can be followed by option settings as well as by
1024        digits. I have, however, made the messages clearer.
1026    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
1027        than the number used in the conditional) now cause a compile-time error.
1028        This is actually not compatible with Perl, which accepts such patterns, but
1029        treats the conditional as always being FALSE (as PCRE used to), but it
1030        seems to me that giving a diagnostic is better.
1032    8.  Change "alphameric" to the more common word "alphanumeric" in comments
1033        and messages.
1035    9.  Fix two occurrences of "backslash" in comments that should have been
1036        "backspace".
1038    10. Remove two redundant lines of code that can never be obeyed (their function
1039        was moved elsewhere).
1041    11. The program that makes PCRE's Unicode character property table had a bug
1042        which caused it to generate incorrect table entries for sequences of
1043        characters that have the same character type, but are in different scripts.
1044        It amalgamated them into a single range, with the script of the first of
1045        them. In other words, some characters were in the wrong script. There were
1046        thirteen such cases, affecting characters in the following ranges:
1048          U+002b0 - U+002c1
1049          U+0060c - U+0060d
1050          U+0061e - U+00612
1051          U+0064b - U+0065e
1052          U+0074d - U+0076d
1053          U+01800 - U+01805
1054          U+01d00 - U+01d77
1055          U+01d9b - U+01dbf
1056          U+0200b - U+0200f
1057          U+030fc - U+030fe
1058          U+03260 - U+0327f
1059          U+0fb46 - U+0fbb1
1060          U+10450 - U+1049d
1062    12. The -o option (show only the matching part of a line) for pcregrep was not
1063        compatible with GNU grep in that, if there was more than one match in a
1064        line, it showed only the first of them. It now behaves in the same way as
1065        GNU grep.
1067    13. If the -o and -v options were combined for pcregrep, it printed a blank
1068        line for every non-matching line. GNU grep prints nothing, and pcregrep now
1069        does the same. The return code can be used to tell if there were any
1070        non-matching lines.
1072    14. Added --file-offsets and --line-offsets to pcregrep.
1074    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
1075        infinitely looping recursion. The bug was that positive lookaheads were not
1076        being skipped when checking for a possible empty match (negative lookaheads
1077        and both kinds of lookbehind were skipped).
1079    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
1080        inclusion of <windows.h> to before rather than after the definition of
1081        INVALID_FILE_ATTRIBUTES (patch from David Byron).
1083    17. Specifying a possessive quantifier with a specific limit for a Unicode
1084        character property caused pcre_compile() to compile bad code, which led at
1085        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
1086        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
1087        caused the error; without that there was no problem.
1089    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
1091    19. Added --enable-pcretest-libreadline.
1093    20. In pcrecpp.cc, the variable 'count' was incremented twice in
1094        RE::GlobalReplace(). As a result, the number of replacements returned was
1095        double what it should be. I removed one of the increments, but Craig sent a
1096        later patch that removed the other one (the right fix) and added unit tests
1097        that check the return values (which was not done before).
1099    21. Several CMake things:
1101        (1) Arranged that, when cmake is used on Unix, the libraries end up with
1102            the names libpcre and libpcreposix, not just pcre and pcreposix.
1104        (2) The above change means that pcretest and pcregrep are now correctly
1105            linked with the newly-built libraries, not previously installed ones.
1109    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
1110        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
1111        UTF-8 newline character). The key issue is that the pattern starts .*;
1112        this means that the match must be either at the beginning, or after a
1113        newline. The bug was in the code for advancing after a failed match and
1114        checking that the new position followed a newline. It was not taking
1115        account of UTF-8 characters correctly.
1117    23. PCRE was behaving differently from Perl in the way it recognized POSIX
1118        character classes. PCRE was not treating the sequence [:...:] as a
1119        character class unless the ... were all letters. Perl, however, seems to
1120        allow any characters between [: and :], though of course it rejects as
1121        unknown any "names" that contain non-letters, because all the known class
1122        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
1123        for example, whereas PCRE did not - it did not recognize a POSIX character
1124        class. This seemed a bit dangerous, so the code has been changed to be
1125        closer to Perl. The behaviour is not identical to Perl, because PCRE will
1126        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
1127        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
1128        Perl does, and where it didn't before.
1130    24. Rewrite so as to remove the single use of %n from pcregrep because in some
1131        Windows environments %n is disabled by default.
1134    Version 7.4 21-Sep-07
1135    ---------------------
1137    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
1138        means that a class such as [\s] counted as "explicit reference to CR or
1139        LF". That isn't really right - the whole point of the change was to try to
1140        help when there was an actual mention of one of the two characters. So now
1141        the change happens only if \r or \n (or a literal CR or LF) character is
1142        encountered.
1144    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
1145        of both had grown to the point where there were only 3 bits left.
1146        Fortunately, there was spare space in the data structure, and so I have
1147        moved the internal flags into a new 16-bit field to free up more option
1148        bits.
1150    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
1151        but did not set the internal JCHANGED flag - either of these is enough to
1152        control the way the "get" function works - but the PCRE_INFO_JCHANGED
1153        facility is supposed to tell if (?J) was ever used, so now (?J) at the
1154        start sets both bits.
1156    4.  Added options (at build time, compile time, exec time) to change \R from
1157        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
1159    5.  doc/pcresyntax.html was missing from the distribution.
1161    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
1162        compatibility, even though it is no longer used.
1164    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
1165        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
1166        windows.h file is present (where different names are used). [This was
1167        reversed later after testing - see 16 below.]
1169    8.  Changed all #include <config.h> to #include "config.h". There were also
1170        some further <pcre.h> cases that I changed to "pcre.h".
1172    9.  When pcregrep was used with the --colour option, it missed the line ending
1173        sequence off the lines that it output.
1175    10. It was pointed out to me that arrays of string pointers cause lots of
1176        relocations when a shared library is dynamically loaded. A technique of
1177        using a single long string with a table of offsets can drastically reduce
1178        these. I have refactored PCRE in four places to do this. The result is
1179        dramatic:
1181          Originally:                          290
1182          After changing UCP table:            187
1183          After changing error message table:   43
1184          After changing table of "verbs"       36
1185          After changing table of Posix names   22
1187        Thanks to the folks working on Gregex for glib for this insight.
1189    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
1190        unicode-properties was also set.
1192    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
1194    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
1195        checked only for CRLF.
1197    14. Added casts to pcretest.c to avoid compiler warnings.
1199    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
1201    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
1202        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
1203        entirely. This removes changes made in 7 above.
1205    17. The CMake files have been updated, and there is now more information about
1206        building with CMake in the NON-UNIX-USE document.
1209    Version 7.3 28-Aug-07
1210  ---------------------  ---------------------
1212   1. In the rejigging of the build system that eventually resulted in 7.1, the   1. In the rejigging of the build system that eventually resulted in 7.1, the
# Line 145  Version 7.3 20-Aug-07 Line 1350  Version 7.3 20-Aug-07
1351  25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.  25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
1353  26. Patterns such as [\P{Yi}A] which include \p or \P and just one other  26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
1354      character were causing crashes (broken optimization).      character were causing crashes (broken optimization).
1356    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
1357        \p or \P) caused a compile-time loop.
1359    28. More problems have arisen in unanchored patterns when CRLF is a valid line
1360        break. For example, the unstudied pattern [\r\n]A does not match the string
1361        "\r\nA" because change 7.0/46 below moves the current point on by two
1362        characters after failing to match at the start. However, the pattern \nA
1363        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
1364        the same is true. There doesn't seem any very clean way out of this, but
1365        what I have chosen to do makes the common cases work: PCRE now takes note
1366        of whether there can be an explicit match for \r or \n anywhere in the
1367        pattern, and if so, 7.0/46 no longer applies. As part of this change,
1368        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
1369        pattern has explicit CR or LF references.
1371    29. Added (*CR) etc for changing newline setting at start of pattern.
1374  Version 7.2 19-Jun-07  Version 7.2 19-Jun-07
1375  ---------------------  ---------------------

Removed from v.223  
changed lines
  Added in v.595

  ViewVC Help
Powered by ViewVC 1.1.5