ViewVC logotype

Diff of /code/trunk/ChangeLog

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

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

Removed from v.223  
changed lines
  Added in v.433

  ViewVC Help
Powered by ViewVC 1.1.5