| 21 |
5. The construct (?&) was not diagnosed as a syntax error (it referenced the |
5. The construct (?&) was not diagnosed as a syntax error (it referenced the |
| 22 |
first named subpattern) and a construct such as (?&a) would reference the |
first named subpattern) and a construct such as (?&a) would reference the |
| 23 |
first named subpattern whose name started with "a" (in other words, the |
first named subpattern whose name started with "a" (in other words, the |
| 24 |
length check was missing). |
length check was missing). Both these problems are fixed. "Subpattern name |
| 25 |
|
expected" is now given for (?&) (a zero-length name), and this patch also |
| 26 |
|
makes it give the same error for \k'' (previously it complained that that |
| 27 |
|
was a reference to a non-existent subpattern). |
| 28 |
|
|
| 29 |
6. The erroneous patterns (?+-a) and (?-+a) give different error messages; |
6. The erroneous patterns (?+-a) and (?-+a) give different error messages; |
| 30 |
this is right because (?- can be followed by option settings as well as by |
this is right because (?- can be followed by option settings as well as by |
| 31 |
digits. I have, however, made the messages clearer. |
digits. I have, however, made the messages clearer. |
| 32 |
|
|
| 33 |
|
7. Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns |
| 34 |
|
than the number used in the conditional) now cause a compile-time error. |
| 35 |
|
This is actually not compatible with Perl, which accepts such patterns, but |
| 36 |
|
treats the conditional as always being FALSE (as PCRE used to), but it |
| 37 |
|
seems to me that giving a diagnostic is better. |
| 38 |
|
|
| 39 |
|
8. Change "alphameric" to the more common word "alphanumeric" in comments |
| 40 |
|
and messages. |
| 41 |
|
|
| 42 |
|
9. Fix two occurrences of "backslash" in comments that should have been |
| 43 |
|
"backspace". |
| 44 |
|
|
| 45 |
|
|
| 46 |
Version 7.4 21-Sep-07 |
Version 7.4 21-Sep-07 |
Parent Directory
| 
Revision Log
| 
Patch