On Mon, Jul 20, 2015 at 8:38 PM, wm4 <nfx...@googlemail.com> wrote:
> On Mon, 20 Jul 2015 18:24:16 +0100
> Vittorio Giovara <vittorio.giov...@gmail.com> wrote:
>
>> Express bitfields more simply.
>>
>> Signed-off-by: Vittorio Giovara <vittorio.giov...@gmail.com>
>> ---
>
> +1
>
> Will there be similar patches for the FF_ public symbols?

The remaining FF_ symbols are definitely non trivial and fall into
three categories:
1. symbol for defaults or set values, eg.
1761ab838c75223a6b97d8c0720d09275374c53d, to be made internal only
2. symbol for values, however for properties which should not be
public (eg. slice_flag) but for which a proper API is difficult to
attain
3. symbol for default values, whose usage is intrinsic to the codec
but need to be exported, eg. FF_PROFILE

I'm done with 0 (simple rename of symbols), I'm tackling 1, 2 is
somewhat difficult but doable, while 3 is not planned right now. Do
you have any specific symbol or API request on any of those levels?
-- 
Vittorio
_______________________________________________
libav-devel mailing list
libav-devel@libav.org
https://lists.libav.org/mailman/listinfo/libav-devel

Reply via email to