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

Diff of /code/trunk/ChangeLog

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

revision 483 by ph10, Mon Jan 4 16:19:17 2010 UTC revision 523 by ph10, Sun May 23 18:48:54 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    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).
34    
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.
39    
40    10. Added --line-buffered to pcregrep.
41    
42    11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was
43        studied, and the match started with a letter with a code point greater than
44        127 whose first byte was different to the first byte of the other case of
45        the letter, the other case of this starting letter was not recognized.
46    
47    12. pcreposix.c included pcre.h before including pcre_internal.h. This caused a
48        conflict in the definition of PCRE_EXP_DECL. I have removed the include of
49        pcre.h as pcre_internal.h includes pcre.h itself. (This may be a bit of
50        historical tidying that never got done.)
51    
52    13. If a pattern that was studied started with a repeated Unicode property
53        test, for example, \p{Nd}+, there was the theoretical possibility of
54        setting up an incorrect bitmap of starting bytes, but fortunately it could
55        not have actually happened in practice until change 8 above was made (it
56        added property types that matched character-matching opcodes).
57    
58    
59    
60    Version 8.02 19-Mar-2010
61    ------------------------
62    
63    1.  The Unicode data tables have been updated to Unicode 5.2.0.
64    
65    2.  Added the option --libs-cpp to pcre-config, but only when C++ support is
66        configured.
67    
68    3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the
69        original author of that file, following a query about its status.
70    
71    4.  On systems that do not have stdint.h (e.g. Solaris), check for and include
72        inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
73    
74    5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
75        quantifier applied to a forward-referencing subroutine call, could compile
76        incorrect code or give the error "internal error: previously-checked
77        referenced subpattern not found".
78    
79    6.  Both MS Visual Studio and Symbian OS have problems with initializing
80        variables to point to external functions. For these systems, therefore,
81        pcre_malloc etc. are now initialized to local functions that call the
82        relevant global functions.
83    
84    7.  There were two entries missing in the vectors called coptable and poptable
85        in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.
86        I've fixed the data, and added a kludgy way of testing at compile time that
87        the lengths are correct (equal to the number of opcodes).
88    
89    8.  Following on from 7, I added a similar kludge to check the length of the
90        eint vector in pcreposix.c.
91    
92    9.  Error texts for pcre_compile() are held as one long string to avoid too
93        much relocation at load time. To find a text, the string is searched,
94        counting zeros. There was no check for running off the end of the string,
95        which could happen if a new error number was added without updating the
96        string.
97    
98    10. \K gave a compile-time error if it appeared in a lookbehind assersion.
99    
100    11. \K was not working if it appeared in an atomic group or in a group that
101        was called as a "subroutine", or in an assertion. Perl 5.11 documents that
102        \K is "not well defined" if used in an assertion. PCRE now accepts it if
103        the assertion is positive, but not if it is negative.
104    
105    12. Change 11 fortuitously reduced the size of the stack frame used in the
106        "match()" function of pcre_exec.c by one pointer. Forthcoming
107        implementation of support for (*MARK) will need an extra pointer on the
108        stack; I have reserved it now, so that the stack frame size does not
109        decrease.
110    
111    13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other
112        item in branch that calls a recursion is a subroutine call - as in the
113        second branch in the above example - was incorrectly given the compile-
114        time error "recursive call could loop indefinitely" because pcre_compile()
115        was not correctly checking the subroutine for matching a non-empty string.
116    
117    14. The checks for overrunning compiling workspace could trigger after an
118        overrun had occurred. This is a "should never occur" error, but it can be
119        triggered by pathological patterns such as hundreds of nested parentheses.
120        The checks now trigger 100 bytes before the end of the workspace.
121    
122    15. Fix typo in configure.ac: "srtoq" should be "strtoq".
123    
124    
125    Version 8.01 19-Jan-2010
126    ------------------------
127    
128  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
129      particular, this includes all (DEFINE) patterns), a call to pcre_study()      particular, this includes all (*DEFINE) patterns), a call to pcre_study()
130      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
131      subpatterns).      subpatterns). This could cause incorrect "no match" results.
132    
133  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
134      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 182  Version 8.01 11-Dec-09
182      custom one, because of the following reported problem in Windows:      custom one, because of the following reported problem in Windows:
183    
184        - libbz2 uses the Pascal calling convention (WINAPI) for the functions        - libbz2 uses the Pascal calling convention (WINAPI) for the functions
185          under Win32.            under Win32.
186        - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",        - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",
187          therefore missing the function definition.            therefore missing the function definition.
188        - The compiler thus generates a "C" signature for the test function.        - The compiler thus generates a "C" signature for the test function.
189        - The linker fails to find the "C" function.        - The linker fails to find the "C" function.
190        - PCRE fails to configure if asked to do so against libbz2.        - PCRE fails to configure if asked to do so against libbz2.
191    
192  11. When running libtoolize from libtool-2.2.6b as part of autogen.sh, these  11. When running libtoolize from libtool-2.2.6b as part of autogen.sh, these
193      messages were output:      messages were output:
194    
195        Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and        Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
196        rerunning libtoolize, to keep the correct libtool macros in-tree.        rerunning libtoolize, to keep the correct libtool macros in-tree.
197        Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.        Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
198    
199      I have done both of these things.      I have done both of these things.
200    
201  12. Although pcre_dfa_exec() does not use nearly as much stack as pcre_exec()  12. Although pcre_dfa_exec() does not use nearly as much stack as pcre_exec()
202      most of the time, it *can* run out if it is given a pattern that contains a      most of the time, it *can* run out if it is given a pattern that contains a
203      runaway infinite recursion. I updated the discussion in the pcrestack man      runaway infinite recursion. I updated the discussion in the pcrestack man
204      page.      page.
205    
206  13. Now that we have gone to the x.xx style of version numbers, the minor  13. Now that we have gone to the x.xx style of version numbers, the minor
207      version may start with zero. Using 08 or 09 is a bad idea because users      version may start with zero. Using 08 or 09 is a bad idea because users
208      might check the value of PCRE_MINOR in their code, and 08 or 09 may be      might check the value of PCRE_MINOR in their code, and 08 or 09 may be
209      interpreted as invalid octal numbers. I've updated the previous comment in      interpreted as invalid octal numbers. I've updated the previous comment in
210      configure.ac, and also added a check that gives an error if 08 or 09 are      configure.ac, and also added a check that gives an error if 08 or 09 are
211      used.      used.
212    
213  14. Change 8.00/11 was not quite complete: code had been accidentally omitted,  14. Change 8.00/11 was not quite complete: code had been accidentally omitted,
214      causing partial matching to fail when the end of the subject matched \W      causing partial matching to fail when the end of the subject matched \W
215      in a UTF-8 pattern where \W was quantified with a minimum of 3.      in a UTF-8 pattern where \W was quantified with a minimum of 3.
216    
217  15. There were some discrepancies between the declarations in pcre_internal.h  15. There were some discrepancies between the declarations in pcre_internal.h
218      of _pcre_is_newline(), _pcre_was_newline(), and _pcre_valid_utf8() and      of _pcre_is_newline(), _pcre_was_newline(), and _pcre_valid_utf8() and
219      their definitions. The declarations used "const uschar *" and the      their definitions. The declarations used "const uschar *" and the
220      definitions used USPTR. Even though USPTR is normally defined as "const      definitions used USPTR. Even though USPTR is normally defined as "const
221      unsigned char *" (and uschar is typedeffed as "unsigned char"), it was      unsigned char *" (and uschar is typedeffed as "unsigned char"), it was
222      reported that: "This difference in casting confuses some C++ compilers, for      reported that: "This difference in casting confuses some C++ compilers, for
223      example, SunCC recognizes above declarations as different functions and      example, SunCC recognizes above declarations as different functions and
224      generates broken code for hbpcre." I have changed the declarations to use      generates broken code for hbpcre." I have changed the declarations to use
225      USPTR.      USPTR.
226    
227    16. GNU libtool is named differently on some systems. The autogen.sh script now
228        tries several variants such as glibtoolize (MacOSX) and libtoolize1x
229        (FreeBSD).
230    
231    17. Applied Craig's patch that fixes an HP aCC compile error in pcre 8.00
232        (strtoXX undefined when compiling pcrecpp.cc). The patch contains this
233        comment: "Figure out how to create a longlong from a string: strtoll and
234        equivalent. It's not enough to call AC_CHECK_FUNCS: hpux has a strtoll, for
235        instance, but it only takes 2 args instead of 3!"
236    
237    18. A subtle bug concerned with back references has been fixed by a change of
238        specification, with a corresponding code fix. A pattern such as
239        ^(xa|=?\1a)+$ which contains a back reference inside the group to which it
240        refers, was giving matches when it shouldn't. For example, xa=xaaa would
241        match that pattern. Interestingly, Perl (at least up to 5.11.3) has the
242        same bug. Such groups have to be quantified to be useful, or contained
243        inside another quantified group. (If there's no repetition, the reference
244        can never match.) The problem arises because, having left the group and
245        moved on to the rest of the pattern, a later failure that backtracks into
246        the group uses the captured value from the final iteration of the group
247        rather than the correct earlier one. I have fixed this in PCRE by forcing
248        any group that contains a reference to itself to be an atomic group; that
249        is, there cannot be any backtracking into it once it has completed. This is
250        similar to recursive and subroutine calls.
251    
252    
253  Version 8.00 19-Oct-09  Version 8.00 19-Oct-09

Legend:
Removed from v.483  
changed lines
  Added in v.523

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12