ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 221 by ph10, Fri Aug 17 09:25:08 2007 UTC revision 442 by ph10, Fri Sep 11 10:21:02 2009 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 7.3 17-Aug-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.
122    Version 7.9 11-Apr-09
123    ---------------------
125    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
126        (pcretest), all targets were linked against these libraries. This included
127        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
128        libraries. This caused unwanted dependencies to be created. This problem
129        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
130        pcretest is linked with readline.
132    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
133        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
134        moved outside it again, because FALSE and TRUE are already defined in AIX,
135        but BOOL is not.
137    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
138        PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
140    4.  The pcregrep documentation said spaces were inserted as well as colons (or
141        hyphens) following file names and line numbers when outputting matching
142        lines. This is not true; no spaces are inserted. I have also clarified the
143        wording for the --colour (or --color) option.
145    5.  In pcregrep, when --colour was used with -o, the list of matching strings
146        was not coloured; this is different to GNU grep, so I have changed it to be
147        the same.
149    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
150        each matching line was coloured. Now it goes on to look for further matches
151        of any of the test patterns, which is the same behaviour as GNU grep.
153    7.  A pattern that could match an empty string could cause pcregrep to loop; it
154        doesn't make sense to accept an empty string match in pcregrep, so I have
155        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
156        seems to be how GNU grep behaves.
158    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
159        start or after a newline", because the conditional assertion was not being
160        correctly handled. The rule now is that both the assertion and what follows
161        in the first alternative must satisfy the test.
163    9.  If auto-callout was enabled in a pattern with a conditional group whose
164        condition was an assertion, PCRE could crash during matching, both with
165        pcre_exec() and pcre_dfa_exec().
167    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
168        used for matching.
170    11. Unicode property support in character classes was not working for
171        characters (bytes) greater than 127 when not in UTF-8 mode.
173    12. Added the -M command line option to pcretest.
175    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
177    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
179    16. Added comments and documentation about mis-use of no_arg in the C++
180        wrapper.
182    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
183        from Martin Jerabek that uses macro names for all relevant character and
184        string constants.
186    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
187        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
188        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
189        these, but not everybody uses configure.
191    19. A conditional group that had only one branch was not being correctly
192        recognized as an item that could match an empty string. This meant that an
193        enclosing group might also not be so recognized, causing infinite looping
194        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
195        with the subject "ab", where knowledge that the repeated group can match
196        nothing is needed in order to break the loop.
198    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
199        exec(), but without supplying a callout function, matching went wrong.
201    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
202        leak if the size of the offset vector was greater than 30. When the vector
203        is smaller, the saved offsets during recursion go onto a local stack
204        vector, but for larger vectors malloc() is used. It was failing to free
205        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
206        error, in fact).
208    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
209        heapframe that is used only when UTF-8 support is enabled. This caused no
210        problem, but was untidy.
212    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
213        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
214        included within another project.
216    24. Steven Van Ingelgem's patches to add more options to the CMake support,
217        slightly modified by me:
219          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
220              not building pcregrep.
222          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
223              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
225    25. Forward references, both numeric and by name, in patterns that made use of
226        duplicate group numbers, could behave incorrectly or give incorrect errors,
227        because when scanning forward to find the reference group, PCRE was not
228        taking into account the duplicate group numbers. A pattern such as
229        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
231    26. Changed a few more instances of "const unsigned char *" to USPTR, making
232        the feature of a custom pointer more persuasive (as requested by a user).
234    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
235        pcretest.c, inside #ifndefs, because it seems they are sometimes already
236        pre-defined.
238    28. Added support for (*UTF8) at the start of a pattern.
240    29. Arrange for flags added by the "release type" setting in CMake to be shown
241        in the configuration summary.
244    Version 7.8 05-Sep-08
245    ---------------------
247    1.  Replaced UCP searching code with optimized version as implemented for Ad
248        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
249        stage table and inline lookup instead of a function, giving speed ups of 2
250        to 5 times on some simple patterns that I tested. Permission was given to
251        distribute the MultiStage2.py script that generates the tables (it's not in
252        the tarball, but is in the Subversion repository).
254    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
255        scripts.
257    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
258        a group with a zero qualifier. The result of the study could be incorrect,
259        or the function might crash, depending on the pattern.
261    4.  Caseless matching was not working for non-ASCII characters in back
262        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
263        It now works when Unicode Property Support is available.
265    5.  In pcretest, an escape such as \x{de} in the data was always generating
266        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
267        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
268        truncation.
270    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
272    7.  Added two (int) casts to pcregrep when printing the difference of two
273        pointers, in case they are 64-bit values.
275    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
276        test 2 if it fails.
278    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
279        and a #define of that name to empty if it is not externally set. This is to
280        allow users of MSVC to set it if necessary.
282    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
283        the convenience functions in the pcre_get.c source file.
285    11. An option change at the start of a pattern that had top-level alternatives
286        could cause overwriting and/or a crash. This command provoked a crash in
287        some environments:
289          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
291        This potential security problem was recorded as CVE-2008-2371.
293    12. For a pattern where the match had to start at the beginning or immediately
294        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
295        pcre_dfa_exec() could read past the end of the passed subject if there was
296        no match. To help with detecting such bugs (e.g. with valgrind), I modified
297        pcretest so that it places the subject at the end of its malloc-ed buffer.
299    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
300        exec() might read past the end of the data buffer in UTF-8 mode.
302    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
303        the data contained the byte 0x85 as part of a UTF-8 character within its
304        first line. This applied both to normal and DFA matching.
306    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
307        /^[^d]*?$/8 failed to match "abc".
309    16. Added a missing copyright notice to pcrecpp_internal.h.
311    17. Make it more clear in the documentation that values returned from
312        pcre_exec() in ovector are byte offsets, not character counts.
314    18. Tidied a few places to stop certain compilers from issuing warnings.
316    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
317        supplied by Stefan Weber. I made a further small update for 7.8 because
318        there is a change of source arrangements: the pcre_searchfuncs.c module is
319        replaced by pcre_ucd.c.
322    Version 7.7 07-May-08
323    ---------------------
325    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
326        a string to a long long, pretend we don't even have a long long." This is
327        done by checking for the strtoq, strtoll, and _strtoi64 functions.
329    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
330        pre-7.6 versions, which defined a global no_arg variable instead of putting
331        it in the RE class. (See also #8 below.)
333    3.  Remove a line of dead code, identified by coverity and reported by Nuno
334        Lopes.
336    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
338        (1) The include/exclude patterns were being applied to the whole pathnames
339            of files, instead of just to the final components.
341        (2) If there was more than one level of directory, the subdirectories were
342            skipped unless they satisfied the include/exclude conditions. This is
343            inconsistent with GNU grep (and could even be seen as contrary to the
344            pcregrep specification - which I improved to make it absolutely clear).
345            The action now is always to scan all levels of directory, and just
346            apply the include/exclude patterns to regular files.
348    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
349        --exclude_dir in the tests to avoid scanning .svn directories.
351    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
352        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
353        doesn't support NULs in patterns.
355    7.  Added some missing "const"s to declarations of static tables in
356        pcre_compile.c and pcre_dfa_exec.c.
358    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
359        caused by fix #2  above. (Subsequently also a second patch to fix the
360        first patch. And a third patch - this was a messy problem.)
362    9.  Applied Craig's patch to remove the use of push_back().
364    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
365        matching function regexec().
367    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
368        which, however, unlike Perl's \g{...}, are subroutine calls, not back
369        references. PCRE supports relative numbers with this syntax (I don't think
370        Oniguruma does).
372    12. Previously, a group with a zero repeat such as (...){0} was completely
373        omitted from the compiled regex. However, this means that if the group
374        was called as a subroutine from elsewhere in the pattern, things went wrong
375        (an internal error was given). Such groups are now left in the compiled
376        pattern, with a new opcode that causes them to be skipped at execution
377        time.
379    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
380        to the way PCRE behaves:
382        (a) A lone ] character is dis-allowed (Perl treats it as data).
384        (b) A back reference to an unmatched subpattern matches an empty string
385            (Perl fails the current match path).
387        (c) A data ] in a character class must be notated as \] because if the
388            first data character in a class is ], it defines an empty class. (In
389            Perl it is not possible to have an empty class.) The empty class []
390            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
391            The negative empty class [^] matches any one character, independently
392            of the DOTALL setting.
394    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
395        non-existent subpattern following a character class starting with ']' and
396        containing () gave an internal compiling error instead of "reference to
397        non-existent subpattern". Fortunately, when the pattern did exist, the
398        compiled code was correct. (When scanning forwards to check for the
399        existencd of the subpattern, it was treating the data ']' as terminating
400        the class, so got the count wrong. When actually compiling, the reference
401        was subsequently set up correctly.)
403    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
404        it was being rejected as not supported by pcre_dfa_exec(), even though
405        other assertions are supported. I have made pcre_dfa_exec() support
406        (*FAIL).
408    16. The implementation of 13c above involved the invention of a new opcode,
409        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
410        cannot be changed at match time, I realized I could make a small
411        improvement to matching performance by compiling OP_ALLANY instead of
412        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
413        on the OP_ANY path.
415    17. Compiling pcretest on Windows with readline support failed without the
416        following two fixes: (1) Make the unistd.h include conditional on
417        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
419    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
420        ncurses library to be included for pcretest when ReadLine support is
421        requested, but also to allow for it to be overridden. This patch came from
422        Daniel Bergström.
424    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
425        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
426        any errors with the current Unicode tables. Thanks to Peter Kankowski for
427        spotting this.
430    Version 7.6 28-Jan-08
431    ---------------------
433    1.  A character class containing a very large number of characters with
434        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
435        overflow.
437    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
438        HAVE_LONG_LONG is not defined.
440    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
441        bring them up to date and include new features. This patch includes:
443        - Fixed PH's badly added libz and libbz2 support.
444        - Fixed a problem with static linking.
445        - Added pcredemo. [But later removed - see 7 below.]
446        - Fixed dftables problem and added an option.
447        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
448            HAVE_LONG_LONG.
449        - Added readline support for pcretest.
450        - Added an listing of the option settings after cmake has run.
452    4.  A user submitted a patch to Makefile that makes it easy to create
453        "pcre.dll" under mingw when using Configure/Make. I added stuff to
454        Makefile.am that cause it to include this special target, without
455        affecting anything else. Note that the same mingw target plus all
456        the other distribution libraries and programs are now supported
457        when configuring with CMake (see 6 below) instead of with
458        Configure/Make.
460    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
461        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
462        exported in the Windows port". It has not yet been confirmed that the patch
463        solves the problem, but it does no harm.
465    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
466        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
467        with CMake, and also correct the comment about stack recursion.
469    7.  Remove the automatic building of pcredemo from the ./configure system and
470        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
471        of a program that users should build themselves after PCRE is installed, so
472        building it automatically is not really right. What is more, it gave
473        trouble in some build environments.
475    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
478    Version 7.5 10-Jan-08
479    ---------------------
481    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
482        values in parens when parsing an RE using the C++ wrapper."
484    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
485        Characters greater than 255 were excluded from the class instead of being
486        included.
488    3.  The same bug as (2) above applied to negated POSIX classes such as
489        [:^space:].
491    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
492        defined or documented. It seems to have been a typo for PCRE_STATIC, so
493        I have changed it.
495    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
496        first named subpattern) and a construct such as (?&a) would reference the
497        first named subpattern whose name started with "a" (in other words, the
498        length check was missing). Both these problems are fixed. "Subpattern name
499        expected" is now given for (?&) (a zero-length name), and this patch also
500        makes it give the same error for \k'' (previously it complained that that
501        was a reference to a non-existent subpattern).
503    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
504        this is right because (?- can be followed by option settings as well as by
505        digits. I have, however, made the messages clearer.
507    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
508        than the number used in the conditional) now cause a compile-time error.
509        This is actually not compatible with Perl, which accepts such patterns, but
510        treats the conditional as always being FALSE (as PCRE used to), but it
511        seems to me that giving a diagnostic is better.
513    8.  Change "alphameric" to the more common word "alphanumeric" in comments
514        and messages.
516    9.  Fix two occurrences of "backslash" in comments that should have been
517        "backspace".
519    10. Remove two redundant lines of code that can never be obeyed (their function
520        was moved elsewhere).
522    11. The program that makes PCRE's Unicode character property table had a bug
523        which caused it to generate incorrect table entries for sequences of
524        characters that have the same character type, but are in different scripts.
525        It amalgamated them into a single range, with the script of the first of
526        them. In other words, some characters were in the wrong script. There were
527        thirteen such cases, affecting characters in the following ranges:
529          U+002b0 - U+002c1
530          U+0060c - U+0060d
531          U+0061e - U+00612
532          U+0064b - U+0065e
533          U+0074d - U+0076d
534          U+01800 - U+01805
535          U+01d00 - U+01d77
536          U+01d9b - U+01dbf
537          U+0200b - U+0200f
538          U+030fc - U+030fe
539          U+03260 - U+0327f
540          U+0fb46 - U+0fbb1
541          U+10450 - U+1049d
543    12. The -o option (show only the matching part of a line) for pcregrep was not
544        compatible with GNU grep in that, if there was more than one match in a
545        line, it showed only the first of them. It now behaves in the same way as
546        GNU grep.
548    13. If the -o and -v options were combined for pcregrep, it printed a blank
549        line for every non-matching line. GNU grep prints nothing, and pcregrep now
550        does the same. The return code can be used to tell if there were any
551        non-matching lines.
553    14. Added --file-offsets and --line-offsets to pcregrep.
555    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
556        infinitely looping recursion. The bug was that positive lookaheads were not
557        being skipped when checking for a possible empty match (negative lookaheads
558        and both kinds of lookbehind were skipped).
560    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
561        inclusion of <windows.h> to before rather than after the definition of
562        INVALID_FILE_ATTRIBUTES (patch from David Byron).
564    17. Specifying a possessive quantifier with a specific limit for a Unicode
565        character property caused pcre_compile() to compile bad code, which led at
566        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
567        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
568        caused the error; without that there was no problem.
570    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
572    19. Added --enable-pcretest-libreadline.
574    20. In pcrecpp.cc, the variable 'count' was incremented twice in
575        RE::GlobalReplace(). As a result, the number of replacements returned was
576        double what it should be. I removed one of the increments, but Craig sent a
577        later patch that removed the other one (the right fix) and added unit tests
578        that check the return values (which was not done before).
580    21. Several CMake things:
582        (1) Arranged that, when cmake is used on Unix, the libraries end up with
583            the names libpcre and libpcreposix, not just pcre and pcreposix.
585        (2) The above change means that pcretest and pcregrep are now correctly
586            linked with the newly-built libraries, not previously installed ones.
590    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
591        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
592        UTF-8 newline character). The key issue is that the pattern starts .*;
593        this means that the match must be either at the beginning, or after a
594        newline. The bug was in the code for advancing after a failed match and
595        checking that the new position followed a newline. It was not taking
596        account of UTF-8 characters correctly.
598    23. PCRE was behaving differently from Perl in the way it recognized POSIX
599        character classes. PCRE was not treating the sequence [:...:] as a
600        character class unless the ... were all letters. Perl, however, seems to
601        allow any characters between [: and :], though of course it rejects as
602        unknown any "names" that contain non-letters, because all the known class
603        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
604        for example, whereas PCRE did not - it did not recognize a POSIX character
605        class. This seemed a bit dangerous, so the code has been changed to be
606        closer to Perl. The behaviour is not identical to Perl, because PCRE will
607        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
608        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
609        Perl does, and where it didn't before.
611    24. Rewrite so as to remove the single use of %n from pcregrep because in some
612        Windows environments %n is disabled by default.
615    Version 7.4 21-Sep-07
616    ---------------------
618    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
619        means that a class such as [\s] counted as "explicit reference to CR or
620        LF". That isn't really right - the whole point of the change was to try to
621        help when there was an actual mention of one of the two characters. So now
622        the change happens only if \r or \n (or a literal CR or LF) character is
623        encountered.
625    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
626        of both had grown to the point where there were only 3 bits left.
627        Fortunately, there was spare space in the data structure, and so I have
628        moved the internal flags into a new 16-bit field to free up more option
629        bits.
631    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
632        but did not set the internal JCHANGED flag - either of these is enough to
633        control the way the "get" function works - but the PCRE_INFO_JCHANGED
634        facility is supposed to tell if (?J) was ever used, so now (?J) at the
635        start sets both bits.
637    4.  Added options (at build time, compile time, exec time) to change \R from
638        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
640    5.  doc/pcresyntax.html was missing from the distribution.
642    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
643        compatibility, even though it is no longer used.
645    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
646        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
647        windows.h file is present (where different names are used). [This was
648        reversed later after testing - see 16 below.]
650    8.  Changed all #include <config.h> to #include "config.h". There were also
651        some further <pcre.h> cases that I changed to "pcre.h".
653    9.  When pcregrep was used with the --colour option, it missed the line ending
654        sequence off the lines that it output.
656    10. It was pointed out to me that arrays of string pointers cause lots of
657        relocations when a shared library is dynamically loaded. A technique of
658        using a single long string with a table of offsets can drastically reduce
659        these. I have refactored PCRE in four places to do this. The result is
660        dramatic:
662          Originally:                          290
663          After changing UCP table:            187
664          After changing error message table:   43
665          After changing table of "verbs"       36
666          After changing table of Posix names   22
668        Thanks to the folks working on Gregex for glib for this insight.
670    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
671        unicode-properties was also set.
673    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
675    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
676        checked only for CRLF.
678    14. Added casts to pcretest.c to avoid compiler warnings.
680    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
682    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
683        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
684        entirely. This removes changes made in 7 above.
686    17. The CMake files have been updated, and there is now more information about
687        building with CMake in the NON-UNIX-USE document.
690    Version 7.3 28-Aug-07
691  ---------------------  ---------------------
693   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 143  Version 7.3 17-Aug-07 Line 829  Version 7.3 17-Aug-07
829  24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte  24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
830      characters were involved (for example /\S{2}/8g with "A\x{a3}BC").      characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
832    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
834    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
835        character were causing crashes (broken optimization).
837    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
838        \p or \P) caused a compile-time loop.
840    28. More problems have arisen in unanchored patterns when CRLF is a valid line
841        break. For example, the unstudied pattern [\r\n]A does not match the string
842        "\r\nA" because change 7.0/46 below moves the current point on by two
843        characters after failing to match at the start. However, the pattern \nA
844        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
845        the same is true. There doesn't seem any very clean way out of this, but
846        what I have chosen to do makes the common cases work: PCRE now takes note
847        of whether there can be an explicit match for \r or \n anywhere in the
848        pattern, and if so, 7.0/46 no longer applies. As part of this change,
849        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
850        pattern has explicit CR or LF references.
852    29. Added (*CR) etc for changing newline setting at start of pattern.
855  Version 7.2 19-Jun-07  Version 7.2 19-Jun-07
856  ---------------------  ---------------------

Removed from v.221  
changed lines
  Added in v.442

  ViewVC Help
Powered by ViewVC 1.1.5