ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 473 by ph10, Sat Jan 2 12:40:07 2010 UTC revision 510 by ph10, Sat Mar 27 17:45:29 2010 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 8.01 11-Dec-09  Version 8.03 26-Mar-2010
5  ----------------------  ------------------------
7    1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and
8        THEN.
11    Version 8.02 19-Mar-2010
12    ------------------------
14    1.  The Unicode data tables have been updated to Unicode 5.2.0.
16    2.  Added the option --libs-cpp to pcre-config, but only when C++ support is
17        configured.
19    3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the
20        original author of that file, following a query about its status.
22    4.  On systems that do not have stdint.h (e.g. Solaris), check for and include
23        inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
25    5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
26        quantifier applied to a forward-referencing subroutine call, could compile
27        incorrect code or give the error "internal error: previously-checked
28        referenced subpattern not found".
30    6.  Both MS Visual Studio and Symbian OS have problems with initializing
31        variables to point to external functions. For these systems, therefore,
32        pcre_malloc etc. are now initialized to local functions that call the
33        relevant global functions.
35    7.  There were two entries missing in the vectors called coptable and poptable
36        in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.
37        I've fixed the data, and added a kludgy way of testing at compile time that
38        the lengths are correct (equal to the number of opcodes).
40    8.  Following on from 7, I added a similar kludge to check the length of the
41        eint vector in pcreposix.c.
43    9.  Error texts for pcre_compile() are held as one long string to avoid too
44        much relocation at load time. To find a text, the string is searched,
45        counting zeros. There was no check for running off the end of the string,
46        which could happen if a new error number was added without updating the
47        string.
49    10. \K gave a compile-time error if it appeared in a lookbehind assersion.
51    11. \K was not working if it appeared in an atomic group or in a group that
52        was called as a "subroutine", or in an assertion. Perl 5.11 documents that
53        \K is "not well defined" if used in an assertion. PCRE now accepts it if
54        the assertion is positive, but not if it is negative.
56    12. Change 11 fortuitously reduced the size of the stack frame used in the
57        "match()" function of pcre_exec.c by one pointer. Forthcoming
58        implementation of support for (*MARK) will need an extra pointer on the
59        stack; I have reserved it now, so that the stack frame size does not
60        decrease.
62    13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other
63        item in branch that calls a recursion is a subroutine call - as in the
64        second branch in the above example - was incorrectly given the compile-
65        time error "recursive call could loop indefinitely" because pcre_compile()
66        was not correctly checking the subroutine for matching a non-empty string.
68    14. The checks for overrunning compiling workspace could trigger after an
69        overrun had occurred. This is a "should never occur" error, but it can be
70        triggered by pathological patterns such as hundreds of nested parentheses.
71        The checks now trigger 100 bytes before the end of the workspace.
73    15. Fix typo in configure.ac: "srtoq" should be "strtoq".
76    Version 8.01 19-Jan-2010
77    ------------------------
79  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
80      particular, this includes all (DEFINE) patterns), a call to pcre_study()      particular, this includes all (*DEFINE) patterns), a call to pcre_study()
81      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
82      subpatterns).      subpatterns). This could cause incorrect "no match" results.
84  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
85      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 27  Version 8.01 11-Dec-09 Line 99  Version 8.01 11-Dec-09
99      unpredictable results occurred, instead of the error return      unpredictable results occurred, instead of the error return
102    5.  The C++ GlobalReplace function was not working like Perl for the special
103        situation when an empty string is matched. It now does the fancy magic
104        stuff that is necessary.
106    6.  In pcre_internal.h, obsolete includes to setjmp.h and stdarg.h have been
107        removed. (These were left over from very, very early versions of PCRE.)
109    7.  Some cosmetic changes to the code to make life easier when compiling it
110        as part of something else:
112        (a) Change DEBUG to PCRE_DEBUG.
114        (b) In pcre_compile(), rename the member of the "branch_chain" structure
115            called "current" as "current_branch", to prevent a collision with the
116            Linux macro when compiled as a kernel module.
118        (c) In pcre_study(), rename the function set_bit() as set_table_bit(), to
119            prevent a collision with the Linux macro when compiled as a kernel
120            module.
122    8.  In pcre_compile() there are some checks for integer overflows that used to
123        cast potentially large values to (double). This has been changed to that
124        when building, a check for int64_t is made, and if it is found, it is used
125        instead, thus avoiding the use of floating point arithmetic. (There is no
126        other use of FP in PCRE.) If int64_t is not found, the fallback is to
127        double.
129    9.  Added two casts to avoid signed/unsigned warnings from VS Studio Express
130        2005 (difference between two addresses compared to an unsigned value).
132    10. Change the standard AC_CHECK_LIB test for libbz2 in configure.ac to a
133        custom one, because of the following reported problem in Windows:
135          - libbz2 uses the Pascal calling convention (WINAPI) for the functions
136              under Win32.
137          - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",
138              therefore missing the function definition.
139          - The compiler thus generates a "C" signature for the test function.
140          - The linker fails to find the "C" function.
141          - PCRE fails to configure if asked to do so against libbz2.
143    11. When running libtoolize from libtool-2.2.6b as part of autogen.sh, these
144        messages were output:
146          Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
147          rerunning libtoolize, to keep the correct libtool macros in-tree.
148          Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
150        I have done both of these things.
152    12. Although pcre_dfa_exec() does not use nearly as much stack as pcre_exec()
153        most of the time, it *can* run out if it is given a pattern that contains a
154        runaway infinite recursion. I updated the discussion in the pcrestack man
155        page.
157    13. Now that we have gone to the x.xx style of version numbers, the minor
158        version may start with zero. Using 08 or 09 is a bad idea because users
159        might check the value of PCRE_MINOR in their code, and 08 or 09 may be
160        interpreted as invalid octal numbers. I've updated the previous comment in
161        configure.ac, and also added a check that gives an error if 08 or 09 are
162        used.
164    14. Change 8.00/11 was not quite complete: code had been accidentally omitted,
165        causing partial matching to fail when the end of the subject matched \W
166        in a UTF-8 pattern where \W was quantified with a minimum of 3.
168    15. There were some discrepancies between the declarations in pcre_internal.h
169        of _pcre_is_newline(), _pcre_was_newline(), and _pcre_valid_utf8() and
170        their definitions. The declarations used "const uschar *" and the
171        definitions used USPTR. Even though USPTR is normally defined as "const
172        unsigned char *" (and uschar is typedeffed as "unsigned char"), it was
173        reported that: "This difference in casting confuses some C++ compilers, for
174        example, SunCC recognizes above declarations as different functions and
175        generates broken code for hbpcre." I have changed the declarations to use
176        USPTR.
178    16. GNU libtool is named differently on some systems. The autogen.sh script now
179        tries several variants such as glibtoolize (MacOSX) and libtoolize1x
180        (FreeBSD).
182    17. Applied Craig's patch that fixes an HP aCC compile error in pcre 8.00
183        (strtoXX undefined when compiling pcrecpp.cc). The patch contains this
184        comment: "Figure out how to create a longlong from a string: strtoll and
185        equivalent. It's not enough to call AC_CHECK_FUNCS: hpux has a strtoll, for
186        instance, but it only takes 2 args instead of 3!"
188    18. A subtle bug concerned with back references has been fixed by a change of
189        specification, with a corresponding code fix. A pattern such as
190        ^(xa|=?\1a)+$ which contains a back reference inside the group to which it
191        refers, was giving matches when it shouldn't. For example, xa=xaaa would
192        match that pattern. Interestingly, Perl (at least up to 5.11.3) has the
193        same bug. Such groups have to be quantified to be useful, or contained
194        inside another quantified group. (If there's no repetition, the reference
195        can never match.) The problem arises because, having left the group and
196        moved on to the rest of the pattern, a later failure that backtracks into
197        the group uses the captured value from the final iteration of the group
198        rather than the correct earlier one. I have fixed this in PCRE by forcing
199        any group that contains a reference to itself to be an atomic group; that
200        is, there cannot be any backtracking into it once it has completed. This is
201        similar to recursive and subroutine calls.
204  Version 8.00 19-Oct-09  Version 8.00 19-Oct-09
205  ----------------------  ----------------------

Removed from v.473  
changed lines
  Added in v.510

  ViewVC Help
Powered by ViewVC 1.1.5