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

Diff of /code/trunk/ChangeLog

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

revision 234 by ph10, Tue Sep 11 11:36:27 2007 UTC revision 298 by ph10, Thu Jan 10 17:09:12 2008 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 7.4 10-Sep-07  Version 7.5 10-Jan-08
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. Added --file-offsets and --line-offsets to pcregrep.
80    
81    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
82        infinitely looping recursion. The bug was that positive lookaheads were not
83        being skipped when checking for a possible empty match (negative lookaheads
84        and both kinds of lookbehind were skipped).
85    
86    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
87        inclusion of <windows.h> to before rather than after the definition of
88        INVALID_FILE_ATTRIBUTES (patch from David Byron).
89    
90    17. Specifying a possessive quantifier with a specific limit for a Unicode
91        character property caused pcre_compile() to compile bad code, which led at
92        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
93        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
94        caused the error; without that there was no problem.
95    
96    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
97    
98    19. Added --enable-pcretest-libreadline.
99    
100    20. In pcrecpp.cc, the variable 'count' was incremented twice in
101        RE::GlobalReplace(). As a result, the number of replacements returned was
102        double what it should be. I removed one of the increments, but Craig sent a
103        later patch that removed the other one (the right fix) and added unit tests
104        that check the return values (which was not done before).
105    
106    21. Several CMake things:
107    
108        (1) Arranged that, when cmake is used on Unix, the libraries end up with
109            the names libpcre and libpcreposix, not just pcre and pcreposix.
110    
111        (2) The above change means that pcretest and pcregrep are now correctly
112            linked with the newly-built libraries, not previously installed ones.
113    
114        (3) Added PCRE_SUPPORT_LIBREADLINE, PCRE_SUPPORT_LIBZ, PCRE_SUPPORT_LIBBZ2.
115    
116    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
117        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
118        UTF-8 newline character). The key issue is that the pattern starts .*;
119        this means that the match must be either at the beginning, or after a
120        newline. The bug was in the code for advancing after a failed match and
121        checking that the new position followed a newline. It was not taking
122        account of UTF-8 characters correctly.
123    
124    23. PCRE was behaving differently from Perl in the way it recognized POSIX
125        character classes. PCRE was not treating the sequence [:...:] as a
126        character class unless the ... were all letters. Perl, however, seems to
127        allow any characters between [: and :], though of course it rejects as
128        unknown any "names" that contain non-letters, because all the known class
129        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
130        for example, whereas PCRE did not - it did not recognize a POSIX character
131        class. This seemed a bit dangerous, so the code has been changed to be
132        closer to Perl. The behaviour is not identical to Perl, because PCRE will
133        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
134        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
135        Perl does, and where it didn't before.
136    
137    24. Rewrite so as to remove the single use of %n from pcregrep because in some
138        Windows environments %n is disabled by default.
139    
140    
141    Version 7.4 21-Sep-07
142  ---------------------  ---------------------
143    
144  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
# Line 25  Version 7.4 10-Sep-07 Line 162  Version 7.4 10-Sep-07
162    
163  4.  Added options (at build time, compile time, exec time) to change \R from  4.  Added options (at build time, compile time, exec time) to change \R from
164      matching any Unicode line ending sequence to just matching CR, LF, or CRLF.      matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
   
 5.  doc/pcresyntax.html was missing from the distribution.  
165    
166  6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward  5.  doc/pcresyntax.html was missing from the distribution.
167    
168    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
169      compatibility, even though it is no longer used.      compatibility, even though it is no longer used.
170    
171  7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and  7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
172      strtoull to pcrecpp.cc to select the available functions in WIN32 (where      strtoull to pcrecpp.cc to select the available functions in WIN32 when the
173      different names are used).      windows.h file is present (where different names are used). [This was
174        reversed later after testing - see 16 below.]
175    
176    8.  Changed all #include <config.h> to #include "config.h". There were also
177        some further <pcre.h> cases that I changed to "pcre.h".
178    
179    9.  When pcregrep was used with the --colour option, it missed the line ending
180        sequence off the lines that it output.
181    
182    10. It was pointed out to me that arrays of string pointers cause lots of
183        relocations when a shared library is dynamically loaded. A technique of
184        using a single long string with a table of offsets can drastically reduce
185        these. I have refactored PCRE in four places to do this. The result is
186        dramatic:
187    
188          Originally:                          290
189          After changing UCP table:            187
190          After changing error message table:   43
191          After changing table of "verbs"       36
192          After changing table of Posix names   22
193    
194        Thanks to the folks working on Gregex for glib for this insight.
195    
196    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
197        unicode-properties was also set.
198    
199    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
200    
201    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
202        checked only for CRLF.
203    
204    14. Added casts to pcretest.c to avoid compiler warnings.
205    
206    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
207    
208    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
209        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
210        entirely. This removes changes made in 7 above.
211    
212    17. The CMake files have been updated, and there is now more information about
213        building with CMake in the NON-UNIX-USE document.
214    
215    
216  Version 7.3 28-Aug-07  Version 7.3 28-Aug-07

Legend:
Removed from v.234  
changed lines
  Added in v.298

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12