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

Diff of /code/trunk/ChangeLog

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

revision 578 by ph10, Tue Nov 23 15:34:55 2010 UTC revision 579 by ph10, Wed Nov 24 17:39:25 2010 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.11 10-Oct-2010  Version 8.11 24-Nov-2010
5  ------------------------  ------------------------
6    
7  1.  (*THEN) was not working properly if there were untried alternatives prior  1.  (*THEN) was not working properly if there were untried alternatives prior
8      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
9      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
10      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
11      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
12      alternative in the innermost enclosing group".      alternative in the innermost enclosing group".
13    
14  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
15      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
16      result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and      result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and
17      (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides      (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides
18      (*THEN).      (*THEN).
19    
20  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
21      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
22      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
23      of \s, but is part of the POSIX "space" class.)      of \s, but is part of the POSIX "space" class.)
24    
25  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
26      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
27      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 31  Version 8.11 10-Oct-2010
31      (previously it gave "no match").      (previously it gave "no match").
32    
33  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
34      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,
35      previously a full match would be given. However, setting PCRE_PARTIAL_HARD      previously a full match would be given. However, setting PCRE_PARTIAL_HARD
36      has an implication that the given string is incomplete (because a partial      has an implication that the given string is incomplete (because a partial
37      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
38      give a partial match in this situation. [Aside: previously, the one case      give a partial match in this situation. [Aside: previously, the one case
39      /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
40      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
41      now correct.]      now correct.]
42    
43  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
44      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.
45      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
46      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
47      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,
48      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
49      places in pcre_compile().      places in pcre_compile().
50    
51  7.  Related to (6) above, when pcre_compile() was skipping #-introduced  7.  Related to (6) above, when pcre_compile() was skipping #-introduced
52      comments when looking ahead for named forward references to subpatterns,      comments when looking ahead for named forward references to subpatterns,
53      the only newline sequence it recognized was NL. It now handles newlines      the only newline sequence it recognized was NL. It now handles newlines
54      according to the set newline convention.      according to the set newline convention.
55    
56  8.  SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the  8.  SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the
57      former, but used strtoul(), whereas pcretest avoided strtoul() but did not      former, but used strtoul(), whereas pcretest avoided strtoul() but did not
58      cater for a lack of strerror(). These oversights have been fixed.      cater for a lack of strerror(). These oversights have been fixed.
59    
60  9.  Added --match-limit and --recursion-limit to pcregrep.  9.  Added --match-limit and --recursion-limit to pcregrep.
61    
62  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.
63    
64  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
65      when matches were found, and --line-buffered was not being honoured.      when matches were found, and --line-buffered was not being honoured.
66    
67  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
68      of pcregrep.      of pcregrep.
69    
70  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
71      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
72      needed fixing:      needed fixing:
73    
74      (a) When the newline convention was "crlf", pcretest got it wrong, skipping      (a) When the newline convention was "crlf", pcretest got it wrong, skipping
75          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
76          just got forgotten; "any" and "anycrlf" were OK).          just got forgotten; "any" and "anycrlf" were OK).
77    
78      (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
79          mode when an empty string match preceded an ASCII character followed by          mode when an empty string match preceded an ASCII character followed by
80          a non-ASCII character. (The code for advancing by one character rather          a non-ASCII character. (The code for advancing by one character rather
81          than one byte was nonsense.)          than one byte was nonsense.)
82    
83      (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
84          the cases when CRLF is a valid newline sequence.          the cases when CRLF is a valid newline sequence.
85    
86  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
87      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
88      error, PCRE_ERROR_BADOFFSET, which is returned if the starting offset is      error, PCRE_ERROR_BADOFFSET, which is returned if the starting offset is
89      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,
90      pcretest is extended to allow the setting of negative starting offsets.      pcretest is extended to allow the setting of negative starting offsets.
91    
92  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
93      starting offset points to the beginning of a UTF-8 character was      starting offset points to the beginning of a UTF-8 character was
94      unnecessarily clumsy. I tidied it up.      unnecessarily clumsy. I tidied it up.
95    
96  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
97      bad UTF-8 sequence and one that is incomplete.      bad UTF-8 sequence and one that is incomplete when using PCRE_PARTIAL_HARD.
98    
99  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
100      release 7.7 should have been called --include-dir (hyphen, not underscore)      release 7.7 should have been called --include-dir (hyphen, not underscore)
101      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
102      left --include_dir as an undocumented synonym, and the same for      left --include_dir as an undocumented synonym, and the same for
103      --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
104      release 2.5.4.      release 2.5.4.
105    
106  18. At a user's suggestion, the macros GETCHAR and friends (which pick up UTF-8  18. At a user's suggestion, the macros GETCHAR and friends (which pick up UTF-8
107      characters from a string of bytes) have been redefined so as not to use      characters from a string of bytes) have been redefined so as not to use
108      loops, in order to improve performance in some environments. At the same      loops, in order to improve performance in some environments. At the same
109      time, I abstracted some of the common code into auxiliary macros to save      time, I abstracted some of the common code into auxiliary macros to save
110      repetition (this should not affect the compiled code).      repetition (this should not affect the compiled code).
111    
112  19. If \c was followed by a multibyte UTF-8 character, bad things happened. A  19. If \c was followed by a multibyte UTF-8 character, bad things happened. A
113      compile-time error is now given if \c is not followed by an ASCII      compile-time error is now given if \c is not followed by an ASCII
114      character, that is, a byte less than 128. (In EBCDIC mode, the code is      character, that is, a byte less than 128. (In EBCDIC mode, the code is
115      different, and any byte value is allowed.)      different, and any byte value is allowed.)
116    
117  20. Recognize (*NO_START_OPT) at the start of a pattern to set the PCRE_NO_  20. Recognize (*NO_START_OPT) at the start of a pattern to set the PCRE_NO_
118      START_OPTIMIZE option, which is now allowed at compile time - but just      START_OPTIMIZE option, which is now allowed at compile time - but just
119      passed through to pcre_exec() or pcre_dfa_exec(). This makes it available      passed through to pcre_exec() or pcre_dfa_exec(). This makes it available
120      to pcregrep and other applications that have no direct access to PCRE      to pcregrep and other applications that have no direct access to PCRE
121      options. The new /Y option in pcretest sets this option when calling      options. The new /Y option in pcretest sets this option when calling
122      pcre_compile().      pcre_compile().
123    
124  21. Change 18 of release 8.01 broke the use of named subpatterns for recursive  21. Change 18 of release 8.01 broke the use of named subpatterns for recursive
125      back references. Groups containing recursive back references were forced to      back references. Groups containing recursive back references were forced to
126      be atomic by that change, but in the case of named groups, the amount of      be atomic by that change, but in the case of named groups, the amount of
127      memory required was incorrectly computed, leading to "Failed: internal      memory required was incorrectly computed, leading to "Failed: internal
128      error: code overflow". This has been fixed.      error: code overflow". This has been fixed.
129    
130    
131  Version 8.10 25-Jun-2010  Version 8.10 25-Jun-2010

Legend:
Removed from v.578  
changed lines
  Added in v.579

  ViewVC Help
Powered by ViewVC 1.1.5