[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Comments on current state of Initialization.
- To: Jon L White <firstname.lastname@example.org>
- Subject: Comments on current state of Initialization.
- From: David A. Moon <Moon@STONY-BROOK.SCRC.Symbolics.COM>
- Date: Sat, 21 May 88 19:04 EDT
- Cc: common-lisp-object-system@SAIL.STANFORD.EDU
- In-reply-to: <8805211344.AA08392@bhopal.lucid.com>
Date: Sat, 21 May 88 06:44:29 PDT
From: Jon L White <email@example.com>
Why should there still be three initialization protocls: "shared-initialize",
"initialize-instance", and "reinitialize-instance"?
[Summary: replace reinitialize-instance with a keyword argument to
Two reasons come immediately to mind: shared-initialize is also used when a
class is redefined or change-class is called; reinitialize-instance is to be
called directly by the user, but initialize-instance cannot be (review how
the keyword arguments get validated).