README revision 1.3 
1The files in this directory with suffixes `.t', `.d', `.r' and `.err' are
2used for testing ed.  To run the tests, set the ED variable in the Makefile
3for the path name of the program to be tested (e.g., /bin/ed), and type
4`make'.  The tests do not exhaustively verify POSIX compliance.
5
6The output of the tests is written to the two files err.o and scripts.o.
7At the end of the tests, these files are grep'ed for error messages,
8which look like:
9	*** The script u.ed exited abnormally ***
10or:
11	*** Output u.o of script u.ed is incorrect ***
12
13It is assumed that the ed being tested processes escapes (\) in file names.
14This is so that a name starting with bang (!) can be read, via:
15	r \!file
16Without the escape, a POSIX ed would attempt to read the output of
17the shell command `file'.  If the ed being tested does not support escape
18processing on file names, then the script `mkscripts.sh' should be modified
19accordingly.
20
21The POSIX requirement that an address range not be used where at most
22a single address is expected has been relaxed in this version of ed.
23Therefore, the  following scripts  which test for compliance with this
24POSIX rule exit abnormally:
25=-err.ed
26a1-err.ed
27i1-err.ed
28k1-err.ed
29r1-err.ed
30
31In addition, one of !1-err.ed or !2.ed will fail, depending on whether or
32not ed was compiled with the VI_BANG directive.
33