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

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

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

  ViewVC Help
Powered by ViewVC 1.1.5