ViewVC logotype

Diff of /code/trunk/ChangeLog

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

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

Removed from v.192  
changed lines
  Added in v.435

  ViewVC Help
Powered by ViewVC 1.1.5