| 31 |
6. When --colo(u)r was used in pcregrep, only the first matching substring in |
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 |
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. |
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 |
|
|
| 41 |
Version 7.8 05-Sep-08 |
Version 7.8 05-Sep-08 |