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

Diff of /code/trunk/ChangeLog

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

revision 478 by ph10, Sun Jan 3 16:05:13 2010 UTC revision 552 by ph10, Wed Oct 13 10:15:41 2010 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.01 11-Dec-09  Version 8.11 10-Oct-2010
5  ----------------------  ------------------------
6    
7    1.  (*THEN) was not working properly if there were untried alternatives prior
8        to it in the current branch. For example, in ((a|b)(*THEN)(*F)|c..) it
9        backtracked to try for "b" instead of moving to the next alternative branch
10        at the same level (in this case, to look for "c"). The Perl documentation
11        is clear that when (*THEN) is backtracked onto, it goes to the "next
12        alternative in the innermost enclosing group".
13    
14    2.  (*COMMIT) was not overriding (*THEN), as it does in Perl. In a pattern
15        such as   (A(*COMMIT)B(*THEN)C|D)  any failure after matching A should
16        result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and
17        (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides
18        (*THEN).
19    
20    3.  If \s appeared in a character class, it removed the VT character from
21        the class, even if it had been included by some previous item, for example
22        in [\x00-\xff\s]. (This was a bug related to the fact that VT is not part
23        of \s, but is part of the POSIX "space" class.)
24    
25    
26    Version 8.10 25-Jun-2010
27    ------------------------
28    
29    1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and
30        THEN.
31    
32    2.  (*ACCEPT) was not working when inside an atomic group.
33    
34    3.  Inside a character class, \B is treated as a literal by default, but
35        faulted if PCRE_EXTRA is set. This mimics Perl's behaviour (the -w option
36        causes the error). The code is unchanged, but I tidied the documentation.
37    
38    4.  Inside a character class, PCRE always treated \R and \X as literals,
39        whereas Perl faults them if its -w option is set. I have changed PCRE so
40        that it faults them when PCRE_EXTRA is set.
41    
42    5.  Added support for \N, which always matches any character other than
43        newline. (It is the same as "." when PCRE_DOTALL is not set.)
44    
45    6.  When compiling pcregrep with newer versions of gcc which may have
46        FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',
47        declared with attribute warn_unused_result" were given. Just casting the
48        result to (void) does not stop the warnings; a more elaborate fudge is
49        needed. I've used a macro to implement this.
50    
51    7.  Minor change to pcretest.c to avoid a compiler warning.
52    
53    8.  Added four artifical Unicode properties to help with an option to make
54        \s etc use properties (see next item). The new properties are: Xan
55        (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).
56    
57    9.  Added PCRE_UCP to make \b, \d, \s, \w, and certain POSIX character classes
58        use Unicode properties. (*UCP) at the start of a pattern can be used to set
59        this option. Modified pcretest to add /W to test this facility. Added
60        REG_UCP to make it available via the POSIX interface.
61    
62    10. Added --line-buffered to pcregrep.
63    
64    11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was
65        studied, and the match started with a letter with a code point greater than
66        127 whose first byte was different to the first byte of the other case of
67        the letter, the other case of this starting letter was not recognized
68        (#976).
69    
70    12. If a pattern that was studied started with a repeated Unicode property
71        test, for example, \p{Nd}+, there was the theoretical possibility of
72        setting up an incorrect bitmap of starting bytes, but fortunately it could
73        not have actually happened in practice until change 8 above was made (it
74        added property types that matched character-matching opcodes).
75    
76    13. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
77        possible starting bytes for non-anchored patterns.
78    
79    14. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes
80        \R, and also a number of cases that involve Unicode properties, both
81        explicit and implicit when PCRE_UCP is set.
82    
83    15. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8
84        input, it could crash or give wrong results if characters with values
85        greater than 0xc0 were present in the subject string. (Detail: it assumed
86        UTF-8 input when processing these items.)
87    
88    16. Added a lot of (int) casts to avoid compiler warnings in systems where
89        size_t is 64-bit (#991).
90    
91    17. Added a check for running out of memory when PCRE is compiled with
92        --disable-stack-for-recursion (#990).
93    
94    18. If the last data line in a file for pcretest does not have a newline on
95        the end, a newline was missing in the output.
96    
97    19. The default pcre_chartables.c file recognizes only ASCII characters (values
98        less than 128) in its various bitmaps. However, there is a facility for
99        generating tables according to the current locale when PCRE is compiled. It
100        turns out that in some environments, 0x85 and 0xa0, which are Unicode space
101        characters, are recognized by isspace() and therefore were getting set in
102        these tables, and indeed these tables seem to approximate to ISO 8859. This
103        caused a problem in UTF-8 mode when pcre_study() was used to create a list
104        of bytes that can start a match. For \s, it was including 0x85 and 0xa0,
105        which of course cannot start UTF-8 characters. I have changed the code so
106        that only real ASCII characters (less than 128) and the correct starting
107        bytes for UTF-8 encodings are set for characters greater than 127 when in
108        UTF-8 mode. (When PCRE_UCP is set - see 9 above - the code is different
109        altogether.)
110    
111    20. Added the /T option to pcretest so as to be able to run tests with non-
112        standard character tables, thus making it possible to include the tests
113        used for 19 above in the standard set of tests.
114    
115    21. A pattern such as (?&t)(?#()(?(DEFINE)(?<t>a)) which has a forward
116        reference to a subpattern the other side of a comment that contains an
117        opening parenthesis caused either an internal compiling error, or a
118        reference to the wrong subpattern.
119    
120    
121    Version 8.02 19-Mar-2010
122    ------------------------
123    
124    1.  The Unicode data tables have been updated to Unicode 5.2.0.
125    
126    2.  Added the option --libs-cpp to pcre-config, but only when C++ support is
127        configured.
128    
129    3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the
130        original author of that file, following a query about its status.
131    
132    4.  On systems that do not have stdint.h (e.g. Solaris), check for and include
133        inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
134    
135    5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
136        quantifier applied to a forward-referencing subroutine call, could compile
137        incorrect code or give the error "internal error: previously-checked
138        referenced subpattern not found".
139    
140    6.  Both MS Visual Studio and Symbian OS have problems with initializing
141        variables to point to external functions. For these systems, therefore,
142        pcre_malloc etc. are now initialized to local functions that call the
143        relevant global functions.
144    
145    7.  There were two entries missing in the vectors called coptable and poptable
146        in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.
147        I've fixed the data, and added a kludgy way of testing at compile time that
148        the lengths are correct (equal to the number of opcodes).
149    
150    8.  Following on from 7, I added a similar kludge to check the length of the
151        eint vector in pcreposix.c.
152    
153    9.  Error texts for pcre_compile() are held as one long string to avoid too
154        much relocation at load time. To find a text, the string is searched,
155        counting zeros. There was no check for running off the end of the string,
156        which could happen if a new error number was added without updating the
157        string.
158    
159    10. \K gave a compile-time error if it appeared in a lookbehind assersion.
160    
161    11. \K was not working if it appeared in an atomic group or in a group that
162        was called as a "subroutine", or in an assertion. Perl 5.11 documents that
163        \K is "not well defined" if used in an assertion. PCRE now accepts it if
164        the assertion is positive, but not if it is negative.
165    
166    12. Change 11 fortuitously reduced the size of the stack frame used in the
167        "match()" function of pcre_exec.c by one pointer. Forthcoming
168        implementation of support for (*MARK) will need an extra pointer on the
169        stack; I have reserved it now, so that the stack frame size does not
170        decrease.
171    
172    13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other
173        item in branch that calls a recursion is a subroutine call - as in the
174        second branch in the above example - was incorrectly given the compile-
175        time error "recursive call could loop indefinitely" because pcre_compile()
176        was not correctly checking the subroutine for matching a non-empty string.
177    
178    14. The checks for overrunning compiling workspace could trigger after an
179        overrun had occurred. This is a "should never occur" error, but it can be
180        triggered by pathological patterns such as hundreds of nested parentheses.
181        The checks now trigger 100 bytes before the end of the workspace.
182    
183    15. Fix typo in configure.ac: "srtoq" should be "strtoq".
184    
185    
186    Version 8.01 19-Jan-2010
187    ------------------------
188    
189  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
190      particular, this includes all (DEFINE) patterns), a call to pcre_study()      particular, this includes all (*DEFINE) patterns), a call to pcre_study()
191      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
192      subpatterns).      subpatterns). This could cause incorrect "no match" results.
193    
194  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
195      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 61  Version 8.01 11-Dec-09 Line 243  Version 8.01 11-Dec-09
243      custom one, because of the following reported problem in Windows:      custom one, because of the following reported problem in Windows:
244    
245        - libbz2 uses the Pascal calling convention (WINAPI) for the functions        - libbz2 uses the Pascal calling convention (WINAPI) for the functions
246          under Win32.            under Win32.
247        - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",        - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",
248          therefore missing the function definition.            therefore missing the function definition.
249        - The compiler thus generates a "C" signature for the test function.        - The compiler thus generates a "C" signature for the test function.
250        - The linker fails to find the "C" function.        - The linker fails to find the "C" function.
251        - PCRE fails to configure if asked to do so against libbz2.        - PCRE fails to configure if asked to do so against libbz2.
252    
253    11. When running libtoolize from libtool-2.2.6b as part of autogen.sh, these
254        messages were output:
255    
256          Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
257          rerunning libtoolize, to keep the correct libtool macros in-tree.
258          Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
259    
260        I have done both of these things.
261    
262    12. Although pcre_dfa_exec() does not use nearly as much stack as pcre_exec()
263        most of the time, it *can* run out if it is given a pattern that contains a
264        runaway infinite recursion. I updated the discussion in the pcrestack man
265        page.
266    
267    13. Now that we have gone to the x.xx style of version numbers, the minor
268        version may start with zero. Using 08 or 09 is a bad idea because users
269        might check the value of PCRE_MINOR in their code, and 08 or 09 may be
270        interpreted as invalid octal numbers. I've updated the previous comment in
271        configure.ac, and also added a check that gives an error if 08 or 09 are
272        used.
273    
274    14. Change 8.00/11 was not quite complete: code had been accidentally omitted,
275        causing partial matching to fail when the end of the subject matched \W
276        in a UTF-8 pattern where \W was quantified with a minimum of 3.
277    
278    15. There were some discrepancies between the declarations in pcre_internal.h
279        of _pcre_is_newline(), _pcre_was_newline(), and _pcre_valid_utf8() and
280        their definitions. The declarations used "const uschar *" and the
281        definitions used USPTR. Even though USPTR is normally defined as "const
282        unsigned char *" (and uschar is typedeffed as "unsigned char"), it was
283        reported that: "This difference in casting confuses some C++ compilers, for
284        example, SunCC recognizes above declarations as different functions and
285        generates broken code for hbpcre." I have changed the declarations to use
286        USPTR.
287    
288    16. GNU libtool is named differently on some systems. The autogen.sh script now
289        tries several variants such as glibtoolize (MacOSX) and libtoolize1x
290        (FreeBSD).
291    
292    17. Applied Craig's patch that fixes an HP aCC compile error in pcre 8.00
293        (strtoXX undefined when compiling pcrecpp.cc). The patch contains this
294        comment: "Figure out how to create a longlong from a string: strtoll and
295        equivalent. It's not enough to call AC_CHECK_FUNCS: hpux has a strtoll, for
296        instance, but it only takes 2 args instead of 3!"
297    
298    18. A subtle bug concerned with back references has been fixed by a change of
299        specification, with a corresponding code fix. A pattern such as
300        ^(xa|=?\1a)+$ which contains a back reference inside the group to which it
301        refers, was giving matches when it shouldn't. For example, xa=xaaa would
302        match that pattern. Interestingly, Perl (at least up to 5.11.3) has the
303        same bug. Such groups have to be quantified to be useful, or contained
304        inside another quantified group. (If there's no repetition, the reference
305        can never match.) The problem arises because, having left the group and
306        moved on to the rest of the pattern, a later failure that backtracks into
307        the group uses the captured value from the final iteration of the group
308        rather than the correct earlier one. I have fixed this in PCRE by forcing
309        any group that contains a reference to itself to be an atomic group; that
310        is, there cannot be any backtracking into it once it has completed. This is
311        similar to recursive and subroutine calls.
312    
313    
314  Version 8.00 19-Oct-09  Version 8.00 19-Oct-09
315  ----------------------  ----------------------

Legend:
Removed from v.478  
changed lines
  Added in v.552

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12