ViewVC logotype

Diff of /code/trunk/ChangeLog

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

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

Removed from v.223  
changed lines
  Added in v.296

  ViewVC Help
Powered by ViewVC 1.1.5