ViewVC logotype

Diff of /code/trunk/ChangeLog

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

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

Removed from v.210  
changed lines
  Added in v.496

  ViewVC Help
Powered by ViewVC 1.1.5