ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 491 by ph10, Mon Mar 1 17:45:08 2010 UTC revision 753 by ph10, Sat Nov 19 17:03:35 2011 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 8.02 01-Mar-2010  Version 8.21
5    ------------
7    1.  Updating the JIT compiler.
9    2.  JIT compiler now supports OP_NCREF, OP_RREF and OP_NRREF. New test cases
10        are added as well.
12    3.  Fix cache-flush issue on PowerPC (It is still an experimental JIT port).
13        PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before
14        calling _pcre_jit_exec. Some extra comments are added.
16    4.  Mark settings inside atomic groups that do not contain any capturing
17        parentheses, for example, (?>a(*:m)), were not being passed out. This bug
18        was introduced by change 18 for 8.20.
20    5.  Supporting of \x, \U and \u in JavaScript compatibility mode based on the
21        ECMA-262 standard.
23    6.  Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were
24        erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
25        This bug was probably introduced by change 9 of 8.13.
27    7.  While fixing 6 above, I noticed that a number of other items were being
28        incorrectly rejected as "not fixed length". This arose partly because newer
29        opcodes had not been added to the fixed-length checking code. I have (a)
30        corrected the bug and added tests for these items, and (b) arranged for an
31        error to occur if an unknown opcode is encountered while checking for fixed
32        length instead of just assuming "not fixed length". The items that were
33        rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
34        (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
35        repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
37    8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
38        being incorrectly compiled and would have given unpredicatble results.
40    9.  A possessively repeated subpattern with minimum repeat count greater than
41        one behaved incorrectly. For example, (A){2,}+ behaved as if it was
42        (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
43        the first (A) could occur when it should not.
45    10. Add a cast and remove a redundant test from the code.
47    11. JIT should use pcre_malloc/pcre_free for allocation.
49    12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems
50        best practice nowadays, and helps with cross-compiling. (If the exec_prefix
51        is anything other than /usr, -L is still shown).
54    Version 8.20 21-Oct-2011
55    ------------------------
57    1.  Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had
58        a POSIX class. After further experiments with Perl, which convinced me that
59        Perl has bugs and confusions, a closing square bracket is no longer allowed
60        in a POSIX name. This bug also affected patterns with classes that started
61        with full stops.
63    2.  If a pattern such as /(a)b|ac/ is matched against "ac", there is no
64        captured substring, but while checking the failing first alternative,
65        substring 1 is temporarily captured. If the output vector supplied to
66        pcre_exec() was not big enough for this capture, the yield of the function
67        was still zero ("insufficient space for captured substrings"). This cannot
68        be totally fixed without adding another stack variable, which seems a lot
69        of expense for a edge case. However, I have improved the situation in cases
70        such as /(a)(b)x|abc/ matched against "abc", where the return code
71        indicates that fewer than the maximum number of slots in the ovector have
72        been set.
74    3.  Related to (2) above: when there are more back references in a pattern than
75        slots in the output vector, pcre_exec() uses temporary memory during
76        matching, and copies in the captures as far as possible afterwards. It was
77        using the entire output vector, but this conflicts with the specification
78        that only 2/3 is used for passing back captured substrings. Now it uses
79        only the first 2/3, for compatibility. This is, of course, another edge
80        case.
82    4.  Zoltan Herczeg's just-in-time compiler support has been integrated into the
83        main code base, and can be used by building with --enable-jit. When this is
84        done, pcregrep automatically uses it unless --disable-pcregrep-jit or the
85        runtime --no-jit option is given.
87    5.  When the number of matches in a pcre_dfa_exec() run exactly filled the
88        ovector, the return from the function was zero, implying that there were
89        other matches that did not fit. The correct "exactly full" value is now
90        returned.
92    6.  If a subpattern that was called recursively or as a subroutine contained
93        (*PRUNE) or any other control that caused it to give a non-standard return,
94        invalid errors such as "Error -26 (nested recursion at the same subject
95        position)" or even infinite loops could occur.
97    7.  If a pattern such as /a(*SKIP)c|b(*ACCEPT)|/ was studied, it stopped
98        computing the minimum length on reaching *ACCEPT, and so ended up with the
99        wrong value of 1 rather than 0. Further investigation indicates that
100        computing a minimum subject length in the presence of *ACCEPT is difficult
101        (think back references, subroutine calls), and so I have changed the code
102        so that no minimum is registered for a pattern that contains *ACCEPT.
104    8.  If (*THEN) was present in the first (true) branch of a conditional group,
105        it was not handled as intended. [But see 16 below.]
107    9.  Replaced RunTest.bat and CMakeLists.txt with improved versions provided by
108        Sheri Pierce.
110    10. A pathological pattern such as /(*ACCEPT)a/ was miscompiled, thinking that
111        the first byte in a match must be "a".
113    11. Change 17 for 8.13 increased the recursion depth for patterns like
114        /a(?:.)*?a/ drastically. I've improved things by remembering whether a
115        pattern contains any instances of (*THEN). If it does not, the old
116        optimizations are restored. It would be nice to do this on a per-group
117        basis, but at the moment that is not feasible.
119    12. In some environments, the output of pcretest -C is CRLF terminated. This
120        broke RunTest's code that checks for the link size. A single white space
121        character after the value is now allowed for.
123    13. RunTest now checks for the "fr" locale as well as for "fr_FR" and "french".
124        For "fr", it uses the Windows-specific input and output files.
126    14. If (*THEN) appeared in a group that was called recursively or as a
127        subroutine, it did not work as intended. [But see next item.]
129    15. Consider the pattern /A (B(*THEN)C) | D/ where A, B, C, and D are complex
130        pattern fragments (but not containing any | characters). If A and B are
131        matched, but there is a failure in C so that it backtracks to (*THEN), PCRE
132        was behaving differently to Perl. PCRE backtracked into A, but Perl goes to
133        D. In other words, Perl considers parentheses that do not contain any |
134        characters to be part of a surrounding alternative, whereas PCRE was
135        treading (B(*THEN)C) the same as (B(*THEN)C|(*FAIL)) -- which Perl handles
136        differently. PCRE now behaves in the same way as Perl, except in the case
137        of subroutine/recursion calls such as (?1) which have in any case always
138        been different (but PCRE had them first :-).
140    16. Related to 15 above: Perl does not treat the | in a conditional group as
141        creating alternatives. Such a group is treated in the same way as an
142        ordinary group without any | characters when processing (*THEN). PCRE has
143        been changed to match Perl's behaviour.
145    17. If a user had set PCREGREP_COLO(U)R to something other than 1:31, the
146        RunGrepTest script failed.
148    18. Change 22 for version 13 caused atomic groups to use more stack. This is
149        inevitable for groups that contain captures, but it can lead to a lot of
150        stack use in large patterns. The old behaviour has been restored for atomic
151        groups that do not contain any capturing parentheses.
153    19. If the PCRE_NO_START_OPTIMIZE option was set for pcre_compile(), it did not
154        suppress the check for a minimum subject length at run time. (If it was
155        given to pcre_exec() or pcre_dfa_exec() it did work.)
157    20. Fixed an ASCII-dependent infelicity in pcretest that would have made it
158        fail to work when decoding hex characters in data strings in EBCDIC
159        environments.
161    21. It appears that in at least one Mac OS environment, the isxdigit() function
162        is implemented as a macro that evaluates to its argument more than once,
163        contravening the C 90 Standard (I haven't checked a later standard). There
164        was an instance in pcretest which caused it to go wrong when processing
165        \x{...} escapes in subject strings. The has been rewritten to avoid using
166        things like p++ in the argument of isxdigit().
169    Version 8.13 16-Aug-2011
170    ------------------------
172    1.  The Unicode data tables have been updated to Unicode 6.0.0.
174    2.  Two minor typos in pcre_internal.h have been fixed.
176    3.  Added #include <string.h> to pcre_scanner_unittest.cc, pcrecpp.cc, and
177        pcrecpp_unittest.cc. They are needed for strcmp(), memset(), and strchr()
178        in some environments (e.g. Solaris 10/SPARC using Sun Studio 12U2).
180    4.  There were a number of related bugs in the code for matching backrefences
181        caselessly in UTF-8 mode when codes for the characters concerned were
182        different numbers of bytes. For example, U+023A and U+2C65 are an upper
183        and lower case pair, using 2 and 3 bytes, respectively. The main bugs were:
184        (a) A reference to 3 copies of a 2-byte code matched only 2 of a 3-byte
185        code. (b) A reference to 2 copies of a 3-byte code would not match 2 of a
186        2-byte code at the end of the subject (it thought there wasn't enough data
187        left).
189    5.  Comprehensive information about what went wrong is now returned by
190        pcre_exec() and pcre_dfa_exec() when the UTF-8 string check fails, as long
191        as the output vector has at least 2 elements. The offset of the start of
192        the failing character and a reason code are placed in the vector.
194    6.  When the UTF-8 string check fails for pcre_compile(), the offset that is
195        now returned is for the first byte of the failing character, instead of the
196        last byte inspected. This is an incompatible change, but I hope it is small
197        enough not to be a problem. It makes the returned offset consistent with
198        pcre_exec() and pcre_dfa_exec().
200    7.  pcretest now gives a text phrase as well as the error number when
201        pcre_exec() or pcre_dfa_exec() fails; if the error is a UTF-8 check
202        failure, the offset and reason code are output.
204    8.  When \R was used with a maximizing quantifier it failed to skip backwards
205        over a \r\n pair if the subsequent match failed. Instead, it just skipped
206        back over a single character (\n). This seems wrong (because it treated the
207        two characters as a single entity when going forwards), conflicts with the
208        documentation that \R is equivalent to (?>\r\n|\n|...etc), and makes the
209        behaviour of \R* different to (\R)*, which also seems wrong. The behaviour
210        has been changed.
212    9.  Some internal refactoring has changed the processing so that the handling
213        of the PCRE_CASELESS and PCRE_MULTILINE options is done entirely at compile
214        time (the PCRE_DOTALL option was changed this way some time ago: version
215        7.7 change 16). This has made it possible to abolish the OP_OPT op code,
216        which was always a bit of a fudge. It also means that there is one less
217        argument for the match() function, which reduces its stack requirements
218        slightly. This change also fixes an incompatibility with Perl: the pattern
219        (?i:([^b]))(?1) should not match "ab", but previously PCRE gave a match.
221    10. More internal refactoring has drastically reduced the number of recursive
222        calls to match() for possessively repeated groups such as (abc)++ when
223        using pcre_exec().
225    11. While implementing 10, a number of bugs in the handling of groups were
226        discovered and fixed:
228        (?<=(a)+) was not diagnosed as invalid (non-fixed-length lookbehind).
229        (a|)*(?1) gave a compile-time internal error.
230        ((a|)+)+  did not notice that the outer group could match an empty string.
231        (^a|^)+   was not marked as anchored.
232        (.*a|.*)+ was not marked as matching at start or after a newline.
234    12. Yet more internal refactoring has removed another argument from the match()
235        function. Special calls to this function are now indicated by setting a
236        value in a variable in the "match data" data block.
238    13. Be more explicit in pcre_study() instead of relying on "default" for
239        opcodes that mean there is no starting character; this means that when new
240        ones are added and accidentally left out of pcre_study(), testing should
241        pick them up.
243    14. The -s option of pcretest has been documented for ages as being an old
244        synonym of -m (show memory usage). I have changed it to mean "force study
245        for every regex", that is, assume /S for every regex. This is similar to -i
246        and -d etc. It's slightly incompatible, but I'm hoping nobody is still
247        using it. It makes it easier to run collections of tests with and without
248        study enabled, and thereby test pcre_study() more easily. All the standard
249        tests are now run with and without -s (but some patterns can be marked as
250        "never study" - see 20 below).
252    15. When (*ACCEPT) was used in a subpattern that was called recursively, the
253        restoration of the capturing data to the outer values was not happening
254        correctly.
256    16. If a recursively called subpattern ended with (*ACCEPT) and matched an
257        empty string, and PCRE_NOTEMPTY was set, pcre_exec() thought the whole
258        pattern had matched an empty string, and so incorrectly returned a no
259        match.
261    17. There was optimizing code for the last branch of non-capturing parentheses,
262        and also for the obeyed branch of a conditional subexpression, which used
263        tail recursion to cut down on stack usage. Unfortunately, now that there is
264        the possibility of (*THEN) occurring in these branches, tail recursion is
265        no longer possible because the return has to be checked for (*THEN). These
266        two optimizations have therefore been removed. [But see 8.20/11 above.]
268    18. If a pattern containing \R was studied, it was assumed that \R always
269        matched two bytes, thus causing the minimum subject length to be
270        incorrectly computed because \R can also match just one byte.
272    19. If a pattern containing (*ACCEPT) was studied, the minimum subject length
273        was incorrectly computed.
275    20. If /S is present twice on a test pattern in pcretest input, it now
276        *disables* studying, thereby overriding the use of -s on the command line
277        (see 14 above). This is necessary for one or two tests to keep the output
278        identical in both cases.
280    21. When (*ACCEPT) was used in an assertion that matched an empty string and
281        PCRE_NOTEMPTY was set, PCRE applied the non-empty test to the assertion.
283    22. When an atomic group that contained a capturing parenthesis was
284        successfully matched, but the branch in which it appeared failed, the
285        capturing was not being forgotten if a higher numbered group was later
286        captured. For example, /(?>(a))b|(a)c/ when matching "ac" set capturing
287        group 1 to "a", when in fact it should be unset. This applied to multi-
288        branched capturing and non-capturing groups, repeated or not, and also to
289        positive assertions (capturing in negative assertions does not happen
290        in PCRE) and also to nested atomic groups.
292    23. Add the ++ qualifier feature to pcretest, to show the remainder of the
293        subject after a captured substring, to make it easier to tell which of a
294        number of identical substrings has been captured.
296    24. The way atomic groups are processed by pcre_exec() has been changed so that
297        if they are repeated, backtracking one repetition now resets captured
298        values correctly. For example, if ((?>(a+)b)+aabab) is matched against
299        "aaaabaaabaabab" the value of captured group 2 is now correctly recorded as
300        "aaa". Previously, it would have been "a". As part of this code
301        refactoring, the way recursive calls are handled has also been changed.
303    25. If an assertion condition captured any substrings, they were not passed
304        back unless some other capturing happened later. For example, if
305        (?(?=(a))a) was matched against "a", no capturing was returned.
307    26. When studying a pattern that contained subroutine calls or assertions,
308        the code for finding the minimum length of a possible match was handling
309        direct recursions such as (xxx(?1)|yyy) but not mutual recursions (where
310        group 1 called group 2 while simultaneously a separate group 2 called group
311        1). A stack overflow occurred in this case. I have fixed this by limiting
312        the recursion depth to 10.
314    27. Updated RunTest.bat in the distribution to the version supplied by Tom
315        Fortmann. This supports explicit test numbers on the command line, and has
316        argument validation and error reporting.
318    28. An instance of \X with an unlimited repeat could fail if at any point the
319        first character it looked at was a mark character.
321    29. Some minor code refactoring concerning Unicode properties and scripts
322        should reduce the stack requirement of match() slightly.
324    30. Added the '=' option to pcretest to check the setting of unused capturing
325        slots at the end of the pattern, which are documented as being -1, but are
326        not included in the return count.
328    31. If \k was not followed by a braced, angle-bracketed, or quoted name, PCRE
329        compiled something random. Now it gives a compile-time error (as does
330        Perl).
332    32. A *MARK encountered during the processing of a positive assertion is now
333        recorded and passed back (compatible with Perl).
335    33. If --only-matching or --colour was set on a pcregrep call whose pattern
336        had alternative anchored branches, the search for a second match in a line
337        was done as if at the line start. Thus, for example, /^01|^02/ incorrectly
338        matched the line "0102" twice. The same bug affected patterns that started
339        with a backwards assertion. For example /\b01|\b02/ also matched "0102"
340        twice.
342    34. Previously, PCRE did not allow quantification of assertions. However, Perl
343        does, and because of capturing effects, quantifying parenthesized
344        assertions may at times be useful. Quantifiers are now allowed for
345        parenthesized assertions.
347    35. A minor code tidy in pcre_compile() when checking options for \R usage.
349    36. \g was being checked for fancy things in a character class, when it should
350        just be a literal "g".
352    37. PCRE was rejecting [:a[:digit:]] whereas Perl was not. It seems that the
353        appearance of a nested POSIX class supersedes an apparent external class.
354        For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,
355        unescaped square brackets may also appear as part of class names. For
356        example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves
357        more like Perl. (But see 8.20/1 above.)
359    38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this
360        was because it thought it was \N{name}, which is not supported).
362    39. Add minix to OS list not supporting the -S option in pcretest.
364    40. PCRE tries to detect cases of infinite recursion at compile time, but it
365        cannot analyze patterns in sufficient detail to catch mutual recursions
366        such as ((?1))((?2)). There is now a runtime test that gives an error if a
367        subgroup is called recursively as a subpattern for a second time at the
368        same position in the subject string. In previous releases this might have
369        been caught by the recursion limit, or it might have run out of stack.
371    41. A pattern such as /(?(R)a+|(?R)b)/ is quite safe, as the recursion can
372        happen only once. PCRE was, however incorrectly giving a compile time error
373        "recursive call could loop indefinitely" because it cannot analyze the
374        pattern in sufficient detail. The compile time test no longer happens when
375        PCRE is compiling a conditional subpattern, but actual runaway loops are
376        now caught at runtime (see 40 above).
378    42. It seems that Perl allows any characters other than a closing parenthesis
379        to be part of the NAME in (*MARK:NAME) and other backtracking verbs. PCRE
380        has been changed to be the same.
382    43. Updated configure.ac to put in more quoting round AC_LANG_PROGRAM etc. so
383        as not to get warnings when autogen.sh is called. Also changed
384        AC_PROG_LIBTOOL (deprecated) to LT_INIT (the current macro).
386    44. To help people who use pcregrep to scan files containing exceedingly long
387        lines, the following changes have been made:
389        (a) The default value of the buffer size parameter has been increased from
390            8K to 20K. (The actual buffer used is three times this size.)
392        (b) The default can be changed by ./configure --with-pcregrep-bufsize when
393            PCRE is built.
395        (c) A --buffer-size=n option has been added to pcregrep, to allow the size
396            to be set at run time.
398        (d) Numerical values in pcregrep options can be followed by K or M, for
399            example --buffer-size=50K.
401        (e) If a line being scanned overflows pcregrep's buffer, an error is now
402            given and the return code is set to 2.
404    45. Add a pointer to the latest mark to the callout data block.
406    46. The pattern /.(*F)/, when applied to "abc" with PCRE_PARTIAL_HARD, gave a
407        partial match of an empty string instead of no match. This was specific to
408        the use of ".".
410    47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a
411        complete match instead of a partial match. This bug was dependent on both
412        the PCRE_UTF8 and PCRE_DOTALL options being set.
414    48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the
415        starting byte set, because \b was not being ignored.
418    Version 8.12 15-Jan-2011
419    ------------------------
421    1.  Fixed some typos in the markup of the man pages, and wrote a script that
422        checks for such things as part of the documentation building process.
424    2.  On a big-endian 64-bit system, pcregrep did not correctly process the
425        --match-limit and --recursion-limit options (added for 8.11). In
426        particular, this made one of the standard tests fail. (The integer value
427        went into the wrong half of a long int.)
429    3.  If the --colour option was given to pcregrep with -v (invert match), it
430        did strange things, either producing crazy output, or crashing. It should,
431        of course, ignore a request for colour when reporting lines that do not
432        match.
434    4.  Another pcregrep bug caused similar problems if --colour was specified with
435        -M (multiline) and the pattern match finished with a line ending.
437    5.  In pcregrep, when a pattern that ended with a literal newline sequence was
438        matched in multiline mode, the following line was shown as part of the
439        match. This seems wrong, so I have changed it.
441    6.  Another pcregrep bug in multiline mode, when --colour was specified, caused
442        the check for further matches in the same line (so they could be coloured)
443        to overrun the end of the current line. If another match was found, it was
444        incorrectly shown (and then shown again when found in the next line).
446    7.  If pcregrep was compiled under Windows, there was a reference to the
447        function pcregrep_exit() before it was defined. I am assuming this was
448        the cause of the "error C2371: 'pcregrep_exit' : redefinition;" that was
449        reported by a user. I've moved the definition above the reference.
452    Version 8.11 10-Dec-2010
453    ------------------------
455    1.  (*THEN) was not working properly if there were untried alternatives prior
456        to it in the current branch. For example, in ((a|b)(*THEN)(*F)|c..) it
457        backtracked to try for "b" instead of moving to the next alternative branch
458        at the same level (in this case, to look for "c"). The Perl documentation
459        is clear that when (*THEN) is backtracked onto, it goes to the "next
460        alternative in the innermost enclosing group".
462    2.  (*COMMIT) was not overriding (*THEN), as it does in Perl. In a pattern
463        such as   (A(*COMMIT)B(*THEN)C|D)  any failure after matching A should
464        result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and
465        (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides
466        (*THEN).
468    3.  If \s appeared in a character class, it removed the VT character from
469        the class, even if it had been included by some previous item, for example
470        in [\x00-\xff\s]. (This was a bug related to the fact that VT is not part
471        of \s, but is part of the POSIX "space" class.)
473    4.  A partial match never returns an empty string (because you can always
474        match an empty string at the end of the subject); however the checking for
475        an empty string was starting at the "start of match" point. This has been
476        changed to the "earliest inspected character" point, because the returned
477        data for a partial match starts at this character. This means that, for
478        example, /(?<=abc)def/ gives a partial match for the subject "abc"
479        (previously it gave "no match").
481    5.  Changes have been made to the way PCRE_PARTIAL_HARD affects the matching
482        of $, \z, \Z, \b, and \B. If the match point is at the end of the string,
483        previously a full match would be given. However, setting PCRE_PARTIAL_HARD
484        has an implication that the given string is incomplete (because a partial
485        match is preferred over a full match). For this reason, these items now
486        give a partial match in this situation. [Aside: previously, the one case
487        /t\b/ matched against "cat" with PCRE_PARTIAL_HARD set did return a partial
488        match rather than a full match, which was wrong by the old rules, but is
489        now correct.]
491    6.  There was a bug in the handling of #-introduced comments, recognized when
492        PCRE_EXTENDED is set, when PCRE_NEWLINE_ANY and PCRE_UTF8 were also set.
493        If a UTF-8 multi-byte character included the byte 0x85 (e.g. +U0445, whose
494        UTF-8 encoding is 0xd1,0x85), this was misinterpreted as a newline when
495        scanning for the end of the comment. (*Character* 0x85 is an "any" newline,
496        but *byte* 0x85 is not, in UTF-8 mode). This bug was present in several
497        places in pcre_compile().
499    7.  Related to (6) above, when pcre_compile() was skipping #-introduced
500        comments when looking ahead for named forward references to subpatterns,
501        the only newline sequence it recognized was NL. It now handles newlines
502        according to the set newline convention.
504    8.  SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the
505        former, but used strtoul(), whereas pcretest avoided strtoul() but did not
506        cater for a lack of strerror(). These oversights have been fixed.
508    9.  Added --match-limit and --recursion-limit to pcregrep.
510    10. Added two casts needed to build with Visual Studio when NO_RECURSE is set.
512    11. When the -o option was used, pcregrep was setting a return code of 1, even
513        when matches were found, and --line-buffered was not being honoured.
515    12. Added an optional parentheses number to the -o and --only-matching options
516        of pcregrep.
518    13. Imitating Perl's /g action for multiple matches is tricky when the pattern
519        can match an empty string. The code to do it in pcretest and pcredemo
520        needed fixing:
522        (a) When the newline convention was "crlf", pcretest got it wrong, skipping
523            only one byte after an empty string match just before CRLF (this case
524            just got forgotten; "any" and "anycrlf" were OK).
526        (b) The pcretest code also had a bug, causing it to loop forever in UTF-8
527            mode when an empty string match preceded an ASCII character followed by
528            a non-ASCII character. (The code for advancing by one character rather
529            than one byte was nonsense.)
531        (c) The pcredemo.c sample program did not have any code at all to handle
532            the cases when CRLF is a valid newline sequence.
534    14. Neither pcre_exec() nor pcre_dfa_exec() was checking that the value given
535        as a starting offset was within the subject string. There is now a new
536        error, PCRE_ERROR_BADOFFSET, which is returned if the starting offset is
537        negative or greater than the length of the string. In order to test this,
538        pcretest is extended to allow the setting of negative starting offsets.
540    15. In both pcre_exec() and pcre_dfa_exec() the code for checking that the
541        starting offset points to the beginning of a UTF-8 character was
542        unnecessarily clumsy. I tidied it up.
544    16. Added PCRE_ERROR_SHORTUTF8 to make it possible to distinguish between a
545        bad UTF-8 sequence and one that is incomplete when using PCRE_PARTIAL_HARD.
547    17. Nobody had reported that the --include_dir option, which was added in
548        release 7.7 should have been called --include-dir (hyphen, not underscore)
549        for compatibility with GNU grep. I have changed it to --include-dir, but
550        left --include_dir as an undocumented synonym, and the same for
551        --exclude-dir, though that is not available in GNU grep, at least as of
552        release 2.5.4.
554    18. At a user's suggestion, the macros GETCHAR and friends (which pick up UTF-8
555        characters from a string of bytes) have been redefined so as not to use
556        loops, in order to improve performance in some environments. At the same
557        time, I abstracted some of the common code into auxiliary macros to save
558        repetition (this should not affect the compiled code).
560    19. If \c was followed by a multibyte UTF-8 character, bad things happened. A
561        compile-time error is now given if \c is not followed by an ASCII
562        character, that is, a byte less than 128. (In EBCDIC mode, the code is
563        different, and any byte value is allowed.)
565    20. Recognize (*NO_START_OPT) at the start of a pattern to set the PCRE_NO_
566        START_OPTIMIZE option, which is now allowed at compile time - but just
567        passed through to pcre_exec() or pcre_dfa_exec(). This makes it available
568        to pcregrep and other applications that have no direct access to PCRE
569        options. The new /Y option in pcretest sets this option when calling
570        pcre_compile().
572    21. Change 18 of release 8.01 broke the use of named subpatterns for recursive
573        back references. Groups containing recursive back references were forced to
574        be atomic by that change, but in the case of named groups, the amount of
575        memory required was incorrectly computed, leading to "Failed: internal
576        error: code overflow". This has been fixed.
578    22. Some patches to pcre_stringpiece.h, pcre_stringpiece_unittest.cc, and
579        pcretest.c, to avoid build problems in some Borland environments.
582    Version 8.10 25-Jun-2010
583    ------------------------
585    1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and
586        THEN.
588    2.  (*ACCEPT) was not working when inside an atomic group.
590    3.  Inside a character class, \B is treated as a literal by default, but
591        faulted if PCRE_EXTRA is set. This mimics Perl's behaviour (the -w option
592        causes the error). The code is unchanged, but I tidied the documentation.
594    4.  Inside a character class, PCRE always treated \R and \X as literals,
595        whereas Perl faults them if its -w option is set. I have changed PCRE so
596        that it faults them when PCRE_EXTRA is set.
598    5.  Added support for \N, which always matches any character other than
599        newline. (It is the same as "." when PCRE_DOTALL is not set.)
601    6.  When compiling pcregrep with newer versions of gcc which may have
602        FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',
603        declared with attribute warn_unused_result" were given. Just casting the
604        result to (void) does not stop the warnings; a more elaborate fudge is
605        needed. I've used a macro to implement this.
607    7.  Minor change to pcretest.c to avoid a compiler warning.
609    8.  Added four artifical Unicode properties to help with an option to make
610        \s etc use properties (see next item). The new properties are: Xan
611        (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).
613    9.  Added PCRE_UCP to make \b, \d, \s, \w, and certain POSIX character classes
614        use Unicode properties. (*UCP) at the start of a pattern can be used to set
615        this option. Modified pcretest to add /W to test this facility. Added
616        REG_UCP to make it available via the POSIX interface.
618    10. Added --line-buffered to pcregrep.
620    11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was
621        studied, and the match started with a letter with a code point greater than
622        127 whose first byte was different to the first byte of the other case of
623        the letter, the other case of this starting letter was not recognized
624        (#976).
626    12. If a pattern that was studied started with a repeated Unicode property
627        test, for example, \p{Nd}+, there was the theoretical possibility of
628        setting up an incorrect bitmap of starting bytes, but fortunately it could
629        not have actually happened in practice until change 8 above was made (it
630        added property types that matched character-matching opcodes).
632    13. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
633        possible starting bytes for non-anchored patterns.
635    14. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes
636        \R, and also a number of cases that involve Unicode properties, both
637        explicit and implicit when PCRE_UCP is set.
639    15. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8
640        input, it could crash or give wrong results if characters with values
641        greater than 0xc0 were present in the subject string. (Detail: it assumed
642        UTF-8 input when processing these items.)
644    16. Added a lot of (int) casts to avoid compiler warnings in systems where
645        size_t is 64-bit (#991).
647    17. Added a check for running out of memory when PCRE is compiled with
648        --disable-stack-for-recursion (#990).
650    18. If the last data line in a file for pcretest does not have a newline on
651        the end, a newline was missing in the output.
653    19. The default pcre_chartables.c file recognizes only ASCII characters (values
654        less than 128) in its various bitmaps. However, there is a facility for
655        generating tables according to the current locale when PCRE is compiled. It
656        turns out that in some environments, 0x85 and 0xa0, which are Unicode space
657        characters, are recognized by isspace() and therefore were getting set in
658        these tables, and indeed these tables seem to approximate to ISO 8859. This
659        caused a problem in UTF-8 mode when pcre_study() was used to create a list
660        of bytes that can start a match. For \s, it was including 0x85 and 0xa0,
661        which of course cannot start UTF-8 characters. I have changed the code so
662        that only real ASCII characters (less than 128) and the correct starting
663        bytes for UTF-8 encodings are set for characters greater than 127 when in
664        UTF-8 mode. (When PCRE_UCP is set - see 9 above - the code is different
665        altogether.)
667    20. Added the /T option to pcretest so as to be able to run tests with non-
668        standard character tables, thus making it possible to include the tests
669        used for 19 above in the standard set of tests.
671    21. A pattern such as (?&t)(?#()(?(DEFINE)(?<t>a)) which has a forward
672        reference to a subpattern the other side of a comment that contains an
673        opening parenthesis caused either an internal compiling error, or a
674        reference to the wrong subpattern.
677    Version 8.02 19-Mar-2010
678  ------------------------  ------------------------
680  1.  The Unicode data tables have been updated to Unicode 5.2.0.  1.  The Unicode data tables have been updated to Unicode 5.2.0.
682    2.  Added the option --libs-cpp to pcre-config, but only when C++ support is
683        configured.
685    3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the
686        original author of that file, following a query about its status.
688    4.  On systems that do not have stdint.h (e.g. Solaris), check for and include
689        inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
691    5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
692        quantifier applied to a forward-referencing subroutine call, could compile
693        incorrect code or give the error "internal error: previously-checked
694        referenced subpattern not found".
696    6.  Both MS Visual Studio and Symbian OS have problems with initializing
697        variables to point to external functions. For these systems, therefore,
698        pcre_malloc etc. are now initialized to local functions that call the
699        relevant global functions.
701    7.  There were two entries missing in the vectors called coptable and poptable
702        in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.
703        I've fixed the data, and added a kludgy way of testing at compile time that
704        the lengths are correct (equal to the number of opcodes).
706    8.  Following on from 7, I added a similar kludge to check the length of the
707        eint vector in pcreposix.c.
709    9.  Error texts for pcre_compile() are held as one long string to avoid too
710        much relocation at load time. To find a text, the string is searched,
711        counting zeros. There was no check for running off the end of the string,
712        which could happen if a new error number was added without updating the
713        string.
715    10. \K gave a compile-time error if it appeared in a lookbehind assersion.
717    11. \K was not working if it appeared in an atomic group or in a group that
718        was called as a "subroutine", or in an assertion. Perl 5.11 documents that
719        \K is "not well defined" if used in an assertion. PCRE now accepts it if
720        the assertion is positive, but not if it is negative.
722    12. Change 11 fortuitously reduced the size of the stack frame used in the
723        "match()" function of pcre_exec.c by one pointer. Forthcoming
724        implementation of support for (*MARK) will need an extra pointer on the
725        stack; I have reserved it now, so that the stack frame size does not
726        decrease.
728    13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other
729        item in branch that calls a recursion is a subroutine call - as in the
730        second branch in the above example - was incorrectly given the compile-
731        time error "recursive call could loop indefinitely" because pcre_compile()
732        was not correctly checking the subroutine for matching a non-empty string.
734    14. The checks for overrunning compiling workspace could trigger after an
735        overrun had occurred. This is a "should never occur" error, but it can be
736        triggered by pathological patterns such as hundreds of nested parentheses.
737        The checks now trigger 100 bytes before the end of the workspace.
739    15. Fix typo in configure.ac: "srtoq" should be "strtoq".
742  Version 8.01 19-Jan-2010  Version 8.01 19-Jan-2010
743  ------------------------  ------------------------

Removed from v.491  
changed lines
  Added in v.753

  ViewVC Help
Powered by ViewVC 1.1.5