Hey,
Thanks for expalining.
I did notice the code now resides in a seperate library. Congratulations on that work. I can see how this provides benefit.
It is also clear that naming it wfSuppressWarnings there does not make a lot of sense. What is not clear to me is why existing MediaWiki extensions that are completely dependent on MediaWiki should now preferrably call the library functions directly. Why do they have to care that this refactoring has been made? If you are writing some new code and are trying to decouple it from MediaWiki, and it needs this functionality, then by all means, use the namespaced one. For existing extensions where such decoupling is not going to happen, I see only cost, not benefit.
I'm not suggesting that the library should not be there, or that the namespacing in it does not make sense. My suggestion is to not deprecate wfSuppressWarnings.
Cheers
-- Jeroen De Dauw - http://www.bn2vs.com Software craftsmanship advocate Developer at Wikimedia Germany ~=[,,_,,]:3