Hello.
I do not know about Torch, Moose, and related tools, and I even as a novice in the art of smalltalk, I will tell an idea. If it seems very silly then simply discarded:)

I also believe that sending information on that part of the system we use is vital for you to make any decisions with less risk of breakage of the tools that we ourselves use.

This allows you to create statistics to revalidate the code identified as unused, or else find that use is being given. I also think they should not be sent anonymously, so as to inquire the user that sent about what use is giving the system and determine if it is a compelling reason to consider. But it should be simple and automatic for a user to send this information, much as do common applications, and should be enabled if you want it or not. But, if a user does not report about his use of the system, then can not claim to be supportive.

All this collecting and sending information can only be done efficiently with a transparent tool for the user. It would be nice to know if it already exists how to use it for that purpose.


2011/5/28 Hilaire Fernandes <hilaire.fernandes@gmail.com>
Go on, then I will try DrGeo on it.

I would love to reduce the size image of the DrGeo4XO, the image is
still 14MB after cleaning.

Hilaire

Le 28/05/2011 15:35, Marcus Denker a �crit :
> Hi,
>
> There is *a lot* of dead code in the image.
>
> I guess around 1/3 of the code base in Core is just not used at all (especially Morphic).
>
> One thing I would like to do is to put, at the beginning of a development cycle,
> a call
>
> � � � self doesAnyOneUseThisTaggedIn: 'pharo 1.3'.
>
> at the beginning of *all* unsent methods. And keep it even in the released image.
>
> This way we can, within 2-3 interations, remove *a lot* of dead code.
>
> Methods where people tell us that they need them, we should tag
> with <api> or <public> or something like that.
>
>
> � � � Marcus
>
> --
> Marcus Denker �-- http://www.marcusdenker.de
> INRIA Lille -- Nord Europe. Team RMoD.
>
>
>


--
Education 0.2 -- http://blog.ofset.org/hilaire