Le 28/01/2014 18:41, Pharo4Stef a écrit :
> this is years since I clean Morphic (may be I’m that good at it) but this is
> important to
> go step by step. So I would really like to get a list of simple actions.
> Do you have an idea?
What about a brutal scheme, independent of all code quality considerations:
- dedicate a Pharo release process *only* to Morphic cleaning so people
will know it gona be brutal
- mark as deprecated all morphic methods unsused in the system. When a
client (like me with DrGeo), use some of the deprecated method, fill a
bug ticket, then discussion should arise about what to do:
i. unmark it as deprecated
ii. move it in external package
iii. adoption by the client in its application code
- do the same with unused classes from the Morph hierarchy.
I guess Steph already did some of this in the past.
The idea is you don't want to refactor unused code, right?
--
Dr. Geo http://drgeo.eu
