ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 181 by ph10, Wed Jun 13 14:55:18 2007 UTC revision 528 by ph10, Sat May 29 16:40:22 2010 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 7.2 13-June-07  Version 8.10 03 May-2010
5    ------------------------
7    1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and
8        THEN.
10    2.  (*ACCEPT) was not working when inside an atomic group.
12    3.  Inside a character class, \B is treated as a literal by default, but
13        faulted if PCRE_EXTRA is set. This mimics Perl's behaviour (the -w option
14        causes the error). The code is unchanged, but I tidied the documentation.
16    4.  Inside a character class, PCRE always treated \R and \X as literals,
17        whereas Perl faults them if its -w option is set. I have changed PCRE so
18        that it faults them when PCRE_EXTRA is set.
20    5.  Added support for \N, which always matches any character other than
21        newline. (It is the same as "." when PCRE_DOTALL is not set.)
23    6.  When compiling pcregrep with newer versions of gcc which may have
24        FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',
25        declared with attribute warn_unused_result" were given. Just casting the
26        result to (void) does not stop the warnings; a more elaborate fudge is
27        needed. I've used a macro to implement this.
29    7.  Minor change to pcretest.c to avoid a compiler warning.
31    8.  Added four artifical Unicode properties to help with an option to make
32        \s etc use properties (see next item). The new properties are: Xan
33        (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).
35    9.  Added PCRE_UCP to make \b, \d, \s, \w, and certain POSIX character classes
36        use Unicode properties. (*UCP) at the start of a pattern can be used to set
37        this option. Modified pcretest to add /W to test this facility. Added
38        REG_UCP to make it available via the POSIX interface.
40    10. Added --line-buffered to pcregrep.
42    11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was
43        studied, and the match started with a letter with a code point greater than
44        127 whose first byte was different to the first byte of the other case of
45        the letter, the other case of this starting letter was not recognized.
47    12. pcreposix.c included pcre.h before including pcre_internal.h. This caused a
48        conflict in the definition of PCRE_EXP_DECL. I have removed the include of
49        pcre.h as pcre_internal.h includes pcre.h itself. (This may be a bit of
50        historical tidying that never got done.)
52    13. If a pattern that was studied started with a repeated Unicode property
53        test, for example, \p{Nd}+, there was the theoretical possibility of
54        setting up an incorrect bitmap of starting bytes, but fortunately it could
55        not have actually happened in practice until change 8 above was made (it
56        added property types that matched character-matching opcodes).
58    14. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
59        possible starting bytes for non-anchored patterns.
61    15. The "auto-possessify" feature of pcre_compile() now recognizes \R.
65    Version 8.02 19-Mar-2010
66    ------------------------
68    1.  The Unicode data tables have been updated to Unicode 5.2.0.
70    2.  Added the option --libs-cpp to pcre-config, but only when C++ support is
71        configured.
73    3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the
74        original author of that file, following a query about its status.
76    4.  On systems that do not have stdint.h (e.g. Solaris), check for and include
77        inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
79    5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
80        quantifier applied to a forward-referencing subroutine call, could compile
81        incorrect code or give the error "internal error: previously-checked
82        referenced subpattern not found".
84    6.  Both MS Visual Studio and Symbian OS have problems with initializing
85        variables to point to external functions. For these systems, therefore,
86        pcre_malloc etc. are now initialized to local functions that call the
87        relevant global functions.
89    7.  There were two entries missing in the vectors called coptable and poptable
90        in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.
91        I've fixed the data, and added a kludgy way of testing at compile time that
92        the lengths are correct (equal to the number of opcodes).
94    8.  Following on from 7, I added a similar kludge to check the length of the
95        eint vector in pcreposix.c.
97    9.  Error texts for pcre_compile() are held as one long string to avoid too
98        much relocation at load time. To find a text, the string is searched,
99        counting zeros. There was no check for running off the end of the string,
100        which could happen if a new error number was added without updating the
101        string.
103    10. \K gave a compile-time error if it appeared in a lookbehind assersion.
105    11. \K was not working if it appeared in an atomic group or in a group that
106        was called as a "subroutine", or in an assertion. Perl 5.11 documents that
107        \K is "not well defined" if used in an assertion. PCRE now accepts it if
108        the assertion is positive, but not if it is negative.
110    12. Change 11 fortuitously reduced the size of the stack frame used in the
111        "match()" function of pcre_exec.c by one pointer. Forthcoming
112        implementation of support for (*MARK) will need an extra pointer on the
113        stack; I have reserved it now, so that the stack frame size does not
114        decrease.
116    13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other
117        item in branch that calls a recursion is a subroutine call - as in the
118        second branch in the above example - was incorrectly given the compile-
119        time error "recursive call could loop indefinitely" because pcre_compile()
120        was not correctly checking the subroutine for matching a non-empty string.
122    14. The checks for overrunning compiling workspace could trigger after an
123        overrun had occurred. This is a "should never occur" error, but it can be
124        triggered by pathological patterns such as hundreds of nested parentheses.
125        The checks now trigger 100 bytes before the end of the workspace.
127    15. Fix typo in configure.ac: "srtoq" should be "strtoq".
130    Version 8.01 19-Jan-2010
131    ------------------------
133    1.  If a pattern contained a conditional subpattern with only one branch (in
134        particular, this includes all (*DEFINE) patterns), a call to pcre_study()
135        computed the wrong minimum data length (which is of course zero for such
136        subpatterns). This could cause incorrect "no match" results.
138    2.  For patterns such as (?i)a(?-i)b|c where an option setting at the start of
139        the pattern is reset in the first branch, pcre_compile() failed with
140        "internal error: code overflow at offset...". This happened only when
141        the reset was to the original external option setting. (An optimization
142        abstracts leading options settings into an external setting, which was the
143        cause of this.)
145    3.  A pattern such as ^(?!a(*SKIP)b) where a negative assertion contained one
146        of the verbs SKIP, PRUNE, or COMMIT, did not work correctly. When the
147        assertion pattern did not match (meaning that the assertion was true), it
148        was incorrectly treated as false if the SKIP had been reached during the
149        matching. This also applied to assertions used as conditions.
151    4.  If an item that is not supported by pcre_dfa_exec() was encountered in an
152        assertion subpattern, including such a pattern used as a condition,
153        unpredictable results occurred, instead of the error return
156    5.  The C++ GlobalReplace function was not working like Perl for the special
157        situation when an empty string is matched. It now does the fancy magic
158        stuff that is necessary.
160    6.  In pcre_internal.h, obsolete includes to setjmp.h and stdarg.h have been
161        removed. (These were left over from very, very early versions of PCRE.)
163    7.  Some cosmetic changes to the code to make life easier when compiling it
164        as part of something else:
166        (a) Change DEBUG to PCRE_DEBUG.
168        (b) In pcre_compile(), rename the member of the "branch_chain" structure
169            called "current" as "current_branch", to prevent a collision with the
170            Linux macro when compiled as a kernel module.
172        (c) In pcre_study(), rename the function set_bit() as set_table_bit(), to
173            prevent a collision with the Linux macro when compiled as a kernel
174            module.
176    8.  In pcre_compile() there are some checks for integer overflows that used to
177        cast potentially large values to (double). This has been changed to that
178        when building, a check for int64_t is made, and if it is found, it is used
179        instead, thus avoiding the use of floating point arithmetic. (There is no
180        other use of FP in PCRE.) If int64_t is not found, the fallback is to
181        double.
183    9.  Added two casts to avoid signed/unsigned warnings from VS Studio Express
184        2005 (difference between two addresses compared to an unsigned value).
186    10. Change the standard AC_CHECK_LIB test for libbz2 in configure.ac to a
187        custom one, because of the following reported problem in Windows:
189          - libbz2 uses the Pascal calling convention (WINAPI) for the functions
190              under Win32.
191          - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",
192              therefore missing the function definition.
193          - The compiler thus generates a "C" signature for the test function.
194          - The linker fails to find the "C" function.
195          - PCRE fails to configure if asked to do so against libbz2.
197    11. When running libtoolize from libtool-2.2.6b as part of autogen.sh, these
198        messages were output:
200          Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
201          rerunning libtoolize, to keep the correct libtool macros in-tree.
202          Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
204        I have done both of these things.
206    12. Although pcre_dfa_exec() does not use nearly as much stack as pcre_exec()
207        most of the time, it *can* run out if it is given a pattern that contains a
208        runaway infinite recursion. I updated the discussion in the pcrestack man
209        page.
211    13. Now that we have gone to the x.xx style of version numbers, the minor
212        version may start with zero. Using 08 or 09 is a bad idea because users
213        might check the value of PCRE_MINOR in their code, and 08 or 09 may be
214        interpreted as invalid octal numbers. I've updated the previous comment in
215        configure.ac, and also added a check that gives an error if 08 or 09 are
216        used.
218    14. Change 8.00/11 was not quite complete: code had been accidentally omitted,
219        causing partial matching to fail when the end of the subject matched \W
220        in a UTF-8 pattern where \W was quantified with a minimum of 3.
222    15. There were some discrepancies between the declarations in pcre_internal.h
223        of _pcre_is_newline(), _pcre_was_newline(), and _pcre_valid_utf8() and
224        their definitions. The declarations used "const uschar *" and the
225        definitions used USPTR. Even though USPTR is normally defined as "const
226        unsigned char *" (and uschar is typedeffed as "unsigned char"), it was
227        reported that: "This difference in casting confuses some C++ compilers, for
228        example, SunCC recognizes above declarations as different functions and
229        generates broken code for hbpcre." I have changed the declarations to use
230        USPTR.
232    16. GNU libtool is named differently on some systems. The autogen.sh script now
233        tries several variants such as glibtoolize (MacOSX) and libtoolize1x
234        (FreeBSD).
236    17. Applied Craig's patch that fixes an HP aCC compile error in pcre 8.00
237        (strtoXX undefined when compiling pcrecpp.cc). The patch contains this
238        comment: "Figure out how to create a longlong from a string: strtoll and
239        equivalent. It's not enough to call AC_CHECK_FUNCS: hpux has a strtoll, for
240        instance, but it only takes 2 args instead of 3!"
242    18. A subtle bug concerned with back references has been fixed by a change of
243        specification, with a corresponding code fix. A pattern such as
244        ^(xa|=?\1a)+$ which contains a back reference inside the group to which it
245        refers, was giving matches when it shouldn't. For example, xa=xaaa would
246        match that pattern. Interestingly, Perl (at least up to 5.11.3) has the
247        same bug. Such groups have to be quantified to be useful, or contained
248        inside another quantified group. (If there's no repetition, the reference
249        can never match.) The problem arises because, having left the group and
250        moved on to the rest of the pattern, a later failure that backtracks into
251        the group uses the captured value from the final iteration of the group
252        rather than the correct earlier one. I have fixed this in PCRE by forcing
253        any group that contains a reference to itself to be an atomic group; that
254        is, there cannot be any backtracking into it once it has completed. This is
255        similar to recursive and subroutine calls.
258    Version 8.00 19-Oct-09
259    ----------------------
261    1.  The table for translating pcre_compile() error codes into POSIX error codes
262        was out-of-date, and there was no check on the pcre_compile() error code
263        being within the table. This could lead to an OK return being given in
264        error.
266    2.  Changed the call to open a subject file in pcregrep from fopen(pathname,
267        "r") to fopen(pathname, "rb"), which fixed a problem with some of the tests
268        in a Windows environment.
270    3.  The pcregrep --count option prints the count for each file even when it is
271        zero, as does GNU grep. However, pcregrep was also printing all files when
272        --files-with-matches was added. Now, when both options are given, it prints
273        counts only for those files that have at least one match. (GNU grep just
274        prints the file name in this circumstance, but including the count seems
275        more useful - otherwise, why use --count?) Also ensured that the
276        combination -clh just lists non-zero counts, with no names.
278    4.  The long form of the pcregrep -F option was incorrectly implemented as
279        --fixed_strings instead of --fixed-strings. This is an incompatible change,
280        but it seems right to fix it, and I didn't think it was worth preserving
281        the old behaviour.
283    5.  The command line items --regex=pattern and --regexp=pattern were not
284        recognized by pcregrep, which required --regex pattern or --regexp pattern
285        (with a space rather than an '='). The man page documented the '=' forms,
286        which are compatible with GNU grep; these now work.
288    6.  No libpcreposix.pc file was created for pkg-config; there was just
289        libpcre.pc and libpcrecpp.pc. The omission has been rectified.
291    7.  Added #ifndef SUPPORT_UCP into the pcre_ucd.c module, to reduce its size
292        when UCP support is not needed, by modifying the Python script that
293        generates it from Unicode data files. This should not matter if the module
294        is correctly used as a library, but I received one complaint about 50K of
295        unwanted data. My guess is that the person linked everything into his
296        program rather than using a library. Anyway, it does no harm.
298    8.  A pattern such as /\x{123}{2,2}+/8 was incorrectly compiled; the trigger
299        was a minimum greater than 1 for a wide character in a possessive
300        repetition. The same bug could also affect patterns like /(\x{ff}{0,2})*/8
301        which had an unlimited repeat of a nested, fixed maximum repeat of a wide
302        character. Chaos in the form of incorrect output or a compiling loop could
303        result.
305    9.  The restrictions on what a pattern can contain when partial matching is
306        requested for pcre_exec() have been removed. All patterns can now be
307        partially matched by this function. In addition, if there are at least two
308        slots in the offset vector, the offset of the earliest inspected character
309        for the match and the offset of the end of the subject are set in them when
310        PCRE_ERROR_PARTIAL is returned.
312    10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is
313        synonymous with PCRE_PARTIAL, for backwards compatibility, and
314        PCRE_PARTIAL_HARD, which causes a partial match to supersede a full match,
315        and may be more useful for multi-segment matching.
317    11. Partial matching with pcre_exec() is now more intuitive. A partial match
318        used to be given if ever the end of the subject was reached; now it is
319        given only if matching could not proceed because another character was
320        needed. This makes a difference in some odd cases such as Z(*FAIL) with the
321        string "Z", which now yields "no match" instead of "partial match". In the
322        case of pcre_dfa_exec(), "no match" is given if every matching path for the
323        final character ended with (*FAIL).
325    12. Restarting a match using pcre_dfa_exec() after a partial match did not work
326        if the pattern had a "must contain" character that was already found in the
327        earlier partial match, unless partial matching was again requested. For
328        example, with the pattern /dog.(body)?/, the "must contain" character is
329        "g". If the first part-match was for the string "dog", restarting with
330        "sbody" failed. This bug has been fixed.
332    13. The string returned by pcre_dfa_exec() after a partial match has been
333        changed so that it starts at the first inspected character rather than the
334        first character of the match. This makes a difference only if the pattern
335        starts with a lookbehind assertion or \b or \B (\K is not supported by
336        pcre_dfa_exec()). It's an incompatible change, but it makes the two
337        matching functions compatible, and I think it's the right thing to do.
339    14. Added a pcredemo man page, created automatically from the pcredemo.c file,
340        so that the demonstration program is easily available in environments where
341        PCRE has not been installed from source.
343    15. Arranged to add -DPCRE_STATIC to cflags in libpcre.pc, libpcreposix.cp,
344        libpcrecpp.pc and pcre-config when PCRE is not compiled as a shared
345        library.
347    16. Added REG_UNGREEDY to the pcreposix interface, at the request of a user.
348        It maps to PCRE_UNGREEDY. It is not, of course, POSIX-compatible, but it
349        is not the first non-POSIX option to be added. Clearly some people find
350        these options useful.
352    17. If a caller to the POSIX matching function regexec() passes a non-zero
353        value for nmatch with a NULL value for pmatch, the value of
354        nmatch is forced to zero.
356    18. RunGrepTest did not have a test for the availability of the -u option of
357        the diff command, as RunTest does. It now checks in the same way as
358        RunTest, and also checks for the -b option.
360    19. If an odd number of negated classes containing just a single character
361        interposed, within parentheses, between a forward reference to a named
362        subpattern and the definition of the subpattern, compilation crashed with
363        an internal error, complaining that it could not find the referenced
364        subpattern. An example of a crashing pattern is /(?&A)(([^m])(?<A>))/.
365        [The bug was that it was starting one character too far in when skipping
366        over the character class, thus treating the ] as data rather than
367        terminating the class. This meant it could skip too much.]
369    20. Added PCRE_NOTEMPTY_ATSTART in order to be able to correctly implement the
370        /g option in pcretest when the pattern contains \K, which makes it possible
371        to have an empty string match not at the start, even when the pattern is
372        anchored. Updated pcretest and pcredemo to use this option.
374    21. If the maximum number of capturing subpatterns in a recursion was greater
375        than the maximum at the outer level, the higher number was returned, but
376        with unset values at the outer level. The correct (outer level) value is
377        now given.
379    22. If (*ACCEPT) appeared inside capturing parentheses, previous releases of
380        PCRE did not set those parentheses (unlike Perl). I have now found a way to
381        make it do so. The string so far is captured, making this feature
382        compatible with Perl.
384    23. The tests have been re-organized, adding tests 11 and 12, to make it
385        possible to check the Perl 5.10 features against Perl 5.10.
387    24. Perl 5.10 allows subroutine calls in lookbehinds, as long as the subroutine
388        pattern matches a fixed length string. PCRE did not allow this; now it
389        does. Neither allows recursion.
391    25. I finally figured out how to implement a request to provide the minimum
392        length of subject string that was needed in order to match a given pattern.
393        (It was back references and recursion that I had previously got hung up
394        on.) This code has now been added to pcre_study(); it finds a lower bound
395        to the length of subject needed. It is not necessarily the greatest lower
396        bound, but using it to avoid searching strings that are too short does give
397        some useful speed-ups. The value is available to calling programs via
398        pcre_fullinfo().
400    26. While implementing 25, I discovered to my embarrassment that pcretest had
401        not been passing the result of pcre_study() to pcre_dfa_exec(), so the
402        study optimizations had never been tested with that matching function.
403        Oops. What is worse, even when it was passed study data, there was a bug in
404        pcre_dfa_exec() that meant it never actually used it. Double oops. There
405        were also very few tests of studied patterns with pcre_dfa_exec().
407    27. If (?| is used to create subpatterns with duplicate numbers, they are now
408        allowed to have the same name, even if PCRE_DUPNAMES is not set. However,
409        on the other side of the coin, they are no longer allowed to have different
410        names, because these cannot be distinguished in PCRE, and this has caused
411        confusion. (This is a difference from Perl.)
413    28. When duplicate subpattern names are present (necessarily with different
414        numbers, as required by 27 above), and a test is made by name in a
415        conditional pattern, either for a subpattern having been matched, or for
416        recursion in such a pattern, all the associated numbered subpatterns are
417        tested, and the overall condition is true if the condition is true for any
418        one of them. This is the way Perl works, and is also more like the way
419        testing by number works.
422    Version 7.9 11-Apr-09
423    ---------------------
425    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
426        (pcretest), all targets were linked against these libraries. This included
427        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
428        libraries. This caused unwanted dependencies to be created. This problem
429        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
430        pcretest is linked with readline.
432    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
433        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
434        moved outside it again, because FALSE and TRUE are already defined in AIX,
435        but BOOL is not.
437    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
438        PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
440    4.  The pcregrep documentation said spaces were inserted as well as colons (or
441        hyphens) following file names and line numbers when outputting matching
442        lines. This is not true; no spaces are inserted. I have also clarified the
443        wording for the --colour (or --color) option.
445    5.  In pcregrep, when --colour was used with -o, the list of matching strings
446        was not coloured; this is different to GNU grep, so I have changed it to be
447        the same.
449    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
450        each matching line was coloured. Now it goes on to look for further matches
451        of any of the test patterns, which is the same behaviour as GNU grep.
453    7.  A pattern that could match an empty string could cause pcregrep to loop; it
454        doesn't make sense to accept an empty string match in pcregrep, so I have
455        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
456        seems to be how GNU grep behaves.
458    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
459        start or after a newline", because the conditional assertion was not being
460        correctly handled. The rule now is that both the assertion and what follows
461        in the first alternative must satisfy the test.
463    9.  If auto-callout was enabled in a pattern with a conditional group whose
464        condition was an assertion, PCRE could crash during matching, both with
465        pcre_exec() and pcre_dfa_exec().
467    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
468        used for matching.
470    11. Unicode property support in character classes was not working for
471        characters (bytes) greater than 127 when not in UTF-8 mode.
473    12. Added the -M command line option to pcretest.
475    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
477    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
479    16. Added comments and documentation about mis-use of no_arg in the C++
480        wrapper.
482    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
483        from Martin Jerabek that uses macro names for all relevant character and
484        string constants.
486    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
487        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
488        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
489        these, but not everybody uses configure.
491    19. A conditional group that had only one branch was not being correctly
492        recognized as an item that could match an empty string. This meant that an
493        enclosing group might also not be so recognized, causing infinite looping
494        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
495        with the subject "ab", where knowledge that the repeated group can match
496        nothing is needed in order to break the loop.
498    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
499        exec(), but without supplying a callout function, matching went wrong.
501    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
502        leak if the size of the offset vector was greater than 30. When the vector
503        is smaller, the saved offsets during recursion go onto a local stack
504        vector, but for larger vectors malloc() is used. It was failing to free
505        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
506        error, in fact).
508    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
509        heapframe that is used only when UTF-8 support is enabled. This caused no
510        problem, but was untidy.
512    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
513        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
514        included within another project.
516    24. Steven Van Ingelgem's patches to add more options to the CMake support,
517        slightly modified by me:
519          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
520              not building pcregrep.
522          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
523              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
525    25. Forward references, both numeric and by name, in patterns that made use of
526        duplicate group numbers, could behave incorrectly or give incorrect errors,
527        because when scanning forward to find the reference group, PCRE was not
528        taking into account the duplicate group numbers. A pattern such as
529        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
531    26. Changed a few more instances of "const unsigned char *" to USPTR, making
532        the feature of a custom pointer more persuasive (as requested by a user).
534    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
535        pcretest.c, inside #ifndefs, because it seems they are sometimes already
536        pre-defined.
538    28. Added support for (*UTF8) at the start of a pattern.
540    29. Arrange for flags added by the "release type" setting in CMake to be shown
541        in the configuration summary.
544    Version 7.8 05-Sep-08
545    ---------------------
547    1.  Replaced UCP searching code with optimized version as implemented for Ad
548        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
549        stage table and inline lookup instead of a function, giving speed ups of 2
550        to 5 times on some simple patterns that I tested. Permission was given to
551        distribute the MultiStage2.py script that generates the tables (it's not in
552        the tarball, but is in the Subversion repository).
554    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
555        scripts.
557    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
558        a group with a zero qualifier. The result of the study could be incorrect,
559        or the function might crash, depending on the pattern.
561    4.  Caseless matching was not working for non-ASCII characters in back
562        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
563        It now works when Unicode Property Support is available.
565    5.  In pcretest, an escape such as \x{de} in the data was always generating
566        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
567        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
568        truncation.
570    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
572    7.  Added two (int) casts to pcregrep when printing the difference of two
573        pointers, in case they are 64-bit values.
575    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
576        test 2 if it fails.
578    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
579        and a #define of that name to empty if it is not externally set. This is to
580        allow users of MSVC to set it if necessary.
582    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
583        the convenience functions in the pcre_get.c source file.
585    11. An option change at the start of a pattern that had top-level alternatives
586        could cause overwriting and/or a crash. This command provoked a crash in
587        some environments:
589          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
591        This potential security problem was recorded as CVE-2008-2371.
593    12. For a pattern where the match had to start at the beginning or immediately
594        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
595        pcre_dfa_exec() could read past the end of the passed subject if there was
596        no match. To help with detecting such bugs (e.g. with valgrind), I modified
597        pcretest so that it places the subject at the end of its malloc-ed buffer.
599    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
600        exec() might read past the end of the data buffer in UTF-8 mode.
602    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
603        the data contained the byte 0x85 as part of a UTF-8 character within its
604        first line. This applied both to normal and DFA matching.
606    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
607        /^[^d]*?$/8 failed to match "abc".
609    16. Added a missing copyright notice to pcrecpp_internal.h.
611    17. Make it more clear in the documentation that values returned from
612        pcre_exec() in ovector are byte offsets, not character counts.
614    18. Tidied a few places to stop certain compilers from issuing warnings.
616    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
617        supplied by Stefan Weber. I made a further small update for 7.8 because
618        there is a change of source arrangements: the pcre_searchfuncs.c module is
619        replaced by pcre_ucd.c.
622    Version 7.7 07-May-08
623    ---------------------
625    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
626        a string to a long long, pretend we don't even have a long long." This is
627        done by checking for the strtoq, strtoll, and _strtoi64 functions.
629    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
630        pre-7.6 versions, which defined a global no_arg variable instead of putting
631        it in the RE class. (See also #8 below.)
633    3.  Remove a line of dead code, identified by coverity and reported by Nuno
634        Lopes.
636    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
638        (1) The include/exclude patterns were being applied to the whole pathnames
639            of files, instead of just to the final components.
641        (2) If there was more than one level of directory, the subdirectories were
642            skipped unless they satisfied the include/exclude conditions. This is
643            inconsistent with GNU grep (and could even be seen as contrary to the
644            pcregrep specification - which I improved to make it absolutely clear).
645            The action now is always to scan all levels of directory, and just
646            apply the include/exclude patterns to regular files.
648    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
649        --exclude_dir in the tests to avoid scanning .svn directories.
651    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
652        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
653        doesn't support NULs in patterns.
655    7.  Added some missing "const"s to declarations of static tables in
656        pcre_compile.c and pcre_dfa_exec.c.
658    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
659        caused by fix #2  above. (Subsequently also a second patch to fix the
660        first patch. And a third patch - this was a messy problem.)
662    9.  Applied Craig's patch to remove the use of push_back().
664    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
665        matching function regexec().
667    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
668        which, however, unlike Perl's \g{...}, are subroutine calls, not back
669        references. PCRE supports relative numbers with this syntax (I don't think
670        Oniguruma does).
672    12. Previously, a group with a zero repeat such as (...){0} was completely
673        omitted from the compiled regex. However, this means that if the group
674        was called as a subroutine from elsewhere in the pattern, things went wrong
675        (an internal error was given). Such groups are now left in the compiled
676        pattern, with a new opcode that causes them to be skipped at execution
677        time.
679    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
680        to the way PCRE behaves:
682        (a) A lone ] character is dis-allowed (Perl treats it as data).
684        (b) A back reference to an unmatched subpattern matches an empty string
685            (Perl fails the current match path).
687        (c) A data ] in a character class must be notated as \] because if the
688            first data character in a class is ], it defines an empty class. (In
689            Perl it is not possible to have an empty class.) The empty class []
690            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
691            The negative empty class [^] matches any one character, independently
692            of the DOTALL setting.
694    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
695        non-existent subpattern following a character class starting with ']' and
696        containing () gave an internal compiling error instead of "reference to
697        non-existent subpattern". Fortunately, when the pattern did exist, the
698        compiled code was correct. (When scanning forwards to check for the
699        existencd of the subpattern, it was treating the data ']' as terminating
700        the class, so got the count wrong. When actually compiling, the reference
701        was subsequently set up correctly.)
703    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
704        it was being rejected as not supported by pcre_dfa_exec(), even though
705        other assertions are supported. I have made pcre_dfa_exec() support
706        (*FAIL).
708    16. The implementation of 13c above involved the invention of a new opcode,
709        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
710        cannot be changed at match time, I realized I could make a small
711        improvement to matching performance by compiling OP_ALLANY instead of
712        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
713        on the OP_ANY path.
715    17. Compiling pcretest on Windows with readline support failed without the
716        following two fixes: (1) Make the unistd.h include conditional on
717        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
719    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
720        ncurses library to be included for pcretest when ReadLine support is
721        requested, but also to allow for it to be overridden. This patch came from
722        Daniel Bergström.
724    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
725        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
726        any errors with the current Unicode tables. Thanks to Peter Kankowski for
727        spotting this.
730    Version 7.6 28-Jan-08
731    ---------------------
733    1.  A character class containing a very large number of characters with
734        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
735        overflow.
737    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
738        HAVE_LONG_LONG is not defined.
740    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
741        bring them up to date and include new features. This patch includes:
743        - Fixed PH's badly added libz and libbz2 support.
744        - Fixed a problem with static linking.
745        - Added pcredemo. [But later removed - see 7 below.]
746        - Fixed dftables problem and added an option.
747        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
748            HAVE_LONG_LONG.
749        - Added readline support for pcretest.
750        - Added an listing of the option settings after cmake has run.
752    4.  A user submitted a patch to Makefile that makes it easy to create
753        "pcre.dll" under mingw when using Configure/Make. I added stuff to
754        Makefile.am that cause it to include this special target, without
755        affecting anything else. Note that the same mingw target plus all
756        the other distribution libraries and programs are now supported
757        when configuring with CMake (see 6 below) instead of with
758        Configure/Make.
760    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
761        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
762        exported in the Windows port". It has not yet been confirmed that the patch
763        solves the problem, but it does no harm.
765    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
766        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
767        with CMake, and also correct the comment about stack recursion.
769    7.  Remove the automatic building of pcredemo from the ./configure system and
770        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
771        of a program that users should build themselves after PCRE is installed, so
772        building it automatically is not really right. What is more, it gave
773        trouble in some build environments.
775    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
778    Version 7.5 10-Jan-08
779    ---------------------
781    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
782        values in parens when parsing an RE using the C++ wrapper."
784    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
785        Characters greater than 255 were excluded from the class instead of being
786        included.
788    3.  The same bug as (2) above applied to negated POSIX classes such as
789        [:^space:].
791    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
792        defined or documented. It seems to have been a typo for PCRE_STATIC, so
793        I have changed it.
795    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
796        first named subpattern) and a construct such as (?&a) would reference the
797        first named subpattern whose name started with "a" (in other words, the
798        length check was missing). Both these problems are fixed. "Subpattern name
799        expected" is now given for (?&) (a zero-length name), and this patch also
800        makes it give the same error for \k'' (previously it complained that that
801        was a reference to a non-existent subpattern).
803    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
804        this is right because (?- can be followed by option settings as well as by
805        digits. I have, however, made the messages clearer.
807    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
808        than the number used in the conditional) now cause a compile-time error.
809        This is actually not compatible with Perl, which accepts such patterns, but
810        treats the conditional as always being FALSE (as PCRE used to), but it
811        seems to me that giving a diagnostic is better.
813    8.  Change "alphameric" to the more common word "alphanumeric" in comments
814        and messages.
816    9.  Fix two occurrences of "backslash" in comments that should have been
817        "backspace".
819    10. Remove two redundant lines of code that can never be obeyed (their function
820        was moved elsewhere).
822    11. The program that makes PCRE's Unicode character property table had a bug
823        which caused it to generate incorrect table entries for sequences of
824        characters that have the same character type, but are in different scripts.
825        It amalgamated them into a single range, with the script of the first of
826        them. In other words, some characters were in the wrong script. There were
827        thirteen such cases, affecting characters in the following ranges:
829          U+002b0 - U+002c1
830          U+0060c - U+0060d
831          U+0061e - U+00612
832          U+0064b - U+0065e
833          U+0074d - U+0076d
834          U+01800 - U+01805
835          U+01d00 - U+01d77
836          U+01d9b - U+01dbf
837          U+0200b - U+0200f
838          U+030fc - U+030fe
839          U+03260 - U+0327f
840          U+0fb46 - U+0fbb1
841          U+10450 - U+1049d
843    12. The -o option (show only the matching part of a line) for pcregrep was not
844        compatible with GNU grep in that, if there was more than one match in a
845        line, it showed only the first of them. It now behaves in the same way as
846        GNU grep.
848    13. If the -o and -v options were combined for pcregrep, it printed a blank
849        line for every non-matching line. GNU grep prints nothing, and pcregrep now
850        does the same. The return code can be used to tell if there were any
851        non-matching lines.
853    14. Added --file-offsets and --line-offsets to pcregrep.
855    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
856        infinitely looping recursion. The bug was that positive lookaheads were not
857        being skipped when checking for a possible empty match (negative lookaheads
858        and both kinds of lookbehind were skipped).
860    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
861        inclusion of <windows.h> to before rather than after the definition of
862        INVALID_FILE_ATTRIBUTES (patch from David Byron).
864    17. Specifying a possessive quantifier with a specific limit for a Unicode
865        character property caused pcre_compile() to compile bad code, which led at
866        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
867        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
868        caused the error; without that there was no problem.
870    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
872    19. Added --enable-pcretest-libreadline.
874    20. In pcrecpp.cc, the variable 'count' was incremented twice in
875        RE::GlobalReplace(). As a result, the number of replacements returned was
876        double what it should be. I removed one of the increments, but Craig sent a
877        later patch that removed the other one (the right fix) and added unit tests
878        that check the return values (which was not done before).
880    21. Several CMake things:
882        (1) Arranged that, when cmake is used on Unix, the libraries end up with
883            the names libpcre and libpcreposix, not just pcre and pcreposix.
885        (2) The above change means that pcretest and pcregrep are now correctly
886            linked with the newly-built libraries, not previously installed ones.
890    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
891        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
892        UTF-8 newline character). The key issue is that the pattern starts .*;
893        this means that the match must be either at the beginning, or after a
894        newline. The bug was in the code for advancing after a failed match and
895        checking that the new position followed a newline. It was not taking
896        account of UTF-8 characters correctly.
898    23. PCRE was behaving differently from Perl in the way it recognized POSIX
899        character classes. PCRE was not treating the sequence [:...:] as a
900        character class unless the ... were all letters. Perl, however, seems to
901        allow any characters between [: and :], though of course it rejects as
902        unknown any "names" that contain non-letters, because all the known class
903        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
904        for example, whereas PCRE did not - it did not recognize a POSIX character
905        class. This seemed a bit dangerous, so the code has been changed to be
906        closer to Perl. The behaviour is not identical to Perl, because PCRE will
907        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
908        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
909        Perl does, and where it didn't before.
911    24. Rewrite so as to remove the single use of %n from pcregrep because in some
912        Windows environments %n is disabled by default.
915    Version 7.4 21-Sep-07
916    ---------------------
918    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
919        means that a class such as [\s] counted as "explicit reference to CR or
920        LF". That isn't really right - the whole point of the change was to try to
921        help when there was an actual mention of one of the two characters. So now
922        the change happens only if \r or \n (or a literal CR or LF) character is
923        encountered.
925    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
926        of both had grown to the point where there were only 3 bits left.
927        Fortunately, there was spare space in the data structure, and so I have
928        moved the internal flags into a new 16-bit field to free up more option
929        bits.
931    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
932        but did not set the internal JCHANGED flag - either of these is enough to
933        control the way the "get" function works - but the PCRE_INFO_JCHANGED
934        facility is supposed to tell if (?J) was ever used, so now (?J) at the
935        start sets both bits.
937    4.  Added options (at build time, compile time, exec time) to change \R from
938        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
940    5.  doc/pcresyntax.html was missing from the distribution.
942    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
943        compatibility, even though it is no longer used.
945    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
946        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
947        windows.h file is present (where different names are used). [This was
948        reversed later after testing - see 16 below.]
950    8.  Changed all #include <config.h> to #include "config.h". There were also
951        some further <pcre.h> cases that I changed to "pcre.h".
953    9.  When pcregrep was used with the --colour option, it missed the line ending
954        sequence off the lines that it output.
956    10. It was pointed out to me that arrays of string pointers cause lots of
957        relocations when a shared library is dynamically loaded. A technique of
958        using a single long string with a table of offsets can drastically reduce
959        these. I have refactored PCRE in four places to do this. The result is
960        dramatic:
962          Originally:                          290
963          After changing UCP table:            187
964          After changing error message table:   43
965          After changing table of "verbs"       36
966          After changing table of Posix names   22
968        Thanks to the folks working on Gregex for glib for this insight.
970    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
971        unicode-properties was also set.
973    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
975    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
976        checked only for CRLF.
978    14. Added casts to pcretest.c to avoid compiler warnings.
980    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
982    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
983        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
984        entirely. This removes changes made in 7 above.
986    17. The CMake files have been updated, and there is now more information about
987        building with CMake in the NON-UNIX-USE document.
990    Version 7.3 28-Aug-07
991    ---------------------
993     1. In the rejigging of the build system that eventually resulted in 7.1, the
994        line "#include <pcre.h>" was included in pcre_internal.h. The use of angle
995        brackets there is not right, since it causes compilers to look for an
996        installed pcre.h, not the version that is in the source that is being
997        compiled (which of course may be different). I have changed it back to:
999          #include "pcre.h"
1001        I have a vague recollection that the change was concerned with compiling in
1002        different directories, but in the new build system, that is taken care of
1003        by the VPATH setting the Makefile.
1005     2. The pattern .*$ when run in not-DOTALL UTF-8 mode with newline=any failed
1006        when the subject happened to end in the byte 0x85 (e.g. if the last
1007        character was \x{1ec5}). *Character* 0x85 is one of the "any" newline
1008        characters but of course it shouldn't be taken as a newline when it is part
1009        of another character. The bug was that, for an unlimited repeat of . in
1010        not-DOTALL UTF-8 mode, PCRE was advancing by bytes rather than by
1011        characters when looking for a newline.
1013     3. A small performance improvement in the DOTALL UTF-8 mode .* case.
1015     4. Debugging: adjusted the names of opcodes for different kinds of parentheses
1016        in debug output.
1018     5. Arrange to use "%I64d" instead of "%lld" and "%I64u" instead of "%llu" for
1019        long printing in the pcrecpp unittest when running under MinGW.
1021     6. ESC_K was left out of the EBCDIC table.
1023     7. Change 7.0/38 introduced a new limit on the number of nested non-capturing
1024        parentheses; I made it 1000, which seemed large enough. Unfortunately, the
1025        limit also applies to "virtual nesting" when a pattern is recursive, and in
1026        this case 1000 isn't so big. I have been able to remove this limit at the
1027        expense of backing off one optimization in certain circumstances. Normally,
1028        when pcre_exec() would call its internal match() function recursively and
1029        immediately return the result unconditionally, it uses a "tail recursion"
1030        feature to save stack. However, when a subpattern that can match an empty
1031        string has an unlimited repetition quantifier, it no longer makes this
1032        optimization. That gives it a stack frame in which to save the data for
1033        checking that an empty string has been matched. Previously this was taken
1034        from the 1000-entry workspace that had been reserved. So now there is no
1035        explicit limit, but more stack is used.
1037     8. Applied Daniel's patches to solve problems with the import/export magic
1038        syntax that is required for Windows, and which was going wrong for the
1039        pcreposix and pcrecpp parts of the library. These were overlooked when this
1040        problem was solved for the main library.
1042     9. There were some crude static tests to avoid integer overflow when computing
1043        the size of patterns that contain repeated groups with explicit upper
1044        limits. As the maximum quantifier is 65535, the maximum group length was
1045        set at 30,000 so that the product of these two numbers did not overflow a
1046        32-bit integer. However, it turns out that people want to use groups that
1047        are longer than 30,000 bytes (though not repeat them that many times).
1048        Change 7.0/17 (the refactoring of the way the pattern size is computed) has
1049        made it possible to implement the integer overflow checks in a much more
1050        dynamic way, which I have now done. The artificial limitation on group
1051        length has been removed - we now have only the limit on the total length of
1052        the compiled pattern, which depends on the LINK_SIZE setting.
1054    10. Fixed a bug in the documentation for get/copy named substring when
1055        duplicate names are permitted. If none of the named substrings are set, the
1056        functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an
1057        empty string.
1059    11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E
1060        instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,
1061        because the ] is interpreted as the first data character and the
1062        terminating ] is not found. PCRE has been made compatible with Perl in this
1063        regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could
1064        cause memory overwriting.
1066    10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty
1067        string has been matched (to stop an infinite loop). It was not recognizing
1068        a conditional subpattern that could match an empty string if that
1069        subpattern was within another subpattern. For example, it looped when
1070        trying to match  (((?(1)X|))*)  but it was OK with  ((?(1)X|)*)  where the
1071        condition was not nested. This bug has been fixed.
1073    12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack
1074        past the start of the subject in the presence of bytes with the top bit
1075        set, for example "\x8aBCD".
1077    13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
1078        (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
1080    14. Optimized (?!) to (*FAIL).
1082    15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
1083        This restricts code points to be within the range 0 to 0x10FFFF, excluding
1084        the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
1085        full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
1086        does: it's just the validity check that is more restrictive.
1088    16. Inserted checks for integer overflows during escape sequence (backslash)
1089        processing, and also fixed erroneous offset values for syntax errors during
1090        backslash processing.
1092    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
1093        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
1095    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
1096        caused an overrun.
1098    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
1099        something other than just ASCII characters) inside a group that had an
1100        unlimited repeat caused a loop at compile time (while checking to see
1101        whether the group could match an empty string).
1103    20. Debugging a pattern containing \p or \P could cause a crash. For example,
1104        [\P{Any}] did so. (Error in the code for printing property names.)
1106    21. An orphan \E inside a character class could cause a crash.
1108    22. A repeated capturing bracket such as (A)? could cause a wild memory
1109        reference during compilation.
1111    23. There are several functions in pcre_compile() that scan along a compiled
1112        expression for various reasons (e.g. to see if it's fixed length for look
1113        behind). There were bugs in these functions when a repeated \p or \P was
1114        present in the pattern. These operators have additional parameters compared
1115        with \d, etc, and these were not being taken into account when moving along
1116        the compiled data. Specifically:
1118        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
1119            length.
1121        (b) An item such as \pL+ within a repeated group could cause crashes or
1122            loops.
1124        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
1125            "reference to non-existent subpattern" error.
1127        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
1129    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
1130        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
1132    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
1134    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
1135        character were causing crashes (broken optimization).
1137    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
1138        \p or \P) caused a compile-time loop.
1140    28. More problems have arisen in unanchored patterns when CRLF is a valid line
1141        break. For example, the unstudied pattern [\r\n]A does not match the string
1142        "\r\nA" because change 7.0/46 below moves the current point on by two
1143        characters after failing to match at the start. However, the pattern \nA
1144        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
1145        the same is true. There doesn't seem any very clean way out of this, but
1146        what I have chosen to do makes the common cases work: PCRE now takes note
1147        of whether there can be an explicit match for \r or \n anywhere in the
1148        pattern, and if so, 7.0/46 no longer applies. As part of this change,
1149        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
1150        pattern has explicit CR or LF references.
1152    29. Added (*CR) etc for changing newline setting at start of pattern.
1155    Version 7.2 19-Jun-07
1156  ---------------------  ---------------------
1158   1. If the fr_FR locale cannot be found for test 3, try the "french" locale,   1. If the fr_FR locale cannot be found for test 3, try the "french" locale,
# Line 40  Version 7.2 13-June-07 Line 1191  Version 7.2 13-June-07
1192      (f) \g{name} is another synonym - part of Perl 5.10's unification of      (f) \g{name} is another synonym - part of Perl 5.10's unification of
1193          reference syntax.          reference syntax.
1195      (g) (?| introduces a group in which the numbering of parentheses in each      (g) (?| introduces a group in which the numbering of parentheses in each
1196          alternative starts with the same number.          alternative starts with the same number.
1198      (h) \h, \H, \v, and \V match horizontal and vertical whitespace.      (h) \h, \H, \v, and \V match horizontal and vertical whitespace.
1200   7. Added two new calls to pcre_fullinfo(): PCRE_INFO_OKPARTIAL and   7. Added two new calls to pcre_fullinfo(): PCRE_INFO_OKPARTIAL and
# Line 59  Version 7.2 13-June-07 Line 1210  Version 7.2 13-June-07
1210      bit of new cunning has reduced the workspace needed for groups with      bit of new cunning has reduced the workspace needed for groups with
1211      alternatives. The 1000-alternative test pattern now uses 12 bytes of      alternatives. The 1000-alternative test pattern now uses 12 bytes of
1212      workspace instead of running out of the 4096 that are available.      workspace instead of running out of the 4096 that are available.
1214  10. Inserted some missing (unsigned int) casts to get rid of compiler warnings.  10. Inserted some missing (unsigned int) casts to get rid of compiler warnings.
1216  11. Applied patch from Google to remove an optimization that didn't quite work.  11. Applied patch from Google to remove an optimization that didn't quite work.
1217      The report of the bug said:      The report of the bug said:
1219        pcrecpp::RE("a*").FullMatch("aaa") matches, while        pcrecpp::RE("a*").FullMatch("aaa") matches, while
1220        pcrecpp::RE("a*?").FullMatch("aaa") does not, and        pcrecpp::RE("a*?").FullMatch("aaa") does not, and
1221        pcrecpp::RE("a*?\\z").FullMatch("aaa") does again.        pcrecpp::RE("a*?\\z").FullMatch("aaa") does again.
1223    12. If \p or \P was used in non-UTF-8 mode on a character greater than 127
1224        it matched the wrong number of bytes.
1227  Version 7.1 24-Apr-07  Version 7.1 24-Apr-07

Removed from v.181  
changed lines
  Added in v.528

  ViewVC Help
Powered by ViewVC 1.1.5