2009/6/8 Christian Haider <Christian.Haider@smalltalked-visuals.com>:
I would get rid of these #initialize methods and use lazy initialization instead. Simple redefinitions in subclasses, no worries.
Cheers, Christian
Using this pattern here and there is at an affordable cost. But generalizing it, you take the risk to multiply cost of every access to an inst var by a huge amount. That would deserve some bench too. Nicolas PS: I'd like to have time to spend thinking about a system that would dynamically change methodDictionary per instance based on previous execution results for such typical cases.
-----Ursprüngliche Nachricht----- Von: pharo-project-bounces@lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] Im Auftrag von Stéphane Ducasse Gesendet: Montag, 8. Juni 2009 18:15 An: Pharo Development Betreff: [Pharo-project] About super initialize
Hi
in http://code.google.com/p/pharo/issues/detail?id=135 may be stupidly I was thinking that it would be nice to check all the initialize methods that are not doing a super call, and fix them. Alain did this crazy and boring tasks and I was reviewing his code. Now I was wondering if it makes sense to add super initialize to the direct subclasses of Object. I have the impression that it is good for uniformity but we are calling an empty so we could do the following only fix the caller that are not subclasses of Object.
What is your point of view,
stef
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project