On Thu, Nov 14, 2013 at 11:47 AM, Luca Barbato <[email protected]> wrote: > On 14/11/13 11:36, Anton Khirnov wrote: >> >> On Thu, 14 Nov 2013 11:29:17 +0100, Luca Barbato <[email protected]> wrote: >>> On 14/11/13 11:10, Anton Khirnov wrote: >>>> >>>> On Thu, 14 Nov 2013 10:43:42 +0100, Luca Barbato <[email protected]> >>>> wrote: >>>>> On 14/11/13 10:31, Anton Khirnov wrote: >>>>> >>>>> I wouldn't add public functions right now, beside that look neat. >>>>> >>>> >>>> ???? >>>> >>>> What public functions? >>> >>> av_vaapi_alloc_context() >>> >>> I'm not exactly happy to have an unbound number of such functions. >>> (as I'm unhappy to have that kind of struct around). >>> >> >> Err...then why didn't you say something when I was adding the exact same >> thing >> for vdpau? > > I did but had a random courmish complain loudly because it would change > completely how it works in vlc and stuff and probably the whole > discussion got swamped.
Didn't the discussion result in that the people actually using HWAccels greatly prefer a struct over terrible AVOptions or any other contrived abomination? structs are fine. Also, use an API before you redesign it. :) - Hendrik _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
