Manuscript (Case [Issue]20063) Kernel - #isDeprecated should consider protocol names

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

Manuscript (Case [Issue]20063) Kernel - #isDeprecated should consider protocol names

Pharo Issue Tracker
Manuscript Notification
avatar
Enhancement in Project:  Kernel: 1. Pharo Image  •  You are subscribed to this case
Hi
I do not really like to rely on protocols. It will make the system more brittle.
I would invest more in a refactoring to help the guy to transform its methods into deprecated methods. I agree with Denis. Protocols are fragile concepts.
If we start to rely on them we will have to pay attention for any other operations.
I would not go that road but focus on refactoring support.

Stef
Priority Priority: 4 – Would be nice 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