On 6/29/2016 7:39 PM, Timo Rothenpieler wrote: > On 6/29/2016 10:31 PM, Michael Niedermayer wrote: >> This is a similar ABI fix to 1eb43af1a0e542ad83dcbf327197785d815fc42d > > +1 for this. > > While it's true that all fields after it are not public API/ABI, a lot > of software seems to misuse it, so to avoid too much trouble for now, > this should be fixed.
How do you expect library users to start using the API correctly if every time they do something wrong we are the ones that rush to break our code just to adapt to their mistakes? > > We should then talk about how to avoid such problems in the future, i.e. > how to make private fields truely private. Yes, this is already decided. No direct access fields product of the old libav compat attempts will be turned public as required, and everything else will be shoved inside an opaque *internal struct, similar to existing ones. _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
