On Wed, 11 May 2016 19:57:19 +0200 Michael Niedermayer <mich...@niedermayer.cc> wrote:
> On Thu, May 05, 2016 at 01:45:55AM +0100, Derek Buitenhuis wrote: > > I am not at all opposed to the idea. I just don't think the current way > > of using internal headers, structs, and APIS (and a wrapper main()) should > > at all be encouraged. If someone were to send patches to *properly* add > > such functionality, with a stable plugin API/ABI, and such, I would not > > oppose. I do not think this is trivial to do, however. > > whatever API we would design/choose to be used for plugins should > be "well designed" (that is it should strive for simplicity, > completeness, correctness, long term stability, efficiency, ...) > > and i belive if we create such an API, all internal codecs, (de)muxers, > filters, protocols and so on should also be moved to use it. I don't think anyone is against that. (Except maybe that for some things, you simply can't make reasonable public APIs and should remain private. Not _everything_ has to be possible to be done externally.) _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
