Oct. 7, 2008
7:40 p.m.
The arguments to not remove it are inertia as usual. I see 163 senders in the 10074 image and probably many more in Squeak packages. Le ver est dans le fruit.
I can understand that to manage cancel button the UI returns nil Now I do not see the gain with always returning '' even on cancel.
If you want to remove such message, it would be good to have a base of refactoring rules to be applied on Squeak packages so that they become Pharo friendly. Sort of one-click compatibility automaton.
Yes I will have probably to support that + a nice deprecated warning. On VW adrian kuhn did a deprecation that walk the stack and invoke the refactoring browser on the fly. This is something that we should do too. Stef