[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Handling of "no applicable method"
- To: commonloops.pa@Xerox.COM
- To: commonloops.pa@Xerox.COM
- Subject: Handling of "no applicable method"
- From: fritzson@PRC.Unisys.COM (Richard Fritzson)
- Date: 9 Mar 88 12:00 EST (Wednesday)
- Redistributed: commonloops.pa
When I mistakenly apply a slot accessor on an entirely inappropriate
object (such as NIL), I would expect to see something like "No
applicable method". Instead the method for "slot-value-using-class
(standard-class)" is invoked on the object producing very bad results.
(On the Xerox machines a lower level error,"ARG NOT IWMC-CLASS", is
produced; on some unix lisps, including kcl and franz, you get a
segmentation fault.)
I can see a use of slot-value being optimized into this situation, but
why do accessors produce it too?