ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 471 by ph10, Fri Dec 11 15:11:55 2009 UTC revision 496 by ph10, Tue Mar 2 19:11:17 2010 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 8.01 11-Dec-09  Version 8.02 01-Mar-2010
5  ----------------------  ------------------------
7    1.  The Unicode data tables have been updated to Unicode 5.2.0.
9    2.  Added the option --libs-cpp to pcre-config, but only when C++ support is
10        configured.
12    3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the
13        original author of that file, following a query about its status.
15    4.  On systems that do not have stdint.h (e.g. Solaris), check for and include
16        inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
18    5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
19        quantifier applied to a forward-referencing subroutine call, could compile
20        incorrect code or give the error "internal error: previously-checked
21        referenced subpattern not found".
24    Version 8.01 19-Jan-2010
25    ------------------------
27  1.  If a pattern contained a conditional subpattern with only one branch (in  1.  If a pattern contained a conditional subpattern with only one branch (in
28      particular, this includes all (DEFINE) patterns), a call to pcre_study()      particular, this includes all (*DEFINE) patterns), a call to pcre_study()
29      computed the wrong minimum data length (which is of course zero for such      computed the wrong minimum data length (which is of course zero for such
30      subpatterns).      subpatterns). This could cause incorrect "no match" results.
32    2.  For patterns such as (?i)a(?-i)b|c where an option setting at the start of
33        the pattern is reset in the first branch, pcre_compile() failed with
34        "internal error: code overflow at offset...". This happened only when
35        the reset was to the original external option setting. (An optimization
36        abstracts leading options settings into an external setting, which was the
37        cause of this.)
39    3.  A pattern such as ^(?!a(*SKIP)b) where a negative assertion contained one
40        of the verbs SKIP, PRUNE, or COMMIT, did not work correctly. When the
41        assertion pattern did not match (meaning that the assertion was true), it
42        was incorrectly treated as false if the SKIP had been reached during the
43        matching. This also applied to assertions used as conditions.
45    4.  If an item that is not supported by pcre_dfa_exec() was encountered in an
46        assertion subpattern, including such a pattern used as a condition,
47        unpredictable results occurred, instead of the error return
50    5.  The C++ GlobalReplace function was not working like Perl for the special
51        situation when an empty string is matched. It now does the fancy magic
52        stuff that is necessary.
54    6.  In pcre_internal.h, obsolete includes to setjmp.h and stdarg.h have been
55        removed. (These were left over from very, very early versions of PCRE.)
57    7.  Some cosmetic changes to the code to make life easier when compiling it
58        as part of something else:
60        (a) Change DEBUG to PCRE_DEBUG.
62        (b) In pcre_compile(), rename the member of the "branch_chain" structure
63            called "current" as "current_branch", to prevent a collision with the
64            Linux macro when compiled as a kernel module.
66        (c) In pcre_study(), rename the function set_bit() as set_table_bit(), to
67            prevent a collision with the Linux macro when compiled as a kernel
68            module.
70    8.  In pcre_compile() there are some checks for integer overflows that used to
71        cast potentially large values to (double). This has been changed to that
72        when building, a check for int64_t is made, and if it is found, it is used
73        instead, thus avoiding the use of floating point arithmetic. (There is no
74        other use of FP in PCRE.) If int64_t is not found, the fallback is to
75        double.
77    9.  Added two casts to avoid signed/unsigned warnings from VS Studio Express
78        2005 (difference between two addresses compared to an unsigned value).
80    10. Change the standard AC_CHECK_LIB test for libbz2 in configure.ac to a
81        custom one, because of the following reported problem in Windows:
83          - libbz2 uses the Pascal calling convention (WINAPI) for the functions
84              under Win32.
85          - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",
86              therefore missing the function definition.
87          - The compiler thus generates a "C" signature for the test function.
88          - The linker fails to find the "C" function.
89          - PCRE fails to configure if asked to do so against libbz2.
91    11. When running libtoolize from libtool-2.2.6b as part of autogen.sh, these
92        messages were output:
94          Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
95          rerunning libtoolize, to keep the correct libtool macros in-tree.
96          Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
98        I have done both of these things.
100    12. Although pcre_dfa_exec() does not use nearly as much stack as pcre_exec()
101        most of the time, it *can* run out if it is given a pattern that contains a
102        runaway infinite recursion. I updated the discussion in the pcrestack man
103        page.
105    13. Now that we have gone to the x.xx style of version numbers, the minor
106        version may start with zero. Using 08 or 09 is a bad idea because users
107        might check the value of PCRE_MINOR in their code, and 08 or 09 may be
108        interpreted as invalid octal numbers. I've updated the previous comment in
109        configure.ac, and also added a check that gives an error if 08 or 09 are
110        used.
112    14. Change 8.00/11 was not quite complete: code had been accidentally omitted,
113        causing partial matching to fail when the end of the subject matched \W
114        in a UTF-8 pattern where \W was quantified with a minimum of 3.
116    15. There were some discrepancies between the declarations in pcre_internal.h
117        of _pcre_is_newline(), _pcre_was_newline(), and _pcre_valid_utf8() and
118        their definitions. The declarations used "const uschar *" and the
119        definitions used USPTR. Even though USPTR is normally defined as "const
120        unsigned char *" (and uschar is typedeffed as "unsigned char"), it was
121        reported that: "This difference in casting confuses some C++ compilers, for
122        example, SunCC recognizes above declarations as different functions and
123        generates broken code for hbpcre." I have changed the declarations to use
124        USPTR.
126    16. GNU libtool is named differently on some systems. The autogen.sh script now
127        tries several variants such as glibtoolize (MacOSX) and libtoolize1x
128        (FreeBSD).
130    17. Applied Craig's patch that fixes an HP aCC compile error in pcre 8.00
131        (strtoXX undefined when compiling pcrecpp.cc). The patch contains this
132        comment: "Figure out how to create a longlong from a string: strtoll and
133        equivalent. It's not enough to call AC_CHECK_FUNCS: hpux has a strtoll, for
134        instance, but it only takes 2 args instead of 3!"
136    18. A subtle bug concerned with back references has been fixed by a change of
137        specification, with a corresponding code fix. A pattern such as
138        ^(xa|=?\1a)+$ which contains a back reference inside the group to which it
139        refers, was giving matches when it shouldn't. For example, xa=xaaa would
140        match that pattern. Interestingly, Perl (at least up to 5.11.3) has the
141        same bug. Such groups have to be quantified to be useful, or contained
142        inside another quantified group. (If there's no repetition, the reference
143        can never match.) The problem arises because, having left the group and
144        moved on to the rest of the pattern, a later failure that backtracks into
145        the group uses the captured value from the final iteration of the group
146        rather than the correct earlier one. I have fixed this in PCRE by forcing
147        any group that contains a reference to itself to be an atomic group; that
148        is, there cannot be any backtracking into it once it has completed. This is
149        similar to recursive and subroutine calls.
152  Version 8.00 19-Oct-09  Version 8.00 19-Oct-09

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

  ViewVC Help
Powered by ViewVC 1.1.5