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

Diff of /code/trunk/ChangeLog

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

revision 535 by ph10, Thu Jun 3 19:18:24 2010 UTC revision 550 by ph10, Sun Oct 10 16:24:11 2010 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.10 03-Jun-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    
15    Version 8.10 25-Jun-2010
16  ------------------------  ------------------------
17    
18  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 42  Version 8.10 03-Jun-2010 Line 53  Version 8.10 03-Jun-2010
53  11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was  11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was
54      studied, and the match started with a letter with a code point greater than      studied, and the match started with a letter with a code point greater than
55      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
56      the letter, the other case of this starting letter was not recognized.      the letter, the other case of this starting letter was not recognized
57        (#976).
58    
59  12. pcreposix.c included pcre.h before including pcre_internal.h. This caused a  12. If a pattern that was studied started with a repeated Unicode property
     conflict in the definition of PCRE_EXP_DECL. I have removed the include of  
     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  
60      test, for example, \p{Nd}+, there was the theoretical possibility of      test, for example, \p{Nd}+, there was the theoretical possibility of
61      setting up an incorrect bitmap of starting bytes, but fortunately it could      setting up an incorrect bitmap of starting bytes, but fortunately it could
62      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
63      added property types that matched character-matching opcodes).      added property types that matched character-matching opcodes).
64    
65  14. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of  13. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
66      possible starting bytes for non-anchored patterns.      possible starting bytes for non-anchored patterns.
67    
68  15. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes  14. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes
69      \R, and also a number of cases that involve Unicode properties, both      \R, and also a number of cases that involve Unicode properties, both
70      explicit and implicit when PCRE_UCP is set.      explicit and implicit when PCRE_UCP is set.
71    
72  16. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8  15. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8
73      input, it could crash or give wrong results if characters with values      input, it could crash or give wrong results if characters with values
74      greater than 0xc0 were present in the subject string. (Detail: it assumed      greater than 0xc0 were present in the subject string. (Detail: it assumed
75      UTF-8 input when processing these items.)      UTF-8 input when processing these items.)
76    
77  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
78      size_t is 64-bit.      size_t is 64-bit (#991).
79    
80    17. Added a check for running out of memory when PCRE is compiled with
81        --disable-stack-for-recursion (#990).
82    
83    18. If the last data line in a file for pcretest does not have a newline on
84        the end, a newline was missing in the output.
85    
86  18. Added a check for running out of memory when PCRE is compiled with  19. The default pcre_chartables.c file recognizes only ASCII characters (values
87      --disable-stack-for-recursion.      less than 128) in its various bitmaps. However, there is a facility for
88        generating tables according to the current locale when PCRE is compiled. It
89        turns out that in some environments, 0x85 and 0xa0, which are Unicode space
90        characters, are recognized by isspace() and therefore were getting set in
91        these tables, and indeed these tables seem to approximate to ISO 8859. This
92        caused a problem in UTF-8 mode when pcre_study() was used to create a list
93        of bytes that can start a match. For \s, it was including 0x85 and 0xa0,
94        which of course cannot start UTF-8 characters. I have changed the code so
95        that only real ASCII characters (less than 128) and the correct starting
96        bytes for UTF-8 encodings are set for characters greater than 127 when in
97        UTF-8 mode. (When PCRE_UCP is set - see 9 above - the code is different
98        altogether.)
99    
100    20. Added the /T option to pcretest so as to be able to run tests with non-
101        standard character tables, thus making it possible to include the tests
102        used for 19 above in the standard set of tests.
103    
104    21. A pattern such as (?&t)(?#()(?(DEFINE)(?<t>a)) which has a forward
105        reference to a subpattern the other side of a comment that contains an
106        opening parenthesis caused either an internal compiling error, or a
107        reference to the wrong subpattern.
108    
109    
110  Version 8.02 19-Mar-2010  Version 8.02 19-Mar-2010

Legend:
Removed from v.535  
changed lines
  Added in v.550

  ViewVC Help
Powered by ViewVC 1.1.5