> IMHO we should also check senders in Pharo and Pharo Web. Pharo core in > itself is nothing. Pharo is the platform for other tools. We have the dev and > web image. We should take care about the packages that are loadable in Pharo. > I am not saying not to remove the method, but at least, to check in dev and > web images and if there are senders, send an email to the > developers/maintainers notifying about this change. Even if the messages > shouldn't be part of the API. With this we avoid possible DNU at runtime. Not > all the external packages covers a good percent of tested code in their unit > tests. >
Yes... but there is really stuff that nobody needs. For the other, we should just put removals on the bugtracker and make sure that we check with the main image before removal... In general, I hope to revisit the idea of supporting software evolution in the language... see e.g. the paper http://scg.unibe.ch/scgbib?query=Nier08b&display=abstract for some thoughts of what is needed. Marcus _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
