ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 87 by nigel, Sat Feb 24 21:41:21 2007 UTC revision 303 by ph10, Sun Jan 20 19:39:43 2008 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4    Version 7.6 19-Jan-08
5    ---------------------
7    1.  A character class containing a very large number of characters with
8        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
9        overflow.
11    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
12        HAVE_LONG_LONG is not defined.
14    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
15        bring them up to date and include new features.
18    Version 7.5 10-Jan-08
19    ---------------------
21    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
22        values in parens when parsing an RE using the C++ wrapper."
24    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
25        Characters greater than 255 were excluded from the class instead of being
26        included.
28    3.  The same bug as (2) above applied to negated POSIX classes such as
29        [:^space:].
31    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
32        defined or documented. It seems to have been a typo for PCRE_STATIC, so
33        I have changed it.
35    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
36        first named subpattern) and a construct such as (?&a) would reference the
37        first named subpattern whose name started with "a" (in other words, the
38        length check was missing). Both these problems are fixed. "Subpattern name
39        expected" is now given for (?&) (a zero-length name), and this patch also
40        makes it give the same error for \k'' (previously it complained that that
41        was a reference to a non-existent subpattern).
43    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
44        this is right because (?- can be followed by option settings as well as by
45        digits. I have, however, made the messages clearer.
47    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
48        than the number used in the conditional) now cause a compile-time error.
49        This is actually not compatible with Perl, which accepts such patterns, but
50        treats the conditional as always being FALSE (as PCRE used to), but it
51        seems to me that giving a diagnostic is better.
53    8.  Change "alphameric" to the more common word "alphanumeric" in comments
54        and messages.
56    9.  Fix two occurrences of "backslash" in comments that should have been
57        "backspace".
59    10. Remove two redundant lines of code that can never be obeyed (their function
60        was moved elsewhere).
62    11. The program that makes PCRE's Unicode character property table had a bug
63        which caused it to generate incorrect table entries for sequences of
64        characters that have the same character type, but are in different scripts.
65        It amalgamated them into a single range, with the script of the first of
66        them. In other words, some characters were in the wrong script. There were
67        thirteen such cases, affecting characters in the following ranges:
69          U+002b0 - U+002c1
70          U+0060c - U+0060d
71          U+0061e - U+00612
72          U+0064b - U+0065e
73          U+0074d - U+0076d
74          U+01800 - U+01805
75          U+01d00 - U+01d77
76          U+01d9b - U+01dbf
77          U+0200b - U+0200f
78          U+030fc - U+030fe
79          U+03260 - U+0327f
80          U+0fb46 - U+0fbb1
81          U+10450 - U+1049d
83    12. The -o option (show only the matching part of a line) for pcregrep was not
84        compatible with GNU grep in that, if there was more than one match in a
85        line, it showed only the first of them. It now behaves in the same way as
86        GNU grep.
88    13. If the -o and -v options were combined for pcregrep, it printed a blank
89        line for every non-matching line. GNU grep prints nothing, and pcregrep now
90        does the same. The return code can be used to tell if there were any
91        non-matching lines.
93    14. Added --file-offsets and --line-offsets to pcregrep.
95    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
96        infinitely looping recursion. The bug was that positive lookaheads were not
97        being skipped when checking for a possible empty match (negative lookaheads
98        and both kinds of lookbehind were skipped).
100    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
101        inclusion of <windows.h> to before rather than after the definition of
102        INVALID_FILE_ATTRIBUTES (patch from David Byron).
104    17. Specifying a possessive quantifier with a specific limit for a Unicode
105        character property caused pcre_compile() to compile bad code, which led at
106        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
107        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
108        caused the error; without that there was no problem.
110    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
112    19. Added --enable-pcretest-libreadline.
114    20. In pcrecpp.cc, the variable 'count' was incremented twice in
115        RE::GlobalReplace(). As a result, the number of replacements returned was
116        double what it should be. I removed one of the increments, but Craig sent a
117        later patch that removed the other one (the right fix) and added unit tests
118        that check the return values (which was not done before).
120    21. Several CMake things:
122        (1) Arranged that, when cmake is used on Unix, the libraries end up with
123            the names libpcre and libpcreposix, not just pcre and pcreposix.
125        (2) The above change means that pcretest and pcregrep are now correctly
126            linked with the newly-built libraries, not previously installed ones.
130    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
131        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
132        UTF-8 newline character). The key issue is that the pattern starts .*;
133        this means that the match must be either at the beginning, or after a
134        newline. The bug was in the code for advancing after a failed match and
135        checking that the new position followed a newline. It was not taking
136        account of UTF-8 characters correctly.
138    23. PCRE was behaving differently from Perl in the way it recognized POSIX
139        character classes. PCRE was not treating the sequence [:...:] as a
140        character class unless the ... were all letters. Perl, however, seems to
141        allow any characters between [: and :], though of course it rejects as
142        unknown any "names" that contain non-letters, because all the known class
143        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
144        for example, whereas PCRE did not - it did not recognize a POSIX character
145        class. This seemed a bit dangerous, so the code has been changed to be
146        closer to Perl. The behaviour is not identical to Perl, because PCRE will
147        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
148        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
149        Perl does, and where it didn't before.
151    24. Rewrite so as to remove the single use of %n from pcregrep because in some
152        Windows environments %n is disabled by default.
155    Version 7.4 21-Sep-07
156    ---------------------
158    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
159        means that a class such as [\s] counted as "explicit reference to CR or
160        LF". That isn't really right - the whole point of the change was to try to
161        help when there was an actual mention of one of the two characters. So now
162        the change happens only if \r or \n (or a literal CR or LF) character is
163        encountered.
165    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
166        of both had grown to the point where there were only 3 bits left.
167        Fortunately, there was spare space in the data structure, and so I have
168        moved the internal flags into a new 16-bit field to free up more option
169        bits.
171    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
172        but did not set the internal JCHANGED flag - either of these is enough to
173        control the way the "get" function works - but the PCRE_INFO_JCHANGED
174        facility is supposed to tell if (?J) was ever used, so now (?J) at the
175        start sets both bits.
177    4.  Added options (at build time, compile time, exec time) to change \R from
178        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
180    5.  doc/pcresyntax.html was missing from the distribution.
182    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
183        compatibility, even though it is no longer used.
185    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
186        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
187        windows.h file is present (where different names are used). [This was
188        reversed later after testing - see 16 below.]
190    8.  Changed all #include <config.h> to #include "config.h". There were also
191        some further <pcre.h> cases that I changed to "pcre.h".
193    9.  When pcregrep was used with the --colour option, it missed the line ending
194        sequence off the lines that it output.
196    10. It was pointed out to me that arrays of string pointers cause lots of
197        relocations when a shared library is dynamically loaded. A technique of
198        using a single long string with a table of offsets can drastically reduce
199        these. I have refactored PCRE in four places to do this. The result is
200        dramatic:
202          Originally:                          290
203          After changing UCP table:            187
204          After changing error message table:   43
205          After changing table of "verbs"       36
206          After changing table of Posix names   22
208        Thanks to the folks working on Gregex for glib for this insight.
210    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
211        unicode-properties was also set.
213    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
215    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
216        checked only for CRLF.
218    14. Added casts to pcretest.c to avoid compiler warnings.
220    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
222    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
223        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
224        entirely. This removes changes made in 7 above.
226    17. The CMake files have been updated, and there is now more information about
227        building with CMake in the NON-UNIX-USE document.
230    Version 7.3 28-Aug-07
231    ---------------------
233     1. In the rejigging of the build system that eventually resulted in 7.1, the
234        line "#include <pcre.h>" was included in pcre_internal.h. The use of angle
235        brackets there is not right, since it causes compilers to look for an
236        installed pcre.h, not the version that is in the source that is being
237        compiled (which of course may be different). I have changed it back to:
239          #include "pcre.h"
241        I have a vague recollection that the change was concerned with compiling in
242        different directories, but in the new build system, that is taken care of
243        by the VPATH setting the Makefile.
245     2. The pattern .*$ when run in not-DOTALL UTF-8 mode with newline=any failed
246        when the subject happened to end in the byte 0x85 (e.g. if the last
247        character was \x{1ec5}). *Character* 0x85 is one of the "any" newline
248        characters but of course it shouldn't be taken as a newline when it is part
249        of another character. The bug was that, for an unlimited repeat of . in
250        not-DOTALL UTF-8 mode, PCRE was advancing by bytes rather than by
251        characters when looking for a newline.
253     3. A small performance improvement in the DOTALL UTF-8 mode .* case.
255     4. Debugging: adjusted the names of opcodes for different kinds of parentheses
256        in debug output.
258     5. Arrange to use "%I64d" instead of "%lld" and "%I64u" instead of "%llu" for
259        long printing in the pcrecpp unittest when running under MinGW.
261     6. ESC_K was left out of the EBCDIC table.
263     7. Change 7.0/38 introduced a new limit on the number of nested non-capturing
264        parentheses; I made it 1000, which seemed large enough. Unfortunately, the
265        limit also applies to "virtual nesting" when a pattern is recursive, and in
266        this case 1000 isn't so big. I have been able to remove this limit at the
267        expense of backing off one optimization in certain circumstances. Normally,
268        when pcre_exec() would call its internal match() function recursively and
269        immediately return the result unconditionally, it uses a "tail recursion"
270        feature to save stack. However, when a subpattern that can match an empty
271        string has an unlimited repetition quantifier, it no longer makes this
272        optimization. That gives it a stack frame in which to save the data for
273        checking that an empty string has been matched. Previously this was taken
274        from the 1000-entry workspace that had been reserved. So now there is no
275        explicit limit, but more stack is used.
277     8. Applied Daniel's patches to solve problems with the import/export magic
278        syntax that is required for Windows, and which was going wrong for the
279        pcreposix and pcrecpp parts of the library. These were overlooked when this
280        problem was solved for the main library.
282     9. There were some crude static tests to avoid integer overflow when computing
283        the size of patterns that contain repeated groups with explicit upper
284        limits. As the maximum quantifier is 65535, the maximum group length was
285        set at 30,000 so that the product of these two numbers did not overflow a
286        32-bit integer. However, it turns out that people want to use groups that
287        are longer than 30,000 bytes (though not repeat them that many times).
288        Change 7.0/17 (the refactoring of the way the pattern size is computed) has
289        made it possible to implement the integer overflow checks in a much more
290        dynamic way, which I have now done. The artificial limitation on group
291        length has been removed - we now have only the limit on the total length of
292        the compiled pattern, which depends on the LINK_SIZE setting.
294    10. Fixed a bug in the documentation for get/copy named substring when
295        duplicate names are permitted. If none of the named substrings are set, the
296        functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an
297        empty string.
299    11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E
300        instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,
301        because the ] is interpreted as the first data character and the
302        terminating ] is not found. PCRE has been made compatible with Perl in this
303        regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could
304        cause memory overwriting.
306    10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty
307        string has been matched (to stop an infinite loop). It was not recognizing
308        a conditional subpattern that could match an empty string if that
309        subpattern was within another subpattern. For example, it looped when
310        trying to match  (((?(1)X|))*)  but it was OK with  ((?(1)X|)*)  where the
311        condition was not nested. This bug has been fixed.
313    12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack
314        past the start of the subject in the presence of bytes with the top bit
315        set, for example "\x8aBCD".
317    13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
318        (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
320    14. Optimized (?!) to (*FAIL).
322    15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
323        This restricts code points to be within the range 0 to 0x10FFFF, excluding
324        the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
325        full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
326        does: it's just the validity check that is more restrictive.
328    16. Inserted checks for integer overflows during escape sequence (backslash)
329        processing, and also fixed erroneous offset values for syntax errors during
330        backslash processing.
332    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
333        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
335    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
336        caused an overrun.
338    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
339        something other than just ASCII characters) inside a group that had an
340        unlimited repeat caused a loop at compile time (while checking to see
341        whether the group could match an empty string).
343    20. Debugging a pattern containing \p or \P could cause a crash. For example,
344        [\P{Any}] did so. (Error in the code for printing property names.)
346    21. An orphan \E inside a character class could cause a crash.
348    22. A repeated capturing bracket such as (A)? could cause a wild memory
349        reference during compilation.
351    23. There are several functions in pcre_compile() that scan along a compiled
352        expression for various reasons (e.g. to see if it's fixed length for look
353        behind). There were bugs in these functions when a repeated \p or \P was
354        present in the pattern. These operators have additional parameters compared
355        with \d, etc, and these were not being taken into account when moving along
356        the compiled data. Specifically:
358        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
359            length.
361        (b) An item such as \pL+ within a repeated group could cause crashes or
362            loops.
364        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
365            "reference to non-existent subpattern" error.
367        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
369    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
370        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
372    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
374    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
375        character were causing crashes (broken optimization).
377    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
378        \p or \P) caused a compile-time loop.
380    28. More problems have arisen in unanchored patterns when CRLF is a valid line
381        break. For example, the unstudied pattern [\r\n]A does not match the string
382        "\r\nA" because change 7.0/46 below moves the current point on by two
383        characters after failing to match at the start. However, the pattern \nA
384        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
385        the same is true. There doesn't seem any very clean way out of this, but
386        what I have chosen to do makes the common cases work: PCRE now takes note
387        of whether there can be an explicit match for \r or \n anywhere in the
388        pattern, and if so, 7.0/46 no longer applies. As part of this change,
389        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
390        pattern has explicit CR or LF references.
392    29. Added (*CR) etc for changing newline setting at start of pattern.
395    Version 7.2 19-Jun-07
396    ---------------------
398     1. If the fr_FR locale cannot be found for test 3, try the "french" locale,
399        which is apparently normally available under Windows.
401     2. Re-jig the pcregrep tests with different newline settings in an attempt
402        to make them independent of the local environment's newline setting.
404     3. Add code to configure.ac to remove -g from the CFLAGS default settings.
406     4. Some of the "internals" tests were previously cut out when the link size
407        was not 2, because the output contained actual offsets. The recent new
408        "Z" feature of pcretest means that these can be cut out, making the tests
409        usable with all link sizes.
411     5. Implemented Stan Switzer's goto replacement for longjmp() when not using
412        stack recursion. This gives a massive performance boost under BSD, but just
413        a small improvement under Linux. However, it saves one field in the frame
414        in all cases.
416     6. Added more features from the forthcoming Perl 5.10:
418        (a) (?-n) (where n is a string of digits) is a relative subroutine or
419            recursion call. It refers to the nth most recently opened parentheses.
421        (b) (?+n) is also a relative subroutine call; it refers to the nth next
422            to be opened parentheses.
424        (c) Conditions that refer to capturing parentheses can be specified
425            relatively, for example, (?(-2)... or (?(+3)...
427        (d) \K resets the start of the current match so that everything before
428            is not part of it.
430        (e) \k{name} is synonymous with \k<name> and \k'name' (.NET compatible).
432        (f) \g{name} is another synonym - part of Perl 5.10's unification of
433            reference syntax.
435        (g) (?| introduces a group in which the numbering of parentheses in each
436            alternative starts with the same number.
438        (h) \h, \H, \v, and \V match horizontal and vertical whitespace.
440     7. Added two new calls to pcre_fullinfo(): PCRE_INFO_OKPARTIAL and
443     8. A pattern such as  (.*(.)?)*  caused pcre_exec() to fail by either not
444        terminating or by crashing. Diagnosed by Viktor Griph; it was in the code
445        for detecting groups that can match an empty string.
447     9. A pattern with a very large number of alternatives (more than several
448        hundred) was running out of internal workspace during the pre-compile
449        phase, where pcre_compile() figures out how much memory will be needed. A
450        bit of new cunning has reduced the workspace needed for groups with
451        alternatives. The 1000-alternative test pattern now uses 12 bytes of
452        workspace instead of running out of the 4096 that are available.
454    10. Inserted some missing (unsigned int) casts to get rid of compiler warnings.
456    11. Applied patch from Google to remove an optimization that didn't quite work.
457        The report of the bug said:
459          pcrecpp::RE("a*").FullMatch("aaa") matches, while
460          pcrecpp::RE("a*?").FullMatch("aaa") does not, and
461          pcrecpp::RE("a*?\\z").FullMatch("aaa") does again.
463    12. If \p or \P was used in non-UTF-8 mode on a character greater than 127
464        it matched the wrong number of bytes.
467    Version 7.1 24-Apr-07
468    ---------------------
470     1. Applied Bob Rossi and Daniel G's patches to convert the build system to one
471        that is more "standard", making use of automake and other Autotools. There
472        is some re-arrangement of the files and adjustment of comments consequent
473        on this.
475     2. Part of the patch fixed a problem with the pcregrep tests. The test of -r
476        for recursive directory scanning broke on some systems because the files
477        are not scanned in any specific order and on different systems the order
478        was different. A call to "sort" has been inserted into RunGrepTest for the
479        approprate test as a short-term fix. In the longer term there may be an
480        alternative.
482     3. I had an email from Eric Raymond about problems translating some of PCRE's
483        man pages to HTML (despite the fact that I distribute HTML pages, some
484        people do their own conversions for various reasons). The problems
485        concerned the use of low-level troff macros .br and .in. I have therefore
486        removed all such uses from the man pages (some were redundant, some could
487        be replaced by .nf/.fi pairs). The 132html script that I use to generate
488        HTML has been updated to handle .nf/.fi and to complain if it encounters
489        .br or .in.
491     4. Updated comments in configure.ac that get placed in config.h.in and also
492        arranged for config.h to be included in the distribution, with the name
493        config.h.generic, for the benefit of those who have to compile without
494        Autotools (compare pcre.h, which is now distributed as pcre.h.generic).
496     5. Updated the support (such as it is) for Virtual Pascal, thanks to Stefan
497        Weber: (1) pcre_internal.h was missing some function renames; (2) updated
498        makevp.bat for the current PCRE, using the additional files
499        makevp_c.txt, makevp_l.txt, and pcregexp.pas.
501     6. A Windows user reported a minor discrepancy with test 2, which turned out
502        to be caused by a trailing space on an input line that had got lost in his
503        copy. The trailing space was an accident, so I've just removed it.
505     7. Add -Wl,-R... flags in pcre-config.in for *BSD* systems, as I'm told
506        that is needed.
508     8. Mark ucp_table (in ucptable.h) and ucp_gentype (in pcre_ucp_searchfuncs.c)
509        as "const" (a) because they are and (b) because it helps the PHP
510        maintainers who have recently made a script to detect big data structures
511        in the php code that should be moved to the .rodata section. I remembered
512        to update Builducptable as well, so it won't revert if ucptable.h is ever
513        re-created.
515     9. Added some extra #ifdef SUPPORT_UTF8 conditionals into pcretest.c,
516        pcre_printint.src, pcre_compile.c, pcre_study.c, and pcre_tables.c, in
517        order to be able to cut out the UTF-8 tables in the latter when UTF-8
518        support is not required. This saves 1.5-2K of code, which is important in
519        some applications.
521        Later: more #ifdefs are needed in pcre_ord2utf8.c and pcre_valid_utf8.c
522        so as not to refer to the tables, even though these functions will never be
523        called when UTF-8 support is disabled. Otherwise there are problems with a
524        shared library.
526    10. Fixed two bugs in the emulated memmove() function in pcre_internal.h:
528        (a) It was defining its arguments as char * instead of void *.
530        (b) It was assuming that all moves were upwards in memory; this was true
531            a long time ago when I wrote it, but is no longer the case.
533        The emulated memove() is provided for those environments that have neither
534        memmove() nor bcopy(). I didn't think anyone used it these days, but that
535        is clearly not the case, as these two bugs were recently reported.
537    11. The script PrepareRelease is now distributed: it calls 132html, CleanTxt,
538        and Detrail to create the HTML documentation, the .txt form of the man
539        pages, and it removes trailing spaces from listed files. It also creates
540        pcre.h.generic and config.h.generic from pcre.h and config.h. In the latter
541        case, it wraps all the #defines with #ifndefs. This script should be run
542        before "make dist".
544    12. Fixed two fairly obscure bugs concerned with quantified caseless matching
545        with Unicode property support.
547        (a) For a maximizing quantifier, if the two different cases of the
548            character were of different lengths in their UTF-8 codings (there are
549            some cases like this - I found 11), and the matching function had to
550            back up over a mixture of the two cases, it incorrectly assumed they
551            were both the same length.
553        (b) When PCRE was configured to use the heap rather than the stack for
554            recursion during matching, it was not correctly preserving the data for
555            the other case of a UTF-8 character when checking ahead for a match
556            while processing a minimizing repeat. If the check also involved
557            matching a wide character, but failed, corruption could cause an
558            erroneous result when trying to check for a repeat of the original
559            character.
561    13. Some tidying changes to the testing mechanism:
563        (a) The RunTest script now detects the internal link size and whether there
564            is UTF-8 and UCP support by running ./pcretest -C instead of relying on
565            values substituted by "configure". (The RunGrepTest script already did
566            this for UTF-8.) The configure.ac script no longer substitutes the
567            relevant variables.
569        (b) The debugging options /B and /D in pcretest show the compiled bytecode
570            with length and offset values. This means that the output is different
571            for different internal link sizes. Test 2 is skipped for link sizes
572            other than 2 because of this, bypassing the problem. Unfortunately,
573            there was also a test in test 3 (the locale tests) that used /B and
574            failed for link sizes other than 2. Rather than cut the whole test out,
575            I have added a new /Z option to pcretest that replaces the length and
576            offset values with spaces. This is now used to make test 3 independent
577            of link size. (Test 2 will be tidied up later.)
579    14. If erroroffset was passed as NULL to pcre_compile, it provoked a
580        segmentation fault instead of returning the appropriate error message.
582    15. In multiline mode when the newline sequence was set to "any", the pattern
583        ^$ would give a match between the \r and \n of a subject such as "A\r\nB".
584        This doesn't seem right; it now treats the CRLF combination as the line
585        ending, and so does not match in that case. It's only a pattern such as ^$
586        that would hit this one: something like ^ABC$ would have failed after \r
587        and then tried again after \r\n.
589    16. Changed the comparison command for RunGrepTest from "diff -u" to "diff -ub"
590        in an attempt to make files that differ only in their line terminators
591        compare equal. This works on Linux.
593    17. Under certain error circumstances pcregrep might try to free random memory
594        as it exited. This is now fixed, thanks to valgrind.
596    19. In pcretest, if the pattern /(?m)^$/g<any> was matched against the string
597        "abc\r\n\r\n", it found an unwanted second match after the second \r. This
598        was because its rules for how to advance for /g after matching an empty
599        string at the end of a line did not allow for this case. They now check for
600        it specially.
602    20. pcretest is supposed to handle patterns and data of any length, by
603        extending its buffers when necessary. It was getting this wrong when the
604        buffer for a data line had to be extended.
606    21. Added PCRE_NEWLINE_ANYCRLF which is like ANY, but matches only CR, LF, or
607        CRLF as a newline sequence.
609    22. Code for handling Unicode properties in pcre_dfa_exec() wasn't being cut
610        out by #ifdef SUPPORT_UCP. This did no harm, as it could never be used, but
611        I have nevertheless tidied it up.
613    23. Added some casts to kill warnings from HP-UX ia64 compiler.
615    24. Added a man page for pcre-config.
618    Version 7.0 19-Dec-06
619    ---------------------
621     1. Fixed a signed/unsigned compiler warning in pcre_compile.c, shown up by
622        moving to gcc 4.1.1.
624     2. The -S option for pcretest uses setrlimit(); I had omitted to #include
625        sys/time.h, which is documented as needed for this function. It doesn't
626        seem to matter on Linux, but it showed up on some releases of OS X.
628     3. It seems that there are systems where bytes whose values are greater than
629        127 match isprint() in the "C" locale. The "C" locale should be the
630        default when a C program starts up. In most systems, only ASCII printing
631        characters match isprint(). This difference caused the output from pcretest
632        to vary, making some of the tests fail. I have changed pcretest so that:
634        (a) When it is outputting text in the compiled version of a pattern, bytes
635            other than 32-126 are always shown as hex escapes.
637        (b) When it is outputting text that is a matched part of a subject string,
638            it does the same, unless a different locale has been set for the match
639            (using the /L modifier). In this case, it uses isprint() to decide.
641     4. Fixed a major bug that caused incorrect computation of the amount of memory
642        required for a compiled pattern when options that changed within the
643        pattern affected the logic of the preliminary scan that determines the
644        length. The relevant options are -x, and -i in UTF-8 mode. The result was
645        that the computed length was too small. The symptoms of this bug were
646        either the PCRE error "internal error: code overflow" from pcre_compile(),
647        or a glibc crash with a message such as "pcretest: free(): invalid next
648        size (fast)". Examples of patterns that provoked this bug (shown in
649        pcretest format) are:
651          /(?-x: )/x
652          /(?x)(?-x: \s*#\s*)/
653          /((?i)[\x{c0}])/8
654          /(?i:[\x{c0}])/8
656        HOWEVER: Change 17 below makes this fix obsolete as the memory computation
657        is now done differently.
659     5. Applied patches from Google to: (a) add a QuoteMeta function to the C++
660        wrapper classes; (b) implement a new function in the C++ scanner that is
661        more efficient than the old way of doing things because it avoids levels of
662        recursion in the regex matching; (c) add a paragraph to the documentation
663        for the FullMatch() function.
665     6. The escape sequence \n was being treated as whatever was defined as
666        "newline". Not only was this contrary to the documentation, which states
667        that \n is character 10 (hex 0A), but it also went horribly wrong when
668        "newline" was defined as CRLF. This has been fixed.
670     7. In pcre_dfa_exec.c the value of an unsigned integer (the variable called c)
671        was being set to -1 for the "end of line" case (supposedly a value that no
672        character can have). Though this value is never used (the check for end of
673        line is "zero bytes in current character"), it caused compiler complaints.
674        I've changed it to 0xffffffff.
676     8. In pcre_version.c, the version string was being built by a sequence of
677        C macros that, in the event of PCRE_PRERELEASE being defined as an empty
678        string (as it is for production releases) called a macro with an empty
679        argument. The C standard says the result of this is undefined. The gcc
680        compiler treats it as an empty string (which was what was wanted) but it is
681        reported that Visual C gives an error. The source has been hacked around to
682        avoid this problem.
684     9. On the advice of a Windows user, included <io.h> and <fcntl.h> in Windows
685        builds of pcretest, and changed the call to _setmode() to use _O_BINARY
686        instead of 0x8000. Made all the #ifdefs test both _WIN32 and WIN32 (not all
687        of them did).
689    10. Originally, pcretest opened its input and output without "b"; then I was
690        told that "b" was needed in some environments, so it was added for release
691        5.0 to both the input and output. (It makes no difference on Unix-like
692        systems.) Later I was told that it is wrong for the input on Windows. I've
693        now abstracted the modes into two macros, to make it easier to fiddle with
694        them, and removed "b" from the input mode under Windows.
696    11. Added pkgconfig support for the C++ wrapper library, libpcrecpp.
698    12. Added -help and --help to pcretest as an official way of being reminded
699        of the options.
701    13. Removed some redundant semicolons after macro calls in pcrecpparg.h.in
702        and pcrecpp.cc because they annoy compilers at high warning levels.
704    14. A bit of tidying/refactoring in pcre_exec.c in the main bumpalong loop.
706    15. Fixed an occurrence of == in configure.ac that should have been = (shell
707        scripts are not C programs :-) and which was not noticed because it works
708        on Linux.
710    16. pcretest is supposed to handle any length of pattern and data line (as one
711        line or as a continued sequence of lines) by extending its input buffer if
712        necessary. This feature was broken for very long pattern lines, leading to
713        a string of junk being passed to pcre_compile() if the pattern was longer
714        than about 50K.
716    17. I have done a major re-factoring of the way pcre_compile() computes the
717        amount of memory needed for a compiled pattern. Previously, there was code
718        that made a preliminary scan of the pattern in order to do this. That was
719        OK when PCRE was new, but as the facilities have expanded, it has become
720        harder and harder to keep it in step with the real compile phase, and there
721        have been a number of bugs (see for example, 4 above). I have now found a
722        cunning way of running the real compile function in a "fake" mode that
723        enables it to compute how much memory it would need, while actually only
724        ever using a few hundred bytes of working memory and without too many
725        tests of the mode. This should make future maintenance and development
726        easier. A side effect of this work is that the limit of 200 on the nesting
727        depth of parentheses has been removed (though this was never a serious
728        limitation, I suspect). However, there is a downside: pcre_compile() now
729        runs more slowly than before (30% or more, depending on the pattern). I
730        hope this isn't a big issue. There is no effect on runtime performance.
732    18. Fixed a minor bug in pcretest: if a pattern line was not terminated by a
733        newline (only possible for the last line of a file) and it was a
734        pattern that set a locale (followed by /Lsomething), pcretest crashed.
736    19. Added additional timing features to pcretest. (1) The -tm option now times
737        matching only, not compiling. (2) Both -t and -tm can be followed, as a
738        separate command line item, by a number that specifies the number of
739        repeats to use when timing. The default is 50000; this gives better
740        precision, but takes uncomfortably long for very large patterns.
742    20. Extended pcre_study() to be more clever in cases where a branch of a
743        subpattern has no definite first character. For example, (a*|b*)[cd] would
744        previously give no result from pcre_study(). Now it recognizes that the
745        first character must be a, b, c, or d.
747    21. There was an incorrect error "recursive call could loop indefinitely" if
748        a subpattern (or the entire pattern) that was being tested for matching an
749        empty string contained only one non-empty item after a nested subpattern.
750        For example, the pattern (?>\x{100}*)\d(?R) provoked this error
751        incorrectly, because the \d was being skipped in the check.
753    22. The pcretest program now has a new pattern option /B and a command line
754        option -b, which is equivalent to adding /B to every pattern. This causes
755        it to show the compiled bytecode, without the additional information that
756        -d shows. The effect of -d is now the same as -b with -i (and similarly, /D
757        is the same as /B/I).
759    23. A new optimization is now able automatically to treat some sequences such
760        as a*b as a*+b. More specifically, if something simple (such as a character
761        or a simple class like \d) has an unlimited quantifier, and is followed by
762        something that cannot possibly match the quantified thing, the quantifier
763        is automatically "possessified".
765    24. A recursive reference to a subpattern whose number was greater than 39
766        went wrong under certain circumstances in UTF-8 mode. This bug could also
767        have affected the operation of pcre_study().
769    25. Realized that a little bit of performance could be had by replacing
770        (c & 0xc0) == 0xc0 with c >= 0xc0 when processing UTF-8 characters.
772    26. Timing data from pcretest is now shown to 4 decimal places instead of 3.
774    27. Possessive quantifiers such as a++ were previously implemented by turning
775        them into atomic groups such as ($>a+). Now they have their own opcodes,
776        which improves performance. This includes the automatically created ones
777        from 23 above.
779    28. A pattern such as (?=(\w+))\1: which simulates an atomic group using a
780        lookahead was broken if it was not anchored. PCRE was mistakenly expecting
781        the first matched character to be a colon. This applied both to named and
782        numbered groups.
784    29. The ucpinternal.h header file was missing its idempotency #ifdef.
786    30. I was sent a "project" file called libpcre.a.dev which I understand makes
787        building PCRE on Windows easier, so I have included it in the distribution.
789    31. There is now a check in pcretest against a ridiculously large number being
790        returned by pcre_exec() or pcre_dfa_exec(). If this happens in a /g or /G
791        loop, the loop is abandoned.
793    32. Forward references to subpatterns in conditions such as (?(2)...) where
794        subpattern 2 is defined later cause pcre_compile() to search forwards in
795        the pattern for the relevant set of parentheses. This search went wrong
796        when there were unescaped parentheses in a character class, parentheses
797        escaped with \Q...\E, or parentheses in a #-comment in /x mode.
799    33. "Subroutine" calls and backreferences were previously restricted to
800        referencing subpatterns earlier in the regex. This restriction has now
801        been removed.
803    34. Added a number of extra features that are going to be in Perl 5.10. On the
804        whole, these are just syntactic alternatives for features that PCRE had
805        previously implemented using the Python syntax or my own invention. The
806        other formats are all retained for compatibility.
808        (a) Named groups can now be defined as (?<name>...) or (?'name'...) as well
809            as (?P<name>...). The new forms, as well as being in Perl 5.10, are
810            also .NET compatible.
812        (b) A recursion or subroutine call to a named group can now be defined as
813            (?&name) as well as (?P>name).
815        (c) A backreference to a named group can now be defined as \k<name> or
816            \k'name' as well as (?P=name). The new forms, as well as being in Perl
817            5.10, are also .NET compatible.
819        (d) A conditional reference to a named group can now use the syntax
820            (?(<name>) or (?('name') as well as (?(name).
822        (e) A "conditional group" of the form (?(DEFINE)...) can be used to define
823            groups (named and numbered) that are never evaluated inline, but can be
824            called as "subroutines" from elsewhere. In effect, the DEFINE condition
825            is always false. There may be only one alternative in such a group.
827        (f) A test for recursion can be given as (?(R1).. or (?(R&name)... as well
828            as the simple (?(R). The condition is true only if the most recent
829            recursion is that of the given number or name. It does not search out
830            through the entire recursion stack.
832        (g) The escape \gN or \g{N} has been added, where N is a positive or
833            negative number, specifying an absolute or relative reference.
835    35. Tidied to get rid of some further signed/unsigned compiler warnings and
836        some "unreachable code" warnings.
838    36. Updated the Unicode property tables to Unicode version 5.0.0. Amongst other
839        things, this adds five new scripts.
841    37. Perl ignores orphaned \E escapes completely. PCRE now does the same.
842        There were also incompatibilities regarding the handling of \Q..\E inside
843        character classes, for example with patterns like [\Qa\E-\Qz\E] where the
844        hyphen was adjacent to \Q or \E. I hope I've cleared all this up now.
846    38. Like Perl, PCRE detects when an indefinitely repeated parenthesized group
847        matches an empty string, and forcibly breaks the loop. There were bugs in
848        this code in non-simple cases. For a pattern such as  ^(a()*)*  matched
849        against  aaaa  the result was just "a" rather than "aaaa", for example. Two
850        separate and independent bugs (that affected different cases) have been
851        fixed.
853    39. Refactored the code to abolish the use of different opcodes for small
854        capturing bracket numbers. This is a tidy that I avoided doing when I
855        removed the limit on the number of capturing brackets for 3.5 back in 2001.
856        The new approach is not only tidier, it makes it possible to reduce the
857        memory needed to fix the previous bug (38).
859    40. Implemented PCRE_NEWLINE_ANY to recognize any of the Unicode newline
860        sequences (http://unicode.org/unicode/reports/tr18/) as "newline" when
861        processing dot, circumflex, or dollar metacharacters, or #-comments in /x
862        mode.
864    41. Add \R to match any Unicode newline sequence, as suggested in the Unicode
865        report.
867    42. Applied patch, originally from Ari Pollak, modified by Google, to allow
868        copy construction and assignment in the C++ wrapper.
870    43. Updated pcregrep to support "--newline=any". In the process, I fixed a
871        couple of bugs that could have given wrong results in the "--newline=crlf"
872        case.
874    44. Added a number of casts and did some reorganization of signed/unsigned int
875        variables following suggestions from Dair Grant. Also renamed the variable
876        "this" as "item" because it is a C++ keyword.
878    45. Arranged for dftables to add
880          #include "pcre_internal.h"
882        to pcre_chartables.c because without it, gcc 4.x may remove the array
883        definition from the final binary if PCRE is built into a static library and
884        dead code stripping is activated.
886    46. For an unanchored pattern, if a match attempt fails at the start of a
887        newline sequence, and the newline setting is CRLF or ANY, and the next two
888        characters are CRLF, advance by two characters instead of one.
891    Version 6.7 04-Jul-06
892    ---------------------
894     1. In order to handle tests when input lines are enormously long, pcretest has
895        been re-factored so that it automatically extends its buffers when
896        necessary. The code is crude, but this _is_ just a test program. The
897        default size has been increased from 32K to 50K.
899     2. The code in pcre_study() was using the value of the re argument before
900        testing it for NULL. (Of course, in any sensible call of the function, it
901        won't be NULL.)
903     3. The memmove() emulation function in pcre_internal.h, which is used on
904        systems that lack both memmove() and bcopy() - that is, hardly ever -
905        was missing a "static" storage class specifier.
907     4. When UTF-8 mode was not set, PCRE looped when compiling certain patterns
908        containing an extended class (one that cannot be represented by a bitmap
909        because it contains high-valued characters or Unicode property items, e.g.
910        [\pZ]). Almost always one would set UTF-8 mode when processing such a
911        pattern, but PCRE should not loop if you do not (it no longer does).
912        [Detail: two cases were found: (a) a repeated subpattern containing an
913        extended class; (b) a recursive reference to a subpattern that followed a
914        previous extended class. It wasn't skipping over the extended class
915        correctly when UTF-8 mode was not set.]
917     5. A negated single-character class was not being recognized as fixed-length
918        in lookbehind assertions such as (?<=[^f]), leading to an incorrect
919        compile error "lookbehind assertion is not fixed length".
921     6. The RunPerlTest auxiliary script was showing an unexpected difference
922        between PCRE and Perl for UTF-8 tests. It turns out that it is hard to
923        write a Perl script that can interpret lines of an input file either as
924        byte characters or as UTF-8, which is what "perltest" was being required to
925        do for the non-UTF-8 and UTF-8 tests, respectively. Essentially what you
926        can't do is switch easily at run time between having the "use utf8;" pragma
927        or not. In the end, I fudged it by using the RunPerlTest script to insert
928        "use utf8;" explicitly for the UTF-8 tests.
930     7. In multiline (/m) mode, PCRE was matching ^ after a terminating newline at
931        the end of the subject string, contrary to the documentation and to what
932        Perl does. This was true of both matching functions. Now it matches only at
933        the start of the subject and immediately after *internal* newlines.
935     8. A call of pcre_fullinfo() from pcretest to get the option bits was passing
936        a pointer to an int instead of a pointer to an unsigned long int. This
937        caused problems on 64-bit systems.
939     9. Applied a patch from the folks at Google to pcrecpp.cc, to fix "another
940        instance of the 'standard' template library not being so standard".
942    10. There was no check on the number of named subpatterns nor the maximum
943        length of a subpattern name. The product of these values is used to compute
944        the size of the memory block for a compiled pattern. By supplying a very
945        long subpattern name and a large number of named subpatterns, the size
946        computation could be caused to overflow. This is now prevented by limiting
947        the length of names to 32 characters, and the number of named subpatterns
948        to 10,000.
950    11. Subpatterns that are repeated with specific counts have to be replicated in
951        the compiled pattern. The size of memory for this was computed from the
952        length of the subpattern and the repeat count. The latter is limited to
953        65535, but there was no limit on the former, meaning that integer overflow
954        could in principle occur. The compiled length of a repeated subpattern is
955        now limited to 30,000 bytes in order to prevent this.
957    12. Added the optional facility to have named substrings with the same name.
959    13. Added the ability to use a named substring as a condition, using the
960        Python syntax: (?(name)yes|no). This overloads (?(R)... and names that
961        are numbers (not recommended). Forward references are permitted.
963    14. Added forward references in named backreferences (if you see what I mean).
965    15. In UTF-8 mode, with the PCRE_DOTALL option set, a quantified dot in the
966        pattern could run off the end of the subject. For example, the pattern
967        "(?s)(.{1,5})"8 did this with the subject "ab".
969    16. If PCRE_DOTALL or PCRE_MULTILINE were set, pcre_dfa_exec() behaved as if
970        PCRE_CASELESS was set when matching characters that were quantified with ?
971        or *.
973    17. A character class other than a single negated character that had a minimum
974        but no maximum quantifier - for example [ab]{6,} - was not handled
975        correctly by pce_dfa_exec(). It would match only one character.
977    18. A valid (though odd) pattern that looked like a POSIX character
978        class but used an invalid character after [ (for example [[,abc,]]) caused
979        pcre_compile() to give the error "Failed: internal error: code overflow" or
980        in some cases to crash with a glibc free() error. This could even happen if
981        the pattern terminated after [[ but there just happened to be a sequence of
982        letters, a binary zero, and a closing ] in the memory that followed.
984    19. Perl's treatment of octal escapes in the range \400 to \777 has changed
985        over the years. Originally (before any Unicode support), just the bottom 8
986        bits were taken. Thus, for example, \500 really meant \100. Nowadays the
987        output from "man perlunicode" includes this:
989          The regular expression compiler produces polymorphic opcodes.  That
990          is, the pattern adapts to the data and automatically switches to
991          the Unicode character scheme when presented with Unicode data--or
992          instead uses a traditional byte scheme when presented with byte
993          data.
995        Sadly, a wide octal escape does not cause a switch, and in a string with
996        no other multibyte characters, these octal escapes are treated as before.
997        Thus, in Perl, the pattern  /\500/ actually matches \100 but the pattern
998        /\500|\x{1ff}/ matches \500 or \777 because the whole thing is treated as a
999        Unicode string.
1001        I have not perpetrated such confusion in PCRE. Up till now, it took just
1002        the bottom 8 bits, as in old Perl. I have now made octal escapes with
1003        values greater than \377 illegal in non-UTF-8 mode. In UTF-8 mode they
1004        translate to the appropriate multibyte character.
1006    29. Applied some refactoring to reduce the number of warnings from Microsoft
1007        and Borland compilers. This has included removing the fudge introduced
1008        seven years ago for the OS/2 compiler (see 2.02/2 below) because it caused
1009        a warning about an unused variable.
1011    21. PCRE has not included VT (character 0x0b) in the set of whitespace
1012        characters since release 4.0, because Perl (from release 5.004) does not.
1013        [Or at least, is documented not to: some releases seem to be in conflict
1014        with the documentation.] However, when a pattern was studied with
1015        pcre_study() and all its branches started with \s, PCRE still included VT
1016        as a possible starting character. Of course, this did no harm; it just
1017        caused an unnecessary match attempt.
1019    22. Removed a now-redundant internal flag bit that recorded the fact that case
1020        dependency changed within the pattern. This was once needed for "required
1021        byte" processing, but is no longer used. This recovers a now-scarce options
1022        bit. Also moved the least significant internal flag bit to the most-
1023        significant bit of the word, which was not previously used (hangover from
1024        the days when it was an int rather than a uint) to free up another bit for
1025        the future.
1027    23. Added support for CRLF line endings as well as CR and LF. As well as the
1028        default being selectable at build time, it can now be changed at runtime
1029        via the PCRE_NEWLINE_xxx flags. There are now options for pcregrep to
1030        specify that it is scanning data with non-default line endings.
1032    24. Changed the definition of CXXLINK to make it agree with the definition of
1033        LINK in the Makefile, by replacing LDFLAGS to CXXFLAGS.
1035    25. Applied Ian Taylor's patches to avoid using another stack frame for tail
1036        recursions. This makes a big different to stack usage for some patterns.
1038    26. If a subpattern containing a named recursion or subroutine reference such
1039        as (?P>B) was quantified, for example (xxx(?P>B)){3}, the calculation of
1040        the space required for the compiled pattern went wrong and gave too small a
1041        value. Depending on the environment, this could lead to "Failed: internal
1042        error: code overflow at offset 49" or "glibc detected double free or
1043        corruption" errors.
1045    27. Applied patches from Google (a) to support the new newline modes and (b) to
1046        advance over multibyte UTF-8 characters in GlobalReplace.
1048    28. Change free() to pcre_free() in pcredemo.c. Apparently this makes a
1049        difference for some implementation of PCRE in some Windows version.
1051    29. Added some extra testing facilities to pcretest:
1053        \q<number>   in a data line sets the "match limit" value
1054        \Q<number>   in a data line sets the "match recursion limt" value
1055        -S <number>  sets the stack size, where <number> is in megabytes
1057        The -S option isn't available for Windows.
1060    Version 6.6 06-Feb-06
1061    ---------------------
1063     1. Change 16(a) for 6.5 broke things, because PCRE_DATA_SCOPE was not defined
1064        in pcreposix.h. I have copied the definition from pcre.h.
1066     2. Change 25 for 6.5 broke compilation in a build directory out-of-tree
1067        because pcre.h is no longer a built file.
1069     3. Added Jeff Friedl's additional debugging patches to pcregrep. These are
1070        not normally included in the compiled code.
1073  Version 6.5 01-Feb-06  Version 6.5 01-Feb-06
1074  ---------------------  ---------------------

Removed from v.87  
changed lines
  Added in v.303

  ViewVC Help
Powered by ViewVC 1.1.5