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


This is a joke, right?  On the outside chance that its not, if you do

(setq t nil)

then the system catches it with a modern-day version of Maclisp's old
"veritas aeternae" message.  However, if you do

(set 't nil)

which should amount to the same thing, then it somehow slips by, and 
t evaluates to nil.  I tried to undo the damage with 

(set 't t)

and this did not work, so I guess you do have to reboot the system (I
will do this after sending this message).  However, at least simple
predicates and conditional actions based upon them continue to work

I'd be interested to know exactly what this *does* break.

Charles Buckley                         uucp  : mcvax!ethz!ceb
Integrated Systems Lab                  bitnet: BUCKLEY@CZHETH5A
Federal Institute of Technology         arpa  : mcvax!ethz!ceb@uunet.uu.net
CH-8092 Zurich                          ptt   : +411 256 5245