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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.340  
changed lines
  Added in v.347

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12