| 7 |
1. Applied Craig's patch to sort out a long long problem: "If we can't convert |
1. Applied Craig's patch to sort out a long long problem: "If we can't convert |
| 8 |
a string to a long long, pretend we don't even have a long long." This is |
a string to a long long, pretend we don't even have a long long." This is |
| 9 |
done by checking for the strtoq, strtoll, and _strtoi64 functions. |
done by checking for the strtoq, strtoll, and _strtoi64 functions. |
| 10 |
|
|
| 11 |
|
2. Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with |
| 12 |
|
pre-7.6 versions, which defined a global no_arg variable instead of putting |
| 13 |
|
it in the RE class. (See also #8 below.) |
| 14 |
|
|
| 15 |
|
3. Remove a line of dead code, identified by coverity and reported by Nuno |
| 16 |
|
Lopes. |
| 17 |
|
|
| 18 |
|
4. Fixed two related pcregrep bugs involving -r with --include or --exclude: |
| 19 |
|
|
| 20 |
|
(1) The include/exclude patterns were being applied to the whole pathnames |
| 21 |
|
of files, instead of just to the final components. |
| 22 |
|
|
| 23 |
|
(2) If there was more than one level of directory, the subdirectories were |
| 24 |
|
skipped unless they satisfied the include/exclude conditions. This is |
| 25 |
|
inconsistent with GNU grep (and could even be seen as contrary to the |
| 26 |
|
pcregrep specification - which I improved to make it absolutely clear). |
| 27 |
|
The action now is always to scan all levels of directory, and just |
| 28 |
|
apply the include/exclude patterns to regular files. |
| 29 |
|
|
| 30 |
|
5. Added the --include_dir and --exclude_dir patterns to pcregrep, and used |
| 31 |
|
--exclude_dir in the tests to avoid scanning .svn directories. |
| 32 |
|
|
| 33 |
|
6. Applied Craig's patch to the QuoteMeta function so that it escapes the |
| 34 |
|
NUL character as backslash + 0 rather than backslash + NUL, because PCRE |
| 35 |
|
doesn't support NULs in patterns. |
| 36 |
|
|
| 37 |
|
7. Added some missing "const"s to declarations of static tables in |
| 38 |
|
pcre_compile.c and pcre_dfa_exec.c. |
| 39 |
|
|
| 40 |
|
8. Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was |
| 41 |
|
caused by fix #2 above. (Subsequently also a second patch to fix the |
| 42 |
|
first patch. And a third patch - this was a messy problem.) |
| 43 |
|
|
| 44 |
|
9. Applied Craig's patch to remove the use of push_back(). |
| 45 |
|
|
| 46 |
|
10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX |
| 47 |
|
matching function regexec(). |
| 48 |
|
|
| 49 |
|
11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n', |
| 50 |
|
which, however, unlike Perl's \g{...}, are subroutine calls, not back |
| 51 |
|
references. PCRE supports relative numbers with this syntax (I don't think |
| 52 |
|
Oniguruma does). |
| 53 |
|
|
| 54 |
|
12. Previously, a group with a zero repeat such as (...){0} was completely |
| 55 |
|
omitted from the compiled regex. However, this means that if the group |
| 56 |
|
was called as a subroutine from elsewhere in the pattern, things went wrong |
| 57 |
|
(an internal error was given). Such groups are now left in the compiled |
| 58 |
|
pattern, with a new opcode that causes them to be skipped at execution |
| 59 |
|
time. |
| 60 |
|
|
| 61 |
|
13. Added the PCRE_JAVASCRIPT_COMPAT option. This currently does two things: |
| 62 |
|
(a) A lone ] character is dis-allowed (Perl treats it as data). |
| 63 |
|
(b) A back reference to an unmatched subpattern matches an empty string |
| 64 |
|
(Perl fails the current match path). |
| 65 |
|
|
| 66 |
|
|
| 67 |
Version 7.6 28-Jan-08 |
Version 7.6 28-Jan-08 |
Parent Directory
| 
Revision Log
| 
Patch