On date Friday 2015-11-27 15:27:02 +0100, Clément Bœsch encoded: > On Fri, Nov 27, 2015 at 01:10:29PM +0100, Nicolas George wrote: > > Le septidi 7 frimaire, an CCXXIV, Clement Boesch a écrit : > > > But then it's still exposed by the API, and someone looking at handling > > > every error code might be wondering how to handle it. > > > > « Handling every error code » seems to me like an impossible and idiotic > > objective. What do you suggest, exactly? > > > > I don't know; I just don't really like the idea of such error code > "leaking" publicly in order to solve an issue internally. I don't have any > solution, I would just loop in the demuxer or use a FFERROR (but that > might be clumsy)
I'd like to fix the libavformat API/ffprobe, so I'm in favor of this patchset. Regarding the specific patch, we could keep the REDO error code (and mark in the comment that's intended for internal use), or add and use an internal error code. I don't think leaking a define which is not supposed to be used by the user is a serious problem. -- FFmpeg = Fast and Formidable Multimedia Pitiless Erudite Gymnast _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel