ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 205 by ph10, Fri Aug 3 13:18:33 2007 UTC revision 494 by ph10, Tue Mar 2 11:53:12 2010 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 7.3 05-Jul-07  Version 8.02 01-Mar-2010
5    ------------------------
7    1.  The Unicode data tables have been updated to Unicode 5.2.0.
9    2.  Added the option --libs-cpp to pcre-config, but only when C++ support is
10        configured.
12    3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the
13        original author of that file, following a query about its status.
15    4.  On systems that do not have stdint.h (e.g. Solaris), check for and include
16        inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
19    Version 8.01 19-Jan-2010
20    ------------------------
22    1.  If a pattern contained a conditional subpattern with only one branch (in
23        particular, this includes all (*DEFINE) patterns), a call to pcre_study()
24        computed the wrong minimum data length (which is of course zero for such
25        subpatterns). This could cause incorrect "no match" results.
27    2.  For patterns such as (?i)a(?-i)b|c where an option setting at the start of
28        the pattern is reset in the first branch, pcre_compile() failed with
29        "internal error: code overflow at offset...". This happened only when
30        the reset was to the original external option setting. (An optimization
31        abstracts leading options settings into an external setting, which was the
32        cause of this.)
34    3.  A pattern such as ^(?!a(*SKIP)b) where a negative assertion contained one
35        of the verbs SKIP, PRUNE, or COMMIT, did not work correctly. When the
36        assertion pattern did not match (meaning that the assertion was true), it
37        was incorrectly treated as false if the SKIP had been reached during the
38        matching. This also applied to assertions used as conditions.
40    4.  If an item that is not supported by pcre_dfa_exec() was encountered in an
41        assertion subpattern, including such a pattern used as a condition,
42        unpredictable results occurred, instead of the error return
45    5.  The C++ GlobalReplace function was not working like Perl for the special
46        situation when an empty string is matched. It now does the fancy magic
47        stuff that is necessary.
49    6.  In pcre_internal.h, obsolete includes to setjmp.h and stdarg.h have been
50        removed. (These were left over from very, very early versions of PCRE.)
52    7.  Some cosmetic changes to the code to make life easier when compiling it
53        as part of something else:
55        (a) Change DEBUG to PCRE_DEBUG.
57        (b) In pcre_compile(), rename the member of the "branch_chain" structure
58            called "current" as "current_branch", to prevent a collision with the
59            Linux macro when compiled as a kernel module.
61        (c) In pcre_study(), rename the function set_bit() as set_table_bit(), to
62            prevent a collision with the Linux macro when compiled as a kernel
63            module.
65    8.  In pcre_compile() there are some checks for integer overflows that used to
66        cast potentially large values to (double). This has been changed to that
67        when building, a check for int64_t is made, and if it is found, it is used
68        instead, thus avoiding the use of floating point arithmetic. (There is no
69        other use of FP in PCRE.) If int64_t is not found, the fallback is to
70        double.
72    9.  Added two casts to avoid signed/unsigned warnings from VS Studio Express
73        2005 (difference between two addresses compared to an unsigned value).
75    10. Change the standard AC_CHECK_LIB test for libbz2 in configure.ac to a
76        custom one, because of the following reported problem in Windows:
78          - libbz2 uses the Pascal calling convention (WINAPI) for the functions
79              under Win32.
80          - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",
81              therefore missing the function definition.
82          - The compiler thus generates a "C" signature for the test function.
83          - The linker fails to find the "C" function.
84          - PCRE fails to configure if asked to do so against libbz2.
86    11. When running libtoolize from libtool-2.2.6b as part of autogen.sh, these
87        messages were output:
89          Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
90          rerunning libtoolize, to keep the correct libtool macros in-tree.
91          Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
93        I have done both of these things.
95    12. Although pcre_dfa_exec() does not use nearly as much stack as pcre_exec()
96        most of the time, it *can* run out if it is given a pattern that contains a
97        runaway infinite recursion. I updated the discussion in the pcrestack man
98        page.
100    13. Now that we have gone to the x.xx style of version numbers, the minor
101        version may start with zero. Using 08 or 09 is a bad idea because users
102        might check the value of PCRE_MINOR in their code, and 08 or 09 may be
103        interpreted as invalid octal numbers. I've updated the previous comment in
104        configure.ac, and also added a check that gives an error if 08 or 09 are
105        used.
107    14. Change 8.00/11 was not quite complete: code had been accidentally omitted,
108        causing partial matching to fail when the end of the subject matched \W
109        in a UTF-8 pattern where \W was quantified with a minimum of 3.
111    15. There were some discrepancies between the declarations in pcre_internal.h
112        of _pcre_is_newline(), _pcre_was_newline(), and _pcre_valid_utf8() and
113        their definitions. The declarations used "const uschar *" and the
114        definitions used USPTR. Even though USPTR is normally defined as "const
115        unsigned char *" (and uschar is typedeffed as "unsigned char"), it was
116        reported that: "This difference in casting confuses some C++ compilers, for
117        example, SunCC recognizes above declarations as different functions and
118        generates broken code for hbpcre." I have changed the declarations to use
119        USPTR.
121    16. GNU libtool is named differently on some systems. The autogen.sh script now
122        tries several variants such as glibtoolize (MacOSX) and libtoolize1x
123        (FreeBSD).
125    17. Applied Craig's patch that fixes an HP aCC compile error in pcre 8.00
126        (strtoXX undefined when compiling pcrecpp.cc). The patch contains this
127        comment: "Figure out how to create a longlong from a string: strtoll and
128        equivalent. It's not enough to call AC_CHECK_FUNCS: hpux has a strtoll, for
129        instance, but it only takes 2 args instead of 3!"
131    18. A subtle bug concerned with back references has been fixed by a change of
132        specification, with a corresponding code fix. A pattern such as
133        ^(xa|=?\1a)+$ which contains a back reference inside the group to which it
134        refers, was giving matches when it shouldn't. For example, xa=xaaa would
135        match that pattern. Interestingly, Perl (at least up to 5.11.3) has the
136        same bug. Such groups have to be quantified to be useful, or contained
137        inside another quantified group. (If there's no repetition, the reference
138        can never match.) The problem arises because, having left the group and
139        moved on to the rest of the pattern, a later failure that backtracks into
140        the group uses the captured value from the final iteration of the group
141        rather than the correct earlier one. I have fixed this in PCRE by forcing
142        any group that contains a reference to itself to be an atomic group; that
143        is, there cannot be any backtracking into it once it has completed. This is
144        similar to recursive and subroutine calls.
147    Version 8.00 19-Oct-09
148    ----------------------
150    1.  The table for translating pcre_compile() error codes into POSIX error codes
151        was out-of-date, and there was no check on the pcre_compile() error code
152        being within the table. This could lead to an OK return being given in
153        error.
155    2.  Changed the call to open a subject file in pcregrep from fopen(pathname,
156        "r") to fopen(pathname, "rb"), which fixed a problem with some of the tests
157        in a Windows environment.
159    3.  The pcregrep --count option prints the count for each file even when it is
160        zero, as does GNU grep. However, pcregrep was also printing all files when
161        --files-with-matches was added. Now, when both options are given, it prints
162        counts only for those files that have at least one match. (GNU grep just
163        prints the file name in this circumstance, but including the count seems
164        more useful - otherwise, why use --count?) Also ensured that the
165        combination -clh just lists non-zero counts, with no names.
167    4.  The long form of the pcregrep -F option was incorrectly implemented as
168        --fixed_strings instead of --fixed-strings. This is an incompatible change,
169        but it seems right to fix it, and I didn't think it was worth preserving
170        the old behaviour.
172    5.  The command line items --regex=pattern and --regexp=pattern were not
173        recognized by pcregrep, which required --regex pattern or --regexp pattern
174        (with a space rather than an '='). The man page documented the '=' forms,
175        which are compatible with GNU grep; these now work.
177    6.  No libpcreposix.pc file was created for pkg-config; there was just
178        libpcre.pc and libpcrecpp.pc. The omission has been rectified.
180    7.  Added #ifndef SUPPORT_UCP into the pcre_ucd.c module, to reduce its size
181        when UCP support is not needed, by modifying the Python script that
182        generates it from Unicode data files. This should not matter if the module
183        is correctly used as a library, but I received one complaint about 50K of
184        unwanted data. My guess is that the person linked everything into his
185        program rather than using a library. Anyway, it does no harm.
187    8.  A pattern such as /\x{123}{2,2}+/8 was incorrectly compiled; the trigger
188        was a minimum greater than 1 for a wide character in a possessive
189        repetition. The same bug could also affect patterns like /(\x{ff}{0,2})*/8
190        which had an unlimited repeat of a nested, fixed maximum repeat of a wide
191        character. Chaos in the form of incorrect output or a compiling loop could
192        result.
194    9.  The restrictions on what a pattern can contain when partial matching is
195        requested for pcre_exec() have been removed. All patterns can now be
196        partially matched by this function. In addition, if there are at least two
197        slots in the offset vector, the offset of the earliest inspected character
198        for the match and the offset of the end of the subject are set in them when
199        PCRE_ERROR_PARTIAL is returned.
201    10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is
202        synonymous with PCRE_PARTIAL, for backwards compatibility, and
203        PCRE_PARTIAL_HARD, which causes a partial match to supersede a full match,
204        and may be more useful for multi-segment matching.
206    11. Partial matching with pcre_exec() is now more intuitive. A partial match
207        used to be given if ever the end of the subject was reached; now it is
208        given only if matching could not proceed because another character was
209        needed. This makes a difference in some odd cases such as Z(*FAIL) with the
210        string "Z", which now yields "no match" instead of "partial match". In the
211        case of pcre_dfa_exec(), "no match" is given if every matching path for the
212        final character ended with (*FAIL).
214    12. Restarting a match using pcre_dfa_exec() after a partial match did not work
215        if the pattern had a "must contain" character that was already found in the
216        earlier partial match, unless partial matching was again requested. For
217        example, with the pattern /dog.(body)?/, the "must contain" character is
218        "g". If the first part-match was for the string "dog", restarting with
219        "sbody" failed. This bug has been fixed.
221    13. The string returned by pcre_dfa_exec() after a partial match has been
222        changed so that it starts at the first inspected character rather than the
223        first character of the match. This makes a difference only if the pattern
224        starts with a lookbehind assertion or \b or \B (\K is not supported by
225        pcre_dfa_exec()). It's an incompatible change, but it makes the two
226        matching functions compatible, and I think it's the right thing to do.
228    14. Added a pcredemo man page, created automatically from the pcredemo.c file,
229        so that the demonstration program is easily available in environments where
230        PCRE has not been installed from source.
232    15. Arranged to add -DPCRE_STATIC to cflags in libpcre.pc, libpcreposix.cp,
233        libpcrecpp.pc and pcre-config when PCRE is not compiled as a shared
234        library.
236    16. Added REG_UNGREEDY to the pcreposix interface, at the request of a user.
237        It maps to PCRE_UNGREEDY. It is not, of course, POSIX-compatible, but it
238        is not the first non-POSIX option to be added. Clearly some people find
239        these options useful.
241    17. If a caller to the POSIX matching function regexec() passes a non-zero
242        value for nmatch with a NULL value for pmatch, the value of
243        nmatch is forced to zero.
245    18. RunGrepTest did not have a test for the availability of the -u option of
246        the diff command, as RunTest does. It now checks in the same way as
247        RunTest, and also checks for the -b option.
249    19. If an odd number of negated classes containing just a single character
250        interposed, within parentheses, between a forward reference to a named
251        subpattern and the definition of the subpattern, compilation crashed with
252        an internal error, complaining that it could not find the referenced
253        subpattern. An example of a crashing pattern is /(?&A)(([^m])(?<A>))/.
254        [The bug was that it was starting one character too far in when skipping
255        over the character class, thus treating the ] as data rather than
256        terminating the class. This meant it could skip too much.]
258    20. Added PCRE_NOTEMPTY_ATSTART in order to be able to correctly implement the
259        /g option in pcretest when the pattern contains \K, which makes it possible
260        to have an empty string match not at the start, even when the pattern is
261        anchored. Updated pcretest and pcredemo to use this option.
263    21. If the maximum number of capturing subpatterns in a recursion was greater
264        than the maximum at the outer level, the higher number was returned, but
265        with unset values at the outer level. The correct (outer level) value is
266        now given.
268    22. If (*ACCEPT) appeared inside capturing parentheses, previous releases of
269        PCRE did not set those parentheses (unlike Perl). I have now found a way to
270        make it do so. The string so far is captured, making this feature
271        compatible with Perl.
273    23. The tests have been re-organized, adding tests 11 and 12, to make it
274        possible to check the Perl 5.10 features against Perl 5.10.
276    24. Perl 5.10 allows subroutine calls in lookbehinds, as long as the subroutine
277        pattern matches a fixed length string. PCRE did not allow this; now it
278        does. Neither allows recursion.
280    25. I finally figured out how to implement a request to provide the minimum
281        length of subject string that was needed in order to match a given pattern.
282        (It was back references and recursion that I had previously got hung up
283        on.) This code has now been added to pcre_study(); it finds a lower bound
284        to the length of subject needed. It is not necessarily the greatest lower
285        bound, but using it to avoid searching strings that are too short does give
286        some useful speed-ups. The value is available to calling programs via
287        pcre_fullinfo().
289    26. While implementing 25, I discovered to my embarrassment that pcretest had
290        not been passing the result of pcre_study() to pcre_dfa_exec(), so the
291        study optimizations had never been tested with that matching function.
292        Oops. What is worse, even when it was passed study data, there was a bug in
293        pcre_dfa_exec() that meant it never actually used it. Double oops. There
294        were also very few tests of studied patterns with pcre_dfa_exec().
296    27. If (?| is used to create subpatterns with duplicate numbers, they are now
297        allowed to have the same name, even if PCRE_DUPNAMES is not set. However,
298        on the other side of the coin, they are no longer allowed to have different
299        names, because these cannot be distinguished in PCRE, and this has caused
300        confusion. (This is a difference from Perl.)
302    28. When duplicate subpattern names are present (necessarily with different
303        numbers, as required by 27 above), and a test is made by name in a
304        conditional pattern, either for a subpattern having been matched, or for
305        recursion in such a pattern, all the associated numbered subpatterns are
306        tested, and the overall condition is true if the condition is true for any
307        one of them. This is the way Perl works, and is also more like the way
308        testing by number works.
311    Version 7.9 11-Apr-09
312    ---------------------
314    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
315        (pcretest), all targets were linked against these libraries. This included
316        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
317        libraries. This caused unwanted dependencies to be created. This problem
318        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
319        pcretest is linked with readline.
321    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
322        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
323        moved outside it again, because FALSE and TRUE are already defined in AIX,
324        but BOOL is not.
326    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
327        PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
329    4.  The pcregrep documentation said spaces were inserted as well as colons (or
330        hyphens) following file names and line numbers when outputting matching
331        lines. This is not true; no spaces are inserted. I have also clarified the
332        wording for the --colour (or --color) option.
334    5.  In pcregrep, when --colour was used with -o, the list of matching strings
335        was not coloured; this is different to GNU grep, so I have changed it to be
336        the same.
338    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
339        each matching line was coloured. Now it goes on to look for further matches
340        of any of the test patterns, which is the same behaviour as GNU grep.
342    7.  A pattern that could match an empty string could cause pcregrep to loop; it
343        doesn't make sense to accept an empty string match in pcregrep, so I have
344        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
345        seems to be how GNU grep behaves.
347    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
348        start or after a newline", because the conditional assertion was not being
349        correctly handled. The rule now is that both the assertion and what follows
350        in the first alternative must satisfy the test.
352    9.  If auto-callout was enabled in a pattern with a conditional group whose
353        condition was an assertion, PCRE could crash during matching, both with
354        pcre_exec() and pcre_dfa_exec().
356    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
357        used for matching.
359    11. Unicode property support in character classes was not working for
360        characters (bytes) greater than 127 when not in UTF-8 mode.
362    12. Added the -M command line option to pcretest.
364    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
366    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
368    16. Added comments and documentation about mis-use of no_arg in the C++
369        wrapper.
371    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
372        from Martin Jerabek that uses macro names for all relevant character and
373        string constants.
375    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
376        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
377        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
378        these, but not everybody uses configure.
380    19. A conditional group that had only one branch was not being correctly
381        recognized as an item that could match an empty string. This meant that an
382        enclosing group might also not be so recognized, causing infinite looping
383        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
384        with the subject "ab", where knowledge that the repeated group can match
385        nothing is needed in order to break the loop.
387    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
388        exec(), but without supplying a callout function, matching went wrong.
390    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
391        leak if the size of the offset vector was greater than 30. When the vector
392        is smaller, the saved offsets during recursion go onto a local stack
393        vector, but for larger vectors malloc() is used. It was failing to free
394        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
395        error, in fact).
397    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
398        heapframe that is used only when UTF-8 support is enabled. This caused no
399        problem, but was untidy.
401    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
402        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
403        included within another project.
405    24. Steven Van Ingelgem's patches to add more options to the CMake support,
406        slightly modified by me:
408          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
409              not building pcregrep.
411          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
412              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
414    25. Forward references, both numeric and by name, in patterns that made use of
415        duplicate group numbers, could behave incorrectly or give incorrect errors,
416        because when scanning forward to find the reference group, PCRE was not
417        taking into account the duplicate group numbers. A pattern such as
418        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
420    26. Changed a few more instances of "const unsigned char *" to USPTR, making
421        the feature of a custom pointer more persuasive (as requested by a user).
423    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
424        pcretest.c, inside #ifndefs, because it seems they are sometimes already
425        pre-defined.
427    28. Added support for (*UTF8) at the start of a pattern.
429    29. Arrange for flags added by the "release type" setting in CMake to be shown
430        in the configuration summary.
433    Version 7.8 05-Sep-08
434    ---------------------
436    1.  Replaced UCP searching code with optimized version as implemented for Ad
437        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
438        stage table and inline lookup instead of a function, giving speed ups of 2
439        to 5 times on some simple patterns that I tested. Permission was given to
440        distribute the MultiStage2.py script that generates the tables (it's not in
441        the tarball, but is in the Subversion repository).
443    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
444        scripts.
446    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
447        a group with a zero qualifier. The result of the study could be incorrect,
448        or the function might crash, depending on the pattern.
450    4.  Caseless matching was not working for non-ASCII characters in back
451        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
452        It now works when Unicode Property Support is available.
454    5.  In pcretest, an escape such as \x{de} in the data was always generating
455        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
456        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
457        truncation.
459    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
461    7.  Added two (int) casts to pcregrep when printing the difference of two
462        pointers, in case they are 64-bit values.
464    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
465        test 2 if it fails.
467    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
468        and a #define of that name to empty if it is not externally set. This is to
469        allow users of MSVC to set it if necessary.
471    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
472        the convenience functions in the pcre_get.c source file.
474    11. An option change at the start of a pattern that had top-level alternatives
475        could cause overwriting and/or a crash. This command provoked a crash in
476        some environments:
478          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
480        This potential security problem was recorded as CVE-2008-2371.
482    12. For a pattern where the match had to start at the beginning or immediately
483        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
484        pcre_dfa_exec() could read past the end of the passed subject if there was
485        no match. To help with detecting such bugs (e.g. with valgrind), I modified
486        pcretest so that it places the subject at the end of its malloc-ed buffer.
488    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
489        exec() might read past the end of the data buffer in UTF-8 mode.
491    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
492        the data contained the byte 0x85 as part of a UTF-8 character within its
493        first line. This applied both to normal and DFA matching.
495    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
496        /^[^d]*?$/8 failed to match "abc".
498    16. Added a missing copyright notice to pcrecpp_internal.h.
500    17. Make it more clear in the documentation that values returned from
501        pcre_exec() in ovector are byte offsets, not character counts.
503    18. Tidied a few places to stop certain compilers from issuing warnings.
505    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
506        supplied by Stefan Weber. I made a further small update for 7.8 because
507        there is a change of source arrangements: the pcre_searchfuncs.c module is
508        replaced by pcre_ucd.c.
511    Version 7.7 07-May-08
512    ---------------------
514    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
515        a string to a long long, pretend we don't even have a long long." This is
516        done by checking for the strtoq, strtoll, and _strtoi64 functions.
518    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
519        pre-7.6 versions, which defined a global no_arg variable instead of putting
520        it in the RE class. (See also #8 below.)
522    3.  Remove a line of dead code, identified by coverity and reported by Nuno
523        Lopes.
525    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
527        (1) The include/exclude patterns were being applied to the whole pathnames
528            of files, instead of just to the final components.
530        (2) If there was more than one level of directory, the subdirectories were
531            skipped unless they satisfied the include/exclude conditions. This is
532            inconsistent with GNU grep (and could even be seen as contrary to the
533            pcregrep specification - which I improved to make it absolutely clear).
534            The action now is always to scan all levels of directory, and just
535            apply the include/exclude patterns to regular files.
537    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
538        --exclude_dir in the tests to avoid scanning .svn directories.
540    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
541        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
542        doesn't support NULs in patterns.
544    7.  Added some missing "const"s to declarations of static tables in
545        pcre_compile.c and pcre_dfa_exec.c.
547    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
548        caused by fix #2  above. (Subsequently also a second patch to fix the
549        first patch. And a third patch - this was a messy problem.)
551    9.  Applied Craig's patch to remove the use of push_back().
553    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
554        matching function regexec().
556    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
557        which, however, unlike Perl's \g{...}, are subroutine calls, not back
558        references. PCRE supports relative numbers with this syntax (I don't think
559        Oniguruma does).
561    12. Previously, a group with a zero repeat such as (...){0} was completely
562        omitted from the compiled regex. However, this means that if the group
563        was called as a subroutine from elsewhere in the pattern, things went wrong
564        (an internal error was given). Such groups are now left in the compiled
565        pattern, with a new opcode that causes them to be skipped at execution
566        time.
568    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
569        to the way PCRE behaves:
571        (a) A lone ] character is dis-allowed (Perl treats it as data).
573        (b) A back reference to an unmatched subpattern matches an empty string
574            (Perl fails the current match path).
576        (c) A data ] in a character class must be notated as \] because if the
577            first data character in a class is ], it defines an empty class. (In
578            Perl it is not possible to have an empty class.) The empty class []
579            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
580            The negative empty class [^] matches any one character, independently
581            of the DOTALL setting.
583    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
584        non-existent subpattern following a character class starting with ']' and
585        containing () gave an internal compiling error instead of "reference to
586        non-existent subpattern". Fortunately, when the pattern did exist, the
587        compiled code was correct. (When scanning forwards to check for the
588        existencd of the subpattern, it was treating the data ']' as terminating
589        the class, so got the count wrong. When actually compiling, the reference
590        was subsequently set up correctly.)
592    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
593        it was being rejected as not supported by pcre_dfa_exec(), even though
594        other assertions are supported. I have made pcre_dfa_exec() support
595        (*FAIL).
597    16. The implementation of 13c above involved the invention of a new opcode,
598        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
599        cannot be changed at match time, I realized I could make a small
600        improvement to matching performance by compiling OP_ALLANY instead of
601        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
602        on the OP_ANY path.
604    17. Compiling pcretest on Windows with readline support failed without the
605        following two fixes: (1) Make the unistd.h include conditional on
606        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
608    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
609        ncurses library to be included for pcretest when ReadLine support is
610        requested, but also to allow for it to be overridden. This patch came from
611        Daniel Bergström.
613    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
614        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
615        any errors with the current Unicode tables. Thanks to Peter Kankowski for
616        spotting this.
619    Version 7.6 28-Jan-08
620    ---------------------
622    1.  A character class containing a very large number of characters with
623        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
624        overflow.
626    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
627        HAVE_LONG_LONG is not defined.
629    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
630        bring them up to date and include new features. This patch includes:
632        - Fixed PH's badly added libz and libbz2 support.
633        - Fixed a problem with static linking.
634        - Added pcredemo. [But later removed - see 7 below.]
635        - Fixed dftables problem and added an option.
636        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
637            HAVE_LONG_LONG.
638        - Added readline support for pcretest.
639        - Added an listing of the option settings after cmake has run.
641    4.  A user submitted a patch to Makefile that makes it easy to create
642        "pcre.dll" under mingw when using Configure/Make. I added stuff to
643        Makefile.am that cause it to include this special target, without
644        affecting anything else. Note that the same mingw target plus all
645        the other distribution libraries and programs are now supported
646        when configuring with CMake (see 6 below) instead of with
647        Configure/Make.
649    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
650        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
651        exported in the Windows port". It has not yet been confirmed that the patch
652        solves the problem, but it does no harm.
654    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
655        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
656        with CMake, and also correct the comment about stack recursion.
658    7.  Remove the automatic building of pcredemo from the ./configure system and
659        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
660        of a program that users should build themselves after PCRE is installed, so
661        building it automatically is not really right. What is more, it gave
662        trouble in some build environments.
664    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
667    Version 7.5 10-Jan-08
668    ---------------------
670    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
671        values in parens when parsing an RE using the C++ wrapper."
673    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
674        Characters greater than 255 were excluded from the class instead of being
675        included.
677    3.  The same bug as (2) above applied to negated POSIX classes such as
678        [:^space:].
680    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
681        defined or documented. It seems to have been a typo for PCRE_STATIC, so
682        I have changed it.
684    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
685        first named subpattern) and a construct such as (?&a) would reference the
686        first named subpattern whose name started with "a" (in other words, the
687        length check was missing). Both these problems are fixed. "Subpattern name
688        expected" is now given for (?&) (a zero-length name), and this patch also
689        makes it give the same error for \k'' (previously it complained that that
690        was a reference to a non-existent subpattern).
692    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
693        this is right because (?- can be followed by option settings as well as by
694        digits. I have, however, made the messages clearer.
696    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
697        than the number used in the conditional) now cause a compile-time error.
698        This is actually not compatible with Perl, which accepts such patterns, but
699        treats the conditional as always being FALSE (as PCRE used to), but it
700        seems to me that giving a diagnostic is better.
702    8.  Change "alphameric" to the more common word "alphanumeric" in comments
703        and messages.
705    9.  Fix two occurrences of "backslash" in comments that should have been
706        "backspace".
708    10. Remove two redundant lines of code that can never be obeyed (their function
709        was moved elsewhere).
711    11. The program that makes PCRE's Unicode character property table had a bug
712        which caused it to generate incorrect table entries for sequences of
713        characters that have the same character type, but are in different scripts.
714        It amalgamated them into a single range, with the script of the first of
715        them. In other words, some characters were in the wrong script. There were
716        thirteen such cases, affecting characters in the following ranges:
718          U+002b0 - U+002c1
719          U+0060c - U+0060d
720          U+0061e - U+00612
721          U+0064b - U+0065e
722          U+0074d - U+0076d
723          U+01800 - U+01805
724          U+01d00 - U+01d77
725          U+01d9b - U+01dbf
726          U+0200b - U+0200f
727          U+030fc - U+030fe
728          U+03260 - U+0327f
729          U+0fb46 - U+0fbb1
730          U+10450 - U+1049d
732    12. The -o option (show only the matching part of a line) for pcregrep was not
733        compatible with GNU grep in that, if there was more than one match in a
734        line, it showed only the first of them. It now behaves in the same way as
735        GNU grep.
737    13. If the -o and -v options were combined for pcregrep, it printed a blank
738        line for every non-matching line. GNU grep prints nothing, and pcregrep now
739        does the same. The return code can be used to tell if there were any
740        non-matching lines.
742    14. Added --file-offsets and --line-offsets to pcregrep.
744    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
745        infinitely looping recursion. The bug was that positive lookaheads were not
746        being skipped when checking for a possible empty match (negative lookaheads
747        and both kinds of lookbehind were skipped).
749    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
750        inclusion of <windows.h> to before rather than after the definition of
751        INVALID_FILE_ATTRIBUTES (patch from David Byron).
753    17. Specifying a possessive quantifier with a specific limit for a Unicode
754        character property caused pcre_compile() to compile bad code, which led at
755        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
756        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
757        caused the error; without that there was no problem.
759    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
761    19. Added --enable-pcretest-libreadline.
763    20. In pcrecpp.cc, the variable 'count' was incremented twice in
764        RE::GlobalReplace(). As a result, the number of replacements returned was
765        double what it should be. I removed one of the increments, but Craig sent a
766        later patch that removed the other one (the right fix) and added unit tests
767        that check the return values (which was not done before).
769    21. Several CMake things:
771        (1) Arranged that, when cmake is used on Unix, the libraries end up with
772            the names libpcre and libpcreposix, not just pcre and pcreposix.
774        (2) The above change means that pcretest and pcregrep are now correctly
775            linked with the newly-built libraries, not previously installed ones.
779    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
780        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
781        UTF-8 newline character). The key issue is that the pattern starts .*;
782        this means that the match must be either at the beginning, or after a
783        newline. The bug was in the code for advancing after a failed match and
784        checking that the new position followed a newline. It was not taking
785        account of UTF-8 characters correctly.
787    23. PCRE was behaving differently from Perl in the way it recognized POSIX
788        character classes. PCRE was not treating the sequence [:...:] as a
789        character class unless the ... were all letters. Perl, however, seems to
790        allow any characters between [: and :], though of course it rejects as
791        unknown any "names" that contain non-letters, because all the known class
792        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
793        for example, whereas PCRE did not - it did not recognize a POSIX character
794        class. This seemed a bit dangerous, so the code has been changed to be
795        closer to Perl. The behaviour is not identical to Perl, because PCRE will
796        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
797        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
798        Perl does, and where it didn't before.
800    24. Rewrite so as to remove the single use of %n from pcregrep because in some
801        Windows environments %n is disabled by default.
804    Version 7.4 21-Sep-07
805    ---------------------
807    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
808        means that a class such as [\s] counted as "explicit reference to CR or
809        LF". That isn't really right - the whole point of the change was to try to
810        help when there was an actual mention of one of the two characters. So now
811        the change happens only if \r or \n (or a literal CR or LF) character is
812        encountered.
814    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
815        of both had grown to the point where there were only 3 bits left.
816        Fortunately, there was spare space in the data structure, and so I have
817        moved the internal flags into a new 16-bit field to free up more option
818        bits.
820    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
821        but did not set the internal JCHANGED flag - either of these is enough to
822        control the way the "get" function works - but the PCRE_INFO_JCHANGED
823        facility is supposed to tell if (?J) was ever used, so now (?J) at the
824        start sets both bits.
826    4.  Added options (at build time, compile time, exec time) to change \R from
827        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
829    5.  doc/pcresyntax.html was missing from the distribution.
831    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
832        compatibility, even though it is no longer used.
834    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
835        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
836        windows.h file is present (where different names are used). [This was
837        reversed later after testing - see 16 below.]
839    8.  Changed all #include <config.h> to #include "config.h". There were also
840        some further <pcre.h> cases that I changed to "pcre.h".
842    9.  When pcregrep was used with the --colour option, it missed the line ending
843        sequence off the lines that it output.
845    10. It was pointed out to me that arrays of string pointers cause lots of
846        relocations when a shared library is dynamically loaded. A technique of
847        using a single long string with a table of offsets can drastically reduce
848        these. I have refactored PCRE in four places to do this. The result is
849        dramatic:
851          Originally:                          290
852          After changing UCP table:            187
853          After changing error message table:   43
854          After changing table of "verbs"       36
855          After changing table of Posix names   22
857        Thanks to the folks working on Gregex for glib for this insight.
859    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
860        unicode-properties was also set.
862    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
864    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
865        checked only for CRLF.
867    14. Added casts to pcretest.c to avoid compiler warnings.
869    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
871    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
872        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
873        entirely. This removes changes made in 7 above.
875    17. The CMake files have been updated, and there is now more information about
876        building with CMake in the NON-UNIX-USE document.
879    Version 7.3 28-Aug-07
880  ---------------------  ---------------------
882   1. In the rejigging of the build system that eventually resulted in 7.1, the   1. In the rejigging of the build system that eventually resulted in 7.1, the
# Line 64  Version 7.3 05-Jul-07 Line 939  Version 7.3 05-Jul-07
939      dynamic way, which I have now done. The artificial limitation on group      dynamic way, which I have now done. The artificial limitation on group
940      length has been removed - we now have only the limit on the total length of      length has been removed - we now have only the limit on the total length of
941      the compiled pattern, which depends on the LINK_SIZE setting.      the compiled pattern, which depends on the LINK_SIZE setting.
943  10. Fixed a bug in the documentation for get/copy named substring when  10. Fixed a bug in the documentation for get/copy named substring when
944      duplicate names are permitted. If none of the named substrings are set, the      duplicate names are permitted. If none of the named substrings are set, the
945      functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an      functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an
946      empty string.      empty string.
948  11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E  11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E
949      instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,      instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,
950      because the ] is interpreted as the first data character and the      because the ] is interpreted as the first data character and the
951      terminating ] is not found. PCRE has been made compatible with Perl in this      terminating ] is not found. PCRE has been made compatible with Perl in this
952      regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could      regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could
953      cause memory overwriting.      cause memory overwriting.
955    10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty
956        string has been matched (to stop an infinite loop). It was not recognizing
957        a conditional subpattern that could match an empty string if that
958        subpattern was within another subpattern. For example, it looped when
959        trying to match  (((?(1)X|))*)  but it was OK with  ((?(1)X|)*)  where the
960        condition was not nested. This bug has been fixed.
962    12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack
963        past the start of the subject in the presence of bytes with the top bit
964        set, for example "\x8aBCD".
966    13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
967        (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
969    14. Optimized (?!) to (*FAIL).
971    15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
972        This restricts code points to be within the range 0 to 0x10FFFF, excluding
973        the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
974        full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
975        does: it's just the validity check that is more restrictive.
977    16. Inserted checks for integer overflows during escape sequence (backslash)
978        processing, and also fixed erroneous offset values for syntax errors during
979        backslash processing.
981    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
982        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
984    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
985        caused an overrun.
987    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
988        something other than just ASCII characters) inside a group that had an
989        unlimited repeat caused a loop at compile time (while checking to see
990        whether the group could match an empty string).
992    20. Debugging a pattern containing \p or \P could cause a crash. For example,
993        [\P{Any}] did so. (Error in the code for printing property names.)
995    21. An orphan \E inside a character class could cause a crash.
997    22. A repeated capturing bracket such as (A)? could cause a wild memory
998        reference during compilation.
1000    23. There are several functions in pcre_compile() that scan along a compiled
1001        expression for various reasons (e.g. to see if it's fixed length for look
1002        behind). There were bugs in these functions when a repeated \p or \P was
1003        present in the pattern. These operators have additional parameters compared
1004        with \d, etc, and these were not being taken into account when moving along
1005        the compiled data. Specifically:
1007        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
1008            length.
1010        (b) An item such as \pL+ within a repeated group could cause crashes or
1011            loops.
1013        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
1014            "reference to non-existent subpattern" error.
1016        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
1018    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
1019        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
1021    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
1023    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
1024        character were causing crashes (broken optimization).
1026    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
1027        \p or \P) caused a compile-time loop.
1029    28. More problems have arisen in unanchored patterns when CRLF is a valid line
1030        break. For example, the unstudied pattern [\r\n]A does not match the string
1031        "\r\nA" because change 7.0/46 below moves the current point on by two
1032        characters after failing to match at the start. However, the pattern \nA
1033        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
1034        the same is true. There doesn't seem any very clean way out of this, but
1035        what I have chosen to do makes the common cases work: PCRE now takes note
1036        of whether there can be an explicit match for \r or \n anywhere in the
1037        pattern, and if so, 7.0/46 no longer applies. As part of this change,
1038        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
1039        pattern has explicit CR or LF references.
1041    29. Added (*CR) etc for changing newline setting at start of pattern.
1044  Version 7.2 19-Jun-07  Version 7.2 19-Jun-07

Removed from v.205  
changed lines
  Added in v.494

  ViewVC Help
Powered by ViewVC 1.1.5