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

Diff of /code/trunk/ChangeLog

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

revision 484 by ph10, Mon Jan 4 17:11:54 2010 UTC revision 541 by ph10, Mon Jun 14 15:19:33 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-Jun-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        (#976).
47    
48    12. If a pattern that was studied started with a repeated Unicode property
49        test, for example, \p{Nd}+, there was the theoretical possibility of
50        setting up an incorrect bitmap of starting bytes, but fortunately it could
51        not have actually happened in practice until change 8 above was made (it
52        added property types that matched character-matching opcodes).
53    
54    13. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
55        possible starting bytes for non-anchored patterns.
56    
57    14. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes
58        \R, and also a number of cases that involve Unicode properties, both
59        explicit and implicit when PCRE_UCP is set.
60    
61    15. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8
62        input, it could crash or give wrong results if characters with values
63        greater than 0xc0 were present in the subject string. (Detail: it assumed
64        UTF-8 input when processing these items.)
65    
66    16. Added a lot of (int) casts to avoid compiler warnings in systems where
67        size_t is 64-bit (#991).
68    
69    17. Added a check for running out of memory when PCRE is compiled with
70        --disable-stack-for-recursion (#990).
71    
72    18. If the last data line in a file for pcretest does not have a newline on
73        the end, a newline was missing in the output.
74    
75    19. The default pcre_chartables.c file recognizes only ASCII characters (values
76        less than 128) in its various bitmaps. However, there is a facility for
77        generating tables according to the current locale when PCRE is compiled. It
78        turns out that in some environments, 0x85 and 0xa0, which are Unicode space
79        characters, are recognized by isspace() and therefore were getting set in
80        these tables, and indeed these tables seem to approximate to ISO 8859. This
81        caused a problem in UTF-8 mode when pcre_study() was used to create a list
82        of bytes that can start a match. For \s, it was including 0x85 and 0xa0,
83        which of course cannot start UTF-8 characters. I have changed the code so
84        that only real ASCII characters (less than 128) and the correct starting
85        bytes for UTF-8 encodings are set for characters greater than 127 when in
86        UTF-8 mode. (When PCRE_UCP is set - see 9 above - the code is different
87        altogether.)
88    
89    20. Added the /T option to pcretest so as to be able to run tests with non-
90        standard character tables, thus making it possible to include the tests
91        used for 19 above in the standard set of tests.
92    
93    
94    Version 8.02 19-Mar-2010
95    ------------------------
96    
97    1.  The Unicode data tables have been updated to Unicode 5.2.0.
98    
99    2.  Added the option --libs-cpp to pcre-config, but only when C++ support is
100        configured.
101    
102    3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the
103        original author of that file, following a query about its status.
104    
105    4.  On systems that do not have stdint.h (e.g. Solaris), check for and include
106        inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
107    
108    5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
109        quantifier applied to a forward-referencing subroutine call, could compile
110        incorrect code or give the error "internal error: previously-checked
111        referenced subpattern not found".
112    
113    6.  Both MS Visual Studio and Symbian OS have problems with initializing
114        variables to point to external functions. For these systems, therefore,
115        pcre_malloc etc. are now initialized to local functions that call the
116        relevant global functions.
117    
118    7.  There were two entries missing in the vectors called coptable and poptable
119        in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.
120        I've fixed the data, and added a kludgy way of testing at compile time that
121        the lengths are correct (equal to the number of opcodes).
122    
123    8.  Following on from 7, I added a similar kludge to check the length of the
124        eint vector in pcreposix.c.
125    
126    9.  Error texts for pcre_compile() are held as one long string to avoid too
127        much relocation at load time. To find a text, the string is searched,
128        counting zeros. There was no check for running off the end of the string,
129        which could happen if a new error number was added without updating the
130        string.
131    
132    10. \K gave a compile-time error if it appeared in a lookbehind assersion.
133    
134    11. \K was not working if it appeared in an atomic group or in a group that
135        was called as a "subroutine", or in an assertion. Perl 5.11 documents that
136        \K is "not well defined" if used in an assertion. PCRE now accepts it if
137        the assertion is positive, but not if it is negative.
138    
139    12. Change 11 fortuitously reduced the size of the stack frame used in the
140        "match()" function of pcre_exec.c by one pointer. Forthcoming
141        implementation of support for (*MARK) will need an extra pointer on the
142        stack; I have reserved it now, so that the stack frame size does not
143        decrease.
144    
145    13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other
146        item in branch that calls a recursion is a subroutine call - as in the
147        second branch in the above example - was incorrectly given the compile-
148        time error "recursive call could loop indefinitely" because pcre_compile()
149        was not correctly checking the subroutine for matching a non-empty string.
150    
151    14. The checks for overrunning compiling workspace could trigger after an
152        overrun had occurred. This is a "should never occur" error, but it can be
153        triggered by pathological patterns such as hundreds of nested parentheses.
154        The checks now trigger 100 bytes before the end of the workspace.
155    
156    15. Fix typo in configure.ac: "srtoq" should be "strtoq".
157    
158    
159    Version 8.01 19-Jan-2010
160    ------------------------
161    
162  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
163      particular, this includes all (DEFINE) patterns), a call to pcre_study()      particular, this includes all (*DEFINE) patterns), a call to pcre_study()
164      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
165      subpatterns).      subpatterns). This could cause incorrect "no match" results.
166    
167  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
168      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 216  Version 8.01 11-Dec-09
216      custom one, because of the following reported problem in Windows:      custom one, because of the following reported problem in Windows:
217    
218        - libbz2 uses the Pascal calling convention (WINAPI) for the functions        - libbz2 uses the Pascal calling convention (WINAPI) for the functions
219          under Win32.            under Win32.
220        - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",        - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",
221          therefore missing the function definition.            therefore missing the function definition.
222        - The compiler thus generates a "C" signature for the test function.        - The compiler thus generates a "C" signature for the test function.
223        - The linker fails to find the "C" function.        - The linker fails to find the "C" function.
224        - PCRE fails to configure if asked to do so against libbz2.        - PCRE fails to configure if asked to do so against libbz2.
225    
226  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
227      messages were output:      messages were output:
228    
229        Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and        Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
230        rerunning libtoolize, to keep the correct libtool macros in-tree.        rerunning libtoolize, to keep the correct libtool macros in-tree.
231        Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.        Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
232    
233      I have done both of these things.      I have done both of these things.
234    
235  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()
236      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
237      runaway infinite recursion. I updated the discussion in the pcrestack man      runaway infinite recursion. I updated the discussion in the pcrestack man
238      page.      page.
239    
240  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
241      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
242      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
243      interpreted as invalid octal numbers. I've updated the previous comment in      interpreted as invalid octal numbers. I've updated the previous comment in
244      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
245      used.      used.
246    
247  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,
248      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
249      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.
250    
251  15. There were some discrepancies between the declarations in pcre_internal.h  15. There were some discrepancies between the declarations in pcre_internal.h
252      of _pcre_is_newline(), _pcre_was_newline(), and _pcre_valid_utf8() and      of _pcre_is_newline(), _pcre_was_newline(), and _pcre_valid_utf8() and
253      their definitions. The declarations used "const uschar *" and the      their definitions. The declarations used "const uschar *" and the
254      definitions used USPTR. Even though USPTR is normally defined as "const      definitions used USPTR. Even though USPTR is normally defined as "const
255      unsigned char *" (and uschar is typedeffed as "unsigned char"), it was      unsigned char *" (and uschar is typedeffed as "unsigned char"), it was
256      reported that: "This difference in casting confuses some C++ compilers, for      reported that: "This difference in casting confuses some C++ compilers, for
257      example, SunCC recognizes above declarations as different functions and      example, SunCC recognizes above declarations as different functions and
258      generates broken code for hbpcre." I have changed the declarations to use      generates broken code for hbpcre." I have changed the declarations to use
259      USPTR.      USPTR.
260    
261  16. GNU libtool is named differently on some systems. The autogen.sh script now  16. GNU libtool is named differently on some systems. The autogen.sh script now
262      tries several variants such as glibtoolize (MacOSX) and libtoolize1x      tries several variants such as glibtoolize (MacOSX) and libtoolize1x
263      (FreeBSD).      (FreeBSD).
264    
265    17. Applied Craig's patch that fixes an HP aCC compile error in pcre 8.00
266        (strtoXX undefined when compiling pcrecpp.cc). The patch contains this
267        comment: "Figure out how to create a longlong from a string: strtoll and
268        equivalent. It's not enough to call AC_CHECK_FUNCS: hpux has a strtoll, for
269        instance, but it only takes 2 args instead of 3!"
270    
271    18. A subtle bug concerned with back references has been fixed by a change of
272        specification, with a corresponding code fix. A pattern such as
273        ^(xa|=?\1a)+$ which contains a back reference inside the group to which it
274        refers, was giving matches when it shouldn't. For example, xa=xaaa would
275        match that pattern. Interestingly, Perl (at least up to 5.11.3) has the
276        same bug. Such groups have to be quantified to be useful, or contained
277        inside another quantified group. (If there's no repetition, the reference
278        can never match.) The problem arises because, having left the group and
279        moved on to the rest of the pattern, a later failure that backtracks into
280        the group uses the captured value from the final iteration of the group
281        rather than the correct earlier one. I have fixed this in PCRE by forcing
282        any group that contains a reference to itself to be an atomic group; that
283        is, there cannot be any backtracking into it once it has completed. This is
284        similar to recursive and subroutine calls.
285    
286    
287  Version 8.00 19-Oct-09  Version 8.00 19-Oct-09

Legend:
Removed from v.484  
changed lines
  Added in v.541

  ViewVC Help
Powered by ViewVC 1.1.5