On Mon, Mar 06, 2017 at 11:34:20AM +0100, wm4 wrote:
> --- a/libavcodec/avcodec.h
> +++ b/libavcodec/avcodec.h
> @@ -161,7 +168,22 @@
> * and will result in arbitrary behavior.
> *
> * Some codecs might require using the new API; using the old API will return
> - * an error when calling it.
>
Make it clear that there is no timing-dependent behavior. In particular,
there is no state in which both input and output are denied, and where
you have to wait for a while yourself to make progress (apparently some
hardware decoders like to do this).
Avoid wording that makes references to time. I
On Mon, Mar 06, 2017 at 10:38:12AM +0100, wm4 wrote:
> --- a/libavcodec/avcodec.h
> +++ b/libavcodec/avcodec.h
> @@ -161,7 +168,20 @@
> + * A codec is not allowed to return EAGAIN for both sending and receiving.
> This
> + * would be an invalid state, which could put the codec user into an endless
Make it clear that there is no timing-dependent behavior. In particular,
there is no state in which both input and output are denied, and where
you have to wait for a while yourself to make progress (apparently some
hardware decoders like to do this).
Avoid wording that makes references to time. I
