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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.282  
changed lines
  Added in v.331

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12