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

Diff of /code/trunk/ChangeLog

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

revision 326 by ph10, Sat Mar 8 17:24:02 2008 UTC revision 360 by ph10, Wed Jul 9 20:00:28 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    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    5.  In pcretest, an escape such as \x{de} in the data was always generating
26        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
27        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
28        truncation.
29    
30    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
31    
32    7.  Added two (int) casts to pcregrep when printing the difference of two
33        pointers, in case they are 64-bit values.
34    
35    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
36        test 2 if it fails.
37    
38    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
39        and a #define of that name to empty if it is not externally set. This is to
40        allow users of MSVC to set it if necessary.
41    
42    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
43        the convenience functions in the pcre_get.c source file.
44    
45    11. An option change at the start of a pattern that had top-level alternatives
46        could cause overwriting and/or a crash. This command provoked a crash in
47        some environments:
48    
49          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
50    
51        This potential security problem was recorded as CVE-2008-2371.
52    
53    
54    Version 7.7 07-May-08
55  ---------------------  ---------------------
56    
57  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
58      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
59      done by checking for the strtoq, strtoll, and _strtoi64 functions.      done by checking for the strtoq, strtoll, and _strtoi64 functions.
60    
61  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
62      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
63      it in the RE class.      it in the RE class. (See also #8 below.)
64    
65  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
66      Lopes.      Lopes.
67    
68  4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:  4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
69    
70      (1) The include/exclude patterns were being applied to the whole pathnames      (1) The include/exclude patterns were being applied to the whole pathnames
71          of files, instead of just to the final components.          of files, instead of just to the final components.
72    
73      (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
74          skipped unless they satisfied the include/exclude conditions. This is          skipped unless they satisfied the include/exclude conditions. This is
75          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
76          pcregrep specification - which I improved to make it absolutely clear).          pcregrep specification - which I improved to make it absolutely clear).
77          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
78          apply the include/exclude patterns to regular files.          apply the include/exclude patterns to regular files.
79    
80  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
81      --exclude_dir in the tests to avoid scanning .svn directories.      --exclude_dir in the tests to avoid scanning .svn directories.
82    
83  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
84      NUL character as backslash + 0 rather than backslash + NUL, because PCRE      NUL character as backslash + 0 rather than backslash + NUL, because PCRE
85      doesn't support NULs in patterns.      doesn't support NULs in patterns.
86    
87    7.  Added some missing "const"s to declarations of static tables in
88        pcre_compile.c and pcre_dfa_exec.c.
89    
90    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
91        caused by fix #2  above. (Subsequently also a second patch to fix the
92        first patch. And a third patch - this was a messy problem.)
93    
94    9.  Applied Craig's patch to remove the use of push_back().
95    
96    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
97        matching function regexec().
98    
99    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
100        which, however, unlike Perl's \g{...}, are subroutine calls, not back
101        references. PCRE supports relative numbers with this syntax (I don't think
102        Oniguruma does).
103    
104    12. Previously, a group with a zero repeat such as (...){0} was completely
105        omitted from the compiled regex. However, this means that if the group
106        was called as a subroutine from elsewhere in the pattern, things went wrong
107        (an internal error was given). Such groups are now left in the compiled
108        pattern, with a new opcode that causes them to be skipped at execution
109        time.
110    
111    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
112        to the way PCRE behaves:
113    
114        (a) A lone ] character is dis-allowed (Perl treats it as data).
115    
116        (b) A back reference to an unmatched subpattern matches an empty string
117            (Perl fails the current match path).
118    
119        (c) A data ] in a character class must be notated as \] because if the
120            first data character in a class is ], it defines an empty class. (In
121            Perl it is not possible to have an empty class.) The empty class []
122            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
123            The negative empty class [^] matches any one character, independently
124            of the DOTALL setting.
125    
126    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
127        non-existent subpattern following a character class starting with ']' and
128        containing () gave an internal compiling error instead of "reference to
129        non-existent subpattern". Fortunately, when the pattern did exist, the
130        compiled code was correct. (When scanning forwards to check for the
131        existencd of the subpattern, it was treating the data ']' as terminating
132        the class, so got the count wrong. When actually compiling, the reference
133        was subsequently set up correctly.)
134    
135    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
136        it was being rejected as not supported by pcre_dfa_exec(), even though
137        other assertions are supported. I have made pcre_dfa_exec() support
138        (*FAIL).
139    
140    16. The implementation of 13c above involved the invention of a new opcode,
141        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
142        cannot be changed at match time, I realized I could make a small
143        improvement to matching performance by compiling OP_ALLANY instead of
144        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
145        on the OP_ANY path.
146    
147    17. Compiling pcretest on Windows with readline support failed without the
148        following two fixes: (1) Make the unistd.h include conditional on
149        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
150    
151    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
152        ncurses library to be included for pcretest when ReadLine support is
153        requested, but also to allow for it to be overridden. This patch came from
154        Daniel Bergström.
155    
156    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
157        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
158        any errors with the current Unicode tables. Thanks to Peter Kankowski for
159        spotting this.
160    
161    
162  Version 7.6 28-Jan-08  Version 7.6 28-Jan-08
163  ---------------------  ---------------------
Legend:
Removed from v.326  
changed lines
  Added in v.360
  ViewVC Help
Powered by ViewVC 1.1.5