[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
GENERIC-FUNCTION-NAME and FIN's
- To: commonloops.pa@Xerox.COM
- Subject: GENERIC-FUNCTION-NAME and FIN's
- From: Jim Kempf <kempf%hplabsc@hplabs.HP.COM>
- Date: Sun, 10 May 87 16:34:12 pdt
Apparently, the metobject generic functions are not getting their
names set during bootstrapping. If I do (for example):
(generic-function-name (symbol-function 'pcl::add-named-class))
In addition, none of the generic functions appear to be getting their
names set via SET-FUNCALLABLE-INSTANCE-NAME. If I do:
(funcallable-instance-name (symbol-function <any generic function>))
0 (what we initialize it to).
From this, I make two conclusions:
1) As initially stated, the names of generic functions in the kernel
are not getting set during bootstrapping.
2) The names of other, user defined generic functions are not getting
set using SET-FUNCALLABLE-INSTANCE-NAME, but rather in some other way.
Note that, since SET-FUNCALLABLE-INSTANCE-NAME has hooks into the
implementation, it can set the name so that debugging and other
environmental info. can be determined.
These tests were done on the 4/21 beta version of PCL/PCLOS.
Jim Kempf email@example.com