From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <ffmpeg-devel-bounces@ffmpeg.org>
Received: from ffbox0-bg.ffmpeg.org (ffbox0-bg.ffmpeg.org [79.124.17.100])
	by master.gitmailbox.com (Postfix) with ESMTPS id E53114BD2E
	for <ffmpegdev@gitmailbox.com>; Mon, 28 Jul 2025 22:05:07 +0000 (UTC)
Received: from [127.0.1.1] (localhost [127.0.0.1])
	by ffbox0-bg.ffmpeg.org (Postfix) with ESMTP id 9341E68D644;
	Tue, 29 Jul 2025 01:05:03 +0300 (EEST)
Received: from nef.ens.fr (nef2.ens.fr [129.199.96.40])
 by ffbox0-bg.ffmpeg.org (Postfix) with ESMTPS id 7310368BF5B
 for <ffmpeg-devel@ffmpeg.org>; Tue, 29 Jul 2025 01:04:57 +0300 (EEST)
X-ENS-nef-client: 129.199.129.80 ( name = phare.normalesup.org )
Received: from phare.normalesup.org (phare.normalesup.org [129.199.129.80])
 by nef.ens.fr (8.14.4/1.01.28121999) with ESMTP id 56SM4uPH027740
 for <ffmpeg-devel@ffmpeg.org>; Tue, 29 Jul 2025 00:04:57 +0200
Received: by phare.normalesup.org (Postfix, from userid 1001)
 id ADDE62EFE3; Tue, 29 Jul 2025 00:04:56 +0200 (CEST)
Date: Tue, 29 Jul 2025 00:04:56 +0200
From: Nicolas George <george@nsup.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Message-ID: <aIf0CB_VbRKKRMLG@phare.normalesup.org>
References: <20250702144355.GE29660@pb2>
 <aGVHypOhb2JfUbhc@phare.normalesup.org>
 <20250702171641.GF29660@pb2>
 <aGZFx2W_fSnJ8Ik5@phare.normalesup.org>
 <20250703155205.GK29660@pb2>
 <aGfXL49EU2uNlz18@phare.normalesup.org>
 <20250706143354.GA29660@pb2>
 <aIfzThQeTTW_DmOo@phare.normalesup.org>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <aIfzThQeTTW_DmOo@phare.normalesup.org>
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3
 (nef.ens.fr [129.199.96.32]); Tue, 29 Jul 2025 00:04:57 +0200 (CEST)
Subject: Re: [FFmpeg-devel] [RFC] Advanced Error Codes
X-BeenThere: ffmpeg-devel@ffmpeg.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: FFmpeg development discussions and patches <ffmpeg-devel.ffmpeg.org>
List-Unsubscribe: <https://ffmpeg.org/mailman/options/ffmpeg-devel>,
 <mailto:ffmpeg-devel-request@ffmpeg.org?subject=unsubscribe>
List-Archive: <https://ffmpeg.org/pipermail/ffmpeg-devel>
List-Post: <mailto:ffmpeg-devel@ffmpeg.org>
List-Help: <mailto:ffmpeg-devel-request@ffmpeg.org?subject=help>
List-Subscribe: <https://ffmpeg.org/mailman/listinfo/ffmpeg-devel>,
 <mailto:ffmpeg-devel-request@ffmpeg.org?subject=subscribe>
Reply-To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ffmpeg-devel-bounces@ffmpeg.org
Sender: "ffmpeg-devel" <ffmpeg-devel-bounces@ffmpeg.org>
Archived-At: <https://master.gitmailbox.com/ffmpegdev/aIf0CB_VbRKKRMLG@phare.normalesup.org/>
List-Archive: <https://master.gitmailbox.com/ffmpegdev/>
List-Post: <mailto:ffmpegdev@gitmailbox.com>


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".