ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 545 by ph10, Wed Jun 16 10:51:15 2010 UTC revision 747 by ph10, Tue Nov 15 17:35:10 2011 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 8.10 16-Jun-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.
38    Version 8.20 21-Oct-2011
39    ------------------------
41    1.  Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had
42        a POSIX class. After further experiments with Perl, which convinced me that
43        Perl has bugs and confusions, a closing square bracket is no longer allowed
44        in a POSIX name. This bug also affected patterns with classes that started
45        with full stops.
47    2.  If a pattern such as /(a)b|ac/ is matched against "ac", there is no
48        captured substring, but while checking the failing first alternative,
49        substring 1 is temporarily captured. If the output vector supplied to
50        pcre_exec() was not big enough for this capture, the yield of the function
51        was still zero ("insufficient space for captured substrings"). This cannot
52        be totally fixed without adding another stack variable, which seems a lot
53        of expense for a edge case. However, I have improved the situation in cases
54        such as /(a)(b)x|abc/ matched against "abc", where the return code
55        indicates that fewer than the maximum number of slots in the ovector have
56        been set.
58    3.  Related to (2) above: when there are more back references in a pattern than
59        slots in the output vector, pcre_exec() uses temporary memory during
60        matching, and copies in the captures as far as possible afterwards. It was
61        using the entire output vector, but this conflicts with the specification
62        that only 2/3 is used for passing back captured substrings. Now it uses
63        only the first 2/3, for compatibility. This is, of course, another edge
64        case.
66    4.  Zoltan Herczeg's just-in-time compiler support has been integrated into the
67        main code base, and can be used by building with --enable-jit. When this is
68        done, pcregrep automatically uses it unless --disable-pcregrep-jit or the
69        runtime --no-jit option is given.
71    5.  When the number of matches in a pcre_dfa_exec() run exactly filled the
72        ovector, the return from the function was zero, implying that there were
73        other matches that did not fit. The correct "exactly full" value is now
74        returned.
76    6.  If a subpattern that was called recursively or as a subroutine contained
77        (*PRUNE) or any other control that caused it to give a non-standard return,
78        invalid errors such as "Error -26 (nested recursion at the same subject
79        position)" or even infinite loops could occur.
81    7.  If a pattern such as /a(*SKIP)c|b(*ACCEPT)|/ was studied, it stopped
82        computing the minimum length on reaching *ACCEPT, and so ended up with the
83        wrong value of 1 rather than 0. Further investigation indicates that
84        computing a minimum subject length in the presence of *ACCEPT is difficult
85        (think back references, subroutine calls), and so I have changed the code
86        so that no minimum is registered for a pattern that contains *ACCEPT.
88    8.  If (*THEN) was present in the first (true) branch of a conditional group,
89        it was not handled as intended. [But see 16 below.]
91    9.  Replaced RunTest.bat and CMakeLists.txt with improved versions provided by
92        Sheri Pierce.
94    10. A pathological pattern such as /(*ACCEPT)a/ was miscompiled, thinking that
95        the first byte in a match must be "a".
97    11. Change 17 for 8.13 increased the recursion depth for patterns like
98        /a(?:.)*?a/ drastically. I've improved things by remembering whether a
99        pattern contains any instances of (*THEN). If it does not, the old
100        optimizations are restored. It would be nice to do this on a per-group
101        basis, but at the moment that is not feasible.
103    12. In some environments, the output of pcretest -C is CRLF terminated. This
104        broke RunTest's code that checks for the link size. A single white space
105        character after the value is now allowed for.
107    13. RunTest now checks for the "fr" locale as well as for "fr_FR" and "french".
108        For "fr", it uses the Windows-specific input and output files.
110    14. If (*THEN) appeared in a group that was called recursively or as a
111        subroutine, it did not work as intended. [But see next item.]
113    15. Consider the pattern /A (B(*THEN)C) | D/ where A, B, C, and D are complex
114        pattern fragments (but not containing any | characters). If A and B are
115        matched, but there is a failure in C so that it backtracks to (*THEN), PCRE
116        was behaving differently to Perl. PCRE backtracked into A, but Perl goes to
117        D. In other words, Perl considers parentheses that do not contain any |
118        characters to be part of a surrounding alternative, whereas PCRE was
119        treading (B(*THEN)C) the same as (B(*THEN)C|(*FAIL)) -- which Perl handles
120        differently. PCRE now behaves in the same way as Perl, except in the case
121        of subroutine/recursion calls such as (?1) which have in any case always
122        been different (but PCRE had them first :-).
124    16. Related to 15 above: Perl does not treat the | in a conditional group as
125        creating alternatives. Such a group is treated in the same way as an
126        ordinary group without any | characters when processing (*THEN). PCRE has
127        been changed to match Perl's behaviour.
129    17. If a user had set PCREGREP_COLO(U)R to something other than 1:31, the
130        RunGrepTest script failed.
132    18. Change 22 for version 13 caused atomic groups to use more stack. This is
133        inevitable for groups that contain captures, but it can lead to a lot of
134        stack use in large patterns. The old behaviour has been restored for atomic
135        groups that do not contain any capturing parentheses.
137    19. If the PCRE_NO_START_OPTIMIZE option was set for pcre_compile(), it did not
138        suppress the check for a minimum subject length at run time. (If it was
139        given to pcre_exec() or pcre_dfa_exec() it did work.)
141    20. Fixed an ASCII-dependent infelicity in pcretest that would have made it
142        fail to work when decoding hex characters in data strings in EBCDIC
143        environments.
145    21. It appears that in at least one Mac OS environment, the isxdigit() function
146        is implemented as a macro that evaluates to its argument more than once,
147        contravening the C 90 Standard (I haven't checked a later standard). There
148        was an instance in pcretest which caused it to go wrong when processing
149        \x{...} escapes in subject strings. The has been rewritten to avoid using
150        things like p++ in the argument of isxdigit().
153    Version 8.13 16-Aug-2011
154    ------------------------
156    1.  The Unicode data tables have been updated to Unicode 6.0.0.
158    2.  Two minor typos in pcre_internal.h have been fixed.
160    3.  Added #include <string.h> to pcre_scanner_unittest.cc, pcrecpp.cc, and
161        pcrecpp_unittest.cc. They are needed for strcmp(), memset(), and strchr()
162        in some environments (e.g. Solaris 10/SPARC using Sun Studio 12U2).
164    4.  There were a number of related bugs in the code for matching backrefences
165        caselessly in UTF-8 mode when codes for the characters concerned were
166        different numbers of bytes. For example, U+023A and U+2C65 are an upper
167        and lower case pair, using 2 and 3 bytes, respectively. The main bugs were:
168        (a) A reference to 3 copies of a 2-byte code matched only 2 of a 3-byte
169        code. (b) A reference to 2 copies of a 3-byte code would not match 2 of a
170        2-byte code at the end of the subject (it thought there wasn't enough data
171        left).
173    5.  Comprehensive information about what went wrong is now returned by
174        pcre_exec() and pcre_dfa_exec() when the UTF-8 string check fails, as long
175        as the output vector has at least 2 elements. The offset of the start of
176        the failing character and a reason code are placed in the vector.
178    6.  When the UTF-8 string check fails for pcre_compile(), the offset that is
179        now returned is for the first byte of the failing character, instead of the
180        last byte inspected. This is an incompatible change, but I hope it is small
181        enough not to be a problem. It makes the returned offset consistent with
182        pcre_exec() and pcre_dfa_exec().
184    7.  pcretest now gives a text phrase as well as the error number when
185        pcre_exec() or pcre_dfa_exec() fails; if the error is a UTF-8 check
186        failure, the offset and reason code are output.
188    8.  When \R was used with a maximizing quantifier it failed to skip backwards
189        over a \r\n pair if the subsequent match failed. Instead, it just skipped
190        back over a single character (\n). This seems wrong (because it treated the
191        two characters as a single entity when going forwards), conflicts with the
192        documentation that \R is equivalent to (?>\r\n|\n|...etc), and makes the
193        behaviour of \R* different to (\R)*, which also seems wrong. The behaviour
194        has been changed.
196    9.  Some internal refactoring has changed the processing so that the handling
197        of the PCRE_CASELESS and PCRE_MULTILINE options is done entirely at compile
198        time (the PCRE_DOTALL option was changed this way some time ago: version
199        7.7 change 16). This has made it possible to abolish the OP_OPT op code,
200        which was always a bit of a fudge. It also means that there is one less
201        argument for the match() function, which reduces its stack requirements
202        slightly. This change also fixes an incompatibility with Perl: the pattern
203        (?i:([^b]))(?1) should not match "ab", but previously PCRE gave a match.
205    10. More internal refactoring has drastically reduced the number of recursive
206        calls to match() for possessively repeated groups such as (abc)++ when
207        using pcre_exec().
209    11. While implementing 10, a number of bugs in the handling of groups were
210        discovered and fixed:
212        (?<=(a)+) was not diagnosed as invalid (non-fixed-length lookbehind).
213        (a|)*(?1) gave a compile-time internal error.
214        ((a|)+)+  did not notice that the outer group could match an empty string.
215        (^a|^)+   was not marked as anchored.
216        (.*a|.*)+ was not marked as matching at start or after a newline.
218    12. Yet more internal refactoring has removed another argument from the match()
219        function. Special calls to this function are now indicated by setting a
220        value in a variable in the "match data" data block.
222    13. Be more explicit in pcre_study() instead of relying on "default" for
223        opcodes that mean there is no starting character; this means that when new
224        ones are added and accidentally left out of pcre_study(), testing should
225        pick them up.
227    14. The -s option of pcretest has been documented for ages as being an old
228        synonym of -m (show memory usage). I have changed it to mean "force study
229        for every regex", that is, assume /S for every regex. This is similar to -i
230        and -d etc. It's slightly incompatible, but I'm hoping nobody is still
231        using it. It makes it easier to run collections of tests with and without
232        study enabled, and thereby test pcre_study() more easily. All the standard
233        tests are now run with and without -s (but some patterns can be marked as
234        "never study" - see 20 below).
236    15. When (*ACCEPT) was used in a subpattern that was called recursively, the
237        restoration of the capturing data to the outer values was not happening
238        correctly.
240    16. If a recursively called subpattern ended with (*ACCEPT) and matched an
241        empty string, and PCRE_NOTEMPTY was set, pcre_exec() thought the whole
242        pattern had matched an empty string, and so incorrectly returned a no
243        match.
245    17. There was optimizing code for the last branch of non-capturing parentheses,
246        and also for the obeyed branch of a conditional subexpression, which used
247        tail recursion to cut down on stack usage. Unfortunately, now that there is
248        the possibility of (*THEN) occurring in these branches, tail recursion is
249        no longer possible because the return has to be checked for (*THEN). These
250        two optimizations have therefore been removed. [But see 8.20/11 above.]
252    18. If a pattern containing \R was studied, it was assumed that \R always
253        matched two bytes, thus causing the minimum subject length to be
254        incorrectly computed because \R can also match just one byte.
256    19. If a pattern containing (*ACCEPT) was studied, the minimum subject length
257        was incorrectly computed.
259    20. If /S is present twice on a test pattern in pcretest input, it now
260        *disables* studying, thereby overriding the use of -s on the command line
261        (see 14 above). This is necessary for one or two tests to keep the output
262        identical in both cases.
264    21. When (*ACCEPT) was used in an assertion that matched an empty string and
265        PCRE_NOTEMPTY was set, PCRE applied the non-empty test to the assertion.
267    22. When an atomic group that contained a capturing parenthesis was
268        successfully matched, but the branch in which it appeared failed, the
269        capturing was not being forgotten if a higher numbered group was later
270        captured. For example, /(?>(a))b|(a)c/ when matching "ac" set capturing
271        group 1 to "a", when in fact it should be unset. This applied to multi-
272        branched capturing and non-capturing groups, repeated or not, and also to
273        positive assertions (capturing in negative assertions does not happen
274        in PCRE) and also to nested atomic groups.
276    23. Add the ++ qualifier feature to pcretest, to show the remainder of the
277        subject after a captured substring, to make it easier to tell which of a
278        number of identical substrings has been captured.
280    24. The way atomic groups are processed by pcre_exec() has been changed so that
281        if they are repeated, backtracking one repetition now resets captured
282        values correctly. For example, if ((?>(a+)b)+aabab) is matched against
283        "aaaabaaabaabab" the value of captured group 2 is now correctly recorded as
284        "aaa". Previously, it would have been "a". As part of this code
285        refactoring, the way recursive calls are handled has also been changed.
287    25. If an assertion condition captured any substrings, they were not passed
288        back unless some other capturing happened later. For example, if
289        (?(?=(a))a) was matched against "a", no capturing was returned.
291    26. When studying a pattern that contained subroutine calls or assertions,
292        the code for finding the minimum length of a possible match was handling
293        direct recursions such as (xxx(?1)|yyy) but not mutual recursions (where
294        group 1 called group 2 while simultaneously a separate group 2 called group
295        1). A stack overflow occurred in this case. I have fixed this by limiting
296        the recursion depth to 10.
298    27. Updated RunTest.bat in the distribution to the version supplied by Tom
299        Fortmann. This supports explicit test numbers on the command line, and has
300        argument validation and error reporting.
302    28. An instance of \X with an unlimited repeat could fail if at any point the
303        first character it looked at was a mark character.
305    29. Some minor code refactoring concerning Unicode properties and scripts
306        should reduce the stack requirement of match() slightly.
308    30. Added the '=' option to pcretest to check the setting of unused capturing
309        slots at the end of the pattern, which are documented as being -1, but are
310        not included in the return count.
312    31. If \k was not followed by a braced, angle-bracketed, or quoted name, PCRE
313        compiled something random. Now it gives a compile-time error (as does
314        Perl).
316    32. A *MARK encountered during the processing of a positive assertion is now
317        recorded and passed back (compatible with Perl).
319    33. If --only-matching or --colour was set on a pcregrep call whose pattern
320        had alternative anchored branches, the search for a second match in a line
321        was done as if at the line start. Thus, for example, /^01|^02/ incorrectly
322        matched the line "0102" twice. The same bug affected patterns that started
323        with a backwards assertion. For example /\b01|\b02/ also matched "0102"
324        twice.
326    34. Previously, PCRE did not allow quantification of assertions. However, Perl
327        does, and because of capturing effects, quantifying parenthesized
328        assertions may at times be useful. Quantifiers are now allowed for
329        parenthesized assertions.
331    35. A minor code tidy in pcre_compile() when checking options for \R usage.
333    36. \g was being checked for fancy things in a character class, when it should
334        just be a literal "g".
336    37. PCRE was rejecting [:a[:digit:]] whereas Perl was not. It seems that the
337        appearance of a nested POSIX class supersedes an apparent external class.
338        For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,
339        unescaped square brackets may also appear as part of class names. For
340        example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves
341        more like Perl. (But see 8.20/1 above.)
343    38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this
344        was because it thought it was \N{name}, which is not supported).
346    39. Add minix to OS list not supporting the -S option in pcretest.
348    40. PCRE tries to detect cases of infinite recursion at compile time, but it
349        cannot analyze patterns in sufficient detail to catch mutual recursions
350        such as ((?1))((?2)). There is now a runtime test that gives an error if a
351        subgroup is called recursively as a subpattern for a second time at the
352        same position in the subject string. In previous releases this might have
353        been caught by the recursion limit, or it might have run out of stack.
355    41. A pattern such as /(?(R)a+|(?R)b)/ is quite safe, as the recursion can
356        happen only once. PCRE was, however incorrectly giving a compile time error
357        "recursive call could loop indefinitely" because it cannot analyze the
358        pattern in sufficient detail. The compile time test no longer happens when
359        PCRE is compiling a conditional subpattern, but actual runaway loops are
360        now caught at runtime (see 40 above).
362    42. It seems that Perl allows any characters other than a closing parenthesis
363        to be part of the NAME in (*MARK:NAME) and other backtracking verbs. PCRE
364        has been changed to be the same.
366    43. Updated configure.ac to put in more quoting round AC_LANG_PROGRAM etc. so
367        as not to get warnings when autogen.sh is called. Also changed
368        AC_PROG_LIBTOOL (deprecated) to LT_INIT (the current macro).
370    44. To help people who use pcregrep to scan files containing exceedingly long
371        lines, the following changes have been made:
373        (a) The default value of the buffer size parameter has been increased from
374            8K to 20K. (The actual buffer used is three times this size.)
376        (b) The default can be changed by ./configure --with-pcregrep-bufsize when
377            PCRE is built.
379        (c) A --buffer-size=n option has been added to pcregrep, to allow the size
380            to be set at run time.
382        (d) Numerical values in pcregrep options can be followed by K or M, for
383            example --buffer-size=50K.
385        (e) If a line being scanned overflows pcregrep's buffer, an error is now
386            given and the return code is set to 2.
388    45. Add a pointer to the latest mark to the callout data block.
390    46. The pattern /.(*F)/, when applied to "abc" with PCRE_PARTIAL_HARD, gave a
391        partial match of an empty string instead of no match. This was specific to
392        the use of ".".
394    47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a
395        complete match instead of a partial match. This bug was dependent on both
396        the PCRE_UTF8 and PCRE_DOTALL options being set.
398    48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the
399        starting byte set, because \b was not being ignored.
402    Version 8.12 15-Jan-2011
403    ------------------------
405    1.  Fixed some typos in the markup of the man pages, and wrote a script that
406        checks for such things as part of the documentation building process.
408    2.  On a big-endian 64-bit system, pcregrep did not correctly process the
409        --match-limit and --recursion-limit options (added for 8.11). In
410        particular, this made one of the standard tests fail. (The integer value
411        went into the wrong half of a long int.)
413    3.  If the --colour option was given to pcregrep with -v (invert match), it
414        did strange things, either producing crazy output, or crashing. It should,
415        of course, ignore a request for colour when reporting lines that do not
416        match.
418    4.  Another pcregrep bug caused similar problems if --colour was specified with
419        -M (multiline) and the pattern match finished with a line ending.
421    5.  In pcregrep, when a pattern that ended with a literal newline sequence was
422        matched in multiline mode, the following line was shown as part of the
423        match. This seems wrong, so I have changed it.
425    6.  Another pcregrep bug in multiline mode, when --colour was specified, caused
426        the check for further matches in the same line (so they could be coloured)
427        to overrun the end of the current line. If another match was found, it was
428        incorrectly shown (and then shown again when found in the next line).
430    7.  If pcregrep was compiled under Windows, there was a reference to the
431        function pcregrep_exit() before it was defined. I am assuming this was
432        the cause of the "error C2371: 'pcregrep_exit' : redefinition;" that was
433        reported by a user. I've moved the definition above the reference.
436    Version 8.11 10-Dec-2010
437    ------------------------
439    1.  (*THEN) was not working properly if there were untried alternatives prior
440        to it in the current branch. For example, in ((a|b)(*THEN)(*F)|c..) it
441        backtracked to try for "b" instead of moving to the next alternative branch
442        at the same level (in this case, to look for "c"). The Perl documentation
443        is clear that when (*THEN) is backtracked onto, it goes to the "next
444        alternative in the innermost enclosing group".
446    2.  (*COMMIT) was not overriding (*THEN), as it does in Perl. In a pattern
447        such as   (A(*COMMIT)B(*THEN)C|D)  any failure after matching A should
448        result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and
449        (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides
450        (*THEN).
452    3.  If \s appeared in a character class, it removed the VT character from
453        the class, even if it had been included by some previous item, for example
454        in [\x00-\xff\s]. (This was a bug related to the fact that VT is not part
455        of \s, but is part of the POSIX "space" class.)
457    4.  A partial match never returns an empty string (because you can always
458        match an empty string at the end of the subject); however the checking for
459        an empty string was starting at the "start of match" point. This has been
460        changed to the "earliest inspected character" point, because the returned
461        data for a partial match starts at this character. This means that, for
462        example, /(?<=abc)def/ gives a partial match for the subject "abc"
463        (previously it gave "no match").
465    5.  Changes have been made to the way PCRE_PARTIAL_HARD affects the matching
466        of $, \z, \Z, \b, and \B. If the match point is at the end of the string,
467        previously a full match would be given. However, setting PCRE_PARTIAL_HARD
468        has an implication that the given string is incomplete (because a partial
469        match is preferred over a full match). For this reason, these items now
470        give a partial match in this situation. [Aside: previously, the one case
471        /t\b/ matched against "cat" with PCRE_PARTIAL_HARD set did return a partial
472        match rather than a full match, which was wrong by the old rules, but is
473        now correct.]
475    6.  There was a bug in the handling of #-introduced comments, recognized when
476        PCRE_EXTENDED is set, when PCRE_NEWLINE_ANY and PCRE_UTF8 were also set.
477        If a UTF-8 multi-byte character included the byte 0x85 (e.g. +U0445, whose
478        UTF-8 encoding is 0xd1,0x85), this was misinterpreted as a newline when
479        scanning for the end of the comment. (*Character* 0x85 is an "any" newline,
480        but *byte* 0x85 is not, in UTF-8 mode). This bug was present in several
481        places in pcre_compile().
483    7.  Related to (6) above, when pcre_compile() was skipping #-introduced
484        comments when looking ahead for named forward references to subpatterns,
485        the only newline sequence it recognized was NL. It now handles newlines
486        according to the set newline convention.
488    8.  SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the
489        former, but used strtoul(), whereas pcretest avoided strtoul() but did not
490        cater for a lack of strerror(). These oversights have been fixed.
492    9.  Added --match-limit and --recursion-limit to pcregrep.
494    10. Added two casts needed to build with Visual Studio when NO_RECURSE is set.
496    11. When the -o option was used, pcregrep was setting a return code of 1, even
497        when matches were found, and --line-buffered was not being honoured.
499    12. Added an optional parentheses number to the -o and --only-matching options
500        of pcregrep.
502    13. Imitating Perl's /g action for multiple matches is tricky when the pattern
503        can match an empty string. The code to do it in pcretest and pcredemo
504        needed fixing:
506        (a) When the newline convention was "crlf", pcretest got it wrong, skipping
507            only one byte after an empty string match just before CRLF (this case
508            just got forgotten; "any" and "anycrlf" were OK).
510        (b) The pcretest code also had a bug, causing it to loop forever in UTF-8
511            mode when an empty string match preceded an ASCII character followed by
512            a non-ASCII character. (The code for advancing by one character rather
513            than one byte was nonsense.)
515        (c) The pcredemo.c sample program did not have any code at all to handle
516            the cases when CRLF is a valid newline sequence.
518    14. Neither pcre_exec() nor pcre_dfa_exec() was checking that the value given
519        as a starting offset was within the subject string. There is now a new
520        error, PCRE_ERROR_BADOFFSET, which is returned if the starting offset is
521        negative or greater than the length of the string. In order to test this,
522        pcretest is extended to allow the setting of negative starting offsets.
524    15. In both pcre_exec() and pcre_dfa_exec() the code for checking that the
525        starting offset points to the beginning of a UTF-8 character was
526        unnecessarily clumsy. I tidied it up.
528    16. Added PCRE_ERROR_SHORTUTF8 to make it possible to distinguish between a
529        bad UTF-8 sequence and one that is incomplete when using PCRE_PARTIAL_HARD.
531    17. Nobody had reported that the --include_dir option, which was added in
532        release 7.7 should have been called --include-dir (hyphen, not underscore)
533        for compatibility with GNU grep. I have changed it to --include-dir, but
534        left --include_dir as an undocumented synonym, and the same for
535        --exclude-dir, though that is not available in GNU grep, at least as of
536        release 2.5.4.
538    18. At a user's suggestion, the macros GETCHAR and friends (which pick up UTF-8
539        characters from a string of bytes) have been redefined so as not to use
540        loops, in order to improve performance in some environments. At the same
541        time, I abstracted some of the common code into auxiliary macros to save
542        repetition (this should not affect the compiled code).
544    19. If \c was followed by a multibyte UTF-8 character, bad things happened. A
545        compile-time error is now given if \c is not followed by an ASCII
546        character, that is, a byte less than 128. (In EBCDIC mode, the code is
547        different, and any byte value is allowed.)
549    20. Recognize (*NO_START_OPT) at the start of a pattern to set the PCRE_NO_
550        START_OPTIMIZE option, which is now allowed at compile time - but just
551        passed through to pcre_exec() or pcre_dfa_exec(). This makes it available
552        to pcregrep and other applications that have no direct access to PCRE
553        options. The new /Y option in pcretest sets this option when calling
554        pcre_compile().
556    21. Change 18 of release 8.01 broke the use of named subpatterns for recursive
557        back references. Groups containing recursive back references were forced to
558        be atomic by that change, but in the case of named groups, the amount of
559        memory required was incorrectly computed, leading to "Failed: internal
560        error: code overflow". This has been fixed.
562    22. Some patches to pcre_stringpiece.h, pcre_stringpiece_unittest.cc, and
563        pcretest.c, to avoid build problems in some Borland environments.
566    Version 8.10 25-Jun-2010
567  ------------------------  ------------------------
569  1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and  1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and

Removed from v.545  
changed lines
  Added in v.747

  ViewVC Help
Powered by ViewVC 1.1.5