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

Diff of /code/trunk/ChangeLog

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

revision 496 by ph10, Tue Mar 2 19:11:17 2010 UTC revision 518 by ph10, Tue May 18 15:47:01 2010 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.02 01-Mar-2010  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    
41    Version 8.02 19-Mar-2010
42  ------------------------  ------------------------
43    
44  1.  The Unicode data tables have been updated to Unicode 5.2.0.  1.  The Unicode data tables have been updated to Unicode 5.2.0.
45    
46  2.  Added the option --libs-cpp to pcre-config, but only when C++ support is  2.  Added the option --libs-cpp to pcre-config, but only when C++ support is
47      configured.      configured.
48    
49  3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the  3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the
50      original author of that file, following a query about its status.      original author of that file, following a query about its status.
51    
52  4.  On systems that do not have stdint.h (e.g. Solaris), check for and include  4.  On systems that do not have stdint.h (e.g. Solaris), check for and include
53      inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.      inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
54    
55  5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive  5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
56      quantifier applied to a forward-referencing subroutine call, could compile      quantifier applied to a forward-referencing subroutine call, could compile
57      incorrect code or give the error "internal error: previously-checked      incorrect code or give the error "internal error: previously-checked
58      referenced subpattern not found".      referenced subpattern not found".
59    
60    6.  Both MS Visual Studio and Symbian OS have problems with initializing
61        variables to point to external functions. For these systems, therefore,
62        pcre_malloc etc. are now initialized to local functions that call the
63        relevant global functions.
64    
65    7.  There were two entries missing in the vectors called coptable and poptable
66        in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.
67        I've fixed the data, and added a kludgy way of testing at compile time that
68        the lengths are correct (equal to the number of opcodes).
69    
70    8.  Following on from 7, I added a similar kludge to check the length of the
71        eint vector in pcreposix.c.
72    
73    9.  Error texts for pcre_compile() are held as one long string to avoid too
74        much relocation at load time. To find a text, the string is searched,
75        counting zeros. There was no check for running off the end of the string,
76        which could happen if a new error number was added without updating the
77        string.
78    
79    10. \K gave a compile-time error if it appeared in a lookbehind assersion.
80    
81    11. \K was not working if it appeared in an atomic group or in a group that
82        was called as a "subroutine", or in an assertion. Perl 5.11 documents that
83        \K is "not well defined" if used in an assertion. PCRE now accepts it if
84        the assertion is positive, but not if it is negative.
85    
86    12. Change 11 fortuitously reduced the size of the stack frame used in the
87        "match()" function of pcre_exec.c by one pointer. Forthcoming
88        implementation of support for (*MARK) will need an extra pointer on the
89        stack; I have reserved it now, so that the stack frame size does not
90        decrease.
91    
92    13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other
93        item in branch that calls a recursion is a subroutine call - as in the
94        second branch in the above example - was incorrectly given the compile-
95        time error "recursive call could loop indefinitely" because pcre_compile()
96        was not correctly checking the subroutine for matching a non-empty string.
97    
98    14. The checks for overrunning compiling workspace could trigger after an
99        overrun had occurred. This is a "should never occur" error, but it can be
100        triggered by pathological patterns such as hundreds of nested parentheses.
101        The checks now trigger 100 bytes before the end of the workspace.
102    
103    15. Fix typo in configure.ac: "srtoq" should be "strtoq".
104    
105    
106  Version 8.01 19-Jan-2010  Version 8.01 19-Jan-2010
107  ------------------------  ------------------------

Legend:
Removed from v.496  
changed lines
  Added in v.518

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12