[Pharo-dev] [Pharo4] Slots: ExampleSlotWithDefaultValue

2015-02-25 Thread Marcus Denker
Hi, Todays small improvement: ExampleSlotWithDefaultValue now allows to set the default in the definition (it was before just hard coding a value). e.g. Object subclass: #GG slots: { #gg => ExampleSlotWithDefaultValue default: 5 } classVariables: { } category: ‘PlayGro

Re: [Pharo-dev] [Pharo4] Slots: ExampleSlotWithDefaultValue

2015-02-27 Thread stepharo
:) look more and more like CLOS :) now a question: what do you accept as value: (literals or expressions). I have the impression that literals are better because no runtime needed. Stef Hi, Todays small improvement: ExampleSlotWithDefaultValue now allows to set the default in the definiti

Re: [Pharo-dev] [Pharo4] Slots: ExampleSlotWithDefaultValue

2015-02-27 Thread Marcus Denker
> On 27 Feb 2015, at 16:01, stepharo wrote: > > :) > look more and more like CLOS :) > > now a question: what do you accept as value: >(literals or expressions). > I have the impression that literals are better because no runtime needed. > right now it is very simplistic: when you accept,

Re: [Pharo-dev] [Pharo4] Slots: ExampleSlotWithDefaultValue

2015-02-27 Thread Sean P. DeNigris
stepharo wrote > I have the impression that literals are better because no runtime needed. Except it eliminates a common-sounding case like: Object subclass: #GG slots: { #creationTimestamp => ExampleSlotWithDefaultValue default: DateAndTime now } classVariables: { } category: ‘PlayGround'

Re: [Pharo-dev] [Pharo4] Slots: ExampleSlotWithDefaultValue

2015-02-27 Thread stepharo
Le 27/2/15 16:07, Marcus Denker a écrit : On 27 Feb 2015, at 16:01, stepharo wrote: :) look more and more like CLOS :) now a question: what do you accept as value: (literals or expressions). I have the impression that literals are better because no runtime needed. right now it is very