/[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 475 by ph10, Sat Jan 2 18:21:30 2010 UTC revision 489 by ph10, Tue Jan 19 16:42: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.01 19-Jan-2010
5  ----------------------  ------------------------
6    
7  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
8      particular, this includes all (DEFINE) patterns), a call to pcre_study()      particular, this includes all (*DEFINE) patterns), a call to pcre_study()
9      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
10      subpatterns).      subpatterns). This could cause incorrect "no match" results.
11    
12  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
13      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 26  Version 8.01 11-Dec-09 Line 26  Version 8.01 11-Dec-09
26      assertion subpattern, including such a pattern used as a condition,      assertion subpattern, including such a pattern used as a condition,
27      unpredictable results occurred, instead of the error return      unpredictable results occurred, instead of the error return
28      PCRE_ERROR_DFA_UITEM.      PCRE_ERROR_DFA_UITEM.
29    
30  5.  The C++ GlobalReplace function was not working like Perl for the special  5.  The C++ GlobalReplace function was not working like Perl for the special
31      situation when an empty string is matched. It now does the fancy magic      situation when an empty string is matched. It now does the fancy magic
32      stuff that is necessary.      stuff that is necessary.
33    
34  6.  In pcre_internal.h, obsolete includes to setjmp.h and stdarg.h have been  6.  In pcre_internal.h, obsolete includes to setjmp.h and stdarg.h have been
35      removed. (These were left over from very, very early versions of PCRE.)      removed. (These were left over from very, very early versions of PCRE.)
36    
37  7.  Some cosmetic changes to the code to make life easier when compiling it  7.  Some cosmetic changes to the code to make life easier when compiling it
38      as part of something else:      as part of something else:
39    
40      (a) Change DEBUG to PCRE_DEBUG.      (a) Change DEBUG to PCRE_DEBUG.
41    
42      (b) In pcre_compile(), rename the member of the "branch_chain" structure      (b) In pcre_compile(), rename the member of the "branch_chain" structure
43          called "current" as "current_branch", to prevent a collision with the          called "current" as "current_branch", to prevent a collision with the
44          Linux macro when compiled as a kernel module.          Linux macro when compiled as a kernel module.
45    
46      (c) In pcre_study(), rename the function set_bit() as set_table_bit(), to      (c) In pcre_study(), rename the function set_bit() as set_table_bit(), to
47          prevent a collision with the Linux macro when compiled as a kernel          prevent a collision with the Linux macro when compiled as a kernel
48          module.          module.
49    
50  8.  In pcre_compile() there are some checks for integer overflows that used to  8.  In pcre_compile() there are some checks for integer overflows that used to
51      cast potentially large values to (double). This has been changed to that      cast potentially large values to (double). This has been changed to that
52      when building, a check for int64_t is made, and if it is found, it is used      when building, a check for int64_t is made, and if it is found, it is used
53      instead, thus avoiding the use of floating point arithmetic. (There is no      instead, thus avoiding the use of floating point arithmetic. (There is no
54      other use of FP in PCRE.) If int64_t is not found, the fallback is to      other use of FP in PCRE.) If int64_t is not found, the fallback is to
55      double.      double.
56    
57    9.  Added two casts to avoid signed/unsigned warnings from VS Studio Express
58        2005 (difference between two addresses compared to an unsigned value).
59    
60    10. Change the standard AC_CHECK_LIB test for libbz2 in configure.ac to a
61        custom one, because of the following reported problem in Windows:
62    
63          - libbz2 uses the Pascal calling convention (WINAPI) for the functions
64              under Win32.
65          - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",
66              therefore missing the function definition.
67          - The compiler thus generates a "C" signature for the test function.
68          - The linker fails to find the "C" function.
69          - PCRE fails to configure if asked to do so against libbz2.
70    
71    11. When running libtoolize from libtool-2.2.6b as part of autogen.sh, these
72        messages were output:
73    
74          Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
75          rerunning libtoolize, to keep the correct libtool macros in-tree.
76          Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
77    
78        I have done both of these things.
79    
80    12. Although pcre_dfa_exec() does not use nearly as much stack as pcre_exec()
81        most of the time, it *can* run out if it is given a pattern that contains a
82        runaway infinite recursion. I updated the discussion in the pcrestack man
83        page.
84    
85    13. Now that we have gone to the x.xx style of version numbers, the minor
86        version may start with zero. Using 08 or 09 is a bad idea because users
87        might check the value of PCRE_MINOR in their code, and 08 or 09 may be
88        interpreted as invalid octal numbers. I've updated the previous comment in
89        configure.ac, and also added a check that gives an error if 08 or 09 are
90        used.
91    
92    14. Change 8.00/11 was not quite complete: code had been accidentally omitted,
93        causing partial matching to fail when the end of the subject matched \W
94        in a UTF-8 pattern where \W was quantified with a minimum of 3.
95    
96    15. There were some discrepancies between the declarations in pcre_internal.h
97        of _pcre_is_newline(), _pcre_was_newline(), and _pcre_valid_utf8() and
98        their definitions. The declarations used "const uschar *" and the
99        definitions used USPTR. Even though USPTR is normally defined as "const
100        unsigned char *" (and uschar is typedeffed as "unsigned char"), it was
101        reported that: "This difference in casting confuses some C++ compilers, for
102        example, SunCC recognizes above declarations as different functions and
103        generates broken code for hbpcre." I have changed the declarations to use
104        USPTR.
105    
106    16. GNU libtool is named differently on some systems. The autogen.sh script now
107        tries several variants such as glibtoolize (MacOSX) and libtoolize1x
108        (FreeBSD).
109    
110    17. Applied Craig's patch that fixes an HP aCC compile error in pcre 8.00
111        (strtoXX undefined when compiling pcrecpp.cc). The patch contains this
112        comment: "Figure out how to create a longlong from a string: strtoll and
113        equivalent. It's not enough to call AC_CHECK_FUNCS: hpux has a strtoll, for
114        instance, but it only takes 2 args instead of 3!"
115    
116    18. A subtle bug concerned with back references has been fixed by a change of
117        specification, with a corresponding code fix. A pattern such as
118        ^(xa|=?\1a)+$ which contains a back reference inside the group to which it
119        refers, was giving matches when it shouldn't. For example, xa=xaaa would
120        match that pattern. Interestingly, Perl (at least up to 5.11.3) has the
121        same bug. Such groups have to be quantified to be useful, or contained
122        inside another quantified group. (If there's no repetition, the reference
123        can never match.) The problem arises because, having left the group and
124        moved on to the rest of the pattern, a later failure that backtracks into
125        the group uses the captured value from the final iteration of the group
126        rather than the correct earlier one. I have fixed this in PCRE by forcing
127        any group that contains a reference to itself to be an atomic group; that
128        is, there cannot be any backtracking into it once it has completed. This is
129        similar to recursive and subroutine calls.
130    
131    
132  Version 8.00 19-Oct-09  Version 8.00 19-Oct-09

Legend:
Removed from v.475  
changed lines
  Added in v.489

  ViewVC Help
Powered by ViewVC 1.1.5