| 8 |
|
|
| 9 |
2. Added the option --libs-cpp to pcre-config, but only when C++ support is |
2. Added the option --libs-cpp to pcre-config, but only when C++ support is |
| 10 |
configured. |
configured. |
| 11 |
|
|
| 12 |
|
3. Updated the licensing terms in the pcregexp.pas file, as agreed with the |
| 13 |
|
original author of that file, following a query about its status. |
| 14 |
|
|
| 15 |
|
4. On systems that do not have stdint.h (e.g. Solaris), check for and include |
| 16 |
|
inttypes.h instead. This fixes a bug that was introduced by change 8.01/8. |
| 17 |
|
|
| 18 |
|
5. A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive |
| 19 |
|
quantifier applied to a forward-referencing subroutine call, could compile |
| 20 |
|
incorrect code or give the error "internal error: previously-checked |
| 21 |
|
referenced subpattern not found". |
| 22 |
|
|
| 23 |
|
6. Both MS Visual Studio and Symbian OS have problems with initializing |
| 24 |
|
variables to point to external functions. For these systems, therefore, |
| 25 |
|
pcre_malloc etc. are now initialized to local functions that call the |
| 26 |
|
relevant global functions. |
| 27 |
|
|
| 28 |
|
7. There were two entries missing in the vectors called coptable and poptable |
| 29 |
|
in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors. |
| 30 |
|
I've fixed the data, and added a kludgy way of testing at compile time that |
| 31 |
|
the lengths are correct (equal to the number of opcodes). |
| 32 |
|
|
| 33 |
|
8. Following on from 7, I added a similar kludge to check the length of the |
| 34 |
|
eint vector in pcreposix.c. |
| 35 |
|
|
| 36 |
|
9. Error texts for pcre_compile() are held as one long string to avoid too |
| 37 |
|
much relocation at load time. To find a text, the string is searched, |
| 38 |
|
counting zeros. There was no check for running off the end of the string, |
| 39 |
|
which could happen if a new error number was added without updating the |
| 40 |
|
string. |
| 41 |
|
|
| 42 |
|
10. \K gave a compile-time error if it appeared in a lookbehind assersion. |
| 43 |
|
|
| 44 |
|
11. \K was not working if it appeared in an atomic group or in a group that |
| 45 |
|
was called as a "subroutine", or in an assertion. Perl 5.11 documents that |
| 46 |
|
\K is "not well defined" if used in an assertion. PCRE now accepts it if |
| 47 |
|
the assertion is positive, but not if it is negative. |
| 48 |
|
|
| 49 |
|
|
| 50 |
Version 8.01 19-Jan-2010 |
Version 8.01 19-Jan-2010 |
Parent Directory
| 
Revision Log
| 
Patch