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

Diff of /code/trunk/ChangeLog

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

revision 376 by ph10, Sun Mar 1 12:00:59 2009 UTC revision 380 by ph10, Tue Mar 3 12:32:47 2009 UTC
# Line 23  Version 7.9 xx-xxx-09 Line 23  Version 7.9 xx-xxx-09
23      hyphens) following file names and line numbers when outputting matching      hyphens) following file names and line numbers when outputting matching
24      lines. This is not true; no spaces are inserted. I have also clarified the      lines. This is not true; no spaces are inserted. I have also clarified the
25      wording for the --colour (or --color) option.      wording for the --colour (or --color) option.
26    
27    5.  In pcregrep, when --colour was used with -o, the list of matching strings
28        was not coloured; this is different to GNU grep, so I have changed it to be
29        the same.
30    
31    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
32        each matching line was coloured. Now it goes on to look for further matches
33        of any of the test patterns, which is the same behaviour as GNU grep.
34    
35    7.  A pattern that could match an empty string could cause pcregrep to loop; it
36        doesn't make sense to accept an empty string match in pcregrep, so I have
37        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
38        seems to be how GNU grep behaves.
39    
40    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
41        start or after a newline", because the conditional assertion was not being
42        skipped when checking for this condition.
43    
44    
45  Version 7.8 05-Sep-08  Version 7.8 05-Sep-08

Legend:
Removed from v.376  
changed lines
  Added in v.380

  ViewVC Help
Powered by ViewVC 1.1.5