[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
find my slot
- To: Moon@stony-brook.scrc.symbolics.com
- Subject: find my slot
- From: Jon L White <firstname.lastname@example.org>
- Date: Thu, 29 Nov 1990 14:58:36 PST
- Cc: email@example.com, mop@arisia.Xerox.COM
- In-reply-to: "Moon@stony-brook.scrc.symbolics.com's message of Thu, 29 Nov 1990 12:19:00 PST <19901129201934.1.MOON@KENNETH-WILLIAMS.SCRC.Symbolics.COM>"
re: Date: Tue, 27 Nov 1990 12:06 EST
Of the 5 major CLOS metaobject types (classes, generic functions,
methods, method combinations, and slot definitions), three have
retrieval functions (FIND-CLASS, FIND-METHOD, FIND-METHOD-COMBINATION),
and one doesn't need one (generic functions). What happened to
It isn't necessary, because CLASS-DIRECT-SLOTS and CLASS-SLOTS are
specified to return lists, therefore the existing FIND function can be
used (with :KEY #'SLOT-DEFINITION-NAME).
If Harley's question is only about introspective capabilities, then
we don't need FIND-METHOD either -- because of the documentation for
GENERIC-FUNCTION-METHODS, METHOD-QUALIFIERS, and METHOD-SPECIALIZERS.
However, FIND-CLASS and FIND-METHOD are "Chapter 2" facilities. Would
you now propose to remove FIND-METHOD? or would the uniformity of
interface resulting from the addition of FIND-SLOT-DEFINITION be
better than trying to retrench into a minimal kernal language?
-- JonL --