[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Comments on current state of Initialization.
- To: Moon@stony-brook.scrc.symbolics.com
- Subject: Comments on current state of Initialization.
- From: Jon L White <edsel!jonl@labrea.stanford.edu>
- Date: Mon, 23 May 88 15:32:51 PDT
- Cc: common-lisp-object-system@sail.stanford.edu
- In-reply-to: David A. Moon's message of Sat, 21 May 88 19:04 EDT <19880521230422.3.MOON@EUPHRATES.SCRC.Symbolics.COM>
re: Date: Sat, 21 May 88 06:44:29 PDT
From: Jon L White <edsel!jonl@labrea.stanford.edu>
Why should there still be three initialization protocls: "shared-
initialize", "initialize-instance", and "reinitialize-instance"?
[Summary: replace reinitialize-instance with a keyword argument to
initialize-instance --Moon]
Two reasons come immediately to mind: shared-initialize is also used when a
class is redefined or change-class is called; . . .
It seemed obvious to me that the "internal" callers from change-class etc.
could just as easily use a simpilifed definition of initialize-instance with
keyword argument.
-- JonL --