[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
compile-time processing of REQUIRE
- To: firstname.lastname@example.org
- Subject: compile-time processing of REQUIRE
- From: email@example.com (Jon L White)
- Date: Mon, 3 Aug 87 20:15:34 PDT
- Cc: firstname.lastname@example.org
- In-reply-to: Alan Snyder's message of Mon, 03 Aug 87 10:18:31 PDT <8708031718.AA03272@hplsny>
You've jumped ahead into another problem -- that of the pervasiveness of
the COMPILE context.
But I was talking merely about the compiler's interface -- when and where
it decides to wrap an eval-when(eval compile load) around a form. When the
user supplies his own wrapper, e.g.
(eval-when (eval load) (require "tarnation"))
then this form is not implicitly "wrapped", since the user's actions take
precedence over the implicit activity. That is, Lucid's compiler does
NOT convert the above form into anything like.
(eval-when (eval load)
(eval-when (eval compile load) (require "tarnation"))
I wonder if this view of "implicit wrapping" is used in other compiler?
-- JonL --