On Thu, Dec 24, 2009 at 11:46 AM, Stéphane Ducasse <
[email protected]> wrote:
> > What's MW ?
>
> MethodWrapper. But you cannot wrap the complete system like do: (if I
> remember correctly).
>
>
ok
> > Yes, I noticed that too. Is very probable that messages very general that
> are used a lot will bring the class again.
>
> Yes the problem is to identify them.
> We tried a bit not too much with mathieu but was not obvious
>
>
yes haha
> > That's the idea of the tracer. WIth this tracer you *should* be able to
> see the messages chain that makes you bring the class (why it was used). But
> I don't know if this stuff is working, as you said.
>
> which tracer?
>
>
Suppose you evaluate this steps:
Smalltalk at: #MDFaultDict put: Dictionary new.
ImageSegment discoverActiveClasses
.... do something here, browse, whatever ....
ImageSegment activeClasses
Here, you can change activeClasses to use recoverFromMDFaultWithTrace
instead of recoverFromMDFault
and with this you can see who used that class. It is stored in Smalltalk at:
#MDFaultDict
Ok...at least that is what I understood, but as this is not working, I am
not sure.
What I suggest:
> - create a new category in the class and move all the methods that
> could be removed. Tag them as deprecated.
- in imageSegments just clean :)
>
>
Ok. Perfect.
Cheers
Mariano
Stef
> _______________________________________________
> 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
