April 28, 2015
6:10 a.m.
On 28 Apr 2015, at 04:25, Sean P. DeNigris <sean@clipperadams.com> wrote:
In String>>#subStrings: there is: "This method is planned for future deprecation in favour of #substrings: (Issue 7592), but we do it gently, first via Critic Browser > Design Flaws > Future Deprecation Warning"
Is that now preferred over #deprecated:on:in:?
No⦠the idea was to experiment how to change methods that are used a lot. In this case we did it very very late in Pharo4 and a real deprecation looked too intrusive. It could be an idea to use staged deprecation for some cases.. i Marcus