Diederick C. Niehorster (12021-06-12):
> One thing to add is this: Errors are often propagated back through
> various layers of function calls. Some next level may:
> 1. decide something is not an error/should be ignored. It should be
> able to unset the current error (if it was set, so something l
On Thu, Dec 31, 2020 at 9:52 PM wrote:
>
> On 31/12/2020 13:36, Nicolas George wrote:
> > This mail is about a project I have to make FFmpeg's API and
> > infrastructure more convenient. For a common introduction, see this
> thread:
> > https://ffmpeg.org/pipermail/ffmpeg-devel/2020-December/27416
On 31/12/2020 13:36, Nicolas George wrote:
> This mail is about a project I have to make FFmpeg's API and
> infrastructure more convenient. For a common introduction, see this thread:
> https://ffmpeg.org/pipermail/ffmpeg-devel/2020-December/274167.html
>
> The way we currently report errors is fi
This mail is about a project I have to make FFmpeg's API and
infrastructure more convenient. For a common introduction, see this thread:
https://ffmpeg.org/pipermail/ffmpeg-devel/2020-December/274167.html
The way we currently report errors is fine for command-line tools running in
a terminal, but
