[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: issue EVAL-WHEN-NON-TOP-LEVEL
- To: Rob.MacLachlan@wb1.cs.cmu.edu
- Subject: Re: issue EVAL-WHEN-NON-TOP-LEVEL
- From: sandra@cs.utah.edu (Sandra J Loosemore)
- Date: Fri, 20 May 88 13:29:58 MDT
- Cc: sandra@cs.utah.edu (Sandra J Loosemore), cl-compiler@sail.stanford.edu
- In-reply-to: Rob.MacLachlan@WB1.CS.CMU.EDU, Fri, 20 May 88 14:59:13 EDT
> Date: Fri, 20 May 88 14:59:13 EDT
> From: Rob.MacLachlan@WB1.CS.CMU.EDU
>
> This is a reasonable approach to making EVAL-WHEN well defined, but there
> seems to be a problem when the COMPILE situation is specified without the
> EVAL situation. In this form, I believe (FOO) would never be evaluated in
> any context, which is definitely an incompatible change:
> (eval-when (compile)
> (eval-when (compile)
> (foo)))
Yes, you are correct that under the current proposal, (foo) would never
be evaluated. I do not think it is "definitely" an incompatible change,
however. The current wording in CLtL seems to leave this behavior
unspecified and I don't know what the original intention was.
-Sandra
-------