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

Diff of /code/trunk/ChangeLog

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

revision 288 by ph10, Wed Dec 19 12:21:45 2007 UTC revision 294 by ph10, Sat Dec 29 16:55:59 2007 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 7.5 12-Nov-07  Version 7.5 29-Dec-07
5  ---------------------  ---------------------
6    
7  1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'  1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
# Line 76  Version 7.5 12-Nov-07 Line 76  Version 7.5 12-Nov-07
76      does the same. The return code can be used to tell if there were any      does the same. The return code can be used to tell if there were any
77      non-matching lines.      non-matching lines.
78    
79  14. The pattern (?=something)(?R) was not being diagnosed as a potentially  14. Added --file-offsets and --line-offsets to pcregrep.
80    
81    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
82      infinitely looping recursion. The bug was that positive lookaheads were not      infinitely looping recursion. The bug was that positive lookaheads were not
83      being skipped when checking for a possible empty match (negative lookaheads      being skipped when checking for a possible empty match (negative lookaheads
84      and both kinds of lookbehind were skipped).      and both kinds of lookbehind were skipped).
85    
86  15. Fixed two typos in the Windows-only code in pcregrep.c, and moved the  16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
87      inclusion of <windows.h> to before rather than after the definition of      inclusion of <windows.h> to before rather than after the definition of
88      INVALID_FILE_ATTRIBUTES (patch from David Byron).      INVALID_FILE_ATTRIBUTES (patch from David Byron).
89    
90  16. Specifying a possessive quantifier with a specific limit for a Unicode  17. Specifying a possessive quantifier with a specific limit for a Unicode
91      character property caused pcre_compile() to compile bad code, which led at      character property caused pcre_compile() to compile bad code, which led at
92      runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this      runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
93      are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that      are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
94      caused the error; without that there was no problem.      caused the error; without that there was no problem.
95    
96  17. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.  18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
97    
98  18. Added --enable-pcretest-libreadline.  19. Added --enable-pcretest-libreadline.
99    
100  19. In pcrecpp.cc, the variable 'count' was incremented twice in  20. In pcrecpp.cc, the variable 'count' was incremented twice in
101      RE::GlobalReplace(). As a result, the number of replacements returned was      RE::GlobalReplace(). As a result, the number of replacements returned was
102      double what it should be. I have removed one of the increments.      double what it should be. I have removed one of the increments.
103    
104    21. Several CMake things:
105    
106        (1) Arranged that, when cmake is used on Unix, the libraries end up with
107            the names libpcre and libpcreposix, not just pcre and pcreposix.
108    
109        (2) The above change means that pcretest and pcregrep are now correctly
110            linked with the newly-built libraries, not previously installed ones.
111    
112        (3) Added PCRE_SUPPORT_LIBREADLINE, PCRE_SUPPORT_LIBZ, PCRE_SUPPORT_LIBBZ2.
113    
114    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
115        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
116        UTF-8 newline character). The key issue is that the pattern starts .*;
117        this means that the match must be either at the beginning, or after a
118        newline. The bug was in the code for advancing after a failed match and
119        checking that the new position followed a newline. It was not taking
120        account of UTF-8 characters correctly.
121    
122    
123  Version 7.4 21-Sep-07  Version 7.4 21-Sep-07
124  ---------------------  ---------------------

Legend:
Removed from v.288  
changed lines
  Added in v.294

  ViewVC Help
Powered by ViewVC 1.1.5