ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 85 by nigel, Sat Feb 24 21:41:13 2007 UTC revision 564 by ph10, Sun Oct 31 16:07:24 2010 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4    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.
68    Version 8.10 25-Jun-2010
69    ------------------------
71    1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and
72        THEN.
74    2.  (*ACCEPT) was not working when inside an atomic group.
76    3.  Inside a character class, \B is treated as a literal by default, but
77        faulted if PCRE_EXTRA is set. This mimics Perl's behaviour (the -w option
78        causes the error). The code is unchanged, but I tidied the documentation.
80    4.  Inside a character class, PCRE always treated \R and \X as literals,
81        whereas Perl faults them if its -w option is set. I have changed PCRE so
82        that it faults them when PCRE_EXTRA is set.
84    5.  Added support for \N, which always matches any character other than
85        newline. (It is the same as "." when PCRE_DOTALL is not set.)
87    6.  When compiling pcregrep with newer versions of gcc which may have
88        FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',
89        declared with attribute warn_unused_result" were given. Just casting the
90        result to (void) does not stop the warnings; a more elaborate fudge is
91        needed. I've used a macro to implement this.
93    7.  Minor change to pcretest.c to avoid a compiler warning.
95    8.  Added four artifical Unicode properties to help with an option to make
96        \s etc use properties (see next item). The new properties are: Xan
97        (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).
99    9.  Added PCRE_UCP to make \b, \d, \s, \w, and certain POSIX character classes
100        use Unicode properties. (*UCP) at the start of a pattern can be used to set
101        this option. Modified pcretest to add /W to test this facility. Added
102        REG_UCP to make it available via the POSIX interface.
104    10. Added --line-buffered to pcregrep.
106    11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was
107        studied, and the match started with a letter with a code point greater than
108        127 whose first byte was different to the first byte of the other case of
109        the letter, the other case of this starting letter was not recognized
110        (#976).
112    12. If a pattern that was studied started with a repeated Unicode property
113        test, for example, \p{Nd}+, there was the theoretical possibility of
114        setting up an incorrect bitmap of starting bytes, but fortunately it could
115        not have actually happened in practice until change 8 above was made (it
116        added property types that matched character-matching opcodes).
118    13. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
119        possible starting bytes for non-anchored patterns.
121    14. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes
122        \R, and also a number of cases that involve Unicode properties, both
123        explicit and implicit when PCRE_UCP is set.
125    15. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8
126        input, it could crash or give wrong results if characters with values
127        greater than 0xc0 were present in the subject string. (Detail: it assumed
128        UTF-8 input when processing these items.)
130    16. Added a lot of (int) casts to avoid compiler warnings in systems where
131        size_t is 64-bit (#991).
133    17. Added a check for running out of memory when PCRE is compiled with
134        --disable-stack-for-recursion (#990).
136    18. If the last data line in a file for pcretest does not have a newline on
137        the end, a newline was missing in the output.
139    19. The default pcre_chartables.c file recognizes only ASCII characters (values
140        less than 128) in its various bitmaps. However, there is a facility for
141        generating tables according to the current locale when PCRE is compiled. It
142        turns out that in some environments, 0x85 and 0xa0, which are Unicode space
143        characters, are recognized by isspace() and therefore were getting set in
144        these tables, and indeed these tables seem to approximate to ISO 8859. This
145        caused a problem in UTF-8 mode when pcre_study() was used to create a list
146        of bytes that can start a match. For \s, it was including 0x85 and 0xa0,
147        which of course cannot start UTF-8 characters. I have changed the code so
148        that only real ASCII characters (less than 128) and the correct starting
149        bytes for UTF-8 encodings are set for characters greater than 127 when in
150        UTF-8 mode. (When PCRE_UCP is set - see 9 above - the code is different
151        altogether.)
153    20. Added the /T option to pcretest so as to be able to run tests with non-
154        standard character tables, thus making it possible to include the tests
155        used for 19 above in the standard set of tests.
157    21. A pattern such as (?&t)(?#()(?(DEFINE)(?<t>a)) which has a forward
158        reference to a subpattern the other side of a comment that contains an
159        opening parenthesis caused either an internal compiling error, or a
160        reference to the wrong subpattern.
163    Version 8.02 19-Mar-2010
164    ------------------------
166    1.  The Unicode data tables have been updated to Unicode 5.2.0.
168    2.  Added the option --libs-cpp to pcre-config, but only when C++ support is
169        configured.
171    3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the
172        original author of that file, following a query about its status.
174    4.  On systems that do not have stdint.h (e.g. Solaris), check for and include
175        inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
177    5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
178        quantifier applied to a forward-referencing subroutine call, could compile
179        incorrect code or give the error "internal error: previously-checked
180        referenced subpattern not found".
182    6.  Both MS Visual Studio and Symbian OS have problems with initializing
183        variables to point to external functions. For these systems, therefore,
184        pcre_malloc etc. are now initialized to local functions that call the
185        relevant global functions.
187    7.  There were two entries missing in the vectors called coptable and poptable
188        in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.
189        I've fixed the data, and added a kludgy way of testing at compile time that
190        the lengths are correct (equal to the number of opcodes).
192    8.  Following on from 7, I added a similar kludge to check the length of the
193        eint vector in pcreposix.c.
195    9.  Error texts for pcre_compile() are held as one long string to avoid too
196        much relocation at load time. To find a text, the string is searched,
197        counting zeros. There was no check for running off the end of the string,
198        which could happen if a new error number was added without updating the
199        string.
201    10. \K gave a compile-time error if it appeared in a lookbehind assersion.
203    11. \K was not working if it appeared in an atomic group or in a group that
204        was called as a "subroutine", or in an assertion. Perl 5.11 documents that
205        \K is "not well defined" if used in an assertion. PCRE now accepts it if
206        the assertion is positive, but not if it is negative.
208    12. Change 11 fortuitously reduced the size of the stack frame used in the
209        "match()" function of pcre_exec.c by one pointer. Forthcoming
210        implementation of support for (*MARK) will need an extra pointer on the
211        stack; I have reserved it now, so that the stack frame size does not
212        decrease.
214    13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other
215        item in branch that calls a recursion is a subroutine call - as in the
216        second branch in the above example - was incorrectly given the compile-
217        time error "recursive call could loop indefinitely" because pcre_compile()
218        was not correctly checking the subroutine for matching a non-empty string.
220    14. The checks for overrunning compiling workspace could trigger after an
221        overrun had occurred. This is a "should never occur" error, but it can be
222        triggered by pathological patterns such as hundreds of nested parentheses.
223        The checks now trigger 100 bytes before the end of the workspace.
225    15. Fix typo in configure.ac: "srtoq" should be "strtoq".
228    Version 8.01 19-Jan-2010
229    ------------------------
231    1.  If a pattern contained a conditional subpattern with only one branch (in
232        particular, this includes all (*DEFINE) patterns), a call to pcre_study()
233        computed the wrong minimum data length (which is of course zero for such
234        subpatterns). This could cause incorrect "no match" results.
236    2.  For patterns such as (?i)a(?-i)b|c where an option setting at the start of
237        the pattern is reset in the first branch, pcre_compile() failed with
238        "internal error: code overflow at offset...". This happened only when
239        the reset was to the original external option setting. (An optimization
240        abstracts leading options settings into an external setting, which was the
241        cause of this.)
243    3.  A pattern such as ^(?!a(*SKIP)b) where a negative assertion contained one
244        of the verbs SKIP, PRUNE, or COMMIT, did not work correctly. When the
245        assertion pattern did not match (meaning that the assertion was true), it
246        was incorrectly treated as false if the SKIP had been reached during the
247        matching. This also applied to assertions used as conditions.
249    4.  If an item that is not supported by pcre_dfa_exec() was encountered in an
250        assertion subpattern, including such a pattern used as a condition,
251        unpredictable results occurred, instead of the error return
254    5.  The C++ GlobalReplace function was not working like Perl for the special
255        situation when an empty string is matched. It now does the fancy magic
256        stuff that is necessary.
258    6.  In pcre_internal.h, obsolete includes to setjmp.h and stdarg.h have been
259        removed. (These were left over from very, very early versions of PCRE.)
261    7.  Some cosmetic changes to the code to make life easier when compiling it
262        as part of something else:
264        (a) Change DEBUG to PCRE_DEBUG.
266        (b) In pcre_compile(), rename the member of the "branch_chain" structure
267            called "current" as "current_branch", to prevent a collision with the
268            Linux macro when compiled as a kernel module.
270        (c) In pcre_study(), rename the function set_bit() as set_table_bit(), to
271            prevent a collision with the Linux macro when compiled as a kernel
272            module.
274    8.  In pcre_compile() there are some checks for integer overflows that used to
275        cast potentially large values to (double). This has been changed to that
276        when building, a check for int64_t is made, and if it is found, it is used
277        instead, thus avoiding the use of floating point arithmetic. (There is no
278        other use of FP in PCRE.) If int64_t is not found, the fallback is to
279        double.
281    9.  Added two casts to avoid signed/unsigned warnings from VS Studio Express
282        2005 (difference between two addresses compared to an unsigned value).
284    10. Change the standard AC_CHECK_LIB test for libbz2 in configure.ac to a
285        custom one, because of the following reported problem in Windows:
287          - libbz2 uses the Pascal calling convention (WINAPI) for the functions
288              under Win32.
289          - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",
290              therefore missing the function definition.
291          - The compiler thus generates a "C" signature for the test function.
292          - The linker fails to find the "C" function.
293          - PCRE fails to configure if asked to do so against libbz2.
295    11. When running libtoolize from libtool-2.2.6b as part of autogen.sh, these
296        messages were output:
298          Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
299          rerunning libtoolize, to keep the correct libtool macros in-tree.
300          Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
302        I have done both of these things.
304    12. Although pcre_dfa_exec() does not use nearly as much stack as pcre_exec()
305        most of the time, it *can* run out if it is given a pattern that contains a
306        runaway infinite recursion. I updated the discussion in the pcrestack man
307        page.
309    13. Now that we have gone to the x.xx style of version numbers, the minor
310        version may start with zero. Using 08 or 09 is a bad idea because users
311        might check the value of PCRE_MINOR in their code, and 08 or 09 may be
312        interpreted as invalid octal numbers. I've updated the previous comment in
313        configure.ac, and also added a check that gives an error if 08 or 09 are
314        used.
316    14. Change 8.00/11 was not quite complete: code had been accidentally omitted,
317        causing partial matching to fail when the end of the subject matched \W
318        in a UTF-8 pattern where \W was quantified with a minimum of 3.
320    15. There were some discrepancies between the declarations in pcre_internal.h
321        of _pcre_is_newline(), _pcre_was_newline(), and _pcre_valid_utf8() and
322        their definitions. The declarations used "const uschar *" and the
323        definitions used USPTR. Even though USPTR is normally defined as "const
324        unsigned char *" (and uschar is typedeffed as "unsigned char"), it was
325        reported that: "This difference in casting confuses some C++ compilers, for
326        example, SunCC recognizes above declarations as different functions and
327        generates broken code for hbpcre." I have changed the declarations to use
328        USPTR.
330    16. GNU libtool is named differently on some systems. The autogen.sh script now
331        tries several variants such as glibtoolize (MacOSX) and libtoolize1x
332        (FreeBSD).
334    17. Applied Craig's patch that fixes an HP aCC compile error in pcre 8.00
335        (strtoXX undefined when compiling pcrecpp.cc). The patch contains this
336        comment: "Figure out how to create a longlong from a string: strtoll and
337        equivalent. It's not enough to call AC_CHECK_FUNCS: hpux has a strtoll, for
338        instance, but it only takes 2 args instead of 3!"
340    18. A subtle bug concerned with back references has been fixed by a change of
341        specification, with a corresponding code fix. A pattern such as
342        ^(xa|=?\1a)+$ which contains a back reference inside the group to which it
343        refers, was giving matches when it shouldn't. For example, xa=xaaa would
344        match that pattern. Interestingly, Perl (at least up to 5.11.3) has the
345        same bug. Such groups have to be quantified to be useful, or contained
346        inside another quantified group. (If there's no repetition, the reference
347        can never match.) The problem arises because, having left the group and
348        moved on to the rest of the pattern, a later failure that backtracks into
349        the group uses the captured value from the final iteration of the group
350        rather than the correct earlier one. I have fixed this in PCRE by forcing
351        any group that contains a reference to itself to be an atomic group; that
352        is, there cannot be any backtracking into it once it has completed. This is
353        similar to recursive and subroutine calls.
356    Version 8.00 19-Oct-09
357    ----------------------
359    1.  The table for translating pcre_compile() error codes into POSIX error codes
360        was out-of-date, and there was no check on the pcre_compile() error code
361        being within the table. This could lead to an OK return being given in
362        error.
364    2.  Changed the call to open a subject file in pcregrep from fopen(pathname,
365        "r") to fopen(pathname, "rb"), which fixed a problem with some of the tests
366        in a Windows environment.
368    3.  The pcregrep --count option prints the count for each file even when it is
369        zero, as does GNU grep. However, pcregrep was also printing all files when
370        --files-with-matches was added. Now, when both options are given, it prints
371        counts only for those files that have at least one match. (GNU grep just
372        prints the file name in this circumstance, but including the count seems
373        more useful - otherwise, why use --count?) Also ensured that the
374        combination -clh just lists non-zero counts, with no names.
376    4.  The long form of the pcregrep -F option was incorrectly implemented as
377        --fixed_strings instead of --fixed-strings. This is an incompatible change,
378        but it seems right to fix it, and I didn't think it was worth preserving
379        the old behaviour.
381    5.  The command line items --regex=pattern and --regexp=pattern were not
382        recognized by pcregrep, which required --regex pattern or --regexp pattern
383        (with a space rather than an '='). The man page documented the '=' forms,
384        which are compatible with GNU grep; these now work.
386    6.  No libpcreposix.pc file was created for pkg-config; there was just
387        libpcre.pc and libpcrecpp.pc. The omission has been rectified.
389    7.  Added #ifndef SUPPORT_UCP into the pcre_ucd.c module, to reduce its size
390        when UCP support is not needed, by modifying the Python script that
391        generates it from Unicode data files. This should not matter if the module
392        is correctly used as a library, but I received one complaint about 50K of
393        unwanted data. My guess is that the person linked everything into his
394        program rather than using a library. Anyway, it does no harm.
396    8.  A pattern such as /\x{123}{2,2}+/8 was incorrectly compiled; the trigger
397        was a minimum greater than 1 for a wide character in a possessive
398        repetition. The same bug could also affect patterns like /(\x{ff}{0,2})*/8
399        which had an unlimited repeat of a nested, fixed maximum repeat of a wide
400        character. Chaos in the form of incorrect output or a compiling loop could
401        result.
403    9.  The restrictions on what a pattern can contain when partial matching is
404        requested for pcre_exec() have been removed. All patterns can now be
405        partially matched by this function. In addition, if there are at least two
406        slots in the offset vector, the offset of the earliest inspected character
407        for the match and the offset of the end of the subject are set in them when
408        PCRE_ERROR_PARTIAL is returned.
410    10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is
411        synonymous with PCRE_PARTIAL, for backwards compatibility, and
412        PCRE_PARTIAL_HARD, which causes a partial match to supersede a full match,
413        and may be more useful for multi-segment matching.
415    11. Partial matching with pcre_exec() is now more intuitive. A partial match
416        used to be given if ever the end of the subject was reached; now it is
417        given only if matching could not proceed because another character was
418        needed. This makes a difference in some odd cases such as Z(*FAIL) with the
419        string "Z", which now yields "no match" instead of "partial match". In the
420        case of pcre_dfa_exec(), "no match" is given if every matching path for the
421        final character ended with (*FAIL).
423    12. Restarting a match using pcre_dfa_exec() after a partial match did not work
424        if the pattern had a "must contain" character that was already found in the
425        earlier partial match, unless partial matching was again requested. For
426        example, with the pattern /dog.(body)?/, the "must contain" character is
427        "g". If the first part-match was for the string "dog", restarting with
428        "sbody" failed. This bug has been fixed.
430    13. The string returned by pcre_dfa_exec() after a partial match has been
431        changed so that it starts at the first inspected character rather than the
432        first character of the match. This makes a difference only if the pattern
433        starts with a lookbehind assertion or \b or \B (\K is not supported by
434        pcre_dfa_exec()). It's an incompatible change, but it makes the two
435        matching functions compatible, and I think it's the right thing to do.
437    14. Added a pcredemo man page, created automatically from the pcredemo.c file,
438        so that the demonstration program is easily available in environments where
439        PCRE has not been installed from source.
441    15. Arranged to add -DPCRE_STATIC to cflags in libpcre.pc, libpcreposix.cp,
442        libpcrecpp.pc and pcre-config when PCRE is not compiled as a shared
443        library.
445    16. Added REG_UNGREEDY to the pcreposix interface, at the request of a user.
446        It maps to PCRE_UNGREEDY. It is not, of course, POSIX-compatible, but it
447        is not the first non-POSIX option to be added. Clearly some people find
448        these options useful.
450    17. If a caller to the POSIX matching function regexec() passes a non-zero
451        value for nmatch with a NULL value for pmatch, the value of
452        nmatch is forced to zero.
454    18. RunGrepTest did not have a test for the availability of the -u option of
455        the diff command, as RunTest does. It now checks in the same way as
456        RunTest, and also checks for the -b option.
458    19. If an odd number of negated classes containing just a single character
459        interposed, within parentheses, between a forward reference to a named
460        subpattern and the definition of the subpattern, compilation crashed with
461        an internal error, complaining that it could not find the referenced
462        subpattern. An example of a crashing pattern is /(?&A)(([^m])(?<A>))/.
463        [The bug was that it was starting one character too far in when skipping
464        over the character class, thus treating the ] as data rather than
465        terminating the class. This meant it could skip too much.]
467    20. Added PCRE_NOTEMPTY_ATSTART in order to be able to correctly implement the
468        /g option in pcretest when the pattern contains \K, which makes it possible
469        to have an empty string match not at the start, even when the pattern is
470        anchored. Updated pcretest and pcredemo to use this option.
472    21. If the maximum number of capturing subpatterns in a recursion was greater
473        than the maximum at the outer level, the higher number was returned, but
474        with unset values at the outer level. The correct (outer level) value is
475        now given.
477    22. If (*ACCEPT) appeared inside capturing parentheses, previous releases of
478        PCRE did not set those parentheses (unlike Perl). I have now found a way to
479        make it do so. The string so far is captured, making this feature
480        compatible with Perl.
482    23. The tests have been re-organized, adding tests 11 and 12, to make it
483        possible to check the Perl 5.10 features against Perl 5.10.
485    24. Perl 5.10 allows subroutine calls in lookbehinds, as long as the subroutine
486        pattern matches a fixed length string. PCRE did not allow this; now it
487        does. Neither allows recursion.
489    25. I finally figured out how to implement a request to provide the minimum
490        length of subject string that was needed in order to match a given pattern.
491        (It was back references and recursion that I had previously got hung up
492        on.) This code has now been added to pcre_study(); it finds a lower bound
493        to the length of subject needed. It is not necessarily the greatest lower
494        bound, but using it to avoid searching strings that are too short does give
495        some useful speed-ups. The value is available to calling programs via
496        pcre_fullinfo().
498    26. While implementing 25, I discovered to my embarrassment that pcretest had
499        not been passing the result of pcre_study() to pcre_dfa_exec(), so the
500        study optimizations had never been tested with that matching function.
501        Oops. What is worse, even when it was passed study data, there was a bug in
502        pcre_dfa_exec() that meant it never actually used it. Double oops. There
503        were also very few tests of studied patterns with pcre_dfa_exec().
505    27. If (?| is used to create subpatterns with duplicate numbers, they are now
506        allowed to have the same name, even if PCRE_DUPNAMES is not set. However,
507        on the other side of the coin, they are no longer allowed to have different
508        names, because these cannot be distinguished in PCRE, and this has caused
509        confusion. (This is a difference from Perl.)
511    28. When duplicate subpattern names are present (necessarily with different
512        numbers, as required by 27 above), and a test is made by name in a
513        conditional pattern, either for a subpattern having been matched, or for
514        recursion in such a pattern, all the associated numbered subpatterns are
515        tested, and the overall condition is true if the condition is true for any
516        one of them. This is the way Perl works, and is also more like the way
517        testing by number works.
520    Version 7.9 11-Apr-09
521    ---------------------
523    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
524        (pcretest), all targets were linked against these libraries. This included
525        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
526        libraries. This caused unwanted dependencies to be created. This problem
527        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
528        pcretest is linked with readline.
530    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
531        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
532        moved outside it again, because FALSE and TRUE are already defined in AIX,
533        but BOOL is not.
535    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
536        PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
538    4.  The pcregrep documentation said spaces were inserted as well as colons (or
539        hyphens) following file names and line numbers when outputting matching
540        lines. This is not true; no spaces are inserted. I have also clarified the
541        wording for the --colour (or --color) option.
543    5.  In pcregrep, when --colour was used with -o, the list of matching strings
544        was not coloured; this is different to GNU grep, so I have changed it to be
545        the same.
547    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
548        each matching line was coloured. Now it goes on to look for further matches
549        of any of the test patterns, which is the same behaviour as GNU grep.
551    7.  A pattern that could match an empty string could cause pcregrep to loop; it
552        doesn't make sense to accept an empty string match in pcregrep, so I have
553        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
554        seems to be how GNU grep behaves.
556    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
557        start or after a newline", because the conditional assertion was not being
558        correctly handled. The rule now is that both the assertion and what follows
559        in the first alternative must satisfy the test.
561    9.  If auto-callout was enabled in a pattern with a conditional group whose
562        condition was an assertion, PCRE could crash during matching, both with
563        pcre_exec() and pcre_dfa_exec().
565    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
566        used for matching.
568    11. Unicode property support in character classes was not working for
569        characters (bytes) greater than 127 when not in UTF-8 mode.
571    12. Added the -M command line option to pcretest.
573    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
575    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
577    16. Added comments and documentation about mis-use of no_arg in the C++
578        wrapper.
580    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
581        from Martin Jerabek that uses macro names for all relevant character and
582        string constants.
584    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
585        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
586        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
587        these, but not everybody uses configure.
589    19. A conditional group that had only one branch was not being correctly
590        recognized as an item that could match an empty string. This meant that an
591        enclosing group might also not be so recognized, causing infinite looping
592        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
593        with the subject "ab", where knowledge that the repeated group can match
594        nothing is needed in order to break the loop.
596    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
597        exec(), but without supplying a callout function, matching went wrong.
599    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
600        leak if the size of the offset vector was greater than 30. When the vector
601        is smaller, the saved offsets during recursion go onto a local stack
602        vector, but for larger vectors malloc() is used. It was failing to free
603        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
604        error, in fact).
606    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
607        heapframe that is used only when UTF-8 support is enabled. This caused no
608        problem, but was untidy.
610    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
611        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
612        included within another project.
614    24. Steven Van Ingelgem's patches to add more options to the CMake support,
615        slightly modified by me:
617          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
618              not building pcregrep.
620          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
621              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
623    25. Forward references, both numeric and by name, in patterns that made use of
624        duplicate group numbers, could behave incorrectly or give incorrect errors,
625        because when scanning forward to find the reference group, PCRE was not
626        taking into account the duplicate group numbers. A pattern such as
627        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
629    26. Changed a few more instances of "const unsigned char *" to USPTR, making
630        the feature of a custom pointer more persuasive (as requested by a user).
632    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
633        pcretest.c, inside #ifndefs, because it seems they are sometimes already
634        pre-defined.
636    28. Added support for (*UTF8) at the start of a pattern.
638    29. Arrange for flags added by the "release type" setting in CMake to be shown
639        in the configuration summary.
642    Version 7.8 05-Sep-08
643    ---------------------
645    1.  Replaced UCP searching code with optimized version as implemented for Ad
646        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
647        stage table and inline lookup instead of a function, giving speed ups of 2
648        to 5 times on some simple patterns that I tested. Permission was given to
649        distribute the MultiStage2.py script that generates the tables (it's not in
650        the tarball, but is in the Subversion repository).
652    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
653        scripts.
655    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
656        a group with a zero qualifier. The result of the study could be incorrect,
657        or the function might crash, depending on the pattern.
659    4.  Caseless matching was not working for non-ASCII characters in back
660        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
661        It now works when Unicode Property Support is available.
663    5.  In pcretest, an escape such as \x{de} in the data was always generating
664        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
665        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
666        truncation.
668    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
670    7.  Added two (int) casts to pcregrep when printing the difference of two
671        pointers, in case they are 64-bit values.
673    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
674        test 2 if it fails.
676    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
677        and a #define of that name to empty if it is not externally set. This is to
678        allow users of MSVC to set it if necessary.
680    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
681        the convenience functions in the pcre_get.c source file.
683    11. An option change at the start of a pattern that had top-level alternatives
684        could cause overwriting and/or a crash. This command provoked a crash in
685        some environments:
687          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
689        This potential security problem was recorded as CVE-2008-2371.
691    12. For a pattern where the match had to start at the beginning or immediately
692        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
693        pcre_dfa_exec() could read past the end of the passed subject if there was
694        no match. To help with detecting such bugs (e.g. with valgrind), I modified
695        pcretest so that it places the subject at the end of its malloc-ed buffer.
697    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
698        exec() might read past the end of the data buffer in UTF-8 mode.
700    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
701        the data contained the byte 0x85 as part of a UTF-8 character within its
702        first line. This applied both to normal and DFA matching.
704    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
705        /^[^d]*?$/8 failed to match "abc".
707    16. Added a missing copyright notice to pcrecpp_internal.h.
709    17. Make it more clear in the documentation that values returned from
710        pcre_exec() in ovector are byte offsets, not character counts.
712    18. Tidied a few places to stop certain compilers from issuing warnings.
714    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
715        supplied by Stefan Weber. I made a further small update for 7.8 because
716        there is a change of source arrangements: the pcre_searchfuncs.c module is
717        replaced by pcre_ucd.c.
720    Version 7.7 07-May-08
721    ---------------------
723    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
724        a string to a long long, pretend we don't even have a long long." This is
725        done by checking for the strtoq, strtoll, and _strtoi64 functions.
727    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
728        pre-7.6 versions, which defined a global no_arg variable instead of putting
729        it in the RE class. (See also #8 below.)
731    3.  Remove a line of dead code, identified by coverity and reported by Nuno
732        Lopes.
734    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
736        (1) The include/exclude patterns were being applied to the whole pathnames
737            of files, instead of just to the final components.
739        (2) If there was more than one level of directory, the subdirectories were
740            skipped unless they satisfied the include/exclude conditions. This is
741            inconsistent with GNU grep (and could even be seen as contrary to the
742            pcregrep specification - which I improved to make it absolutely clear).
743            The action now is always to scan all levels of directory, and just
744            apply the include/exclude patterns to regular files.
746    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
747        --exclude_dir in the tests to avoid scanning .svn directories.
749    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
750        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
751        doesn't support NULs in patterns.
753    7.  Added some missing "const"s to declarations of static tables in
754        pcre_compile.c and pcre_dfa_exec.c.
756    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
757        caused by fix #2  above. (Subsequently also a second patch to fix the
758        first patch. And a third patch - this was a messy problem.)
760    9.  Applied Craig's patch to remove the use of push_back().
762    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
763        matching function regexec().
765    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
766        which, however, unlike Perl's \g{...}, are subroutine calls, not back
767        references. PCRE supports relative numbers with this syntax (I don't think
768        Oniguruma does).
770    12. Previously, a group with a zero repeat such as (...){0} was completely
771        omitted from the compiled regex. However, this means that if the group
772        was called as a subroutine from elsewhere in the pattern, things went wrong
773        (an internal error was given). Such groups are now left in the compiled
774        pattern, with a new opcode that causes them to be skipped at execution
775        time.
777    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
778        to the way PCRE behaves:
780        (a) A lone ] character is dis-allowed (Perl treats it as data).
782        (b) A back reference to an unmatched subpattern matches an empty string
783            (Perl fails the current match path).
785        (c) A data ] in a character class must be notated as \] because if the
786            first data character in a class is ], it defines an empty class. (In
787            Perl it is not possible to have an empty class.) The empty class []
788            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
789            The negative empty class [^] matches any one character, independently
790            of the DOTALL setting.
792    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
793        non-existent subpattern following a character class starting with ']' and
794        containing () gave an internal compiling error instead of "reference to
795        non-existent subpattern". Fortunately, when the pattern did exist, the
796        compiled code was correct. (When scanning forwards to check for the
797        existencd of the subpattern, it was treating the data ']' as terminating
798        the class, so got the count wrong. When actually compiling, the reference
799        was subsequently set up correctly.)
801    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
802        it was being rejected as not supported by pcre_dfa_exec(), even though
803        other assertions are supported. I have made pcre_dfa_exec() support
804        (*FAIL).
806    16. The implementation of 13c above involved the invention of a new opcode,
807        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
808        cannot be changed at match time, I realized I could make a small
809        improvement to matching performance by compiling OP_ALLANY instead of
810        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
811        on the OP_ANY path.
813    17. Compiling pcretest on Windows with readline support failed without the
814        following two fixes: (1) Make the unistd.h include conditional on
815        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
817    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
818        ncurses library to be included for pcretest when ReadLine support is
819        requested, but also to allow for it to be overridden. This patch came from
820        Daniel Bergström.
822    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
823        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
824        any errors with the current Unicode tables. Thanks to Peter Kankowski for
825        spotting this.
828    Version 7.6 28-Jan-08
829    ---------------------
831    1.  A character class containing a very large number of characters with
832        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
833        overflow.
835    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
836        HAVE_LONG_LONG is not defined.
838    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
839        bring them up to date and include new features. This patch includes:
841        - Fixed PH's badly added libz and libbz2 support.
842        - Fixed a problem with static linking.
843        - Added pcredemo. [But later removed - see 7 below.]
844        - Fixed dftables problem and added an option.
845        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
846            HAVE_LONG_LONG.
847        - Added readline support for pcretest.
848        - Added an listing of the option settings after cmake has run.
850    4.  A user submitted a patch to Makefile that makes it easy to create
851        "pcre.dll" under mingw when using Configure/Make. I added stuff to
852        Makefile.am that cause it to include this special target, without
853        affecting anything else. Note that the same mingw target plus all
854        the other distribution libraries and programs are now supported
855        when configuring with CMake (see 6 below) instead of with
856        Configure/Make.
858    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
859        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
860        exported in the Windows port". It has not yet been confirmed that the patch
861        solves the problem, but it does no harm.
863    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
864        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
865        with CMake, and also correct the comment about stack recursion.
867    7.  Remove the automatic building of pcredemo from the ./configure system and
868        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
869        of a program that users should build themselves after PCRE is installed, so
870        building it automatically is not really right. What is more, it gave
871        trouble in some build environments.
873    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
876    Version 7.5 10-Jan-08
877    ---------------------
879    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
880        values in parens when parsing an RE using the C++ wrapper."
882    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
883        Characters greater than 255 were excluded from the class instead of being
884        included.
886    3.  The same bug as (2) above applied to negated POSIX classes such as
887        [:^space:].
889    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
890        defined or documented. It seems to have been a typo for PCRE_STATIC, so
891        I have changed it.
893    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
894        first named subpattern) and a construct such as (?&a) would reference the
895        first named subpattern whose name started with "a" (in other words, the
896        length check was missing). Both these problems are fixed. "Subpattern name
897        expected" is now given for (?&) (a zero-length name), and this patch also
898        makes it give the same error for \k'' (previously it complained that that
899        was a reference to a non-existent subpattern).
901    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
902        this is right because (?- can be followed by option settings as well as by
903        digits. I have, however, made the messages clearer.
905    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
906        than the number used in the conditional) now cause a compile-time error.
907        This is actually not compatible with Perl, which accepts such patterns, but
908        treats the conditional as always being FALSE (as PCRE used to), but it
909        seems to me that giving a diagnostic is better.
911    8.  Change "alphameric" to the more common word "alphanumeric" in comments
912        and messages.
914    9.  Fix two occurrences of "backslash" in comments that should have been
915        "backspace".
917    10. Remove two redundant lines of code that can never be obeyed (their function
918        was moved elsewhere).
920    11. The program that makes PCRE's Unicode character property table had a bug
921        which caused it to generate incorrect table entries for sequences of
922        characters that have the same character type, but are in different scripts.
923        It amalgamated them into a single range, with the script of the first of
924        them. In other words, some characters were in the wrong script. There were
925        thirteen such cases, affecting characters in the following ranges:
927          U+002b0 - U+002c1
928          U+0060c - U+0060d
929          U+0061e - U+00612
930          U+0064b - U+0065e
931          U+0074d - U+0076d
932          U+01800 - U+01805
933          U+01d00 - U+01d77
934          U+01d9b - U+01dbf
935          U+0200b - U+0200f
936          U+030fc - U+030fe
937          U+03260 - U+0327f
938          U+0fb46 - U+0fbb1
939          U+10450 - U+1049d
941    12. The -o option (show only the matching part of a line) for pcregrep was not
942        compatible with GNU grep in that, if there was more than one match in a
943        line, it showed only the first of them. It now behaves in the same way as
944        GNU grep.
946    13. If the -o and -v options were combined for pcregrep, it printed a blank
947        line for every non-matching line. GNU grep prints nothing, and pcregrep now
948        does the same. The return code can be used to tell if there were any
949        non-matching lines.
951    14. Added --file-offsets and --line-offsets to pcregrep.
953    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
954        infinitely looping recursion. The bug was that positive lookaheads were not
955        being skipped when checking for a possible empty match (negative lookaheads
956        and both kinds of lookbehind were skipped).
958    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
959        inclusion of <windows.h> to before rather than after the definition of
960        INVALID_FILE_ATTRIBUTES (patch from David Byron).
962    17. Specifying a possessive quantifier with a specific limit for a Unicode
963        character property caused pcre_compile() to compile bad code, which led at
964        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
965        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
966        caused the error; without that there was no problem.
968    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
970    19. Added --enable-pcretest-libreadline.
972    20. In pcrecpp.cc, the variable 'count' was incremented twice in
973        RE::GlobalReplace(). As a result, the number of replacements returned was
974        double what it should be. I removed one of the increments, but Craig sent a
975        later patch that removed the other one (the right fix) and added unit tests
976        that check the return values (which was not done before).
978    21. Several CMake things:
980        (1) Arranged that, when cmake is used on Unix, the libraries end up with
981            the names libpcre and libpcreposix, not just pcre and pcreposix.
983        (2) The above change means that pcretest and pcregrep are now correctly
984            linked with the newly-built libraries, not previously installed ones.
988    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
989        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
990        UTF-8 newline character). The key issue is that the pattern starts .*;
991        this means that the match must be either at the beginning, or after a
992        newline. The bug was in the code for advancing after a failed match and
993        checking that the new position followed a newline. It was not taking
994        account of UTF-8 characters correctly.
996    23. PCRE was behaving differently from Perl in the way it recognized POSIX
997        character classes. PCRE was not treating the sequence [:...:] as a
998        character class unless the ... were all letters. Perl, however, seems to
999        allow any characters between [: and :], though of course it rejects as
1000        unknown any "names" that contain non-letters, because all the known class
1001        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
1002        for example, whereas PCRE did not - it did not recognize a POSIX character
1003        class. This seemed a bit dangerous, so the code has been changed to be
1004        closer to Perl. The behaviour is not identical to Perl, because PCRE will
1005        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
1006        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
1007        Perl does, and where it didn't before.
1009    24. Rewrite so as to remove the single use of %n from pcregrep because in some
1010        Windows environments %n is disabled by default.
1013    Version 7.4 21-Sep-07
1014    ---------------------
1016    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
1017        means that a class such as [\s] counted as "explicit reference to CR or
1018        LF". That isn't really right - the whole point of the change was to try to
1019        help when there was an actual mention of one of the two characters. So now
1020        the change happens only if \r or \n (or a literal CR or LF) character is
1021        encountered.
1023    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
1024        of both had grown to the point where there were only 3 bits left.
1025        Fortunately, there was spare space in the data structure, and so I have
1026        moved the internal flags into a new 16-bit field to free up more option
1027        bits.
1029    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
1030        but did not set the internal JCHANGED flag - either of these is enough to
1031        control the way the "get" function works - but the PCRE_INFO_JCHANGED
1032        facility is supposed to tell if (?J) was ever used, so now (?J) at the
1033        start sets both bits.
1035    4.  Added options (at build time, compile time, exec time) to change \R from
1036        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
1038    5.  doc/pcresyntax.html was missing from the distribution.
1040    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
1041        compatibility, even though it is no longer used.
1043    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
1044        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
1045        windows.h file is present (where different names are used). [This was
1046        reversed later after testing - see 16 below.]
1048    8.  Changed all #include <config.h> to #include "config.h". There were also
1049        some further <pcre.h> cases that I changed to "pcre.h".
1051    9.  When pcregrep was used with the --colour option, it missed the line ending
1052        sequence off the lines that it output.
1054    10. It was pointed out to me that arrays of string pointers cause lots of
1055        relocations when a shared library is dynamically loaded. A technique of
1056        using a single long string with a table of offsets can drastically reduce
1057        these. I have refactored PCRE in four places to do this. The result is
1058        dramatic:
1060          Originally:                          290
1061          After changing UCP table:            187
1062          After changing error message table:   43
1063          After changing table of "verbs"       36
1064          After changing table of Posix names   22
1066        Thanks to the folks working on Gregex for glib for this insight.
1068    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
1069        unicode-properties was also set.
1071    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
1073    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
1074        checked only for CRLF.
1076    14. Added casts to pcretest.c to avoid compiler warnings.
1078    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
1080    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
1081        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
1082        entirely. This removes changes made in 7 above.
1084    17. The CMake files have been updated, and there is now more information about
1085        building with CMake in the NON-UNIX-USE document.
1088    Version 7.3 28-Aug-07
1089    ---------------------
1091     1. In the rejigging of the build system that eventually resulted in 7.1, the
1092        line "#include <pcre.h>" was included in pcre_internal.h. The use of angle
1093        brackets there is not right, since it causes compilers to look for an
1094        installed pcre.h, not the version that is in the source that is being
1095        compiled (which of course may be different). I have changed it back to:
1097          #include "pcre.h"
1099        I have a vague recollection that the change was concerned with compiling in
1100        different directories, but in the new build system, that is taken care of
1101        by the VPATH setting the Makefile.
1103     2. The pattern .*$ when run in not-DOTALL UTF-8 mode with newline=any failed
1104        when the subject happened to end in the byte 0x85 (e.g. if the last
1105        character was \x{1ec5}). *Character* 0x85 is one of the "any" newline
1106        characters but of course it shouldn't be taken as a newline when it is part
1107        of another character. The bug was that, for an unlimited repeat of . in
1108        not-DOTALL UTF-8 mode, PCRE was advancing by bytes rather than by
1109        characters when looking for a newline.
1111     3. A small performance improvement in the DOTALL UTF-8 mode .* case.
1113     4. Debugging: adjusted the names of opcodes for different kinds of parentheses
1114        in debug output.
1116     5. Arrange to use "%I64d" instead of "%lld" and "%I64u" instead of "%llu" for
1117        long printing in the pcrecpp unittest when running under MinGW.
1119     6. ESC_K was left out of the EBCDIC table.
1121     7. Change 7.0/38 introduced a new limit on the number of nested non-capturing
1122        parentheses; I made it 1000, which seemed large enough. Unfortunately, the
1123        limit also applies to "virtual nesting" when a pattern is recursive, and in
1124        this case 1000 isn't so big. I have been able to remove this limit at the
1125        expense of backing off one optimization in certain circumstances. Normally,
1126        when pcre_exec() would call its internal match() function recursively and
1127        immediately return the result unconditionally, it uses a "tail recursion"
1128        feature to save stack. However, when a subpattern that can match an empty
1129        string has an unlimited repetition quantifier, it no longer makes this
1130        optimization. That gives it a stack frame in which to save the data for
1131        checking that an empty string has been matched. Previously this was taken
1132        from the 1000-entry workspace that had been reserved. So now there is no
1133        explicit limit, but more stack is used.
1135     8. Applied Daniel's patches to solve problems with the import/export magic
1136        syntax that is required for Windows, and which was going wrong for the
1137        pcreposix and pcrecpp parts of the library. These were overlooked when this
1138        problem was solved for the main library.
1140     9. There were some crude static tests to avoid integer overflow when computing
1141        the size of patterns that contain repeated groups with explicit upper
1142        limits. As the maximum quantifier is 65535, the maximum group length was
1143        set at 30,000 so that the product of these two numbers did not overflow a
1144        32-bit integer. However, it turns out that people want to use groups that
1145        are longer than 30,000 bytes (though not repeat them that many times).
1146        Change 7.0/17 (the refactoring of the way the pattern size is computed) has
1147        made it possible to implement the integer overflow checks in a much more
1148        dynamic way, which I have now done. The artificial limitation on group
1149        length has been removed - we now have only the limit on the total length of
1150        the compiled pattern, which depends on the LINK_SIZE setting.
1152    10. Fixed a bug in the documentation for get/copy named substring when
1153        duplicate names are permitted. If none of the named substrings are set, the
1154        functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an
1155        empty string.
1157    11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E
1158        instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,
1159        because the ] is interpreted as the first data character and the
1160        terminating ] is not found. PCRE has been made compatible with Perl in this
1161        regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could
1162        cause memory overwriting.
1164    10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty
1165        string has been matched (to stop an infinite loop). It was not recognizing
1166        a conditional subpattern that could match an empty string if that
1167        subpattern was within another subpattern. For example, it looped when
1168        trying to match  (((?(1)X|))*)  but it was OK with  ((?(1)X|)*)  where the
1169        condition was not nested. This bug has been fixed.
1171    12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack
1172        past the start of the subject in the presence of bytes with the top bit
1173        set, for example "\x8aBCD".
1175    13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
1176        (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
1178    14. Optimized (?!) to (*FAIL).
1180    15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
1181        This restricts code points to be within the range 0 to 0x10FFFF, excluding
1182        the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
1183        full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
1184        does: it's just the validity check that is more restrictive.
1186    16. Inserted checks for integer overflows during escape sequence (backslash)
1187        processing, and also fixed erroneous offset values for syntax errors during
1188        backslash processing.
1190    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
1191        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
1193    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
1194        caused an overrun.
1196    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
1197        something other than just ASCII characters) inside a group that had an
1198        unlimited repeat caused a loop at compile time (while checking to see
1199        whether the group could match an empty string).
1201    20. Debugging a pattern containing \p or \P could cause a crash. For example,
1202        [\P{Any}] did so. (Error in the code for printing property names.)
1204    21. An orphan \E inside a character class could cause a crash.
1206    22. A repeated capturing bracket such as (A)? could cause a wild memory
1207        reference during compilation.
1209    23. There are several functions in pcre_compile() that scan along a compiled
1210        expression for various reasons (e.g. to see if it's fixed length for look
1211        behind). There were bugs in these functions when a repeated \p or \P was
1212        present in the pattern. These operators have additional parameters compared
1213        with \d, etc, and these were not being taken into account when moving along
1214        the compiled data. Specifically:
1216        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
1217            length.
1219        (b) An item such as \pL+ within a repeated group could cause crashes or
1220            loops.
1222        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
1223            "reference to non-existent subpattern" error.
1225        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
1227    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
1228        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
1230    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
1232    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
1233        character were causing crashes (broken optimization).
1235    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
1236        \p or \P) caused a compile-time loop.
1238    28. More problems have arisen in unanchored patterns when CRLF is a valid line
1239        break. For example, the unstudied pattern [\r\n]A does not match the string
1240        "\r\nA" because change 7.0/46 below moves the current point on by two
1241        characters after failing to match at the start. However, the pattern \nA
1242        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
1243        the same is true. There doesn't seem any very clean way out of this, but
1244        what I have chosen to do makes the common cases work: PCRE now takes note
1245        of whether there can be an explicit match for \r or \n anywhere in the
1246        pattern, and if so, 7.0/46 no longer applies. As part of this change,
1247        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
1248        pattern has explicit CR or LF references.
1250    29. Added (*CR) etc for changing newline setting at start of pattern.
1253    Version 7.2 19-Jun-07
1254    ---------------------
1256     1. If the fr_FR locale cannot be found for test 3, try the "french" locale,
1257        which is apparently normally available under Windows.
1259     2. Re-jig the pcregrep tests with different newline settings in an attempt
1260        to make them independent of the local environment's newline setting.
1262     3. Add code to configure.ac to remove -g from the CFLAGS default settings.
1264     4. Some of the "internals" tests were previously cut out when the link size
1265        was not 2, because the output contained actual offsets. The recent new
1266        "Z" feature of pcretest means that these can be cut out, making the tests
1267        usable with all link sizes.
1269     5. Implemented Stan Switzer's goto replacement for longjmp() when not using
1270        stack recursion. This gives a massive performance boost under BSD, but just
1271        a small improvement under Linux. However, it saves one field in the frame
1272        in all cases.
1274     6. Added more features from the forthcoming Perl 5.10:
1276        (a) (?-n) (where n is a string of digits) is a relative subroutine or
1277            recursion call. It refers to the nth most recently opened parentheses.
1279        (b) (?+n) is also a relative subroutine call; it refers to the nth next
1280            to be opened parentheses.
1282        (c) Conditions that refer to capturing parentheses can be specified
1283            relatively, for example, (?(-2)... or (?(+3)...
1285        (d) \K resets the start of the current match so that everything before
1286            is not part of it.
1288        (e) \k{name} is synonymous with \k<name> and \k'name' (.NET compatible).
1290        (f) \g{name} is another synonym - part of Perl 5.10's unification of
1291            reference syntax.
1293        (g) (?| introduces a group in which the numbering of parentheses in each
1294            alternative starts with the same number.
1296        (h) \h, \H, \v, and \V match horizontal and vertical whitespace.
1298     7. Added two new calls to pcre_fullinfo(): PCRE_INFO_OKPARTIAL and
1301     8. A pattern such as  (.*(.)?)*  caused pcre_exec() to fail by either not
1302        terminating or by crashing. Diagnosed by Viktor Griph; it was in the code
1303        for detecting groups that can match an empty string.
1305     9. A pattern with a very large number of alternatives (more than several
1306        hundred) was running out of internal workspace during the pre-compile
1307        phase, where pcre_compile() figures out how much memory will be needed. A
1308        bit of new cunning has reduced the workspace needed for groups with
1309        alternatives. The 1000-alternative test pattern now uses 12 bytes of
1310        workspace instead of running out of the 4096 that are available.
1312    10. Inserted some missing (unsigned int) casts to get rid of compiler warnings.
1314    11. Applied patch from Google to remove an optimization that didn't quite work.
1315        The report of the bug said:
1317          pcrecpp::RE("a*").FullMatch("aaa") matches, while
1318          pcrecpp::RE("a*?").FullMatch("aaa") does not, and
1319          pcrecpp::RE("a*?\\z").FullMatch("aaa") does again.
1321    12. If \p or \P was used in non-UTF-8 mode on a character greater than 127
1322        it matched the wrong number of bytes.
1325    Version 7.1 24-Apr-07
1326    ---------------------
1328     1. Applied Bob Rossi and Daniel G's patches to convert the build system to one
1329        that is more "standard", making use of automake and other Autotools. There
1330        is some re-arrangement of the files and adjustment of comments consequent
1331        on this.
1333     2. Part of the patch fixed a problem with the pcregrep tests. The test of -r
1334        for recursive directory scanning broke on some systems because the files
1335        are not scanned in any specific order and on different systems the order
1336        was different. A call to "sort" has been inserted into RunGrepTest for the
1337        approprate test as a short-term fix. In the longer term there may be an
1338        alternative.
1340     3. I had an email from Eric Raymond about problems translating some of PCRE's
1341        man pages to HTML (despite the fact that I distribute HTML pages, some
1342        people do their own conversions for various reasons). The problems
1343        concerned the use of low-level troff macros .br and .in. I have therefore
1344        removed all such uses from the man pages (some were redundant, some could
1345        be replaced by .nf/.fi pairs). The 132html script that I use to generate
1346        HTML has been updated to handle .nf/.fi and to complain if it encounters
1347        .br or .in.
1349     4. Updated comments in configure.ac that get placed in config.h.in and also
1350        arranged for config.h to be included in the distribution, with the name
1351        config.h.generic, for the benefit of those who have to compile without
1352        Autotools (compare pcre.h, which is now distributed as pcre.h.generic).
1354     5. Updated the support (such as it is) for Virtual Pascal, thanks to Stefan
1355        Weber: (1) pcre_internal.h was missing some function renames; (2) updated
1356        makevp.bat for the current PCRE, using the additional files
1357        makevp_c.txt, makevp_l.txt, and pcregexp.pas.
1359     6. A Windows user reported a minor discrepancy with test 2, which turned out
1360        to be caused by a trailing space on an input line that had got lost in his
1361        copy. The trailing space was an accident, so I've just removed it.
1363     7. Add -Wl,-R... flags in pcre-config.in for *BSD* systems, as I'm told
1364        that is needed.
1366     8. Mark ucp_table (in ucptable.h) and ucp_gentype (in pcre_ucp_searchfuncs.c)
1367        as "const" (a) because they are and (b) because it helps the PHP
1368        maintainers who have recently made a script to detect big data structures
1369        in the php code that should be moved to the .rodata section. I remembered
1370        to update Builducptable as well, so it won't revert if ucptable.h is ever
1371        re-created.
1373     9. Added some extra #ifdef SUPPORT_UTF8 conditionals into pcretest.c,
1374        pcre_printint.src, pcre_compile.c, pcre_study.c, and pcre_tables.c, in
1375        order to be able to cut out the UTF-8 tables in the latter when UTF-8
1376        support is not required. This saves 1.5-2K of code, which is important in
1377        some applications.
1379        Later: more #ifdefs are needed in pcre_ord2utf8.c and pcre_valid_utf8.c
1380        so as not to refer to the tables, even though these functions will never be
1381        called when UTF-8 support is disabled. Otherwise there are problems with a
1382        shared library.
1384    10. Fixed two bugs in the emulated memmove() function in pcre_internal.h:
1386        (a) It was defining its arguments as char * instead of void *.
1388        (b) It was assuming that all moves were upwards in memory; this was true
1389            a long time ago when I wrote it, but is no longer the case.
1391        The emulated memove() is provided for those environments that have neither
1392        memmove() nor bcopy(). I didn't think anyone used it these days, but that
1393        is clearly not the case, as these two bugs were recently reported.
1395    11. The script PrepareRelease is now distributed: it calls 132html, CleanTxt,
1396        and Detrail to create the HTML documentation, the .txt form of the man
1397        pages, and it removes trailing spaces from listed files. It also creates
1398        pcre.h.generic and config.h.generic from pcre.h and config.h. In the latter
1399        case, it wraps all the #defines with #ifndefs. This script should be run
1400        before "make dist".
1402    12. Fixed two fairly obscure bugs concerned with quantified caseless matching
1403        with Unicode property support.
1405        (a) For a maximizing quantifier, if the two different cases of the
1406            character were of different lengths in their UTF-8 codings (there are
1407            some cases like this - I found 11), and the matching function had to
1408            back up over a mixture of the two cases, it incorrectly assumed they
1409            were both the same length.
1411        (b) When PCRE was configured to use the heap rather than the stack for
1412            recursion during matching, it was not correctly preserving the data for
1413            the other case of a UTF-8 character when checking ahead for a match
1414            while processing a minimizing repeat. If the check also involved
1415            matching a wide character, but failed, corruption could cause an
1416            erroneous result when trying to check for a repeat of the original
1417            character.
1419    13. Some tidying changes to the testing mechanism:
1421        (a) The RunTest script now detects the internal link size and whether there
1422            is UTF-8 and UCP support by running ./pcretest -C instead of relying on
1423            values substituted by "configure". (The RunGrepTest script already did
1424            this for UTF-8.) The configure.ac script no longer substitutes the
1425            relevant variables.
1427        (b) The debugging options /B and /D in pcretest show the compiled bytecode
1428            with length and offset values. This means that the output is different
1429            for different internal link sizes. Test 2 is skipped for link sizes
1430            other than 2 because of this, bypassing the problem. Unfortunately,
1431            there was also a test in test 3 (the locale tests) that used /B and
1432            failed for link sizes other than 2. Rather than cut the whole test out,
1433            I have added a new /Z option to pcretest that replaces the length and
1434            offset values with spaces. This is now used to make test 3 independent
1435            of link size. (Test 2 will be tidied up later.)
1437    14. If erroroffset was passed as NULL to pcre_compile, it provoked a
1438        segmentation fault instead of returning the appropriate error message.
1440    15. In multiline mode when the newline sequence was set to "any", the pattern
1441        ^$ would give a match between the \r and \n of a subject such as "A\r\nB".
1442        This doesn't seem right; it now treats the CRLF combination as the line
1443        ending, and so does not match in that case. It's only a pattern such as ^$
1444        that would hit this one: something like ^ABC$ would have failed after \r
1445        and then tried again after \r\n.
1447    16. Changed the comparison command for RunGrepTest from "diff -u" to "diff -ub"
1448        in an attempt to make files that differ only in their line terminators
1449        compare equal. This works on Linux.
1451    17. Under certain error circumstances pcregrep might try to free random memory
1452        as it exited. This is now fixed, thanks to valgrind.
1454    19. In pcretest, if the pattern /(?m)^$/g<any> was matched against the string
1455        "abc\r\n\r\n", it found an unwanted second match after the second \r. This
1456        was because its rules for how to advance for /g after matching an empty
1457        string at the end of a line did not allow for this case. They now check for
1458        it specially.
1460    20. pcretest is supposed to handle patterns and data of any length, by
1461        extending its buffers when necessary. It was getting this wrong when the
1462        buffer for a data line had to be extended.
1464    21. Added PCRE_NEWLINE_ANYCRLF which is like ANY, but matches only CR, LF, or
1465        CRLF as a newline sequence.
1467    22. Code for handling Unicode properties in pcre_dfa_exec() wasn't being cut
1468        out by #ifdef SUPPORT_UCP. This did no harm, as it could never be used, but
1469        I have nevertheless tidied it up.
1471    23. Added some casts to kill warnings from HP-UX ia64 compiler.
1473    24. Added a man page for pcre-config.
1476    Version 7.0 19-Dec-06
1477    ---------------------
1479     1. Fixed a signed/unsigned compiler warning in pcre_compile.c, shown up by
1480        moving to gcc 4.1.1.
1482     2. The -S option for pcretest uses setrlimit(); I had omitted to #include
1483        sys/time.h, which is documented as needed for this function. It doesn't
1484        seem to matter on Linux, but it showed up on some releases of OS X.
1486     3. It seems that there are systems where bytes whose values are greater than
1487        127 match isprint() in the "C" locale. The "C" locale should be the
1488        default when a C program starts up. In most systems, only ASCII printing
1489        characters match isprint(). This difference caused the output from pcretest
1490        to vary, making some of the tests fail. I have changed pcretest so that:
1492        (a) When it is outputting text in the compiled version of a pattern, bytes
1493            other than 32-126 are always shown as hex escapes.
1495        (b) When it is outputting text that is a matched part of a subject string,
1496            it does the same, unless a different locale has been set for the match
1497            (using the /L modifier). In this case, it uses isprint() to decide.
1499     4. Fixed a major bug that caused incorrect computation of the amount of memory
1500        required for a compiled pattern when options that changed within the
1501        pattern affected the logic of the preliminary scan that determines the
1502        length. The relevant options are -x, and -i in UTF-8 mode. The result was
1503        that the computed length was too small. The symptoms of this bug were
1504        either the PCRE error "internal error: code overflow" from pcre_compile(),
1505        or a glibc crash with a message such as "pcretest: free(): invalid next
1506        size (fast)". Examples of patterns that provoked this bug (shown in
1507        pcretest format) are:
1509          /(?-x: )/x
1510          /(?x)(?-x: \s*#\s*)/
1511          /((?i)[\x{c0}])/8
1512          /(?i:[\x{c0}])/8
1514        HOWEVER: Change 17 below makes this fix obsolete as the memory computation
1515        is now done differently.
1517     5. Applied patches from Google to: (a) add a QuoteMeta function to the C++
1518        wrapper classes; (b) implement a new function in the C++ scanner that is
1519        more efficient than the old way of doing things because it avoids levels of
1520        recursion in the regex matching; (c) add a paragraph to the documentation
1521        for the FullMatch() function.
1523     6. The escape sequence \n was being treated as whatever was defined as
1524        "newline". Not only was this contrary to the documentation, which states
1525        that \n is character 10 (hex 0A), but it also went horribly wrong when
1526        "newline" was defined as CRLF. This has been fixed.
1528     7. In pcre_dfa_exec.c the value of an unsigned integer (the variable called c)
1529        was being set to -1 for the "end of line" case (supposedly a value that no
1530        character can have). Though this value is never used (the check for end of
1531        line is "zero bytes in current character"), it caused compiler complaints.
1532        I've changed it to 0xffffffff.
1534     8. In pcre_version.c, the version string was being built by a sequence of
1535        C macros that, in the event of PCRE_PRERELEASE being defined as an empty
1536        string (as it is for production releases) called a macro with an empty
1537        argument. The C standard says the result of this is undefined. The gcc
1538        compiler treats it as an empty string (which was what was wanted) but it is
1539        reported that Visual C gives an error. The source has been hacked around to
1540        avoid this problem.
1542     9. On the advice of a Windows user, included <io.h> and <fcntl.h> in Windows
1543        builds of pcretest, and changed the call to _setmode() to use _O_BINARY
1544        instead of 0x8000. Made all the #ifdefs test both _WIN32 and WIN32 (not all
1545        of them did).
1547    10. Originally, pcretest opened its input and output without "b"; then I was
1548        told that "b" was needed in some environments, so it was added for release
1549        5.0 to both the input and output. (It makes no difference on Unix-like
1550        systems.) Later I was told that it is wrong for the input on Windows. I've
1551        now abstracted the modes into two macros, to make it easier to fiddle with
1552        them, and removed "b" from the input mode under Windows.
1554    11. Added pkgconfig support for the C++ wrapper library, libpcrecpp.
1556    12. Added -help and --help to pcretest as an official way of being reminded
1557        of the options.
1559    13. Removed some redundant semicolons after macro calls in pcrecpparg.h.in
1560        and pcrecpp.cc because they annoy compilers at high warning levels.
1562    14. A bit of tidying/refactoring in pcre_exec.c in the main bumpalong loop.
1564    15. Fixed an occurrence of == in configure.ac that should have been = (shell
1565        scripts are not C programs :-) and which was not noticed because it works
1566        on Linux.
1568    16. pcretest is supposed to handle any length of pattern and data line (as one
1569        line or as a continued sequence of lines) by extending its input buffer if
1570        necessary. This feature was broken for very long pattern lines, leading to
1571        a string of junk being passed to pcre_compile() if the pattern was longer
1572        than about 50K.
1574    17. I have done a major re-factoring of the way pcre_compile() computes the
1575        amount of memory needed for a compiled pattern. Previously, there was code
1576        that made a preliminary scan of the pattern in order to do this. That was
1577        OK when PCRE was new, but as the facilities have expanded, it has become
1578        harder and harder to keep it in step with the real compile phase, and there
1579        have been a number of bugs (see for example, 4 above). I have now found a
1580        cunning way of running the real compile function in a "fake" mode that
1581        enables it to compute how much memory it would need, while actually only
1582        ever using a few hundred bytes of working memory and without too many
1583        tests of the mode. This should make future maintenance and development
1584        easier. A side effect of this work is that the limit of 200 on the nesting
1585        depth of parentheses has been removed (though this was never a serious
1586        limitation, I suspect). However, there is a downside: pcre_compile() now
1587        runs more slowly than before (30% or more, depending on the pattern). I
1588        hope this isn't a big issue. There is no effect on runtime performance.
1590    18. Fixed a minor bug in pcretest: if a pattern line was not terminated by a
1591        newline (only possible for the last line of a file) and it was a
1592        pattern that set a locale (followed by /Lsomething), pcretest crashed.
1594    19. Added additional timing features to pcretest. (1) The -tm option now times
1595        matching only, not compiling. (2) Both -t and -tm can be followed, as a
1596        separate command line item, by a number that specifies the number of
1597        repeats to use when timing. The default is 50000; this gives better
1598        precision, but takes uncomfortably long for very large patterns.
1600    20. Extended pcre_study() to be more clever in cases where a branch of a
1601        subpattern has no definite first character. For example, (a*|b*)[cd] would
1602        previously give no result from pcre_study(). Now it recognizes that the
1603        first character must be a, b, c, or d.
1605    21. There was an incorrect error "recursive call could loop indefinitely" if
1606        a subpattern (or the entire pattern) that was being tested for matching an
1607        empty string contained only one non-empty item after a nested subpattern.
1608        For example, the pattern (?>\x{100}*)\d(?R) provoked this error
1609        incorrectly, because the \d was being skipped in the check.
1611    22. The pcretest program now has a new pattern option /B and a command line
1612        option -b, which is equivalent to adding /B to every pattern. This causes
1613        it to show the compiled bytecode, without the additional information that
1614        -d shows. The effect of -d is now the same as -b with -i (and similarly, /D
1615        is the same as /B/I).
1617    23. A new optimization is now able automatically to treat some sequences such
1618        as a*b as a*+b. More specifically, if something simple (such as a character
1619        or a simple class like \d) has an unlimited quantifier, and is followed by
1620        something that cannot possibly match the quantified thing, the quantifier
1621        is automatically "possessified".
1623    24. A recursive reference to a subpattern whose number was greater than 39
1624        went wrong under certain circumstances in UTF-8 mode. This bug could also
1625        have affected the operation of pcre_study().
1627    25. Realized that a little bit of performance could be had by replacing
1628        (c & 0xc0) == 0xc0 with c >= 0xc0 when processing UTF-8 characters.
1630    26. Timing data from pcretest is now shown to 4 decimal places instead of 3.
1632    27. Possessive quantifiers such as a++ were previously implemented by turning
1633        them into atomic groups such as ($>a+). Now they have their own opcodes,
1634        which improves performance. This includes the automatically created ones
1635        from 23 above.
1637    28. A pattern such as (?=(\w+))\1: which simulates an atomic group using a
1638        lookahead was broken if it was not anchored. PCRE was mistakenly expecting
1639        the first matched character to be a colon. This applied both to named and
1640        numbered groups.
1642    29. The ucpinternal.h header file was missing its idempotency #ifdef.
1644    30. I was sent a "project" file called libpcre.a.dev which I understand makes
1645        building PCRE on Windows easier, so I have included it in the distribution.
1647    31. There is now a check in pcretest against a ridiculously large number being
1648        returned by pcre_exec() or pcre_dfa_exec(). If this happens in a /g or /G
1649        loop, the loop is abandoned.
1651    32. Forward references to subpatterns in conditions such as (?(2)...) where
1652        subpattern 2 is defined later cause pcre_compile() to search forwards in
1653        the pattern for the relevant set of parentheses. This search went wrong
1654        when there were unescaped parentheses in a character class, parentheses
1655        escaped with \Q...\E, or parentheses in a #-comment in /x mode.
1657    33. "Subroutine" calls and backreferences were previously restricted to
1658        referencing subpatterns earlier in the regex. This restriction has now
1659        been removed.
1661    34. Added a number of extra features that are going to be in Perl 5.10. On the
1662        whole, these are just syntactic alternatives for features that PCRE had
1663        previously implemented using the Python syntax or my own invention. The
1664        other formats are all retained for compatibility.
1666        (a) Named groups can now be defined as (?<name>...) or (?'name'...) as well
1667            as (?P<name>...). The new forms, as well as being in Perl 5.10, are
1668            also .NET compatible.
1670        (b) A recursion or subroutine call to a named group can now be defined as
1671            (?&name) as well as (?P>name).
1673        (c) A backreference to a named group can now be defined as \k<name> or
1674            \k'name' as well as (?P=name). The new forms, as well as being in Perl
1675            5.10, are also .NET compatible.
1677        (d) A conditional reference to a named group can now use the syntax
1678            (?(<name>) or (?('name') as well as (?(name).
1680        (e) A "conditional group" of the form (?(DEFINE)...) can be used to define
1681            groups (named and numbered) that are never evaluated inline, but can be
1682            called as "subroutines" from elsewhere. In effect, the DEFINE condition
1683            is always false. There may be only one alternative in such a group.
1685        (f) A test for recursion can be given as (?(R1).. or (?(R&name)... as well
1686            as the simple (?(R). The condition is true only if the most recent
1687            recursion is that of the given number or name. It does not search out
1688            through the entire recursion stack.
1690        (g) The escape \gN or \g{N} has been added, where N is a positive or
1691            negative number, specifying an absolute or relative reference.
1693    35. Tidied to get rid of some further signed/unsigned compiler warnings and
1694        some "unreachable code" warnings.
1696    36. Updated the Unicode property tables to Unicode version 5.0.0. Amongst other
1697        things, this adds five new scripts.
1699    37. Perl ignores orphaned \E escapes completely. PCRE now does the same.
1700        There were also incompatibilities regarding the handling of \Q..\E inside
1701        character classes, for example with patterns like [\Qa\E-\Qz\E] where the
1702        hyphen was adjacent to \Q or \E. I hope I've cleared all this up now.
1704    38. Like Perl, PCRE detects when an indefinitely repeated parenthesized group
1705        matches an empty string, and forcibly breaks the loop. There were bugs in
1706        this code in non-simple cases. For a pattern such as  ^(a()*)*  matched
1707        against  aaaa  the result was just "a" rather than "aaaa", for example. Two
1708        separate and independent bugs (that affected different cases) have been
1709        fixed.
1711    39. Refactored the code to abolish the use of different opcodes for small
1712        capturing bracket numbers. This is a tidy that I avoided doing when I
1713        removed the limit on the number of capturing brackets for 3.5 back in 2001.
1714        The new approach is not only tidier, it makes it possible to reduce the
1715        memory needed to fix the previous bug (38).
1717    40. Implemented PCRE_NEWLINE_ANY to recognize any of the Unicode newline
1718        sequences (http://unicode.org/unicode/reports/tr18/) as "newline" when
1719        processing dot, circumflex, or dollar metacharacters, or #-comments in /x
1720        mode.
1722    41. Add \R to match any Unicode newline sequence, as suggested in the Unicode
1723        report.
1725    42. Applied patch, originally from Ari Pollak, modified by Google, to allow
1726        copy construction and assignment in the C++ wrapper.
1728    43. Updated pcregrep to support "--newline=any". In the process, I fixed a
1729        couple of bugs that could have given wrong results in the "--newline=crlf"
1730        case.
1732    44. Added a number of casts and did some reorganization of signed/unsigned int
1733        variables following suggestions from Dair Grant. Also renamed the variable
1734        "this" as "item" because it is a C++ keyword.
1736    45. Arranged for dftables to add
1738          #include "pcre_internal.h"
1740        to pcre_chartables.c because without it, gcc 4.x may remove the array
1741        definition from the final binary if PCRE is built into a static library and
1742        dead code stripping is activated.
1744    46. For an unanchored pattern, if a match attempt fails at the start of a
1745        newline sequence, and the newline setting is CRLF or ANY, and the next two
1746        characters are CRLF, advance by two characters instead of one.
1749    Version 6.7 04-Jul-06
1750    ---------------------
1752     1. In order to handle tests when input lines are enormously long, pcretest has
1753        been re-factored so that it automatically extends its buffers when
1754        necessary. The code is crude, but this _is_ just a test program. The
1755        default size has been increased from 32K to 50K.
1757     2. The code in pcre_study() was using the value of the re argument before
1758        testing it for NULL. (Of course, in any sensible call of the function, it
1759        won't be NULL.)
1761     3. The memmove() emulation function in pcre_internal.h, which is used on
1762        systems that lack both memmove() and bcopy() - that is, hardly ever -
1763        was missing a "static" storage class specifier.
1765     4. When UTF-8 mode was not set, PCRE looped when compiling certain patterns
1766        containing an extended class (one that cannot be represented by a bitmap
1767        because it contains high-valued characters or Unicode property items, e.g.
1768        [\pZ]). Almost always one would set UTF-8 mode when processing such a
1769        pattern, but PCRE should not loop if you do not (it no longer does).
1770        [Detail: two cases were found: (a) a repeated subpattern containing an
1771        extended class; (b) a recursive reference to a subpattern that followed a
1772        previous extended class. It wasn't skipping over the extended class
1773        correctly when UTF-8 mode was not set.]
1775     5. A negated single-character class was not being recognized as fixed-length
1776        in lookbehind assertions such as (?<=[^f]), leading to an incorrect
1777        compile error "lookbehind assertion is not fixed length".
1779     6. The RunPerlTest auxiliary script was showing an unexpected difference
1780        between PCRE and Perl for UTF-8 tests. It turns out that it is hard to
1781        write a Perl script that can interpret lines of an input file either as
1782        byte characters or as UTF-8, which is what "perltest" was being required to
1783        do for the non-UTF-8 and UTF-8 tests, respectively. Essentially what you
1784        can't do is switch easily at run time between having the "use utf8;" pragma
1785        or not. In the end, I fudged it by using the RunPerlTest script to insert
1786        "use utf8;" explicitly for the UTF-8 tests.
1788     7. In multiline (/m) mode, PCRE was matching ^ after a terminating newline at
1789        the end of the subject string, contrary to the documentation and to what
1790        Perl does. This was true of both matching functions. Now it matches only at
1791        the start of the subject and immediately after *internal* newlines.
1793     8. A call of pcre_fullinfo() from pcretest to get the option bits was passing
1794        a pointer to an int instead of a pointer to an unsigned long int. This
1795        caused problems on 64-bit systems.
1797     9. Applied a patch from the folks at Google to pcrecpp.cc, to fix "another
1798        instance of the 'standard' template library not being so standard".
1800    10. There was no check on the number of named subpatterns nor the maximum
1801        length of a subpattern name. The product of these values is used to compute
1802        the size of the memory block for a compiled pattern. By supplying a very
1803        long subpattern name and a large number of named subpatterns, the size
1804        computation could be caused to overflow. This is now prevented by limiting
1805        the length of names to 32 characters, and the number of named subpatterns
1806        to 10,000.
1808    11. Subpatterns that are repeated with specific counts have to be replicated in
1809        the compiled pattern. The size of memory for this was computed from the
1810        length of the subpattern and the repeat count. The latter is limited to
1811        65535, but there was no limit on the former, meaning that integer overflow
1812        could in principle occur. The compiled length of a repeated subpattern is
1813        now limited to 30,000 bytes in order to prevent this.
1815    12. Added the optional facility to have named substrings with the same name.
1817    13. Added the ability to use a named substring as a condition, using the
1818        Python syntax: (?(name)yes|no). This overloads (?(R)... and names that
1819        are numbers (not recommended). Forward references are permitted.
1821    14. Added forward references in named backreferences (if you see what I mean).
1823    15. In UTF-8 mode, with the PCRE_DOTALL option set, a quantified dot in the
1824        pattern could run off the end of the subject. For example, the pattern
1825        "(?s)(.{1,5})"8 did this with the subject "ab".
1827    16. If PCRE_DOTALL or PCRE_MULTILINE were set, pcre_dfa_exec() behaved as if
1828        PCRE_CASELESS was set when matching characters that were quantified with ?
1829        or *.
1831    17. A character class other than a single negated character that had a minimum
1832        but no maximum quantifier - for example [ab]{6,} - was not handled
1833        correctly by pce_dfa_exec(). It would match only one character.
1835    18. A valid (though odd) pattern that looked like a POSIX character
1836        class but used an invalid character after [ (for example [[,abc,]]) caused
1837        pcre_compile() to give the error "Failed: internal error: code overflow" or
1838        in some cases to crash with a glibc free() error. This could even happen if
1839        the pattern terminated after [[ but there just happened to be a sequence of
1840        letters, a binary zero, and a closing ] in the memory that followed.
1842    19. Perl's treatment of octal escapes in the range \400 to \777 has changed
1843        over the years. Originally (before any Unicode support), just the bottom 8
1844        bits were taken. Thus, for example, \500 really meant \100. Nowadays the
1845        output from "man perlunicode" includes this:
1847          The regular expression compiler produces polymorphic opcodes.  That
1848          is, the pattern adapts to the data and automatically switches to
1849          the Unicode character scheme when presented with Unicode data--or
1850          instead uses a traditional byte scheme when presented with byte
1851          data.
1853        Sadly, a wide octal escape does not cause a switch, and in a string with
1854        no other multibyte characters, these octal escapes are treated as before.
1855        Thus, in Perl, the pattern  /\500/ actually matches \100 but the pattern
1856        /\500|\x{1ff}/ matches \500 or \777 because the whole thing is treated as a
1857        Unicode string.
1859        I have not perpetrated such confusion in PCRE. Up till now, it took just
1860        the bottom 8 bits, as in old Perl. I have now made octal escapes with
1861        values greater than \377 illegal in non-UTF-8 mode. In UTF-8 mode they
1862        translate to the appropriate multibyte character.
1864    29. Applied some refactoring to reduce the number of warnings from Microsoft
1865        and Borland compilers. This has included removing the fudge introduced
1866        seven years ago for the OS/2 compiler (see 2.02/2 below) because it caused
1867        a warning about an unused variable.
1869    21. PCRE has not included VT (character 0x0b) in the set of whitespace
1870        characters since release 4.0, because Perl (from release 5.004) does not.
1871        [Or at least, is documented not to: some releases seem to be in conflict
1872        with the documentation.] However, when a pattern was studied with
1873        pcre_study() and all its branches started with \s, PCRE still included VT
1874        as a possible starting character. Of course, this did no harm; it just
1875        caused an unnecessary match attempt.
1877    22. Removed a now-redundant internal flag bit that recorded the fact that case
1878        dependency changed within the pattern. This was once needed for "required
1879        byte" processing, but is no longer used. This recovers a now-scarce options
1880        bit. Also moved the least significant internal flag bit to the most-
1881        significant bit of the word, which was not previously used (hangover from
1882        the days when it was an int rather than a uint) to free up another bit for
1883        the future.
1885    23. Added support for CRLF line endings as well as CR and LF. As well as the
1886        default being selectable at build time, it can now be changed at runtime
1887        via the PCRE_NEWLINE_xxx flags. There are now options for pcregrep to
1888        specify that it is scanning data with non-default line endings.
1890    24. Changed the definition of CXXLINK to make it agree with the definition of
1891        LINK in the Makefile, by replacing LDFLAGS to CXXFLAGS.
1893    25. Applied Ian Taylor's patches to avoid using another stack frame for tail
1894        recursions. This makes a big different to stack usage for some patterns.
1896    26. If a subpattern containing a named recursion or subroutine reference such
1897        as (?P>B) was quantified, for example (xxx(?P>B)){3}, the calculation of
1898        the space required for the compiled pattern went wrong and gave too small a
1899        value. Depending on the environment, this could lead to "Failed: internal
1900        error: code overflow at offset 49" or "glibc detected double free or
1901        corruption" errors.
1903    27. Applied patches from Google (a) to support the new newline modes and (b) to
1904        advance over multibyte UTF-8 characters in GlobalReplace.
1906    28. Change free() to pcre_free() in pcredemo.c. Apparently this makes a
1907        difference for some implementation of PCRE in some Windows version.
1909    29. Added some extra testing facilities to pcretest:
1911        \q<number>   in a data line sets the "match limit" value
1912        \Q<number>   in a data line sets the "match recursion limt" value
1913        -S <number>  sets the stack size, where <number> is in megabytes
1915        The -S option isn't available for Windows.
1918    Version 6.6 06-Feb-06
1919    ---------------------
1921     1. Change 16(a) for 6.5 broke things, because PCRE_DATA_SCOPE was not defined
1922        in pcreposix.h. I have copied the definition from pcre.h.
1924     2. Change 25 for 6.5 broke compilation in a build directory out-of-tree
1925        because pcre.h is no longer a built file.
1927     3. Added Jeff Friedl's additional debugging patches to pcregrep. These are
1928        not normally included in the compiled code.
1931    Version 6.5 01-Feb-06
1932    ---------------------
1934     1. When using the partial match feature with pcre_dfa_exec(), it was not
1935        anchoring the second and subsequent partial matches at the new starting
1936        point. This could lead to incorrect results. For example, with the pattern
1937        /1234/, partially matching against "123" and then "a4" gave a match.
1939     2. Changes to pcregrep:
1941        (a) All non-match returns from pcre_exec() were being treated as failures
1942            to match the line. Now, unless the error is PCRE_ERROR_NOMATCH, an
1943            error message is output. Some extra information is given for the
1944            PCRE_ERROR_MATCHLIMIT and PCRE_ERROR_RECURSIONLIMIT errors, which are
1945            probably the only errors that are likely to be caused by users (by
1946            specifying a regex that has nested indefinite repeats, for instance).
1947            If there are more than 20 of these errors, pcregrep is abandoned.
1949        (b) A binary zero was treated as data while matching, but terminated the
1950            output line if it was written out. This has been fixed: binary zeroes
1951            are now no different to any other data bytes.
1953        (c) Whichever of the LC_ALL or LC_CTYPE environment variables is set is
1954            used to set a locale for matching. The --locale=xxxx long option has
1955            been added (no short equivalent) to specify a locale explicitly on the
1956            pcregrep command, overriding the environment variables.
1958        (d) When -B was used with -n, some line numbers in the output were one less
1959            than they should have been.
1961        (e) Added the -o (--only-matching) option.
1963        (f) If -A or -C was used with -c (count only), some lines of context were
1964            accidentally printed for the final match.
1966        (g) Added the -H (--with-filename) option.
1968        (h) The combination of options -rh failed to suppress file names for files
1969            that were found from directory arguments.
1971        (i) Added the -D (--devices) and -d (--directories) options.
1973        (j) Added the -F (--fixed-strings) option.
1975        (k) Allow "-" to be used as a file name for -f as well as for a data file.
1977        (l) Added the --colo(u)r option.
1979        (m) Added Jeffrey Friedl's -S testing option, but within #ifdefs so that it
1980            is not present by default.
1982     3. A nasty bug was discovered in the handling of recursive patterns, that is,
1983        items such as (?R) or (?1), when the recursion could match a number of
1984        alternatives. If it matched one of the alternatives, but subsequently,
1985        outside the recursion, there was a failure, the code tried to back up into
1986        the recursion. However, because of the way PCRE is implemented, this is not
1987        possible, and the result was an incorrect result from the match.
1989        In order to prevent this happening, the specification of recursion has
1990        been changed so that all such subpatterns are automatically treated as
1991        atomic groups. Thus, for example, (?R) is treated as if it were (?>(?R)).
1993     4. I had overlooked the fact that, in some locales, there are characters for
1994        which isalpha() is true but neither isupper() nor islower() are true. In
1995        the fr_FR locale, for instance, the \xAA and \xBA characters (ordmasculine
1996        and ordfeminine) are like this. This affected the treatment of \w and \W
1997        when they appeared in character classes, but not when they appeared outside
1998        a character class. The bit map for "word" characters is now created
1999        separately from the results of isalnum() instead of just taking it from the
2000        upper, lower, and digit maps. (Plus the underscore character, of course.)
2002     5. The above bug also affected the handling of POSIX character classes such as
2003        [[:alpha:]] and [[:alnum:]]. These do not have their own bit maps in PCRE's
2004        permanent tables. Instead, the bit maps for such a class were previously
2005        created as the appropriate unions of the upper, lower, and digit bitmaps.
2006        Now they are created by subtraction from the [[:word:]] class, which has
2007        its own bitmap.
2009     6. The [[:blank:]] character class matches horizontal, but not vertical space.
2010        It is created by subtracting the vertical space characters (\x09, \x0a,
2011        \x0b, \x0c) from the [[:space:]] bitmap. Previously, however, the
2012        subtraction was done in the overall bitmap for a character class, meaning
2013        that a class such as [\x0c[:blank:]] was incorrect because \x0c would not
2014        be recognized. This bug has been fixed.
2016     7. Patches from the folks at Google:
2018          (a) pcrecpp.cc: "to handle a corner case that may or may not happen in
2019          real life, but is still worth protecting against".
2021          (b) pcrecpp.cc: "corrects a bug when negative radixes are used with
2022          regular expressions".
2024          (c) pcre_scanner.cc: avoid use of std::count() because not all systems
2025          have it.
2027          (d) Split off pcrecpparg.h from pcrecpp.h and had the former built by
2028          "configure" and the latter not, in order to fix a problem somebody had
2029          with compiling the Arg class on HP-UX.
2031          (e) Improve the error-handling of the C++ wrapper a little bit.
2033          (f) New tests for checking recursion limiting.
2035     8. The pcre_memmove() function, which is used only if the environment does not
2036        have a standard memmove() function (and is therefore rarely compiled),
2037        contained two bugs: (a) use of int instead of size_t, and (b) it was not
2038        returning a result (though PCRE never actually uses the result).
2040     9. In the POSIX regexec() interface, if nmatch is specified as a ridiculously
2041        large number - greater than INT_MAX/(3*sizeof(int)) - REG_ESPACE is
2042        returned instead of calling malloc() with an overflowing number that would
2043        most likely cause subsequent chaos.
2045    10. The debugging option of pcretest was not showing the NO_AUTO_CAPTURE flag.
2047    11. The POSIX flag REG_NOSUB is now supported. When a pattern that was compiled
2048        with this option is matched, the nmatch and pmatch options of regexec() are
2049        ignored.
2051    12. Added REG_UTF8 to the POSIX interface. This is not defined by POSIX, but is
2052        provided in case anyone wants to the the POSIX interface with UTF-8
2053        strings.
2055    13. Added CXXLDFLAGS to the Makefile parameters to provide settings only on the
2056        C++ linking (needed for some HP-UX environments).
2058    14. Avoid compiler warnings in get_ucpname() when compiled without UCP support
2059        (unused parameter) and in the pcre_printint() function (omitted "default"
2060        switch label when the default is to do nothing).
2062    15. Added some code to make it possible, when PCRE is compiled as a C++
2063        library, to replace subject pointers for pcre_exec() with a smart pointer
2064        class, thus making it possible to process discontinuous strings.
2066    16. The two macros PCRE_EXPORT and PCRE_DATA_SCOPE are confusing, and perform
2067        much the same function. They were added by different people who were trying
2068        to make PCRE easy to compile on non-Unix systems. It has been suggested
2069        that PCRE_EXPORT be abolished now that there is more automatic apparatus
2070        for compiling on Windows systems. I have therefore replaced it with
2071        PCRE_DATA_SCOPE. This is set automatically for Windows; if not set it
2072        defaults to "extern" for C or "extern C" for C++, which works fine on
2073        Unix-like systems. It is now possible to override the value of PCRE_DATA_
2074        SCOPE with something explicit in config.h. In addition:
2076        (a) pcreposix.h still had just "extern" instead of either of these macros;
2077            I have replaced it with PCRE_DATA_SCOPE.
2079        (b) Functions such as _pcre_xclass(), which are internal to the library,
2080            but external in the C sense, all had PCRE_EXPORT in their definitions.
2081            This is apparently wrong for the Windows case, so I have removed it.
2082            (It makes no difference on Unix-like systems.)
2084    17. Added a new limit, MATCH_LIMIT_RECURSION, which limits the depth of nesting
2085        of recursive calls to match(). This is different to MATCH_LIMIT because
2086        that limits the total number of calls to match(), not all of which increase
2087        the depth of recursion. Limiting the recursion depth limits the amount of
2088        stack (or heap if NO_RECURSE is set) that is used. The default can be set
2089        when PCRE is compiled, and changed at run time. A patch from Google adds
2090        this functionality to the C++ interface.
2092    18. Changes to the handling of Unicode character properties:
2094        (a) Updated the table to Unicode 4.1.0.
2096        (b) Recognize characters that are not in the table as "Cn" (undefined).
2098        (c) I revised the way the table is implemented to a much improved format
2099            which includes recognition of ranges. It now supports the ranges that
2100            are defined in UnicodeData.txt, and it also amalgamates other
2101            characters into ranges. This has reduced the number of entries in the
2102            table from around 16,000 to around 3,000, thus reducing its size
2103            considerably. I realized I did not need to use a tree structure after
2104            all - a binary chop search is just as efficient. Having reduced the
2105            number of entries, I extended their size from 6 bytes to 8 bytes to
2106            allow for more data.
2108        (d) Added support for Unicode script names via properties such as \p{Han}.
2110    19. In UTF-8 mode, a backslash followed by a non-Ascii character was not
2111        matching that character.
2113    20. When matching a repeated Unicode property with a minimum greater than zero,
2114        (for example \pL{2,}), PCRE could look past the end of the subject if it
2115        reached it while seeking the minimum number of characters. This could
2116        happen only if some of the characters were more than one byte long, because
2117        there is a check for at least the minimum number of bytes.
2119    21. Refactored the implementation of \p and \P so as to be more general, to
2120        allow for more different types of property in future. This has changed the
2121        compiled form incompatibly. Anybody with saved compiled patterns that use
2122        \p or \P will have to recompile them.
2124    22. Added "Any" and "L&" to the supported property types.
2126    23. Recognize \x{...} as a code point specifier, even when not in UTF-8 mode,
2127        but give a compile time error if the value is greater than 0xff.
2129    24. The man pages for pcrepartial, pcreprecompile, and pcre_compile2 were
2130        accidentally not being installed or uninstalled.
2132    25. The pcre.h file was built from pcre.h.in, but the only changes that were
2133        made were to insert the current release number. This seemed silly, because
2134        it made things harder for people building PCRE on systems that don't run
2135        "configure". I have turned pcre.h into a distributed file, no longer built
2136        by "configure", with the version identification directly included. There is
2137        no longer a pcre.h.in file.
2139        However, this change necessitated a change to the pcre-config script as
2140        well. It is built from pcre-config.in, and one of the substitutions was the
2141        release number. I have updated configure.ac so that ./configure now finds
2142        the release number by grepping pcre.h.
2144    26. Added the ability to run the tests under valgrind.
2147  Version 6.4 05-Sep-05  Version 6.4 05-Sep-05
2148  ---------------------  ---------------------

Removed from v.85  
changed lines
  Added in v.564

  ViewVC Help
Powered by ViewVC 1.1.5