ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 494 by ph10, Tue Mar 2 11:53:12 2010 UTC revision 538 by ph10, Wed Jun 9 19:30:57 2010 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 8.02 01-Mar-2010  Version 8.10 03-Jun-2010
5    ------------------------
7    1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and
8        THEN.
10    2.  (*ACCEPT) was not working when inside an atomic group.
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.
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.
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.)
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.
29    7.  Minor change to pcretest.c to avoid a compiler warning.
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).
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.
40    10. Added --line-buffered to pcregrep.
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).
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).
54    13. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
55        possible starting bytes for non-anchored patterns.
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.
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.)
66    16. Added a lot of (int) casts to avoid compiler warnings in systems where
67        size_t is 64-bit (#991).
69    17. Added a check for running out of memory when PCRE is compiled with
70        --disable-stack-for-recursion (#990).
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.
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. This caused a problem in UTF-8 mode when pcre_study() was
81        used to create a list of bytes that can start a match. For \s, it was
82        including 0x85 and 0xa0, which of course cannot start UTF-8 characters. I
83        have changed the code so that only real ASCII characters (less than 128)
84        are set in this case because the \s etc escapes are documented as
85        recognizing only ASCII characters. (When PCRE_UCP is set - see 9 above -
86        the code is different altogether.)
89    Version 8.02 19-Mar-2010
90  ------------------------  ------------------------
92  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.
94  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
95      configured.      configured.
97  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
98      original author of that file, following a query about its status.      original author of that file, following a query about its status.
100  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
101      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.
103    5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
104        quantifier applied to a forward-referencing subroutine call, could compile
105        incorrect code or give the error "internal error: previously-checked
106        referenced subpattern not found".
108    6.  Both MS Visual Studio and Symbian OS have problems with initializing
109        variables to point to external functions. For these systems, therefore,
110        pcre_malloc etc. are now initialized to local functions that call the
111        relevant global functions.
113    7.  There were two entries missing in the vectors called coptable and poptable
114        in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.
115        I've fixed the data, and added a kludgy way of testing at compile time that
116        the lengths are correct (equal to the number of opcodes).
118    8.  Following on from 7, I added a similar kludge to check the length of the
119        eint vector in pcreposix.c.
121    9.  Error texts for pcre_compile() are held as one long string to avoid too
122        much relocation at load time. To find a text, the string is searched,
123        counting zeros. There was no check for running off the end of the string,
124        which could happen if a new error number was added without updating the
125        string.
127    10. \K gave a compile-time error if it appeared in a lookbehind assersion.
129    11. \K was not working if it appeared in an atomic group or in a group that
130        was called as a "subroutine", or in an assertion. Perl 5.11 documents that
131        \K is "not well defined" if used in an assertion. PCRE now accepts it if
132        the assertion is positive, but not if it is negative.
134    12. Change 11 fortuitously reduced the size of the stack frame used in the
135        "match()" function of pcre_exec.c by one pointer. Forthcoming
136        implementation of support for (*MARK) will need an extra pointer on the
137        stack; I have reserved it now, so that the stack frame size does not
138        decrease.
140    13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other
141        item in branch that calls a recursion is a subroutine call - as in the
142        second branch in the above example - was incorrectly given the compile-
143        time error "recursive call could loop indefinitely" because pcre_compile()
144        was not correctly checking the subroutine for matching a non-empty string.
146    14. The checks for overrunning compiling workspace could trigger after an
147        overrun had occurred. This is a "should never occur" error, but it can be
148        triggered by pathological patterns such as hundreds of nested parentheses.
149        The checks now trigger 100 bytes before the end of the workspace.
151    15. Fix typo in configure.ac: "srtoq" should be "strtoq".
154  Version 8.01 19-Jan-2010  Version 8.01 19-Jan-2010
155  ------------------------  ------------------------

Removed from v.494  
changed lines
  Added in v.538

  ViewVC Help
Powered by ViewVC 1.1.5