| 87 |
matching a wide character, but failed, corruption could cause an |
matching a wide character, but failed, corruption could cause an |
| 88 |
erroneous result when trying to check for a repeat of the original |
erroneous result when trying to check for a repeat of the original |
| 89 |
character. |
character. |
| 90 |
|
|
| 91 |
|
13. Some tidying changes to the testing mechanism: |
| 92 |
|
|
| 93 |
|
(a) The RunTest script now detects the internal link size and whether there |
| 94 |
|
is UTF-8 and UCP support by running ./pcretest -C instead of relying on |
| 95 |
|
values substituted by "configure". (The RunGrepTest script already did |
| 96 |
|
this for UTF-8.) The configure.ac script no longer substitutes the |
| 97 |
|
relevant variables. |
| 98 |
|
|
| 99 |
|
(b) The debugging options /B and /D in pcretest show the compiled bytecode |
| 100 |
|
with length and offset values. This means that the output is different |
| 101 |
|
for different internal link sizes. Test 2 is skipped for link sizes |
| 102 |
|
other than 2 because of this, bypassing the problem. Unfortunately, |
| 103 |
|
there was also a test in test 3 (the locale tests) that used /B and |
| 104 |
|
failed for link sizes other than 2. Rather than cut the whole test out, |
| 105 |
|
I have added a new /Z option to pcretest that replaces the length and |
| 106 |
|
offset values with spaces. This is now used to make test 3 independent |
| 107 |
|
of link size. |
| 108 |
|
|
| 109 |
|
|
| 110 |
Version 7.0 19-Dec-06 |
Version 7.0 19-Dec-06 |
Parent Directory
| 
Revision Log
| 
Patch