[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
omissions from chapter 3
- To: Gregor.pa@Xerox.COM
- Subject: omissions from chapter 3
- From: David N Gray <Gray@DSG.csc.ti.com>
- Date: Wed, 8 Feb 89 14:38:50 CST
- Cc: Common-Lisp-Object-System@SAIL.STANFORD.EDU
- Sender: GRAY@Kelvin.csc.ti.com
I'm puzzled by some of the things that were in document 88-003 [the
March draft of the MOP] but disappeared in document 89-003 [December].
CHECK-INITARGS and DEFAULT-INITARGS [88-003 p. 3-12] have disappeared.
OK, maybe these don't need to be standardized, but note that pages 1-41
and 42 will need to be updated -- it mentions DEFAULT-INITARGS and
CLASS-SLOT-INITARGS, which has also disappeared.
Also gone are CLASS-DIRECT-SLOT-INITARGS [p. 3-17], CLASS-SLOT-INITARGS,
CLASS-DIRECT-INITARGS, and CLASS-INITARGS [p. 3-18]; is that
Generic functions VALID-CLASS-OPTION-P, VALID-SLOT-DESCRIPTION-P, and
VALID-SLOT-OPTION-P [all on page 3-15 of 88-003] are gone. The new
document doesn't discuss how extensions to the options are to be
handled. Is the idea that all class and slot options appearing in a
DEFCLASS will simply be passed on to MAKE-INSTANCE and it will decide
what is legal? If so, does that mean that MAKE-INSTANCE of a class will
Starting on page 3-43 of 88-003 is a three page discussion of the
expansion of DEFINE-METHOD-COMBINATION, while document 89-003 has
nothing. Should I assume from this that you have decided that the old
description was wrong, but don't yet know what the right answer is?
The "instance access optimization protocol" [88-003 p. 56] has
disappeared. We had already implemented
OPTIMIZE-SETF-SLOT-VALUE, STANDARD-INSTANCE-ACCESS, and
(SETF STANDARD-INSTANCE-ACCESS), and it all seemed to be working quite
nicely. This seems like a significant loss in functionality for the