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

Diff of /code/trunk/ChangeLog

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

revision 295 by ph10, Mon Dec 31 17:00:24 2007 UTC revision 426 by ph10, Wed Aug 26 15:38:32 2009 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 7.5 31-Dec-07  Version 8.00 ??-???-??
5    ----------------------
6    
7    1.  The table for translating pcre_compile() error codes into POSIX error codes
8        was out-of-date, and there was no check on the pcre_compile() error code
9        being within the table. This could lead to an OK return being given in
10        error.
11    
12    2.  Changed the call to open a subject file in pcregrep from fopen(pathname,
13        "r") to fopen(pathname, "rb"), which fixed a problem with some of the tests
14        in a Windows environment.
15    
16    3.  The pcregrep --count option prints the count for each file even when it is
17        zero, as does GNU grep. However, pcregrep was also printing all files when
18        --files-with-matches was added. Now, when both options are given, it prints
19        counts only for those files that have at least one match. (GNU grep just
20        prints the file name in this circumstance, but including the count seems
21        more useful - otherwise, why use --count?) Also ensured that the
22        combination -clh just lists non-zero counts, with no names.
23    
24    4.  The long form of the pcregrep -F option was incorrectly implemented as
25        --fixed_strings instead of --fixed-strings. This is an incompatible change,
26        but it seems right to fix it, and I didn't think it was worth preserving
27        the old behaviour.
28    
29    5.  The command line items --regex=pattern and --regexp=pattern were not
30        recognized by pcregrep, which required --regex pattern or --regexp pattern
31        (with a space rather than an '='). The man page documented the '=' forms,
32        which are compatible with GNU grep; these now work.
33    
34    6.  No libpcreposix.pc file was created for pkg-config; there was just
35        libpcre.pc and libpcrecpp.pc. The omission has been rectified.
36    
37    7.  Added #ifndef SUPPORT_UCP into the pcre_ucd.c module, to reduce its size
38        when UCP support is not needed, by modifying the Python script that
39        generates it from Unicode data files. This should not matter if the module
40        is correctly used as a library, but I received one complaint about 50K of
41        unwanted data. My guess is that the person linked everything into his
42        program rather than using a library. Anyway, it does no harm.
43    
44    8.  A pattern such as /\x{123}{2,2}+/8 was incorrectly compiled; the trigger
45        was a minimum greater than 1 for a wide character in a possessive
46        repetition. Chaos could result.
47    
48    9.  The restrictions on what a pattern can contain when partial matching is
49        requested for pcre_exec() have been removed. All patterns can now be
50        partially matched by this function. In addition, if there are at least two
51        slots in the offset vector, the offsets of the first-encountered partial
52        match are set in them when PCRE_ERROR_PARTIAL is returned.
53    
54    
55    Version 7.9 11-Apr-09
56    ---------------------
57    
58    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
59        (pcretest), all targets were linked against these libraries. This included
60        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
61        libraries. This caused unwanted dependencies to be created. This problem
62        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
63        pcretest is linked with readline.
64    
65    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
66        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
67        moved outside it again, because FALSE and TRUE are already defined in AIX,
68        but BOOL is not.
69    
70    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
71        PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
72    
73    4.  The pcregrep documentation said spaces were inserted as well as colons (or
74        hyphens) following file names and line numbers when outputting matching
75        lines. This is not true; no spaces are inserted. I have also clarified the
76        wording for the --colour (or --color) option.
77    
78    5.  In pcregrep, when --colour was used with -o, the list of matching strings
79        was not coloured; this is different to GNU grep, so I have changed it to be
80        the same.
81    
82    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
83        each matching line was coloured. Now it goes on to look for further matches
84        of any of the test patterns, which is the same behaviour as GNU grep.
85    
86    7.  A pattern that could match an empty string could cause pcregrep to loop; it
87        doesn't make sense to accept an empty string match in pcregrep, so I have
88        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
89        seems to be how GNU grep behaves.
90    
91    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
92        start or after a newline", because the conditional assertion was not being
93        correctly handled. The rule now is that both the assertion and what follows
94        in the first alternative must satisfy the test.
95    
96    9.  If auto-callout was enabled in a pattern with a conditional group whose
97        condition was an assertion, PCRE could crash during matching, both with
98        pcre_exec() and pcre_dfa_exec().
99    
100    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
101        used for matching.
102    
103    11. Unicode property support in character classes was not working for
104        characters (bytes) greater than 127 when not in UTF-8 mode.
105    
106    12. Added the -M command line option to pcretest.
107    
108    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
109    
110    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
111    
112    16. Added comments and documentation about mis-use of no_arg in the C++
113        wrapper.
114    
115    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
116        from Martin Jerabek that uses macro names for all relevant character and
117        string constants.
118    
119    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
120        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
121        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
122        these, but not everybody uses configure.
123    
124    19. A conditional group that had only one branch was not being correctly
125        recognized as an item that could match an empty string. This meant that an
126        enclosing group might also not be so recognized, causing infinite looping
127        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
128        with the subject "ab", where knowledge that the repeated group can match
129        nothing is needed in order to break the loop.
130    
131    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
132        exec(), but without supplying a callout function, matching went wrong.
133    
134    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
135        leak if the size of the offset vector was greater than 30. When the vector
136        is smaller, the saved offsets during recursion go onto a local stack
137        vector, but for larger vectors malloc() is used. It was failing to free
138        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
139        error, in fact).
140    
141    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
142        heapframe that is used only when UTF-8 support is enabled. This caused no
143        problem, but was untidy.
144    
145    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
146        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
147        included within another project.
148    
149    24. Steven Van Ingelgem's patches to add more options to the CMake support,
150        slightly modified by me:
151    
152          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
153              not building pcregrep.
154    
155          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
156              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
157    
158    25. Forward references, both numeric and by name, in patterns that made use of
159        duplicate group numbers, could behave incorrectly or give incorrect errors,
160        because when scanning forward to find the reference group, PCRE was not
161        taking into account the duplicate group numbers. A pattern such as
162        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
163    
164    26. Changed a few more instances of "const unsigned char *" to USPTR, making
165        the feature of a custom pointer more persuasive (as requested by a user).
166    
167    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
168        pcretest.c, inside #ifndefs, because it seems they are sometimes already
169        pre-defined.
170    
171    28. Added support for (*UTF8) at the start of a pattern.
172    
173    29. Arrange for flags added by the "release type" setting in CMake to be shown
174        in the configuration summary.
175    
176    
177    Version 7.8 05-Sep-08
178    ---------------------
179    
180    1.  Replaced UCP searching code with optimized version as implemented for Ad
181        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
182        stage table and inline lookup instead of a function, giving speed ups of 2
183        to 5 times on some simple patterns that I tested. Permission was given to
184        distribute the MultiStage2.py script that generates the tables (it's not in
185        the tarball, but is in the Subversion repository).
186    
187    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
188        scripts.
189    
190    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
191        a group with a zero qualifier. The result of the study could be incorrect,
192        or the function might crash, depending on the pattern.
193    
194    4.  Caseless matching was not working for non-ASCII characters in back
195        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
196        It now works when Unicode Property Support is available.
197    
198    5.  In pcretest, an escape such as \x{de} in the data was always generating
199        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
200        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
201        truncation.
202    
203    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
204    
205    7.  Added two (int) casts to pcregrep when printing the difference of two
206        pointers, in case they are 64-bit values.
207    
208    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
209        test 2 if it fails.
210    
211    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
212        and a #define of that name to empty if it is not externally set. This is to
213        allow users of MSVC to set it if necessary.
214    
215    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
216        the convenience functions in the pcre_get.c source file.
217    
218    11. An option change at the start of a pattern that had top-level alternatives
219        could cause overwriting and/or a crash. This command provoked a crash in
220        some environments:
221    
222          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
223    
224        This potential security problem was recorded as CVE-2008-2371.
225    
226    12. For a pattern where the match had to start at the beginning or immediately
227        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
228        pcre_dfa_exec() could read past the end of the passed subject if there was
229        no match. To help with detecting such bugs (e.g. with valgrind), I modified
230        pcretest so that it places the subject at the end of its malloc-ed buffer.
231    
232    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
233        exec() might read past the end of the data buffer in UTF-8 mode.
234    
235    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
236        the data contained the byte 0x85 as part of a UTF-8 character within its
237        first line. This applied both to normal and DFA matching.
238    
239    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
240        /^[^d]*?$/8 failed to match "abc".
241    
242    16. Added a missing copyright notice to pcrecpp_internal.h.
243    
244    17. Make it more clear in the documentation that values returned from
245        pcre_exec() in ovector are byte offsets, not character counts.
246    
247    18. Tidied a few places to stop certain compilers from issuing warnings.
248    
249    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
250        supplied by Stefan Weber. I made a further small update for 7.8 because
251        there is a change of source arrangements: the pcre_searchfuncs.c module is
252        replaced by pcre_ucd.c.
253    
254    
255    Version 7.7 07-May-08
256    ---------------------
257    
258    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
259        a string to a long long, pretend we don't even have a long long." This is
260        done by checking for the strtoq, strtoll, and _strtoi64 functions.
261    
262    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
263        pre-7.6 versions, which defined a global no_arg variable instead of putting
264        it in the RE class. (See also #8 below.)
265    
266    3.  Remove a line of dead code, identified by coverity and reported by Nuno
267        Lopes.
268    
269    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
270    
271        (1) The include/exclude patterns were being applied to the whole pathnames
272            of files, instead of just to the final components.
273    
274        (2) If there was more than one level of directory, the subdirectories were
275            skipped unless they satisfied the include/exclude conditions. This is
276            inconsistent with GNU grep (and could even be seen as contrary to the
277            pcregrep specification - which I improved to make it absolutely clear).
278            The action now is always to scan all levels of directory, and just
279            apply the include/exclude patterns to regular files.
280    
281    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
282        --exclude_dir in the tests to avoid scanning .svn directories.
283    
284    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
285        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
286        doesn't support NULs in patterns.
287    
288    7.  Added some missing "const"s to declarations of static tables in
289        pcre_compile.c and pcre_dfa_exec.c.
290    
291    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
292        caused by fix #2  above. (Subsequently also a second patch to fix the
293        first patch. And a third patch - this was a messy problem.)
294    
295    9.  Applied Craig's patch to remove the use of push_back().
296    
297    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
298        matching function regexec().
299    
300    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
301        which, however, unlike Perl's \g{...}, are subroutine calls, not back
302        references. PCRE supports relative numbers with this syntax (I don't think
303        Oniguruma does).
304    
305    12. Previously, a group with a zero repeat such as (...){0} was completely
306        omitted from the compiled regex. However, this means that if the group
307        was called as a subroutine from elsewhere in the pattern, things went wrong
308        (an internal error was given). Such groups are now left in the compiled
309        pattern, with a new opcode that causes them to be skipped at execution
310        time.
311    
312    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
313        to the way PCRE behaves:
314    
315        (a) A lone ] character is dis-allowed (Perl treats it as data).
316    
317        (b) A back reference to an unmatched subpattern matches an empty string
318            (Perl fails the current match path).
319    
320        (c) A data ] in a character class must be notated as \] because if the
321            first data character in a class is ], it defines an empty class. (In
322            Perl it is not possible to have an empty class.) The empty class []
323            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
324            The negative empty class [^] matches any one character, independently
325            of the DOTALL setting.
326    
327    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
328        non-existent subpattern following a character class starting with ']' and
329        containing () gave an internal compiling error instead of "reference to
330        non-existent subpattern". Fortunately, when the pattern did exist, the
331        compiled code was correct. (When scanning forwards to check for the
332        existencd of the subpattern, it was treating the data ']' as terminating
333        the class, so got the count wrong. When actually compiling, the reference
334        was subsequently set up correctly.)
335    
336    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
337        it was being rejected as not supported by pcre_dfa_exec(), even though
338        other assertions are supported. I have made pcre_dfa_exec() support
339        (*FAIL).
340    
341    16. The implementation of 13c above involved the invention of a new opcode,
342        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
343        cannot be changed at match time, I realized I could make a small
344        improvement to matching performance by compiling OP_ALLANY instead of
345        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
346        on the OP_ANY path.
347    
348    17. Compiling pcretest on Windows with readline support failed without the
349        following two fixes: (1) Make the unistd.h include conditional on
350        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
351    
352    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
353        ncurses library to be included for pcretest when ReadLine support is
354        requested, but also to allow for it to be overridden. This patch came from
355        Daniel Bergström.
356    
357    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
358        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
359        any errors with the current Unicode tables. Thanks to Peter Kankowski for
360        spotting this.
361    
362    
363    Version 7.6 28-Jan-08
364    ---------------------
365    
366    1.  A character class containing a very large number of characters with
367        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
368        overflow.
369    
370    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
371        HAVE_LONG_LONG is not defined.
372    
373    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
374        bring them up to date and include new features. This patch includes:
375    
376        - Fixed PH's badly added libz and libbz2 support.
377        - Fixed a problem with static linking.
378        - Added pcredemo. [But later removed - see 7 below.]
379        - Fixed dftables problem and added an option.
380        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
381            HAVE_LONG_LONG.
382        - Added readline support for pcretest.
383        - Added an listing of the option settings after cmake has run.
384    
385    4.  A user submitted a patch to Makefile that makes it easy to create
386        "pcre.dll" under mingw when using Configure/Make. I added stuff to
387        Makefile.am that cause it to include this special target, without
388        affecting anything else. Note that the same mingw target plus all
389        the other distribution libraries and programs are now supported
390        when configuring with CMake (see 6 below) instead of with
391        Configure/Make.
392    
393    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
394        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
395        exported in the Windows port". It has not yet been confirmed that the patch
396        solves the problem, but it does no harm.
397    
398    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
399        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
400        with CMake, and also correct the comment about stack recursion.
401    
402    7.  Remove the automatic building of pcredemo from the ./configure system and
403        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
404        of a program that users should build themselves after PCRE is installed, so
405        building it automatically is not really right. What is more, it gave
406        trouble in some build environments.
407    
408    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
409    
410    
411    Version 7.5 10-Jan-08
412  ---------------------  ---------------------
413    
414  1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'  1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
# Line 99  Version 7.5 31-Dec-07 Line 506  Version 7.5 31-Dec-07
506    
507  20. In pcrecpp.cc, the variable 'count' was incremented twice in  20. In pcrecpp.cc, the variable 'count' was incremented twice in
508      RE::GlobalReplace(). As a result, the number of replacements returned was      RE::GlobalReplace(). As a result, the number of replacements returned was
509      double what it should be. I have removed one of the increments.      double what it should be. I removed one of the increments, but Craig sent a
510        later patch that removed the other one (the right fix) and added unit tests
511        that check the return values (which was not done before).
512    
513  21. Several CMake things:  21. Several CMake things:
514    
# Line 110  Version 7.5 31-Dec-07 Line 519  Version 7.5 31-Dec-07
519          linked with the newly-built libraries, not previously installed ones.          linked with the newly-built libraries, not previously installed ones.
520    
521      (3) Added PCRE_SUPPORT_LIBREADLINE, PCRE_SUPPORT_LIBZ, PCRE_SUPPORT_LIBBZ2.      (3) Added PCRE_SUPPORT_LIBREADLINE, PCRE_SUPPORT_LIBZ, PCRE_SUPPORT_LIBBZ2.
522    
523  22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*  22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
524      crashed when matching a string such as a\x{2029}b (note that \x{2029} is a      crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
525      UTF-8 newline character). The key issue is that the pattern starts .*;      UTF-8 newline character). The key issue is that the pattern starts .*;
526      this means that the match must be either at the beginning, or after a      this means that the match must be either at the beginning, or after a
527      newline. The bug was in the code for advancing after a failed match and      newline. The bug was in the code for advancing after a failed match and
528      checking that the new position followed a newline. It was not taking      checking that the new position followed a newline. It was not taking
529      account of UTF-8 characters correctly.      account of UTF-8 characters correctly.
530    
531  23. PCRE was behaving differently from Perl in the way it recognized POSIX  23. PCRE was behaving differently from Perl in the way it recognized POSIX
532      character classes. PCRE was not treating the sequence [:...:] as a      character classes. PCRE was not treating the sequence [:...:] as a
533      character class unless the ... were all letters. Perl, however, seems to      character class unless the ... were all letters. Perl, however, seems to
534      allow any characters between [: and :], though of course it rejects as      allow any characters between [: and :], though of course it rejects as
535      unknown any "names" that contain non-letters, because all the known class      unknown any "names" that contain non-letters, because all the known class
536      names consist only of letters. Thus, Perl gives an error for [[:1234:]],      names consist only of letters. Thus, Perl gives an error for [[:1234:]],
537      for example, whereas PCRE did not - it did not recognize a POSIX character      for example, whereas PCRE did not - it did not recognize a POSIX character
538      class. This seemed a bit dangerous, so the code has been changed to be      class. This seemed a bit dangerous, so the code has been changed to be
539      closer to Perl. The behaviour is not identical to Perl, because PCRE will      closer to Perl. The behaviour is not identical to Perl, because PCRE will
540      diagnose an unknown class for, for example, [[:l\ower:]] where Perl will      diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
541      treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where      treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
542      Perl does, and where it didn't before.      Perl does, and where it didn't before.
543    
544    24. Rewrite so as to remove the single use of %n from pcregrep because in some
545        Windows environments %n is disabled by default.
546    
547    
548  Version 7.4 21-Sep-07  Version 7.4 21-Sep-07

Legend:
Removed from v.295  
changed lines
  Added in v.426

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12