[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: RWK@SCRC-TENEX
- From: David Rogers <DRogers@MIT-OZ>
- From: DROGERS@MIT-OZ
- Date: Mon ,16 Apr 84 20:38:10 EDT
- Date: Mon, 16 Apr 1984 19:33 EST
- Cc: bug-file@MIT-OZ, bug-system@MIT-OZ, BUG-ZWEI@MIT-OZ, Moon@SCRC-TENEX
- Mail-from: DROGERS created at 16-Apr-84 19:38:10
Sounds like all alternatives are bad. For reference, they are:
1. Have a list of fields that it has to copy on every machine.
Then, some machines will always spit out errors (ie TOPS-20)
2. Have a list of fields to copy for each machine type. This has
been called an incredible kludge; better to have the user
get unneeded error messages.
3. Have a special "copy all fields you can" command, that each
host interprets correctly. This transfers the kludge out of
the lisp machine and into the host FILE program.
I vote for whatever kludge protects the user from brain damaged
unneeded error messages. And I don't buy the argument that
it is not the responsibility of the lisp machine to protect
the user from brain damage, either its own or that of damaged