[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[no subject]

Reminder for more error checking:
    Date: 18 January 1981 23:08-EST
    From: Kent M. Pitman <KMP at MIT-MC>
    (SETQ MSGFILES 0)
    (ERROR)
    .VAL 0; ...
    or
    (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?