ViewVC logotype

Diff of /code/trunk/ChangeLog

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

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

Removed from v.197  
changed lines
  Added in v.493

  ViewVC Help
Powered by ViewVC 1.1.5