[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Issue: LOAD-TIME-EVAL (Version 8)
- To: sandra%defun@cs.utah.edu (Sandra J Loosemore)
- Subject: Re: Issue: LOAD-TIME-EVAL (Version 8)
- From: David N Gray <Gray@DSG.csc.ti.com>
- Date: Wed, 25 Jan 89 17:54:12 CST
- Cc: Kent M Pitman <KMP@STONY-BROOK.SCRC.Symbolics.COM>, Moon@STONY-BROOK.SCRC.Symbolics.COM, CL-Compiler@SAIL.STANFORD.EDU
- In-reply-to: Msg of Wed, 25 Jan 89 14:52:54 MST from sandra%defun@cs.utah.edu (Sandra J Loosemore)
- Sender: GRAY@Kelvin.csc.ti.com
> What I was envisioning as a solution to Moon's
> objections is that if you had several references to the same (EQ)
> LOAD-TIME-VALUE expression within a single call to EVAL, COMPILE, or
> COMPILE-FILE, it would be OK to evaluate it only once, but that each call
> to EVAL, COMPILE, or COMPILE-FILE would have to start out with a fresh
> "cache".
But "within a single call to EVAL" would have to mean lexically within the
form being evaluated (you don't want to re-do LOAD-TIME-VALUEs within
evaluated functions called by the current form), so interpreted functions
would need to be thought of as closures over the cache. But you wouldn't
want that overhead on every interpreted function, so we're right back to
having the evaluator need to do a pre-pass on functions.