On 11/01/16 21:46, Vittorio Giovara wrote: > On Mon, Jan 4, 2016 at 8:34 AM, Vittorio Giovara > <[email protected]> wrote: >> AVCodecContext holds a lot of fields that are used seldom within >> libavcodec, in most cases only to set options that apply to a single >> family of codecs, or sometimes to completely unrelated codecs. >> This was done before in the long past there was no codec private option, >> and in fact nowadays global context options are rarely added (and only >> when it really applies to something global), preferring to add codec >> private options instead. >> >> This set (1 of 3) tries to go over each context field and to identify >> which not-really-global options should be moved to private codec options. >> The rationale is that after my changes options would have a much more precise >> scope, as right now it is not possible to understand which option affects >> which codec without looking at the source code. The (long term) improvement >> would also be to have a more compact context, with less fields to document >> >> The option selection is a trade off between how widespread the option is >> within libavcodec and how much it makes sense for an option to be global. >> >> Vittorio > > ping on the set with the replaced - to _ >
I'm not against it. _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
