[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Issue: FUNCTION-COERCE-TIME (Version 2)
- To: Kent M Pitman <KMP@STONY-BROOK.SCRC.Symbolics.COM>
- Subject: Re: Issue: FUNCTION-COERCE-TIME (Version 2)
- From: masinter.pa@Xerox.COM
- Date: 2 Oct 88 14:24 PDT
- Cc: Masinter.PA@Xerox.COM, CL-Cleanup@SAIL.STANFORD.EDU
- In-reply-to: Kent M Pitman <KMP@STONY-BROOK.SCRC.Symbolics.COM>'s message of Fri, 16 Sep 88 11:35 EDT
Well, this is a puzzle. It seems intertwined in an odd way with
FUNCTION-CALL-EVALUATION-ORDER. There we want to leave unspecified where
efunctuation takes place, but here we're trying to nail it down. There it
was important for performance. Here it isn't except where it is. Is it?
I.e., is there a performance hit for LAZY? Certainly it would force some
inlining of macros not to.
I'll go for HYBRID. Its the most implementable, and reasonable to explain,
and seems to cause the least performance hit.
Probably we need to list explicitly which functions with functional
arguments are lazy and which are ambitious.