[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Issue: LOAD-TIME-EVAL, Sub-Issue: Displacing macros
- To: KMP@STONY-BROOK.SCRC.Symbolics.COM
- Subject: Issue: LOAD-TIME-EVAL, Sub-Issue: Displacing macros
- From: Jon L White <firstname.lastname@example.org>
- Date: Tue, 31 Jan 89 05:23:50 PST
- Cc: Gray@DSG.CSC.TI.COM, KMP@STONY-BROOK.SCRC.Symbolics.COM, Moon@STONY-BROOK.SCRC.Symbolics.COM, CL-Compiler@SAIL.Stanford.EDU
- In-reply-to: Kent M Pitman's message of Thu, 26 Jan 89 08:54 EST <890126085447.4.KMP@BOBOLINK.SCRC.Symbolics.COM>
re: Personally, I can't imagine how displacing macros can work at all.
Previous mail may have suggested that MacLisp's interpreter used
"displacing macros". This was not a part of the interpreter; rather, it
was a common idiom of code produced by the DEFMACRO macro. Furthermore,
it was not the only option, nor was it the default (as I remember it).
In fact, years ago I would frequently make "pure" dumps of a MacLisp
system with lots of intrepreted code stored in it, in read-only areas
(I got it there by calling PURCOPY on the definition of each interpreted
function). The macro cache feature I selected for this application was
called MACROMEMO (it worked like Interlisp's CLISPARRAY).
re: But this whole sub-issue aside, all we're really saying is that
LOAD-TIME-VALUE should not be done by displacing.
-- JonL --