summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authornigel <nigel@2f5784b3-3f2a-0410-8824-cb99058d5e15>2007-02-24 21:38:09 +0000
committernigel <nigel@2f5784b3-3f2a-0410-8824-cb99058d5e15>2007-02-24 21:38:09 +0000
commit94ffc03e8ac1628911f231a91d7d8d94c2f0dc38 (patch)
tree29906e1897834846e4d630ac09285b27656f2cdc /README
parente390bd8b72ea8a359349a0d3ec2061289dc65b56 (diff)
downloadpcre-94ffc03e8ac1628911f231a91d7d8d94c2f0dc38.tar.gz
Load pcre-1.02 into code/trunk.
git-svn-id: svn://vcs.exim.org/pcre/code/trunk@7 2f5784b3-3f2a-0410-8824-cb99058d5e15
Diffstat (limited to 'README')
-rw-r--r--README11
1 files changed, 7 insertions, 4 deletions
diff --git a/README b/README
index 65fe6b2..80d9d05 100644
--- a/README
+++ b/README
@@ -33,14 +33,17 @@ a test program called pcretest, and the pgrep command.
To test PCRE, run pcretest on the file testinput, and compare the output with
the contents of testoutput. There should be no differences. For example:
- pcretest testinput /tmp/anything
- diff /tmp/anything testoutput
+ pcretest testinput some.file
+ diff some.file testoutput
Do the same with testinput2, comparing the output with testoutput2, but this
time using the -i flag for pcretest, i.e.
- pcretest -i testinput2 /tmp/anything
- diff /tmp/anything testoutput2
+ pcretest -i testinput2 some.file
+ diff some.file testoutput2
+
+The make target "runtest" runs both these tests, using the file "testtry" to
+store the intermediate output, deleting it at the end if all goes well.
There are two sets of tests because the first set can also be fed directly into
the perltest program to check that Perl gives the same results. The second set