Quoting wm4 (2016-01-13 16:46:31) > On Wed, 13 Jan 2016 11:06:06 +0100 > Anton Khirnov <an...@khirnov.net> wrote: > > > I don't think it's particularly painful, as far as API changes go -- you > > only need like 2 different lines for each version (the struct name + > > av_mallocz() vs the new constructor). > > > > And besides > > - it needs to be done eventually anyway, so better sooner than later > > - it's unlikely that this specific part will need any further changes in > > the future -- we'll probably always need some kind of a hw-specific > > context and there must be a constructor for it. > > > > See the vdpau hwaccel how it could change. (Of course vdpau still has > the old mechanisms, for compatibility or those who want to do it > manually.)
I tend to see the VDPAU function as a kind of a convenience shortcut for the callers, the underlying hw context is still there. -- Anton Khirnov _______________________________________________ libav-devel mailing list libav-devel@libav.org https://lists.libav.org/mailman/listinfo/libav-devel
