[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
**DRAFT** issue PROCLAIM-ETC-IN-COMPILE-FILE
- To: email@example.com
- Subject: **DRAFT** issue PROCLAIM-ETC-IN-COMPILE-FILE
- From: Jon L White <firstname.lastname@example.org>
- Date: Mon, 26 Sep 88 17:58:15 PDT
- Cc: email@example.com
- In-reply-to: Sandra J Loosemore's message of Fri, 23 Sep 88 11:56:59 MDT <8809231757.AA02537@defun.utah.edu>
re: Current Practice:
. . .
The Lucid documentation indicates
that certain functions at top-level are treated as though within an
(EVAL-WHEN (EVAL COMPILE LOAD) ...): REQUIRE, all of the package
functions listed above, INTERN, and UNINTERN; it is not clear what
happens with PROCLAIM.
Two things should be clarified here [just in case anyone raises the
issue in the future]:
(1) The forms documented by Lucid as being implicitly wrapped within
an eval-when do not include toplevel EVAL-WHEN forms; as can be seen
from the proposal regarding non-top-level eval-when's, the semantics
of the situation (EVAL COMPILE LOAD) cannot be fully "undone" by
(2) Lucid does not currently include PROCLAIM, but no doubt would be
quite happy to do so.
-- JonL --
P.S. Note that I cc'd this comment only to cl-compiler -- not to x3j13.