ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 474 by ph10, Sat Jan 2 16:30:46 2010 UTC revision 518 by ph10, Tue May 18 15:47:01 2010 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 8.01 11-Dec-09  Version 8.10 03 May-2010
5  ----------------------  ------------------------
7    1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and
8        THEN.
10    2.  (*ACCEPT) was not working when inside an atomic group.
12    3.  Inside a character class, \B is treated as a literal by default, but
13        faulted if PCRE_EXTRA is set. This mimics Perl's behaviour (the -w option
14        causes the error). The code is unchanged, but I tidied the documentation.
16    4.  Inside a character class, PCRE always treated \R and \X as literals,
17        whereas Perl faults them if its -w option is set. I have changed PCRE so
18        that it faults them when PCRE_EXTRA is set.
20    5.  Added support for \N, which always matches any character other than
21        newline. (It is the same as "." when PCRE_DOTALL is not set.)
23    6.  When compiling pcregrep with newer versions of gcc which may have
24        FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',
25        declared with attribute warn_unused_result" were given. Just casting the
26        result to (void) does not stop the warnings; a more elaborate fudge is
27        needed. I've used a macro to implement this.
29    7.  Minor change to pcretest.c to avoid a compiler warning.
31    8.  Added four artifical Unicode properties to help with an option to make
32        \s etc use properties (see next item). The new properties are: Xan
33        (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).
35    9.  Added PCRE_UCP to make \b, \d, \s, \w, and certain POSIX character classes
36        use Unicode properties. (*UCP) at the start of a pattern can be used to set
37        this option. Modified pcretest to add /W to test this facility. Added
38        REG_UCP to make it available via the POSIX interface.
41    Version 8.02 19-Mar-2010
42    ------------------------
44    1.  The Unicode data tables have been updated to Unicode 5.2.0.
46    2.  Added the option --libs-cpp to pcre-config, but only when C++ support is
47        configured.
49    3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the
50        original author of that file, following a query about its status.
52    4.  On systems that do not have stdint.h (e.g. Solaris), check for and include
53        inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
55    5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
56        quantifier applied to a forward-referencing subroutine call, could compile
57        incorrect code or give the error "internal error: previously-checked
58        referenced subpattern not found".
60    6.  Both MS Visual Studio and Symbian OS have problems with initializing
61        variables to point to external functions. For these systems, therefore,
62        pcre_malloc etc. are now initialized to local functions that call the
63        relevant global functions.
65    7.  There were two entries missing in the vectors called coptable and poptable
66        in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.
67        I've fixed the data, and added a kludgy way of testing at compile time that
68        the lengths are correct (equal to the number of opcodes).
70    8.  Following on from 7, I added a similar kludge to check the length of the
71        eint vector in pcreposix.c.
73    9.  Error texts for pcre_compile() are held as one long string to avoid too
74        much relocation at load time. To find a text, the string is searched,
75        counting zeros. There was no check for running off the end of the string,
76        which could happen if a new error number was added without updating the
77        string.
79    10. \K gave a compile-time error if it appeared in a lookbehind assersion.
81    11. \K was not working if it appeared in an atomic group or in a group that
82        was called as a "subroutine", or in an assertion. Perl 5.11 documents that
83        \K is "not well defined" if used in an assertion. PCRE now accepts it if
84        the assertion is positive, but not if it is negative.
86    12. Change 11 fortuitously reduced the size of the stack frame used in the
87        "match()" function of pcre_exec.c by one pointer. Forthcoming
88        implementation of support for (*MARK) will need an extra pointer on the
89        stack; I have reserved it now, so that the stack frame size does not
90        decrease.
92    13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other
93        item in branch that calls a recursion is a subroutine call - as in the
94        second branch in the above example - was incorrectly given the compile-
95        time error "recursive call could loop indefinitely" because pcre_compile()
96        was not correctly checking the subroutine for matching a non-empty string.
98    14. The checks for overrunning compiling workspace could trigger after an
99        overrun had occurred. This is a "should never occur" error, but it can be
100        triggered by pathological patterns such as hundreds of nested parentheses.
101        The checks now trigger 100 bytes before the end of the workspace.
103    15. Fix typo in configure.ac: "srtoq" should be "strtoq".
106    Version 8.01 19-Jan-2010
107    ------------------------
109  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
110      particular, this includes all (DEFINE) patterns), a call to pcre_study()      particular, this includes all (*DEFINE) patterns), a call to pcre_study()
111      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
112      subpatterns).      subpatterns). This could cause incorrect "no match" results.
114  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
115      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 128  Version 8.01 11-Dec-09
128      assertion subpattern, including such a pattern used as a condition,      assertion subpattern, including such a pattern used as a condition,
129      unpredictable results occurred, instead of the error return      unpredictable results occurred, instead of the error return
132  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
133      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
134      stuff that is necessary.      stuff that is necessary.
136    6.  In pcre_internal.h, obsolete includes to setjmp.h and stdarg.h have been
137        removed. (These were left over from very, very early versions of PCRE.)
139    7.  Some cosmetic changes to the code to make life easier when compiling it
140        as part of something else:
142        (a) Change DEBUG to PCRE_DEBUG.
144        (b) In pcre_compile(), rename the member of the "branch_chain" structure
145            called "current" as "current_branch", to prevent a collision with the
146            Linux macro when compiled as a kernel module.
148        (c) In pcre_study(), rename the function set_bit() as set_table_bit(), to
149            prevent a collision with the Linux macro when compiled as a kernel
150            module.
152    8.  In pcre_compile() there are some checks for integer overflows that used to
153        cast potentially large values to (double). This has been changed to that
154        when building, a check for int64_t is made, and if it is found, it is used
155        instead, thus avoiding the use of floating point arithmetic. (There is no
156        other use of FP in PCRE.) If int64_t is not found, the fallback is to
157        double.
159    9.  Added two casts to avoid signed/unsigned warnings from VS Studio Express
160        2005 (difference between two addresses compared to an unsigned value).
162    10. Change the standard AC_CHECK_LIB test for libbz2 in configure.ac to a
163        custom one, because of the following reported problem in Windows:
165          - libbz2 uses the Pascal calling convention (WINAPI) for the functions
166              under Win32.
167          - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",
168              therefore missing the function definition.
169          - The compiler thus generates a "C" signature for the test function.
170          - The linker fails to find the "C" function.
171          - PCRE fails to configure if asked to do so against libbz2.
173    11. When running libtoolize from libtool-2.2.6b as part of autogen.sh, these
174        messages were output:
176          Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
177          rerunning libtoolize, to keep the correct libtool macros in-tree.
178          Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
180        I have done both of these things.
182    12. Although pcre_dfa_exec() does not use nearly as much stack as pcre_exec()
183        most of the time, it *can* run out if it is given a pattern that contains a
184        runaway infinite recursion. I updated the discussion in the pcrestack man
185        page.
187    13. Now that we have gone to the x.xx style of version numbers, the minor
188        version may start with zero. Using 08 or 09 is a bad idea because users
189        might check the value of PCRE_MINOR in their code, and 08 or 09 may be
190        interpreted as invalid octal numbers. I've updated the previous comment in
191        configure.ac, and also added a check that gives an error if 08 or 09 are
192        used.
194    14. Change 8.00/11 was not quite complete: code had been accidentally omitted,
195        causing partial matching to fail when the end of the subject matched \W
196        in a UTF-8 pattern where \W was quantified with a minimum of 3.
198    15. There were some discrepancies between the declarations in pcre_internal.h
199        of _pcre_is_newline(), _pcre_was_newline(), and _pcre_valid_utf8() and
200        their definitions. The declarations used "const uschar *" and the
201        definitions used USPTR. Even though USPTR is normally defined as "const
202        unsigned char *" (and uschar is typedeffed as "unsigned char"), it was
203        reported that: "This difference in casting confuses some C++ compilers, for
204        example, SunCC recognizes above declarations as different functions and
205        generates broken code for hbpcre." I have changed the declarations to use
206        USPTR.
208    16. GNU libtool is named differently on some systems. The autogen.sh script now
209        tries several variants such as glibtoolize (MacOSX) and libtoolize1x
210        (FreeBSD).
212    17. Applied Craig's patch that fixes an HP aCC compile error in pcre 8.00
213        (strtoXX undefined when compiling pcrecpp.cc). The patch contains this
214        comment: "Figure out how to create a longlong from a string: strtoll and
215        equivalent. It's not enough to call AC_CHECK_FUNCS: hpux has a strtoll, for
216        instance, but it only takes 2 args instead of 3!"
218    18. A subtle bug concerned with back references has been fixed by a change of
219        specification, with a corresponding code fix. A pattern such as
220        ^(xa|=?\1a)+$ which contains a back reference inside the group to which it
221        refers, was giving matches when it shouldn't. For example, xa=xaaa would
222        match that pattern. Interestingly, Perl (at least up to 5.11.3) has the
223        same bug. Such groups have to be quantified to be useful, or contained
224        inside another quantified group. (If there's no repetition, the reference
225        can never match.) The problem arises because, having left the group and
226        moved on to the rest of the pattern, a later failure that backtracks into
227        the group uses the captured value from the final iteration of the group
228        rather than the correct earlier one. I have fixed this in PCRE by forcing
229        any group that contains a reference to itself to be an atomic group; that
230        is, there cannot be any backtracking into it once it has completed. This is
231        similar to recursive and subroutine calls.
234  Version 8.00 19-Oct-09  Version 8.00 19-Oct-09

Removed from v.474  
changed lines
  Added in v.518

  ViewVC Help
Powered by ViewVC 1.1.5