[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
user interface macros
- To: Jon L White <jonl@lucid.com>
- Subject: user interface macros
- From: David A. Moon <Moon@STONY-BROOK.SCRC.Symbolics.COM>
- Date: Mon, 7 May 90 19:06 EDT
- Cc: gray@lucid.com, gregor@parc.xerox.com, mop.pa@Xerox.COM
- In-reply-to: <9005072251.AA05025@ptl-club>
- Line-fold: No
Date: Mon, 7 May 90 15:51:53 PDT
From: Jon L White <jonl@lucid.com>
So a fundamental question would first be: "How
does ENSURE-CLASS treat non-standard options in its arguments that
specify slot or class options?" A typical answer could be something
like "implementations are free to extend ...". Or, these options might
even be specified to be passed along to the required initialization
methods that ENSURE-CLASS would call [see my previous note about the
good steps taken in this direction by the the "Rainy Day" PCL.]
Quite right.