ViewVC logotype

Diff of /code/trunk/ChangeLog

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

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

Removed from v.269  
changed lines
  Added in v.510

  ViewVC Help
Powered by ViewVC 1.1.5