/[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 346 by ph10, Wed Apr 30 16:35:49 2008 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 7.3 20-Aug-07  Version 7.7 28-Apr-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. (See also #8 below.)
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. And a third patch - this was a messy problem.)
43    
44    9.  Applied Craig's patch to remove the use of push_back().
45    
46    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
47        matching function regexec().
48    
49    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
50        which, however, unlike Perl's \g{...}, are subroutine calls, not back
51        references. PCRE supports relative numbers with this syntax (I don't think
52        Oniguruma does).
53    
54    12. Previously, a group with a zero repeat such as (...){0} was completely
55        omitted from the compiled regex. However, this means that if the group
56        was called as a subroutine from elsewhere in the pattern, things went wrong
57        (an internal error was given). Such groups are now left in the compiled
58        pattern, with a new opcode that causes them to be skipped at execution
59        time.
60    
61    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
62        to the way PCRE behaves:
63    
64        (a) A lone ] character is dis-allowed (Perl treats it as data).
65    
66        (b) A back reference to an unmatched subpattern matches an empty string
67            (Perl fails the current match path).
68    
69        (c) A data ] in a character class must be notated as \] because if the
70            first data character in a class is ], it defines an empty class. (In
71            Perl it is not possible to have an empty class.) The empty class []
72            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
73            The negative empty class [^] matches any one character, independently
74            of the DOTALL setting.
75    
76    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
77        non-existent subpattern following a character class starting with ']' and
78        containing () gave an internal compiling error instead of "reference to
79        non-existent subpattern". Fortunately, when the pattern did exist, the
80        compiled code was correct. (When scanning forwards to check for the
81        existencd of the subpattern, it was treating the data ']' as terminating
82        the class, so got the count wrong. When actually compiling, the reference
83        was subsequently set up correctly.)
84    
85    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
86        it was being rejected as not supported by pcre_dfa_exec(), even though
87        other assertions are supported. I have made pcre_dfa_exec() support
88        (*FAIL).
89    
90    16. The implementation of 13c above involved the invention of a new opcode,
91        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
92        cannot be changed at match time, I realized I could make a small
93        improvement to matching performance by compiling OP_ALLANY instead of
94        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
95        on the OP_ANY path.
96    
97    17. Compiling pcretest on Windows with readline support failed without the
98        following two fixes: (1) Make the unistd.h include conditional on
99        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
100    
101    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
102        ncurses library to be included for pcretest when ReadLine support is
103        requested, but also to allow for it to be overridden. This patch came from
104        Daniel Bergström.
105    
106    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
107        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
108        any errors with the current Unicode tables. Thanks to Peter Kankowski for
109        spotting this.
110    
111    
112    Version 7.6 28-Jan-08
113    ---------------------
114    
115    1.  A character class containing a very large number of characters with
116        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
117        overflow.
118    
119    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
120        HAVE_LONG_LONG is not defined.
121    
122    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
123        bring them up to date and include new features. This patch includes:
124    
125        - Fixed PH's badly added libz and libbz2 support.
126        - Fixed a problem with static linking.
127        - Added pcredemo. [But later removed - see 7 below.]
128        - Fixed dftables problem and added an option.
129        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
130            HAVE_LONG_LONG.
131        - Added readline support for pcretest.
132        - Added an listing of the option settings after cmake has run.
133    
134    4.  A user submitted a patch to Makefile that makes it easy to create
135        "pcre.dll" under mingw when using Configure/Make. I added stuff to
136        Makefile.am that cause it to include this special target, without
137        affecting anything else. Note that the same mingw target plus all
138        the other distribution libraries and programs are now supported
139        when configuring with CMake (see 6 below) instead of with
140        Configure/Make.
141    
142    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
143        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
144        exported in the Windows port". It has not yet been confirmed that the patch
145        solves the problem, but it does no harm.
146    
147    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
148        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
149        with CMake, and also correct the comment about stack recursion.
150    
151    7.  Remove the automatic building of pcredemo from the ./configure system and
152        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
153        of a program that users should build themselves after PCRE is installed, so
154        building it automatically is not really right. What is more, it gave
155        trouble in some build environments.
156    
157    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
158    
159    
160    Version 7.5 10-Jan-08
161    ---------------------
162    
163    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
164        values in parens when parsing an RE using the C++ wrapper."
165    
166    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
167        Characters greater than 255 were excluded from the class instead of being
168        included.
169    
170    3.  The same bug as (2) above applied to negated POSIX classes such as
171        [:^space:].
172    
173    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
174        defined or documented. It seems to have been a typo for PCRE_STATIC, so
175        I have changed it.
176    
177    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
178        first named subpattern) and a construct such as (?&a) would reference the
179        first named subpattern whose name started with "a" (in other words, the
180        length check was missing). Both these problems are fixed. "Subpattern name
181        expected" is now given for (?&) (a zero-length name), and this patch also
182        makes it give the same error for \k'' (previously it complained that that
183        was a reference to a non-existent subpattern).
184    
185    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
186        this is right because (?- can be followed by option settings as well as by
187        digits. I have, however, made the messages clearer.
188    
189    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
190        than the number used in the conditional) now cause a compile-time error.
191        This is actually not compatible with Perl, which accepts such patterns, but
192        treats the conditional as always being FALSE (as PCRE used to), but it
193        seems to me that giving a diagnostic is better.
194    
195    8.  Change "alphameric" to the more common word "alphanumeric" in comments
196        and messages.
197    
198    9.  Fix two occurrences of "backslash" in comments that should have been
199        "backspace".
200    
201    10. Remove two redundant lines of code that can never be obeyed (their function
202        was moved elsewhere).
203    
204    11. The program that makes PCRE's Unicode character property table had a bug
205        which caused it to generate incorrect table entries for sequences of
206        characters that have the same character type, but are in different scripts.
207        It amalgamated them into a single range, with the script of the first of
208        them. In other words, some characters were in the wrong script. There were
209        thirteen such cases, affecting characters in the following ranges:
210    
211          U+002b0 - U+002c1
212          U+0060c - U+0060d
213          U+0061e - U+00612
214          U+0064b - U+0065e
215          U+0074d - U+0076d
216          U+01800 - U+01805
217          U+01d00 - U+01d77
218          U+01d9b - U+01dbf
219          U+0200b - U+0200f
220          U+030fc - U+030fe
221          U+03260 - U+0327f
222          U+0fb46 - U+0fbb1
223          U+10450 - U+1049d
224    
225    12. The -o option (show only the matching part of a line) for pcregrep was not
226        compatible with GNU grep in that, if there was more than one match in a
227        line, it showed only the first of them. It now behaves in the same way as
228        GNU grep.
229    
230    13. If the -o and -v options were combined for pcregrep, it printed a blank
231        line for every non-matching line. GNU grep prints nothing, and pcregrep now
232        does the same. The return code can be used to tell if there were any
233        non-matching lines.
234    
235    14. Added --file-offsets and --line-offsets to pcregrep.
236    
237    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
238        infinitely looping recursion. The bug was that positive lookaheads were not
239        being skipped when checking for a possible empty match (negative lookaheads
240        and both kinds of lookbehind were skipped).
241    
242    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
243        inclusion of <windows.h> to before rather than after the definition of
244        INVALID_FILE_ATTRIBUTES (patch from David Byron).
245    
246    17. Specifying a possessive quantifier with a specific limit for a Unicode
247        character property caused pcre_compile() to compile bad code, which led at
248        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
249        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
250        caused the error; without that there was no problem.
251    
252    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
253    
254    19. Added --enable-pcretest-libreadline.
255    
256    20. In pcrecpp.cc, the variable 'count' was incremented twice in
257        RE::GlobalReplace(). As a result, the number of replacements returned was
258        double what it should be. I removed one of the increments, but Craig sent a
259        later patch that removed the other one (the right fix) and added unit tests
260        that check the return values (which was not done before).
261    
262    21. Several CMake things:
263    
264        (1) Arranged that, when cmake is used on Unix, the libraries end up with
265            the names libpcre and libpcreposix, not just pcre and pcreposix.
266    
267        (2) The above change means that pcretest and pcregrep are now correctly
268            linked with the newly-built libraries, not previously installed ones.
269    
270        (3) Added PCRE_SUPPORT_LIBREADLINE, PCRE_SUPPORT_LIBZ, PCRE_SUPPORT_LIBBZ2.
271    
272    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
273        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
274        UTF-8 newline character). The key issue is that the pattern starts .*;
275        this means that the match must be either at the beginning, or after a
276        newline. The bug was in the code for advancing after a failed match and
277        checking that the new position followed a newline. It was not taking
278        account of UTF-8 characters correctly.
279    
280    23. PCRE was behaving differently from Perl in the way it recognized POSIX
281        character classes. PCRE was not treating the sequence [:...:] as a
282        character class unless the ... were all letters. Perl, however, seems to
283        allow any characters between [: and :], though of course it rejects as
284        unknown any "names" that contain non-letters, because all the known class
285        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
286        for example, whereas PCRE did not - it did not recognize a POSIX character
287        class. This seemed a bit dangerous, so the code has been changed to be
288        closer to Perl. The behaviour is not identical to Perl, because PCRE will
289        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
290        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
291        Perl does, and where it didn't before.
292    
293    24. Rewrite so as to remove the single use of %n from pcregrep because in some
294        Windows environments %n is disabled by default.
295    
296    
297    Version 7.4 21-Sep-07
298    ---------------------
299    
300    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
301        means that a class such as [\s] counted as "explicit reference to CR or
302        LF". That isn't really right - the whole point of the change was to try to
303        help when there was an actual mention of one of the two characters. So now
304        the change happens only if \r or \n (or a literal CR or LF) character is
305        encountered.
306    
307    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
308        of both had grown to the point where there were only 3 bits left.
309        Fortunately, there was spare space in the data structure, and so I have
310        moved the internal flags into a new 16-bit field to free up more option
311        bits.
312    
313    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
314        but did not set the internal JCHANGED flag - either of these is enough to
315        control the way the "get" function works - but the PCRE_INFO_JCHANGED
316        facility is supposed to tell if (?J) was ever used, so now (?J) at the
317        start sets both bits.
318    
319    4.  Added options (at build time, compile time, exec time) to change \R from
320        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
321    
322    5.  doc/pcresyntax.html was missing from the distribution.
323    
324    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
325        compatibility, even though it is no longer used.
326    
327    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
328        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
329        windows.h file is present (where different names are used). [This was
330        reversed later after testing - see 16 below.]
331    
332    8.  Changed all #include <config.h> to #include "config.h". There were also
333        some further <pcre.h> cases that I changed to "pcre.h".
334    
335    9.  When pcregrep was used with the --colour option, it missed the line ending
336        sequence off the lines that it output.
337    
338    10. It was pointed out to me that arrays of string pointers cause lots of
339        relocations when a shared library is dynamically loaded. A technique of
340        using a single long string with a table of offsets can drastically reduce
341        these. I have refactored PCRE in four places to do this. The result is
342        dramatic:
343    
344          Originally:                          290
345          After changing UCP table:            187
346          After changing error message table:   43
347          After changing table of "verbs"       36
348          After changing table of Posix names   22
349    
350        Thanks to the folks working on Gregex for glib for this insight.
351    
352    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
353        unicode-properties was also set.
354    
355    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
356    
357    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
358        checked only for CRLF.
359    
360    14. Added casts to pcretest.c to avoid compiler warnings.
361    
362    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
363    
364    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
365        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
366        entirely. This removes changes made in 7 above.
367    
368    17. The CMake files have been updated, and there is now more information about
369        building with CMake in the NON-UNIX-USE document.
370    
371    
372    Version 7.3 28-Aug-07
373  ---------------------  ---------------------
374    
375   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.346

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12