/[pcre]/code/trunk/ChangeLog
ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 480 by ph10, Sun Jan 3 17:29:59 2010 UTC revision 493 by ph10, Tue Mar 2 11:37:21 2010 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.01 11-Dec-09  Version 8.02 01-Mar-2010
5  ----------------------  ------------------------
6    
7    1.  The Unicode data tables have been updated to Unicode 5.2.0.
8    
9    2.  Added the option --libs-cpp to pcre-config, but only when C++ support is
10        configured.
11    
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.
14    
15    
16    Version 8.01 19-Jan-2010
17    ------------------------
18    
19  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
20      particular, this includes all (DEFINE) patterns), a call to pcre_study()      particular, this includes all (*DEFINE) patterns), a call to pcre_study()
21      computed the wrong minimum data length (which is of course zero for such      computed the wrong minimum data length (which is of course zero for such
22      subpatterns).      subpatterns). This could cause incorrect "no match" results.
23    
24  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
25      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 61  Version 8.01 11-Dec-09 Line 73  Version 8.01 11-Dec-09
73      custom one, because of the following reported problem in Windows:      custom one, because of the following reported problem in Windows:
74    
75        - libbz2 uses the Pascal calling convention (WINAPI) for the functions        - libbz2 uses the Pascal calling convention (WINAPI) for the functions
76          under Win32.            under Win32.
77        - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",        - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",
78          therefore missing the function definition.            therefore missing the function definition.
79        - The compiler thus generates a "C" signature for the test function.        - The compiler thus generates a "C" signature for the test function.
80        - The linker fails to find the "C" function.        - The linker fails to find the "C" function.
81        - PCRE fails to configure if asked to do so against libbz2.        - PCRE fails to configure if asked to do so against libbz2.
82    
83  11. When running libtoolize from libtool-2.2.6b as part of autogen.sh, these  11. When running libtoolize from libtool-2.2.6b as part of autogen.sh, these
84      messages were output:      messages were output:
85    
86        Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and        Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
87        rerunning libtoolize, to keep the correct libtool macros in-tree.        rerunning libtoolize, to keep the correct libtool macros in-tree.
88        Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.        Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
89    
90      I have done both of these things.      I have done both of these things.
91    
92  12. Although pcre_dfa_exec() does not use nearly as much stack as pcre_exec()  12. Although pcre_dfa_exec() does not use nearly as much stack as pcre_exec()
93      most of the time, it *can* run out if it is given a pattern that contains a      most of the time, it *can* run out if it is given a pattern that contains a
94      runaway infinite recursion. I updated the discussion in the pcrestack man      runaway infinite recursion. I updated the discussion in the pcrestack man
95      page.      page.
96    
97    13. Now that we have gone to the x.xx style of version numbers, the minor
98        version may start with zero. Using 08 or 09 is a bad idea because users
99        might check the value of PCRE_MINOR in their code, and 08 or 09 may be
100        interpreted as invalid octal numbers. I've updated the previous comment in
101        configure.ac, and also added a check that gives an error if 08 or 09 are
102        used.
103    
104    14. Change 8.00/11 was not quite complete: code had been accidentally omitted,
105        causing partial matching to fail when the end of the subject matched \W
106        in a UTF-8 pattern where \W was quantified with a minimum of 3.
107    
108    15. There were some discrepancies between the declarations in pcre_internal.h
109        of _pcre_is_newline(), _pcre_was_newline(), and _pcre_valid_utf8() and
110        their definitions. The declarations used "const uschar *" and the
111        definitions used USPTR. Even though USPTR is normally defined as "const
112        unsigned char *" (and uschar is typedeffed as "unsigned char"), it was
113        reported that: "This difference in casting confuses some C++ compilers, for
114        example, SunCC recognizes above declarations as different functions and
115        generates broken code for hbpcre." I have changed the declarations to use
116        USPTR.
117    
118    16. GNU libtool is named differently on some systems. The autogen.sh script now
119        tries several variants such as glibtoolize (MacOSX) and libtoolize1x
120        (FreeBSD).
121    
122    17. Applied Craig's patch that fixes an HP aCC compile error in pcre 8.00
123        (strtoXX undefined when compiling pcrecpp.cc). The patch contains this
124        comment: "Figure out how to create a longlong from a string: strtoll and
125        equivalent. It's not enough to call AC_CHECK_FUNCS: hpux has a strtoll, for
126        instance, but it only takes 2 args instead of 3!"
127    
128    18. A subtle bug concerned with back references has been fixed by a change of
129        specification, with a corresponding code fix. A pattern such as
130        ^(xa|=?\1a)+$ which contains a back reference inside the group to which it
131        refers, was giving matches when it shouldn't. For example, xa=xaaa would
132        match that pattern. Interestingly, Perl (at least up to 5.11.3) has the
133        same bug. Such groups have to be quantified to be useful, or contained
134        inside another quantified group. (If there's no repetition, the reference
135        can never match.) The problem arises because, having left the group and
136        moved on to the rest of the pattern, a later failure that backtracks into
137        the group uses the captured value from the final iteration of the group
138        rather than the correct earlier one. I have fixed this in PCRE by forcing
139        any group that contains a reference to itself to be an atomic group; that
140        is, there cannot be any backtracking into it once it has completed. This is
141        similar to recursive and subroutine calls.
142    
143    
144  Version 8.00 19-Oct-09  Version 8.00 19-Oct-09

Legend:
Removed from v.480  
changed lines
  Added in v.493

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12