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

Diff of /code/trunk/ChangeLog

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

revision 488 by ph10, Mon Jan 11 15:29:42 2010 UTC revision 537 by ph10, Tue Jun 8 15:28:26 2010 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.01 01-Jan-10  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    
76    
77    Version 8.02 19-Mar-2010
78    ------------------------
79    
80    1.  The Unicode data tables have been updated to Unicode 5.2.0.
81    
82    2.  Added the option --libs-cpp to pcre-config, but only when C++ support is
83        configured.
84    
85    3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the
86        original author of that file, following a query about its status.
87    
88    4.  On systems that do not have stdint.h (e.g. Solaris), check for and include
89        inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
90    
91    5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
92        quantifier applied to a forward-referencing subroutine call, could compile
93        incorrect code or give the error "internal error: previously-checked
94        referenced subpattern not found".
95    
96    6.  Both MS Visual Studio and Symbian OS have problems with initializing
97        variables to point to external functions. For these systems, therefore,
98        pcre_malloc etc. are now initialized to local functions that call the
99        relevant global functions.
100    
101    7.  There were two entries missing in the vectors called coptable and poptable
102        in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.
103        I've fixed the data, and added a kludgy way of testing at compile time that
104        the lengths are correct (equal to the number of opcodes).
105    
106    8.  Following on from 7, I added a similar kludge to check the length of the
107        eint vector in pcreposix.c.
108    
109    9.  Error texts for pcre_compile() are held as one long string to avoid too
110        much relocation at load time. To find a text, the string is searched,
111        counting zeros. There was no check for running off the end of the string,
112        which could happen if a new error number was added without updating the
113        string.
114    
115    10. \K gave a compile-time error if it appeared in a lookbehind assersion.
116    
117    11. \K was not working if it appeared in an atomic group or in a group that
118        was called as a "subroutine", or in an assertion. Perl 5.11 documents that
119        \K is "not well defined" if used in an assertion. PCRE now accepts it if
120        the assertion is positive, but not if it is negative.
121    
122    12. Change 11 fortuitously reduced the size of the stack frame used in the
123        "match()" function of pcre_exec.c by one pointer. Forthcoming
124        implementation of support for (*MARK) will need an extra pointer on the
125        stack; I have reserved it now, so that the stack frame size does not
126        decrease.
127    
128    13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other
129        item in branch that calls a recursion is a subroutine call - as in the
130        second branch in the above example - was incorrectly given the compile-
131        time error "recursive call could loop indefinitely" because pcre_compile()
132        was not correctly checking the subroutine for matching a non-empty string.
133    
134    14. The checks for overrunning compiling workspace could trigger after an
135        overrun had occurred. This is a "should never occur" error, but it can be
136        triggered by pathological patterns such as hundreds of nested parentheses.
137        The checks now trigger 100 bytes before the end of the workspace.
138    
139    15. Fix typo in configure.ac: "srtoq" should be "strtoq".
140    
141    
142    Version 8.01 19-Jan-2010
143    ------------------------
144    
145  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
146      particular, this includes all (DEFINE) patterns), a call to pcre_study()      particular, this includes all (*DEFINE) patterns), a call to pcre_study()
147      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
148      subpatterns).      subpatterns). This could cause incorrect "no match" results.
149    
150  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
151      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 01-Jan-10 Line 199  Version 8.01 01-Jan-10
199      custom one, because of the following reported problem in Windows:      custom one, because of the following reported problem in Windows:
200    
201        - libbz2 uses the Pascal calling convention (WINAPI) for the functions        - libbz2 uses the Pascal calling convention (WINAPI) for the functions
202          under Win32.            under Win32.
203        - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",        - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",
204          therefore missing the function definition.            therefore missing the function definition.
205        - The compiler thus generates a "C" signature for the test function.        - The compiler thus generates a "C" signature for the test function.
206        - The linker fails to find the "C" function.        - The linker fails to find the "C" function.
207        - PCRE fails to configure if asked to do so against libbz2.        - PCRE fails to configure if asked to do so against libbz2.

Legend:
Removed from v.488  
changed lines
  Added in v.537

  ViewVC Help
Powered by ViewVC 1.1.5