ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 181 by ph10, Wed Jun 13 14:55:18 2007 UTC revision 411 by ph10, Fri Apr 10 15:40:21 2009 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 7.2 13-June-07  Version 7.9 10-Apr-09
5    ---------------------
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.
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.
19    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
20        PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
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.
27    5.  In pcregrep, when --colour was used with -o, the list of matching strings
28        was not coloured; this is different to GNU grep, so I have changed it to be
29        the same.
31    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
32        each matching line was coloured. Now it goes on to look for further matches
33        of any of the test patterns, which is the same behaviour as GNU grep.
35    7.  A pattern that could match an empty string could cause pcregrep to loop; it
36        doesn't make sense to accept an empty string match in pcregrep, so I have
37        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
38        seems to be how GNU grep behaves.
40    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
41        start or after a newline", because the conditional assertion was not being
42        correctly handled. The rule now is that both the assertion and what follows
43        in the first alternative must satisfy the test.
45    9.  If auto-callout was enabled in a pattern with a conditional group whose
46        condition was an assertion, PCRE could crash during matching, both with
47        pcre_exec() and pcre_dfa_exec().
49    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
50        used for matching.
52    11. Unicode property support in character classes was not working for
53        characters (bytes) greater than 127 when not in UTF-8 mode.
55    12. Added the -M command line option to pcretest.
57    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
59    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
61    16. Added comments and documentation about mis-use of no_arg in the C++
62        wrapper.
64    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
65        from Martin Jerabek that uses macro names for all relevant character and
66        string constants.
68    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
69        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
70        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
71        these, but not everybody uses configure.
73    19. A conditional group that had only one branch was not being correctly
74        recognized as an item that could match an empty string. This meant that an
75        enclosing group might also not be so recognized, causing infinite looping
76        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
77        with the subject "ab", where knowledge that the repeated group can match
78        nothing is needed in order to break the loop.
80    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
81        exec(), but without supplying a callout function, matching went wrong.
83    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
84        leak if the size of the offset vector was greater than 30. When the vector
85        is smaller, the saved offsets during recursion go onto a local stack
86        vector, but for larger vectors malloc() is used. It was failing to free
87        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
88        error, in fact).
90    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
91        heapframe that is used only when UTF-8 support is enabled. This caused no
92        problem, but was untidy.
94    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
95        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
96        included within another project.
98    24. Steven Van Ingelgem's patches to add more options to the CMake support,
99        slightly modified by me:
101          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
102              not building pcregrep.
104          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
105              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
107    25. Forward references, both numeric and by name, in patterns that made use of
108        duplicate group numbers, could behave incorrectly or give incorrect errors,
109        because when scanning forward to find the reference group, PCRE was not
110        taking into account the duplicate group numbers. A pattern such as
111        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
113    26. Changed a few more instances of "const unsigned char *" to USPTR, making
114        the feature of a custom pointer more persuasive (as requested by a user).
116    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
117        pcretest.c, inside #ifndefs, because it seems they are sometimes already
118        pre-defined.
122    Version 7.8 05-Sep-08
123    ---------------------
125    1.  Replaced UCP searching code with optimized version as implemented for Ad
126        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
127        stage table and inline lookup instead of a function, giving speed ups of 2
128        to 5 times on some simple patterns that I tested. Permission was given to
129        distribute the MultiStage2.py script that generates the tables (it's not in
130        the tarball, but is in the Subversion repository).
132    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
133        scripts.
135    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
136        a group with a zero qualifier. The result of the study could be incorrect,
137        or the function might crash, depending on the pattern.
139    4.  Caseless matching was not working for non-ASCII characters in back
140        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
141        It now works when Unicode Property Support is available.
143    5.  In pcretest, an escape such as \x{de} in the data was always generating
144        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
145        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
146        truncation.
148    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
150    7.  Added two (int) casts to pcregrep when printing the difference of two
151        pointers, in case they are 64-bit values.
153    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
154        test 2 if it fails.
156    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
157        and a #define of that name to empty if it is not externally set. This is to
158        allow users of MSVC to set it if necessary.
160    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
161        the convenience functions in the pcre_get.c source file.
163    11. An option change at the start of a pattern that had top-level alternatives
164        could cause overwriting and/or a crash. This command provoked a crash in
165        some environments:
167          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
169        This potential security problem was recorded as CVE-2008-2371.
171    12. For a pattern where the match had to start at the beginning or immediately
172        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
173        pcre_dfa_exec() could read past the end of the passed subject if there was
174        no match. To help with detecting such bugs (e.g. with valgrind), I modified
175        pcretest so that it places the subject at the end of its malloc-ed buffer.
177    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
178        exec() might read past the end of the data buffer in UTF-8 mode.
180    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
181        the data contained the byte 0x85 as part of a UTF-8 character within its
182        first line. This applied both to normal and DFA matching.
184    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
185        /^[^d]*?$/8 failed to match "abc".
187    16. Added a missing copyright notice to pcrecpp_internal.h.
189    17. Make it more clear in the documentation that values returned from
190        pcre_exec() in ovector are byte offsets, not character counts.
192    18. Tidied a few places to stop certain compilers from issuing warnings.
194    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
195        supplied by Stefan Weber. I made a further small update for 7.8 because
196        there is a change of source arrangements: the pcre_searchfuncs.c module is
197        replaced by pcre_ucd.c.
200    Version 7.7 07-May-08
201    ---------------------
203    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
204        a string to a long long, pretend we don't even have a long long." This is
205        done by checking for the strtoq, strtoll, and _strtoi64 functions.
207    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
208        pre-7.6 versions, which defined a global no_arg variable instead of putting
209        it in the RE class. (See also #8 below.)
211    3.  Remove a line of dead code, identified by coverity and reported by Nuno
212        Lopes.
214    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
216        (1) The include/exclude patterns were being applied to the whole pathnames
217            of files, instead of just to the final components.
219        (2) If there was more than one level of directory, the subdirectories were
220            skipped unless they satisfied the include/exclude conditions. This is
221            inconsistent with GNU grep (and could even be seen as contrary to the
222            pcregrep specification - which I improved to make it absolutely clear).
223            The action now is always to scan all levels of directory, and just
224            apply the include/exclude patterns to regular files.
226    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
227        --exclude_dir in the tests to avoid scanning .svn directories.
229    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
230        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
231        doesn't support NULs in patterns.
233    7.  Added some missing "const"s to declarations of static tables in
234        pcre_compile.c and pcre_dfa_exec.c.
236    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
237        caused by fix #2  above. (Subsequently also a second patch to fix the
238        first patch. And a third patch - this was a messy problem.)
240    9.  Applied Craig's patch to remove the use of push_back().
242    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
243        matching function regexec().
245    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
246        which, however, unlike Perl's \g{...}, are subroutine calls, not back
247        references. PCRE supports relative numbers with this syntax (I don't think
248        Oniguruma does).
250    12. Previously, a group with a zero repeat such as (...){0} was completely
251        omitted from the compiled regex. However, this means that if the group
252        was called as a subroutine from elsewhere in the pattern, things went wrong
253        (an internal error was given). Such groups are now left in the compiled
254        pattern, with a new opcode that causes them to be skipped at execution
255        time.
257    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
258        to the way PCRE behaves:
260        (a) A lone ] character is dis-allowed (Perl treats it as data).
262        (b) A back reference to an unmatched subpattern matches an empty string
263            (Perl fails the current match path).
265        (c) A data ] in a character class must be notated as \] because if the
266            first data character in a class is ], it defines an empty class. (In
267            Perl it is not possible to have an empty class.) The empty class []
268            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
269            The negative empty class [^] matches any one character, independently
270            of the DOTALL setting.
272    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
273        non-existent subpattern following a character class starting with ']' and
274        containing () gave an internal compiling error instead of "reference to
275        non-existent subpattern". Fortunately, when the pattern did exist, the
276        compiled code was correct. (When scanning forwards to check for the
277        existencd of the subpattern, it was treating the data ']' as terminating
278        the class, so got the count wrong. When actually compiling, the reference
279        was subsequently set up correctly.)
281    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
282        it was being rejected as not supported by pcre_dfa_exec(), even though
283        other assertions are supported. I have made pcre_dfa_exec() support
284        (*FAIL).
286    16. The implementation of 13c above involved the invention of a new opcode,
287        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
288        cannot be changed at match time, I realized I could make a small
289        improvement to matching performance by compiling OP_ALLANY instead of
290        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
291        on the OP_ANY path.
293    17. Compiling pcretest on Windows with readline support failed without the
294        following two fixes: (1) Make the unistd.h include conditional on
295        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
297    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
298        ncurses library to be included for pcretest when ReadLine support is
299        requested, but also to allow for it to be overridden. This patch came from
300        Daniel Bergström.
302    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
303        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
304        any errors with the current Unicode tables. Thanks to Peter Kankowski for
305        spotting this.
308    Version 7.6 28-Jan-08
309    ---------------------
311    1.  A character class containing a very large number of characters with
312        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
313        overflow.
315    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
316        HAVE_LONG_LONG is not defined.
318    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
319        bring them up to date and include new features. This patch includes:
321        - Fixed PH's badly added libz and libbz2 support.
322        - Fixed a problem with static linking.
323        - Added pcredemo. [But later removed - see 7 below.]
324        - Fixed dftables problem and added an option.
325        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
326            HAVE_LONG_LONG.
327        - Added readline support for pcretest.
328        - Added an listing of the option settings after cmake has run.
330    4.  A user submitted a patch to Makefile that makes it easy to create
331        "pcre.dll" under mingw when using Configure/Make. I added stuff to
332        Makefile.am that cause it to include this special target, without
333        affecting anything else. Note that the same mingw target plus all
334        the other distribution libraries and programs are now supported
335        when configuring with CMake (see 6 below) instead of with
336        Configure/Make.
338    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
339        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
340        exported in the Windows port". It has not yet been confirmed that the patch
341        solves the problem, but it does no harm.
343    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
344        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
345        with CMake, and also correct the comment about stack recursion.
347    7.  Remove the automatic building of pcredemo from the ./configure system and
348        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
349        of a program that users should build themselves after PCRE is installed, so
350        building it automatically is not really right. What is more, it gave
351        trouble in some build environments.
353    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
356    Version 7.5 10-Jan-08
357    ---------------------
359    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
360        values in parens when parsing an RE using the C++ wrapper."
362    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
363        Characters greater than 255 were excluded from the class instead of being
364        included.
366    3.  The same bug as (2) above applied to negated POSIX classes such as
367        [:^space:].
369    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
370        defined or documented. It seems to have been a typo for PCRE_STATIC, so
371        I have changed it.
373    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
374        first named subpattern) and a construct such as (?&a) would reference the
375        first named subpattern whose name started with "a" (in other words, the
376        length check was missing). Both these problems are fixed. "Subpattern name
377        expected" is now given for (?&) (a zero-length name), and this patch also
378        makes it give the same error for \k'' (previously it complained that that
379        was a reference to a non-existent subpattern).
381    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
382        this is right because (?- can be followed by option settings as well as by
383        digits. I have, however, made the messages clearer.
385    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
386        than the number used in the conditional) now cause a compile-time error.
387        This is actually not compatible with Perl, which accepts such patterns, but
388        treats the conditional as always being FALSE (as PCRE used to), but it
389        seems to me that giving a diagnostic is better.
391    8.  Change "alphameric" to the more common word "alphanumeric" in comments
392        and messages.
394    9.  Fix two occurrences of "backslash" in comments that should have been
395        "backspace".
397    10. Remove two redundant lines of code that can never be obeyed (their function
398        was moved elsewhere).
400    11. The program that makes PCRE's Unicode character property table had a bug
401        which caused it to generate incorrect table entries for sequences of
402        characters that have the same character type, but are in different scripts.
403        It amalgamated them into a single range, with the script of the first of
404        them. In other words, some characters were in the wrong script. There were
405        thirteen such cases, affecting characters in the following ranges:
407          U+002b0 - U+002c1
408          U+0060c - U+0060d
409          U+0061e - U+00612
410          U+0064b - U+0065e
411          U+0074d - U+0076d
412          U+01800 - U+01805
413          U+01d00 - U+01d77
414          U+01d9b - U+01dbf
415          U+0200b - U+0200f
416          U+030fc - U+030fe
417          U+03260 - U+0327f
418          U+0fb46 - U+0fbb1
419          U+10450 - U+1049d
421    12. The -o option (show only the matching part of a line) for pcregrep was not
422        compatible with GNU grep in that, if there was more than one match in a
423        line, it showed only the first of them. It now behaves in the same way as
424        GNU grep.
426    13. If the -o and -v options were combined for pcregrep, it printed a blank
427        line for every non-matching line. GNU grep prints nothing, and pcregrep now
428        does the same. The return code can be used to tell if there were any
429        non-matching lines.
431    14. Added --file-offsets and --line-offsets to pcregrep.
433    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
434        infinitely looping recursion. The bug was that positive lookaheads were not
435        being skipped when checking for a possible empty match (negative lookaheads
436        and both kinds of lookbehind were skipped).
438    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
439        inclusion of <windows.h> to before rather than after the definition of
440        INVALID_FILE_ATTRIBUTES (patch from David Byron).
442    17. Specifying a possessive quantifier with a specific limit for a Unicode
443        character property caused pcre_compile() to compile bad code, which led at
444        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
445        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
446        caused the error; without that there was no problem.
448    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
450    19. Added --enable-pcretest-libreadline.
452    20. In pcrecpp.cc, the variable 'count' was incremented twice in
453        RE::GlobalReplace(). As a result, the number of replacements returned was
454        double what it should be. I removed one of the increments, but Craig sent a
455        later patch that removed the other one (the right fix) and added unit tests
456        that check the return values (which was not done before).
458    21. Several CMake things:
460        (1) Arranged that, when cmake is used on Unix, the libraries end up with
461            the names libpcre and libpcreposix, not just pcre and pcreposix.
463        (2) The above change means that pcretest and pcregrep are now correctly
464            linked with the newly-built libraries, not previously installed ones.
468    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
469        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
470        UTF-8 newline character). The key issue is that the pattern starts .*;
471        this means that the match must be either at the beginning, or after a
472        newline. The bug was in the code for advancing after a failed match and
473        checking that the new position followed a newline. It was not taking
474        account of UTF-8 characters correctly.
476    23. PCRE was behaving differently from Perl in the way it recognized POSIX
477        character classes. PCRE was not treating the sequence [:...:] as a
478        character class unless the ... were all letters. Perl, however, seems to
479        allow any characters between [: and :], though of course it rejects as
480        unknown any "names" that contain non-letters, because all the known class
481        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
482        for example, whereas PCRE did not - it did not recognize a POSIX character
483        class. This seemed a bit dangerous, so the code has been changed to be
484        closer to Perl. The behaviour is not identical to Perl, because PCRE will
485        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
486        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
487        Perl does, and where it didn't before.
489    24. Rewrite so as to remove the single use of %n from pcregrep because in some
490        Windows environments %n is disabled by default.
493    Version 7.4 21-Sep-07
494    ---------------------
496    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
497        means that a class such as [\s] counted as "explicit reference to CR or
498        LF". That isn't really right - the whole point of the change was to try to
499        help when there was an actual mention of one of the two characters. So now
500        the change happens only if \r or \n (or a literal CR or LF) character is
501        encountered.
503    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
504        of both had grown to the point where there were only 3 bits left.
505        Fortunately, there was spare space in the data structure, and so I have
506        moved the internal flags into a new 16-bit field to free up more option
507        bits.
509    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
510        but did not set the internal JCHANGED flag - either of these is enough to
511        control the way the "get" function works - but the PCRE_INFO_JCHANGED
512        facility is supposed to tell if (?J) was ever used, so now (?J) at the
513        start sets both bits.
515    4.  Added options (at build time, compile time, exec time) to change \R from
516        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
518    5.  doc/pcresyntax.html was missing from the distribution.
520    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
521        compatibility, even though it is no longer used.
523    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
524        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
525        windows.h file is present (where different names are used). [This was
526        reversed later after testing - see 16 below.]
528    8.  Changed all #include <config.h> to #include "config.h". There were also
529        some further <pcre.h> cases that I changed to "pcre.h".
531    9.  When pcregrep was used with the --colour option, it missed the line ending
532        sequence off the lines that it output.
534    10. It was pointed out to me that arrays of string pointers cause lots of
535        relocations when a shared library is dynamically loaded. A technique of
536        using a single long string with a table of offsets can drastically reduce
537        these. I have refactored PCRE in four places to do this. The result is
538        dramatic:
540          Originally:                          290
541          After changing UCP table:            187
542          After changing error message table:   43
543          After changing table of "verbs"       36
544          After changing table of Posix names   22
546        Thanks to the folks working on Gregex for glib for this insight.
548    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
549        unicode-properties was also set.
551    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
553    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
554        checked only for CRLF.
556    14. Added casts to pcretest.c to avoid compiler warnings.
558    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
560    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
561        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
562        entirely. This removes changes made in 7 above.
564    17. The CMake files have been updated, and there is now more information about
565        building with CMake in the NON-UNIX-USE document.
568    Version 7.3 28-Aug-07
569    ---------------------
571     1. In the rejigging of the build system that eventually resulted in 7.1, the
572        line "#include <pcre.h>" was included in pcre_internal.h. The use of angle
573        brackets there is not right, since it causes compilers to look for an
574        installed pcre.h, not the version that is in the source that is being
575        compiled (which of course may be different). I have changed it back to:
577          #include "pcre.h"
579        I have a vague recollection that the change was concerned with compiling in
580        different directories, but in the new build system, that is taken care of
581        by the VPATH setting the Makefile.
583     2. The pattern .*$ when run in not-DOTALL UTF-8 mode with newline=any failed
584        when the subject happened to end in the byte 0x85 (e.g. if the last
585        character was \x{1ec5}). *Character* 0x85 is one of the "any" newline
586        characters but of course it shouldn't be taken as a newline when it is part
587        of another character. The bug was that, for an unlimited repeat of . in
588        not-DOTALL UTF-8 mode, PCRE was advancing by bytes rather than by
589        characters when looking for a newline.
591     3. A small performance improvement in the DOTALL UTF-8 mode .* case.
593     4. Debugging: adjusted the names of opcodes for different kinds of parentheses
594        in debug output.
596     5. Arrange to use "%I64d" instead of "%lld" and "%I64u" instead of "%llu" for
597        long printing in the pcrecpp unittest when running under MinGW.
599     6. ESC_K was left out of the EBCDIC table.
601     7. Change 7.0/38 introduced a new limit on the number of nested non-capturing
602        parentheses; I made it 1000, which seemed large enough. Unfortunately, the
603        limit also applies to "virtual nesting" when a pattern is recursive, and in
604        this case 1000 isn't so big. I have been able to remove this limit at the
605        expense of backing off one optimization in certain circumstances. Normally,
606        when pcre_exec() would call its internal match() function recursively and
607        immediately return the result unconditionally, it uses a "tail recursion"
608        feature to save stack. However, when a subpattern that can match an empty
609        string has an unlimited repetition quantifier, it no longer makes this
610        optimization. That gives it a stack frame in which to save the data for
611        checking that an empty string has been matched. Previously this was taken
612        from the 1000-entry workspace that had been reserved. So now there is no
613        explicit limit, but more stack is used.
615     8. Applied Daniel's patches to solve problems with the import/export magic
616        syntax that is required for Windows, and which was going wrong for the
617        pcreposix and pcrecpp parts of the library. These were overlooked when this
618        problem was solved for the main library.
620     9. There were some crude static tests to avoid integer overflow when computing
621        the size of patterns that contain repeated groups with explicit upper
622        limits. As the maximum quantifier is 65535, the maximum group length was
623        set at 30,000 so that the product of these two numbers did not overflow a
624        32-bit integer. However, it turns out that people want to use groups that
625        are longer than 30,000 bytes (though not repeat them that many times).
626        Change 7.0/17 (the refactoring of the way the pattern size is computed) has
627        made it possible to implement the integer overflow checks in a much more
628        dynamic way, which I have now done. The artificial limitation on group
629        length has been removed - we now have only the limit on the total length of
630        the compiled pattern, which depends on the LINK_SIZE setting.
632    10. Fixed a bug in the documentation for get/copy named substring when
633        duplicate names are permitted. If none of the named substrings are set, the
634        functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an
635        empty string.
637    11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E
638        instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,
639        because the ] is interpreted as the first data character and the
640        terminating ] is not found. PCRE has been made compatible with Perl in this
641        regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could
642        cause memory overwriting.
644    10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty
645        string has been matched (to stop an infinite loop). It was not recognizing
646        a conditional subpattern that could match an empty string if that
647        subpattern was within another subpattern. For example, it looped when
648        trying to match  (((?(1)X|))*)  but it was OK with  ((?(1)X|)*)  where the
649        condition was not nested. This bug has been fixed.
651    12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack
652        past the start of the subject in the presence of bytes with the top bit
653        set, for example "\x8aBCD".
655    13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
656        (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
658    14. Optimized (?!) to (*FAIL).
660    15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
661        This restricts code points to be within the range 0 to 0x10FFFF, excluding
662        the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
663        full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
664        does: it's just the validity check that is more restrictive.
666    16. Inserted checks for integer overflows during escape sequence (backslash)
667        processing, and also fixed erroneous offset values for syntax errors during
668        backslash processing.
670    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
671        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
673    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
674        caused an overrun.
676    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
677        something other than just ASCII characters) inside a group that had an
678        unlimited repeat caused a loop at compile time (while checking to see
679        whether the group could match an empty string).
681    20. Debugging a pattern containing \p or \P could cause a crash. For example,
682        [\P{Any}] did so. (Error in the code for printing property names.)
684    21. An orphan \E inside a character class could cause a crash.
686    22. A repeated capturing bracket such as (A)? could cause a wild memory
687        reference during compilation.
689    23. There are several functions in pcre_compile() that scan along a compiled
690        expression for various reasons (e.g. to see if it's fixed length for look
691        behind). There were bugs in these functions when a repeated \p or \P was
692        present in the pattern. These operators have additional parameters compared
693        with \d, etc, and these were not being taken into account when moving along
694        the compiled data. Specifically:
696        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
697            length.
699        (b) An item such as \pL+ within a repeated group could cause crashes or
700            loops.
702        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
703            "reference to non-existent subpattern" error.
705        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
707    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
708        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
710    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
712    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
713        character were causing crashes (broken optimization).
715    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
716        \p or \P) caused a compile-time loop.
718    28. More problems have arisen in unanchored patterns when CRLF is a valid line
719        break. For example, the unstudied pattern [\r\n]A does not match the string
720        "\r\nA" because change 7.0/46 below moves the current point on by two
721        characters after failing to match at the start. However, the pattern \nA
722        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
723        the same is true. There doesn't seem any very clean way out of this, but
724        what I have chosen to do makes the common cases work: PCRE now takes note
725        of whether there can be an explicit match for \r or \n anywhere in the
726        pattern, and if so, 7.0/46 no longer applies. As part of this change,
727        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
728        pattern has explicit CR or LF references.
730    29. Added (*CR) etc for changing newline setting at start of pattern.
733    Version 7.2 19-Jun-07
734  ---------------------  ---------------------
736   1. If the fr_FR locale cannot be found for test 3, try the "french" locale,   1. If the fr_FR locale cannot be found for test 3, try the "french" locale,
# Line 40  Version 7.2 13-June-07 Line 769  Version 7.2 13-June-07
770      (f) \g{name} is another synonym - part of Perl 5.10's unification of      (f) \g{name} is another synonym - part of Perl 5.10's unification of
771          reference syntax.          reference syntax.
773      (g) (?| introduces a group in which the numbering of parentheses in each      (g) (?| introduces a group in which the numbering of parentheses in each
774          alternative starts with the same number.          alternative starts with the same number.
776      (h) \h, \H, \v, and \V match horizontal and vertical whitespace.      (h) \h, \H, \v, and \V match horizontal and vertical whitespace.
778   7. Added two new calls to pcre_fullinfo(): PCRE_INFO_OKPARTIAL and   7. Added two new calls to pcre_fullinfo(): PCRE_INFO_OKPARTIAL and
# Line 59  Version 7.2 13-June-07 Line 788  Version 7.2 13-June-07
788      bit of new cunning has reduced the workspace needed for groups with      bit of new cunning has reduced the workspace needed for groups with
789      alternatives. The 1000-alternative test pattern now uses 12 bytes of      alternatives. The 1000-alternative test pattern now uses 12 bytes of
790      workspace instead of running out of the 4096 that are available.      workspace instead of running out of the 4096 that are available.
792  10. Inserted some missing (unsigned int) casts to get rid of compiler warnings.  10. Inserted some missing (unsigned int) casts to get rid of compiler warnings.
794  11. Applied patch from Google to remove an optimization that didn't quite work.  11. Applied patch from Google to remove an optimization that didn't quite work.
795      The report of the bug said:      The report of the bug said:
797        pcrecpp::RE("a*").FullMatch("aaa") matches, while        pcrecpp::RE("a*").FullMatch("aaa") matches, while
798        pcrecpp::RE("a*?").FullMatch("aaa") does not, and        pcrecpp::RE("a*?").FullMatch("aaa") does not, and
799        pcrecpp::RE("a*?\\z").FullMatch("aaa") does again.        pcrecpp::RE("a*?\\z").FullMatch("aaa") does again.
801    12. If \p or \P was used in non-UTF-8 mode on a character greater than 127
802        it matched the wrong number of bytes.
805  Version 7.1 24-Apr-07  Version 7.1 24-Apr-07

Removed from v.181  
changed lines
  Added in v.411

  ViewVC Help
Powered by ViewVC 1.1.5