ViewVC logotype

Diff of /code/trunk/ChangeLog

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

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

Removed from v.223  
changed lines
  Added in v.498

  ViewVC Help
Powered by ViewVC 1.1.5