> What's MW ?
MethodWrapper. But you cannot wrap the complete system like do: (if I remember
correctly).
> 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
> 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?
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 :)
Stef
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project