[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: commonloops.pa@Xerox.COM
- Subject: slot unbound
- From: jkf%frisky%franz@ucbarpa.Berkeley.EDU (John Foderaro)
- Date: Tue, 30 Aug 88 16:21:22 PDT
- Cc: larus%ucbarpa%franz@ucbarpa.Berkeley.EDU, bugs%franz@ucbarpa.Berkeley.EDU
- Redistributed: commonloops.pa
Could it be that during the construction of a pcl class object, there
is a period of time between the time the object is created and the time
that the slots are filled in that the object is unprintable because
certain slots needed for printing are unbound? If so then this should
be corrected because attempting to print such a class object causes
slot-unbound to be called which creates an error message including the
object in question which causes the slot-unbound error to occur and
so on and so on.
The slots necessary for printing should be given initial dummy
values so the object is at least printable.
You can often cause this recursive error to happen by tracing
'class-of' before loading in a file containing defclasses.