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

Diff of /code/trunk/ChangeLog

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

revision 223 by ph10, Mon Aug 20 11:07:53 2007 UTC revision 244 by ph10, Fri Sep 14 09:14:24 2007 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 7.3 20-Aug-07  Version 7.4 10-Sep-07
5    ---------------------
6    
7    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
8        means that a class such as [\s] counted as "explicit reference to CR or
9        LF". That isn't really right - the whole point of the change was to try to
10        help when there was an actual mention of one of the two characters. So now
11        the change happens only if \r or \n (or a literal CR or LF) character is
12        encountered.
13    
14    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
15        of both had grown to the point where there were only 3 bits left.
16        Fortunately, there was spare space in the data structure, and so I have
17        moved the internal flags into a new 16-bit field to free up more option
18        bits.
19    
20    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
21        but did not set the internal JCHANGED flag - either of these is enough to
22        control the way the "get" function works - but the PCRE_INFO_JCHANGED
23        facility is supposed to tell if (?J) was ever used, so now (?J) at the
24        start sets both bits.
25    
26    4.  Added options (at build time, compile time, exec time) to change \R from
27        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
28    
29    5.  doc/pcresyntax.html was missing from the distribution.
30    
31    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
32        compatibility, even though it is no longer used.
33    
34    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
35        strtoull to pcrecpp.cc to select the available functions in WIN32 (where
36        different names are used).
37    
38    8.  Changed all #include <config.h> to #include "config.h". There were also
39        some further <pcre.h> cases that I changed to "pcre.h".
40    
41    9.  When pcregrep was used with the --colour option, it missed the line ending
42        sequence off the lines that it output.
43    
44    10. It was pointed out to me that arrays of string pointers cause lots of
45        relocations when a shared library is dynamically loaded. A technique of
46        using a single long string with a table of offsets can drastically reduce
47        these. I have refactored PCRE in four places to do this. The result is
48        dramatic:
49    
50          Originally:                          290
51          After changing UCP table:            187
52          After changing error message table:   43
53          After changing table of "verbs"       36
54          After changing table of Posix names   22
55    
56        Thanks to the folks working on Gregex for glib for this insight.
57    
58    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
59        unicode-properties was also set.
60    
61    
62    Version 7.3 28-Aug-07
63  ---------------------  ---------------------
64    
65   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 145  Version 7.3 20-Aug-07 Line 203  Version 7.3 20-Aug-07
203    
204  25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.  25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
205    
206  26. Patterns such as [\P{Yi}A] which include \p or \P and just one other  26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
207      character were causing crashes (broken optimization).      character were causing crashes (broken optimization).
208    
209    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
210        \p or \P) caused a compile-time loop.
211    
212    28. More problems have arisen in unanchored patterns when CRLF is a valid line
213        break. For example, the unstudied pattern [\r\n]A does not match the string
214        "\r\nA" because change 7.0/46 below moves the current point on by two
215        characters after failing to match at the start. However, the pattern \nA
216        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
217        the same is true. There doesn't seem any very clean way out of this, but
218        what I have chosen to do makes the common cases work: PCRE now takes note
219        of whether there can be an explicit match for \r or \n anywhere in the
220        pattern, and if so, 7.0/46 no longer applies. As part of this change,
221        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
222        pattern has explicit CR or LF references.
223    
224    29. Added (*CR) etc for changing newline setting at start of pattern.
225    
226    
227  Version 7.2 19-Jun-07  Version 7.2 19-Jun-07
228  ---------------------  ---------------------
Legend:
Removed from v.223  
changed lines
  Added in v.244
webmaster@exim.org
 ViewVC Help
Powered by ViewVC 1.1.12