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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.288  
changed lines
  Added in v.351

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12