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

Diff of /code/trunk/ChangeLog

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

revision 227 by ph10, Tue Aug 21 15:00:15 2007 UTC revision 285 by ph10, Wed Dec 12 17:03:50 2007 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 7.3 20-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    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    14. The pattern (?=something)(?R) was not being diagnosed as a potentially
80        infinitely looping recursion. The bug was that positive lookaheads were not
81        being skipped when checking for a possible empty match (negative lookaheads
82        and both kinds of lookbehind were skipped).
83    
84    15. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
85        inclusion of <windows.h> to before rather than after the definition of
86        INVALID_FILE_ATTRIBUTES (patch from David Byron).
87    
88    16. Specifying a possessive quantifier with a specific limit for a Unicode
89        character property caused pcre_compile() to compile bad code, which led at
90        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
91        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
92        caused the error; without that there was no problem.
93    
94    
95    Version 7.4 21-Sep-07
96    ---------------------
97    
98    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
99        means that a class such as [\s] counted as "explicit reference to CR or
100        LF". That isn't really right - the whole point of the change was to try to
101        help when there was an actual mention of one of the two characters. So now
102        the change happens only if \r or \n (or a literal CR or LF) character is
103        encountered.
104    
105    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
106        of both had grown to the point where there were only 3 bits left.
107        Fortunately, there was spare space in the data structure, and so I have
108        moved the internal flags into a new 16-bit field to free up more option
109        bits.
110    
111    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
112        but did not set the internal JCHANGED flag - either of these is enough to
113        control the way the "get" function works - but the PCRE_INFO_JCHANGED
114        facility is supposed to tell if (?J) was ever used, so now (?J) at the
115        start sets both bits.
116    
117    4.  Added options (at build time, compile time, exec time) to change \R from
118        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
119    
120    5.  doc/pcresyntax.html was missing from the distribution.
121    
122    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
123        compatibility, even though it is no longer used.
124    
125    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
126        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
127        windows.h file is present (where different names are used). [This was
128        reversed later after testing - see 16 below.]
129    
130    8.  Changed all #include <config.h> to #include "config.h". There were also
131        some further <pcre.h> cases that I changed to "pcre.h".
132    
133    9.  When pcregrep was used with the --colour option, it missed the line ending
134        sequence off the lines that it output.
135    
136    10. It was pointed out to me that arrays of string pointers cause lots of
137        relocations when a shared library is dynamically loaded. A technique of
138        using a single long string with a table of offsets can drastically reduce
139        these. I have refactored PCRE in four places to do this. The result is
140        dramatic:
141    
142          Originally:                          290
143          After changing UCP table:            187
144          After changing error message table:   43
145          After changing table of "verbs"       36
146          After changing table of Posix names   22
147    
148        Thanks to the folks working on Gregex for glib for this insight.
149    
150    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
151        unicode-properties was also set.
152    
153    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
154    
155    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
156        checked only for CRLF.
157    
158    14. Added casts to pcretest.c to avoid compiler warnings.
159    
160    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
161    
162    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
163        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
164        entirely. This removes changes made in 7 above.
165    
166    17. The CMake files have been updated, and there is now more information about
167        building with CMake in the NON-UNIX-USE document.
168    
169    
170    Version 7.3 28-Aug-07
171  ---------------------  ---------------------
172    
173   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

Legend:
Removed from v.227  
changed lines
  Added in v.285

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12