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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.531  
changed lines
  Added in v.751

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12