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 321 by ph10, Wed Mar 5 17:10:45 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.
12    Version 7.6 28-Jan-08
13    ---------------------
15    1.  A character class containing a very large number of characters with
16        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
17        overflow.
19    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
20        HAVE_LONG_LONG is not defined.
22    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
23        bring them up to date and include new features. This patch includes:
25        - Fixed PH's badly added libz and libbz2 support.
26        - Fixed a problem with static linking.
27        - Added pcredemo. [But later removed - see 7 below.]
28        - Fixed dftables problem and added an option.
29        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
30            HAVE_LONG_LONG.
31        - Added readline support for pcretest.
32        - Added an listing of the option settings after cmake has run.
34    4.  A user submitted a patch to Makefile that makes it easy to create
35        "pcre.dll" under mingw when using Configure/Make. I added stuff to
36        Makefile.am that cause it to include this special target, without
37        affecting anything else. Note that the same mingw target plus all
38        the other distribution libraries and programs are now supported
39        when configuring with CMake (see 6 below) instead of with
40        Configure/Make.
42    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
43        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
44        exported in the Windows port". It has not yet been confirmed that the patch
45        solves the problem, but it does no harm.
47    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
48        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
49        with CMake, and also correct the comment about stack recursion.
51    7.  Remove the automatic building of pcredemo from the ./configure system and
52        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
53        of a program that users should build themselves after PCRE is installed, so
54        building it automatically is not really right. What is more, it gave
55        trouble in some build environments.
57    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
60    Version 7.5 10-Jan-08
61    ---------------------
63    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
64        values in parens when parsing an RE using the C++ wrapper."
66    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
67        Characters greater than 255 were excluded from the class instead of being
68        included.
70    3.  The same bug as (2) above applied to negated POSIX classes such as
71        [:^space:].
73    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
74        defined or documented. It seems to have been a typo for PCRE_STATIC, so
75        I have changed it.
77    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
78        first named subpattern) and a construct such as (?&a) would reference the
79        first named subpattern whose name started with "a" (in other words, the
80        length check was missing). Both these problems are fixed. "Subpattern name
81        expected" is now given for (?&) (a zero-length name), and this patch also
82        makes it give the same error for \k'' (previously it complained that that
83        was a reference to a non-existent subpattern).
85    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
86        this is right because (?- can be followed by option settings as well as by
87        digits. I have, however, made the messages clearer.
89    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
90        than the number used in the conditional) now cause a compile-time error.
91        This is actually not compatible with Perl, which accepts such patterns, but
92        treats the conditional as always being FALSE (as PCRE used to), but it
93        seems to me that giving a diagnostic is better.
95    8.  Change "alphameric" to the more common word "alphanumeric" in comments
96        and messages.
98    9.  Fix two occurrences of "backslash" in comments that should have been
99        "backspace".
101    10. Remove two redundant lines of code that can never be obeyed (their function
102        was moved elsewhere).
104    11. The program that makes PCRE's Unicode character property table had a bug
105        which caused it to generate incorrect table entries for sequences of
106        characters that have the same character type, but are in different scripts.
107        It amalgamated them into a single range, with the script of the first of
108        them. In other words, some characters were in the wrong script. There were
109        thirteen such cases, affecting characters in the following ranges:
111          U+002b0 - U+002c1
112          U+0060c - U+0060d
113          U+0061e - U+00612
114          U+0064b - U+0065e
115          U+0074d - U+0076d
116          U+01800 - U+01805
117          U+01d00 - U+01d77
118          U+01d9b - U+01dbf
119          U+0200b - U+0200f
120          U+030fc - U+030fe
121          U+03260 - U+0327f
122          U+0fb46 - U+0fbb1
123          U+10450 - U+1049d
125    12. The -o option (show only the matching part of a line) for pcregrep was not
126        compatible with GNU grep in that, if there was more than one match in a
127        line, it showed only the first of them. It now behaves in the same way as
128        GNU grep.
130    13. If the -o and -v options were combined for pcregrep, it printed a blank
131        line for every non-matching line. GNU grep prints nothing, and pcregrep now
132        does the same. The return code can be used to tell if there were any
133        non-matching lines.
135    14. Added --file-offsets and --line-offsets to pcregrep.
137    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
138        infinitely looping recursion. The bug was that positive lookaheads were not
139        being skipped when checking for a possible empty match (negative lookaheads
140        and both kinds of lookbehind were skipped).
142    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
143        inclusion of <windows.h> to before rather than after the definition of
144        INVALID_FILE_ATTRIBUTES (patch from David Byron).
146    17. Specifying a possessive quantifier with a specific limit for a Unicode
147        character property caused pcre_compile() to compile bad code, which led at
148        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
149        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
150        caused the error; without that there was no problem.
152    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
154    19. Added --enable-pcretest-libreadline.
156    20. In pcrecpp.cc, the variable 'count' was incremented twice in
157        RE::GlobalReplace(). As a result, the number of replacements returned was
158        double what it should be. I removed one of the increments, but Craig sent a
159        later patch that removed the other one (the right fix) and added unit tests
160        that check the return values (which was not done before).
162    21. Several CMake things:
164        (1) Arranged that, when cmake is used on Unix, the libraries end up with
165            the names libpcre and libpcreposix, not just pcre and pcreposix.
167        (2) The above change means that pcretest and pcregrep are now correctly
168            linked with the newly-built libraries, not previously installed ones.
172    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
173        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
174        UTF-8 newline character). The key issue is that the pattern starts .*;
175        this means that the match must be either at the beginning, or after a
176        newline. The bug was in the code for advancing after a failed match and
177        checking that the new position followed a newline. It was not taking
178        account of UTF-8 characters correctly.
180    23. PCRE was behaving differently from Perl in the way it recognized POSIX
181        character classes. PCRE was not treating the sequence [:...:] as a
182        character class unless the ... were all letters. Perl, however, seems to
183        allow any characters between [: and :], though of course it rejects as
184        unknown any "names" that contain non-letters, because all the known class
185        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
186        for example, whereas PCRE did not - it did not recognize a POSIX character
187        class. This seemed a bit dangerous, so the code has been changed to be
188        closer to Perl. The behaviour is not identical to Perl, because PCRE will
189        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
190        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
191        Perl does, and where it didn't before.
193    24. Rewrite so as to remove the single use of %n from pcregrep because in some
194        Windows environments %n is disabled by default.
197    Version 7.4 21-Sep-07
198  ---------------------  ---------------------
200  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 218  Version 7.4 10-Sep-07
219  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
220      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.  
222  6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward  5.  doc/pcresyntax.html was missing from the distribution.
224    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
225      compatibility, even though it is no longer used.      compatibility, even though it is no longer used.
227  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
228      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
229      different names are used).      windows.h file is present (where different names are used). [This was
230        reversed later after testing - see 16 below.]
231  8.  Changed all #include <config.h> to #include "config.h". There were also  
232    8.  Changed all #include <config.h> to #include "config.h". There were also
233      some further <pcre.h> cases that I changed to "pcre.h".      some further <pcre.h> cases that I changed to "pcre.h".
235    9.  When pcregrep was used with the --colour option, it missed the line ending
236        sequence off the lines that it output.
238    10. It was pointed out to me that arrays of string pointers cause lots of
239        relocations when a shared library is dynamically loaded. A technique of
240        using a single long string with a table of offsets can drastically reduce
241        these. I have refactored PCRE in four places to do this. The result is
242        dramatic:
244          Originally:                          290
245          After changing UCP table:            187
246          After changing error message table:   43
247          After changing table of "verbs"       36
248          After changing table of Posix names   22
250        Thanks to the folks working on Gregex for glib for this insight.
252    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
253        unicode-properties was also set.
255    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
257    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
258        checked only for CRLF.
260    14. Added casts to pcretest.c to avoid compiler warnings.
262    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
264    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
265        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
266        entirely. This removes changes made in 7 above.
268    17. The CMake files have been updated, and there is now more information about
269        building with CMake in the NON-UNIX-USE document.
272  Version 7.3 28-Aug-07  Version 7.3 28-Aug-07
273  ---------------------  ---------------------

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

  ViewVC Help
Powered by ViewVC 1.1.5