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

Diff of /code/trunk/ChangeLog

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

revision 213 by ph10, Wed Aug 15 11:34:14 2007 UTC revision 265 by ph10, Wed Nov 14 11:35:48 2007 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 7.3 09-Aug-07  Version 7.5 12-Nov-07
5    ---------------------
6    
7    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
8        values in parens when parsing an RE using the C++ wrapper."
9    
10    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
11        Characters greater than 255 were excluded from the class instead of being
12        included.
13    
14    3.  The same bug as (2) above applied to negated POSIX classes such as
15        [:^space:].
16    
17    
18    Version 7.4 21-Sep-07
19    ---------------------
20    
21    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
22        means that a class such as [\s] counted as "explicit reference to CR or
23        LF". That isn't really right - the whole point of the change was to try to
24        help when there was an actual mention of one of the two characters. So now
25        the change happens only if \r or \n (or a literal CR or LF) character is
26        encountered.
27    
28    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
29        of both had grown to the point where there were only 3 bits left.
30        Fortunately, there was spare space in the data structure, and so I have
31        moved the internal flags into a new 16-bit field to free up more option
32        bits.
33    
34    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
35        but did not set the internal JCHANGED flag - either of these is enough to
36        control the way the "get" function works - but the PCRE_INFO_JCHANGED
37        facility is supposed to tell if (?J) was ever used, so now (?J) at the
38        start sets both bits.
39    
40    4.  Added options (at build time, compile time, exec time) to change \R from
41        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
42    
43    5.  doc/pcresyntax.html was missing from the distribution.
44    
45    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
46        compatibility, even though it is no longer used.
47    
48    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
49        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
50        windows.h file is present (where different names are used). [This was
51        reversed later after testing - see 16 below.]
52    
53    8.  Changed all #include <config.h> to #include "config.h". There were also
54        some further <pcre.h> cases that I changed to "pcre.h".
55    
56    9.  When pcregrep was used with the --colour option, it missed the line ending
57        sequence off the lines that it output.
58    
59    10. It was pointed out to me that arrays of string pointers cause lots of
60        relocations when a shared library is dynamically loaded. A technique of
61        using a single long string with a table of offsets can drastically reduce
62        these. I have refactored PCRE in four places to do this. The result is
63        dramatic:
64    
65          Originally:                          290
66          After changing UCP table:            187
67          After changing error message table:   43
68          After changing table of "verbs"       36
69          After changing table of Posix names   22
70    
71        Thanks to the folks working on Gregex for glib for this insight.
72    
73    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
74        unicode-properties was also set.
75    
76    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
77    
78    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
79        checked only for CRLF.
80    
81    14. Added casts to pcretest.c to avoid compiler warnings.
82    
83    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
84    
85    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
86        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
87        entirely. This removes changes made in 7 above.
88    
89    17. The CMake files have been updated, and there is now more information about
90        building with CMake in the NON-UNIX-USE document.
91    
92    
93    Version 7.3 28-Aug-07
94  ---------------------  ---------------------
95    
96   1. In the rejigging of the build system that eventually resulted in 7.1, the   1. In the rejigging of the build system that eventually resulted in 7.1, the
# Line 98  Version 7.3 09-Aug-07 Line 187  Version 7.3 09-Aug-07
187      the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the      the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
188      full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still      full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
189      does: it's just the validity check that is more restrictive.      does: it's just the validity check that is more restrictive.
190    
191  16. Inserted checks for integer overflows during escape sequence (backslash)  16. Inserted checks for integer overflows during escape sequence (backslash)
192      processing, and also fixed erroneous offset values for syntax errors during      processing, and also fixed erroneous offset values for syntax errors during
193      backslash processing.      backslash processing.
194    
195    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
196        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
197    
198    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
199        caused an overrun.
200    
201    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
202        something other than just ASCII characters) inside a group that had an
203        unlimited repeat caused a loop at compile time (while checking to see
204        whether the group could match an empty string).
205    
206    20. Debugging a pattern containing \p or \P could cause a crash. For example,
207        [\P{Any}] did so. (Error in the code for printing property names.)
208    
209    21. An orphan \E inside a character class could cause a crash.
210    
211    22. A repeated capturing bracket such as (A)? could cause a wild memory
212        reference during compilation.
213    
214    23. There are several functions in pcre_compile() that scan along a compiled
215        expression for various reasons (e.g. to see if it's fixed length for look
216        behind). There were bugs in these functions when a repeated \p or \P was
217        present in the pattern. These operators have additional parameters compared
218        with \d, etc, and these were not being taken into account when moving along
219        the compiled data. Specifically:
220    
221        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
222            length.
223    
224        (b) An item such as \pL+ within a repeated group could cause crashes or
225            loops.
226    
227        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
228            "reference to non-existent subpattern" error.
229    
230        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
231    
232    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
233        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
234    
235    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
236    
237    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
238        character were causing crashes (broken optimization).
239    
240    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
241        \p or \P) caused a compile-time loop.
242    
243    28. More problems have arisen in unanchored patterns when CRLF is a valid line
244        break. For example, the unstudied pattern [\r\n]A does not match the string
245        "\r\nA" because change 7.0/46 below moves the current point on by two
246        characters after failing to match at the start. However, the pattern \nA
247        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
248        the same is true. There doesn't seem any very clean way out of this, but
249        what I have chosen to do makes the common cases work: PCRE now takes note
250        of whether there can be an explicit match for \r or \n anywhere in the
251        pattern, and if so, 7.0/46 no longer applies. As part of this change,
252        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
253        pattern has explicit CR or LF references.
254    
255    29. Added (*CR) etc for changing newline setting at start of pattern.
256    
257    
258  Version 7.2 19-Jun-07  Version 7.2 19-Jun-07

Legend:
Removed from v.213  
changed lines
  Added in v.265

  ViewVC Help
Powered by ViewVC 1.1.5