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

Diff of /code/trunk/ChangeLog

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

revision 285 by ph10, Wed Dec 12 17:03:50 2007 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.5 12-Nov-07  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
58        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.
60    
61    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
63        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
66        Lopes.
67    
68    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
71            of files, instead of just to the final components.
72    
73        (2) If there was more than one level of directory, the subdirectories were
74            skipped unless they satisfied the include/exclude conditions. This is
75            inconsistent with GNU grep (and could even be seen as contrary to the
76            pcregrep specification - which I improved to make it absolutely clear).
77            The action now is always to scan all levels of directory, and just
78            apply the include/exclude patterns to regular files.
79    
80    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
81        --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
84        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
85        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
163    ---------------------
164    
165    1.  A character class containing a very large number of characters with
166        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
167        overflow.
168    
169    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
170        HAVE_LONG_LONG is not defined.
171    
172    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
173        bring them up to date and include new features. This patch includes:
174    
175        - Fixed PH's badly added libz and libbz2 support.
176        - Fixed a problem with static linking.
177        - Added pcredemo. [But later removed - see 7 below.]
178        - Fixed dftables problem and added an option.
179        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
180            HAVE_LONG_LONG.
181        - Added readline support for pcretest.
182        - Added an listing of the option settings after cmake has run.
183    
184    4.  A user submitted a patch to Makefile that makes it easy to create
185        "pcre.dll" under mingw when using Configure/Make. I added stuff to
186        Makefile.am that cause it to include this special target, without
187        affecting anything else. Note that the same mingw target plus all
188        the other distribution libraries and programs are now supported
189        when configuring with CMake (see 6 below) instead of with
190        Configure/Make.
191    
192    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
193        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
194        exported in the Windows port". It has not yet been confirmed that the patch
195        solves the problem, but it does no harm.
196    
197    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
198        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
199        with CMake, and also correct the comment about stack recursion.
200    
201    7.  Remove the automatic building of pcredemo from the ./configure system and
202        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
203        of a program that users should build themselves after PCRE is installed, so
204        building it automatically is not really right. What is more, it gave
205        trouble in some build environments.
206    
207    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
208    
209    
210    Version 7.5 10-Jan-08
211  ---------------------  ---------------------
212    
213  1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'  1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
214      values in parens when parsing an RE using the C++ wrapper."      values in parens when parsing an RE using the C++ wrapper."
215    
216  2.  Negative specials like \S did not work in character classes in UTF-8 mode.  2.  Negative specials like \S did not work in character classes in UTF-8 mode.
217      Characters greater than 255 were excluded from the class instead of being      Characters greater than 255 were excluded from the class instead of being
218      included.      included.
219    
220  3.  The same bug as (2) above applied to negated POSIX classes such as  3.  The same bug as (2) above applied to negated POSIX classes such as
221      [:^space:].      [:^space:].
222    
223  4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it  4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
224      defined or documented. It seems to have been a typo for PCRE_STATIC, so      defined or documented. It seems to have been a typo for PCRE_STATIC, so
225      I have changed it.      I have changed it.
226    
227  5.  The construct (?&) was not diagnosed as a syntax error (it referenced the  5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
228      first named subpattern) and a construct such as (?&a) would reference the      first named subpattern) and a construct such as (?&a) would reference the
229      first named subpattern whose name started with "a" (in other words, the      first named subpattern whose name started with "a" (in other words, the
230      length check was missing). Both these problems are fixed. "Subpattern name      length check was missing). Both these problems are fixed. "Subpattern name
231      expected" is now given for (?&) (a zero-length name), and this patch also      expected" is now given for (?&) (a zero-length name), and this patch also
232      makes it give the same error for \k'' (previously it complained that that      makes it give the same error for \k'' (previously it complained that that
233      was a reference to a non-existent subpattern).      was a reference to a non-existent subpattern).
234    
235  6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;  6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
236      this is right because (?- can be followed by option settings as well as by      this is right because (?- can be followed by option settings as well as by
237      digits. I have, however, made the messages clearer.      digits. I have, however, made the messages clearer.
238    
239  7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns  7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
240      than the number used in the conditional) now cause a compile-time error.      than the number used in the conditional) now cause a compile-time error.
241      This is actually not compatible with Perl, which accepts such patterns, but      This is actually not compatible with Perl, which accepts such patterns, but
242      treats the conditional as always being FALSE (as PCRE used to), but it      treats the conditional as always being FALSE (as PCRE used to), but it
243      seems to me that giving a diagnostic is better.      seems to me that giving a diagnostic is better.
244    
245  8.  Change "alphameric" to the more common word "alphanumeric" in comments  8.  Change "alphameric" to the more common word "alphanumeric" in comments
246      and messages.      and messages.
247    
248  9.  Fix two occurrences of "backslash" in comments that should have been  9.  Fix two occurrences of "backslash" in comments that should have been
249      "backspace".      "backspace".
250    
251  10. Remove two redundant lines of code that can never be obeyed (their function  10. Remove two redundant lines of code that can never be obeyed (their function
252      was moved elsewhere).      was moved elsewhere).
253    
254  11. The program that makes PCRE's Unicode character property table had a bug  11. The program that makes PCRE's Unicode character property table had a bug
255      which caused it to generate incorrect table entries for sequences of      which caused it to generate incorrect table entries for sequences of
256      characters that have the same character type, but are in different scripts.      characters that have the same character type, but are in different scripts.
257      It amalgamated them into a single range, with the script of the first of      It amalgamated them into a single range, with the script of the first of
258      them. In other words, some characters were in the wrong script. There were      them. In other words, some characters were in the wrong script. There were
259      thirteen such cases, affecting characters in the following ranges:      thirteen such cases, affecting characters in the following ranges:
260    
261        U+002b0 - U+002c1        U+002b0 - U+002c1
262        U+0060c - U+0060d        U+0060c - U+0060d
263        U+0061e - U+00612        U+0061e - U+00612
264        U+0064b - U+0065e        U+0064b - U+0065e
265        U+0074d - U+0076d        U+0074d - U+0076d
266        U+01800 - U+01805        U+01800 - U+01805
# Line 65  Version 7.5 12-Nov-07 Line 271  Version 7.5 12-Nov-07
271        U+03260 - U+0327f        U+03260 - U+0327f
272        U+0fb46 - U+0fbb1        U+0fb46 - U+0fbb1
273        U+10450 - U+1049d        U+10450 - U+1049d
274    
275  12. The -o option (show only the matching part of a line) for pcregrep was not  12. The -o option (show only the matching part of a line) for pcregrep was not
276      compatible with GNU grep in that, if there was more than one match in a      compatible with GNU grep in that, if there was more than one match in a
277      line, it showed only the first of them. It now behaves in the same way as      line, it showed only the first of them. It now behaves in the same way as
278      GNU grep.      GNU grep.
279    
280  13. If the -o and -v options were combined for pcregrep, it printed a blank  13. If the -o and -v options were combined for pcregrep, it printed a blank
281      line for every non-matching line. GNU grep prints nothing, and pcregrep now      line for every non-matching line. GNU grep prints nothing, and pcregrep now
282      does the same. The return code can be used to tell if there were any      does the same. The return code can be used to tell if there were any
283      non-matching lines.      non-matching lines.
284    
285  14. The pattern (?=something)(?R) was not being diagnosed as a potentially  14. Added --file-offsets and --line-offsets to pcregrep.
286    
287    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
288      infinitely looping recursion. The bug was that positive lookaheads were not      infinitely looping recursion. The bug was that positive lookaheads were not
289      being skipped when checking for a possible empty match (negative lookaheads      being skipped when checking for a possible empty match (negative lookaheads
290      and both kinds of lookbehind were skipped).      and both kinds of lookbehind were skipped).
291    
292  15. Fixed two typos in the Windows-only code in pcregrep.c, and moved the  16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
293      inclusion of <windows.h> to before rather than after the definition of      inclusion of <windows.h> to before rather than after the definition of
294      INVALID_FILE_ATTRIBUTES (patch from David Byron).      INVALID_FILE_ATTRIBUTES (patch from David Byron).
295    
296  16. Specifying a possessive quantifier with a specific limit for a Unicode  17. Specifying a possessive quantifier with a specific limit for a Unicode
297      character property caused pcre_compile() to compile bad code, which led at      character property caused pcre_compile() to compile bad code, which led at
298      runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this      runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
299      are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that      are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
300      caused the error; without that there was no problem.      caused the error; without that there was no problem.
301    
302    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
303    
304    19. Added --enable-pcretest-libreadline.
305    
306    20. In pcrecpp.cc, the variable 'count' was incremented twice in
307        RE::GlobalReplace(). As a result, the number of replacements returned was
308        double what it should be. I removed one of the increments, but Craig sent a
309        later patch that removed the other one (the right fix) and added unit tests
310        that check the return values (which was not done before).
311    
312    21. Several CMake things:
313    
314        (1) Arranged that, when cmake is used on Unix, the libraries end up with
315            the names libpcre and libpcreposix, not just pcre and pcreposix.
316    
317        (2) The above change means that pcretest and pcregrep are now correctly
318            linked with the newly-built libraries, not previously installed ones.
319    
320        (3) Added PCRE_SUPPORT_LIBREADLINE, PCRE_SUPPORT_LIBZ, PCRE_SUPPORT_LIBBZ2.
321    
322    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
323        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
324        UTF-8 newline character). The key issue is that the pattern starts .*;
325        this means that the match must be either at the beginning, or after a
326        newline. The bug was in the code for advancing after a failed match and
327        checking that the new position followed a newline. It was not taking
328        account of UTF-8 characters correctly.
329    
330    23. PCRE was behaving differently from Perl in the way it recognized POSIX
331        character classes. PCRE was not treating the sequence [:...:] as a
332        character class unless the ... were all letters. Perl, however, seems to
333        allow any characters between [: and :], though of course it rejects as
334        unknown any "names" that contain non-letters, because all the known class
335        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
336        for example, whereas PCRE did not - it did not recognize a POSIX character
337        class. This seemed a bit dangerous, so the code has been changed to be
338        closer to Perl. The behaviour is not identical to Perl, because PCRE will
339        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
340        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
341        Perl does, and where it didn't before.
342    
343    24. Rewrite so as to remove the single use of %n from pcregrep because in some
344        Windows environments %n is disabled by default.
345    
346    
347  Version 7.4 21-Sep-07  Version 7.4 21-Sep-07

Legend:
Removed from v.285  
changed lines
  Added in v.360

  ViewVC Help
Powered by ViewVC 1.1.5