Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Nicolas George <george@nsup.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [RFC] Advanced Error Codes
Date: Tue, 29 Jul 2025 00:04:56 +0200
Message-ID: <aIf0CB_VbRKKRMLG@phare.normalesup.org> (raw)
In-Reply-To: <aIfzThQeTTW_DmOo@phare.normalesup.org>


Sorry, forgot a bit:

> The first group:
> 
> - do not get a context;
> 
> - perform a rather simple task;

- have a perimeter small enough that an error code is enough for the
  caller to know what went wrong;

> 
> - could be called in tight loops, even when they fail repeatedly, and
>   therefore should not waste time fiddling with strings;
> 
> - do not have enough information to design a useful error message
>   anyway.
> 
> The second group, is all the opposite. I do not think there is much in
> between.

Regards,

-- 
  Nicolas George
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

  reply	other threads:[~2025-07-28 22:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-02 14:43 Michael Niedermayer
2025-07-02 14:52 ` Nicolas George
2025-07-02 17:16   ` Michael Niedermayer
2025-07-03  8:56     ` Nicolas George
2025-07-03 15:52       ` Michael Niedermayer
2025-07-04 13:29         ` Nicolas George
2025-07-06 14:33           ` Michael Niedermayer
2025-07-28 22:01             ` Nicolas George
2025-07-28 22:04               ` Nicolas George [this message]
2025-07-02 17:21 ` Michael Niedermayer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aIf0CB_VbRKKRMLG@phare.normalesup.org \
    --to=george@nsup.org \
    --cc=ffmpeg-devel@ffmpeg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git