| 1 |
nigel |
41 |
The perltest program |
| 2 |
|
|
-------------------- |
| 3 |
|
|
|
| 4 |
|
|
The perltest program tests Perl's regular expressions; it has the same |
| 5 |
|
|
specification as pcretest, and so can be given identical input, except that |
| 6 |
|
|
input patterns can be followed only by Perl's lower case modifiers and /+ (as |
| 7 |
|
|
used by pcretest), which is recognized and handled by the program. |
| 8 |
|
|
|
| 9 |
|
|
The data lines are processed as Perl double-quoted strings, so if they contain |
| 10 |
|
|
" \ $ or @ characters, these have to be escaped. For this reason, all such |
| 11 |
|
|
characters in testinput1 and testinput3 are escaped so that they can be used |
| 12 |
|
|
for perltest as well as for pcretest, and the special upper case modifiers such |
| 13 |
|
|
as /A that pcretest recognizes are not used in these files. The output should |
| 14 |
|
|
be identical, apart from the initial identifying banner. |
| 15 |
|
|
|
| 16 |
|
|
The testinput2 and testinput4 files are not suitable for feeding to perltest, |
| 17 |
|
|
since they do make use of the special upper case modifiers and escapes that |
| 18 |
|
|
pcretest uses to test some features of PCRE. The first of these files also |
| 19 |
|
|
contains malformed regular expressions, in order to check that PCRE diagnoses |
| 20 |
|
|
them correctly. |
| 21 |
|
|
|
| 22 |
|
|
Philip Hazel <ph10@cam.ac.uk> |
| 23 |
|
|
January 2000 |