[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Various Decisions
- To: Pavel.pa@Xerox.COM
- Subject: Re: Various Decisions
- From: David A. Moon <Moon@STONY-BROOK.SCRC.Symbolics.COM>
- Date: Tue, 29 Sep 87 17:36 EDT
- Cc: Common-lisp-object-system@SAIL.STANFORD.EDU
- In-reply-to: <870929-120601-2316@Xerox>
- Line-fold: No
Date: Tue, 29 Sep 87 12:05:58 PDT
Why are folks so opposed to using the error system instead of this
NEXT-METHOD function? It seems the obvious thing, leading to more
readable code with a clearer intent.
Note that condition handlers have dynamic rather than lexical "scope"
(or whatever word you want to use for the portion of program that they
affect). Thus a HANDLER-CASE around a CALL-NEXT-METHOD might actually
intercept some inner CALL-NEXT-METHOD in some inner, nested method.
There's no way to turn off the handler as soon as the CALL-NEXT-METHOD
has succeeded in passing control to the next method.