Feb. 23, 2018
7:20 p.m.
Sean P. DeNigris <sean@clipperadams.com> 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. Stephan