Revision: 458
http://vcs.pcre.org/viewvc?view=rev&revision=458
Author: ph10
Date: 2009-10-03 17:48:17 +0100 (Sat, 03 Oct 2009)
Log Message:
-----------
Documentation update.
Modified Paths:
--------------
code/trunk/doc/perltest.txt
Modified: code/trunk/doc/perltest.txt
===================================================================
--- code/trunk/doc/perltest.txt 2009-10-03 16:24:08 UTC (rev 457)
+++ code/trunk/doc/perltest.txt 2009-10-03 16:48:17 UTC (rev 458)
@@ -8,20 +8,25 @@
The data lines are processed as Perl double-quoted strings, so if they contain
" $ or @ characters, these have to be escaped. For this reason, all such
-characters in testinput1 and testinput4 are escaped so that they can be used
-for perltest as well as for pcretest. The special upper case pattern
-modifiers such as /A that pcretest recognizes, and its special data line
-escapes, are not used in these files. The output should be identical, apart
-from the initial identifying banner.
+characters in testinput1, testinput4, testinput6, and testinput11 are escaped
+so that they can be used for perltest as well as for pcretest. The special
+upper case pattern modifiers such as /A that pcretest recognizes, and its
+special data line escapes, are not used in these files. The output should be
+identical, apart from the initial identifying banner.
The perltest.pl script can also test UTF-8 features. It recognizes the special
modifier /8 that pcretest uses to invoke UTF-8 functionality. The testinput4
-file can be fed to perltest to run compatible UTF-8 tests.
+and testinput6 files can be fed to perltest to run compatible UTF-8 tests.
+However, it is necessary to add "use utf8;" to the script to make this work
+correctly.
+The testinput11 file contains tests that use features of Perl 5.10, so does not
+work with Perl 5.8.
+
The other testinput files are not suitable for feeding to perltest.pl, since
they make use of the special upper case modifiers and escapes that pcretest
uses to test some features of PCRE. Some of these files also contains malformed
regular expressions, in order to check that PCRE diagnoses them correctly.
Philip Hazel
-September 2009
+October 2009
