Manuscript (Case [Issue]21570) Kernel - The system should not decide if a class is abstract or not

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Manuscript (Case [Issue]21570) Kernel - The system should not decide if a class is abstract or not

Pharo Issue Tracker
Manuscript Notification
avatar
Guillermo Polito opened Case 21570: The system should not decide if a class is abstract or not and assigned it to Everyone:
Bug in Project:  Kernel: 1. Pharo Image  •  You are subscribed to this case
The current implementation of #isAbstract

isAbstract

self withAllSuperclassesDo: [ :eachClass |
eachClass methodsDo: [ :eachMethod |
(eachMethod isAbstract and: [ (self lookupSelector: eachMethod selector) isAbstract ])
ifTrue: [ ^true ]]].

^false

leads to a lot of false positives.

A class is abstract by design, not by implementation. This should probably be replaced by something like #isFullyImplemented
Priority Priority: 3 – Must Fix Status Status: Work Needed
Assigned To Assigned to: Everyone Milestone Milestone: Later

Go to Case
No longer need updates? Unsubscribe from this case.

Don't want Manuscript notifications anymore? Update your preferences.

Manuscript

_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
https://lists.gforge.inria.fr/mailman/listinfo/pharo-bugtracker