ViewVC logotype

Diff of /code/trunk/ChangeLog

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

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

Removed from v.213  
changed lines
  Added in v.420

  ViewVC Help
Powered by ViewVC 1.1.5