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

Diff of /code/trunk/ChangeLog

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

revision 341 by ph10, Sat Apr 19 16:41:04 2008 UTC revision 353 by ph10, Mon Jul 7 15:44:24 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    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    
22    Version 7.7 07-May-08
23  ---------------------  ---------------------
24    
25  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
26      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
27      done by checking for the strtoq, strtoll, and _strtoi64 functions.      done by checking for the strtoq, strtoll, and _strtoi64 functions.
28    
29  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
30      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
31      it in the RE class. (See also #8 below.)      it in the RE class. (See also #8 below.)
32    
33  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
34      Lopes.      Lopes.
35    
36  4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:  4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
37    
38      (1) The include/exclude patterns were being applied to the whole pathnames      (1) The include/exclude patterns were being applied to the whole pathnames
39          of files, instead of just to the final components.          of files, instead of just to the final components.
40    
41      (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
42          skipped unless they satisfied the include/exclude conditions. This is          skipped unless they satisfied the include/exclude conditions. This is
43          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
44          pcregrep specification - which I improved to make it absolutely clear).          pcregrep specification - which I improved to make it absolutely clear).
45          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
46          apply the include/exclude patterns to regular files.          apply the include/exclude patterns to regular files.
47    
48  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
49      --exclude_dir in the tests to avoid scanning .svn directories.      --exclude_dir in the tests to avoid scanning .svn directories.
50    
51  6.  Applied Craig's patch to the QuoteMeta function so that it escapes the  6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
52      NUL character as backslash + 0 rather than backslash + NUL, because PCRE      NUL character as backslash + 0 rather than backslash + NUL, because PCRE
53      doesn't support NULs in patterns.      doesn't support NULs in patterns.
54    
55  7.  Added some missing "const"s to declarations of static tables in  7.  Added some missing "const"s to declarations of static tables in
56      pcre_compile.c and pcre_dfa_exec.c.      pcre_compile.c and pcre_dfa_exec.c.
57    
58  8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was  8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
59      caused by fix #2  above. (Subsequently also a second patch to fix the      caused by fix #2  above. (Subsequently also a second patch to fix the
60      first patch. And a third patch - this was a messy problem.)      first patch. And a third patch - this was a messy problem.)
61    
62  9.  Applied Craig's patch to remove the use of push_back().  9.  Applied Craig's patch to remove the use of push_back().
63    
64  10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX  10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
65      matching function regexec().      matching function regexec().
66    
67  11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',  11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
68      which, however, unlike Perl's \g{...}, are subroutine calls, not back      which, however, unlike Perl's \g{...}, are subroutine calls, not back
69      references. PCRE supports relative numbers with this syntax (I don't think      references. PCRE supports relative numbers with this syntax (I don't think
70      Oniguruma does).      Oniguruma does).
71    
72  12. Previously, a group with a zero repeat such as (...){0} was completely  12. Previously, a group with a zero repeat such as (...){0} was completely
73      omitted from the compiled regex. However, this means that if the group      omitted from the compiled regex. However, this means that if the group
74      was called as a subroutine from elsewhere in the pattern, things went wrong      was called as a subroutine from elsewhere in the pattern, things went wrong
75      (an internal error was given). Such groups are now left in the compiled      (an internal error was given). Such groups are now left in the compiled
76      pattern, with a new opcode that causes them to be skipped at execution      pattern, with a new opcode that causes them to be skipped at execution
77      time.      time.
78    
79  13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes  13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
80      to the way PCRE behaves:      to the way PCRE behaves:
81    
82      (a) A lone ] character is dis-allowed (Perl treats it as data).      (a) A lone ] character is dis-allowed (Perl treats it as data).
83    
84      (b) A back reference to an unmatched subpattern matches an empty string      (b) A back reference to an unmatched subpattern matches an empty string
85          (Perl fails the current match path).          (Perl fails the current match path).
86    
87      (c) A data ] in a character class must be notated as \] because if the      (c) A data ] in a character class must be notated as \] because if the
88          first data character in a class is ], it defines an empty class. (In          first data character in a class is ], it defines an empty class. (In
89          Perl it is not possible to have an empty class.) The empty class []          Perl it is not possible to have an empty class.) The empty class []
90          never matches; it forces failure and is equivalent to (*FAIL) or (?!).          never matches; it forces failure and is equivalent to (*FAIL) or (?!).
91          The negative empty class [^] matches any one character, independently          The negative empty class [^] matches any one character, independently
92          of the DOTALL setting.          of the DOTALL setting.
93    
94  14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a  14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
95      non-existent subpattern following a character class starting with ']' and      non-existent subpattern following a character class starting with ']' and
96      containing () gave an internal compiling error instead of "reference to      containing () gave an internal compiling error instead of "reference to
97      non-existent subpattern". Fortunately, when the pattern did exist, the      non-existent subpattern". Fortunately, when the pattern did exist, the
98      compiled code was correct. (When scanning forwards to check for the      compiled code was correct. (When scanning forwards to check for the
99      existencd of the subpattern, it was treating the data ']' as terminating      existencd of the subpattern, it was treating the data ']' as terminating
100      the class, so got the count wrong. When actually compiling, the reference      the class, so got the count wrong. When actually compiling, the reference
101      was subsequently set up correctly.)      was subsequently set up correctly.)
102    
103  15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;  15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
104      it was being rejected as not supported by pcre_dfa_exec(), even though      it was being rejected as not supported by pcre_dfa_exec(), even though
105      other assertions are supported. I have made pcre_dfa_exec() support      other assertions are supported. I have made pcre_dfa_exec() support
106      (*FAIL).      (*FAIL).
107    
108    16. The implementation of 13c above involved the invention of a new opcode,
109        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
110        cannot be changed at match time, I realized I could make a small
111        improvement to matching performance by compiling OP_ALLANY instead of
112        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
113        on the OP_ANY path.
114    
115    17. Compiling pcretest on Windows with readline support failed without the
116        following two fixes: (1) Make the unistd.h include conditional on
117        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
118    
119    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
120        ncurses library to be included for pcretest when ReadLine support is
121        requested, but also to allow for it to be overridden. This patch came from
122        Daniel Bergström.
123    
124    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
125        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
126        any errors with the current Unicode tables. Thanks to Peter Kankowski for
127        spotting this.
128    
129    
130  Version 7.6 28-Jan-08  Version 7.6 28-Jan-08

Legend:
Removed from v.341  
changed lines
  Added in v.353

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12