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

Manuscript Notification

	Denis Kudryashov edited Case 20063: #isDeprecated should consider protocol names: Enhancement in Kernel: 1. Pharo Image • You are subscribed to this case

monty2, two questions:
- why you want move method to special protocol "deprecated"? what you try achieve with it?
- why you prefer categorisation instead of explicit deprecation message in the source code?

I have feeling that the reason is because we do not have right tools for deprecation and you are trying address it with available features like method protocols.

For example in Calypso browser there is virtual protocol "deprecated" with all deprecated methods. It appears automatically and I think it could address first question.
For the second, I think we should extend method rename refactoring with deprecation option. And probably we should add explicit "deprecate method" command. So you will not need remember and search what deprecation messages to use.

	Priority: 4 – Would be nice		Status: Work Needed
	Assigned to: Everyone		Milestone: Pharo7.0

Go to Case

No longer need updates? Unsubscribe from this case.

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

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