hi folks, just wanted to ask what the correct way we should expect deprecations to be used. Updates are great of course! I am running all the tests to generate baseline results and then try and chip away at a few of the new/old errors. However, now when I run the whole test suite it pauses because there is a deprecation. If we are going to deprecate a method would it be good to also fix up the senders? or have a mechanism that suppresses the deprecation in the context of the test run? thanks, Mike On Thu, Jun 11, 2009 at 4:50 PM, Marcus Denker<denker@acm.org> wrote:
#10334 ====== Issue 877: Â Â Â Collection>>isZero use deprecatedDescrition: instead of deprecated Issue 686: Â Â Â Remove dice methods in Random Issue 631: Â Â Â API Consistency on MIMEDocument
-- Marcus Denker - http://marcusdenker.de PLEIAD Lab - Computer Science Department (DCC) - University of Chile
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project