Previous names is a good idea We should adopt it! Stef On Jan 15, 2011, at 9:52 AM, Hernán Morales Durand wrote:
Hi Stef
2011/1/15 Stéphane Ducasse <stephane.ducasse@inria.fr>:
On Jan 14, 2011, at 6:24 PM, Hernán Morales Durand wrote:
Try PluggableSet
http://www.mail-archive.com/pharo-project@lists.gforge.inria.fr/msg22890.htm...
Is there a way for you guys to deprecate deleted classes or mantain a record of deleted behaviors? (IIRC VW did this from 2.x versions)
We try but we do not have the engineers of VW. Now find somebody that pay us just 3 engineers full time for two years and you will not recognized pharo and its process.
I know we are very few, but what about this idea, instead of just deleting a class we may adopt these simple rules:
1 - If deleting a class add the deleted class name somewhere (in a method?) 2 - If renaming a class, make the class to know its previous names like #previousNames (Norberto Manzanos implemented this for his own package management and I think is a great idea)
doesn't require tools, just some consensus and maybe a modified #deleteClass to enforce this "policy"
it sounds feasible for you? what do you think?
Hernán