[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Grief with T and NIL as Filespecs
- To: (BUG Lisp) at MIT-MC, KMP at MIT-MC I agree with KMP wholeheartedly -- down with T and NIL as filespecs! (Defun RawTyo Nargs (cond ((> Nargs 1) (Unwind-Protect (prog2 (Binary-Mode T (arg 2)) (tyo (arg 1) (arg 2))) (Binary-Mode Nil (arg 2)))) (T (Unwind-Protect (prog2 (Binary-Mode T) (Tyo (arg 1))) (Binary-Mode Nil))))) Regards, Mark
- To: GSB at MIT-MC, (BUG LISP) at MIT-MC
- Subject: Re: Grief with T and NIL as Filespecs
- From: MILLER@MIT-AI
- From: KMP at MIT-MC (Kent M. Pitman)
- Date: Sun, 19 Nov 79 14:47:31 GMT
- Date: Mon, 19 Nov 79 14:18:00 GMT
- Cc: RWK at MIT-MC, REES at MIT-MC
- Original-date: 11/19/79 10:47:31 EDT
- Original-date: 19 NOV 1979 0918-EST
From: GSB@MIT-ML
Date: Sun, 19 Nov 79 04:03:58 GMT
Original-Date: 11/19/79 00:03:58 EDT
Subject:
Date: 18 NOV 1979 0736-EST
From: KMP at MIT-MC (Kent M. Pitman)
(SETQ ^R T ^W T OUTFILES '(NIL)) according to the lisp manual will
make the output go to the terminal. It doesn't -- it does
a .VAL 0; EROR5A+22>>PUSHJ P,UINT
instead. The lisp manual quite 'clearly' states that if ^W is on,
that the default output destinations do not include the tty unless
^R is on and NIL is a member of the OUTFILES list...
-kmp
Obviously the lisp manual should be fixed, since this 'clearly'
contradicts newio conventions. (Sigh. My personal opinion is that
T and NIL should be flushed as filespecs. Too much greif.)
-----
Well, step one could be to change the losing default error handlers
so they don't try to print to '(T) ... This caused REES and me no end of
hassles this weekend. The number of cases of file objects and lists
thereof that a printer must handle to be compatible as a value of PRIN1 is
ridiculous. -kmp