Re: [Pharo-project] A radical proposal (to cut down dead code)
On May 30, 2011, at 9:59 PM, Casimiro de Almeida Barreto wrote:
Regarding this subject I think:
⢠There's impossible to authoritatively classify anything as "dead code" unless there's a reference standard of what's core and what's not core (like, Java defines the JFCs). At this point it would be useful to have a reference standard of "core classes" and their "core messages/methods".
We do not have such a reference. I do not know how you can build one without cleaning up. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.
If we have backup of old sources in squeaksource, removing old code is not something to be scared of :). BTW, we should begin to determine what is public api for devs and what is not. On Mon, May 30, 2011 at 5:23 PM, Marcus Denker <marcus.denker@inria.fr>wrote:
On May 30, 2011, at 9:59 PM, Casimiro de Almeida Barreto wrote:
Regarding this subject I think:
⢠There's impossible to authoritatively classify anything as "dead code" unless there's a reference standard of what's core and what's not core (like, Java defines the JFCs). At this point it would be useful to have a reference standard of "core classes" and their "core messages/methods".
We do not have such a reference. I do not know how you can build one without cleaning up.
Marcus
-- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.
Em 30-05-2011 17:23, Marcus Denker escreveu:
On May 30, 2011, at 9:59 PM, Casimiro de Almeida Barreto wrote:
Regarding this subject I think:
⢠There's impossible to authoritatively classify anything as "dead code" unless there's a reference standard of what's core and what's not core (like, Java defines the JFCs). At this point it would be useful to have a reference standard of "core classes" and their "core messages/methods".
We do not have such a reference. I do not know how you can build one without cleaning up.
Marcus In my mind such a cycle would be something like:
freeze -> clean up & debug -> map dependencies -> orthogonalize -> define core & extras -> implement control mechanisms to avoid "contamination/degradation" of core stuff -> document CdAB
-- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.
participants (3)
-
Casimiro de Almeida Barreto -
Guillermo Polito -
Marcus Denker