[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: who makes class-prototype
- To: Aaron Larson <alarson@src.honeywell.com>
- Subject: Re: who makes class-prototype
- From: Gregor.pa@Xerox.COM
- Date: Wed, 17 Aug 88 19:45 PDT
- Cc: commonloops.pa@Xerox.COM
- Fcc: BD:>Gregor>mail>outgoing-mail-3.text.newest
- In-reply-to: <8808172023.AA21539@pavo.src.honeywell.com>
- Line-fold: no
Date: Wed, 17 Aug 88 15:23:05 CDT
From: alarson@src.honeywell.com (Aaron Larson)
About a month ago Gregor posted several versions of a message with subject
"Re: method discrimination on persistent objects" that contained the
following:
(defmethod allocate-instance ((class db-class))
(let ((instance (call-next-method)))
(setf (slot-value instance 'object-id) (allocate-object-id))
instance))
The problem is knowing whether 'allocate-object-id' is called when the
class-prototype instace is allocated. In my application it is imperative
that it not be. Hence it is necessary that CLOS specifies that
allocate-instance is not called for the class-prototpe, or that there be
some canonical way for an application to determine that the current call is
to make the class-prototype.
To help me think about this, could you explain why it is, in your
application, that allocate-object-id not be called when allocating
the prototype?
-------