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

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

  ViewVC Help
Powered by ViewVC 1.1.5