ViewVC logotype

Diff of /code/trunk/ChangeLog

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

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

Removed from v.200  
changed lines
  Added in v.427

  ViewVC Help
Powered by ViewVC 1.1.5