ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 473 by ph10, Sat Jan 2 12:40:07 2010 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 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".
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  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()      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      computed the wrong minimum data length (which is of course zero for such
40      subpatterns).      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  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      the pattern is reset in the first branch, pcre_compile() failed with
# Line 27  Version 8.01 11-Dec-09 Line 57  Version 8.01 11-Dec-09
57      unpredictable results occurred, instead of the error return      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  Version 8.00 19-Oct-09
163  ----------------------  ----------------------

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

  ViewVC Help
Powered by ViewVC 1.1.5