Manuscript (Case [Issue]22676) Refactoring - Cannot extract method with a name matching the one in a superclass being a subclassResponsibility

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

Manuscript (Case [Issue]22676) Refactoring - Cannot extract method with a name matching the one in a superclass being a subclassResponsibility

Pharo Issue Tracker
Manuscript Notification
avatar
Bug in Project:  Refactoring: 1. Pharo Image  •  You are subscribed to this case
If you try to perform an extract method and use as the method name one that collides with the one in a superclass it will open a debugger, even if the superclass implementation is a subclassResponsibility.

Find attached an screenshot showing the problem.

Image
-----
/home/gcotelli/Pharo/7.0-64bits/Pharo.image
Pharo7.0.0rc1
Build information: Pharo-7.0.0+rc1.build.1402.sha.e783ea64f0f928333ec5e80d64656b8dae18c821 (64 Bit)
Unnamed
Priority Priority: 2 – Really Important Status Status: Work Needed
Assigned To Assigned to: Everyone Milestone Milestone: Pharo7.0

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