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 409 by ph10, Sat Mar 28 17:10:56 2009 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 7.3 17-Aug-07  Version 7.9 xx-xxx-09
5    ---------------------
7    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
8        (pcretest), all targets were linked against these libraries. This included
9        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
10        libraries. This caused unwanted dependencies to be created. This problem
11        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
12        pcretest is linked with readline.
14    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
15        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
16        moved outside it again, because FALSE and TRUE are already defined in AIX,
17        but BOOL is not.
19    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
20        PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
22    4.  The pcregrep documentation said spaces were inserted as well as colons (or
23        hyphens) following file names and line numbers when outputting matching
24        lines. This is not true; no spaces are inserted. I have also clarified the
25        wording for the --colour (or --color) option.
27    5.  In pcregrep, when --colour was used with -o, the list of matching strings
28        was not coloured; this is different to GNU grep, so I have changed it to be
29        the same.
31    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
32        each matching line was coloured. Now it goes on to look for further matches
33        of any of the test patterns, which is the same behaviour as GNU grep.
35    7.  A pattern that could match an empty string could cause pcregrep to loop; it
36        doesn't make sense to accept an empty string match in pcregrep, so I have
37        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
38        seems to be how GNU grep behaves.
40    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
41        start or after a newline", because the conditional assertion was not being
42        correctly handled. The rule now is that both the assertion and what follows
43        in the first alternative must satisfy the test.
45    9.  If auto-callout was enabled in a pattern with a conditional group whose
46        condition was an assertion, PCRE could crash during matching, both with
47        pcre_exec() and pcre_dfa_exec().
49    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
50        used for matching.
52    11. Unicode property support in character classes was not working for
53        characters (bytes) greater than 127 when not in UTF-8 mode.
55    12. Added the -M command line option to pcretest.
57    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
59    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
61    16. Added comments and documentation about mis-use of no_arg in the C++
62        wrapper.
64    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
65        from Martin Jerabek that uses macro names for all relevant character and
66        string constants.
68    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
69        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
70        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
71        these, but not everybody uses configure.
73    19. A conditional group that had only one branch was not being correctly
74        recognized as an item that could match an empty string. This meant that an
75        enclosing group might also not be so recognized, causing infinite looping
76        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
77        with the subject "ab", where knowledge that the repeated group can match
78        nothing is needed in order to break the loop.
80    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
81        exec(), but without supplying a callout function, matching went wrong.
83    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
84        leak if the size of the offset vector was greater than 30. When the vector
85        is smaller, the saved offsets during recursion go onto a local stack
86        vector, but for larger vectors malloc() is used. It was failing to free
87        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
88        error, in fact).
90    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
91        heapframe that is used only when UTF-8 support is enabled. This caused no
92        problem, but was untidy.
94    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
95        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
96        included within another project.
98    24. Steven Van Ingelgem's patches to add more options to the CMake support,
99        slightly modified by me:
101          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
102              not building pcregrep.
104          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
105              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
107    25. Forward references, both numeric and by name, in patterns that made use of
108        duplicate group numbers, could behave incorrectly or give incorrect errors,
109        because when scanning forward to find the reference group, PCRE was not
110        taking into account the duplicate group numbers. A pattern such as
111        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
113    26. Changed a few more instances of "const unsigned char *" to USPTR, making
114        the feature of a custom pointer more persuasive (as requested by a user).
118    Version 7.8 05-Sep-08
119    ---------------------
121    1.  Replaced UCP searching code with optimized version as implemented for Ad
122        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
123        stage table and inline lookup instead of a function, giving speed ups of 2
124        to 5 times on some simple patterns that I tested. Permission was given to
125        distribute the MultiStage2.py script that generates the tables (it's not in
126        the tarball, but is in the Subversion repository).
128    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
129        scripts.
131    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
132        a group with a zero qualifier. The result of the study could be incorrect,
133        or the function might crash, depending on the pattern.
135    4.  Caseless matching was not working for non-ASCII characters in back
136        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
137        It now works when Unicode Property Support is available.
139    5.  In pcretest, an escape such as \x{de} in the data was always generating
140        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
141        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
142        truncation.
144    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
146    7.  Added two (int) casts to pcregrep when printing the difference of two
147        pointers, in case they are 64-bit values.
149    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
150        test 2 if it fails.
152    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
153        and a #define of that name to empty if it is not externally set. This is to
154        allow users of MSVC to set it if necessary.
156    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
157        the convenience functions in the pcre_get.c source file.
159    11. An option change at the start of a pattern that had top-level alternatives
160        could cause overwriting and/or a crash. This command provoked a crash in
161        some environments:
163          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
165        This potential security problem was recorded as CVE-2008-2371.
167    12. For a pattern where the match had to start at the beginning or immediately
168        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
169        pcre_dfa_exec() could read past the end of the passed subject if there was
170        no match. To help with detecting such bugs (e.g. with valgrind), I modified
171        pcretest so that it places the subject at the end of its malloc-ed buffer.
173    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
174        exec() might read past the end of the data buffer in UTF-8 mode.
176    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
177        the data contained the byte 0x85 as part of a UTF-8 character within its
178        first line. This applied both to normal and DFA matching.
180    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
181        /^[^d]*?$/8 failed to match "abc".
183    16. Added a missing copyright notice to pcrecpp_internal.h.
185    17. Make it more clear in the documentation that values returned from
186        pcre_exec() in ovector are byte offsets, not character counts.
188    18. Tidied a few places to stop certain compilers from issuing warnings.
190    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
191        supplied by Stefan Weber. I made a further small update for 7.8 because
192        there is a change of source arrangements: the pcre_searchfuncs.c module is
193        replaced by pcre_ucd.c.
196    Version 7.7 07-May-08
197    ---------------------
199    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
200        a string to a long long, pretend we don't even have a long long." This is
201        done by checking for the strtoq, strtoll, and _strtoi64 functions.
203    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
204        pre-7.6 versions, which defined a global no_arg variable instead of putting
205        it in the RE class. (See also #8 below.)
207    3.  Remove a line of dead code, identified by coverity and reported by Nuno
208        Lopes.
210    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
212        (1) The include/exclude patterns were being applied to the whole pathnames
213            of files, instead of just to the final components.
215        (2) If there was more than one level of directory, the subdirectories were
216            skipped unless they satisfied the include/exclude conditions. This is
217            inconsistent with GNU grep (and could even be seen as contrary to the
218            pcregrep specification - which I improved to make it absolutely clear).
219            The action now is always to scan all levels of directory, and just
220            apply the include/exclude patterns to regular files.
222    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
223        --exclude_dir in the tests to avoid scanning .svn directories.
225    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
226        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
227        doesn't support NULs in patterns.
229    7.  Added some missing "const"s to declarations of static tables in
230        pcre_compile.c and pcre_dfa_exec.c.
232    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
233        caused by fix #2  above. (Subsequently also a second patch to fix the
234        first patch. And a third patch - this was a messy problem.)
236    9.  Applied Craig's patch to remove the use of push_back().
238    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
239        matching function regexec().
241    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
242        which, however, unlike Perl's \g{...}, are subroutine calls, not back
243        references. PCRE supports relative numbers with this syntax (I don't think
244        Oniguruma does).
246    12. Previously, a group with a zero repeat such as (...){0} was completely
247        omitted from the compiled regex. However, this means that if the group
248        was called as a subroutine from elsewhere in the pattern, things went wrong
249        (an internal error was given). Such groups are now left in the compiled
250        pattern, with a new opcode that causes them to be skipped at execution
251        time.
253    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
254        to the way PCRE behaves:
256        (a) A lone ] character is dis-allowed (Perl treats it as data).
258        (b) A back reference to an unmatched subpattern matches an empty string
259            (Perl fails the current match path).
261        (c) A data ] in a character class must be notated as \] because if the
262            first data character in a class is ], it defines an empty class. (In
263            Perl it is not possible to have an empty class.) The empty class []
264            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
265            The negative empty class [^] matches any one character, independently
266            of the DOTALL setting.
268    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
269        non-existent subpattern following a character class starting with ']' and
270        containing () gave an internal compiling error instead of "reference to
271        non-existent subpattern". Fortunately, when the pattern did exist, the
272        compiled code was correct. (When scanning forwards to check for the
273        existencd of the subpattern, it was treating the data ']' as terminating
274        the class, so got the count wrong. When actually compiling, the reference
275        was subsequently set up correctly.)
277    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
278        it was being rejected as not supported by pcre_dfa_exec(), even though
279        other assertions are supported. I have made pcre_dfa_exec() support
280        (*FAIL).
282    16. The implementation of 13c above involved the invention of a new opcode,
283        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
284        cannot be changed at match time, I realized I could make a small
285        improvement to matching performance by compiling OP_ALLANY instead of
286        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
287        on the OP_ANY path.
289    17. Compiling pcretest on Windows with readline support failed without the
290        following two fixes: (1) Make the unistd.h include conditional on
291        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
293    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
294        ncurses library to be included for pcretest when ReadLine support is
295        requested, but also to allow for it to be overridden. This patch came from
296        Daniel Bergström.
298    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
299        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
300        any errors with the current Unicode tables. Thanks to Peter Kankowski for
301        spotting this.
304    Version 7.6 28-Jan-08
305    ---------------------
307    1.  A character class containing a very large number of characters with
308        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
309        overflow.
311    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
312        HAVE_LONG_LONG is not defined.
314    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
315        bring them up to date and include new features. This patch includes:
317        - Fixed PH's badly added libz and libbz2 support.
318        - Fixed a problem with static linking.
319        - Added pcredemo. [But later removed - see 7 below.]
320        - Fixed dftables problem and added an option.
321        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
322            HAVE_LONG_LONG.
323        - Added readline support for pcretest.
324        - Added an listing of the option settings after cmake has run.
326    4.  A user submitted a patch to Makefile that makes it easy to create
327        "pcre.dll" under mingw when using Configure/Make. I added stuff to
328        Makefile.am that cause it to include this special target, without
329        affecting anything else. Note that the same mingw target plus all
330        the other distribution libraries and programs are now supported
331        when configuring with CMake (see 6 below) instead of with
332        Configure/Make.
334    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
335        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
336        exported in the Windows port". It has not yet been confirmed that the patch
337        solves the problem, but it does no harm.
339    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
340        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
341        with CMake, and also correct the comment about stack recursion.
343    7.  Remove the automatic building of pcredemo from the ./configure system and
344        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
345        of a program that users should build themselves after PCRE is installed, so
346        building it automatically is not really right. What is more, it gave
347        trouble in some build environments.
349    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
352    Version 7.5 10-Jan-08
353    ---------------------
355    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
356        values in parens when parsing an RE using the C++ wrapper."
358    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
359        Characters greater than 255 were excluded from the class instead of being
360        included.
362    3.  The same bug as (2) above applied to negated POSIX classes such as
363        [:^space:].
365    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
366        defined or documented. It seems to have been a typo for PCRE_STATIC, so
367        I have changed it.
369    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
370        first named subpattern) and a construct such as (?&a) would reference the
371        first named subpattern whose name started with "a" (in other words, the
372        length check was missing). Both these problems are fixed. "Subpattern name
373        expected" is now given for (?&) (a zero-length name), and this patch also
374        makes it give the same error for \k'' (previously it complained that that
375        was a reference to a non-existent subpattern).
377    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
378        this is right because (?- can be followed by option settings as well as by
379        digits. I have, however, made the messages clearer.
381    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
382        than the number used in the conditional) now cause a compile-time error.
383        This is actually not compatible with Perl, which accepts such patterns, but
384        treats the conditional as always being FALSE (as PCRE used to), but it
385        seems to me that giving a diagnostic is better.
387    8.  Change "alphameric" to the more common word "alphanumeric" in comments
388        and messages.
390    9.  Fix two occurrences of "backslash" in comments that should have been
391        "backspace".
393    10. Remove two redundant lines of code that can never be obeyed (their function
394        was moved elsewhere).
396    11. The program that makes PCRE's Unicode character property table had a bug
397        which caused it to generate incorrect table entries for sequences of
398        characters that have the same character type, but are in different scripts.
399        It amalgamated them into a single range, with the script of the first of
400        them. In other words, some characters were in the wrong script. There were
401        thirteen such cases, affecting characters in the following ranges:
403          U+002b0 - U+002c1
404          U+0060c - U+0060d
405          U+0061e - U+00612
406          U+0064b - U+0065e
407          U+0074d - U+0076d
408          U+01800 - U+01805
409          U+01d00 - U+01d77
410          U+01d9b - U+01dbf
411          U+0200b - U+0200f
412          U+030fc - U+030fe
413          U+03260 - U+0327f
414          U+0fb46 - U+0fbb1
415          U+10450 - U+1049d
417    12. The -o option (show only the matching part of a line) for pcregrep was not
418        compatible with GNU grep in that, if there was more than one match in a
419        line, it showed only the first of them. It now behaves in the same way as
420        GNU grep.
422    13. If the -o and -v options were combined for pcregrep, it printed a blank
423        line for every non-matching line. GNU grep prints nothing, and pcregrep now
424        does the same. The return code can be used to tell if there were any
425        non-matching lines.
427    14. Added --file-offsets and --line-offsets to pcregrep.
429    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
430        infinitely looping recursion. The bug was that positive lookaheads were not
431        being skipped when checking for a possible empty match (negative lookaheads
432        and both kinds of lookbehind were skipped).
434    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
435        inclusion of <windows.h> to before rather than after the definition of
436        INVALID_FILE_ATTRIBUTES (patch from David Byron).
438    17. Specifying a possessive quantifier with a specific limit for a Unicode
439        character property caused pcre_compile() to compile bad code, which led at
440        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
441        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
442        caused the error; without that there was no problem.
444    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
446    19. Added --enable-pcretest-libreadline.
448    20. In pcrecpp.cc, the variable 'count' was incremented twice in
449        RE::GlobalReplace(). As a result, the number of replacements returned was
450        double what it should be. I removed one of the increments, but Craig sent a
451        later patch that removed the other one (the right fix) and added unit tests
452        that check the return values (which was not done before).
454    21. Several CMake things:
456        (1) Arranged that, when cmake is used on Unix, the libraries end up with
457            the names libpcre and libpcreposix, not just pcre and pcreposix.
459        (2) The above change means that pcretest and pcregrep are now correctly
460            linked with the newly-built libraries, not previously installed ones.
464    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
465        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
466        UTF-8 newline character). The key issue is that the pattern starts .*;
467        this means that the match must be either at the beginning, or after a
468        newline. The bug was in the code for advancing after a failed match and
469        checking that the new position followed a newline. It was not taking
470        account of UTF-8 characters correctly.
472    23. PCRE was behaving differently from Perl in the way it recognized POSIX
473        character classes. PCRE was not treating the sequence [:...:] as a
474        character class unless the ... were all letters. Perl, however, seems to
475        allow any characters between [: and :], though of course it rejects as
476        unknown any "names" that contain non-letters, because all the known class
477        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
478        for example, whereas PCRE did not - it did not recognize a POSIX character
479        class. This seemed a bit dangerous, so the code has been changed to be
480        closer to Perl. The behaviour is not identical to Perl, because PCRE will
481        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
482        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
483        Perl does, and where it didn't before.
485    24. Rewrite so as to remove the single use of %n from pcregrep because in some
486        Windows environments %n is disabled by default.
489    Version 7.4 21-Sep-07
490    ---------------------
492    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
493        means that a class such as [\s] counted as "explicit reference to CR or
494        LF". That isn't really right - the whole point of the change was to try to
495        help when there was an actual mention of one of the two characters. So now
496        the change happens only if \r or \n (or a literal CR or LF) character is
497        encountered.
499    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
500        of both had grown to the point where there were only 3 bits left.
501        Fortunately, there was spare space in the data structure, and so I have
502        moved the internal flags into a new 16-bit field to free up more option
503        bits.
505    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
506        but did not set the internal JCHANGED flag - either of these is enough to
507        control the way the "get" function works - but the PCRE_INFO_JCHANGED
508        facility is supposed to tell if (?J) was ever used, so now (?J) at the
509        start sets both bits.
511    4.  Added options (at build time, compile time, exec time) to change \R from
512        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
514    5.  doc/pcresyntax.html was missing from the distribution.
516    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
517        compatibility, even though it is no longer used.
519    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
520        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
521        windows.h file is present (where different names are used). [This was
522        reversed later after testing - see 16 below.]
524    8.  Changed all #include <config.h> to #include "config.h". There were also
525        some further <pcre.h> cases that I changed to "pcre.h".
527    9.  When pcregrep was used with the --colour option, it missed the line ending
528        sequence off the lines that it output.
530    10. It was pointed out to me that arrays of string pointers cause lots of
531        relocations when a shared library is dynamically loaded. A technique of
532        using a single long string with a table of offsets can drastically reduce
533        these. I have refactored PCRE in four places to do this. The result is
534        dramatic:
536          Originally:                          290
537          After changing UCP table:            187
538          After changing error message table:   43
539          After changing table of "verbs"       36
540          After changing table of Posix names   22
542        Thanks to the folks working on Gregex for glib for this insight.
544    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
545        unicode-properties was also set.
547    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
549    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
550        checked only for CRLF.
552    14. Added casts to pcretest.c to avoid compiler warnings.
554    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
556    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
557        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
558        entirely. This removes changes made in 7 above.
560    17. The CMake files have been updated, and there is now more information about
561        building with CMake in the NON-UNIX-USE document.
564    Version 7.3 28-Aug-07
565  ---------------------  ---------------------
567   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 703  Version 7.3 17-Aug-07
703  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
704      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").
706    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
708    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
709        character were causing crashes (broken optimization).
711    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
712        \p or \P) caused a compile-time loop.
714    28. More problems have arisen in unanchored patterns when CRLF is a valid line
715        break. For example, the unstudied pattern [\r\n]A does not match the string
716        "\r\nA" because change 7.0/46 below moves the current point on by two
717        characters after failing to match at the start. However, the pattern \nA
718        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
719        the same is true. There doesn't seem any very clean way out of this, but
720        what I have chosen to do makes the common cases work: PCRE now takes note
721        of whether there can be an explicit match for \r or \n anywhere in the
722        pattern, and if so, 7.0/46 no longer applies. As part of this change,
723        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
724        pattern has explicit CR or LF references.
726    29. Added (*CR) etc for changing newline setting at start of pattern.
729  Version 7.2 19-Jun-07  Version 7.2 19-Jun-07
730  ---------------------  ---------------------

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

  ViewVC Help
Powered by ViewVC 1.1.5