Le tridi 3 brumaire, an CCXXVI, Jan Ekstrom a écrit : > The base idea was grasped rather quickly though, which seems to be > that all API clients utilizing their own IO seem to now require an > update to their code to return AVERROR_EOF if EOF was hit instead of > being able to return the number of read bytes, as usual.
I had not considered the case of custom callbacks, indeed. I do not consider this a public API change because 0 was never documented as a valid return value for a read_packet callback, while AVERROR_EOF has been around for a long time. But my goal is not to break existing code on purpose. Fortunately, there is a rather simple workaround, I will try to implement it tomorrow. Still, lacking a simple test case, I will not be able to test it. Regards, -- Nicolas George
signature.asc
Description: Digital signature
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
