[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Issue EVAL-WHEN-NON-TOP-LEVEL, v2
- To: sandra%defun@cs.utah.edu
- Subject: Issue EVAL-WHEN-NON-TOP-LEVEL, v2
- From: Jon L White <jonl@lucid.com>
- Date: Tue, 3 Jan 89 15:29:01 PST
- Cc: IIM@ECLA.USC.EDU, cl-compiler@SAIL.STANFORD.EDU
- In-reply-to: Sandra J Loosemore's message of Mon, 2 Jan 89 21:56:42 MST <8901030456.AA05311@defun.utah.edu>
re:
(eval-when (eval compile load)
(eval-when (eval compile load)
(punch-paper-tape)))
Yes, I too feel that it is absolutely unacceptable for PUNCH-PAPER-TAPE to
be called twice at compile time. Still, as far as other processing
goes, (PUNCH-PAPER-TAPE) must appear to be "at toplevel". Hmmmm, maybe
KIM's solution still doesn't dispense with the need to do a MACROLET
on EVAL-WHEN so that nested eval-whens can have the correct semantics.
-- JonL --