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

Diff of /code/trunk/ChangeLog

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

revision 538 by ph10, Wed Jun 9 19:30:57 2010 UTC revision 548 by ph10, Fri Jun 25 14:42:00 2010 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.10 03-Jun-2010  Version 8.10 25-Jun-2010
5  ------------------------  ------------------------
6    
7  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 42  Version 8.10 03-Jun-2010
42  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
43      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
44      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
45      the letter, the other case of this starting letter was not recognized      the letter, the other case of this starting letter was not recognized
46      (#976).      (#976).
47    
48  12. If a pattern that was studied started with a repeated Unicode property  12. If a pattern that was studied started with a repeated Unicode property
# Line 68  Version 8.10 03-Jun-2010 Line 68  Version 8.10 03-Jun-2010
68    
69  17. 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
70      --disable-stack-for-recursion (#990).      --disable-stack-for-recursion (#990).
71    
72  18. If the last data line in a file for pcretest does not have a newline on  18. If the last data line in a file for pcretest does not have a newline on
73      the end, a newline was missing in the output.      the end, a newline was missing in the output.
74    
75  19. The default pcre_chartables.c file recognizes only ASCII characters (values  19. The default pcre_chartables.c file recognizes only ASCII characters (values
76      less than 128) in its various bitmaps. However, there is a facility for      less than 128) in its various bitmaps. However, there is a facility for
77      generating tables according to the current locale when PCRE is compiled. It      generating tables according to the current locale when PCRE is compiled. It
78      turns out that in some environments, 0x85 and 0xa0, which are Unicode space      turns out that in some environments, 0x85 and 0xa0, which are Unicode space
79      characters, are recognized by isspace() and therefore were getting set in      characters, are recognized by isspace() and therefore were getting set in
80      these tables. This caused a problem in UTF-8 mode when pcre_study() was      these tables, and indeed these tables seem to approximate to ISO 8859. This
81      used to create a list of bytes that can start a match. For \s, it was      caused a problem in UTF-8 mode when pcre_study() was used to create a list
82      including 0x85 and 0xa0, which of course cannot start UTF-8 characters. I      of bytes that can start a match. For \s, it was including 0x85 and 0xa0,
83      have changed the code so that only real ASCII characters (less than 128)      which of course cannot start UTF-8 characters. I have changed the code so
84      are set in this case because the \s etc escapes are documented as      that only real ASCII characters (less than 128) and the correct starting
85      recognizing only ASCII characters. (When PCRE_UCP is set - see 9 above -      bytes for UTF-8 encodings are set for characters greater than 127 when in
86      the code is different altogether.)      UTF-8 mode. (When PCRE_UCP is set - see 9 above - the code is different
87        altogether.)
88    
89    20. Added the /T option to pcretest so as to be able to run tests with non-
90        standard character tables, thus making it possible to include the tests
91        used for 19 above in the standard set of tests.
92    
93    21. A pattern such as (?&t)(?#()(?(DEFINE)(?<t>a)) which has a forward
94        reference to a subpattern the other side of a comment that contains an
95        opening parenthesis caused either an internal compiling error, or a
96        reference to the wrong subpattern.
97    
98    
99  Version 8.02 19-Mar-2010  Version 8.02 19-Mar-2010

Legend:
Removed from v.538  
changed lines
  Added in v.548

  ViewVC Help
Powered by ViewVC 1.1.5