>> My point is still valid
>>
>>>> Igor now one of the problem is see with the possible to add and access
>>>> slot everywhere is illustrated by morphic code
>>>> when a method add a property extension to a morph, another tests for its
>>>> value and the third one remove it.
>>>> You get code that is really difficult to understand.
>>
> You mean that morphs could add arbitrary slots to its instances?
yes look at addProperty and friends
> Why difficult?
Apparently you never tried to understand morphic code.
Try in Squeak 3.9 not pharo because we removed a lot of problem already
> This extension is to match the object format of Self and JavaScript.
Why do we need that?
When do you need that?
Why an instance should have a dictionary based access?
How this is integrate with our tools?
Why a good mop does not let you do that :)
We will be working on that
I asked but this is several years that I think that under specific
circumstances it would make sense
to have
Object dictionaryVariableSubclass:
but not just to look like self or javascript.
Stef
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
