ViewVC logotype

Diff of /code/trunk/ChangeLog

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

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

Removed from v.175  
changed lines
  Added in v.598

  ViewVC Help
Powered by ViewVC 1.1.5