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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.272  
changed lines
  Added in v.336

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12