ViewVC logotype

Diff of /code/trunk/ChangeLog

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

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

Removed from v.200  
changed lines
  Added in v.600

  ViewVC Help
Powered by ViewVC 1.1.5