On Wed, 15 Apr 2015 12:01:51 +0200 Nicolas George <geo...@nsup.org> wrote:
> Le sextidi 26 germinal, an CCXXIII, wm4 a écrit : > > How hard is it to understand that a program built for a specific > > purpose can not be made to use an API in all possible ways? Unless you > > add dozens of redundant code paths to ffmpeg.c (do you want this?), you > > won't be able to get full API coverage, and more importantly, you won't > > be able to test all kinds of ways the API could be used in alternative > > ways. > > Unless you give some specific examples, I will consider this as simple FUD. Both ffmpeg.c and the API are very complex, so it's obvious that ffmpeg.c can't possibly be using all possible ways the API can be used. If you really want a concrete example: av_seek_frame() is not used in any of the command line tools. Except ffserver.c, which is AFAIK not involved in any tests, and libavfilter/src_movie.c, which probably could be used in a FATE test, but passes a static set of flags and can't e.g. execute multiple seeks with multiple target destinations, and would make a very bad test. (Why do I even have to explain this.) > Regards, > _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
