2012/1/6 Levente Uzonyi <[email protected]> > On Fri, 6 Jan 2012, Mariano Martinez Peck wrote: > > On Fri, Jan 6, 2012 at 2:59 PM, Stéphane Ducasse >> <[email protected]>**wrote: >> >> >>> On Jan 6, 2012, at 2:46 PM, Levente Uzonyi wrote: >>> >>> Of course, but I'd check for the class equality first, because it's >>>> >>> faster (yeah, i know you turned off inlining of #class, but Cog doesn't >>> care about that ;)). >>> >> >> >> Ok, makes sense. >> >> >> Another thing that you should add (besides tests of course) is >>> SmallInteger >> #pointsTo: which should return false. >>> >> >> >> Ok. >> >> >> Also make sure that pointer tracing tools use #pointsTo:. In Squeak I >>> found that some of them "reinvented" this method? >>> >>> >>> I found a problem with the PointerFinder: >> http://forum.world.st/Help-**pointersTo-broken-and-fix-but-** >> I-don-t-understand-why-it-**fixes-td4244097.html<http://forum.world.st/Help-pointersTo-broken-and-fix-but-I-don-t-understand-why-it-fixes-td4244097.html> >> However, I still don't understand why it works if I use #instVarsInclude: >> and doesn't with #pointsTo: >> > > IIUC your problem is that MethodContext instances show up as objects which > point to your object.
yes > And in fact (i think, but didn't check) they do point to your object, > because the sender of those MethodContexts is the Date object. probably > I think it only depends on when GC will happen. If the GC kicks in too > late, then PointerFinder will find those transient objects and they will be > listed. > > Thanks Levente. However, #pointersToExcept: does a GC at the beginning... so.. am I missing something? Thanks again. > > Levente > > > >> >> Do you mean what I understand :)? that some tools compiled methods? :) >> >>> >>> Stef >>> >>> >>> >> >> -- >> Mariano >> http://marianopeck.wordpress.**com <http://marianopeck.wordpress.com> >> > -- Mariano http://marianopeck.wordpress.com
