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 311 by ph10, Wed Jan 23 17:34:58 2008 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 7.3 17-Aug-07  Version 7.6 21-Jan-08
5    ---------------------
7    1.  A character class containing a very large number of characters with
8        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
9        overflow.
11    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
12        HAVE_LONG_LONG is not defined.
14    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
15        bring them up to date and include new features. This patch includes:
17        - Fixed PH's badly added libz and libbz2 support.
18        - Fixed a problem with static linking.
19        - Added pcredemo.
20        - Fixed dftables problem and added an option.
21        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
22            HAVE_LONG_LONG.
23        - Added readline support for pcretest.
24        - Added an listing of the option settings after cmake has run.
26    4.  A user submitted a patch to Makefile that makes it easy to created a dll
27        under mingw. I added stuff to Makefile.am that cause it to include this
28        special target, without affecting anything else.
30    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
31        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
32        exported in the Windows port". It has not yet been confirmed that the patch
33        solves the problem, but it does no harm.
35    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
36        NON_STANDARD_LIB_SUFFIX and correct the comment about stack recursion.
39    Version 7.5 10-Jan-08
40    ---------------------
42    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
43        values in parens when parsing an RE using the C++ wrapper."
45    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
46        Characters greater than 255 were excluded from the class instead of being
47        included.
49    3.  The same bug as (2) above applied to negated POSIX classes such as
50        [:^space:].
52    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
53        defined or documented. It seems to have been a typo for PCRE_STATIC, so
54        I have changed it.
56    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
57        first named subpattern) and a construct such as (?&a) would reference the
58        first named subpattern whose name started with "a" (in other words, the
59        length check was missing). Both these problems are fixed. "Subpattern name
60        expected" is now given for (?&) (a zero-length name), and this patch also
61        makes it give the same error for \k'' (previously it complained that that
62        was a reference to a non-existent subpattern).
64    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
65        this is right because (?- can be followed by option settings as well as by
66        digits. I have, however, made the messages clearer.
68    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
69        than the number used in the conditional) now cause a compile-time error.
70        This is actually not compatible with Perl, which accepts such patterns, but
71        treats the conditional as always being FALSE (as PCRE used to), but it
72        seems to me that giving a diagnostic is better.
74    8.  Change "alphameric" to the more common word "alphanumeric" in comments
75        and messages.
77    9.  Fix two occurrences of "backslash" in comments that should have been
78        "backspace".
80    10. Remove two redundant lines of code that can never be obeyed (their function
81        was moved elsewhere).
83    11. The program that makes PCRE's Unicode character property table had a bug
84        which caused it to generate incorrect table entries for sequences of
85        characters that have the same character type, but are in different scripts.
86        It amalgamated them into a single range, with the script of the first of
87        them. In other words, some characters were in the wrong script. There were
88        thirteen such cases, affecting characters in the following ranges:
90          U+002b0 - U+002c1
91          U+0060c - U+0060d
92          U+0061e - U+00612
93          U+0064b - U+0065e
94          U+0074d - U+0076d
95          U+01800 - U+01805
96          U+01d00 - U+01d77
97          U+01d9b - U+01dbf
98          U+0200b - U+0200f
99          U+030fc - U+030fe
100          U+03260 - U+0327f
101          U+0fb46 - U+0fbb1
102          U+10450 - U+1049d
104    12. The -o option (show only the matching part of a line) for pcregrep was not
105        compatible with GNU grep in that, if there was more than one match in a
106        line, it showed only the first of them. It now behaves in the same way as
107        GNU grep.
109    13. If the -o and -v options were combined for pcregrep, it printed a blank
110        line for every non-matching line. GNU grep prints nothing, and pcregrep now
111        does the same. The return code can be used to tell if there were any
112        non-matching lines.
114    14. Added --file-offsets and --line-offsets to pcregrep.
116    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
117        infinitely looping recursion. The bug was that positive lookaheads were not
118        being skipped when checking for a possible empty match (negative lookaheads
119        and both kinds of lookbehind were skipped).
121    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
122        inclusion of <windows.h> to before rather than after the definition of
123        INVALID_FILE_ATTRIBUTES (patch from David Byron).
125    17. Specifying a possessive quantifier with a specific limit for a Unicode
126        character property caused pcre_compile() to compile bad code, which led at
127        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
128        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
129        caused the error; without that there was no problem.
131    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
133    19. Added --enable-pcretest-libreadline.
135    20. In pcrecpp.cc, the variable 'count' was incremented twice in
136        RE::GlobalReplace(). As a result, the number of replacements returned was
137        double what it should be. I removed one of the increments, but Craig sent a
138        later patch that removed the other one (the right fix) and added unit tests
139        that check the return values (which was not done before).
141    21. Several CMake things:
143        (1) Arranged that, when cmake is used on Unix, the libraries end up with
144            the names libpcre and libpcreposix, not just pcre and pcreposix.
146        (2) The above change means that pcretest and pcregrep are now correctly
147            linked with the newly-built libraries, not previously installed ones.
151    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
152        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
153        UTF-8 newline character). The key issue is that the pattern starts .*;
154        this means that the match must be either at the beginning, or after a
155        newline. The bug was in the code for advancing after a failed match and
156        checking that the new position followed a newline. It was not taking
157        account of UTF-8 characters correctly.
159    23. PCRE was behaving differently from Perl in the way it recognized POSIX
160        character classes. PCRE was not treating the sequence [:...:] as a
161        character class unless the ... were all letters. Perl, however, seems to
162        allow any characters between [: and :], though of course it rejects as
163        unknown any "names" that contain non-letters, because all the known class
164        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
165        for example, whereas PCRE did not - it did not recognize a POSIX character
166        class. This seemed a bit dangerous, so the code has been changed to be
167        closer to Perl. The behaviour is not identical to Perl, because PCRE will
168        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
169        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
170        Perl does, and where it didn't before.
172    24. Rewrite so as to remove the single use of %n from pcregrep because in some
173        Windows environments %n is disabled by default.
176    Version 7.4 21-Sep-07
177    ---------------------
179    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
180        means that a class such as [\s] counted as "explicit reference to CR or
181        LF". That isn't really right - the whole point of the change was to try to
182        help when there was an actual mention of one of the two characters. So now
183        the change happens only if \r or \n (or a literal CR or LF) character is
184        encountered.
186    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
187        of both had grown to the point where there were only 3 bits left.
188        Fortunately, there was spare space in the data structure, and so I have
189        moved the internal flags into a new 16-bit field to free up more option
190        bits.
192    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
193        but did not set the internal JCHANGED flag - either of these is enough to
194        control the way the "get" function works - but the PCRE_INFO_JCHANGED
195        facility is supposed to tell if (?J) was ever used, so now (?J) at the
196        start sets both bits.
198    4.  Added options (at build time, compile time, exec time) to change \R from
199        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
201    5.  doc/pcresyntax.html was missing from the distribution.
203    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
204        compatibility, even though it is no longer used.
206    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
207        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
208        windows.h file is present (where different names are used). [This was
209        reversed later after testing - see 16 below.]
211    8.  Changed all #include <config.h> to #include "config.h". There were also
212        some further <pcre.h> cases that I changed to "pcre.h".
214    9.  When pcregrep was used with the --colour option, it missed the line ending
215        sequence off the lines that it output.
217    10. It was pointed out to me that arrays of string pointers cause lots of
218        relocations when a shared library is dynamically loaded. A technique of
219        using a single long string with a table of offsets can drastically reduce
220        these. I have refactored PCRE in four places to do this. The result is
221        dramatic:
223          Originally:                          290
224          After changing UCP table:            187
225          After changing error message table:   43
226          After changing table of "verbs"       36
227          After changing table of Posix names   22
229        Thanks to the folks working on Gregex for glib for this insight.
231    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
232        unicode-properties was also set.
234    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
236    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
237        checked only for CRLF.
239    14. Added casts to pcretest.c to avoid compiler warnings.
241    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
243    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
244        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
245        entirely. This removes changes made in 7 above.
247    17. The CMake files have been updated, and there is now more information about
248        building with CMake in the NON-UNIX-USE document.
251    Version 7.3 28-Aug-07
252  ---------------------  ---------------------
254   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 390  Version 7.3 17-Aug-07
390  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
391      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").
393    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
395    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
396        character were causing crashes (broken optimization).
398    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
399        \p or \P) caused a compile-time loop.
401    28. More problems have arisen in unanchored patterns when CRLF is a valid line
402        break. For example, the unstudied pattern [\r\n]A does not match the string
403        "\r\nA" because change 7.0/46 below moves the current point on by two
404        characters after failing to match at the start. However, the pattern \nA
405        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
406        the same is true. There doesn't seem any very clean way out of this, but
407        what I have chosen to do makes the common cases work: PCRE now takes note
408        of whether there can be an explicit match for \r or \n anywhere in the
409        pattern, and if so, 7.0/46 no longer applies. As part of this change,
410        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
411        pattern has explicit CR or LF references.
413    29. Added (*CR) etc for changing newline setting at start of pattern.
416  Version 7.2 19-Jun-07  Version 7.2 19-Jun-07
417  ---------------------  ---------------------

Removed from v.221  
changed lines
  Added in v.311

  ViewVC Help
Powered by ViewVC 1.1.5