ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 175 by ph10, Mon Jun 11 13:38:38 2007 UTC revision 430 by ph10, Tue Sep 1 16:29:46 2009 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 7.2 05-June-07  Version 8.00 ??-???-??
5    ----------------------
7    1.  The table for translating pcre_compile() error codes into POSIX error codes
8        was out-of-date, and there was no check on the pcre_compile() error code
9        being within the table. This could lead to an OK return being given in
10        error.
12    2.  Changed the call to open a subject file in pcregrep from fopen(pathname,
13        "r") to fopen(pathname, "rb"), which fixed a problem with some of the tests
14        in a Windows environment.
16    3.  The pcregrep --count option prints the count for each file even when it is
17        zero, as does GNU grep. However, pcregrep was also printing all files when
18        --files-with-matches was added. Now, when both options are given, it prints
19        counts only for those files that have at least one match. (GNU grep just
20        prints the file name in this circumstance, but including the count seems
21        more useful - otherwise, why use --count?) Also ensured that the
22        combination -clh just lists non-zero counts, with no names.
24    4.  The long form of the pcregrep -F option was incorrectly implemented as
25        --fixed_strings instead of --fixed-strings. This is an incompatible change,
26        but it seems right to fix it, and I didn't think it was worth preserving
27        the old behaviour.
29    5.  The command line items --regex=pattern and --regexp=pattern were not
30        recognized by pcregrep, which required --regex pattern or --regexp pattern
31        (with a space rather than an '='). The man page documented the '=' forms,
32        which are compatible with GNU grep; these now work.
34    6.  No libpcreposix.pc file was created for pkg-config; there was just
35        libpcre.pc and libpcrecpp.pc. The omission has been rectified.
37    7.  Added #ifndef SUPPORT_UCP into the pcre_ucd.c module, to reduce its size
38        when UCP support is not needed, by modifying the Python script that
39        generates it from Unicode data files. This should not matter if the module
40        is correctly used as a library, but I received one complaint about 50K of
41        unwanted data. My guess is that the person linked everything into his
42        program rather than using a library. Anyway, it does no harm.
44    8.  A pattern such as /\x{123}{2,2}+/8 was incorrectly compiled; the trigger
45        was a minimum greater than 1 for a wide character in a possessive
46        repetition. Chaos could result.
48    9.  The restrictions on what a pattern can contain when partial matching is
49        requested for pcre_exec() have been removed. All patterns can now be
50        partially matched by this function. In addition, if there are at least two
51        slots in the offset vector, the offsets of the first-encountered partial
52        match are set in them when PCRE_ERROR_PARTIAL is returned.
54    10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is
55        synonymous with PCRE_PARTIAL, for backwards compatibility, and
56        PCRE_PARTIAL_HARD, which causes a partial match to supersede a full match,
57        and may be more useful for multi-segment matching, especially with
58        pcre_exec().
60    11. Partial matching with pcre_exec() is now more intuitive. A partial match
61        used to be given if ever the end of the subject was reached; now it is
62        given only if matching could not proceed because another character was
63        needed. This makes a difference in some odd cases such as Z(*FAIL) with the
64        string "Z", which now yields "no match" instead of "partial match". In the
65        case of pcre_dfa_exec(), "no match" is given if every matching path for the
66        final character ended with (*FAIL).
68    12. Restarting a match using pcre_dfa_exec() after a partial match did not work
69        if the pattern had a "must contain" character that was already found in the
70        earlier partial match, unless partial matching was again requested. For
71        example, with the pattern /dog.(body)?/, the "must contain" character is
72        "g". If the first part-match was for the string "dog", restarting with
73        "sbody" failed.
75    13. Added a pcredemo man page, created automatically from the pcredemo.c file,
76        so that the demonstration program is easily available in environments where
77        PCRE has not been installed from source.
79    14. Arranged to add -DPCRE_STATIC to cflags in libpcre.pc, libpcreposix.cp,
80        libpcrecpp.pc and pcre-config when PCRE is not compiled as a shared
81        library.
84    Version 7.9 11-Apr-09
85    ---------------------
87    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
88        (pcretest), all targets were linked against these libraries. This included
89        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
90        libraries. This caused unwanted dependencies to be created. This problem
91        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
92        pcretest is linked with readline.
94    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
95        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
96        moved outside it again, because FALSE and TRUE are already defined in AIX,
97        but BOOL is not.
99    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
100        PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
102    4.  The pcregrep documentation said spaces were inserted as well as colons (or
103        hyphens) following file names and line numbers when outputting matching
104        lines. This is not true; no spaces are inserted. I have also clarified the
105        wording for the --colour (or --color) option.
107    5.  In pcregrep, when --colour was used with -o, the list of matching strings
108        was not coloured; this is different to GNU grep, so I have changed it to be
109        the same.
111    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
112        each matching line was coloured. Now it goes on to look for further matches
113        of any of the test patterns, which is the same behaviour as GNU grep.
115    7.  A pattern that could match an empty string could cause pcregrep to loop; it
116        doesn't make sense to accept an empty string match in pcregrep, so I have
117        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
118        seems to be how GNU grep behaves.
120    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
121        start or after a newline", because the conditional assertion was not being
122        correctly handled. The rule now is that both the assertion and what follows
123        in the first alternative must satisfy the test.
125    9.  If auto-callout was enabled in a pattern with a conditional group whose
126        condition was an assertion, PCRE could crash during matching, both with
127        pcre_exec() and pcre_dfa_exec().
129    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
130        used for matching.
132    11. Unicode property support in character classes was not working for
133        characters (bytes) greater than 127 when not in UTF-8 mode.
135    12. Added the -M command line option to pcretest.
137    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
139    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
141    16. Added comments and documentation about mis-use of no_arg in the C++
142        wrapper.
144    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
145        from Martin Jerabek that uses macro names for all relevant character and
146        string constants.
148    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
149        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
150        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
151        these, but not everybody uses configure.
153    19. A conditional group that had only one branch was not being correctly
154        recognized as an item that could match an empty string. This meant that an
155        enclosing group might also not be so recognized, causing infinite looping
156        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
157        with the subject "ab", where knowledge that the repeated group can match
158        nothing is needed in order to break the loop.
160    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
161        exec(), but without supplying a callout function, matching went wrong.
163    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
164        leak if the size of the offset vector was greater than 30. When the vector
165        is smaller, the saved offsets during recursion go onto a local stack
166        vector, but for larger vectors malloc() is used. It was failing to free
167        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
168        error, in fact).
170    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
171        heapframe that is used only when UTF-8 support is enabled. This caused no
172        problem, but was untidy.
174    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
175        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
176        included within another project.
178    24. Steven Van Ingelgem's patches to add more options to the CMake support,
179        slightly modified by me:
181          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
182              not building pcregrep.
184          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
185              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
187    25. Forward references, both numeric and by name, in patterns that made use of
188        duplicate group numbers, could behave incorrectly or give incorrect errors,
189        because when scanning forward to find the reference group, PCRE was not
190        taking into account the duplicate group numbers. A pattern such as
191        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
193    26. Changed a few more instances of "const unsigned char *" to USPTR, making
194        the feature of a custom pointer more persuasive (as requested by a user).
196    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
197        pcretest.c, inside #ifndefs, because it seems they are sometimes already
198        pre-defined.
200    28. Added support for (*UTF8) at the start of a pattern.
202    29. Arrange for flags added by the "release type" setting in CMake to be shown
203        in the configuration summary.
206    Version 7.8 05-Sep-08
207    ---------------------
209    1.  Replaced UCP searching code with optimized version as implemented for Ad
210        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
211        stage table and inline lookup instead of a function, giving speed ups of 2
212        to 5 times on some simple patterns that I tested. Permission was given to
213        distribute the MultiStage2.py script that generates the tables (it's not in
214        the tarball, but is in the Subversion repository).
216    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
217        scripts.
219    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
220        a group with a zero qualifier. The result of the study could be incorrect,
221        or the function might crash, depending on the pattern.
223    4.  Caseless matching was not working for non-ASCII characters in back
224        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
225        It now works when Unicode Property Support is available.
227    5.  In pcretest, an escape such as \x{de} in the data was always generating
228        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
229        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
230        truncation.
232    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
234    7.  Added two (int) casts to pcregrep when printing the difference of two
235        pointers, in case they are 64-bit values.
237    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
238        test 2 if it fails.
240    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
241        and a #define of that name to empty if it is not externally set. This is to
242        allow users of MSVC to set it if necessary.
244    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
245        the convenience functions in the pcre_get.c source file.
247    11. An option change at the start of a pattern that had top-level alternatives
248        could cause overwriting and/or a crash. This command provoked a crash in
249        some environments:
251          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
253        This potential security problem was recorded as CVE-2008-2371.
255    12. For a pattern where the match had to start at the beginning or immediately
256        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
257        pcre_dfa_exec() could read past the end of the passed subject if there was
258        no match. To help with detecting such bugs (e.g. with valgrind), I modified
259        pcretest so that it places the subject at the end of its malloc-ed buffer.
261    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
262        exec() might read past the end of the data buffer in UTF-8 mode.
264    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
265        the data contained the byte 0x85 as part of a UTF-8 character within its
266        first line. This applied both to normal and DFA matching.
268    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
269        /^[^d]*?$/8 failed to match "abc".
271    16. Added a missing copyright notice to pcrecpp_internal.h.
273    17. Make it more clear in the documentation that values returned from
274        pcre_exec() in ovector are byte offsets, not character counts.
276    18. Tidied a few places to stop certain compilers from issuing warnings.
278    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
279        supplied by Stefan Weber. I made a further small update for 7.8 because
280        there is a change of source arrangements: the pcre_searchfuncs.c module is
281        replaced by pcre_ucd.c.
284    Version 7.7 07-May-08
285    ---------------------
287    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
288        a string to a long long, pretend we don't even have a long long." This is
289        done by checking for the strtoq, strtoll, and _strtoi64 functions.
291    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
292        pre-7.6 versions, which defined a global no_arg variable instead of putting
293        it in the RE class. (See also #8 below.)
295    3.  Remove a line of dead code, identified by coverity and reported by Nuno
296        Lopes.
298    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
300        (1) The include/exclude patterns were being applied to the whole pathnames
301            of files, instead of just to the final components.
303        (2) If there was more than one level of directory, the subdirectories were
304            skipped unless they satisfied the include/exclude conditions. This is
305            inconsistent with GNU grep (and could even be seen as contrary to the
306            pcregrep specification - which I improved to make it absolutely clear).
307            The action now is always to scan all levels of directory, and just
308            apply the include/exclude patterns to regular files.
310    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
311        --exclude_dir in the tests to avoid scanning .svn directories.
313    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
314        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
315        doesn't support NULs in patterns.
317    7.  Added some missing "const"s to declarations of static tables in
318        pcre_compile.c and pcre_dfa_exec.c.
320    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
321        caused by fix #2  above. (Subsequently also a second patch to fix the
322        first patch. And a third patch - this was a messy problem.)
324    9.  Applied Craig's patch to remove the use of push_back().
326    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
327        matching function regexec().
329    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
330        which, however, unlike Perl's \g{...}, are subroutine calls, not back
331        references. PCRE supports relative numbers with this syntax (I don't think
332        Oniguruma does).
334    12. Previously, a group with a zero repeat such as (...){0} was completely
335        omitted from the compiled regex. However, this means that if the group
336        was called as a subroutine from elsewhere in the pattern, things went wrong
337        (an internal error was given). Such groups are now left in the compiled
338        pattern, with a new opcode that causes them to be skipped at execution
339        time.
341    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
342        to the way PCRE behaves:
344        (a) A lone ] character is dis-allowed (Perl treats it as data).
346        (b) A back reference to an unmatched subpattern matches an empty string
347            (Perl fails the current match path).
349        (c) A data ] in a character class must be notated as \] because if the
350            first data character in a class is ], it defines an empty class. (In
351            Perl it is not possible to have an empty class.) The empty class []
352            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
353            The negative empty class [^] matches any one character, independently
354            of the DOTALL setting.
356    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
357        non-existent subpattern following a character class starting with ']' and
358        containing () gave an internal compiling error instead of "reference to
359        non-existent subpattern". Fortunately, when the pattern did exist, the
360        compiled code was correct. (When scanning forwards to check for the
361        existencd of the subpattern, it was treating the data ']' as terminating
362        the class, so got the count wrong. When actually compiling, the reference
363        was subsequently set up correctly.)
365    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
366        it was being rejected as not supported by pcre_dfa_exec(), even though
367        other assertions are supported. I have made pcre_dfa_exec() support
368        (*FAIL).
370    16. The implementation of 13c above involved the invention of a new opcode,
371        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
372        cannot be changed at match time, I realized I could make a small
373        improvement to matching performance by compiling OP_ALLANY instead of
374        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
375        on the OP_ANY path.
377    17. Compiling pcretest on Windows with readline support failed without the
378        following two fixes: (1) Make the unistd.h include conditional on
379        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
381    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
382        ncurses library to be included for pcretest when ReadLine support is
383        requested, but also to allow for it to be overridden. This patch came from
384        Daniel Bergström.
386    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
387        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
388        any errors with the current Unicode tables. Thanks to Peter Kankowski for
389        spotting this.
392    Version 7.6 28-Jan-08
393    ---------------------
395    1.  A character class containing a very large number of characters with
396        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
397        overflow.
399    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
400        HAVE_LONG_LONG is not defined.
402    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
403        bring them up to date and include new features. This patch includes:
405        - Fixed PH's badly added libz and libbz2 support.
406        - Fixed a problem with static linking.
407        - Added pcredemo. [But later removed - see 7 below.]
408        - Fixed dftables problem and added an option.
409        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
410            HAVE_LONG_LONG.
411        - Added readline support for pcretest.
412        - Added an listing of the option settings after cmake has run.
414    4.  A user submitted a patch to Makefile that makes it easy to create
415        "pcre.dll" under mingw when using Configure/Make. I added stuff to
416        Makefile.am that cause it to include this special target, without
417        affecting anything else. Note that the same mingw target plus all
418        the other distribution libraries and programs are now supported
419        when configuring with CMake (see 6 below) instead of with
420        Configure/Make.
422    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
423        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
424        exported in the Windows port". It has not yet been confirmed that the patch
425        solves the problem, but it does no harm.
427    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
428        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
429        with CMake, and also correct the comment about stack recursion.
431    7.  Remove the automatic building of pcredemo from the ./configure system and
432        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
433        of a program that users should build themselves after PCRE is installed, so
434        building it automatically is not really right. What is more, it gave
435        trouble in some build environments.
437    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
440    Version 7.5 10-Jan-08
441    ---------------------
443    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
444        values in parens when parsing an RE using the C++ wrapper."
446    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
447        Characters greater than 255 were excluded from the class instead of being
448        included.
450    3.  The same bug as (2) above applied to negated POSIX classes such as
451        [:^space:].
453    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
454        defined or documented. It seems to have been a typo for PCRE_STATIC, so
455        I have changed it.
457    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
458        first named subpattern) and a construct such as (?&a) would reference the
459        first named subpattern whose name started with "a" (in other words, the
460        length check was missing). Both these problems are fixed. "Subpattern name
461        expected" is now given for (?&) (a zero-length name), and this patch also
462        makes it give the same error for \k'' (previously it complained that that
463        was a reference to a non-existent subpattern).
465    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
466        this is right because (?- can be followed by option settings as well as by
467        digits. I have, however, made the messages clearer.
469    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
470        than the number used in the conditional) now cause a compile-time error.
471        This is actually not compatible with Perl, which accepts such patterns, but
472        treats the conditional as always being FALSE (as PCRE used to), but it
473        seems to me that giving a diagnostic is better.
475    8.  Change "alphameric" to the more common word "alphanumeric" in comments
476        and messages.
478    9.  Fix two occurrences of "backslash" in comments that should have been
479        "backspace".
481    10. Remove two redundant lines of code that can never be obeyed (their function
482        was moved elsewhere).
484    11. The program that makes PCRE's Unicode character property table had a bug
485        which caused it to generate incorrect table entries for sequences of
486        characters that have the same character type, but are in different scripts.
487        It amalgamated them into a single range, with the script of the first of
488        them. In other words, some characters were in the wrong script. There were
489        thirteen such cases, affecting characters in the following ranges:
491          U+002b0 - U+002c1
492          U+0060c - U+0060d
493          U+0061e - U+00612
494          U+0064b - U+0065e
495          U+0074d - U+0076d
496          U+01800 - U+01805
497          U+01d00 - U+01d77
498          U+01d9b - U+01dbf
499          U+0200b - U+0200f
500          U+030fc - U+030fe
501          U+03260 - U+0327f
502          U+0fb46 - U+0fbb1
503          U+10450 - U+1049d
505    12. The -o option (show only the matching part of a line) for pcregrep was not
506        compatible with GNU grep in that, if there was more than one match in a
507        line, it showed only the first of them. It now behaves in the same way as
508        GNU grep.
510    13. If the -o and -v options were combined for pcregrep, it printed a blank
511        line for every non-matching line. GNU grep prints nothing, and pcregrep now
512        does the same. The return code can be used to tell if there were any
513        non-matching lines.
515    14. Added --file-offsets and --line-offsets to pcregrep.
517    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
518        infinitely looping recursion. The bug was that positive lookaheads were not
519        being skipped when checking for a possible empty match (negative lookaheads
520        and both kinds of lookbehind were skipped).
522    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
523        inclusion of <windows.h> to before rather than after the definition of
524        INVALID_FILE_ATTRIBUTES (patch from David Byron).
526    17. Specifying a possessive quantifier with a specific limit for a Unicode
527        character property caused pcre_compile() to compile bad code, which led at
528        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
529        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
530        caused the error; without that there was no problem.
532    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
534    19. Added --enable-pcretest-libreadline.
536    20. In pcrecpp.cc, the variable 'count' was incremented twice in
537        RE::GlobalReplace(). As a result, the number of replacements returned was
538        double what it should be. I removed one of the increments, but Craig sent a
539        later patch that removed the other one (the right fix) and added unit tests
540        that check the return values (which was not done before).
542    21. Several CMake things:
544        (1) Arranged that, when cmake is used on Unix, the libraries end up with
545            the names libpcre and libpcreposix, not just pcre and pcreposix.
547        (2) The above change means that pcretest and pcregrep are now correctly
548            linked with the newly-built libraries, not previously installed ones.
552    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
553        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
554        UTF-8 newline character). The key issue is that the pattern starts .*;
555        this means that the match must be either at the beginning, or after a
556        newline. The bug was in the code for advancing after a failed match and
557        checking that the new position followed a newline. It was not taking
558        account of UTF-8 characters correctly.
560    23. PCRE was behaving differently from Perl in the way it recognized POSIX
561        character classes. PCRE was not treating the sequence [:...:] as a
562        character class unless the ... were all letters. Perl, however, seems to
563        allow any characters between [: and :], though of course it rejects as
564        unknown any "names" that contain non-letters, because all the known class
565        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
566        for example, whereas PCRE did not - it did not recognize a POSIX character
567        class. This seemed a bit dangerous, so the code has been changed to be
568        closer to Perl. The behaviour is not identical to Perl, because PCRE will
569        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
570        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
571        Perl does, and where it didn't before.
573    24. Rewrite so as to remove the single use of %n from pcregrep because in some
574        Windows environments %n is disabled by default.
577    Version 7.4 21-Sep-07
578    ---------------------
580    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
581        means that a class such as [\s] counted as "explicit reference to CR or
582        LF". That isn't really right - the whole point of the change was to try to
583        help when there was an actual mention of one of the two characters. So now
584        the change happens only if \r or \n (or a literal CR or LF) character is
585        encountered.
587    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
588        of both had grown to the point where there were only 3 bits left.
589        Fortunately, there was spare space in the data structure, and so I have
590        moved the internal flags into a new 16-bit field to free up more option
591        bits.
593    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
594        but did not set the internal JCHANGED flag - either of these is enough to
595        control the way the "get" function works - but the PCRE_INFO_JCHANGED
596        facility is supposed to tell if (?J) was ever used, so now (?J) at the
597        start sets both bits.
599    4.  Added options (at build time, compile time, exec time) to change \R from
600        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
602    5.  doc/pcresyntax.html was missing from the distribution.
604    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
605        compatibility, even though it is no longer used.
607    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
608        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
609        windows.h file is present (where different names are used). [This was
610        reversed later after testing - see 16 below.]
612    8.  Changed all #include <config.h> to #include "config.h". There were also
613        some further <pcre.h> cases that I changed to "pcre.h".
615    9.  When pcregrep was used with the --colour option, it missed the line ending
616        sequence off the lines that it output.
618    10. It was pointed out to me that arrays of string pointers cause lots of
619        relocations when a shared library is dynamically loaded. A technique of
620        using a single long string with a table of offsets can drastically reduce
621        these. I have refactored PCRE in four places to do this. The result is
622        dramatic:
624          Originally:                          290
625          After changing UCP table:            187
626          After changing error message table:   43
627          After changing table of "verbs"       36
628          After changing table of Posix names   22
630        Thanks to the folks working on Gregex for glib for this insight.
632    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
633        unicode-properties was also set.
635    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
637    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
638        checked only for CRLF.
640    14. Added casts to pcretest.c to avoid compiler warnings.
642    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
644    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
645        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
646        entirely. This removes changes made in 7 above.
648    17. The CMake files have been updated, and there is now more information about
649        building with CMake in the NON-UNIX-USE document.
652    Version 7.3 28-Aug-07
653    ---------------------
655     1. In the rejigging of the build system that eventually resulted in 7.1, the
656        line "#include <pcre.h>" was included in pcre_internal.h. The use of angle
657        brackets there is not right, since it causes compilers to look for an
658        installed pcre.h, not the version that is in the source that is being
659        compiled (which of course may be different). I have changed it back to:
661          #include "pcre.h"
663        I have a vague recollection that the change was concerned with compiling in
664        different directories, but in the new build system, that is taken care of
665        by the VPATH setting the Makefile.
667     2. The pattern .*$ when run in not-DOTALL UTF-8 mode with newline=any failed
668        when the subject happened to end in the byte 0x85 (e.g. if the last
669        character was \x{1ec5}). *Character* 0x85 is one of the "any" newline
670        characters but of course it shouldn't be taken as a newline when it is part
671        of another character. The bug was that, for an unlimited repeat of . in
672        not-DOTALL UTF-8 mode, PCRE was advancing by bytes rather than by
673        characters when looking for a newline.
675     3. A small performance improvement in the DOTALL UTF-8 mode .* case.
677     4. Debugging: adjusted the names of opcodes for different kinds of parentheses
678        in debug output.
680     5. Arrange to use "%I64d" instead of "%lld" and "%I64u" instead of "%llu" for
681        long printing in the pcrecpp unittest when running under MinGW.
683     6. ESC_K was left out of the EBCDIC table.
685     7. Change 7.0/38 introduced a new limit on the number of nested non-capturing
686        parentheses; I made it 1000, which seemed large enough. Unfortunately, the
687        limit also applies to "virtual nesting" when a pattern is recursive, and in
688        this case 1000 isn't so big. I have been able to remove this limit at the
689        expense of backing off one optimization in certain circumstances. Normally,
690        when pcre_exec() would call its internal match() function recursively and
691        immediately return the result unconditionally, it uses a "tail recursion"
692        feature to save stack. However, when a subpattern that can match an empty
693        string has an unlimited repetition quantifier, it no longer makes this
694        optimization. That gives it a stack frame in which to save the data for
695        checking that an empty string has been matched. Previously this was taken
696        from the 1000-entry workspace that had been reserved. So now there is no
697        explicit limit, but more stack is used.
699     8. Applied Daniel's patches to solve problems with the import/export magic
700        syntax that is required for Windows, and which was going wrong for the
701        pcreposix and pcrecpp parts of the library. These were overlooked when this
702        problem was solved for the main library.
704     9. There were some crude static tests to avoid integer overflow when computing
705        the size of patterns that contain repeated groups with explicit upper
706        limits. As the maximum quantifier is 65535, the maximum group length was
707        set at 30,000 so that the product of these two numbers did not overflow a
708        32-bit integer. However, it turns out that people want to use groups that
709        are longer than 30,000 bytes (though not repeat them that many times).
710        Change 7.0/17 (the refactoring of the way the pattern size is computed) has
711        made it possible to implement the integer overflow checks in a much more
712        dynamic way, which I have now done. The artificial limitation on group
713        length has been removed - we now have only the limit on the total length of
714        the compiled pattern, which depends on the LINK_SIZE setting.
716    10. Fixed a bug in the documentation for get/copy named substring when
717        duplicate names are permitted. If none of the named substrings are set, the
718        functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an
719        empty string.
721    11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E
722        instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,
723        because the ] is interpreted as the first data character and the
724        terminating ] is not found. PCRE has been made compatible with Perl in this
725        regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could
726        cause memory overwriting.
728    10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty
729        string has been matched (to stop an infinite loop). It was not recognizing
730        a conditional subpattern that could match an empty string if that
731        subpattern was within another subpattern. For example, it looped when
732        trying to match  (((?(1)X|))*)  but it was OK with  ((?(1)X|)*)  where the
733        condition was not nested. This bug has been fixed.
735    12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack
736        past the start of the subject in the presence of bytes with the top bit
737        set, for example "\x8aBCD".
739    13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
740        (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
742    14. Optimized (?!) to (*FAIL).
744    15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
745        This restricts code points to be within the range 0 to 0x10FFFF, excluding
746        the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
747        full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
748        does: it's just the validity check that is more restrictive.
750    16. Inserted checks for integer overflows during escape sequence (backslash)
751        processing, and also fixed erroneous offset values for syntax errors during
752        backslash processing.
754    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
755        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
757    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
758        caused an overrun.
760    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
761        something other than just ASCII characters) inside a group that had an
762        unlimited repeat caused a loop at compile time (while checking to see
763        whether the group could match an empty string).
765    20. Debugging a pattern containing \p or \P could cause a crash. For example,
766        [\P{Any}] did so. (Error in the code for printing property names.)
768    21. An orphan \E inside a character class could cause a crash.
770    22. A repeated capturing bracket such as (A)? could cause a wild memory
771        reference during compilation.
773    23. There are several functions in pcre_compile() that scan along a compiled
774        expression for various reasons (e.g. to see if it's fixed length for look
775        behind). There were bugs in these functions when a repeated \p or \P was
776        present in the pattern. These operators have additional parameters compared
777        with \d, etc, and these were not being taken into account when moving along
778        the compiled data. Specifically:
780        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
781            length.
783        (b) An item such as \pL+ within a repeated group could cause crashes or
784            loops.
786        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
787            "reference to non-existent subpattern" error.
789        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
791    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
792        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
794    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
796    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
797        character were causing crashes (broken optimization).
799    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
800        \p or \P) caused a compile-time loop.
802    28. More problems have arisen in unanchored patterns when CRLF is a valid line
803        break. For example, the unstudied pattern [\r\n]A does not match the string
804        "\r\nA" because change 7.0/46 below moves the current point on by two
805        characters after failing to match at the start. However, the pattern \nA
806        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
807        the same is true. There doesn't seem any very clean way out of this, but
808        what I have chosen to do makes the common cases work: PCRE now takes note
809        of whether there can be an explicit match for \r or \n anywhere in the
810        pattern, and if so, 7.0/46 no longer applies. As part of this change,
811        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
812        pattern has explicit CR or LF references.
814    29. Added (*CR) etc for changing newline setting at start of pattern.
817    Version 7.2 19-Jun-07
818  ---------------------  ---------------------
820   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 05-June-07 Line 853  Version 7.2 05-June-07
854      (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
855          reference syntax.          reference syntax.
857      (g) (?| introduces a group in which the numbering of parentheses in each      (g) (?| introduces a group in which the numbering of parentheses in each
858          alternative starts with the same number.          alternative starts with the same number.
860        (h) \h, \H, \v, and \V match horizontal and vertical whitespace.
862   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 58  Version 7.2 05-June-07 Line 873  Version 7.2 05-June-07
873      alternatives. The 1000-alternative test pattern now uses 12 bytes of      alternatives. The 1000-alternative test pattern now uses 12 bytes of
874      workspace instead of running out of the 4096 that are available.      workspace instead of running out of the 4096 that are available.
876    10. Inserted some missing (unsigned int) casts to get rid of compiler warnings.
878    11. Applied patch from Google to remove an optimization that didn't quite work.
879        The report of the bug said:
881          pcrecpp::RE("a*").FullMatch("aaa") matches, while
882          pcrecpp::RE("a*?").FullMatch("aaa") does not, and
883          pcrecpp::RE("a*?\\z").FullMatch("aaa") does again.
885    12. If \p or \P was used in non-UTF-8 mode on a character greater than 127
886        it matched the wrong number of bytes.
889  Version 7.1 24-Apr-07  Version 7.1 24-Apr-07
890  ---------------------  ---------------------

Removed from v.175  
changed lines
  Added in v.430

  ViewVC Help
Powered by ViewVC 1.1.5