6 |
|
|
7 |
1. Fixed some typos in the markup of the man pages, and wrote a script that |
1. Fixed some typos in the markup of the man pages, and wrote a script that |
8 |
checks for such things as part of the documentation building process. |
checks for such things as part of the documentation building process. |
9 |
|
|
10 |
2. On a big-endian 64-bit system, pcregrep did not correctly process the |
2. On a big-endian 64-bit system, pcregrep did not correctly process the |
11 |
--match-limit and --recursion-limit options (added for 8.11). In |
--match-limit and --recursion-limit options (added for 8.11). In |
12 |
particular, this made one of the standard tests fail. (The integer value |
particular, this made one of the standard tests fail. (The integer value |
13 |
went into the wrong half of a long int.) |
went into the wrong half of a long int.) |
14 |
|
|
15 |
3. If the --colour option was given to pcregrep with -v (invert match), it |
3. If the --colour option was given to pcregrep with -v (invert match), it |
16 |
did strange things, either producing crazy output, or crashing. It should, |
did strange things, either producing crazy output, or crashing. It should, |
17 |
of course, ignore a request for colour when reporting lines that do not |
of course, ignore a request for colour when reporting lines that do not |
18 |
match. |
match. |
19 |
|
|
20 |
4. Another pcregrep bug caused similar problems if --colour was specified with |
4. Another pcregrep bug caused similar problems if --colour was specified with |
21 |
-M (multiline) and the pattern match finished with a line ending. |
-M (multiline) and the pattern match finished with a line ending. |
22 |
|
|
23 |
5. In pcregrep, when a pattern that ended with a literal newline sequence was |
5. In pcregrep, when a pattern that ended with a literal newline sequence was |
24 |
matched in multiline mode, the following line was shown as part of the |
matched in multiline mode, the following line was shown as part of the |
25 |
match. This seems wrong, so I have changed it. |
match. This seems wrong, so I have changed it. |
26 |
|
|
27 |
6. Another pcregrep bug in multiline mode, when --colour was specified, caused |
6. Another pcregrep bug in multiline mode, when --colour was specified, caused |
28 |
the check for further matches in the same line (so they could be coloured) |
the check for further matches in the same line (so they could be coloured) |
29 |
to overrun the end of the current line. If another match was found, it was |
to overrun the end of the current line. If another match was found, it was |
30 |
incorrectly shown (and then shown again when found in the next line). |
incorrectly shown (and then shown again when found in the next line). |
31 |
|
|
32 |
7. If pcregrep was compiled under Windows, there was a reference to the |
7. If pcregrep was compiled under Windows, there was a reference to the |
33 |
function pcregrep_exit() before it was defined. I am assuming this was |
function pcregrep_exit() before it was defined. I am assuming this was |
34 |
the cause of the "error C2371: 'pcregrep_exit' : redefinition;" that was |
the cause of the "error C2371: 'pcregrep_exit' : redefinition;" that was |
35 |
reported by a user. I've moved the definition above the reference. |
reported by a user. I've moved the definition above the reference. |
36 |
|
|
37 |
|
|
38 |
Version 8.11 10-Dec-2010 |
Version 8.11 10-Dec-2010 |
39 |
------------------------ |
------------------------ |