ViewVC logotype

Diff of /code/trunk/ChangeLog

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

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

Removed from v.289  
changed lines
  Added in v.523

  ViewVC Help
Powered by ViewVC 1.1.5