Igor Stasenko wrote: > > On 31 December 2010 12:45, Igor Stasenko <[email protected]> wrote: >> On 31 December 2010 11:03, Nicolas Cellier >> <[email protected]> wrote: >>> If Pharo wants to remove these deprecated methods, an alternative >>> policy is to move deprecated methods in a separate backward >>> compatibility package. > > Utilities moveDeprecatedToCruft > "put all senders of #deprecated to '*Pharo-Cruft' category" > ... >
Yes, awesome idea! This would be so helpful. When rescuing an old package, one could load it into an image with Cruft installed, and... Igor Stasenko wrote: > > (all deprecated methods should contain a comment describing, why it was > removed and what should be used instead). > This is the key! It would be almost trivial to upgrade old packages if the debugger explained how the code should be changed! There could even be a link to a relevant help topic, if one exists. Sean -- View this message in context: http://forum.world.st/WeakArray-isFinalizationSupported-tp3168849p3169485.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
