ViewVC logotype

Diff of /code/trunk/ChangeLog

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

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

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

  ViewVC Help
Powered by ViewVC 1.1.5