Hey,
That was then opposed a "fuck you" argument and reverted ....
This seems to be quoting me out of context. Here is my full comment to Hashars revert of mine:
------
Ok, apparently I need to explain this once more - sort of getting tired of it, this is why I send a flipping email to the list with my reasoning.
Scenario: some interface gets changed for a valid reason in 1.19. You are an extension developer with an extension that needs to be compatible with 1.17 to 1.19. Now you do not have the time to put in code to handle both versions, which might be a lot of work depending on the interface change. So you want to ignore this usage of this detracted interface for now, and fix it later on. However, you want to get a warning as soon as you use some other detracted interface.
To me this very much comes off as a "fuck you" to extension developers. ------
I do not think we want such setting in core since it does not make sense. Developers can opt-in to get deprecation warnings shown, it is not to have them whitelisted later with yet another global. Either the extension need to be fixed or the core call should not be deprecated.
You are suggesting this feature is useless. The scenario I used as an example proves it is for developers, that want to have an option between "warnings" and "no warnings". I introduced the setting because I _needed_ it, and anticipate it to be useful for other people that have $wgDeprecationReleaseLimit set to false.
Cheers
-- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. --