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

Diff of /code/trunk/ChangeLog

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

revision 284 by ph10, Fri Dec 7 20:01:16 2007 UTC revision 357 by ph10, Tue Jul 8 14:18:28 2008 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 7.5 12-Nov-07  Version 8.0 02 Jul-08
5    ---------------------
6    
7    1.  Replaced UCP searching code with optimized version as implemented for Ad
8        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
9        stage table and inline lookup instead of a function, giving speed ups of 2
10        to 5 times on some simple patterns that I tested. Permission was given to
11        distribute the MultiStage2.py script that generates the tables (it's not in
12        the tarball, but is in the Subversion repository).
13    
14    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
15        scripts.
16    
17    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
18        a group with a zero qualifier. The result of the study could be incorrect,
19        or the function might crash, depending on the pattern.
20    
21    4.  Caseless matching was not working for non-ASCII characters in back
22        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
23        It now works when Unicode Property Support is available.
24    
25    5.  In pcretest, an escape such as \x{de} in the data was always generating
26        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
27        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
28        truncation.
29    
30    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
31    
32    7.  Added two (int) casts to pcregrep when printing the difference of two
33        pointers, in case they are 64-bit values.
34    
35    
36    Version 7.7 07-May-08
37    ---------------------
38    
39    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
40        a string to a long long, pretend we don't even have a long long." This is
41        done by checking for the strtoq, strtoll, and _strtoi64 functions.
42    
43    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
44        pre-7.6 versions, which defined a global no_arg variable instead of putting
45        it in the RE class. (See also #8 below.)
46    
47    3.  Remove a line of dead code, identified by coverity and reported by Nuno
48        Lopes.
49    
50    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
51    
52        (1) The include/exclude patterns were being applied to the whole pathnames
53            of files, instead of just to the final components.
54    
55        (2) If there was more than one level of directory, the subdirectories were
56            skipped unless they satisfied the include/exclude conditions. This is
57            inconsistent with GNU grep (and could even be seen as contrary to the
58            pcregrep specification - which I improved to make it absolutely clear).
59            The action now is always to scan all levels of directory, and just
60            apply the include/exclude patterns to regular files.
61    
62    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
63        --exclude_dir in the tests to avoid scanning .svn directories.
64    
65    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
66        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
67        doesn't support NULs in patterns.
68    
69    7.  Added some missing "const"s to declarations of static tables in
70        pcre_compile.c and pcre_dfa_exec.c.
71    
72    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
73        caused by fix #2  above. (Subsequently also a second patch to fix the
74        first patch. And a third patch - this was a messy problem.)
75    
76    9.  Applied Craig's patch to remove the use of push_back().
77    
78    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
79        matching function regexec().
80    
81    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
82        which, however, unlike Perl's \g{...}, are subroutine calls, not back
83        references. PCRE supports relative numbers with this syntax (I don't think
84        Oniguruma does).
85    
86    12. Previously, a group with a zero repeat such as (...){0} was completely
87        omitted from the compiled regex. However, this means that if the group
88        was called as a subroutine from elsewhere in the pattern, things went wrong
89        (an internal error was given). Such groups are now left in the compiled
90        pattern, with a new opcode that causes them to be skipped at execution
91        time.
92    
93    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
94        to the way PCRE behaves:
95    
96        (a) A lone ] character is dis-allowed (Perl treats it as data).
97    
98        (b) A back reference to an unmatched subpattern matches an empty string
99            (Perl fails the current match path).
100    
101        (c) A data ] in a character class must be notated as \] because if the
102            first data character in a class is ], it defines an empty class. (In
103            Perl it is not possible to have an empty class.) The empty class []
104            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
105            The negative empty class [^] matches any one character, independently
106            of the DOTALL setting.
107    
108    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
109        non-existent subpattern following a character class starting with ']' and
110        containing () gave an internal compiling error instead of "reference to
111        non-existent subpattern". Fortunately, when the pattern did exist, the
112        compiled code was correct. (When scanning forwards to check for the
113        existencd of the subpattern, it was treating the data ']' as terminating
114        the class, so got the count wrong. When actually compiling, the reference
115        was subsequently set up correctly.)
116    
117    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
118        it was being rejected as not supported by pcre_dfa_exec(), even though
119        other assertions are supported. I have made pcre_dfa_exec() support
120        (*FAIL).
121    
122    16. The implementation of 13c above involved the invention of a new opcode,
123        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
124        cannot be changed at match time, I realized I could make a small
125        improvement to matching performance by compiling OP_ALLANY instead of
126        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
127        on the OP_ANY path.
128    
129    17. Compiling pcretest on Windows with readline support failed without the
130        following two fixes: (1) Make the unistd.h include conditional on
131        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
132    
133    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
134        ncurses library to be included for pcretest when ReadLine support is
135        requested, but also to allow for it to be overridden. This patch came from
136        Daniel Bergström.
137    
138    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
139        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
140        any errors with the current Unicode tables. Thanks to Peter Kankowski for
141        spotting this.
142    
143    
144    Version 7.6 28-Jan-08
145    ---------------------
146    
147    1.  A character class containing a very large number of characters with
148        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
149        overflow.
150    
151    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
152        HAVE_LONG_LONG is not defined.
153    
154    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
155        bring them up to date and include new features. This patch includes:
156    
157        - Fixed PH's badly added libz and libbz2 support.
158        - Fixed a problem with static linking.
159        - Added pcredemo. [But later removed - see 7 below.]
160        - Fixed dftables problem and added an option.
161        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
162            HAVE_LONG_LONG.
163        - Added readline support for pcretest.
164        - Added an listing of the option settings after cmake has run.
165    
166    4.  A user submitted a patch to Makefile that makes it easy to create
167        "pcre.dll" under mingw when using Configure/Make. I added stuff to
168        Makefile.am that cause it to include this special target, without
169        affecting anything else. Note that the same mingw target plus all
170        the other distribution libraries and programs are now supported
171        when configuring with CMake (see 6 below) instead of with
172        Configure/Make.
173    
174    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
175        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
176        exported in the Windows port". It has not yet been confirmed that the patch
177        solves the problem, but it does no harm.
178    
179    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
180        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
181        with CMake, and also correct the comment about stack recursion.
182    
183    7.  Remove the automatic building of pcredemo from the ./configure system and
184        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
185        of a program that users should build themselves after PCRE is installed, so
186        building it automatically is not really right. What is more, it gave
187        trouble in some build environments.
188    
189    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
190    
191    
192    Version 7.5 10-Jan-08
193  ---------------------  ---------------------
194    
195  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'
196      values in parens when parsing an RE using the C++ wrapper."      values in parens when parsing an RE using the C++ wrapper."
197    
198  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.
199      Characters greater than 255 were excluded from the class instead of being      Characters greater than 255 were excluded from the class instead of being
200      included.      included.
201    
202  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
203      [:^space:].      [:^space:].
204    
205  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
206      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
207      I have changed it.      I have changed it.
208    
209  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
210      first named subpattern) and a construct such as (?&a) would reference the      first named subpattern) and a construct such as (?&a) would reference the
211      first named subpattern whose name started with "a" (in other words, the      first named subpattern whose name started with "a" (in other words, the
212      length check was missing). Both these problems are fixed. "Subpattern name      length check was missing). Both these problems are fixed. "Subpattern name
213      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
214      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
215      was a reference to a non-existent subpattern).      was a reference to a non-existent subpattern).
216    
217  6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;  6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
218      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
219      digits. I have, however, made the messages clearer.      digits. I have, however, made the messages clearer.
220    
221  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
222      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.
223      This is actually not compatible with Perl, which accepts such patterns, but      This is actually not compatible with Perl, which accepts such patterns, but
224      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
225      seems to me that giving a diagnostic is better.      seems to me that giving a diagnostic is better.
226    
227  8.  Change "alphameric" to the more common word "alphanumeric" in comments  8.  Change "alphameric" to the more common word "alphanumeric" in comments
228      and messages.      and messages.
229    
230  9.  Fix two occurrences of "backslash" in comments that should have been  9.  Fix two occurrences of "backslash" in comments that should have been
231      "backspace".      "backspace".
232    
233  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
234      was moved elsewhere).      was moved elsewhere).
235    
236  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
237      which caused it to generate incorrect table entries for sequences of      which caused it to generate incorrect table entries for sequences of
238      characters that have the same character type, but are in different scripts.      characters that have the same character type, but are in different scripts.
239      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
240      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
241      thirteen such cases, affecting characters in the following ranges:      thirteen such cases, affecting characters in the following ranges:
242    
243        U+002b0 - U+002c1        U+002b0 - U+002c1
244        U+0060c - U+0060d        U+0060c - U+0060d
245        U+0061e - U+00612        U+0061e - U+00612
246        U+0064b - U+0065e        U+0064b - U+0065e
247        U+0074d - U+0076d        U+0074d - U+0076d
248        U+01800 - U+01805        U+01800 - U+01805
# Line 65  Version 7.5 12-Nov-07 Line 253  Version 7.5 12-Nov-07
253        U+03260 - U+0327f        U+03260 - U+0327f
254        U+0fb46 - U+0fbb1        U+0fb46 - U+0fbb1
255        U+10450 - U+1049d        U+10450 - U+1049d
256    
257  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
258      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
259      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
260      GNU grep.      GNU grep.
261    
262  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
263      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
264      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
265      non-matching lines.      non-matching lines.
266    
267  14. The pattern (?=something)(?R) was not being diagnosed as a potentially  14. Added --file-offsets and --line-offsets to pcregrep.
268    
269    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
270      infinitely looping recursion. The bug was that positive lookaheads were not      infinitely looping recursion. The bug was that positive lookaheads were not
271      being skipped when checking for a possible empty match (negative lookaheads      being skipped when checking for a possible empty match (negative lookaheads
272      and both kinds of lookbehind were skipped).      and both kinds of lookbehind were skipped).
273    
274  15. Fixed two typos in the Windows-only code in pcregrep.c, and moved the  16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
275      inclusion of <windows.h> to before rather than after the definition of      inclusion of <windows.h> to before rather than after the definition of
276      INVALID_FILE_ATTRIBUTES (patch from David Byron).      INVALID_FILE_ATTRIBUTES (patch from David Byron).
277    
278    17. Specifying a possessive quantifier with a specific limit for a Unicode
279        character property caused pcre_compile() to compile bad code, which led at
280        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
281        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
282        caused the error; without that there was no problem.
283    
284    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
285    
286    19. Added --enable-pcretest-libreadline.
287    
288    20. In pcrecpp.cc, the variable 'count' was incremented twice in
289        RE::GlobalReplace(). As a result, the number of replacements returned was
290        double what it should be. I removed one of the increments, but Craig sent a
291        later patch that removed the other one (the right fix) and added unit tests
292        that check the return values (which was not done before).
293    
294    21. Several CMake things:
295    
296        (1) Arranged that, when cmake is used on Unix, the libraries end up with
297            the names libpcre and libpcreposix, not just pcre and pcreposix.
298    
299        (2) The above change means that pcretest and pcregrep are now correctly
300            linked with the newly-built libraries, not previously installed ones.
301    
302        (3) Added PCRE_SUPPORT_LIBREADLINE, PCRE_SUPPORT_LIBZ, PCRE_SUPPORT_LIBBZ2.
303    
304    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
305        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
306        UTF-8 newline character). The key issue is that the pattern starts .*;
307        this means that the match must be either at the beginning, or after a
308        newline. The bug was in the code for advancing after a failed match and
309        checking that the new position followed a newline. It was not taking
310        account of UTF-8 characters correctly.
311    
312    23. PCRE was behaving differently from Perl in the way it recognized POSIX
313        character classes. PCRE was not treating the sequence [:...:] as a
314        character class unless the ... were all letters. Perl, however, seems to
315        allow any characters between [: and :], though of course it rejects as
316        unknown any "names" that contain non-letters, because all the known class
317        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
318        for example, whereas PCRE did not - it did not recognize a POSIX character
319        class. This seemed a bit dangerous, so the code has been changed to be
320        closer to Perl. The behaviour is not identical to Perl, because PCRE will
321        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
322        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
323        Perl does, and where it didn't before.
324    
325    24. Rewrite so as to remove the single use of %n from pcregrep because in some
326        Windows environments %n is disabled by default.
327    
328    
329  Version 7.4 21-Sep-07  Version 7.4 21-Sep-07
330  ---------------------  ---------------------

Legend:
Removed from v.284  
changed lines
  Added in v.357

  ViewVC Help
Powered by ViewVC 1.1.5