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

Diff of /code/trunk/ChangeLog

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

revision 268 by ph10, Thu Nov 15 10:28:09 2007 UTC revision 333 by ph10, Thu Apr 10 19:55:57 2008 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 7.5 12-Nov-07  Version 7.7 05-Mar-08
5    ---------------------
6    
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.
10    
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.)
14    
15    3.  Remove a line of dead code, identified by coverity and reported by Nuno
16        Lopes.
17    
18    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
19    
20        (1) The include/exclude patterns were being applied to the whole pathnames
21            of files, instead of just to the final components.
22    
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.
29    
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.
32    
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.
36    
37    7.  Added some missing "const"s to declarations of static tables in
38        pcre_compile.c and pcre_dfa_exec.c.
39    
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.)
43    
44    9.  Applied Craig's patch to remove the use of push_back().
45    
46    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
47        matching function regexec().
48    
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).
53    
54    
55    Version 7.6 28-Jan-08
56    ---------------------
57    
58    1.  A character class containing a very large number of characters with
59        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
60        overflow.
61    
62    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
63        HAVE_LONG_LONG is not defined.
64    
65    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
66        bring them up to date and include new features. This patch includes:
67    
68        - Fixed PH's badly added libz and libbz2 support.
69        - Fixed a problem with static linking.
70        - Added pcredemo. [But later removed - see 7 below.]
71        - Fixed dftables problem and added an option.
72        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
73            HAVE_LONG_LONG.
74        - Added readline support for pcretest.
75        - Added an listing of the option settings after cmake has run.
76    
77    4.  A user submitted a patch to Makefile that makes it easy to create
78        "pcre.dll" under mingw when using Configure/Make. I added stuff to
79        Makefile.am that cause it to include this special target, without
80        affecting anything else. Note that the same mingw target plus all
81        the other distribution libraries and programs are now supported
82        when configuring with CMake (see 6 below) instead of with
83        Configure/Make.
84    
85    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
86        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
87        exported in the Windows port". It has not yet been confirmed that the patch
88        solves the problem, but it does no harm.
89    
90    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
91        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
92        with CMake, and also correct the comment about stack recursion.
93    
94    7.  Remove the automatic building of pcredemo from the ./configure system and
95        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
96        of a program that users should build themselves after PCRE is installed, so
97        building it automatically is not really right. What is more, it gave
98        trouble in some build environments.
99    
100    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
101    
102    
103    Version 7.5 10-Jan-08
104  ---------------------  ---------------------
105    
106  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'
107      values in parens when parsing an RE using the C++ wrapper."      values in parens when parsing an RE using the C++ wrapper."
108    
109  2.  Negative specials like \S did not work in character classes in UTF-8 mode.  2.  Negative specials like \S did not work in character classes in UTF-8 mode.
110      Characters greater than 255 were excluded from the class instead of being      Characters greater than 255 were excluded from the class instead of being
111      included.      included.
112    
113  3.  The same bug as (2) above applied to negated POSIX classes such as  3.  The same bug as (2) above applied to negated POSIX classes such as
114      [:^space:].      [:^space:].
115    
116  4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it  4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
117      defined or documented. It seems to have been a typo for PCRE_STATIC, so      defined or documented. It seems to have been a typo for PCRE_STATIC, so
118      I have changed it.      I have changed it.
119    
120  5.  The construct (?&) was not diagnosed as a syntax error (it referenced the  5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
121      first named subpattern) and a construct such as (?&a) would reference the      first named subpattern) and a construct such as (?&a) would reference the
122      first named subpattern whose name started with "a" (in other words, the      first named subpattern whose name started with "a" (in other words, the
123      length check was missing).      length check was missing). Both these problems are fixed. "Subpattern name
124        expected" is now given for (?&) (a zero-length name), and this patch also
125        makes it give the same error for \k'' (previously it complained that that
126        was a reference to a non-existent subpattern).
127    
128    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
129        this is right because (?- can be followed by option settings as well as by
130        digits. I have, however, made the messages clearer.
131    
132    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
133        than the number used in the conditional) now cause a compile-time error.
134        This is actually not compatible with Perl, which accepts such patterns, but
135        treats the conditional as always being FALSE (as PCRE used to), but it
136        seems to me that giving a diagnostic is better.
137    
138    8.  Change "alphameric" to the more common word "alphanumeric" in comments
139        and messages.
140    
141    9.  Fix two occurrences of "backslash" in comments that should have been
142        "backspace".
143    
144    10. Remove two redundant lines of code that can never be obeyed (their function
145        was moved elsewhere).
146    
147    11. The program that makes PCRE's Unicode character property table had a bug
148        which caused it to generate incorrect table entries for sequences of
149        characters that have the same character type, but are in different scripts.
150        It amalgamated them into a single range, with the script of the first of
151        them. In other words, some characters were in the wrong script. There were
152        thirteen such cases, affecting characters in the following ranges:
153    
154          U+002b0 - U+002c1
155          U+0060c - U+0060d
156          U+0061e - U+00612
157          U+0064b - U+0065e
158          U+0074d - U+0076d
159          U+01800 - U+01805
160          U+01d00 - U+01d77
161          U+01d9b - U+01dbf
162          U+0200b - U+0200f
163          U+030fc - U+030fe
164          U+03260 - U+0327f
165          U+0fb46 - U+0fbb1
166          U+10450 - U+1049d
167    
168    12. The -o option (show only the matching part of a line) for pcregrep was not
169        compatible with GNU grep in that, if there was more than one match in a
170        line, it showed only the first of them. It now behaves in the same way as
171        GNU grep.
172    
173    13. If the -o and -v options were combined for pcregrep, it printed a blank
174        line for every non-matching line. GNU grep prints nothing, and pcregrep now
175        does the same. The return code can be used to tell if there were any
176        non-matching lines.
177    
178    14. Added --file-offsets and --line-offsets to pcregrep.
179    
180    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
181        infinitely looping recursion. The bug was that positive lookaheads were not
182        being skipped when checking for a possible empty match (negative lookaheads
183        and both kinds of lookbehind were skipped).
184    
185    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
186        inclusion of <windows.h> to before rather than after the definition of
187        INVALID_FILE_ATTRIBUTES (patch from David Byron).
188    
189    17. Specifying a possessive quantifier with a specific limit for a Unicode
190        character property caused pcre_compile() to compile bad code, which led at
191        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
192        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
193        caused the error; without that there was no problem.
194    
195    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
196    
197    19. Added --enable-pcretest-libreadline.
198    
199    20. In pcrecpp.cc, the variable 'count' was incremented twice in
200        RE::GlobalReplace(). As a result, the number of replacements returned was
201        double what it should be. I removed one of the increments, but Craig sent a
202        later patch that removed the other one (the right fix) and added unit tests
203        that check the return values (which was not done before).
204    
205    21. Several CMake things:
206    
207        (1) Arranged that, when cmake is used on Unix, the libraries end up with
208            the names libpcre and libpcreposix, not just pcre and pcreposix.
209    
210        (2) The above change means that pcretest and pcregrep are now correctly
211            linked with the newly-built libraries, not previously installed ones.
212    
213        (3) Added PCRE_SUPPORT_LIBREADLINE, PCRE_SUPPORT_LIBZ, PCRE_SUPPORT_LIBBZ2.
214    
215    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
216        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
217        UTF-8 newline character). The key issue is that the pattern starts .*;
218        this means that the match must be either at the beginning, or after a
219        newline. The bug was in the code for advancing after a failed match and
220        checking that the new position followed a newline. It was not taking
221        account of UTF-8 characters correctly.
222    
223    23. PCRE was behaving differently from Perl in the way it recognized POSIX
224        character classes. PCRE was not treating the sequence [:...:] as a
225        character class unless the ... were all letters. Perl, however, seems to
226        allow any characters between [: and :], though of course it rejects as
227        unknown any "names" that contain non-letters, because all the known class
228        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
229        for example, whereas PCRE did not - it did not recognize a POSIX character
230        class. This seemed a bit dangerous, so the code has been changed to be
231        closer to Perl. The behaviour is not identical to Perl, because PCRE will
232        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
233        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
234        Perl does, and where it didn't before.
235    
236    24. Rewrite so as to remove the single use of %n from pcregrep because in some
237        Windows environments %n is disabled by default.
238    
239    
240  Version 7.4 21-Sep-07  Version 7.4 21-Sep-07

Legend:
Removed from v.268  
changed lines
  Added in v.333

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12