ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 236 by ph10, Tue Sep 11 12:57:06 2007 UTC revision 340 by ph10, Fri Apr 18 20:00:21 2008 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 7.4 10-Sep-07  Version 7.7 05-Mar-08
5    ---------------------
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.
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.)
15    3.  Remove a line of dead code, identified by coverity and reported by Nuno
16        Lopes.
18    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
20        (1) The include/exclude patterns were being applied to the whole pathnames
21            of files, instead of just to the final components.
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.
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.
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.
37    7.  Added some missing "const"s to declarations of static tables in
38        pcre_compile.c and pcre_dfa_exec.c.
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.)
44    9.  Applied Craig's patch to remove the use of push_back().
46    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
47        matching function regexec().
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).
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.
61    13. Added the PCRE_JAVASCRIPT_COMPAT option. This currently does two things:
62        (a) A lone ] character is dis-allowed (Perl treats it as data).
63        (b) A back reference to an unmatched subpattern matches an empty string
64            (Perl fails the current match path).
66    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
67        non-existent subpattern following a character class starting with ']' and
68        containing () gave an internal compiling error instead of "reference to
69        non-existent subpattern". Fortunately, when the pattern did exist, the
70        compiled code was correct. (When scanning forwards to check for the
71        existencd of the subpattern, it was treating the data ']' as terminating
72        the class, so got the count wrong. When actually compiling, the reference
73        was subsequently set up correctly.)
76    Version 7.6 28-Jan-08
77    ---------------------
79    1.  A character class containing a very large number of characters with
80        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
81        overflow.
83    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
84        HAVE_LONG_LONG is not defined.
86    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
87        bring them up to date and include new features. This patch includes:
89        - Fixed PH's badly added libz and libbz2 support.
90        - Fixed a problem with static linking.
91        - Added pcredemo. [But later removed - see 7 below.]
92        - Fixed dftables problem and added an option.
93        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
94            HAVE_LONG_LONG.
95        - Added readline support for pcretest.
96        - Added an listing of the option settings after cmake has run.
98    4.  A user submitted a patch to Makefile that makes it easy to create
99        "pcre.dll" under mingw when using Configure/Make. I added stuff to
100        Makefile.am that cause it to include this special target, without
101        affecting anything else. Note that the same mingw target plus all
102        the other distribution libraries and programs are now supported
103        when configuring with CMake (see 6 below) instead of with
104        Configure/Make.
106    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
107        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
108        exported in the Windows port". It has not yet been confirmed that the patch
109        solves the problem, but it does no harm.
111    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
112        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
113        with CMake, and also correct the comment about stack recursion.
115    7.  Remove the automatic building of pcredemo from the ./configure system and
116        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
117        of a program that users should build themselves after PCRE is installed, so
118        building it automatically is not really right. What is more, it gave
119        trouble in some build environments.
121    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
124    Version 7.5 10-Jan-08
125    ---------------------
127    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
128        values in parens when parsing an RE using the C++ wrapper."
130    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
131        Characters greater than 255 were excluded from the class instead of being
132        included.
134    3.  The same bug as (2) above applied to negated POSIX classes such as
135        [:^space:].
137    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
138        defined or documented. It seems to have been a typo for PCRE_STATIC, so
139        I have changed it.
141    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
142        first named subpattern) and a construct such as (?&a) would reference the
143        first named subpattern whose name started with "a" (in other words, the
144        length check was missing). Both these problems are fixed. "Subpattern name
145        expected" is now given for (?&) (a zero-length name), and this patch also
146        makes it give the same error for \k'' (previously it complained that that
147        was a reference to a non-existent subpattern).
149    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
150        this is right because (?- can be followed by option settings as well as by
151        digits. I have, however, made the messages clearer.
153    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
154        than the number used in the conditional) now cause a compile-time error.
155        This is actually not compatible with Perl, which accepts such patterns, but
156        treats the conditional as always being FALSE (as PCRE used to), but it
157        seems to me that giving a diagnostic is better.
159    8.  Change "alphameric" to the more common word "alphanumeric" in comments
160        and messages.
162    9.  Fix two occurrences of "backslash" in comments that should have been
163        "backspace".
165    10. Remove two redundant lines of code that can never be obeyed (their function
166        was moved elsewhere).
168    11. The program that makes PCRE's Unicode character property table had a bug
169        which caused it to generate incorrect table entries for sequences of
170        characters that have the same character type, but are in different scripts.
171        It amalgamated them into a single range, with the script of the first of
172        them. In other words, some characters were in the wrong script. There were
173        thirteen such cases, affecting characters in the following ranges:
175          U+002b0 - U+002c1
176          U+0060c - U+0060d
177          U+0061e - U+00612
178          U+0064b - U+0065e
179          U+0074d - U+0076d
180          U+01800 - U+01805
181          U+01d00 - U+01d77
182          U+01d9b - U+01dbf
183          U+0200b - U+0200f
184          U+030fc - U+030fe
185          U+03260 - U+0327f
186          U+0fb46 - U+0fbb1
187          U+10450 - U+1049d
189    12. The -o option (show only the matching part of a line) for pcregrep was not
190        compatible with GNU grep in that, if there was more than one match in a
191        line, it showed only the first of them. It now behaves in the same way as
192        GNU grep.
194    13. If the -o and -v options were combined for pcregrep, it printed a blank
195        line for every non-matching line. GNU grep prints nothing, and pcregrep now
196        does the same. The return code can be used to tell if there were any
197        non-matching lines.
199    14. Added --file-offsets and --line-offsets to pcregrep.
201    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
202        infinitely looping recursion. The bug was that positive lookaheads were not
203        being skipped when checking for a possible empty match (negative lookaheads
204        and both kinds of lookbehind were skipped).
206    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
207        inclusion of <windows.h> to before rather than after the definition of
208        INVALID_FILE_ATTRIBUTES (patch from David Byron).
210    17. Specifying a possessive quantifier with a specific limit for a Unicode
211        character property caused pcre_compile() to compile bad code, which led at
212        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
213        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
214        caused the error; without that there was no problem.
216    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
218    19. Added --enable-pcretest-libreadline.
220    20. In pcrecpp.cc, the variable 'count' was incremented twice in
221        RE::GlobalReplace(). As a result, the number of replacements returned was
222        double what it should be. I removed one of the increments, but Craig sent a
223        later patch that removed the other one (the right fix) and added unit tests
224        that check the return values (which was not done before).
226    21. Several CMake things:
228        (1) Arranged that, when cmake is used on Unix, the libraries end up with
229            the names libpcre and libpcreposix, not just pcre and pcreposix.
231        (2) The above change means that pcretest and pcregrep are now correctly
232            linked with the newly-built libraries, not previously installed ones.
236    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
237        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
238        UTF-8 newline character). The key issue is that the pattern starts .*;
239        this means that the match must be either at the beginning, or after a
240        newline. The bug was in the code for advancing after a failed match and
241        checking that the new position followed a newline. It was not taking
242        account of UTF-8 characters correctly.
244    23. PCRE was behaving differently from Perl in the way it recognized POSIX
245        character classes. PCRE was not treating the sequence [:...:] as a
246        character class unless the ... were all letters. Perl, however, seems to
247        allow any characters between [: and :], though of course it rejects as
248        unknown any "names" that contain non-letters, because all the known class
249        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
250        for example, whereas PCRE did not - it did not recognize a POSIX character
251        class. This seemed a bit dangerous, so the code has been changed to be
252        closer to Perl. The behaviour is not identical to Perl, because PCRE will
253        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
254        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
255        Perl does, and where it didn't before.
257    24. Rewrite so as to remove the single use of %n from pcregrep because in some
258        Windows environments %n is disabled by default.
261    Version 7.4 21-Sep-07
262  ---------------------  ---------------------
264  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 282  Version 7.4 10-Sep-07
283  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
284      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.  
286  6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward  5.  doc/pcresyntax.html was missing from the distribution.
288    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
289      compatibility, even though it is no longer used.      compatibility, even though it is no longer used.
291  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
292      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
293      different names are used).      windows.h file is present (where different names are used). [This was
294        reversed later after testing - see 16 below.]
295  8.  Changed all #include <config.h> to #include "config.h". There were also  
296    8.  Changed all #include <config.h> to #include "config.h". There were also
297      some further <pcre.h> cases that I changed to "pcre.h".      some further <pcre.h> cases that I changed to "pcre.h".
299    9.  When pcregrep was used with the --colour option, it missed the line ending
300        sequence off the lines that it output.
302    10. It was pointed out to me that arrays of string pointers cause lots of
303        relocations when a shared library is dynamically loaded. A technique of
304        using a single long string with a table of offsets can drastically reduce
305        these. I have refactored PCRE in four places to do this. The result is
306        dramatic:
308          Originally:                          290
309          After changing UCP table:            187
310          After changing error message table:   43
311          After changing table of "verbs"       36
312          After changing table of Posix names   22
314        Thanks to the folks working on Gregex for glib for this insight.
316    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
317        unicode-properties was also set.
319    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
321    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
322        checked only for CRLF.
324    14. Added casts to pcretest.c to avoid compiler warnings.
326    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
328    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
329        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
330        entirely. This removes changes made in 7 above.
332    17. The CMake files have been updated, and there is now more information about
333        building with CMake in the NON-UNIX-USE document.
336  Version 7.3 28-Aug-07  Version 7.3 28-Aug-07
337  ---------------------  ---------------------

Removed from v.236  
changed lines
  Added in v.340

  ViewVC Help
Powered by ViewVC 1.1.5