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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.518  
changed lines
  Added in v.881

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12