ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 221 by ph10, Fri Aug 17 09:25:08 2007 UTC revision 274 by ph10, Tue Nov 20 10:05:23 2007 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 7.3 17-Aug-07  Version 7.5 12-Nov-07
5    ---------------------
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."
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.
14    3.  The same bug as (2) above applied to negated POSIX classes such as
15        [:^space:].
17    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
18        defined or documented. It seems to have been a typo for PCRE_STATIC, so
19        I have changed it.
21    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
22        first named subpattern) and a construct such as (?&a) would reference the
23        first named subpattern whose name started with "a" (in other words, the
24        length check was missing). Both these problems are fixed. "Subpattern name
25        expected" is now given for (?&) (a zero-length name), and this patch also
26        makes it give the same error for \k'' (previously it complained that that
27        was a reference to a non-existent subpattern).
29    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
30        this is right because (?- can be followed by option settings as well as by
31        digits. I have, however, made the messages clearer.
33    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
34        than the number used in the conditional) now cause a compile-time error.
35        This is actually not compatible with Perl, which accepts such patterns, but
36        treats the conditional as always being FALSE (as PCRE used to), but it
37        seems to me that giving a diagnostic is better.
39    8.  Change "alphameric" to the more common word "alphanumeric" in comments
40        and messages.
43    Version 7.4 21-Sep-07
44    ---------------------
46    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
47        means that a class such as [\s] counted as "explicit reference to CR or
48        LF". That isn't really right - the whole point of the change was to try to
49        help when there was an actual mention of one of the two characters. So now
50        the change happens only if \r or \n (or a literal CR or LF) character is
51        encountered.
53    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
54        of both had grown to the point where there were only 3 bits left.
55        Fortunately, there was spare space in the data structure, and so I have
56        moved the internal flags into a new 16-bit field to free up more option
57        bits.
59    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
60        but did not set the internal JCHANGED flag - either of these is enough to
61        control the way the "get" function works - but the PCRE_INFO_JCHANGED
62        facility is supposed to tell if (?J) was ever used, so now (?J) at the
63        start sets both bits.
65    4.  Added options (at build time, compile time, exec time) to change \R from
66        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
68    5.  doc/pcresyntax.html was missing from the distribution.
70    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
71        compatibility, even though it is no longer used.
73    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
74        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
75        windows.h file is present (where different names are used). [This was
76        reversed later after testing - see 16 below.]
78    8.  Changed all #include <config.h> to #include "config.h". There were also
79        some further <pcre.h> cases that I changed to "pcre.h".
81    9.  When pcregrep was used with the --colour option, it missed the line ending
82        sequence off the lines that it output.
84    10. It was pointed out to me that arrays of string pointers cause lots of
85        relocations when a shared library is dynamically loaded. A technique of
86        using a single long string with a table of offsets can drastically reduce
87        these. I have refactored PCRE in four places to do this. The result is
88        dramatic:
90          Originally:                          290
91          After changing UCP table:            187
92          After changing error message table:   43
93          After changing table of "verbs"       36
94          After changing table of Posix names   22
96        Thanks to the folks working on Gregex for glib for this insight.
98    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
99        unicode-properties was also set.
101    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
103    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
104        checked only for CRLF.
106    14. Added casts to pcretest.c to avoid compiler warnings.
108    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
110    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
111        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
112        entirely. This removes changes made in 7 above.
114    17. The CMake files have been updated, and there is now more information about
115        building with CMake in the NON-UNIX-USE document.
118    Version 7.3 28-Aug-07
119  ---------------------  ---------------------
121   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 143  Version 7.3 17-Aug-07 Line 257  Version 7.3 17-Aug-07
257  24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte  24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
258      characters were involved (for example /\S{2}/8g with "A\x{a3}BC").      characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
260    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
262    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
263        character were causing crashes (broken optimization).
265    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
266        \p or \P) caused a compile-time loop.
268    28. More problems have arisen in unanchored patterns when CRLF is a valid line
269        break. For example, the unstudied pattern [\r\n]A does not match the string
270        "\r\nA" because change 7.0/46 below moves the current point on by two
271        characters after failing to match at the start. However, the pattern \nA
272        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
273        the same is true. There doesn't seem any very clean way out of this, but
274        what I have chosen to do makes the common cases work: PCRE now takes note
275        of whether there can be an explicit match for \r or \n anywhere in the
276        pattern, and if so, 7.0/46 no longer applies. As part of this change,
277        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
278        pattern has explicit CR or LF references.
280    29. Added (*CR) etc for changing newline setting at start of pattern.
283  Version 7.2 19-Jun-07  Version 7.2 19-Jun-07
284  ---------------------  ---------------------

Removed from v.221  
changed lines
  Added in v.274

  ViewVC Help
Powered by ViewVC 1.1.5