ViewVC logotype

Diff of /code/trunk/ChangeLog

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

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

Removed from v.200  
changed lines
  Added in v.486

  ViewVC Help
Powered by ViewVC 1.1.5