> On 8 Sep 2019, at 10:15, [email protected] wrote: > > Hi, I really like the idea of returning a node object for the initialization. > From seeing the class definition, I think we should assume that: > > - the receiver of the slot instantiation message is a Slot. > - the parameters to the slot instatiation message are literals or > literal-only expressions. > > Do you think that these assumptions / constraints are cool / enough?
I had the same :) Now I wondered if allowing a block would make sense. But it automatically raises the evaluation environment so I would prefer not. > Cheers. > > On Sun, 8 Sep 2019, 09:41 ducasse, <[email protected] > <mailto:[email protected]>> wrote: > Hi > > I’m fixing the class definition parser and I have a question. > > I’m stabilizing the API of CDSlotNode > > > 1 ‘first' => LazyClassVariable default: 5. > 2 ’second' => InstanceVariableSlot. > 3 ‘instVar3’ > > Here is a proposal > > slotdefinition(3) name ? variable name > >>> ’instVar3' > > slotDefinition(2) slotClass? > >>> InstanceVariableSlot > > slotDefinition(1) initializationMessage > >>> 'default: 5’ > or better > >>> Node(default: 5) if it exist > > S. > > >
