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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.461  
changed lines
  Added in v.491

  ViewVC Help
Powered by ViewVC 1.1.5