On Sun, Aug 10, 2014 at 12:01 AM, Matthias Urlichs <matth...@urlichs.de>
wrote:

> Jean-Yves Avenard:
> > Including rename of constants (code enums id for example).
>
> Another nail in libav's coffin, then.
>
> IMHO it's reasonable to expect core APIs to be upwards-compatible and keep
> deprecated interfaces around for another release or two.


High quality libraries must iterate on their API. Especially for a library
trying to solve such a complex problem as audio and video encoding and
decoding for every codec and format. It is unreasonable to expect no
incompatible changes. Also both ffmpeg and libav codebases have a lot of
legacy cruft. Libav is making a more concentrated effort at improving this,
and the evolving API is a side-effect of that.

Reply via email to