On Dec 23, 2009, at 9:37 AM, Lukas Renggli wrote: >>> May be this is MC that does this? Does anybody knows about it? > > MC uses the changes file to restore methods that are put into an > *packagename-override protocol, see MCMethodDefinition>>#unload. > Practically this does not work, because it makes all kind of generally > invalid assumptions.
Thanks lukas. OK I have the impression that the package should know m1 is an override and when I unload I should put back the method I overrode but > >>> Then I have also another question related to the order >>> >>> P1>>*m >>> p1 >>> P2>>*m >>> p2 >>> P3>>*m >>> p3 >>> >>> right now is the load order preserved? >>> ie does P3 takes precedence over p2 and p1 > > I don't understand that question/syntax. *m means that the package P1 overrdies m1 and return ^ 'p1' Originally I did not like overrides but sometimes you cruelly need them and I want package to be backwards > > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
