Yes, I read those two things too... but it doesn't seem like a giant
leap of an improvement :)
On 04/05/2011 02:34 PM, Alexandre Bergel wrote:
I remember Fred has lazy initialization of variable. All variables are lazy
initialized. This means that variables set to nil when you change the class are
lazy initialized.
It has been a long time I looked at it.
Alexandre
On 4 Apr 2011, at 16:32, Stéphane Ducasse wrote:
In fact he got a better changeClassToThatOf: implementation and got kind of
initform for slots.
Stef
I do read French too, no problem.
I'm having a look at
http://fredrivard.ifrance.com/fredrivard/pub/dicl/dicl.ps
That seems related.
On 04/04/2011 09:20 PM, Alexandre Bergel wrote:
he he. I am not sure Fred wrote in English.
http://scg.unibe.ch/scgbib?_k=qQPhJdNf&query=rivard
Cheers,
Alexandre
On 4 Apr 2011, at 14:15, Toon Verwaest wrote:
Do you have an exact reference on this?
On 04/04/2011 05:55 PM, Stéphane Ducasse wrote:
Another very cool thing that we can do now (which would require 3 lines of
change in my system though), is that the slot can also be responsible for
instance migration. There are four cases:
1- the instance variable didn't exist and now it does
2- the instance variable existed but disappeared
3- the metaobject changed (new semantics)
4- the metaobject stayed the same
Did you check the work of fred rivard because he was managing the dynamic
change of class and managing slot reinitialization?
Basically the only case that is "handled" by standard Pharo is case 1; and what
you do there is putting nil in the field. In our model the slot could do something more
interesting when it's migrating the instances. And we could tackle the other cases too. I
think it's starting to get ideal to implement an active context on top ;-)
cheers,
Toon
