On Sun, 2011-12-18 at 19:05 +0000, Måns Rullgård wrote: > Uoti Urpala <[email protected]> writes: > > > Yes. It should not produce a forced warning now. Having a separate > > method to request warnings for everything that is scheduled to be > > changed in the (possibly distant) future would be more appropriate. > > That method already exists. Simply turn deprecation warnings on/off as > desired in your build.
I am aware of the ability to turn off deprecation warnings, and already mentioned it in my first post in this thread. I don't consider that to be a good solution to the issue however. Libav should not produce inappropriate warnings by default and require special action to turn them off. And there are appropriate uses of deprecation warnings; turning the warnings off globally would hide those too. If the replacement interface was already available in versions from a year ago and/or in the last release, or the old interface was scheduled to be deleted next week, then deprecation warnings from Libav would be perfectly appropriate too. And those should not be hidden just because you don't want to see warnings about not yet using some new API added one day ago. _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
