/[pcre]/code/trunk/ChangeLog
ViewVC logotype

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.571  
changed lines
  Added in v.882

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12