Hi Lukas, Igor 2011/8/17 Lukas Renggli <renggli@gmail.com>:
How would that help anybody to find out whether they are relying on deprecated methods? This seems like a big step backwards form a user point of view. Suddenly a method is gone and you didn't get a warning. You are you supposed to check for deprecated methods? Debug each and every one of your message sends?
+1, such an annotation is totally counterproductive.
Provide an alternative. Imagine that we're want to deprecate Array>>at:
Disable the deprecateded notifications in the system settings. Like this you acknoledge that you use outdated code; and if this gets too annoying you might want to actually fix it.
What I don't like of disabling deprecations is that is black or white. You get deprecations or you don't get at all. My view is that deprecations are context dependent, I want to disable them: -For this package -For this class and -For this execution context (or "session") -Always Why? Because I'm working in other parts of the code and now I don't want to care deprecations in an unrelated package/class, but I know later I'd like to see them. Hernán