/[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 376 by ph10, Sun Mar 1 12:00:59 2009 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 7.7 05-Mar-08  Version 7.9 xx-xxx-09
5    ---------------------
6    
7    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
8        (pcretest), all targets were linked against these libraries. This included
9        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
10        libraries. This caused unwanted dependencies to be created. This problem
11        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
12        pcretest is linked with readline.
13    
14    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
15        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
16        moved outside it again, because FALSE and TRUE are already defined in AIX,
17        but BOOL is not.
18    
19    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
20        PCRE_MATCH_LIMIT_RETURSION values as ints, when they should be long ints.
21    
22    4.  The pcregrep documentation said spaces were inserted as well as colons (or
23        hyphens) following file names and line numbers when outputting matching
24        lines. This is not true; no spaces are inserted. I have also clarified the
25        wording for the --colour (or --color) option.
26    
27    
28    Version 7.8 05-Sep-08
29    ---------------------
30    
31    1.  Replaced UCP searching code with optimized version as implemented for Ad
32        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
33        stage table and inline lookup instead of a function, giving speed ups of 2
34        to 5 times on some simple patterns that I tested. Permission was given to
35        distribute the MultiStage2.py script that generates the tables (it's not in
36        the tarball, but is in the Subversion repository).
37    
38    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
39        scripts.
40    
41    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
42        a group with a zero qualifier. The result of the study could be incorrect,
43        or the function might crash, depending on the pattern.
44    
45    4.  Caseless matching was not working for non-ASCII characters in back
46        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
47        It now works when Unicode Property Support is available.
48    
49    5.  In pcretest, an escape such as \x{de} in the data was always generating
50        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
51        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
52        truncation.
53    
54    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
55    
56    7.  Added two (int) casts to pcregrep when printing the difference of two
57        pointers, in case they are 64-bit values.
58    
59    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
60        test 2 if it fails.
61    
62    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
63        and a #define of that name to empty if it is not externally set. This is to
64        allow users of MSVC to set it if necessary.
65    
66    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
67        the convenience functions in the pcre_get.c source file.
68    
69    11. An option change at the start of a pattern that had top-level alternatives
70        could cause overwriting and/or a crash. This command provoked a crash in
71        some environments:
72    
73          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
74    
75        This potential security problem was recorded as CVE-2008-2371.
76    
77    12. For a pattern where the match had to start at the beginning or immediately
78        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
79        pcre_dfa_exec() could read past the end of the passed subject if there was
80        no match. To help with detecting such bugs (e.g. with valgrind), I modified
81        pcretest so that it places the subject at the end of its malloc-ed buffer.
82    
83    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
84        exec() might read past the end of the data buffer in UTF-8 mode.
85    
86    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
87        the data contained the byte 0x85 as part of a UTF-8 character within its
88        first line. This applied both to normal and DFA matching.
89    
90    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
91        /^[^d]*?$/8 failed to match "abc".
92    
93    16. Added a missing copyright notice to pcrecpp_internal.h.
94    
95    17. Make it more clear in the documentation that values returned from
96        pcre_exec() in ovector are byte offsets, not character counts.
97    
98    18. Tidied a few places to stop certain compilers from issuing warnings.
99    
100    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
101        supplied by Stefan Weber. I made a further small update for 7.8 because
102        there is a change of source arrangements: the pcre_searchfuncs.c module is
103        replaced by pcre_ucd.c.
104    
105    
106    Version 7.7 07-May-08
107  ---------------------  ---------------------
108    
109  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
110      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
111      done by checking for the strtoq, strtoll, and _strtoi64 functions.      done by checking for the strtoq, strtoll, and _strtoi64 functions.
112    
113  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
114      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
115      it in the RE class.      it in the RE class. (See also #8 below.)
116    
117  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
118      Lopes.      Lopes.
119    
120  4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:  4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
121    
122      (1) The include/exclude patterns were being applied to the whole pathnames      (1) The include/exclude patterns were being applied to the whole pathnames
123          of files, instead of just to the final components.          of files, instead of just to the final components.
124    
125      (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
126          skipped unless they satisfied the include/exclude conditions. This is          skipped unless they satisfied the include/exclude conditions. This is
127          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
128          pcregrep specification - which I improved to make it absolutely clear).          pcregrep specification - which I improved to make it absolutely clear).
129          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
130          apply the include/exclude patterns to regular files.          apply the include/exclude patterns to regular files.
131    
132  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
133      --exclude_dir in the tests to avoid scanning .svn directories.      --exclude_dir in the tests to avoid scanning .svn directories.
134    
135  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
136      NUL character as backslash + 0 rather than backslash + NUL, because PCRE      NUL character as backslash + 0 rather than backslash + NUL, because PCRE
137      doesn't support NULs in patterns.      doesn't support NULs in patterns.
138    
139    7.  Added some missing "const"s to declarations of static tables in
140        pcre_compile.c and pcre_dfa_exec.c.
141    
142    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
143        caused by fix #2  above. (Subsequently also a second patch to fix the
144        first patch. And a third patch - this was a messy problem.)
145    
146    9.  Applied Craig's patch to remove the use of push_back().
147    
148    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
149        matching function regexec().
150    
151    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
152        which, however, unlike Perl's \g{...}, are subroutine calls, not back
153        references. PCRE supports relative numbers with this syntax (I don't think
154        Oniguruma does).
155    
156    12. Previously, a group with a zero repeat such as (...){0} was completely
157        omitted from the compiled regex. However, this means that if the group
158        was called as a subroutine from elsewhere in the pattern, things went wrong
159        (an internal error was given). Such groups are now left in the compiled
160        pattern, with a new opcode that causes them to be skipped at execution
161        time.
162    
163    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
164        to the way PCRE behaves:
165    
166        (a) A lone ] character is dis-allowed (Perl treats it as data).
167    
168        (b) A back reference to an unmatched subpattern matches an empty string
169            (Perl fails the current match path).
170    
171        (c) A data ] in a character class must be notated as \] because if the
172            first data character in a class is ], it defines an empty class. (In
173            Perl it is not possible to have an empty class.) The empty class []
174            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
175            The negative empty class [^] matches any one character, independently
176            of the DOTALL setting.
177    
178    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
179        non-existent subpattern following a character class starting with ']' and
180        containing () gave an internal compiling error instead of "reference to
181        non-existent subpattern". Fortunately, when the pattern did exist, the
182        compiled code was correct. (When scanning forwards to check for the
183        existencd of the subpattern, it was treating the data ']' as terminating
184        the class, so got the count wrong. When actually compiling, the reference
185        was subsequently set up correctly.)
186    
187    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
188        it was being rejected as not supported by pcre_dfa_exec(), even though
189        other assertions are supported. I have made pcre_dfa_exec() support
190        (*FAIL).
191    
192    16. The implementation of 13c above involved the invention of a new opcode,
193        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
194        cannot be changed at match time, I realized I could make a small
195        improvement to matching performance by compiling OP_ALLANY instead of
196        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
197        on the OP_ANY path.
198    
199    17. Compiling pcretest on Windows with readline support failed without the
200        following two fixes: (1) Make the unistd.h include conditional on
201        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
202    
203    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
204        ncurses library to be included for pcretest when ReadLine support is
205        requested, but also to allow for it to be overridden. This patch came from
206        Daniel Bergström.
207    
208    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
209        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
210        any errors with the current Unicode tables. Thanks to Peter Kankowski for
211        spotting this.
212    
213    
214  Version 7.6 28-Jan-08  Version 7.6 28-Jan-08
215  ---------------------  ---------------------

Legend:
Removed from v.326  
changed lines
  Added in v.376

  ViewVC Help
Powered by ViewVC 1.1.5