On Mar 17, 2010, at 10:05 AM, Tudor Girba wrote:
Hi Stef,
On 17 Mar 2010, at 09:50, Stéphane Ducasse wrote:
On Mar 17, 2010, at 9:23 AM, Lukas Renggli wrote:
It tries to work with methods and classes through symbolic names.. and you immediately end up with gemmorage of a need to keep separate 'core' and 'extension' , 'meta' and 'instance-side' methods in your model.
Yes, that's what I suggested, merge the extension and core dictionaries.
I do not see how? without first class class and no string match: '* class' ? I'm curious
The issue is not between instance side and meta side. The issue is with having two dictionaries for each: one for extensions and one for definitions. If we have the information about which classes are defined in this package, we only need to store the methods for the class and we know which are extensions and which are not.
this is not that simple. For each class I have to know the methods (defined | extended) So I have to encode that information why because not all the methods of a defined class are defined in a package! The class point defined in package graphics can be extended by myPackage and these methods should not be part of the Graphics. So I always need three information Class * method * extended|defined
Cheers, Doru
-- www.tudorgirba.com
"Every now and then stop and ask yourself if the war you're fighting is the right one."
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project