2010/8/27 Marcus Denker <marcus.den...@inria.fr> > > Smalltalk.true. > > takes a while, but it does not try to call #quitPrimitive. Which it would > if Methodfinder would not be based on a positive list. > > > Ah, and a negative list was I think not used as it is too dangerous wrt. to > completenes. If the positive list is incomplete, you miss > a hit. If the negative list is incomplete, you woud crash in some nasty > way. > > Just look at the lists and how many methods you find that have been removed > years ago... > > It's not just methods like #quitPrimitive. In general, with the image based > nature you could end up modifying state of objects > in the image by accident, and realize it weeks later. > e.g. this means one would very carefully protect the reflective model, to > not accidentally modify the methodDictionary, for example. >
So if someone did try my simulation approach above the only lists needed would be a positive list of those primitives that were safe to apply to any object and a positive list of those primitives it would be safe to apply to the objects allocated during the simulation. best, Eliot > Marcus > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > > _______________________________________________ > 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
