On Fri, Mar 04, 2016 at 01:34:55PM +0000, Derek Buitenhuis wrote: > On 3/3/2016 7:50 PM, Michael Niedermayer wrote: > > The io_open/close callbacks afterwards seem direct access IIUC > > so its not possible to remove or add any fields prior > > > > though maybe they have been added so recently that its ok to move > > them above all "no direct access" fields > > or maybe iam missing something > > Crap. I must have screwed up when merging those callbacks. I can move > the be blacklist entry under them, or I can break ABI and move both, > since I don't think there is release.
i thought it was post 3.0 but it seems, it was in 3.0 git grep io_close release/3.0:libavformat/avformat.h release/3.0:libavformat/avformat.h:#define AVFMT_FLAG_CUSTOM_IO 0x0080 ///< The caller has supplied a custom AVIOContext, don't avio_close() it. release/3.0:libavformat/avformat.h: * @deprecated Use io_open and io_close. release/3.0:libavformat/avformat.h: void (*io_close)(struct AVFormatContext *s, AVIOContext *pb); > > Which do people prefer? They're both kinda meh. > > - Derek > _______________________________________________ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > http://ffmpeg.org/mailman/listinfo/ffmpeg-devel -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Modern terrorism, a quick summary: Need oil, start war with country that has oil, kill hundread thousands in war. Let country fall into chaos, be surprised about raise of fundamantalists. Drop more bombs, kill more people, be surprised about them taking revenge and drop even more bombs and strip your own citizens of their rights and freedoms. to be continued
signature.asc
Description: Digital signature
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
