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

Legend:
Removed from v.473  
changed lines
  Added in v.516

  ViewVC Help
Powered by ViewVC 1.1.5