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

Diff of /code/trunk/ChangeLog

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

revision 1334 by ph10, Wed May 15 16:53:18 2013 UTC revision 1335 by ph10, Tue May 28 09:13:59 2013 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.33 28-April-2013  Version 8.33 28-May-2013
5  --------------------------  --------------------------
6    
7  1.  Added 'U' to some constants that are compared to unsigned integers, to  1.  Added 'U' to some constants that are compared to unsigned integers, to
# Line 36  Version 8.33 28-April-2013 Line 36  Version 8.33 28-April-2013
36    
37  9.  Optimizing fast_forward_start_bits in JIT.  9.  Optimizing fast_forward_start_bits in JIT.
38    
39  10. Adding experimental support for callouts in JIT, and fixing some  10. Adding support for callouts in JIT, and fixing some issues revealed
40      issues revealed during this work. Namely:      during this work. Namely:
41    
42      (a) Unoptimized capturing brackets incorrectly reset on backtrack.      (a) Unoptimized capturing brackets incorrectly reset on backtrack.
43    
# Line 125  Version 8.33 28-April-2013 Line 125  Version 8.33 28-April-2013
125      have been moved to test 1, because either Perl or PCRE has changed, and      have been moved to test 1, because either Perl or PCRE has changed, and
126      these tests are now compatible.      these tests are now compatible.
127    
128  32. Control verbs are handled in the same way in JIT and interpreter.  32. Backtracking control verbs are now handled in the same way in JIT and
129        interpreter.
130    
131  33. An opening parenthesis in a MARK/PRUNE/SKIP/THEN name in a pattern that  33. An opening parenthesis in a MARK/PRUNE/SKIP/THEN name in a pattern that
132      contained a forward subroutine reference caused a compile error.      contained a forward subroutine reference caused a compile error.
# Line 148  Version 8.33 28-April-2013 Line 149  Version 8.33 28-April-2013
149  39. Try madvise first before posix_madvise.  39. Try madvise first before posix_madvise.
150    
151  40. Change 7 for PCRE 7.9 made it impossible for pcregrep to find empty lines  40. Change 7 for PCRE 7.9 made it impossible for pcregrep to find empty lines
152      with a pattern such as ^$. It has taken 4 years for anybody to notice! The      with a pattern such as ^$. It has taken 4 years for anybody to notice! The
153      original change locked out all matches of empty strings. This has been      original change locked out all matches of empty strings. This has been
154      changed so that one match of an empty string per line is recognized.      changed so that one match of an empty string per line is recognized.
155      Subsequent searches on the same line (for colouring or for --only-matching,      Subsequent searches on the same line (for colouring or for --only-matching,
156      for example) do not recognize empty strings.      for example) do not recognize empty strings.
157    
158  41. Applied a user patch to fix a number of spelling mistakes in comments.  41. Applied a user patch to fix a number of spelling mistakes in comments.
159    
160  42. Data lines longer than 65536 caused pcretest to crash.  42. Data lines longer than 65536 caused pcretest to crash.
161    
162  43. Clarified the data type for length and startoffset arguments for pcre_exec  43. Clarified the data type for length and startoffset arguments for pcre_exec
163      and pcre_dfa_exec in the function-specific man pages, where they were      and pcre_dfa_exec in the function-specific man pages, where they were
164      explicitly stated to be in bytes, never having been updated. I also added      explicitly stated to be in bytes, never having been updated. I also added
165      some clarification to the pcreapi man page.      some clarification to the pcreapi man page.
166    
167  44. A call to pcre_dfa_exec() with an output vector size less than 2 caused  44. A call to pcre_dfa_exec() with an output vector size less than 2 caused
168      a segmentation fault.      a segmentation fault.
169    
170    
171  Version 8.32 30-November-2012  Version 8.32 30-November-2012
# Line 1674  Version 7.9 11-Apr-09 Line 1675  Version 7.9 11-Apr-09
1675  7.  A pattern that could match an empty string could cause pcregrep to loop; it  7.  A pattern that could match an empty string could cause pcregrep to loop; it
1676      doesn't make sense to accept an empty string match in pcregrep, so I have      doesn't make sense to accept an empty string match in pcregrep, so I have
1677      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
1678      seems to be how GNU grep behaves. [But see later change 40 for release      seems to be how GNU grep behaves. [But see later change 40 for release
1679      8.33.]      8.33.]
1680    
1681  8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at  8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at

Legend:
Removed from v.1334  
changed lines
  Added in v.1335

  ViewVC Help
Powered by ViewVC 1.1.5