kilon.alios wrote


For example, let's say your project has a class that implements a
generically-named method, like #asMorph. If you try to rename that method
via Refactoring, Pharo will try to rename all #asMorph methods, and update
all senders, in the entire system, not just yours. But if you scope the
browser first to your package or class, you can restrict the environment to
which the refactoring is applied