ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 282 by ph10, Fri Dec 7 19:32:32 2007 UTC revision 519 by ph10, Fri May 21 16:43:17 2010 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 7.5 12-Nov-07  Version 8.10 03 May-2010
5    ------------------------
7    1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and
8        THEN.
10    2.  (*ACCEPT) was not working when inside an atomic group.
12    3.  Inside a character class, \B is treated as a literal by default, but
13        faulted if PCRE_EXTRA is set. This mimics Perl's behaviour (the -w option
14        causes the error). The code is unchanged, but I tidied the documentation.
16    4.  Inside a character class, PCRE always treated \R and \X as literals,
17        whereas Perl faults them if its -w option is set. I have changed PCRE so
18        that it faults them when PCRE_EXTRA is set.
20    5.  Added support for \N, which always matches any character other than
21        newline. (It is the same as "." when PCRE_DOTALL is not set.)
23    6.  When compiling pcregrep with newer versions of gcc which may have
24        FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',
25        declared with attribute warn_unused_result" were given. Just casting the
26        result to (void) does not stop the warnings; a more elaborate fudge is
27        needed. I've used a macro to implement this.
29    7.  Minor change to pcretest.c to avoid a compiler warning.
31    8.  Added four artifical Unicode properties to help with an option to make
32        \s etc use properties (see next item). The new properties are: Xan
33        (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).
35    9.  Added PCRE_UCP to make \b, \d, \s, \w, and certain POSIX character classes
36        use Unicode properties. (*UCP) at the start of a pattern can be used to set
37        this option. Modified pcretest to add /W to test this facility. Added
38        REG_UCP to make it available via the POSIX interface.
40    10. Added --line-buffered to pcregrep.
43    Version 8.02 19-Mar-2010
44    ------------------------
46    1.  The Unicode data tables have been updated to Unicode 5.2.0.
48    2.  Added the option --libs-cpp to pcre-config, but only when C++ support is
49        configured.
51    3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the
52        original author of that file, following a query about its status.
54    4.  On systems that do not have stdint.h (e.g. Solaris), check for and include
55        inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
57    5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
58        quantifier applied to a forward-referencing subroutine call, could compile
59        incorrect code or give the error "internal error: previously-checked
60        referenced subpattern not found".
62    6.  Both MS Visual Studio and Symbian OS have problems with initializing
63        variables to point to external functions. For these systems, therefore,
64        pcre_malloc etc. are now initialized to local functions that call the
65        relevant global functions.
67    7.  There were two entries missing in the vectors called coptable and poptable
68        in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.
69        I've fixed the data, and added a kludgy way of testing at compile time that
70        the lengths are correct (equal to the number of opcodes).
72    8.  Following on from 7, I added a similar kludge to check the length of the
73        eint vector in pcreposix.c.
75    9.  Error texts for pcre_compile() are held as one long string to avoid too
76        much relocation at load time. To find a text, the string is searched,
77        counting zeros. There was no check for running off the end of the string,
78        which could happen if a new error number was added without updating the
79        string.
81    10. \K gave a compile-time error if it appeared in a lookbehind assersion.
83    11. \K was not working if it appeared in an atomic group or in a group that
84        was called as a "subroutine", or in an assertion. Perl 5.11 documents that
85        \K is "not well defined" if used in an assertion. PCRE now accepts it if
86        the assertion is positive, but not if it is negative.
88    12. Change 11 fortuitously reduced the size of the stack frame used in the
89        "match()" function of pcre_exec.c by one pointer. Forthcoming
90        implementation of support for (*MARK) will need an extra pointer on the
91        stack; I have reserved it now, so that the stack frame size does not
92        decrease.
94    13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other
95        item in branch that calls a recursion is a subroutine call - as in the
96        second branch in the above example - was incorrectly given the compile-
97        time error "recursive call could loop indefinitely" because pcre_compile()
98        was not correctly checking the subroutine for matching a non-empty string.
100    14. The checks for overrunning compiling workspace could trigger after an
101        overrun had occurred. This is a "should never occur" error, but it can be
102        triggered by pathological patterns such as hundreds of nested parentheses.
103        The checks now trigger 100 bytes before the end of the workspace.
105    15. Fix typo in configure.ac: "srtoq" should be "strtoq".
108    Version 8.01 19-Jan-2010
109    ------------------------
111    1.  If a pattern contained a conditional subpattern with only one branch (in
112        particular, this includes all (*DEFINE) patterns), a call to pcre_study()
113        computed the wrong minimum data length (which is of course zero for such
114        subpatterns). This could cause incorrect "no match" results.
116    2.  For patterns such as (?i)a(?-i)b|c where an option setting at the start of
117        the pattern is reset in the first branch, pcre_compile() failed with
118        "internal error: code overflow at offset...". This happened only when
119        the reset was to the original external option setting. (An optimization
120        abstracts leading options settings into an external setting, which was the
121        cause of this.)
123    3.  A pattern such as ^(?!a(*SKIP)b) where a negative assertion contained one
124        of the verbs SKIP, PRUNE, or COMMIT, did not work correctly. When the
125        assertion pattern did not match (meaning that the assertion was true), it
126        was incorrectly treated as false if the SKIP had been reached during the
127        matching. This also applied to assertions used as conditions.
129    4.  If an item that is not supported by pcre_dfa_exec() was encountered in an
130        assertion subpattern, including such a pattern used as a condition,
131        unpredictable results occurred, instead of the error return
134    5.  The C++ GlobalReplace function was not working like Perl for the special
135        situation when an empty string is matched. It now does the fancy magic
136        stuff that is necessary.
138    6.  In pcre_internal.h, obsolete includes to setjmp.h and stdarg.h have been
139        removed. (These were left over from very, very early versions of PCRE.)
141    7.  Some cosmetic changes to the code to make life easier when compiling it
142        as part of something else:
144        (a) Change DEBUG to PCRE_DEBUG.
146        (b) In pcre_compile(), rename the member of the "branch_chain" structure
147            called "current" as "current_branch", to prevent a collision with the
148            Linux macro when compiled as a kernel module.
150        (c) In pcre_study(), rename the function set_bit() as set_table_bit(), to
151            prevent a collision with the Linux macro when compiled as a kernel
152            module.
154    8.  In pcre_compile() there are some checks for integer overflows that used to
155        cast potentially large values to (double). This has been changed to that
156        when building, a check for int64_t is made, and if it is found, it is used
157        instead, thus avoiding the use of floating point arithmetic. (There is no
158        other use of FP in PCRE.) If int64_t is not found, the fallback is to
159        double.
161    9.  Added two casts to avoid signed/unsigned warnings from VS Studio Express
162        2005 (difference between two addresses compared to an unsigned value).
164    10. Change the standard AC_CHECK_LIB test for libbz2 in configure.ac to a
165        custom one, because of the following reported problem in Windows:
167          - libbz2 uses the Pascal calling convention (WINAPI) for the functions
168              under Win32.
169          - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",
170              therefore missing the function definition.
171          - The compiler thus generates a "C" signature for the test function.
172          - The linker fails to find the "C" function.
173          - PCRE fails to configure if asked to do so against libbz2.
175    11. When running libtoolize from libtool-2.2.6b as part of autogen.sh, these
176        messages were output:
178          Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
179          rerunning libtoolize, to keep the correct libtool macros in-tree.
180          Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
182        I have done both of these things.
184    12. Although pcre_dfa_exec() does not use nearly as much stack as pcre_exec()
185        most of the time, it *can* run out if it is given a pattern that contains a
186        runaway infinite recursion. I updated the discussion in the pcrestack man
187        page.
189    13. Now that we have gone to the x.xx style of version numbers, the minor
190        version may start with zero. Using 08 or 09 is a bad idea because users
191        might check the value of PCRE_MINOR in their code, and 08 or 09 may be
192        interpreted as invalid octal numbers. I've updated the previous comment in
193        configure.ac, and also added a check that gives an error if 08 or 09 are
194        used.
196    14. Change 8.00/11 was not quite complete: code had been accidentally omitted,
197        causing partial matching to fail when the end of the subject matched \W
198        in a UTF-8 pattern where \W was quantified with a minimum of 3.
200    15. There were some discrepancies between the declarations in pcre_internal.h
201        of _pcre_is_newline(), _pcre_was_newline(), and _pcre_valid_utf8() and
202        their definitions. The declarations used "const uschar *" and the
203        definitions used USPTR. Even though USPTR is normally defined as "const
204        unsigned char *" (and uschar is typedeffed as "unsigned char"), it was
205        reported that: "This difference in casting confuses some C++ compilers, for
206        example, SunCC recognizes above declarations as different functions and
207        generates broken code for hbpcre." I have changed the declarations to use
208        USPTR.
210    16. GNU libtool is named differently on some systems. The autogen.sh script now
211        tries several variants such as glibtoolize (MacOSX) and libtoolize1x
212        (FreeBSD).
214    17. Applied Craig's patch that fixes an HP aCC compile error in pcre 8.00
215        (strtoXX undefined when compiling pcrecpp.cc). The patch contains this
216        comment: "Figure out how to create a longlong from a string: strtoll and
217        equivalent. It's not enough to call AC_CHECK_FUNCS: hpux has a strtoll, for
218        instance, but it only takes 2 args instead of 3!"
220    18. A subtle bug concerned with back references has been fixed by a change of
221        specification, with a corresponding code fix. A pattern such as
222        ^(xa|=?\1a)+$ which contains a back reference inside the group to which it
223        refers, was giving matches when it shouldn't. For example, xa=xaaa would
224        match that pattern. Interestingly, Perl (at least up to 5.11.3) has the
225        same bug. Such groups have to be quantified to be useful, or contained
226        inside another quantified group. (If there's no repetition, the reference
227        can never match.) The problem arises because, having left the group and
228        moved on to the rest of the pattern, a later failure that backtracks into
229        the group uses the captured value from the final iteration of the group
230        rather than the correct earlier one. I have fixed this in PCRE by forcing
231        any group that contains a reference to itself to be an atomic group; that
232        is, there cannot be any backtracking into it once it has completed. This is
233        similar to recursive and subroutine calls.
236    Version 8.00 19-Oct-09
237    ----------------------
239    1.  The table for translating pcre_compile() error codes into POSIX error codes
240        was out-of-date, and there was no check on the pcre_compile() error code
241        being within the table. This could lead to an OK return being given in
242        error.
244    2.  Changed the call to open a subject file in pcregrep from fopen(pathname,
245        "r") to fopen(pathname, "rb"), which fixed a problem with some of the tests
246        in a Windows environment.
248    3.  The pcregrep --count option prints the count for each file even when it is
249        zero, as does GNU grep. However, pcregrep was also printing all files when
250        --files-with-matches was added. Now, when both options are given, it prints
251        counts only for those files that have at least one match. (GNU grep just
252        prints the file name in this circumstance, but including the count seems
253        more useful - otherwise, why use --count?) Also ensured that the
254        combination -clh just lists non-zero counts, with no names.
256    4.  The long form of the pcregrep -F option was incorrectly implemented as
257        --fixed_strings instead of --fixed-strings. This is an incompatible change,
258        but it seems right to fix it, and I didn't think it was worth preserving
259        the old behaviour.
261    5.  The command line items --regex=pattern and --regexp=pattern were not
262        recognized by pcregrep, which required --regex pattern or --regexp pattern
263        (with a space rather than an '='). The man page documented the '=' forms,
264        which are compatible with GNU grep; these now work.
266    6.  No libpcreposix.pc file was created for pkg-config; there was just
267        libpcre.pc and libpcrecpp.pc. The omission has been rectified.
269    7.  Added #ifndef SUPPORT_UCP into the pcre_ucd.c module, to reduce its size
270        when UCP support is not needed, by modifying the Python script that
271        generates it from Unicode data files. This should not matter if the module
272        is correctly used as a library, but I received one complaint about 50K of
273        unwanted data. My guess is that the person linked everything into his
274        program rather than using a library. Anyway, it does no harm.
276    8.  A pattern such as /\x{123}{2,2}+/8 was incorrectly compiled; the trigger
277        was a minimum greater than 1 for a wide character in a possessive
278        repetition. The same bug could also affect patterns like /(\x{ff}{0,2})*/8
279        which had an unlimited repeat of a nested, fixed maximum repeat of a wide
280        character. Chaos in the form of incorrect output or a compiling loop could
281        result.
283    9.  The restrictions on what a pattern can contain when partial matching is
284        requested for pcre_exec() have been removed. All patterns can now be
285        partially matched by this function. In addition, if there are at least two
286        slots in the offset vector, the offset of the earliest inspected character
287        for the match and the offset of the end of the subject are set in them when
288        PCRE_ERROR_PARTIAL is returned.
290    10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is
291        synonymous with PCRE_PARTIAL, for backwards compatibility, and
292        PCRE_PARTIAL_HARD, which causes a partial match to supersede a full match,
293        and may be more useful for multi-segment matching.
295    11. Partial matching with pcre_exec() is now more intuitive. A partial match
296        used to be given if ever the end of the subject was reached; now it is
297        given only if matching could not proceed because another character was
298        needed. This makes a difference in some odd cases such as Z(*FAIL) with the
299        string "Z", which now yields "no match" instead of "partial match". In the
300        case of pcre_dfa_exec(), "no match" is given if every matching path for the
301        final character ended with (*FAIL).
303    12. Restarting a match using pcre_dfa_exec() after a partial match did not work
304        if the pattern had a "must contain" character that was already found in the
305        earlier partial match, unless partial matching was again requested. For
306        example, with the pattern /dog.(body)?/, the "must contain" character is
307        "g". If the first part-match was for the string "dog", restarting with
308        "sbody" failed. This bug has been fixed.
310    13. The string returned by pcre_dfa_exec() after a partial match has been
311        changed so that it starts at the first inspected character rather than the
312        first character of the match. This makes a difference only if the pattern
313        starts with a lookbehind assertion or \b or \B (\K is not supported by
314        pcre_dfa_exec()). It's an incompatible change, but it makes the two
315        matching functions compatible, and I think it's the right thing to do.
317    14. Added a pcredemo man page, created automatically from the pcredemo.c file,
318        so that the demonstration program is easily available in environments where
319        PCRE has not been installed from source.
321    15. Arranged to add -DPCRE_STATIC to cflags in libpcre.pc, libpcreposix.cp,
322        libpcrecpp.pc and pcre-config when PCRE is not compiled as a shared
323        library.
325    16. Added REG_UNGREEDY to the pcreposix interface, at the request of a user.
326        It maps to PCRE_UNGREEDY. It is not, of course, POSIX-compatible, but it
327        is not the first non-POSIX option to be added. Clearly some people find
328        these options useful.
330    17. If a caller to the POSIX matching function regexec() passes a non-zero
331        value for nmatch with a NULL value for pmatch, the value of
332        nmatch is forced to zero.
334    18. RunGrepTest did not have a test for the availability of the -u option of
335        the diff command, as RunTest does. It now checks in the same way as
336        RunTest, and also checks for the -b option.
338    19. If an odd number of negated classes containing just a single character
339        interposed, within parentheses, between a forward reference to a named
340        subpattern and the definition of the subpattern, compilation crashed with
341        an internal error, complaining that it could not find the referenced
342        subpattern. An example of a crashing pattern is /(?&A)(([^m])(?<A>))/.
343        [The bug was that it was starting one character too far in when skipping
344        over the character class, thus treating the ] as data rather than
345        terminating the class. This meant it could skip too much.]
347    20. Added PCRE_NOTEMPTY_ATSTART in order to be able to correctly implement the
348        /g option in pcretest when the pattern contains \K, which makes it possible
349        to have an empty string match not at the start, even when the pattern is
350        anchored. Updated pcretest and pcredemo to use this option.
352    21. If the maximum number of capturing subpatterns in a recursion was greater
353        than the maximum at the outer level, the higher number was returned, but
354        with unset values at the outer level. The correct (outer level) value is
355        now given.
357    22. If (*ACCEPT) appeared inside capturing parentheses, previous releases of
358        PCRE did not set those parentheses (unlike Perl). I have now found a way to
359        make it do so. The string so far is captured, making this feature
360        compatible with Perl.
362    23. The tests have been re-organized, adding tests 11 and 12, to make it
363        possible to check the Perl 5.10 features against Perl 5.10.
365    24. Perl 5.10 allows subroutine calls in lookbehinds, as long as the subroutine
366        pattern matches a fixed length string. PCRE did not allow this; now it
367        does. Neither allows recursion.
369    25. I finally figured out how to implement a request to provide the minimum
370        length of subject string that was needed in order to match a given pattern.
371        (It was back references and recursion that I had previously got hung up
372        on.) This code has now been added to pcre_study(); it finds a lower bound
373        to the length of subject needed. It is not necessarily the greatest lower
374        bound, but using it to avoid searching strings that are too short does give
375        some useful speed-ups. The value is available to calling programs via
376        pcre_fullinfo().
378    26. While implementing 25, I discovered to my embarrassment that pcretest had
379        not been passing the result of pcre_study() to pcre_dfa_exec(), so the
380        study optimizations had never been tested with that matching function.
381        Oops. What is worse, even when it was passed study data, there was a bug in
382        pcre_dfa_exec() that meant it never actually used it. Double oops. There
383        were also very few tests of studied patterns with pcre_dfa_exec().
385    27. If (?| is used to create subpatterns with duplicate numbers, they are now
386        allowed to have the same name, even if PCRE_DUPNAMES is not set. However,
387        on the other side of the coin, they are no longer allowed to have different
388        names, because these cannot be distinguished in PCRE, and this has caused
389        confusion. (This is a difference from Perl.)
391    28. When duplicate subpattern names are present (necessarily with different
392        numbers, as required by 27 above), and a test is made by name in a
393        conditional pattern, either for a subpattern having been matched, or for
394        recursion in such a pattern, all the associated numbered subpatterns are
395        tested, and the overall condition is true if the condition is true for any
396        one of them. This is the way Perl works, and is also more like the way
397        testing by number works.
400    Version 7.9 11-Apr-09
401    ---------------------
403    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
404        (pcretest), all targets were linked against these libraries. This included
405        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
406        libraries. This caused unwanted dependencies to be created. This problem
407        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
408        pcretest is linked with readline.
410    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
411        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
412        moved outside it again, because FALSE and TRUE are already defined in AIX,
413        but BOOL is not.
415    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
416        PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
418    4.  The pcregrep documentation said spaces were inserted as well as colons (or
419        hyphens) following file names and line numbers when outputting matching
420        lines. This is not true; no spaces are inserted. I have also clarified the
421        wording for the --colour (or --color) option.
423    5.  In pcregrep, when --colour was used with -o, the list of matching strings
424        was not coloured; this is different to GNU grep, so I have changed it to be
425        the same.
427    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
428        each matching line was coloured. Now it goes on to look for further matches
429        of any of the test patterns, which is the same behaviour as GNU grep.
431    7.  A pattern that could match an empty string could cause pcregrep to loop; it
432        doesn't make sense to accept an empty string match in pcregrep, so I have
433        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
434        seems to be how GNU grep behaves.
436    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
437        start or after a newline", because the conditional assertion was not being
438        correctly handled. The rule now is that both the assertion and what follows
439        in the first alternative must satisfy the test.
441    9.  If auto-callout was enabled in a pattern with a conditional group whose
442        condition was an assertion, PCRE could crash during matching, both with
443        pcre_exec() and pcre_dfa_exec().
445    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
446        used for matching.
448    11. Unicode property support in character classes was not working for
449        characters (bytes) greater than 127 when not in UTF-8 mode.
451    12. Added the -M command line option to pcretest.
453    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
455    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
457    16. Added comments and documentation about mis-use of no_arg in the C++
458        wrapper.
460    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
461        from Martin Jerabek that uses macro names for all relevant character and
462        string constants.
464    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
465        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
466        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
467        these, but not everybody uses configure.
469    19. A conditional group that had only one branch was not being correctly
470        recognized as an item that could match an empty string. This meant that an
471        enclosing group might also not be so recognized, causing infinite looping
472        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
473        with the subject "ab", where knowledge that the repeated group can match
474        nothing is needed in order to break the loop.
476    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
477        exec(), but without supplying a callout function, matching went wrong.
479    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
480        leak if the size of the offset vector was greater than 30. When the vector
481        is smaller, the saved offsets during recursion go onto a local stack
482        vector, but for larger vectors malloc() is used. It was failing to free
483        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
484        error, in fact).
486    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
487        heapframe that is used only when UTF-8 support is enabled. This caused no
488        problem, but was untidy.
490    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
491        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
492        included within another project.
494    24. Steven Van Ingelgem's patches to add more options to the CMake support,
495        slightly modified by me:
497          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
498              not building pcregrep.
500          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
501              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
503    25. Forward references, both numeric and by name, in patterns that made use of
504        duplicate group numbers, could behave incorrectly or give incorrect errors,
505        because when scanning forward to find the reference group, PCRE was not
506        taking into account the duplicate group numbers. A pattern such as
507        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
509    26. Changed a few more instances of "const unsigned char *" to USPTR, making
510        the feature of a custom pointer more persuasive (as requested by a user).
512    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
513        pcretest.c, inside #ifndefs, because it seems they are sometimes already
514        pre-defined.
516    28. Added support for (*UTF8) at the start of a pattern.
518    29. Arrange for flags added by the "release type" setting in CMake to be shown
519        in the configuration summary.
522    Version 7.8 05-Sep-08
523    ---------------------
525    1.  Replaced UCP searching code with optimized version as implemented for Ad
526        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
527        stage table and inline lookup instead of a function, giving speed ups of 2
528        to 5 times on some simple patterns that I tested. Permission was given to
529        distribute the MultiStage2.py script that generates the tables (it's not in
530        the tarball, but is in the Subversion repository).
532    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
533        scripts.
535    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
536        a group with a zero qualifier. The result of the study could be incorrect,
537        or the function might crash, depending on the pattern.
539    4.  Caseless matching was not working for non-ASCII characters in back
540        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
541        It now works when Unicode Property Support is available.
543    5.  In pcretest, an escape such as \x{de} in the data was always generating
544        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
545        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
546        truncation.
548    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
550    7.  Added two (int) casts to pcregrep when printing the difference of two
551        pointers, in case they are 64-bit values.
553    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
554        test 2 if it fails.
556    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
557        and a #define of that name to empty if it is not externally set. This is to
558        allow users of MSVC to set it if necessary.
560    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
561        the convenience functions in the pcre_get.c source file.
563    11. An option change at the start of a pattern that had top-level alternatives
564        could cause overwriting and/or a crash. This command provoked a crash in
565        some environments:
567          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
569        This potential security problem was recorded as CVE-2008-2371.
571    12. For a pattern where the match had to start at the beginning or immediately
572        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
573        pcre_dfa_exec() could read past the end of the passed subject if there was
574        no match. To help with detecting such bugs (e.g. with valgrind), I modified
575        pcretest so that it places the subject at the end of its malloc-ed buffer.
577    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
578        exec() might read past the end of the data buffer in UTF-8 mode.
580    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
581        the data contained the byte 0x85 as part of a UTF-8 character within its
582        first line. This applied both to normal and DFA matching.
584    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
585        /^[^d]*?$/8 failed to match "abc".
587    16. Added a missing copyright notice to pcrecpp_internal.h.
589    17. Make it more clear in the documentation that values returned from
590        pcre_exec() in ovector are byte offsets, not character counts.
592    18. Tidied a few places to stop certain compilers from issuing warnings.
594    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
595        supplied by Stefan Weber. I made a further small update for 7.8 because
596        there is a change of source arrangements: the pcre_searchfuncs.c module is
597        replaced by pcre_ucd.c.
600    Version 7.7 07-May-08
601    ---------------------
603    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
604        a string to a long long, pretend we don't even have a long long." This is
605        done by checking for the strtoq, strtoll, and _strtoi64 functions.
607    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
608        pre-7.6 versions, which defined a global no_arg variable instead of putting
609        it in the RE class. (See also #8 below.)
611    3.  Remove a line of dead code, identified by coverity and reported by Nuno
612        Lopes.
614    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
616        (1) The include/exclude patterns were being applied to the whole pathnames
617            of files, instead of just to the final components.
619        (2) If there was more than one level of directory, the subdirectories were
620            skipped unless they satisfied the include/exclude conditions. This is
621            inconsistent with GNU grep (and could even be seen as contrary to the
622            pcregrep specification - which I improved to make it absolutely clear).
623            The action now is always to scan all levels of directory, and just
624            apply the include/exclude patterns to regular files.
626    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
627        --exclude_dir in the tests to avoid scanning .svn directories.
629    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
630        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
631        doesn't support NULs in patterns.
633    7.  Added some missing "const"s to declarations of static tables in
634        pcre_compile.c and pcre_dfa_exec.c.
636    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
637        caused by fix #2  above. (Subsequently also a second patch to fix the
638        first patch. And a third patch - this was a messy problem.)
640    9.  Applied Craig's patch to remove the use of push_back().
642    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
643        matching function regexec().
645    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
646        which, however, unlike Perl's \g{...}, are subroutine calls, not back
647        references. PCRE supports relative numbers with this syntax (I don't think
648        Oniguruma does).
650    12. Previously, a group with a zero repeat such as (...){0} was completely
651        omitted from the compiled regex. However, this means that if the group
652        was called as a subroutine from elsewhere in the pattern, things went wrong
653        (an internal error was given). Such groups are now left in the compiled
654        pattern, with a new opcode that causes them to be skipped at execution
655        time.
657    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
658        to the way PCRE behaves:
660        (a) A lone ] character is dis-allowed (Perl treats it as data).
662        (b) A back reference to an unmatched subpattern matches an empty string
663            (Perl fails the current match path).
665        (c) A data ] in a character class must be notated as \] because if the
666            first data character in a class is ], it defines an empty class. (In
667            Perl it is not possible to have an empty class.) The empty class []
668            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
669            The negative empty class [^] matches any one character, independently
670            of the DOTALL setting.
672    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
673        non-existent subpattern following a character class starting with ']' and
674        containing () gave an internal compiling error instead of "reference to
675        non-existent subpattern". Fortunately, when the pattern did exist, the
676        compiled code was correct. (When scanning forwards to check for the
677        existencd of the subpattern, it was treating the data ']' as terminating
678        the class, so got the count wrong. When actually compiling, the reference
679        was subsequently set up correctly.)
681    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
682        it was being rejected as not supported by pcre_dfa_exec(), even though
683        other assertions are supported. I have made pcre_dfa_exec() support
684        (*FAIL).
686    16. The implementation of 13c above involved the invention of a new opcode,
687        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
688        cannot be changed at match time, I realized I could make a small
689        improvement to matching performance by compiling OP_ALLANY instead of
690        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
691        on the OP_ANY path.
693    17. Compiling pcretest on Windows with readline support failed without the
694        following two fixes: (1) Make the unistd.h include conditional on
695        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
697    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
698        ncurses library to be included for pcretest when ReadLine support is
699        requested, but also to allow for it to be overridden. This patch came from
700        Daniel Bergström.
702    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
703        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
704        any errors with the current Unicode tables. Thanks to Peter Kankowski for
705        spotting this.
708    Version 7.6 28-Jan-08
709    ---------------------
711    1.  A character class containing a very large number of characters with
712        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
713        overflow.
715    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
716        HAVE_LONG_LONG is not defined.
718    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
719        bring them up to date and include new features. This patch includes:
721        - Fixed PH's badly added libz and libbz2 support.
722        - Fixed a problem with static linking.
723        - Added pcredemo. [But later removed - see 7 below.]
724        - Fixed dftables problem and added an option.
725        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
726            HAVE_LONG_LONG.
727        - Added readline support for pcretest.
728        - Added an listing of the option settings after cmake has run.
730    4.  A user submitted a patch to Makefile that makes it easy to create
731        "pcre.dll" under mingw when using Configure/Make. I added stuff to
732        Makefile.am that cause it to include this special target, without
733        affecting anything else. Note that the same mingw target plus all
734        the other distribution libraries and programs are now supported
735        when configuring with CMake (see 6 below) instead of with
736        Configure/Make.
738    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
739        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
740        exported in the Windows port". It has not yet been confirmed that the patch
741        solves the problem, but it does no harm.
743    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
744        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
745        with CMake, and also correct the comment about stack recursion.
747    7.  Remove the automatic building of pcredemo from the ./configure system and
748        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
749        of a program that users should build themselves after PCRE is installed, so
750        building it automatically is not really right. What is more, it gave
751        trouble in some build environments.
753    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
756    Version 7.5 10-Jan-08
757  ---------------------  ---------------------
759  1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'  1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
760      values in parens when parsing an RE using the C++ wrapper."      values in parens when parsing an RE using the C++ wrapper."
762  2.  Negative specials like \S did not work in character classes in UTF-8 mode.  2.  Negative specials like \S did not work in character classes in UTF-8 mode.
763      Characters greater than 255 were excluded from the class instead of being      Characters greater than 255 were excluded from the class instead of being
764      included.      included.
766  3.  The same bug as (2) above applied to negated POSIX classes such as  3.  The same bug as (2) above applied to negated POSIX classes such as
767      [:^space:].      [:^space:].
769  4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it  4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
770      defined or documented. It seems to have been a typo for PCRE_STATIC, so      defined or documented. It seems to have been a typo for PCRE_STATIC, so
771      I have changed it.      I have changed it.
773  5.  The construct (?&) was not diagnosed as a syntax error (it referenced the  5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
774      first named subpattern) and a construct such as (?&a) would reference the      first named subpattern) and a construct such as (?&a) would reference the
775      first named subpattern whose name started with "a" (in other words, the      first named subpattern whose name started with "a" (in other words, the
776      length check was missing). Both these problems are fixed. "Subpattern name      length check was missing). Both these problems are fixed. "Subpattern name
777      expected" is now given for (?&) (a zero-length name), and this patch also      expected" is now given for (?&) (a zero-length name), and this patch also
778      makes it give the same error for \k'' (previously it complained that that      makes it give the same error for \k'' (previously it complained that that
779      was a reference to a non-existent subpattern).      was a reference to a non-existent subpattern).
781  6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;  6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
782      this is right because (?- can be followed by option settings as well as by      this is right because (?- can be followed by option settings as well as by
783      digits. I have, however, made the messages clearer.      digits. I have, however, made the messages clearer.
785  7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns  7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
786      than the number used in the conditional) now cause a compile-time error.      than the number used in the conditional) now cause a compile-time error.
787      This is actually not compatible with Perl, which accepts such patterns, but      This is actually not compatible with Perl, which accepts such patterns, but
788      treats the conditional as always being FALSE (as PCRE used to), but it      treats the conditional as always being FALSE (as PCRE used to), but it
789      seems to me that giving a diagnostic is better.      seems to me that giving a diagnostic is better.
791  8.  Change "alphameric" to the more common word "alphanumeric" in comments  8.  Change "alphameric" to the more common word "alphanumeric" in comments
792      and messages.      and messages.
794  9.  Fix two occurrences of "backslash" in comments that should have been  9.  Fix two occurrences of "backslash" in comments that should have been
795      "backspace".      "backspace".
797  10. Remove two redundant lines of code that can never be obeyed (their function  10. Remove two redundant lines of code that can never be obeyed (their function
798      was moved elsewhere).      was moved elsewhere).
800  11. The program that makes PCRE's Unicode character property table had a bug  11. The program that makes PCRE's Unicode character property table had a bug
801      which caused it to generate incorrect table entries for sequences of      which caused it to generate incorrect table entries for sequences of
802      characters that have the same character type, but are in different scripts.      characters that have the same character type, but are in different scripts.
803      It amalgamated them into a single range, with the script of the first of      It amalgamated them into a single range, with the script of the first of
804      them. In other words, some characters were in the wrong script. There were      them. In other words, some characters were in the wrong script. There were
805      thirteen such cases, affecting characters in the following ranges:      thirteen such cases, affecting characters in the following ranges:
807        U+002b0 - U+002c1        U+002b0 - U+002c1
808        U+0060c - U+0060d        U+0060c - U+0060d
809        U+0061e - U+00612        U+0061e - U+00612
810        U+0064b - U+0065e        U+0064b - U+0065e
811        U+0074d - U+0076d        U+0074d - U+0076d
812        U+01800 - U+01805        U+01800 - U+01805
# Line 65  Version 7.5 12-Nov-07 Line 817  Version 7.5 12-Nov-07
817        U+03260 - U+0327f        U+03260 - U+0327f
818        U+0fb46 - U+0fbb1        U+0fb46 - U+0fbb1
819        U+10450 - U+1049d        U+10450 - U+1049d
821  12. The -o option (show only the matching part of a line) for pcregrep was not  12. The -o option (show only the matching part of a line) for pcregrep was not
822      compatible with GNU grep in that, if there was more than one match in a      compatible with GNU grep in that, if there was more than one match in a
823      line, it showed only the first of them. It now behaves in the same way as      line, it showed only the first of them. It now behaves in the same way as
824      GNU grep.      GNU grep.
826  13. If the -o and -v options were combined for pcregrep, it printed a blank  13. If the -o and -v options were combined for pcregrep, it printed a blank
827      line for every non-matching line. GNU grep prints nothing, and pcregrep now      line for every non-matching line. GNU grep prints nothing, and pcregrep now
828      does the same. The return code can be used to tell if there were any      does the same. The return code can be used to tell if there were any
829      non-matching lines.      non-matching lines.
831  14. The pattern (?=something)(?R) was not being diagnosed as a potentially  14. Added --file-offsets and --line-offsets to pcregrep.
833    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
834      infinitely looping recursion. The bug was that positive lookaheads were not      infinitely looping recursion. The bug was that positive lookaheads were not
835      being skipped when checking for a possible empty match (negative lookaheads      being skipped when checking for a possible empty match (negative lookaheads
836      and both kinds of lookbehind were skipped).      and both kinds of lookbehind were skipped).
838    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
839        inclusion of <windows.h> to before rather than after the definition of
840        INVALID_FILE_ATTRIBUTES (patch from David Byron).
842    17. Specifying a possessive quantifier with a specific limit for a Unicode
843        character property caused pcre_compile() to compile bad code, which led at
844        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
845        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
846        caused the error; without that there was no problem.
848    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
850    19. Added --enable-pcretest-libreadline.
852    20. In pcrecpp.cc, the variable 'count' was incremented twice in
853        RE::GlobalReplace(). As a result, the number of replacements returned was
854        double what it should be. I removed one of the increments, but Craig sent a
855        later patch that removed the other one (the right fix) and added unit tests
856        that check the return values (which was not done before).
858    21. Several CMake things:
860        (1) Arranged that, when cmake is used on Unix, the libraries end up with
861            the names libpcre and libpcreposix, not just pcre and pcreposix.
863        (2) The above change means that pcretest and pcregrep are now correctly
864            linked with the newly-built libraries, not previously installed ones.
868    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
869        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
870        UTF-8 newline character). The key issue is that the pattern starts .*;
871        this means that the match must be either at the beginning, or after a
872        newline. The bug was in the code for advancing after a failed match and
873        checking that the new position followed a newline. It was not taking
874        account of UTF-8 characters correctly.
876    23. PCRE was behaving differently from Perl in the way it recognized POSIX
877        character classes. PCRE was not treating the sequence [:...:] as a
878        character class unless the ... were all letters. Perl, however, seems to
879        allow any characters between [: and :], though of course it rejects as
880        unknown any "names" that contain non-letters, because all the known class
881        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
882        for example, whereas PCRE did not - it did not recognize a POSIX character
883        class. This seemed a bit dangerous, so the code has been changed to be
884        closer to Perl. The behaviour is not identical to Perl, because PCRE will
885        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
886        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
887        Perl does, and where it didn't before.
889    24. Rewrite so as to remove the single use of %n from pcregrep because in some
890        Windows environments %n is disabled by default.
893  Version 7.4 21-Sep-07  Version 7.4 21-Sep-07

Removed from v.282  
changed lines
  Added in v.519

  ViewVC Help
Powered by ViewVC 1.1.5