You can probably remove it directly from Pharo instead https://pharo.fogbugz.com/f/cases/15858/review-rule-RBAbstractClassRule Peter On Thu, Sep 17, 2015 at 9:09 AM, Yuriy Tymchuk <yuriy.tymchuk@me.com> wrote:
Hi.
First of all: thank you for the feedback Damien! It makes sense, the rule also has higher amount of negative feedback. I will remove it from QA, let it stay in the image, it actually can be useful.
Uko
On 17 Sep 2015, at 06:49, Damien Cassou <damien.cassou@inria.fr> wrote:
This lint rule pops up all the times and my code is always ok. I typically have to reference an abstract class when:
- the abstract class takes care of choosing the concrete class to instantiate
- the abstract class takes care of some shared variable for its subclasses (e.g., a cache or an shared external object)
I propose to remove this rule which has never been useful for me.
-- Damien Cassou http://damiencassou.seasidehosting.st
"Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill