[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
issue COMPILED-FUNCTION-REQUIREMENTS, version 4
- To: firstname.lastname@example.org
- Subject: issue COMPILED-FUNCTION-REQUIREMENTS, version 4
- From: David A. Moon <Moon@STONY-BROOK.SCRC.Symbolics.COM>
- Date: Tue, 14 Mar 89 20:27 EST
- Cc: email@example.com
- In-reply-to: <8903131544.AA02070@defun.utah.edu>
I much prefer the option FLUSH, which was in version 2 but has been
removed. That option was to remove the COMPILED-FUNCTION type.
This type has no portable meaning and never should have existed.
I have no objection to the proposed specification of what the COMPILE
and COMPILE-FILE functions do, but it should be decoupled from the
COMPILED-FUNCTION type and discussed under the rubric of those two
functions. The parts about COMPILER-LET and EVAL-WHEN can probably be
removed (assuming the COMPILER-LET-CONFUSION proposal that eliminates
the possibility of COMPILER-LET binding any variables at run time
passes, and the EVAL-WHEN-NON-TOP-LEVEL proposal passes) since they are
redundant; there is never any interpeter/compiler difference for
COMPILER-LET or EVAL-WHEN any more.