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 412 by ph10, Sat Apr 11 10:34:37 2009 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 7.2 13-June-07  Version 7.9 11-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.
120    28. Added support for (*UTF8) at the start of a pattern.
124    Version 7.8 05-Sep-08
125    ---------------------
127    1.  Replaced UCP searching code with optimized version as implemented for Ad
128        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
129        stage table and inline lookup instead of a function, giving speed ups of 2
130        to 5 times on some simple patterns that I tested. Permission was given to
131        distribute the MultiStage2.py script that generates the tables (it's not in
132        the tarball, but is in the Subversion repository).
134    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
135        scripts.
137    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
138        a group with a zero qualifier. The result of the study could be incorrect,
139        or the function might crash, depending on the pattern.
141    4.  Caseless matching was not working for non-ASCII characters in back
142        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
143        It now works when Unicode Property Support is available.
145    5.  In pcretest, an escape such as \x{de} in the data was always generating
146        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
147        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
148        truncation.
150    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
152    7.  Added two (int) casts to pcregrep when printing the difference of two
153        pointers, in case they are 64-bit values.
155    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
156        test 2 if it fails.
158    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
159        and a #define of that name to empty if it is not externally set. This is to
160        allow users of MSVC to set it if necessary.
162    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
163        the convenience functions in the pcre_get.c source file.
165    11. An option change at the start of a pattern that had top-level alternatives
166        could cause overwriting and/or a crash. This command provoked a crash in
167        some environments:
169          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
171        This potential security problem was recorded as CVE-2008-2371.
173    12. For a pattern where the match had to start at the beginning or immediately
174        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
175        pcre_dfa_exec() could read past the end of the passed subject if there was
176        no match. To help with detecting such bugs (e.g. with valgrind), I modified
177        pcretest so that it places the subject at the end of its malloc-ed buffer.
179    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
180        exec() might read past the end of the data buffer in UTF-8 mode.
182    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
183        the data contained the byte 0x85 as part of a UTF-8 character within its
184        first line. This applied both to normal and DFA matching.
186    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
187        /^[^d]*?$/8 failed to match "abc".
189    16. Added a missing copyright notice to pcrecpp_internal.h.
191    17. Make it more clear in the documentation that values returned from
192        pcre_exec() in ovector are byte offsets, not character counts.
194    18. Tidied a few places to stop certain compilers from issuing warnings.
196    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
197        supplied by Stefan Weber. I made a further small update for 7.8 because
198        there is a change of source arrangements: the pcre_searchfuncs.c module is
199        replaced by pcre_ucd.c.
202    Version 7.7 07-May-08
203    ---------------------
205    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
206        a string to a long long, pretend we don't even have a long long." This is
207        done by checking for the strtoq, strtoll, and _strtoi64 functions.
209    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
210        pre-7.6 versions, which defined a global no_arg variable instead of putting
211        it in the RE class. (See also #8 below.)
213    3.  Remove a line of dead code, identified by coverity and reported by Nuno
214        Lopes.
216    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
218        (1) The include/exclude patterns were being applied to the whole pathnames
219            of files, instead of just to the final components.
221        (2) If there was more than one level of directory, the subdirectories were
222            skipped unless they satisfied the include/exclude conditions. This is
223            inconsistent with GNU grep (and could even be seen as contrary to the
224            pcregrep specification - which I improved to make it absolutely clear).
225            The action now is always to scan all levels of directory, and just
226            apply the include/exclude patterns to regular files.
228    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
229        --exclude_dir in the tests to avoid scanning .svn directories.
231    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
232        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
233        doesn't support NULs in patterns.
235    7.  Added some missing "const"s to declarations of static tables in
236        pcre_compile.c and pcre_dfa_exec.c.
238    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
239        caused by fix #2  above. (Subsequently also a second patch to fix the
240        first patch. And a third patch - this was a messy problem.)
242    9.  Applied Craig's patch to remove the use of push_back().
244    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
245        matching function regexec().
247    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
248        which, however, unlike Perl's \g{...}, are subroutine calls, not back
249        references. PCRE supports relative numbers with this syntax (I don't think
250        Oniguruma does).
252    12. Previously, a group with a zero repeat such as (...){0} was completely
253        omitted from the compiled regex. However, this means that if the group
254        was called as a subroutine from elsewhere in the pattern, things went wrong
255        (an internal error was given). Such groups are now left in the compiled
256        pattern, with a new opcode that causes them to be skipped at execution
257        time.
259    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
260        to the way PCRE behaves:
262        (a) A lone ] character is dis-allowed (Perl treats it as data).
264        (b) A back reference to an unmatched subpattern matches an empty string
265            (Perl fails the current match path).
267        (c) A data ] in a character class must be notated as \] because if the
268            first data character in a class is ], it defines an empty class. (In
269            Perl it is not possible to have an empty class.) The empty class []
270            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
271            The negative empty class [^] matches any one character, independently
272            of the DOTALL setting.
274    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
275        non-existent subpattern following a character class starting with ']' and
276        containing () gave an internal compiling error instead of "reference to
277        non-existent subpattern". Fortunately, when the pattern did exist, the
278        compiled code was correct. (When scanning forwards to check for the
279        existencd of the subpattern, it was treating the data ']' as terminating
280        the class, so got the count wrong. When actually compiling, the reference
281        was subsequently set up correctly.)
283    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
284        it was being rejected as not supported by pcre_dfa_exec(), even though
285        other assertions are supported. I have made pcre_dfa_exec() support
286        (*FAIL).
288    16. The implementation of 13c above involved the invention of a new opcode,
289        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
290        cannot be changed at match time, I realized I could make a small
291        improvement to matching performance by compiling OP_ALLANY instead of
292        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
293        on the OP_ANY path.
295    17. Compiling pcretest on Windows with readline support failed without the
296        following two fixes: (1) Make the unistd.h include conditional on
297        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
299    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
300        ncurses library to be included for pcretest when ReadLine support is
301        requested, but also to allow for it to be overridden. This patch came from
302        Daniel Bergström.
304    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
305        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
306        any errors with the current Unicode tables. Thanks to Peter Kankowski for
307        spotting this.
310    Version 7.6 28-Jan-08
311    ---------------------
313    1.  A character class containing a very large number of characters with
314        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
315        overflow.
317    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
318        HAVE_LONG_LONG is not defined.
320    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
321        bring them up to date and include new features. This patch includes:
323        - Fixed PH's badly added libz and libbz2 support.
324        - Fixed a problem with static linking.
325        - Added pcredemo. [But later removed - see 7 below.]
326        - Fixed dftables problem and added an option.
327        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
328            HAVE_LONG_LONG.
329        - Added readline support for pcretest.
330        - Added an listing of the option settings after cmake has run.
332    4.  A user submitted a patch to Makefile that makes it easy to create
333        "pcre.dll" under mingw when using Configure/Make. I added stuff to
334        Makefile.am that cause it to include this special target, without
335        affecting anything else. Note that the same mingw target plus all
336        the other distribution libraries and programs are now supported
337        when configuring with CMake (see 6 below) instead of with
338        Configure/Make.
340    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
341        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
342        exported in the Windows port". It has not yet been confirmed that the patch
343        solves the problem, but it does no harm.
345    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
346        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
347        with CMake, and also correct the comment about stack recursion.
349    7.  Remove the automatic building of pcredemo from the ./configure system and
350        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
351        of a program that users should build themselves after PCRE is installed, so
352        building it automatically is not really right. What is more, it gave
353        trouble in some build environments.
355    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
358    Version 7.5 10-Jan-08
359    ---------------------
361    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
362        values in parens when parsing an RE using the C++ wrapper."
364    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
365        Characters greater than 255 were excluded from the class instead of being
366        included.
368    3.  The same bug as (2) above applied to negated POSIX classes such as
369        [:^space:].
371    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
372        defined or documented. It seems to have been a typo for PCRE_STATIC, so
373        I have changed it.
375    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
376        first named subpattern) and a construct such as (?&a) would reference the
377        first named subpattern whose name started with "a" (in other words, the
378        length check was missing). Both these problems are fixed. "Subpattern name
379        expected" is now given for (?&) (a zero-length name), and this patch also
380        makes it give the same error for \k'' (previously it complained that that
381        was a reference to a non-existent subpattern).
383    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
384        this is right because (?- can be followed by option settings as well as by
385        digits. I have, however, made the messages clearer.
387    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
388        than the number used in the conditional) now cause a compile-time error.
389        This is actually not compatible with Perl, which accepts such patterns, but
390        treats the conditional as always being FALSE (as PCRE used to), but it
391        seems to me that giving a diagnostic is better.
393    8.  Change "alphameric" to the more common word "alphanumeric" in comments
394        and messages.
396    9.  Fix two occurrences of "backslash" in comments that should have been
397        "backspace".
399    10. Remove two redundant lines of code that can never be obeyed (their function
400        was moved elsewhere).
402    11. The program that makes PCRE's Unicode character property table had a bug
403        which caused it to generate incorrect table entries for sequences of
404        characters that have the same character type, but are in different scripts.
405        It amalgamated them into a single range, with the script of the first of
406        them. In other words, some characters were in the wrong script. There were
407        thirteen such cases, affecting characters in the following ranges:
409          U+002b0 - U+002c1
410          U+0060c - U+0060d
411          U+0061e - U+00612
412          U+0064b - U+0065e
413          U+0074d - U+0076d
414          U+01800 - U+01805
415          U+01d00 - U+01d77
416          U+01d9b - U+01dbf
417          U+0200b - U+0200f
418          U+030fc - U+030fe
419          U+03260 - U+0327f
420          U+0fb46 - U+0fbb1
421          U+10450 - U+1049d
423    12. The -o option (show only the matching part of a line) for pcregrep was not
424        compatible with GNU grep in that, if there was more than one match in a
425        line, it showed only the first of them. It now behaves in the same way as
426        GNU grep.
428    13. If the -o and -v options were combined for pcregrep, it printed a blank
429        line for every non-matching line. GNU grep prints nothing, and pcregrep now
430        does the same. The return code can be used to tell if there were any
431        non-matching lines.
433    14. Added --file-offsets and --line-offsets to pcregrep.
435    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
436        infinitely looping recursion. The bug was that positive lookaheads were not
437        being skipped when checking for a possible empty match (negative lookaheads
438        and both kinds of lookbehind were skipped).
440    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
441        inclusion of <windows.h> to before rather than after the definition of
442        INVALID_FILE_ATTRIBUTES (patch from David Byron).
444    17. Specifying a possessive quantifier with a specific limit for a Unicode
445        character property caused pcre_compile() to compile bad code, which led at
446        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
447        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
448        caused the error; without that there was no problem.
450    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
452    19. Added --enable-pcretest-libreadline.
454    20. In pcrecpp.cc, the variable 'count' was incremented twice in
455        RE::GlobalReplace(). As a result, the number of replacements returned was
456        double what it should be. I removed one of the increments, but Craig sent a
457        later patch that removed the other one (the right fix) and added unit tests
458        that check the return values (which was not done before).
460    21. Several CMake things:
462        (1) Arranged that, when cmake is used on Unix, the libraries end up with
463            the names libpcre and libpcreposix, not just pcre and pcreposix.
465        (2) The above change means that pcretest and pcregrep are now correctly
466            linked with the newly-built libraries, not previously installed ones.
470    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
471        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
472        UTF-8 newline character). The key issue is that the pattern starts .*;
473        this means that the match must be either at the beginning, or after a
474        newline. The bug was in the code for advancing after a failed match and
475        checking that the new position followed a newline. It was not taking
476        account of UTF-8 characters correctly.
478    23. PCRE was behaving differently from Perl in the way it recognized POSIX
479        character classes. PCRE was not treating the sequence [:...:] as a
480        character class unless the ... were all letters. Perl, however, seems to
481        allow any characters between [: and :], though of course it rejects as
482        unknown any "names" that contain non-letters, because all the known class
483        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
484        for example, whereas PCRE did not - it did not recognize a POSIX character
485        class. This seemed a bit dangerous, so the code has been changed to be
486        closer to Perl. The behaviour is not identical to Perl, because PCRE will
487        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
488        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
489        Perl does, and where it didn't before.
491    24. Rewrite so as to remove the single use of %n from pcregrep because in some
492        Windows environments %n is disabled by default.
495    Version 7.4 21-Sep-07
496    ---------------------
498    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
499        means that a class such as [\s] counted as "explicit reference to CR or
500        LF". That isn't really right - the whole point of the change was to try to
501        help when there was an actual mention of one of the two characters. So now
502        the change happens only if \r or \n (or a literal CR or LF) character is
503        encountered.
505    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
506        of both had grown to the point where there were only 3 bits left.
507        Fortunately, there was spare space in the data structure, and so I have
508        moved the internal flags into a new 16-bit field to free up more option
509        bits.
511    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
512        but did not set the internal JCHANGED flag - either of these is enough to
513        control the way the "get" function works - but the PCRE_INFO_JCHANGED
514        facility is supposed to tell if (?J) was ever used, so now (?J) at the
515        start sets both bits.
517    4.  Added options (at build time, compile time, exec time) to change \R from
518        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
520    5.  doc/pcresyntax.html was missing from the distribution.
522    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
523        compatibility, even though it is no longer used.
525    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
526        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
527        windows.h file is present (where different names are used). [This was
528        reversed later after testing - see 16 below.]
530    8.  Changed all #include <config.h> to #include "config.h". There were also
531        some further <pcre.h> cases that I changed to "pcre.h".
533    9.  When pcregrep was used with the --colour option, it missed the line ending
534        sequence off the lines that it output.
536    10. It was pointed out to me that arrays of string pointers cause lots of
537        relocations when a shared library is dynamically loaded. A technique of
538        using a single long string with a table of offsets can drastically reduce
539        these. I have refactored PCRE in four places to do this. The result is
540        dramatic:
542          Originally:                          290
543          After changing UCP table:            187
544          After changing error message table:   43
545          After changing table of "verbs"       36
546          After changing table of Posix names   22
548        Thanks to the folks working on Gregex for glib for this insight.
550    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
551        unicode-properties was also set.
553    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
555    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
556        checked only for CRLF.
558    14. Added casts to pcretest.c to avoid compiler warnings.
560    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
562    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
563        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
564        entirely. This removes changes made in 7 above.
566    17. The CMake files have been updated, and there is now more information about
567        building with CMake in the NON-UNIX-USE document.
570    Version 7.3 28-Aug-07
571    ---------------------
573     1. In the rejigging of the build system that eventually resulted in 7.1, the
574        line "#include <pcre.h>" was included in pcre_internal.h. The use of angle
575        brackets there is not right, since it causes compilers to look for an
576        installed pcre.h, not the version that is in the source that is being
577        compiled (which of course may be different). I have changed it back to:
579          #include "pcre.h"
581        I have a vague recollection that the change was concerned with compiling in
582        different directories, but in the new build system, that is taken care of
583        by the VPATH setting the Makefile.
585     2. The pattern .*$ when run in not-DOTALL UTF-8 mode with newline=any failed
586        when the subject happened to end in the byte 0x85 (e.g. if the last
587        character was \x{1ec5}). *Character* 0x85 is one of the "any" newline
588        characters but of course it shouldn't be taken as a newline when it is part
589        of another character. The bug was that, for an unlimited repeat of . in
590        not-DOTALL UTF-8 mode, PCRE was advancing by bytes rather than by
591        characters when looking for a newline.
593     3. A small performance improvement in the DOTALL UTF-8 mode .* case.
595     4. Debugging: adjusted the names of opcodes for different kinds of parentheses
596        in debug output.
598     5. Arrange to use "%I64d" instead of "%lld" and "%I64u" instead of "%llu" for
599        long printing in the pcrecpp unittest when running under MinGW.
601     6. ESC_K was left out of the EBCDIC table.
603     7. Change 7.0/38 introduced a new limit on the number of nested non-capturing
604        parentheses; I made it 1000, which seemed large enough. Unfortunately, the
605        limit also applies to "virtual nesting" when a pattern is recursive, and in
606        this case 1000 isn't so big. I have been able to remove this limit at the
607        expense of backing off one optimization in certain circumstances. Normally,
608        when pcre_exec() would call its internal match() function recursively and
609        immediately return the result unconditionally, it uses a "tail recursion"
610        feature to save stack. However, when a subpattern that can match an empty
611        string has an unlimited repetition quantifier, it no longer makes this
612        optimization. That gives it a stack frame in which to save the data for
613        checking that an empty string has been matched. Previously this was taken
614        from the 1000-entry workspace that had been reserved. So now there is no
615        explicit limit, but more stack is used.
617     8. Applied Daniel's patches to solve problems with the import/export magic
618        syntax that is required for Windows, and which was going wrong for the
619        pcreposix and pcrecpp parts of the library. These were overlooked when this
620        problem was solved for the main library.
622     9. There were some crude static tests to avoid integer overflow when computing
623        the size of patterns that contain repeated groups with explicit upper
624        limits. As the maximum quantifier is 65535, the maximum group length was
625        set at 30,000 so that the product of these two numbers did not overflow a
626        32-bit integer. However, it turns out that people want to use groups that
627        are longer than 30,000 bytes (though not repeat them that many times).
628        Change 7.0/17 (the refactoring of the way the pattern size is computed) has
629        made it possible to implement the integer overflow checks in a much more
630        dynamic way, which I have now done. The artificial limitation on group
631        length has been removed - we now have only the limit on the total length of
632        the compiled pattern, which depends on the LINK_SIZE setting.
634    10. Fixed a bug in the documentation for get/copy named substring when
635        duplicate names are permitted. If none of the named substrings are set, the
636        functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an
637        empty string.
639    11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E
640        instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,
641        because the ] is interpreted as the first data character and the
642        terminating ] is not found. PCRE has been made compatible with Perl in this
643        regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could
644        cause memory overwriting.
646    10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty
647        string has been matched (to stop an infinite loop). It was not recognizing
648        a conditional subpattern that could match an empty string if that
649        subpattern was within another subpattern. For example, it looped when
650        trying to match  (((?(1)X|))*)  but it was OK with  ((?(1)X|)*)  where the
651        condition was not nested. This bug has been fixed.
653    12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack
654        past the start of the subject in the presence of bytes with the top bit
655        set, for example "\x8aBCD".
657    13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
658        (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
660    14. Optimized (?!) to (*FAIL).
662    15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
663        This restricts code points to be within the range 0 to 0x10FFFF, excluding
664        the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
665        full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
666        does: it's just the validity check that is more restrictive.
668    16. Inserted checks for integer overflows during escape sequence (backslash)
669        processing, and also fixed erroneous offset values for syntax errors during
670        backslash processing.
672    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
673        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
675    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
676        caused an overrun.
678    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
679        something other than just ASCII characters) inside a group that had an
680        unlimited repeat caused a loop at compile time (while checking to see
681        whether the group could match an empty string).
683    20. Debugging a pattern containing \p or \P could cause a crash. For example,
684        [\P{Any}] did so. (Error in the code for printing property names.)
686    21. An orphan \E inside a character class could cause a crash.
688    22. A repeated capturing bracket such as (A)? could cause a wild memory
689        reference during compilation.
691    23. There are several functions in pcre_compile() that scan along a compiled
692        expression for various reasons (e.g. to see if it's fixed length for look
693        behind). There were bugs in these functions when a repeated \p or \P was
694        present in the pattern. These operators have additional parameters compared
695        with \d, etc, and these were not being taken into account when moving along
696        the compiled data. Specifically:
698        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
699            length.
701        (b) An item such as \pL+ within a repeated group could cause crashes or
702            loops.
704        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
705            "reference to non-existent subpattern" error.
707        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
709    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
710        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
712    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
714    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
715        character were causing crashes (broken optimization).
717    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
718        \p or \P) caused a compile-time loop.
720    28. More problems have arisen in unanchored patterns when CRLF is a valid line
721        break. For example, the unstudied pattern [\r\n]A does not match the string
722        "\r\nA" because change 7.0/46 below moves the current point on by two
723        characters after failing to match at the start. However, the pattern \nA
724        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
725        the same is true. There doesn't seem any very clean way out of this, but
726        what I have chosen to do makes the common cases work: PCRE now takes note
727        of whether there can be an explicit match for \r or \n anywhere in the
728        pattern, and if so, 7.0/46 no longer applies. As part of this change,
729        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
730        pattern has explicit CR or LF references.
732    29. Added (*CR) etc for changing newline setting at start of pattern.
735    Version 7.2 19-Jun-07
736  ---------------------  ---------------------
738   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 771  Version 7.2 13-June-07
772      (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
773          reference syntax.          reference syntax.
775      (g) (?| introduces a group in which the numbering of parentheses in each      (g) (?| introduces a group in which the numbering of parentheses in each
776          alternative starts with the same number.          alternative starts with the same number.
778      (h) \h, \H, \v, and \V match horizontal and vertical whitespace.      (h) \h, \H, \v, and \V match horizontal and vertical whitespace.
780   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 790  Version 7.2 13-June-07
790      bit of new cunning has reduced the workspace needed for groups with      bit of new cunning has reduced the workspace needed for groups with
791      alternatives. The 1000-alternative test pattern now uses 12 bytes of      alternatives. The 1000-alternative test pattern now uses 12 bytes of
792      workspace instead of running out of the 4096 that are available.      workspace instead of running out of the 4096 that are available.
794  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.
796  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.
797      The report of the bug said:      The report of the bug said:
799        pcrecpp::RE("a*").FullMatch("aaa") matches, while        pcrecpp::RE("a*").FullMatch("aaa") matches, while
800        pcrecpp::RE("a*?").FullMatch("aaa") does not, and        pcrecpp::RE("a*?").FullMatch("aaa") does not, and
801        pcrecpp::RE("a*?\\z").FullMatch("aaa") does again.        pcrecpp::RE("a*?\\z").FullMatch("aaa") does again.
803    12. If \p or \P was used in non-UTF-8 mode on a character greater than 127
804        it matched the wrong number of bytes.
807  Version 7.1 24-Apr-07  Version 7.1 24-Apr-07

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

  ViewVC Help
Powered by ViewVC 1.1.5