On 1/12/2018 10:46 PM, Carl Eugen Hoyos wrote: > Hi! > > Seeing 6e80079a it appears that the unstable period is not over yet. > Vittorio posted a patch that introduces a temporary type to avoid > breaking API, but that may not be relevant if the api currently > unstable.
The ABI is what is in the unstable post bump period (Although that should end soon), but the API never goes through such thing. It's why the two years deprecation periods exist every time a public symbol needs to be removed or some behavior changed, and why Vittorio's patch implemented this by starting one. > > Attached patch (inspired by Vittorio's RFC) passes fate with > --disable-asm and does not introduce new warnings with gcc 6.3. > Do we generally need this change? > Do we generally want it? > > If yes, I will likely need help for the asm changes. > > I would like to avoid a temporary type and I would like to avoid a > future version bump only because this change suddenly becomes > necessary. > > Please comment, Carl Eugen > > > > _______________________________________________ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > http://ffmpeg.org/mailman/listinfo/ffmpeg-devel > _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
