[Pharo-project] A radical proposal (to cut down dead code)
alexandre.bergel at me.com
Sat May 28 17:06:16 CEST 2011
I like the idea. Who should identify the dead code? What role will you have? Should we send you the list of methods we need? Or do you want to take the ten most downloaded project, run their tests and identify what is used, remove dead code and ask us to try?
If you have a bit of time, then just do it. Just tell us how we can help you. I have no problem to regularly send reports. I did it for romain and David already.
My advice: whatever the complains people can do right now about breaking old code, this is a kind of action that can radically change the face of Pharo, for a better future.
Le 28 mai 2011 à 09:35, Marcus Denker <marcus.denker at inria.fr> a écrit :
> 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 Denker -- http://www.marcusdenker.de
> INRIA Lille -- Nord Europe. Team RMoD.
More information about the Pharo-project