/[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 550 by ph10, Sun Oct 10 16:24:11 2010 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.01 01-Jan-10  Version 8.11 10-Oct-2010
5  ----------------------  ------------------------
6    
7    1.  (*THEN) was not working properly if there were untried alternatives prior
8        to it in the current branch. For example, in ((a|b)(*THEN)(*F)|c..) it
9        backtracked to try for "b" instead of moving to the next alternative branch
10        at the same level (in this case, to look for "c"). The Perl documentation
11        is clear that when (*THEN) is backtracked onto, it goes to the "next
12        alternative in the innermost enclosing group".
13    
14    
15    Version 8.10 25-Jun-2010
16    ------------------------
17    
18    1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and
19        THEN.
20    
21    2.  (*ACCEPT) was not working when inside an atomic group.
22    
23    3.  Inside a character class, \B is treated as a literal by default, but
24        faulted if PCRE_EXTRA is set. This mimics Perl's behaviour (the -w option
25        causes the error). The code is unchanged, but I tidied the documentation.
26    
27    4.  Inside a character class, PCRE always treated \R and \X as literals,
28        whereas Perl faults them if its -w option is set. I have changed PCRE so
29        that it faults them when PCRE_EXTRA is set.
30    
31    5.  Added support for \N, which always matches any character other than
32        newline. (It is the same as "." when PCRE_DOTALL is not set.)
33    
34    6.  When compiling pcregrep with newer versions of gcc which may have
35        FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',
36        declared with attribute warn_unused_result" were given. Just casting the
37        result to (void) does not stop the warnings; a more elaborate fudge is
38        needed. I've used a macro to implement this.
39    
40    7.  Minor change to pcretest.c to avoid a compiler warning.
41    
42    8.  Added four artifical Unicode properties to help with an option to make
43        \s etc use properties (see next item). The new properties are: Xan
44        (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).
45    
46    9.  Added PCRE_UCP to make \b, \d, \s, \w, and certain POSIX character classes
47        use Unicode properties. (*UCP) at the start of a pattern can be used to set
48        this option. Modified pcretest to add /W to test this facility. Added
49        REG_UCP to make it available via the POSIX interface.
50    
51    10. Added --line-buffered to pcregrep.
52    
53    11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was
54        studied, and the match started with a letter with a code point greater than
55        127 whose first byte was different to the first byte of the other case of
56        the letter, the other case of this starting letter was not recognized
57        (#976).
58    
59    12. If a pattern that was studied started with a repeated Unicode property
60        test, for example, \p{Nd}+, there was the theoretical possibility of
61        setting up an incorrect bitmap of starting bytes, but fortunately it could
62        not have actually happened in practice until change 8 above was made (it
63        added property types that matched character-matching opcodes).
64    
65    13. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
66        possible starting bytes for non-anchored patterns.
67    
68    14. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes
69        \R, and also a number of cases that involve Unicode properties, both
70        explicit and implicit when PCRE_UCP is set.
71    
72    15. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8
73        input, it could crash or give wrong results if characters with values
74        greater than 0xc0 were present in the subject string. (Detail: it assumed
75        UTF-8 input when processing these items.)
76    
77    16. Added a lot of (int) casts to avoid compiler warnings in systems where
78        size_t is 64-bit (#991).
79    
80    17. Added a check for running out of memory when PCRE is compiled with
81        --disable-stack-for-recursion (#990).
82    
83    18. If the last data line in a file for pcretest does not have a newline on
84        the end, a newline was missing in the output.
85    
86    19. The default pcre_chartables.c file recognizes only ASCII characters (values
87        less than 128) in its various bitmaps. However, there is a facility for
88        generating tables according to the current locale when PCRE is compiled. It
89        turns out that in some environments, 0x85 and 0xa0, which are Unicode space
90        characters, are recognized by isspace() and therefore were getting set in
91        these tables, and indeed these tables seem to approximate to ISO 8859. This
92        caused a problem in UTF-8 mode when pcre_study() was used to create a list
93        of bytes that can start a match. For \s, it was including 0x85 and 0xa0,
94        which of course cannot start UTF-8 characters. I have changed the code so
95        that only real ASCII characters (less than 128) and the correct starting
96        bytes for UTF-8 encodings are set for characters greater than 127 when in
97        UTF-8 mode. (When PCRE_UCP is set - see 9 above - the code is different
98        altogether.)
99    
100    20. Added the /T option to pcretest so as to be able to run tests with non-
101        standard character tables, thus making it possible to include the tests
102        used for 19 above in the standard set of tests.
103    
104    21. A pattern such as (?&t)(?#()(?(DEFINE)(?<t>a)) which has a forward
105        reference to a subpattern the other side of a comment that contains an
106        opening parenthesis caused either an internal compiling error, or a
107        reference to the wrong subpattern.
108    
109    
110    Version 8.02 19-Mar-2010
111    ------------------------
112    
113    1.  The Unicode data tables have been updated to Unicode 5.2.0.
114    
115    2.  Added the option --libs-cpp to pcre-config, but only when C++ support is
116        configured.
117    
118    3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the
119        original author of that file, following a query about its status.
120    
121    4.  On systems that do not have stdint.h (e.g. Solaris), check for and include
122        inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
123    
124    5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
125        quantifier applied to a forward-referencing subroutine call, could compile
126        incorrect code or give the error "internal error: previously-checked
127        referenced subpattern not found".
128    
129    6.  Both MS Visual Studio and Symbian OS have problems with initializing
130        variables to point to external functions. For these systems, therefore,
131        pcre_malloc etc. are now initialized to local functions that call the
132        relevant global functions.
133    
134    7.  There were two entries missing in the vectors called coptable and poptable
135        in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.
136        I've fixed the data, and added a kludgy way of testing at compile time that
137        the lengths are correct (equal to the number of opcodes).
138    
139    8.  Following on from 7, I added a similar kludge to check the length of the
140        eint vector in pcreposix.c.
141    
142    9.  Error texts for pcre_compile() are held as one long string to avoid too
143        much relocation at load time. To find a text, the string is searched,
144        counting zeros. There was no check for running off the end of the string,
145        which could happen if a new error number was added without updating the
146        string.
147    
148    10. \K gave a compile-time error if it appeared in a lookbehind assersion.
149    
150    11. \K was not working if it appeared in an atomic group or in a group that
151        was called as a "subroutine", or in an assertion. Perl 5.11 documents that
152        \K is "not well defined" if used in an assertion. PCRE now accepts it if
153        the assertion is positive, but not if it is negative.
154    
155    12. Change 11 fortuitously reduced the size of the stack frame used in the
156        "match()" function of pcre_exec.c by one pointer. Forthcoming
157        implementation of support for (*MARK) will need an extra pointer on the
158        stack; I have reserved it now, so that the stack frame size does not
159        decrease.
160    
161    13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other
162        item in branch that calls a recursion is a subroutine call - as in the
163        second branch in the above example - was incorrectly given the compile-
164        time error "recursive call could loop indefinitely" because pcre_compile()
165        was not correctly checking the subroutine for matching a non-empty string.
166    
167    14. The checks for overrunning compiling workspace could trigger after an
168        overrun had occurred. This is a "should never occur" error, but it can be
169        triggered by pathological patterns such as hundreds of nested parentheses.
170        The checks now trigger 100 bytes before the end of the workspace.
171    
172    15. Fix typo in configure.ac: "srtoq" should be "strtoq".
173    
174    
175    Version 8.01 19-Jan-2010
176    ------------------------
177    
178  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
179      particular, this includes all (DEFINE) patterns), a call to pcre_study()      particular, this includes all (*DEFINE) patterns), a call to pcre_study()
180      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
181      subpatterns).      subpatterns). This could cause incorrect "no match" results.
182    
183  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
184      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 232  Version 8.01 01-Jan-10
232      custom one, because of the following reported problem in Windows:      custom one, because of the following reported problem in Windows:
233    
234        - libbz2 uses the Pascal calling convention (WINAPI) for the functions        - libbz2 uses the Pascal calling convention (WINAPI) for the functions
235          under Win32.            under Win32.
236        - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",        - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",
237          therefore missing the function definition.            therefore missing the function definition.
238        - The compiler thus generates a "C" signature for the test function.        - The compiler thus generates a "C" signature for the test function.
239        - The linker fails to find the "C" function.        - The linker fails to find the "C" function.
240        - 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.550

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12