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

Diff of /code/trunk/ChangeLog

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

revision 325 by ph10, Sat Mar 8 17:13:02 2008 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.7 05-Mar-08  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  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      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.      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  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      pre-7.6 versions, which defined a global no_arg variable instead of putting
27      it in the RE class.      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  3.  Remove a line of dead code, identified by coverity and reported by Nuno
30      Lopes.      Lopes.
31    
32  4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:  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      (1) The include/exclude patterns were being applied to the whole pathnames
35          of files, instead of just to the final components.          of files, instead of just to the final components.
36    
37      (2) If there was more than one level of directory, the subdirectories were      (2) If there was more than one level of directory, the subdirectories were
38          skipped unless they satisfied the include/exclude conditions. This is          skipped unless they satisfied the include/exclude conditions. This is
39          inconsistent with GNU grep (and could even be seen as contrary to the          inconsistent with GNU grep (and could even be seen as contrary to the
40          pcregrep specification - which I improved to make it absolutely clear).          pcregrep specification - which I improved to make it absolutely clear).
41          The action now is always to scan all levels of directory, and just          The action now is always to scan all levels of directory, and just
42          apply the include/exclude patterns to regular files.          apply the include/exclude patterns to regular files.
43    
44  5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used  5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
45      --exclude_dir in the tests to avoid scanning .svn directories.      --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  Version 7.6 28-Jan-08

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

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12