[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: issue PROCLAIM-ETC-IN-COMPILE-FILE, version 3
- To: Gray@DSG.CSC.TI.COM, sandra%defun@CS.Utah.EDU
- Subject: Re: issue PROCLAIM-ETC-IN-COMPILE-FILE, version 3
- From: Kent M Pitman <KMP@STONY-BROOK.SCRC.Symbolics.COM>
- Date: Tue, 14 Mar 89 09:47 EST
- Cc: CL-Compiler@SAIL.Stanford.EDU
- In-reply-to: <2814827699-4227621@Kelvin>
Date: Mon, 13 Mar 89 18:34:59 CST
From: David N Gray <Gray@DSG.csc.ti.com>
> Cost to users:
> For proposal YES, users would have no way to suppress compile-time
> evaluation of a top-level call to PROCLAIM. Wrapping it in an
> (EVAL-WHEN (EVAL LOAD)...) wouldn't work under the model of how
> EVAL-WHEN works in proposal EVAL-WHEN-NON-TOP-LEVEL:GENERALIZE-EVAL.
How about (LET () (PROCLAIM ...)) ?
Actually, I often use (EVAL '...) to defer evaluation to load time.
I have to say, though, that I don't know of any reason why I would
use PROCLAIM at toplevel and not want the compiler to notice it.
I can't remember this ever coming up.