ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 329 by ph10, Fri Mar 28 12:06:36 2008 UTC revision 539 by ph10, Sun Jun 13 21:35:04 2010 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 7.7 05-Mar-08  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).
72    18. If the last data line in a file for pcretest does not have a newline on
73        the end, a newline was missing in the output.
75    19. The default pcre_chartables.c file recognizes only ASCII characters (values
76        less than 128) in its various bitmaps. However, there is a facility for
77        generating tables according to the current locale when PCRE is compiled. It
78        turns out that in some environments, 0x85 and 0xa0, which are Unicode space
79        characters, are recognized by isspace() and therefore were getting set in
80        these tables. This caused a problem in UTF-8 mode when pcre_study() was
81        used to create a list of bytes that can start a match. For \s, it was
82        including 0x85 and 0xa0, which of course cannot start UTF-8 characters. I
83        have changed the code so that only real ASCII characters (less than 128)
84        and the correct starting bytes for UTF-8 encodings are set in this case.
85        (When PCRE_UCP is set - see 9 above - the code is different altogether.)
88    Version 8.02 19-Mar-2010
89    ------------------------
91    1.  The Unicode data tables have been updated to Unicode 5.2.0.
93    2.  Added the option --libs-cpp to pcre-config, but only when C++ support is
94        configured.
96    3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the
97        original author of that file, following a query about its status.
99    4.  On systems that do not have stdint.h (e.g. Solaris), check for and include
100        inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
102    5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
103        quantifier applied to a forward-referencing subroutine call, could compile
104        incorrect code or give the error "internal error: previously-checked
105        referenced subpattern not found".
107    6.  Both MS Visual Studio and Symbian OS have problems with initializing
108        variables to point to external functions. For these systems, therefore,
109        pcre_malloc etc. are now initialized to local functions that call the
110        relevant global functions.
112    7.  There were two entries missing in the vectors called coptable and poptable
113        in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.
114        I've fixed the data, and added a kludgy way of testing at compile time that
115        the lengths are correct (equal to the number of opcodes).
117    8.  Following on from 7, I added a similar kludge to check the length of the
118        eint vector in pcreposix.c.
120    9.  Error texts for pcre_compile() are held as one long string to avoid too
121        much relocation at load time. To find a text, the string is searched,
122        counting zeros. There was no check for running off the end of the string,
123        which could happen if a new error number was added without updating the
124        string.
126    10. \K gave a compile-time error if it appeared in a lookbehind assersion.
128    11. \K was not working if it appeared in an atomic group or in a group that
129        was called as a "subroutine", or in an assertion. Perl 5.11 documents that
130        \K is "not well defined" if used in an assertion. PCRE now accepts it if
131        the assertion is positive, but not if it is negative.
133    12. Change 11 fortuitously reduced the size of the stack frame used in the
134        "match()" function of pcre_exec.c by one pointer. Forthcoming
135        implementation of support for (*MARK) will need an extra pointer on the
136        stack; I have reserved it now, so that the stack frame size does not
137        decrease.
139    13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other
140        item in branch that calls a recursion is a subroutine call - as in the
141        second branch in the above example - was incorrectly given the compile-
142        time error "recursive call could loop indefinitely" because pcre_compile()
143        was not correctly checking the subroutine for matching a non-empty string.
145    14. The checks for overrunning compiling workspace could trigger after an
146        overrun had occurred. This is a "should never occur" error, but it can be
147        triggered by pathological patterns such as hundreds of nested parentheses.
148        The checks now trigger 100 bytes before the end of the workspace.
150    15. Fix typo in configure.ac: "srtoq" should be "strtoq".
153    Version 8.01 19-Jan-2010
154    ------------------------
156    1.  If a pattern contained a conditional subpattern with only one branch (in
157        particular, this includes all (*DEFINE) patterns), a call to pcre_study()
158        computed the wrong minimum data length (which is of course zero for such
159        subpatterns). This could cause incorrect "no match" results.
161    2.  For patterns such as (?i)a(?-i)b|c where an option setting at the start of
162        the pattern is reset in the first branch, pcre_compile() failed with
163        "internal error: code overflow at offset...". This happened only when
164        the reset was to the original external option setting. (An optimization
165        abstracts leading options settings into an external setting, which was the
166        cause of this.)
168    3.  A pattern such as ^(?!a(*SKIP)b) where a negative assertion contained one
169        of the verbs SKIP, PRUNE, or COMMIT, did not work correctly. When the
170        assertion pattern did not match (meaning that the assertion was true), it
171        was incorrectly treated as false if the SKIP had been reached during the
172        matching. This also applied to assertions used as conditions.
174    4.  If an item that is not supported by pcre_dfa_exec() was encountered in an
175        assertion subpattern, including such a pattern used as a condition,
176        unpredictable results occurred, instead of the error return
179    5.  The C++ GlobalReplace function was not working like Perl for the special
180        situation when an empty string is matched. It now does the fancy magic
181        stuff that is necessary.
183    6.  In pcre_internal.h, obsolete includes to setjmp.h and stdarg.h have been
184        removed. (These were left over from very, very early versions of PCRE.)
186    7.  Some cosmetic changes to the code to make life easier when compiling it
187        as part of something else:
189        (a) Change DEBUG to PCRE_DEBUG.
191        (b) In pcre_compile(), rename the member of the "branch_chain" structure
192            called "current" as "current_branch", to prevent a collision with the
193            Linux macro when compiled as a kernel module.
195        (c) In pcre_study(), rename the function set_bit() as set_table_bit(), to
196            prevent a collision with the Linux macro when compiled as a kernel
197            module.
199    8.  In pcre_compile() there are some checks for integer overflows that used to
200        cast potentially large values to (double). This has been changed to that
201        when building, a check for int64_t is made, and if it is found, it is used
202        instead, thus avoiding the use of floating point arithmetic. (There is no
203        other use of FP in PCRE.) If int64_t is not found, the fallback is to
204        double.
206    9.  Added two casts to avoid signed/unsigned warnings from VS Studio Express
207        2005 (difference between two addresses compared to an unsigned value).
209    10. Change the standard AC_CHECK_LIB test for libbz2 in configure.ac to a
210        custom one, because of the following reported problem in Windows:
212          - libbz2 uses the Pascal calling convention (WINAPI) for the functions
213              under Win32.
214          - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",
215              therefore missing the function definition.
216          - The compiler thus generates a "C" signature for the test function.
217          - The linker fails to find the "C" function.
218          - PCRE fails to configure if asked to do so against libbz2.
220    11. When running libtoolize from libtool-2.2.6b as part of autogen.sh, these
221        messages were output:
223          Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
224          rerunning libtoolize, to keep the correct libtool macros in-tree.
225          Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
227        I have done both of these things.
229    12. Although pcre_dfa_exec() does not use nearly as much stack as pcre_exec()
230        most of the time, it *can* run out if it is given a pattern that contains a
231        runaway infinite recursion. I updated the discussion in the pcrestack man
232        page.
234    13. Now that we have gone to the x.xx style of version numbers, the minor
235        version may start with zero. Using 08 or 09 is a bad idea because users
236        might check the value of PCRE_MINOR in their code, and 08 or 09 may be
237        interpreted as invalid octal numbers. I've updated the previous comment in
238        configure.ac, and also added a check that gives an error if 08 or 09 are
239        used.
241    14. Change 8.00/11 was not quite complete: code had been accidentally omitted,
242        causing partial matching to fail when the end of the subject matched \W
243        in a UTF-8 pattern where \W was quantified with a minimum of 3.
245    15. There were some discrepancies between the declarations in pcre_internal.h
246        of _pcre_is_newline(), _pcre_was_newline(), and _pcre_valid_utf8() and
247        their definitions. The declarations used "const uschar *" and the
248        definitions used USPTR. Even though USPTR is normally defined as "const
249        unsigned char *" (and uschar is typedeffed as "unsigned char"), it was
250        reported that: "This difference in casting confuses some C++ compilers, for
251        example, SunCC recognizes above declarations as different functions and
252        generates broken code for hbpcre." I have changed the declarations to use
253        USPTR.
255    16. GNU libtool is named differently on some systems. The autogen.sh script now
256        tries several variants such as glibtoolize (MacOSX) and libtoolize1x
257        (FreeBSD).
259    17. Applied Craig's patch that fixes an HP aCC compile error in pcre 8.00
260        (strtoXX undefined when compiling pcrecpp.cc). The patch contains this
261        comment: "Figure out how to create a longlong from a string: strtoll and
262        equivalent. It's not enough to call AC_CHECK_FUNCS: hpux has a strtoll, for
263        instance, but it only takes 2 args instead of 3!"
265    18. A subtle bug concerned with back references has been fixed by a change of
266        specification, with a corresponding code fix. A pattern such as
267        ^(xa|=?\1a)+$ which contains a back reference inside the group to which it
268        refers, was giving matches when it shouldn't. For example, xa=xaaa would
269        match that pattern. Interestingly, Perl (at least up to 5.11.3) has the
270        same bug. Such groups have to be quantified to be useful, or contained
271        inside another quantified group. (If there's no repetition, the reference
272        can never match.) The problem arises because, having left the group and
273        moved on to the rest of the pattern, a later failure that backtracks into
274        the group uses the captured value from the final iteration of the group
275        rather than the correct earlier one. I have fixed this in PCRE by forcing
276        any group that contains a reference to itself to be an atomic group; that
277        is, there cannot be any backtracking into it once it has completed. This is
278        similar to recursive and subroutine calls.
281    Version 8.00 19-Oct-09
282    ----------------------
284    1.  The table for translating pcre_compile() error codes into POSIX error codes
285        was out-of-date, and there was no check on the pcre_compile() error code
286        being within the table. This could lead to an OK return being given in
287        error.
289    2.  Changed the call to open a subject file in pcregrep from fopen(pathname,
290        "r") to fopen(pathname, "rb"), which fixed a problem with some of the tests
291        in a Windows environment.
293    3.  The pcregrep --count option prints the count for each file even when it is
294        zero, as does GNU grep. However, pcregrep was also printing all files when
295        --files-with-matches was added. Now, when both options are given, it prints
296        counts only for those files that have at least one match. (GNU grep just
297        prints the file name in this circumstance, but including the count seems
298        more useful - otherwise, why use --count?) Also ensured that the
299        combination -clh just lists non-zero counts, with no names.
301    4.  The long form of the pcregrep -F option was incorrectly implemented as
302        --fixed_strings instead of --fixed-strings. This is an incompatible change,
303        but it seems right to fix it, and I didn't think it was worth preserving
304        the old behaviour.
306    5.  The command line items --regex=pattern and --regexp=pattern were not
307        recognized by pcregrep, which required --regex pattern or --regexp pattern
308        (with a space rather than an '='). The man page documented the '=' forms,
309        which are compatible with GNU grep; these now work.
311    6.  No libpcreposix.pc file was created for pkg-config; there was just
312        libpcre.pc and libpcrecpp.pc. The omission has been rectified.
314    7.  Added #ifndef SUPPORT_UCP into the pcre_ucd.c module, to reduce its size
315        when UCP support is not needed, by modifying the Python script that
316        generates it from Unicode data files. This should not matter if the module
317        is correctly used as a library, but I received one complaint about 50K of
318        unwanted data. My guess is that the person linked everything into his
319        program rather than using a library. Anyway, it does no harm.
321    8.  A pattern such as /\x{123}{2,2}+/8 was incorrectly compiled; the trigger
322        was a minimum greater than 1 for a wide character in a possessive
323        repetition. The same bug could also affect patterns like /(\x{ff}{0,2})*/8
324        which had an unlimited repeat of a nested, fixed maximum repeat of a wide
325        character. Chaos in the form of incorrect output or a compiling loop could
326        result.
328    9.  The restrictions on what a pattern can contain when partial matching is
329        requested for pcre_exec() have been removed. All patterns can now be
330        partially matched by this function. In addition, if there are at least two
331        slots in the offset vector, the offset of the earliest inspected character
332        for the match and the offset of the end of the subject are set in them when
333        PCRE_ERROR_PARTIAL is returned.
335    10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is
336        synonymous with PCRE_PARTIAL, for backwards compatibility, and
337        PCRE_PARTIAL_HARD, which causes a partial match to supersede a full match,
338        and may be more useful for multi-segment matching.
340    11. Partial matching with pcre_exec() is now more intuitive. A partial match
341        used to be given if ever the end of the subject was reached; now it is
342        given only if matching could not proceed because another character was
343        needed. This makes a difference in some odd cases such as Z(*FAIL) with the
344        string "Z", which now yields "no match" instead of "partial match". In the
345        case of pcre_dfa_exec(), "no match" is given if every matching path for the
346        final character ended with (*FAIL).
348    12. Restarting a match using pcre_dfa_exec() after a partial match did not work
349        if the pattern had a "must contain" character that was already found in the
350        earlier partial match, unless partial matching was again requested. For
351        example, with the pattern /dog.(body)?/, the "must contain" character is
352        "g". If the first part-match was for the string "dog", restarting with
353        "sbody" failed. This bug has been fixed.
355    13. The string returned by pcre_dfa_exec() after a partial match has been
356        changed so that it starts at the first inspected character rather than the
357        first character of the match. This makes a difference only if the pattern
358        starts with a lookbehind assertion or \b or \B (\K is not supported by
359        pcre_dfa_exec()). It's an incompatible change, but it makes the two
360        matching functions compatible, and I think it's the right thing to do.
362    14. Added a pcredemo man page, created automatically from the pcredemo.c file,
363        so that the demonstration program is easily available in environments where
364        PCRE has not been installed from source.
366    15. Arranged to add -DPCRE_STATIC to cflags in libpcre.pc, libpcreposix.cp,
367        libpcrecpp.pc and pcre-config when PCRE is not compiled as a shared
368        library.
370    16. Added REG_UNGREEDY to the pcreposix interface, at the request of a user.
371        It maps to PCRE_UNGREEDY. It is not, of course, POSIX-compatible, but it
372        is not the first non-POSIX option to be added. Clearly some people find
373        these options useful.
375    17. If a caller to the POSIX matching function regexec() passes a non-zero
376        value for nmatch with a NULL value for pmatch, the value of
377        nmatch is forced to zero.
379    18. RunGrepTest did not have a test for the availability of the -u option of
380        the diff command, as RunTest does. It now checks in the same way as
381        RunTest, and also checks for the -b option.
383    19. If an odd number of negated classes containing just a single character
384        interposed, within parentheses, between a forward reference to a named
385        subpattern and the definition of the subpattern, compilation crashed with
386        an internal error, complaining that it could not find the referenced
387        subpattern. An example of a crashing pattern is /(?&A)(([^m])(?<A>))/.
388        [The bug was that it was starting one character too far in when skipping
389        over the character class, thus treating the ] as data rather than
390        terminating the class. This meant it could skip too much.]
392    20. Added PCRE_NOTEMPTY_ATSTART in order to be able to correctly implement the
393        /g option in pcretest when the pattern contains \K, which makes it possible
394        to have an empty string match not at the start, even when the pattern is
395        anchored. Updated pcretest and pcredemo to use this option.
397    21. If the maximum number of capturing subpatterns in a recursion was greater
398        than the maximum at the outer level, the higher number was returned, but
399        with unset values at the outer level. The correct (outer level) value is
400        now given.
402    22. If (*ACCEPT) appeared inside capturing parentheses, previous releases of
403        PCRE did not set those parentheses (unlike Perl). I have now found a way to
404        make it do so. The string so far is captured, making this feature
405        compatible with Perl.
407    23. The tests have been re-organized, adding tests 11 and 12, to make it
408        possible to check the Perl 5.10 features against Perl 5.10.
410    24. Perl 5.10 allows subroutine calls in lookbehinds, as long as the subroutine
411        pattern matches a fixed length string. PCRE did not allow this; now it
412        does. Neither allows recursion.
414    25. I finally figured out how to implement a request to provide the minimum
415        length of subject string that was needed in order to match a given pattern.
416        (It was back references and recursion that I had previously got hung up
417        on.) This code has now been added to pcre_study(); it finds a lower bound
418        to the length of subject needed. It is not necessarily the greatest lower
419        bound, but using it to avoid searching strings that are too short does give
420        some useful speed-ups. The value is available to calling programs via
421        pcre_fullinfo().
423    26. While implementing 25, I discovered to my embarrassment that pcretest had
424        not been passing the result of pcre_study() to pcre_dfa_exec(), so the
425        study optimizations had never been tested with that matching function.
426        Oops. What is worse, even when it was passed study data, there was a bug in
427        pcre_dfa_exec() that meant it never actually used it. Double oops. There
428        were also very few tests of studied patterns with pcre_dfa_exec().
430    27. If (?| is used to create subpatterns with duplicate numbers, they are now
431        allowed to have the same name, even if PCRE_DUPNAMES is not set. However,
432        on the other side of the coin, they are no longer allowed to have different
433        names, because these cannot be distinguished in PCRE, and this has caused
434        confusion. (This is a difference from Perl.)
436    28. When duplicate subpattern names are present (necessarily with different
437        numbers, as required by 27 above), and a test is made by name in a
438        conditional pattern, either for a subpattern having been matched, or for
439        recursion in such a pattern, all the associated numbered subpatterns are
440        tested, and the overall condition is true if the condition is true for any
441        one of them. This is the way Perl works, and is also more like the way
442        testing by number works.
445    Version 7.9 11-Apr-09
446    ---------------------
448    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
449        (pcretest), all targets were linked against these libraries. This included
450        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
451        libraries. This caused unwanted dependencies to be created. This problem
452        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
453        pcretest is linked with readline.
455    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
456        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
457        moved outside it again, because FALSE and TRUE are already defined in AIX,
458        but BOOL is not.
460    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
461        PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
463    4.  The pcregrep documentation said spaces were inserted as well as colons (or
464        hyphens) following file names and line numbers when outputting matching
465        lines. This is not true; no spaces are inserted. I have also clarified the
466        wording for the --colour (or --color) option.
468    5.  In pcregrep, when --colour was used with -o, the list of matching strings
469        was not coloured; this is different to GNU grep, so I have changed it to be
470        the same.
472    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
473        each matching line was coloured. Now it goes on to look for further matches
474        of any of the test patterns, which is the same behaviour as GNU grep.
476    7.  A pattern that could match an empty string could cause pcregrep to loop; it
477        doesn't make sense to accept an empty string match in pcregrep, so I have
478        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
479        seems to be how GNU grep behaves.
481    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
482        start or after a newline", because the conditional assertion was not being
483        correctly handled. The rule now is that both the assertion and what follows
484        in the first alternative must satisfy the test.
486    9.  If auto-callout was enabled in a pattern with a conditional group whose
487        condition was an assertion, PCRE could crash during matching, both with
488        pcre_exec() and pcre_dfa_exec().
490    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
491        used for matching.
493    11. Unicode property support in character classes was not working for
494        characters (bytes) greater than 127 when not in UTF-8 mode.
496    12. Added the -M command line option to pcretest.
498    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
500    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
502    16. Added comments and documentation about mis-use of no_arg in the C++
503        wrapper.
505    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
506        from Martin Jerabek that uses macro names for all relevant character and
507        string constants.
509    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
510        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
511        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
512        these, but not everybody uses configure.
514    19. A conditional group that had only one branch was not being correctly
515        recognized as an item that could match an empty string. This meant that an
516        enclosing group might also not be so recognized, causing infinite looping
517        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
518        with the subject "ab", where knowledge that the repeated group can match
519        nothing is needed in order to break the loop.
521    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
522        exec(), but without supplying a callout function, matching went wrong.
524    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
525        leak if the size of the offset vector was greater than 30. When the vector
526        is smaller, the saved offsets during recursion go onto a local stack
527        vector, but for larger vectors malloc() is used. It was failing to free
528        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
529        error, in fact).
531    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
532        heapframe that is used only when UTF-8 support is enabled. This caused no
533        problem, but was untidy.
535    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
536        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
537        included within another project.
539    24. Steven Van Ingelgem's patches to add more options to the CMake support,
540        slightly modified by me:
542          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
543              not building pcregrep.
545          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
546              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
548    25. Forward references, both numeric and by name, in patterns that made use of
549        duplicate group numbers, could behave incorrectly or give incorrect errors,
550        because when scanning forward to find the reference group, PCRE was not
551        taking into account the duplicate group numbers. A pattern such as
552        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
554    26. Changed a few more instances of "const unsigned char *" to USPTR, making
555        the feature of a custom pointer more persuasive (as requested by a user).
557    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
558        pcretest.c, inside #ifndefs, because it seems they are sometimes already
559        pre-defined.
561    28. Added support for (*UTF8) at the start of a pattern.
563    29. Arrange for flags added by the "release type" setting in CMake to be shown
564        in the configuration summary.
567    Version 7.8 05-Sep-08
568    ---------------------
570    1.  Replaced UCP searching code with optimized version as implemented for Ad
571        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
572        stage table and inline lookup instead of a function, giving speed ups of 2
573        to 5 times on some simple patterns that I tested. Permission was given to
574        distribute the MultiStage2.py script that generates the tables (it's not in
575        the tarball, but is in the Subversion repository).
577    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
578        scripts.
580    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
581        a group with a zero qualifier. The result of the study could be incorrect,
582        or the function might crash, depending on the pattern.
584    4.  Caseless matching was not working for non-ASCII characters in back
585        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
586        It now works when Unicode Property Support is available.
588    5.  In pcretest, an escape such as \x{de} in the data was always generating
589        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
590        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
591        truncation.
593    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
595    7.  Added two (int) casts to pcregrep when printing the difference of two
596        pointers, in case they are 64-bit values.
598    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
599        test 2 if it fails.
601    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
602        and a #define of that name to empty if it is not externally set. This is to
603        allow users of MSVC to set it if necessary.
605    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
606        the convenience functions in the pcre_get.c source file.
608    11. An option change at the start of a pattern that had top-level alternatives
609        could cause overwriting and/or a crash. This command provoked a crash in
610        some environments:
612          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
614        This potential security problem was recorded as CVE-2008-2371.
616    12. For a pattern where the match had to start at the beginning or immediately
617        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
618        pcre_dfa_exec() could read past the end of the passed subject if there was
619        no match. To help with detecting such bugs (e.g. with valgrind), I modified
620        pcretest so that it places the subject at the end of its malloc-ed buffer.
622    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
623        exec() might read past the end of the data buffer in UTF-8 mode.
625    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
626        the data contained the byte 0x85 as part of a UTF-8 character within its
627        first line. This applied both to normal and DFA matching.
629    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
630        /^[^d]*?$/8 failed to match "abc".
632    16. Added a missing copyright notice to pcrecpp_internal.h.
634    17. Make it more clear in the documentation that values returned from
635        pcre_exec() in ovector are byte offsets, not character counts.
637    18. Tidied a few places to stop certain compilers from issuing warnings.
639    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
640        supplied by Stefan Weber. I made a further small update for 7.8 because
641        there is a change of source arrangements: the pcre_searchfuncs.c module is
642        replaced by pcre_ucd.c.
645    Version 7.7 07-May-08
646  ---------------------  ---------------------
648  1.  Applied Craig's patch to sort out a long long problem: "If we can't convert  1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
649      a string to a long long, pretend we don't even have a long long." This is      a string to a long long, pretend we don't even have a long long." This is
650      done by checking for the strtoq, strtoll, and _strtoi64 functions.      done by checking for the strtoq, strtoll, and _strtoi64 functions.
652  2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with  2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
653      pre-7.6 versions, which defined a global no_arg variable instead of putting      pre-7.6 versions, which defined a global no_arg variable instead of putting
654      it in the RE class.      it in the RE class. (See also #8 below.)
656  3.  Remove a line of dead code, identified by coverity and reported by Nuno  3.  Remove a line of dead code, identified by coverity and reported by Nuno
657      Lopes.      Lopes.
659  4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:  4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
661      (1) The include/exclude patterns were being applied to the whole pathnames      (1) The include/exclude patterns were being applied to the whole pathnames
662          of files, instead of just to the final components.          of files, instead of just to the final components.
664      (2) If there was more than one level of directory, the subdirectories were      (2) If there was more than one level of directory, the subdirectories were
665          skipped unless they satisfied the include/exclude conditions. This is          skipped unless they satisfied the include/exclude conditions. This is
666          inconsistent with GNU grep (and could even be seen as contrary to the          inconsistent with GNU grep (and could even be seen as contrary to the
667          pcregrep specification - which I improved to make it absolutely clear).          pcregrep specification - which I improved to make it absolutely clear).
668          The action now is always to scan all levels of directory, and just          The action now is always to scan all levels of directory, and just
669          apply the include/exclude patterns to regular files.          apply the include/exclude patterns to regular files.
671  5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used  5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
672      --exclude_dir in the tests to avoid scanning .svn directories.      --exclude_dir in the tests to avoid scanning .svn directories.
674  6.  Applied Craig's patch to the QuoteMeta function so that it escapes the  6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
675      NUL character as backslash + 0 rather than backslash + NUL, because PCRE      NUL character as backslash + 0 rather than backslash + NUL, because PCRE
676      doesn't support NULs in patterns.      doesn't support NULs in patterns.
678  7.  Added some missing "const"s to declarations of static tables in  7.  Added some missing "const"s to declarations of static tables in
679      pcre_compile.c and pcre_dfa_exec.c.      pcre_compile.c and pcre_dfa_exec.c.
681  8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was  8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
682      caused by fix #2  above. (Subsequently also a second patch to fix the      caused by fix #2  above. (Subsequently also a second patch to fix the
683      first patch.)      first patch. And a third patch - this was a messy problem.)
685    9.  Applied Craig's patch to remove the use of push_back().
687    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
688        matching function regexec().
690    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
691        which, however, unlike Perl's \g{...}, are subroutine calls, not back
692        references. PCRE supports relative numbers with this syntax (I don't think
693        Oniguruma does).
695    12. Previously, a group with a zero repeat such as (...){0} was completely
696        omitted from the compiled regex. However, this means that if the group
697        was called as a subroutine from elsewhere in the pattern, things went wrong
698        (an internal error was given). Such groups are now left in the compiled
699        pattern, with a new opcode that causes them to be skipped at execution
700        time.
702    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
703        to the way PCRE behaves:
705        (a) A lone ] character is dis-allowed (Perl treats it as data).
707        (b) A back reference to an unmatched subpattern matches an empty string
708            (Perl fails the current match path).
710        (c) A data ] in a character class must be notated as \] because if the
711            first data character in a class is ], it defines an empty class. (In
712            Perl it is not possible to have an empty class.) The empty class []
713            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
714            The negative empty class [^] matches any one character, independently
715            of the DOTALL setting.
717    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
718        non-existent subpattern following a character class starting with ']' and
719        containing () gave an internal compiling error instead of "reference to
720        non-existent subpattern". Fortunately, when the pattern did exist, the
721        compiled code was correct. (When scanning forwards to check for the
722        existencd of the subpattern, it was treating the data ']' as terminating
723        the class, so got the count wrong. When actually compiling, the reference
724        was subsequently set up correctly.)
726    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
727        it was being rejected as not supported by pcre_dfa_exec(), even though
728        other assertions are supported. I have made pcre_dfa_exec() support
729        (*FAIL).
731    16. The implementation of 13c above involved the invention of a new opcode,
732        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
733        cannot be changed at match time, I realized I could make a small
734        improvement to matching performance by compiling OP_ALLANY instead of
735        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
736        on the OP_ANY path.
738    17. Compiling pcretest on Windows with readline support failed without the
739        following two fixes: (1) Make the unistd.h include conditional on
740        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
742    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
743        ncurses library to be included for pcretest when ReadLine support is
744        requested, but also to allow for it to be overridden. This patch came from
745        Daniel Bergström.
747    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
748        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
749        any errors with the current Unicode tables. Thanks to Peter Kankowski for
750        spotting this.
753  Version 7.6 28-Jan-08  Version 7.6 28-Jan-08

Removed from v.329  
changed lines
  Added in v.539

  ViewVC Help
Powered by ViewVC 1.1.5