/[pcre]/code/trunk/ChangeLog
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 329 by ph10, Fri Mar 28 12:06:36 2008 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 7.3 17-Aug-07  Version 7.7 05-Mar-08
5    ---------------------
6    
7    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
8        a string to a long long, pretend we don't even have a long long." This is
9        done by checking for the strtoq, strtoll, and _strtoi64 functions.
10    
11    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
12        pre-7.6 versions, which defined a global no_arg variable instead of putting
13        it in the RE class.
14    
15    3.  Remove a line of dead code, identified by coverity and reported by Nuno
16        Lopes.
17    
18    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
19    
20        (1) The include/exclude patterns were being applied to the whole pathnames
21            of files, instead of just to the final components.
22    
23        (2) If there was more than one level of directory, the subdirectories were
24            skipped unless they satisfied the include/exclude conditions. This is
25            inconsistent with GNU grep (and could even be seen as contrary to the
26            pcregrep specification - which I improved to make it absolutely clear).
27            The action now is always to scan all levels of directory, and just
28            apply the include/exclude patterns to regular files.
29    
30    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
31        --exclude_dir in the tests to avoid scanning .svn directories.
32    
33    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
34        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
35        doesn't support NULs in patterns.
36    
37    7.  Added some missing "const"s to declarations of static tables in
38        pcre_compile.c and pcre_dfa_exec.c.
39    
40    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
41        caused by fix #2  above. (Subsequently also a second patch to fix the
42        first patch.)
43    
44    
45    Version 7.6 28-Jan-08
46    ---------------------
47    
48    1.  A character class containing a very large number of characters with
49        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
50        overflow.
51    
52    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
53        HAVE_LONG_LONG is not defined.
54    
55    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
56        bring them up to date and include new features. This patch includes:
57    
58        - Fixed PH's badly added libz and libbz2 support.
59        - Fixed a problem with static linking.
60        - Added pcredemo. [But later removed - see 7 below.]
61        - Fixed dftables problem and added an option.
62        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
63            HAVE_LONG_LONG.
64        - Added readline support for pcretest.
65        - Added an listing of the option settings after cmake has run.
66    
67    4.  A user submitted a patch to Makefile that makes it easy to create
68        "pcre.dll" under mingw when using Configure/Make. I added stuff to
69        Makefile.am that cause it to include this special target, without
70        affecting anything else. Note that the same mingw target plus all
71        the other distribution libraries and programs are now supported
72        when configuring with CMake (see 6 below) instead of with
73        Configure/Make.
74    
75    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
76        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
77        exported in the Windows port". It has not yet been confirmed that the patch
78        solves the problem, but it does no harm.
79    
80    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
81        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
82        with CMake, and also correct the comment about stack recursion.
83    
84    7.  Remove the automatic building of pcredemo from the ./configure system and
85        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
86        of a program that users should build themselves after PCRE is installed, so
87        building it automatically is not really right. What is more, it gave
88        trouble in some build environments.
89    
90    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
91    
92    
93    Version 7.5 10-Jan-08
94    ---------------------
95    
96    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
97        values in parens when parsing an RE using the C++ wrapper."
98    
99    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
100        Characters greater than 255 were excluded from the class instead of being
101        included.
102    
103    3.  The same bug as (2) above applied to negated POSIX classes such as
104        [:^space:].
105    
106    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
107        defined or documented. It seems to have been a typo for PCRE_STATIC, so
108        I have changed it.
109    
110    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
111        first named subpattern) and a construct such as (?&a) would reference the
112        first named subpattern whose name started with "a" (in other words, the
113        length check was missing). Both these problems are fixed. "Subpattern name
114        expected" is now given for (?&) (a zero-length name), and this patch also
115        makes it give the same error for \k'' (previously it complained that that
116        was a reference to a non-existent subpattern).
117    
118    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
119        this is right because (?- can be followed by option settings as well as by
120        digits. I have, however, made the messages clearer.
121    
122    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
123        than the number used in the conditional) now cause a compile-time error.
124        This is actually not compatible with Perl, which accepts such patterns, but
125        treats the conditional as always being FALSE (as PCRE used to), but it
126        seems to me that giving a diagnostic is better.
127    
128    8.  Change "alphameric" to the more common word "alphanumeric" in comments
129        and messages.
130    
131    9.  Fix two occurrences of "backslash" in comments that should have been
132        "backspace".
133    
134    10. Remove two redundant lines of code that can never be obeyed (their function
135        was moved elsewhere).
136    
137    11. The program that makes PCRE's Unicode character property table had a bug
138        which caused it to generate incorrect table entries for sequences of
139        characters that have the same character type, but are in different scripts.
140        It amalgamated them into a single range, with the script of the first of
141        them. In other words, some characters were in the wrong script. There were
142        thirteen such cases, affecting characters in the following ranges:
143    
144          U+002b0 - U+002c1
145          U+0060c - U+0060d
146          U+0061e - U+00612
147          U+0064b - U+0065e
148          U+0074d - U+0076d
149          U+01800 - U+01805
150          U+01d00 - U+01d77
151          U+01d9b - U+01dbf
152          U+0200b - U+0200f
153          U+030fc - U+030fe
154          U+03260 - U+0327f
155          U+0fb46 - U+0fbb1
156          U+10450 - U+1049d
157    
158    12. The -o option (show only the matching part of a line) for pcregrep was not
159        compatible with GNU grep in that, if there was more than one match in a
160        line, it showed only the first of them. It now behaves in the same way as
161        GNU grep.
162    
163    13. If the -o and -v options were combined for pcregrep, it printed a blank
164        line for every non-matching line. GNU grep prints nothing, and pcregrep now
165        does the same. The return code can be used to tell if there were any
166        non-matching lines.
167    
168    14. Added --file-offsets and --line-offsets to pcregrep.
169    
170    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
171        infinitely looping recursion. The bug was that positive lookaheads were not
172        being skipped when checking for a possible empty match (negative lookaheads
173        and both kinds of lookbehind were skipped).
174    
175    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
176        inclusion of <windows.h> to before rather than after the definition of
177        INVALID_FILE_ATTRIBUTES (patch from David Byron).
178    
179    17. Specifying a possessive quantifier with a specific limit for a Unicode
180        character property caused pcre_compile() to compile bad code, which led at
181        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
182        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
183        caused the error; without that there was no problem.
184    
185    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
186    
187    19. Added --enable-pcretest-libreadline.
188    
189    20. In pcrecpp.cc, the variable 'count' was incremented twice in
190        RE::GlobalReplace(). As a result, the number of replacements returned was
191        double what it should be. I removed one of the increments, but Craig sent a
192        later patch that removed the other one (the right fix) and added unit tests
193        that check the return values (which was not done before).
194    
195    21. Several CMake things:
196    
197        (1) Arranged that, when cmake is used on Unix, the libraries end up with
198            the names libpcre and libpcreposix, not just pcre and pcreposix.
199    
200        (2) The above change means that pcretest and pcregrep are now correctly
201            linked with the newly-built libraries, not previously installed ones.
202    
203        (3) Added PCRE_SUPPORT_LIBREADLINE, PCRE_SUPPORT_LIBZ, PCRE_SUPPORT_LIBBZ2.
204    
205    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
206        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
207        UTF-8 newline character). The key issue is that the pattern starts .*;
208        this means that the match must be either at the beginning, or after a
209        newline. The bug was in the code for advancing after a failed match and
210        checking that the new position followed a newline. It was not taking
211        account of UTF-8 characters correctly.
212    
213    23. PCRE was behaving differently from Perl in the way it recognized POSIX
214        character classes. PCRE was not treating the sequence [:...:] as a
215        character class unless the ... were all letters. Perl, however, seems to
216        allow any characters between [: and :], though of course it rejects as
217        unknown any "names" that contain non-letters, because all the known class
218        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
219        for example, whereas PCRE did not - it did not recognize a POSIX character
220        class. This seemed a bit dangerous, so the code has been changed to be
221        closer to Perl. The behaviour is not identical to Perl, because PCRE will
222        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
223        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
224        Perl does, and where it didn't before.
225    
226    24. Rewrite so as to remove the single use of %n from pcregrep because in some
227        Windows environments %n is disabled by default.
228    
229    
230    Version 7.4 21-Sep-07
231    ---------------------
232    
233    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
234        means that a class such as [\s] counted as "explicit reference to CR or
235        LF". That isn't really right - the whole point of the change was to try to
236        help when there was an actual mention of one of the two characters. So now
237        the change happens only if \r or \n (or a literal CR or LF) character is
238        encountered.
239    
240    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
241        of both had grown to the point where there were only 3 bits left.
242        Fortunately, there was spare space in the data structure, and so I have
243        moved the internal flags into a new 16-bit field to free up more option
244        bits.
245    
246    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
247        but did not set the internal JCHANGED flag - either of these is enough to
248        control the way the "get" function works - but the PCRE_INFO_JCHANGED
249        facility is supposed to tell if (?J) was ever used, so now (?J) at the
250        start sets both bits.
251    
252    4.  Added options (at build time, compile time, exec time) to change \R from
253        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
254    
255    5.  doc/pcresyntax.html was missing from the distribution.
256    
257    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
258        compatibility, even though it is no longer used.
259    
260    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
261        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
262        windows.h file is present (where different names are used). [This was
263        reversed later after testing - see 16 below.]
264    
265    8.  Changed all #include <config.h> to #include "config.h". There were also
266        some further <pcre.h> cases that I changed to "pcre.h".
267    
268    9.  When pcregrep was used with the --colour option, it missed the line ending
269        sequence off the lines that it output.
270    
271    10. It was pointed out to me that arrays of string pointers cause lots of
272        relocations when a shared library is dynamically loaded. A technique of
273        using a single long string with a table of offsets can drastically reduce
274        these. I have refactored PCRE in four places to do this. The result is
275        dramatic:
276    
277          Originally:                          290
278          After changing UCP table:            187
279          After changing error message table:   43
280          After changing table of "verbs"       36
281          After changing table of Posix names   22
282    
283        Thanks to the folks working on Gregex for glib for this insight.
284    
285    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
286        unicode-properties was also set.
287    
288    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
289    
290    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
291        checked only for CRLF.
292    
293    14. Added casts to pcretest.c to avoid compiler warnings.
294    
295    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
296    
297    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
298        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
299        entirely. This removes changes made in 7 above.
300    
301    17. The CMake files have been updated, and there is now more information about
302        building with CMake in the NON-UNIX-USE document.
303    
304    
305    Version 7.3 28-Aug-07
306  ---------------------  ---------------------
307    
308   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 444  Version 7.3 17-Aug-07
444  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
445      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").
446    
447    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
448    
449    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
450        character were causing crashes (broken optimization).
451    
452    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
453        \p or \P) caused a compile-time loop.
454    
455    28. More problems have arisen in unanchored patterns when CRLF is a valid line
456        break. For example, the unstudied pattern [\r\n]A does not match the string
457        "\r\nA" because change 7.0/46 below moves the current point on by two
458        characters after failing to match at the start. However, the pattern \nA
459        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
460        the same is true. There doesn't seem any very clean way out of this, but
461        what I have chosen to do makes the common cases work: PCRE now takes note
462        of whether there can be an explicit match for \r or \n anywhere in the
463        pattern, and if so, 7.0/46 no longer applies. As part of this change,
464        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
465        pattern has explicit CR or LF references.
466    
467    29. Added (*CR) etc for changing newline setting at start of pattern.
468    
469    
470  Version 7.2 19-Jun-07  Version 7.2 19-Jun-07
471  ---------------------  ---------------------

Legend:
Removed from v.221  
changed lines
  Added in v.329

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12