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

  ViewVC Help
Powered by ViewVC 1.1.5