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

Diff of /code/trunk/ChangeLog

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

revision 521 by ph10, Sat May 22 19:03:35 2010 UTC revision 551 by ph10, Sun Oct 10 17:33:07 2010 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.10 03 May-2010  Version 8.11 10-Oct-2010
5    ------------------------
6    
7    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
9        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
11        is clear that when (*THEN) is backtracked onto, it goes to the "next
12        alternative in the innermost enclosing group".
13    
14    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
16        result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and
17        (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides
18        (*THEN).
19    
20    
21    Version 8.10 25-Jun-2010
22  ------------------------  ------------------------
23    
24  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 26  Version 8.10 03 May-2010
26    
27  2.  (*ACCEPT) was not working when inside an atomic group.  2.  (*ACCEPT) was not working when inside an atomic group.
28    
29  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
30      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
31      causes the error). The code is unchanged, but I tidied the documentation.      causes the error). The code is unchanged, but I tidied the documentation.
32    
33  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,
34      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
35      that it faults them when PCRE_EXTRA is set.      that it faults them when PCRE_EXTRA is set.
36    
37  5.  Added support for \N, which always matches any character other than  5.  Added support for \N, which always matches any character other than
38      newline. (It is the same as "." when PCRE_DOTALL is not set.)      newline. (It is the same as "." when PCRE_DOTALL is not set.)
39    
40  6.  When compiling pcregrep with newer versions of gcc which may have  6.  When compiling pcregrep with newer versions of gcc which may have
41      FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',      FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',
42      declared with attribute warn_unused_result" were given. Just casting the      declared with attribute warn_unused_result" were given. Just casting the
43      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
44      needed. I've used a macro to implement this.      needed. I've used a macro to implement this.
45    
46  7.  Minor change to pcretest.c to avoid a compiler warning.  7.  Minor change to pcretest.c to avoid a compiler warning.
47    
48  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
49      \s etc use properties (see next item). The new properties are: Xan      \s etc use properties (see next item). The new properties are: Xan
50      (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).      (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).
51    
52  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
53      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
54      this option. Modified pcretest to add /W to test this facility. Added      this option. Modified pcretest to add /W to test this facility. Added
55      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.  
56    
57  11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was  10. Added --line-buffered to pcregrep.
58      studied, and the match started with a letter with a code point greater than  
59    11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was
60        studied, and the match started with a letter with a code point greater than
61      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
62      the letter, the other case of this starting letter was not recognized.      the letter, the other case of this starting letter was not recognized
63        (#976).
64  12. pcreposix.c included pcre.h before including pcre_internal.h. This caused a  
65      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
66      pcre.h as pcre_internal.h includes pcre.h itself. (This may be a bit of      test, for example, \p{Nd}+, there was the theoretical possibility of
67      historical tidying that never got done.)      setting up an incorrect bitmap of starting bytes, but fortunately it could
68        not have actually happened in practice until change 8 above was made (it
69        added property types that matched character-matching opcodes).
70    
71    13. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
72        possible starting bytes for non-anchored patterns.
73    
74    14. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes
75        \R, and also a number of cases that involve Unicode properties, both
76        explicit and implicit when PCRE_UCP is set.
77    
78    15. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8
79        input, it could crash or give wrong results if characters with values
80        greater than 0xc0 were present in the subject string. (Detail: it assumed
81        UTF-8 input when processing these items.)
82    
83    16. Added a lot of (int) casts to avoid compiler warnings in systems where
84        size_t is 64-bit (#991).
85    
86    17. Added a check for running out of memory when PCRE is compiled with
87        --disable-stack-for-recursion (#990).
88    
89    18. If the last data line in a file for pcretest does not have a newline on
90        the end, a newline was missing in the output.
91    
92    19. The default pcre_chartables.c file recognizes only ASCII characters (values
93        less than 128) in its various bitmaps. However, there is a facility for
94        generating tables according to the current locale when PCRE is compiled. It
95        turns out that in some environments, 0x85 and 0xa0, which are Unicode space
96        characters, are recognized by isspace() and therefore were getting set in
97        these tables, and indeed these tables seem to approximate to ISO 8859. This
98        caused a problem in UTF-8 mode when pcre_study() was used to create a list
99        of bytes that can start a match. For \s, it was including 0x85 and 0xa0,
100        which of course cannot start UTF-8 characters. I have changed the code so
101        that only real ASCII characters (less than 128) and the correct starting
102        bytes for UTF-8 encodings are set for characters greater than 127 when in
103        UTF-8 mode. (When PCRE_UCP is set - see 9 above - the code is different
104        altogether.)
105    
106    20. Added the /T option to pcretest so as to be able to run tests with non-
107        standard character tables, thus making it possible to include the tests
108        used for 19 above in the standard set of tests.
109    
110    21. A pattern such as (?&t)(?#()(?(DEFINE)(?<t>a)) which has a forward
111        reference to a subpattern the other side of a comment that contains an
112        opening parenthesis caused either an internal compiling error, or a
113        reference to the wrong subpattern.
114    
115    
116  Version 8.02 19-Mar-2010  Version 8.02 19-Mar-2010

Legend:
Removed from v.521  
changed lines
  Added in v.551

  ViewVC Help
Powered by ViewVC 1.1.5