[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: common-lisp-object-system@SAIL.STANFORD.EDU
- Subject: Semantic difficulties
- From: David A. Moon <Moon@STONY-BROOK.SCRC.Symbolics.COM>
- Date: Tue, 10 Feb 87 12:45 EST
- In-reply-to: The message of 7 Feb 87 01:18 EST from Dick Gabriel <RPG@SAIL.STANFORD.EDU>
Date: 06 Feb 87 2218 PST
From: Dick Gabriel <RPG@SAIL.STANFORD.EDU>
Possibly defining CALL-NEXT-METHOD to have dynamic extent within
a generic function invocation along with Moon's clarification of
100 Iterations of Call-Next-Methoditude would do the trick?
I don't think so. I don't see why it should have dynamic extent
rather than indefinite extent like all other closures. Furthermore,
changing the class in the middle of a method can make its valid
extent end even before dynamic extent ends.