[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[no subject]
- To: (BUG LISP) at MIT-MC
- From: KMP at MIT-MC (Kent M. Pitman)
- Date: Mon, 19 Jan 81 04:08:00 GMT
- Original-date: 18 JAN 1981 2308-EST
:L
ALLOC? N
(SETQ MSGFILES 0)
(ERROR)
.VAL 0; ...
:L
ALLOC? N
(SETQ MSGFILES 'FOO)
(ERROR)
PURPG;....
In .INFO.;LISP NEWS, bad values of MSGFILES are documented to cause an
IO-LOSSAGE type error (after setting MSGFILES to '(T)), similar to the
way bad BASE and IBASE values are treated with FAIL-ACT breaks. Couldn't
Lisp be coaxed to do something along the lines of what it's documented to?
-kmp