Sean P. DeNigris <> wrote:
> Or are you saying there should be a collection of rewrite rules even after
> the method is totally removed so one can bring a very old project up to the
> newest APIs?

Making sure the code works in each intermediate version of Pharo is
increasingly unattractive. It also requires indefinite support of all the
old pharo versions. A collection of separate rewrite rules looks to me like
the right thing to both explain changes and speed up migrations. 


Reply via email to