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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.277  
changed lines
  Added in v.354

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12