[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Lazy error signaling?
- To: dussud@lucid.com
- Subject: Lazy error signaling?
- From: kab@charon.MIT.EDU (Kim A. Barrett)
- Date: Mon, 14 May 90 17:59:36 EDT
- Cc: jonl@lucid.com, Common-Lisp-Object-System@MCC.COM
- In-reply-to: Patrick Dussud's message of Mon, 14 May 90 08:21:52 PDT <9005141521.AA04941@challenger>
> ... bad practice for the implementation to add obscure system defined methods
> in places that are visible by the programmer. ...
Right. My suggested possible implementation of (... :required t) is completely
bogus. I was confused about how our implementation of STANDARD method
combination works (it doesn't use (primary () :required t) at all).
Regarding precomputing of combined methods and METHOD-COMBINATION-ERROR, this
only works if the place doing the precomputing knows how to detect and
gracefully handle a corresponding call to METHOD-COMBINATION-ERROR. Since we
didn't specify much about the behavior of METHOD-COMBINATION-ERROR, this is
currently impossible in portable code. Of course, it's not clear that
precomputing methods can be done for any useful purpose without a metaobject
proposal anyway.
kab