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

NIL and DEFCONSTANT [Gall: Bug Report]

To: Gall%MULTICS.MIT@Think
Subject: NIL and DEFCONSTANT [Gall: Bug Report]
From: Guy Steele <gls%AQUINAS.TMC@Think>
Date: Mon, 8 Apr 85 11:16 EST
Cc: common-lisp@SU-AI.ARPA, gls%AQUINAS.TMC@Think
In-reply-to: <FAHLMAN.12100620981.BABYL@CMU-CS-C.ARPA>

Maybe a right attitude to take is that it is an error
to execute any compiled code that refers to a DEFCONSTANT'ed
name that has been re-DEFCONSTANT'ed to a different (non-EQL?)
value since the code was compiled.

That would say that it is okay to (DEFCONSTANT T 43), but then
you had better not execute any system code that refers to T.
But the evaluator probably refers to T, so in practice you had
simply better not do it.
--Guy

References:
- NIL and DEFCONSTANT [Gall: Bug Report]
  - From: "Scott E. Fahlman" <Fahlman@CMU-CS-C.ARPA>

Prev by Date: Probe-File and proposed extension.
Next by Date: Probe-File and proposed extension.
Previous by thread: NIL and DEFCONSTANT [Gall: Bug Report]
Next by thread: NIL and DEFCONSTANT [Gall: Bug Report]
Index(es):
- Date
- Thread