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

Diff of /code/trunk/ChangeLog

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

revision 517 by ph10, Wed May 5 10:44:20 2010 UTC revision 532 by ph10, Tue Jun 1 16:21:42 2010 UTC
# Line 29  Version 8.10 03 May-2010 Line 29  Version 8.10 03 May-2010
29  7.  Minor change to pcretest.c to avoid a compiler warning.  7.  Minor change to pcretest.c to avoid a compiler warning.
30    
31  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
32      \s etc use properties. The new properties are: Xan (alphanumeric), Xsp      \s etc use properties (see next item). The new properties are: Xan
33      (Perl space), Xps (POSIX space), and Xwd (word).      (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).
34    
35    9.  Added PCRE_UCP to make \b, \d, \s, \w, and certain POSIX character classes
36        use Unicode properties. (*UCP) at the start of a pattern can be used to set
37        this option. Modified pcretest to add /W to test this facility. Added
38        REG_UCP to make it available via the POSIX interface.
39    
40    10. Added --line-buffered to pcregrep.
41    
42    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
44        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.
46    
47    12. pcreposix.c included pcre.h before including pcre_internal.h. This caused a
48        conflict in the definition of PCRE_EXP_DECL. I have removed the include of
49        pcre.h as pcre_internal.h includes pcre.h itself. (This may be a bit of
50        historical tidying that never got done.)
51    
52    13. If a pattern that was studied started with a repeated Unicode property
53        test, for example, \p{Nd}+, there was the theoretical possibility of
54        setting up an incorrect bitmap of starting bytes, but fortunately it could
55        not have actually happened in practice until change 8 above was made (it
56        added property types that matched character-matching opcodes).
57    
58    14. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
59        possible starting bytes for non-anchored patterns.
60    
61    15. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes
62        \R, and also a number of cases that involve Unicode properties, both
63        explicit and implicit when PCRE_UCP is set.
64    
65    16. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8
66        input, it could crash or give wrong results if characters with values
67        greater than 0xc0 were present in the subject string. (Detail: it assumed
68        UTF-8 input when processing these items.)
69    
70    17. Added a lot of (int) casts to avoid compiler warnings in systems where
71        size_t is 64-bit.
72    
73    18. Added a check for running out of memory when PCRE is compiled with
74        --disable-stack-for-recursion.
75    
76    
77    
78  Version 8.02 19-Mar-2010  Version 8.02 19-Mar-2010

Legend:
Removed from v.517  
changed lines
  Added in v.532

  ViewVC Help
Powered by ViewVC 1.1.5