Maybe we can have a superclass for that? Because for example selection (highlight) of the problematic code was not implemented some time ago for RBFutureDeprecationWarningRule. And it’s not trivial to do. So maybe having a superclass that implements this functionality can be useful.
Uko > On 17 Aug 2015, at 14:17, Marcus Denker <[email protected]> wrote: > > Hi, > > The idea behind RBFutureDeprecationWarningRule is very good, but I think we > should not have one > Rule for all selectors, but if a rule makes sense, just add a new class for > each. This way they are much > better… to e.g. back port. And can be transformation rules in most cases. > > https://pharo.fogbugz.com/f/cases/16241 > > Marcus >
