/[pcre]/code/branches/pcre16/ChangeLog
ViewVC logotype

Diff of /code/branches/pcre16/ChangeLog

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

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

Legend:
Removed from v.479  
changed lines
  Added in v.494

  ViewVC Help
Powered by ViewVC 1.1.5