This is a use case that is addressed at the level of the method, not of a class. I see the issue similarly to Stef: as I can utilize a class, it has little meaning to call it abstract. A missing method has a different meaning from the typical meaning associated with a class being abstract. Cheers, Doru
On Apr 1, 2019, at 10:54 AM, Henrik Sperre Johansen <henrik.s.johansen@veloxit.no> wrote:
Tim Mackinnon wrote
Calypso warns you about missing methods if it doesnât understand a class is abstract, so itâs useful to avoid those warnings otherwise you become desensitised to them.
Tim
Or, if the class has subclasses, one could get a suggestion/action to implement the missing method as missingMethod ^self subclassResponsibility
Which also has the benefit of working nicely with the "expected (or was that "missing"?) protocol" functionality. Unless you meant something else?
Cheers, Henry
-- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html
-- www.feenk.com "Problem solving should be focused on describing the problem in a way that makes the solution obvious."