ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 269 by ph10, Fri Nov 16 16:22:24 2007 UTC revision 455 by ph10, Sat Sep 26 19:12:32 2009 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 7.5 12-Nov-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 nmatch with a NULL value for pmatch, the value of
101        nmatch is forced to zero.
103    18. RunGrepTest did not have a test for the availability of the -u option of
104        the diff command, as RunTest does. It now checks in the same way as
105        RunTest, and also checks for the -b option.
107    19. If an odd number of negated classes containing just a single character
108        interposed, within parentheses, between a forward reference to a named
109        subpattern and the definition of the subpattern, compilation crashed with
110        an internal error, complaining that it could not find the referenced
111        subpattern. An example of a crashing pattern is /(?&A)(([^m])(?<A>))/.
112        [The bug was that it was starting one character too far in when skipping
113        over the character class, thus treating the ] as data rather than
114        terminating the class. This meant it could skip too much.]
116    20. Added PCRE_NOTEMPTY_ATSTART in order to be able to correctly implement the
117        /g option in pcretest when the pattern contains \K, which makes it possible
118        to have an empty string match not at the start, even when the pattern is
119        anchored. Updated pcretest and pcredemo to use this option.
121    21. If the maximum number of capturing subpatterns in a recursion was greater
122        than the maximum at the outer level, the higher number was returned, but
123        with unset values at the outer level. The correct (outer level) value is
124        now given.
126    22. If (*ACCEPT) appeared inside capturing parentheses, previous releases of
127        PCRE did not set those parentheses (unlike Perl). I have now found a way to
128        make it do so. The string so far is captured, making this feature
129        compatible with Perl.
131    23. The tests have been re-organized, adding tests 11 and 12, to make it
132        possible to check the Perl 5.10 features against Perl 5.10.
134    24. Perl 5.10 allows subroutine calls in lookbehinds, as long as the subroutine
135        pattern matches a fixed length string. PCRE did not allow this; now it
136        does. Neither allows recursion.
138    25. I finally figured out how to implement a request to provide the minimum
139        length of subject string that was needed in order to match a given pattern.
140        (It was back references and recursion that I had previously got hung up
141        on.) This code has now been added to pcre_study(); it finds a lower bound
142        to the length of subject needed. It is not necessarily the greatest lower
143        bound, but using it to avoid searching strings that are too short does give
144        some useful speed-ups. The value is available to calling programs via
145        pcre_fullinfo().
147    26. While implementing 25, I discovered to my embarrassment that pcretest had
148        not been passing the result of pcre_study() to pcre_dfa_exec(), so the
149        study optimizations had never been tested with that matching function.
150        Oops. What is worse, even when it was passed study data, there was a bug in
151        pcre_dfa_exec() that meant it never actually used it. Double oops. There
152        were also very few tests of studied patterns with pcre_dfa_exec().
155    Version 7.9 11-Apr-09
156    ---------------------
158    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
159        (pcretest), all targets were linked against these libraries. This included
160        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
161        libraries. This caused unwanted dependencies to be created. This problem
162        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
163        pcretest is linked with readline.
165    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
166        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
167        moved outside it again, because FALSE and TRUE are already defined in AIX,
168        but BOOL is not.
170    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
171        PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
173    4.  The pcregrep documentation said spaces were inserted as well as colons (or
174        hyphens) following file names and line numbers when outputting matching
175        lines. This is not true; no spaces are inserted. I have also clarified the
176        wording for the --colour (or --color) option.
178    5.  In pcregrep, when --colour was used with -o, the list of matching strings
179        was not coloured; this is different to GNU grep, so I have changed it to be
180        the same.
182    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
183        each matching line was coloured. Now it goes on to look for further matches
184        of any of the test patterns, which is the same behaviour as GNU grep.
186    7.  A pattern that could match an empty string could cause pcregrep to loop; it
187        doesn't make sense to accept an empty string match in pcregrep, so I have
188        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
189        seems to be how GNU grep behaves.
191    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
192        start or after a newline", because the conditional assertion was not being
193        correctly handled. The rule now is that both the assertion and what follows
194        in the first alternative must satisfy the test.
196    9.  If auto-callout was enabled in a pattern with a conditional group whose
197        condition was an assertion, PCRE could crash during matching, both with
198        pcre_exec() and pcre_dfa_exec().
200    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
201        used for matching.
203    11. Unicode property support in character classes was not working for
204        characters (bytes) greater than 127 when not in UTF-8 mode.
206    12. Added the -M command line option to pcretest.
208    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
210    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
212    16. Added comments and documentation about mis-use of no_arg in the C++
213        wrapper.
215    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
216        from Martin Jerabek that uses macro names for all relevant character and
217        string constants.
219    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
220        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
221        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
222        these, but not everybody uses configure.
224    19. A conditional group that had only one branch was not being correctly
225        recognized as an item that could match an empty string. This meant that an
226        enclosing group might also not be so recognized, causing infinite looping
227        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
228        with the subject "ab", where knowledge that the repeated group can match
229        nothing is needed in order to break the loop.
231    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
232        exec(), but without supplying a callout function, matching went wrong.
234    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
235        leak if the size of the offset vector was greater than 30. When the vector
236        is smaller, the saved offsets during recursion go onto a local stack
237        vector, but for larger vectors malloc() is used. It was failing to free
238        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
239        error, in fact).
241    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
242        heapframe that is used only when UTF-8 support is enabled. This caused no
243        problem, but was untidy.
245    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
246        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
247        included within another project.
249    24. Steven Van Ingelgem's patches to add more options to the CMake support,
250        slightly modified by me:
252          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
253              not building pcregrep.
255          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
256              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
258    25. Forward references, both numeric and by name, in patterns that made use of
259        duplicate group numbers, could behave incorrectly or give incorrect errors,
260        because when scanning forward to find the reference group, PCRE was not
261        taking into account the duplicate group numbers. A pattern such as
262        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
264    26. Changed a few more instances of "const unsigned char *" to USPTR, making
265        the feature of a custom pointer more persuasive (as requested by a user).
267    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
268        pcretest.c, inside #ifndefs, because it seems they are sometimes already
269        pre-defined.
271    28. Added support for (*UTF8) at the start of a pattern.
273    29. Arrange for flags added by the "release type" setting in CMake to be shown
274        in the configuration summary.
277    Version 7.8 05-Sep-08
278    ---------------------
280    1.  Replaced UCP searching code with optimized version as implemented for Ad
281        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
282        stage table and inline lookup instead of a function, giving speed ups of 2
283        to 5 times on some simple patterns that I tested. Permission was given to
284        distribute the MultiStage2.py script that generates the tables (it's not in
285        the tarball, but is in the Subversion repository).
287    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
288        scripts.
290    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
291        a group with a zero qualifier. The result of the study could be incorrect,
292        or the function might crash, depending on the pattern.
294    4.  Caseless matching was not working for non-ASCII characters in back
295        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
296        It now works when Unicode Property Support is available.
298    5.  In pcretest, an escape such as \x{de} in the data was always generating
299        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
300        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
301        truncation.
303    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
305    7.  Added two (int) casts to pcregrep when printing the difference of two
306        pointers, in case they are 64-bit values.
308    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
309        test 2 if it fails.
311    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
312        and a #define of that name to empty if it is not externally set. This is to
313        allow users of MSVC to set it if necessary.
315    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
316        the convenience functions in the pcre_get.c source file.
318    11. An option change at the start of a pattern that had top-level alternatives
319        could cause overwriting and/or a crash. This command provoked a crash in
320        some environments:
322          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
324        This potential security problem was recorded as CVE-2008-2371.
326    12. For a pattern where the match had to start at the beginning or immediately
327        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
328        pcre_dfa_exec() could read past the end of the passed subject if there was
329        no match. To help with detecting such bugs (e.g. with valgrind), I modified
330        pcretest so that it places the subject at the end of its malloc-ed buffer.
332    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
333        exec() might read past the end of the data buffer in UTF-8 mode.
335    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
336        the data contained the byte 0x85 as part of a UTF-8 character within its
337        first line. This applied both to normal and DFA matching.
339    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
340        /^[^d]*?$/8 failed to match "abc".
342    16. Added a missing copyright notice to pcrecpp_internal.h.
344    17. Make it more clear in the documentation that values returned from
345        pcre_exec() in ovector are byte offsets, not character counts.
347    18. Tidied a few places to stop certain compilers from issuing warnings.
349    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
350        supplied by Stefan Weber. I made a further small update for 7.8 because
351        there is a change of source arrangements: the pcre_searchfuncs.c module is
352        replaced by pcre_ucd.c.
355    Version 7.7 07-May-08
356    ---------------------
358    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
359        a string to a long long, pretend we don't even have a long long." This is
360        done by checking for the strtoq, strtoll, and _strtoi64 functions.
362    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
363        pre-7.6 versions, which defined a global no_arg variable instead of putting
364        it in the RE class. (See also #8 below.)
366    3.  Remove a line of dead code, identified by coverity and reported by Nuno
367        Lopes.
369    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
371        (1) The include/exclude patterns were being applied to the whole pathnames
372            of files, instead of just to the final components.
374        (2) If there was more than one level of directory, the subdirectories were
375            skipped unless they satisfied the include/exclude conditions. This is
376            inconsistent with GNU grep (and could even be seen as contrary to the
377            pcregrep specification - which I improved to make it absolutely clear).
378            The action now is always to scan all levels of directory, and just
379            apply the include/exclude patterns to regular files.
381    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
382        --exclude_dir in the tests to avoid scanning .svn directories.
384    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
385        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
386        doesn't support NULs in patterns.
388    7.  Added some missing "const"s to declarations of static tables in
389        pcre_compile.c and pcre_dfa_exec.c.
391    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
392        caused by fix #2  above. (Subsequently also a second patch to fix the
393        first patch. And a third patch - this was a messy problem.)
395    9.  Applied Craig's patch to remove the use of push_back().
397    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
398        matching function regexec().
400    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
401        which, however, unlike Perl's \g{...}, are subroutine calls, not back
402        references. PCRE supports relative numbers with this syntax (I don't think
403        Oniguruma does).
405    12. Previously, a group with a zero repeat such as (...){0} was completely
406        omitted from the compiled regex. However, this means that if the group
407        was called as a subroutine from elsewhere in the pattern, things went wrong
408        (an internal error was given). Such groups are now left in the compiled
409        pattern, with a new opcode that causes them to be skipped at execution
410        time.
412    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
413        to the way PCRE behaves:
415        (a) A lone ] character is dis-allowed (Perl treats it as data).
417        (b) A back reference to an unmatched subpattern matches an empty string
418            (Perl fails the current match path).
420        (c) A data ] in a character class must be notated as \] because if the
421            first data character in a class is ], it defines an empty class. (In
422            Perl it is not possible to have an empty class.) The empty class []
423            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
424            The negative empty class [^] matches any one character, independently
425            of the DOTALL setting.
427    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
428        non-existent subpattern following a character class starting with ']' and
429        containing () gave an internal compiling error instead of "reference to
430        non-existent subpattern". Fortunately, when the pattern did exist, the
431        compiled code was correct. (When scanning forwards to check for the
432        existencd of the subpattern, it was treating the data ']' as terminating
433        the class, so got the count wrong. When actually compiling, the reference
434        was subsequently set up correctly.)
436    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
437        it was being rejected as not supported by pcre_dfa_exec(), even though
438        other assertions are supported. I have made pcre_dfa_exec() support
439        (*FAIL).
441    16. The implementation of 13c above involved the invention of a new opcode,
442        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
443        cannot be changed at match time, I realized I could make a small
444        improvement to matching performance by compiling OP_ALLANY instead of
445        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
446        on the OP_ANY path.
448    17. Compiling pcretest on Windows with readline support failed without the
449        following two fixes: (1) Make the unistd.h include conditional on
450        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
452    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
453        ncurses library to be included for pcretest when ReadLine support is
454        requested, but also to allow for it to be overridden. This patch came from
455        Daniel Bergström.
457    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
458        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
459        any errors with the current Unicode tables. Thanks to Peter Kankowski for
460        spotting this.
463    Version 7.6 28-Jan-08
464    ---------------------
466    1.  A character class containing a very large number of characters with
467        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
468        overflow.
470    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
471        HAVE_LONG_LONG is not defined.
473    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
474        bring them up to date and include new features. This patch includes:
476        - Fixed PH's badly added libz and libbz2 support.
477        - Fixed a problem with static linking.
478        - Added pcredemo. [But later removed - see 7 below.]
479        - Fixed dftables problem and added an option.
480        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
481            HAVE_LONG_LONG.
482        - Added readline support for pcretest.
483        - Added an listing of the option settings after cmake has run.
485    4.  A user submitted a patch to Makefile that makes it easy to create
486        "pcre.dll" under mingw when using Configure/Make. I added stuff to
487        Makefile.am that cause it to include this special target, without
488        affecting anything else. Note that the same mingw target plus all
489        the other distribution libraries and programs are now supported
490        when configuring with CMake (see 6 below) instead of with
491        Configure/Make.
493    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
494        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
495        exported in the Windows port". It has not yet been confirmed that the patch
496        solves the problem, but it does no harm.
498    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
499        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
500        with CMake, and also correct the comment about stack recursion.
502    7.  Remove the automatic building of pcredemo from the ./configure system and
503        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
504        of a program that users should build themselves after PCRE is installed, so
505        building it automatically is not really right. What is more, it gave
506        trouble in some build environments.
508    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
511    Version 7.5 10-Jan-08
512  ---------------------  ---------------------
514  1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'  1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
515      values in parens when parsing an RE using the C++ wrapper."      values in parens when parsing an RE using the C++ wrapper."
517  2.  Negative specials like \S did not work in character classes in UTF-8 mode.  2.  Negative specials like \S did not work in character classes in UTF-8 mode.
518      Characters greater than 255 were excluded from the class instead of being      Characters greater than 255 were excluded from the class instead of being
519      included.      included.
521  3.  The same bug as (2) above applied to negated POSIX classes such as  3.  The same bug as (2) above applied to negated POSIX classes such as
522      [:^space:].      [:^space:].
524  4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it  4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
525      defined or documented. It seems to have been a typo for PCRE_STATIC, so      defined or documented. It seems to have been a typo for PCRE_STATIC, so
526      I have changed it.      I have changed it.
528  5.  The construct (?&) was not diagnosed as a syntax error (it referenced the  5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
529      first named subpattern) and a construct such as (?&a) would reference the      first named subpattern) and a construct such as (?&a) would reference the
530      first named subpattern whose name started with "a" (in other words, the      first named subpattern whose name started with "a" (in other words, the
531      length check was missing).      length check was missing). Both these problems are fixed. "Subpattern name
532        expected" is now given for (?&) (a zero-length name), and this patch also
533        makes it give the same error for \k'' (previously it complained that that
534        was a reference to a non-existent subpattern).
536  6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;  6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
537      this is right because (?- can be followed by option settings as well as by      this is right because (?- can be followed by option settings as well as by
538      digits. I have, however, made the messages clearer.      digits. I have, however, made the messages clearer.
540    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
541        than the number used in the conditional) now cause a compile-time error.
542        This is actually not compatible with Perl, which accepts such patterns, but
543        treats the conditional as always being FALSE (as PCRE used to), but it
544        seems to me that giving a diagnostic is better.
546    8.  Change "alphameric" to the more common word "alphanumeric" in comments
547        and messages.
549    9.  Fix two occurrences of "backslash" in comments that should have been
550        "backspace".
552    10. Remove two redundant lines of code that can never be obeyed (their function
553        was moved elsewhere).
555    11. The program that makes PCRE's Unicode character property table had a bug
556        which caused it to generate incorrect table entries for sequences of
557        characters that have the same character type, but are in different scripts.
558        It amalgamated them into a single range, with the script of the first of
559        them. In other words, some characters were in the wrong script. There were
560        thirteen such cases, affecting characters in the following ranges:
562          U+002b0 - U+002c1
563          U+0060c - U+0060d
564          U+0061e - U+00612
565          U+0064b - U+0065e
566          U+0074d - U+0076d
567          U+01800 - U+01805
568          U+01d00 - U+01d77
569          U+01d9b - U+01dbf
570          U+0200b - U+0200f
571          U+030fc - U+030fe
572          U+03260 - U+0327f
573          U+0fb46 - U+0fbb1
574          U+10450 - U+1049d
576    12. The -o option (show only the matching part of a line) for pcregrep was not
577        compatible with GNU grep in that, if there was more than one match in a
578        line, it showed only the first of them. It now behaves in the same way as
579        GNU grep.
581    13. If the -o and -v options were combined for pcregrep, it printed a blank
582        line for every non-matching line. GNU grep prints nothing, and pcregrep now
583        does the same. The return code can be used to tell if there were any
584        non-matching lines.
586    14. Added --file-offsets and --line-offsets to pcregrep.
588    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
589        infinitely looping recursion. The bug was that positive lookaheads were not
590        being skipped when checking for a possible empty match (negative lookaheads
591        and both kinds of lookbehind were skipped).
593    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
594        inclusion of <windows.h> to before rather than after the definition of
595        INVALID_FILE_ATTRIBUTES (patch from David Byron).
597    17. Specifying a possessive quantifier with a specific limit for a Unicode
598        character property caused pcre_compile() to compile bad code, which led at
599        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
600        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
601        caused the error; without that there was no problem.
603    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
605    19. Added --enable-pcretest-libreadline.
607    20. In pcrecpp.cc, the variable 'count' was incremented twice in
608        RE::GlobalReplace(). As a result, the number of replacements returned was
609        double what it should be. I removed one of the increments, but Craig sent a
610        later patch that removed the other one (the right fix) and added unit tests
611        that check the return values (which was not done before).
613    21. Several CMake things:
615        (1) Arranged that, when cmake is used on Unix, the libraries end up with
616            the names libpcre and libpcreposix, not just pcre and pcreposix.
618        (2) The above change means that pcretest and pcregrep are now correctly
619            linked with the newly-built libraries, not previously installed ones.
623    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
624        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
625        UTF-8 newline character). The key issue is that the pattern starts .*;
626        this means that the match must be either at the beginning, or after a
627        newline. The bug was in the code for advancing after a failed match and
628        checking that the new position followed a newline. It was not taking
629        account of UTF-8 characters correctly.
631    23. PCRE was behaving differently from Perl in the way it recognized POSIX
632        character classes. PCRE was not treating the sequence [:...:] as a
633        character class unless the ... were all letters. Perl, however, seems to
634        allow any characters between [: and :], though of course it rejects as
635        unknown any "names" that contain non-letters, because all the known class
636        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
637        for example, whereas PCRE did not - it did not recognize a POSIX character
638        class. This seemed a bit dangerous, so the code has been changed to be
639        closer to Perl. The behaviour is not identical to Perl, because PCRE will
640        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
641        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
642        Perl does, and where it didn't before.
644    24. Rewrite so as to remove the single use of %n from pcregrep because in some
645        Windows environments %n is disabled by default.
648  Version 7.4 21-Sep-07  Version 7.4 21-Sep-07
649  ---------------------  ---------------------

Removed from v.269  
changed lines
  Added in v.455

  ViewVC Help
Powered by ViewVC 1.1.5