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

Diff of /code/trunk/ChangeLog

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

revision 220 by ph10, Thu Aug 16 13:29:39 2007 UTC revision 276 by ph10, Wed Nov 21 15:39:20 2007 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 7.3 16-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    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.
20    
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).
28    
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.
32    
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.
38    
39    8.  Change "alphameric" to the more common word "alphanumeric" in comments
40        and messages.
41    
42    9.  Fix two occurrences of "backslash" in comments that should have been
43        "backspace".
44    
45    10. Remove two redundant lines of code that can never be obeyed (their function
46        was moved elsewhere).
47    
48    
49    Version 7.4 21-Sep-07
50    ---------------------
51    
52    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
53        means that a class such as [\s] counted as "explicit reference to CR or
54        LF". That isn't really right - the whole point of the change was to try to
55        help when there was an actual mention of one of the two characters. So now
56        the change happens only if \r or \n (or a literal CR or LF) character is
57        encountered.
58    
59    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
60        of both had grown to the point where there were only 3 bits left.
61        Fortunately, there was spare space in the data structure, and so I have
62        moved the internal flags into a new 16-bit field to free up more option
63        bits.
64    
65    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
66        but did not set the internal JCHANGED flag - either of these is enough to
67        control the way the "get" function works - but the PCRE_INFO_JCHANGED
68        facility is supposed to tell if (?J) was ever used, so now (?J) at the
69        start sets both bits.
70    
71    4.  Added options (at build time, compile time, exec time) to change \R from
72        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
73    
74    5.  doc/pcresyntax.html was missing from the distribution.
75    
76    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
77        compatibility, even though it is no longer used.
78    
79    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
80        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
81        windows.h file is present (where different names are used). [This was
82        reversed later after testing - see 16 below.]
83    
84    8.  Changed all #include <config.h> to #include "config.h". There were also
85        some further <pcre.h> cases that I changed to "pcre.h".
86    
87    9.  When pcregrep was used with the --colour option, it missed the line ending
88        sequence off the lines that it output.
89    
90    10. It was pointed out to me that arrays of string pointers cause lots of
91        relocations when a shared library is dynamically loaded. A technique of
92        using a single long string with a table of offsets can drastically reduce
93        these. I have refactored PCRE in four places to do this. The result is
94        dramatic:
95    
96          Originally:                          290
97          After changing UCP table:            187
98          After changing error message table:   43
99          After changing table of "verbs"       36
100          After changing table of Posix names   22
101    
102        Thanks to the folks working on Gregex for glib for this insight.
103    
104    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
105        unicode-properties was also set.
106    
107    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
108    
109    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
110        checked only for CRLF.
111    
112    14. Added casts to pcretest.c to avoid compiler warnings.
113    
114    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
115    
116    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
117        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
118        entirely. This removes changes made in 7 above.
119    
120    17. The CMake files have been updated, and there is now more information about
121        building with CMake in the NON-UNIX-USE document.
122    
123    
124    Version 7.3 28-Aug-07
125  ---------------------  ---------------------
126    
127   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 138  Version 7.3 16-Aug-07 Line 258  Version 7.3 16-Aug-07
258      (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect      (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
259          "reference to non-existent subpattern" error.          "reference to non-existent subpattern" error.
260    
261        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
262    
263  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
264      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").
265    
266    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
267    
268    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
269        character were causing crashes (broken optimization).
270    
271    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
272        \p or \P) caused a compile-time loop.
273    
274    28. More problems have arisen in unanchored patterns when CRLF is a valid line
275        break. For example, the unstudied pattern [\r\n]A does not match the string
276        "\r\nA" because change 7.0/46 below moves the current point on by two
277        characters after failing to match at the start. However, the pattern \nA
278        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
279        the same is true. There doesn't seem any very clean way out of this, but
280        what I have chosen to do makes the common cases work: PCRE now takes note
281        of whether there can be an explicit match for \r or \n anywhere in the
282        pattern, and if so, 7.0/46 no longer applies. As part of this change,
283        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
284        pattern has explicit CR or LF references.
285    
286    29. Added (*CR) etc for changing newline setting at start of pattern.
287    
288    
289  Version 7.2 19-Jun-07  Version 7.2 19-Jun-07
290  ---------------------  ---------------------

Legend:
Removed from v.220  
changed lines
  Added in v.276

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12