[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Issue DEFCONSTANT-VALUE (V2)
- To: sandra%defun@cs.utah.edu
- Subject: Issue DEFCONSTANT-VALUE (V2)
- From: Jon L White <jonl@lucid.com>
- Date: Fri, 7 Oct 88 14:48:48 PDT
- Cc: Gray@dsg.csc.ti.com, CL-Compiler@sail.stanford.edu
- In-reply-to: Sandra J Loosemore's message of Thu, 6 Oct 88 16:19:26 MDT <8810062219.AA15555@defun.utah.edu>
re: My understanding of JonL's comments on this were that Lucid only does
compile-time evaluation of the value form when the DEFCONSTANT appears
at top-level.
No, this isn't correct. Lucid's DEFCONSTANT is implemented as a very
ordinary macro which expands into an eval-when(eval compile load); so
the non-top-level behaviour depends on the treatment of eval-when at
non-top-level. Lucid's current behaviour for eval-when is not too far
off from the cl-compiler proposal, but of course it doesn't match
exactly.
-- JonL --