ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 583 by ph10, Tue Jan 11 16:49:55 2011 UTC revision 889 by ph10, Tue Jan 17 14:51:50 2012 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 8.12 11-Jan-2011  Version 8.30
5    ------------
7    1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
8        name is defined in ctype.h.
10    2.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
11        only in quite long subpatterns.
13    3.  Removed the function pcre_info(), which has been obsolete and deprecated
14        since it was replaced by pcre_fullinfo() in February 2000.
16    4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
17        match a (*MARK), and the match failed at the start of the subject, a
18        reference to memory before the start of the subject could occur. This bug
19        was introduced by fix 17 of release 8.21.
21    5.  A reference to an unset group with zero minimum repetition was giving
22        totally wrong answers (in non-JavaScript-compatibility mode). For example,
23        /(another)?(\1?)test/ matched against "hello world test". This bug was
24        introduced in release 8.13.
26    6.  Add support for 16-bit character strings (a large amount of work involving
27        many changes and refactorings).
29    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
30        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
31        from a file.
33    8.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
34        rounding is not applied in this particular case).
36    9.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
37        if they appear, or are escaped, in patterns.
39    10. Get rid of a number of -Wunused-but-set-variable warnings.
41    11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
42        "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
43        Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
44        also returns the mark "x". This bug applied to capturing parentheses,
45        non-capturing parentheses, and atomic parentheses. It also applied to some
46        assertions.
48    12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
49        information out of configure.ac instead of relying on pcre.h.generic, which
50        is not stored in the repository.
52    13. Applied Dmitry V. Levin's patch for a more portable method for linking with
53        -lreadline.
56    Version 8.21 12-Dec-2011
57    ------------------------
59    1.  Updating the JIT compiler.
61    2.  JIT compiler now supports OP_NCREF, OP_RREF and OP_NRREF. New test cases
62        are added as well.
64    3.  Fix cache-flush issue on PowerPC (It is still an experimental JIT port).
65        PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before
66        calling _pcre_jit_exec. Some extra comments are added.
68    4.  (*MARK) settings inside atomic groups that do not contain any capturing
69        parentheses, for example, (?>a(*:m)), were not being passed out. This bug
70        was introduced by change 18 for 8.20.
72    5.  Supporting of \x, \U and \u in JavaScript compatibility mode based on the
73        ECMA-262 standard.
75    6.  Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were
76        erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
77        This bug was probably introduced by change 9 of 8.13.
79    7.  While fixing 6 above, I noticed that a number of other items were being
80        incorrectly rejected as "not fixed length". This arose partly because newer
81        opcodes had not been added to the fixed-length checking code. I have (a)
82        corrected the bug and added tests for these items, and (b) arranged for an
83        error to occur if an unknown opcode is encountered while checking for fixed
84        length instead of just assuming "not fixed length". The items that were
85        rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
86        (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
87        repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
89    8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
90        being incorrectly compiled and would have given unpredicatble results.
92    9.  A possessively repeated subpattern with minimum repeat count greater than
93        one behaved incorrectly. For example, (A){2,}+ behaved as if it was
94        (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
95        the first (A) could occur when it should not.
97    10. Add a cast and remove a redundant test from the code.
99    11. JIT should use pcre_malloc/pcre_free for allocation.
101    12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems
102        best practice nowadays, and helps with cross-compiling. (If the exec_prefix
103        is anything other than /usr, -L is still shown).
105    13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.
107    14. Perl does not support \N without a following name in a [] class; PCRE now
108        also gives an error.
110    15. If a forward reference was repeated with an upper limit of around 2000,
111        it caused the error "internal error: overran compiling workspace". The
112        maximum number of forward references (including repeats) was limited by the
113        internal workspace, and dependent on the LINK_SIZE. The code has been
114        rewritten so that the workspace expands (via pcre_malloc) if necessary, and
115        the default depends on LINK_SIZE. There is a new upper limit (for safety)
116        of around 200,000 forward references. While doing this, I also speeded up
117        the filling in of repeated forward references.
119    16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
120        incorrectly expecting the subject to contain another "a" after the start.
122    17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
123        in the match, the SKIP should be ignored. This was not happening; instead
124        the SKIP was being treated as NOMATCH. For patterns such as
125        /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
126        tested.
128    18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
129        now much more compatible with Perl, in particular in cases where the result
130        is a non-match for a non-anchored pattern. For example, if
131        /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
132        "m", where previously it did not return a name. A side effect of this
133        change is that for partial matches, the last encountered mark name is
134        returned, as for non matches. A number of tests that were previously not
135        Perl-compatible have been moved into the Perl-compatible test files. The
136        refactoring has had the pleasing side effect of removing one argument from
137        the match() function, thus reducing its stack requirements.
139    19. If the /S+ option was used in pcretest to study a pattern using JIT,
140        subsequent uses of /S (without +) incorrectly behaved like /S+.
142    21. Retrieve executable code size support for the JIT compiler and fixing
143        some warnings.
145    22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
146        not work when the shorter character appeared right at the end of the
147        subject string.
149    23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
150        systems.
152    24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
153        output it when the /M option is used in pcretest.
155    25. The CheckMan script was not being included in the distribution. Also, added
156        an explicit "perl" to run Perl scripts from the PrepareRelease script
157        because this is reportedly needed in Windows.
159    26. If study data was being save in a file and studying had not found a set of
160        "starts with" bytes for the pattern, the data written to the file (though
161        never used) was taken from uninitialized memory and so caused valgrind to
162        complain.
164    27. Updated RunTest.bat as provided by Sheri Pierce.
166    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
168    29. Computation of memory usage for the table of capturing group names was
169        giving an unnecessarily large value.
172    Version 8.20 21-Oct-2011
173    ------------------------
175    1.  Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had
176        a POSIX class. After further experiments with Perl, which convinced me that
177        Perl has bugs and confusions, a closing square bracket is no longer allowed
178        in a POSIX name. This bug also affected patterns with classes that started
179        with full stops.
181    2.  If a pattern such as /(a)b|ac/ is matched against "ac", there is no
182        captured substring, but while checking the failing first alternative,
183        substring 1 is temporarily captured. If the output vector supplied to
184        pcre_exec() was not big enough for this capture, the yield of the function
185        was still zero ("insufficient space for captured substrings"). This cannot
186        be totally fixed without adding another stack variable, which seems a lot
187        of expense for a edge case. However, I have improved the situation in cases
188        such as /(a)(b)x|abc/ matched against "abc", where the return code
189        indicates that fewer than the maximum number of slots in the ovector have
190        been set.
192    3.  Related to (2) above: when there are more back references in a pattern than
193        slots in the output vector, pcre_exec() uses temporary memory during
194        matching, and copies in the captures as far as possible afterwards. It was
195        using the entire output vector, but this conflicts with the specification
196        that only 2/3 is used for passing back captured substrings. Now it uses
197        only the first 2/3, for compatibility. This is, of course, another edge
198        case.
200    4.  Zoltan Herczeg's just-in-time compiler support has been integrated into the
201        main code base, and can be used by building with --enable-jit. When this is
202        done, pcregrep automatically uses it unless --disable-pcregrep-jit or the
203        runtime --no-jit option is given.
205    5.  When the number of matches in a pcre_dfa_exec() run exactly filled the
206        ovector, the return from the function was zero, implying that there were
207        other matches that did not fit. The correct "exactly full" value is now
208        returned.
210    6.  If a subpattern that was called recursively or as a subroutine contained
211        (*PRUNE) or any other control that caused it to give a non-standard return,
212        invalid errors such as "Error -26 (nested recursion at the same subject
213        position)" or even infinite loops could occur.
215    7.  If a pattern such as /a(*SKIP)c|b(*ACCEPT)|/ was studied, it stopped
216        computing the minimum length on reaching *ACCEPT, and so ended up with the
217        wrong value of 1 rather than 0. Further investigation indicates that
218        computing a minimum subject length in the presence of *ACCEPT is difficult
219        (think back references, subroutine calls), and so I have changed the code
220        so that no minimum is registered for a pattern that contains *ACCEPT.
222    8.  If (*THEN) was present in the first (true) branch of a conditional group,
223        it was not handled as intended. [But see 16 below.]
225    9.  Replaced RunTest.bat and CMakeLists.txt with improved versions provided by
226        Sheri Pierce.
228    10. A pathological pattern such as /(*ACCEPT)a/ was miscompiled, thinking that
229        the first byte in a match must be "a".
231    11. Change 17 for 8.13 increased the recursion depth for patterns like
232        /a(?:.)*?a/ drastically. I've improved things by remembering whether a
233        pattern contains any instances of (*THEN). If it does not, the old
234        optimizations are restored. It would be nice to do this on a per-group
235        basis, but at the moment that is not feasible.
237    12. In some environments, the output of pcretest -C is CRLF terminated. This
238        broke RunTest's code that checks for the link size. A single white space
239        character after the value is now allowed for.
241    13. RunTest now checks for the "fr" locale as well as for "fr_FR" and "french".
242        For "fr", it uses the Windows-specific input and output files.
244    14. If (*THEN) appeared in a group that was called recursively or as a
245        subroutine, it did not work as intended. [But see next item.]
247    15. Consider the pattern /A (B(*THEN)C) | D/ where A, B, C, and D are complex
248        pattern fragments (but not containing any | characters). If A and B are
249        matched, but there is a failure in C so that it backtracks to (*THEN), PCRE
250        was behaving differently to Perl. PCRE backtracked into A, but Perl goes to
251        D. In other words, Perl considers parentheses that do not contain any |
252        characters to be part of a surrounding alternative, whereas PCRE was
253        treading (B(*THEN)C) the same as (B(*THEN)C|(*FAIL)) -- which Perl handles
254        differently. PCRE now behaves in the same way as Perl, except in the case
255        of subroutine/recursion calls such as (?1) which have in any case always
256        been different (but PCRE had them first :-).
258    16. Related to 15 above: Perl does not treat the | in a conditional group as
259        creating alternatives. Such a group is treated in the same way as an
260        ordinary group without any | characters when processing (*THEN). PCRE has
261        been changed to match Perl's behaviour.
263    17. If a user had set PCREGREP_COLO(U)R to something other than 1:31, the
264        RunGrepTest script failed.
266    18. Change 22 for version 13 caused atomic groups to use more stack. This is
267        inevitable for groups that contain captures, but it can lead to a lot of
268        stack use in large patterns. The old behaviour has been restored for atomic
269        groups that do not contain any capturing parentheses.
271    19. If the PCRE_NO_START_OPTIMIZE option was set for pcre_compile(), it did not
272        suppress the check for a minimum subject length at run time. (If it was
273        given to pcre_exec() or pcre_dfa_exec() it did work.)
275    20. Fixed an ASCII-dependent infelicity in pcretest that would have made it
276        fail to work when decoding hex characters in data strings in EBCDIC
277        environments.
279    21. It appears that in at least one Mac OS environment, the isxdigit() function
280        is implemented as a macro that evaluates to its argument more than once,
281        contravening the C 90 Standard (I haven't checked a later standard). There
282        was an instance in pcretest which caused it to go wrong when processing
283        \x{...} escapes in subject strings. The has been rewritten to avoid using
284        things like p++ in the argument of isxdigit().
287    Version 8.13 16-Aug-2011
288    ------------------------
290    1.  The Unicode data tables have been updated to Unicode 6.0.0.
292    2.  Two minor typos in pcre_internal.h have been fixed.
294    3.  Added #include <string.h> to pcre_scanner_unittest.cc, pcrecpp.cc, and
295        pcrecpp_unittest.cc. They are needed for strcmp(), memset(), and strchr()
296        in some environments (e.g. Solaris 10/SPARC using Sun Studio 12U2).
298    4.  There were a number of related bugs in the code for matching backrefences
299        caselessly in UTF-8 mode when codes for the characters concerned were
300        different numbers of bytes. For example, U+023A and U+2C65 are an upper
301        and lower case pair, using 2 and 3 bytes, respectively. The main bugs were:
302        (a) A reference to 3 copies of a 2-byte code matched only 2 of a 3-byte
303        code. (b) A reference to 2 copies of a 3-byte code would not match 2 of a
304        2-byte code at the end of the subject (it thought there wasn't enough data
305        left).
307    5.  Comprehensive information about what went wrong is now returned by
308        pcre_exec() and pcre_dfa_exec() when the UTF-8 string check fails, as long
309        as the output vector has at least 2 elements. The offset of the start of
310        the failing character and a reason code are placed in the vector.
312    6.  When the UTF-8 string check fails for pcre_compile(), the offset that is
313        now returned is for the first byte of the failing character, instead of the
314        last byte inspected. This is an incompatible change, but I hope it is small
315        enough not to be a problem. It makes the returned offset consistent with
316        pcre_exec() and pcre_dfa_exec().
318    7.  pcretest now gives a text phrase as well as the error number when
319        pcre_exec() or pcre_dfa_exec() fails; if the error is a UTF-8 check
320        failure, the offset and reason code are output.
322    8.  When \R was used with a maximizing quantifier it failed to skip backwards
323        over a \r\n pair if the subsequent match failed. Instead, it just skipped
324        back over a single character (\n). This seems wrong (because it treated the
325        two characters as a single entity when going forwards), conflicts with the
326        documentation that \R is equivalent to (?>\r\n|\n|...etc), and makes the
327        behaviour of \R* different to (\R)*, which also seems wrong. The behaviour
328        has been changed.
330    9.  Some internal refactoring has changed the processing so that the handling
331        of the PCRE_CASELESS and PCRE_MULTILINE options is done entirely at compile
332        time (the PCRE_DOTALL option was changed this way some time ago: version
333        7.7 change 16). This has made it possible to abolish the OP_OPT op code,
334        which was always a bit of a fudge. It also means that there is one less
335        argument for the match() function, which reduces its stack requirements
336        slightly. This change also fixes an incompatibility with Perl: the pattern
337        (?i:([^b]))(?1) should not match "ab", but previously PCRE gave a match.
339    10. More internal refactoring has drastically reduced the number of recursive
340        calls to match() for possessively repeated groups such as (abc)++ when
341        using pcre_exec().
343    11. While implementing 10, a number of bugs in the handling of groups were
344        discovered and fixed:
346        (?<=(a)+) was not diagnosed as invalid (non-fixed-length lookbehind).
347        (a|)*(?1) gave a compile-time internal error.
348        ((a|)+)+  did not notice that the outer group could match an empty string.
349        (^a|^)+   was not marked as anchored.
350        (.*a|.*)+ was not marked as matching at start or after a newline.
352    12. Yet more internal refactoring has removed another argument from the match()
353        function. Special calls to this function are now indicated by setting a
354        value in a variable in the "match data" data block.
356    13. Be more explicit in pcre_study() instead of relying on "default" for
357        opcodes that mean there is no starting character; this means that when new
358        ones are added and accidentally left out of pcre_study(), testing should
359        pick them up.
361    14. The -s option of pcretest has been documented for ages as being an old
362        synonym of -m (show memory usage). I have changed it to mean "force study
363        for every regex", that is, assume /S for every regex. This is similar to -i
364        and -d etc. It's slightly incompatible, but I'm hoping nobody is still
365        using it. It makes it easier to run collections of tests with and without
366        study enabled, and thereby test pcre_study() more easily. All the standard
367        tests are now run with and without -s (but some patterns can be marked as
368        "never study" - see 20 below).
370    15. When (*ACCEPT) was used in a subpattern that was called recursively, the
371        restoration of the capturing data to the outer values was not happening
372        correctly.
374    16. If a recursively called subpattern ended with (*ACCEPT) and matched an
375        empty string, and PCRE_NOTEMPTY was set, pcre_exec() thought the whole
376        pattern had matched an empty string, and so incorrectly returned a no
377        match.
379    17. There was optimizing code for the last branch of non-capturing parentheses,
380        and also for the obeyed branch of a conditional subexpression, which used
381        tail recursion to cut down on stack usage. Unfortunately, now that there is
382        the possibility of (*THEN) occurring in these branches, tail recursion is
383        no longer possible because the return has to be checked for (*THEN). These
384        two optimizations have therefore been removed. [But see 8.20/11 above.]
386    18. If a pattern containing \R was studied, it was assumed that \R always
387        matched two bytes, thus causing the minimum subject length to be
388        incorrectly computed because \R can also match just one byte.
390    19. If a pattern containing (*ACCEPT) was studied, the minimum subject length
391        was incorrectly computed.
393    20. If /S is present twice on a test pattern in pcretest input, it now
394        *disables* studying, thereby overriding the use of -s on the command line
395        (see 14 above). This is necessary for one or two tests to keep the output
396        identical in both cases.
398    21. When (*ACCEPT) was used in an assertion that matched an empty string and
399        PCRE_NOTEMPTY was set, PCRE applied the non-empty test to the assertion.
401    22. When an atomic group that contained a capturing parenthesis was
402        successfully matched, but the branch in which it appeared failed, the
403        capturing was not being forgotten if a higher numbered group was later
404        captured. For example, /(?>(a))b|(a)c/ when matching "ac" set capturing
405        group 1 to "a", when in fact it should be unset. This applied to multi-
406        branched capturing and non-capturing groups, repeated or not, and also to
407        positive assertions (capturing in negative assertions does not happen
408        in PCRE) and also to nested atomic groups.
410    23. Add the ++ qualifier feature to pcretest, to show the remainder of the
411        subject after a captured substring, to make it easier to tell which of a
412        number of identical substrings has been captured.
414    24. The way atomic groups are processed by pcre_exec() has been changed so that
415        if they are repeated, backtracking one repetition now resets captured
416        values correctly. For example, if ((?>(a+)b)+aabab) is matched against
417        "aaaabaaabaabab" the value of captured group 2 is now correctly recorded as
418        "aaa". Previously, it would have been "a". As part of this code
419        refactoring, the way recursive calls are handled has also been changed.
421    25. If an assertion condition captured any substrings, they were not passed
422        back unless some other capturing happened later. For example, if
423        (?(?=(a))a) was matched against "a", no capturing was returned.
425    26. When studying a pattern that contained subroutine calls or assertions,
426        the code for finding the minimum length of a possible match was handling
427        direct recursions such as (xxx(?1)|yyy) but not mutual recursions (where
428        group 1 called group 2 while simultaneously a separate group 2 called group
429        1). A stack overflow occurred in this case. I have fixed this by limiting
430        the recursion depth to 10.
432    27. Updated RunTest.bat in the distribution to the version supplied by Tom
433        Fortmann. This supports explicit test numbers on the command line, and has
434        argument validation and error reporting.
436    28. An instance of \X with an unlimited repeat could fail if at any point the
437        first character it looked at was a mark character.
439    29. Some minor code refactoring concerning Unicode properties and scripts
440        should reduce the stack requirement of match() slightly.
442    30. Added the '=' option to pcretest to check the setting of unused capturing
443        slots at the end of the pattern, which are documented as being -1, but are
444        not included in the return count.
446    31. If \k was not followed by a braced, angle-bracketed, or quoted name, PCRE
447        compiled something random. Now it gives a compile-time error (as does
448        Perl).
450    32. A *MARK encountered during the processing of a positive assertion is now
451        recorded and passed back (compatible with Perl).
453    33. If --only-matching or --colour was set on a pcregrep call whose pattern
454        had alternative anchored branches, the search for a second match in a line
455        was done as if at the line start. Thus, for example, /^01|^02/ incorrectly
456        matched the line "0102" twice. The same bug affected patterns that started
457        with a backwards assertion. For example /\b01|\b02/ also matched "0102"
458        twice.
460    34. Previously, PCRE did not allow quantification of assertions. However, Perl
461        does, and because of capturing effects, quantifying parenthesized
462        assertions may at times be useful. Quantifiers are now allowed for
463        parenthesized assertions.
465    35. A minor code tidy in pcre_compile() when checking options for \R usage.
467    36. \g was being checked for fancy things in a character class, when it should
468        just be a literal "g".
470    37. PCRE was rejecting [:a[:digit:]] whereas Perl was not. It seems that the
471        appearance of a nested POSIX class supersedes an apparent external class.
472        For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,
473        unescaped square brackets may also appear as part of class names. For
474        example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves
475        more like Perl. (But see 8.20/1 above.)
477    38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this
478        was because it thought it was \N{name}, which is not supported).
480    39. Add minix to OS list not supporting the -S option in pcretest.
482    40. PCRE tries to detect cases of infinite recursion at compile time, but it
483        cannot analyze patterns in sufficient detail to catch mutual recursions
484        such as ((?1))((?2)). There is now a runtime test that gives an error if a
485        subgroup is called recursively as a subpattern for a second time at the
486        same position in the subject string. In previous releases this might have
487        been caught by the recursion limit, or it might have run out of stack.
489    41. A pattern such as /(?(R)a+|(?R)b)/ is quite safe, as the recursion can
490        happen only once. PCRE was, however incorrectly giving a compile time error
491        "recursive call could loop indefinitely" because it cannot analyze the
492        pattern in sufficient detail. The compile time test no longer happens when
493        PCRE is compiling a conditional subpattern, but actual runaway loops are
494        now caught at runtime (see 40 above).
496    42. It seems that Perl allows any characters other than a closing parenthesis
497        to be part of the NAME in (*MARK:NAME) and other backtracking verbs. PCRE
498        has been changed to be the same.
500    43. Updated configure.ac to put in more quoting round AC_LANG_PROGRAM etc. so
501        as not to get warnings when autogen.sh is called. Also changed
502        AC_PROG_LIBTOOL (deprecated) to LT_INIT (the current macro).
504    44. To help people who use pcregrep to scan files containing exceedingly long
505        lines, the following changes have been made:
507        (a) The default value of the buffer size parameter has been increased from
508            8K to 20K. (The actual buffer used is three times this size.)
510        (b) The default can be changed by ./configure --with-pcregrep-bufsize when
511            PCRE is built.
513        (c) A --buffer-size=n option has been added to pcregrep, to allow the size
514            to be set at run time.
516        (d) Numerical values in pcregrep options can be followed by K or M, for
517            example --buffer-size=50K.
519        (e) If a line being scanned overflows pcregrep's buffer, an error is now
520            given and the return code is set to 2.
522    45. Add a pointer to the latest mark to the callout data block.
524    46. The pattern /.(*F)/, when applied to "abc" with PCRE_PARTIAL_HARD, gave a
525        partial match of an empty string instead of no match. This was specific to
526        the use of ".".
528    47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a
529        complete match instead of a partial match. This bug was dependent on both
530        the PCRE_UTF8 and PCRE_DOTALL options being set.
532    48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the
533        starting byte set, because \b was not being ignored.
536    Version 8.12 15-Jan-2011
537  ------------------------  ------------------------
539  1.  Fixed some typos in the markup of the man pages, and wrote a script that  1.  Fixed some typos in the markup of the man pages, and wrote a script that
540      checks for such things as part of the documentation building process.      checks for such things as part of the documentation building process.
542    2.  On a big-endian 64-bit system, pcregrep did not correctly process the
543        --match-limit and --recursion-limit options (added for 8.11). In
544        particular, this made one of the standard tests fail. (The integer value
545        went into the wrong half of a long int.)
547    3.  If the --colour option was given to pcregrep with -v (invert match), it
548        did strange things, either producing crazy output, or crashing. It should,
549        of course, ignore a request for colour when reporting lines that do not
550        match.
552    4.  Another pcregrep bug caused similar problems if --colour was specified with
553        -M (multiline) and the pattern match finished with a line ending.
555    5.  In pcregrep, when a pattern that ended with a literal newline sequence was
556        matched in multiline mode, the following line was shown as part of the
557        match. This seems wrong, so I have changed it.
559    6.  Another pcregrep bug in multiline mode, when --colour was specified, caused
560        the check for further matches in the same line (so they could be coloured)
561        to overrun the end of the current line. If another match was found, it was
562        incorrectly shown (and then shown again when found in the next line).
564    7.  If pcregrep was compiled under Windows, there was a reference to the
565        function pcregrep_exit() before it was defined. I am assuming this was
566        the cause of the "error C2371: 'pcregrep_exit' : redefinition;" that was
567        reported by a user. I've moved the definition above the reference.
570  Version 8.11 10-Dec-2010  Version 8.11 10-Dec-2010
571  ------------------------  ------------------------

Removed from v.583  
changed lines
  Added in v.889

  ViewVC Help
Powered by ViewVC 1.1.5