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

Diff of /code/trunk/ChangeLog

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

revision 230 by ph10, Mon Sep 10 13:23:56 2007 UTC revision 279 by ph10, Tue Dec 4 20:01:43 2007 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 7.4 10-Sep-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    11. The program that makes PCRE's Unicode character property table had a bug
49        which caused it to generate incorrect table entries for sequences of
50        characters that have the same character type, but are in different scripts.
51        It amalgamated them into a single range, with the script of the first of
52        them. In other words, some characters were in the wrong script. There were
53        thirteen such cases, affecting characters in the following ranges:
54    
55          U+002b0 - U+002c1
56          U+0060c - U+0060d
57          U+0061e - U+00612
58          U+0064b - U+0065e
59          U+0074d - U+0076d
60          U+01800 - U+01805
61          U+01d00 - U+01d77
62          U+01d9b - U+01dbf
63          U+0200b - U+0200f
64          U+030fc - U+030fe
65          U+03260 - U+0327f
66          U+0fb46 - U+0fbb1
67          U+10450 - U+1049d
68    
69    12. The -o option (show only the matching part of a line) for pcregrep was not
70        compatible with GNU grep in that, if there was more than one match in a
71        line, it showed only the first of them. It now behaves in the same way as
72        GNU grep.
73    
74    13. If the -o and -v options were combined for pcregrep, it printed a blank
75        line for every non-matching line. GNU grep prints nothing, and pcregrep now
76        does the same. The return code can be used to tell if there were any
77        non-matching lines.
78    
79    
80    Version 7.4 21-Sep-07
81  ---------------------  ---------------------
82    
83  1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This  1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
84      means that a class such as [\s] counted as "explicit reference to CR or      means that a class such as [\s] counted as "explicit reference to CR or
85      LF". That isn't really right - the whole point of the change was to try to      LF". That isn't really right - the whole point of the change was to try to
86      help when there was an actual mention of one of the two characters. So now      help when there was an actual mention of one of the two characters. So now
87      the change happens only if \r or \n (or a literal CR or LF) character is      the change happens only if \r or \n (or a literal CR or LF) character is
88      encountered.      encountered.
89    
90  2.  The 32-bit options word was also used for 6 internal flags, but the numbers  2.  The 32-bit options word was also used for 6 internal flags, but the numbers
91      of both had grown to the point where there were only 3 bits left.      of both had grown to the point where there were only 3 bits left.
92      Fortunately, there was spare space in the data structure, and so I have      Fortunately, there was spare space in the data structure, and so I have
93      moved the internal flags into a new 16-bit field to free up more option      moved the internal flags into a new 16-bit field to free up more option
94      bits.      bits.
95    
96  3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,  3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
97      but did not set the internal JCHANGED flag - either of these is enough to      but did not set the internal JCHANGED flag - either of these is enough to
98      control the way the "get" function works - but the PCRE_INFO_JCHANGED      control the way the "get" function works - but the PCRE_INFO_JCHANGED
99      facility is supposed to tell if (?J) was ever used, so now (?J) at the      facility is supposed to tell if (?J) was ever used, so now (?J) at the
100      start sets both bits.      start sets both bits.
101    
102    4.  Added options (at build time, compile time, exec time) to change \R from
103        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
104    
105    5.  doc/pcresyntax.html was missing from the distribution.
106    
107    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
108        compatibility, even though it is no longer used.
109    
110    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
111        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
112        windows.h file is present (where different names are used). [This was
113        reversed later after testing - see 16 below.]
114    
115    8.  Changed all #include <config.h> to #include "config.h". There were also
116        some further <pcre.h> cases that I changed to "pcre.h".
117    
118    9.  When pcregrep was used with the --colour option, it missed the line ending
119        sequence off the lines that it output.
120    
121    10. It was pointed out to me that arrays of string pointers cause lots of
122        relocations when a shared library is dynamically loaded. A technique of
123        using a single long string with a table of offsets can drastically reduce
124        these. I have refactored PCRE in four places to do this. The result is
125        dramatic:
126    
127          Originally:                          290
128          After changing UCP table:            187
129          After changing error message table:   43
130          After changing table of "verbs"       36
131          After changing table of Posix names   22
132    
133        Thanks to the folks working on Gregex for glib for this insight.
134    
135    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
136        unicode-properties was also set.
137    
138    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
139    
140    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
141        checked only for CRLF.
142    
143    14. Added casts to pcretest.c to avoid compiler warnings.
144    
145    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
146    
147    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
148        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
149        entirely. This removes changes made in 7 above.
150    
151    17. The CMake files have been updated, and there is now more information about
152        building with CMake in the NON-UNIX-USE document.
153    
154    
155  Version 7.3 28-Aug-07  Version 7.3 28-Aug-07
156  ---------------------  ---------------------
Legend:
Removed from v.230  
changed lines
  Added in v.279
webmaster@exim.org
 ViewVC Help
Powered by ViewVC 1.1.12