From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <ffmpeg-devel-bounces@ffmpeg.org>
Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100])
	by master.gitmailbox.com (Postfix) with ESMTPS id 2141C4C76C
	for <ffmpegdev@gitmailbox.com>; Wed,  9 Apr 2025 08:34:10 +0000 (UTC)
Received: from [127.0.1.1] (localhost [127.0.0.1])
	by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id B344C687C2E;
	Wed,  9 Apr 2025 11:34:06 +0300 (EEST)
Received: from nef.ens.fr (nef2.ens.fr [129.199.96.40])
 by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 1F116687A55
 for <ffmpeg-devel@ffmpeg.org>; Wed,  9 Apr 2025 11:34:00 +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 5398XxvL015461
 for <ffmpeg-devel@ffmpeg.org>; Wed, 9 Apr 2025 10:33:59 +0200
Received: by phare.normalesup.org (Postfix, from userid 1001)
 id 5EEFF2EFD9; Wed,  9 Apr 2025 10:33:59 +0200 (CEST)
Date: Wed, 9 Apr 2025 10:33:59 +0200
From: Nicolas George <george@nsup.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Message-ID: <Z_Yw9zf_ZveCoIP5@phare.normalesup.org>
References: <DM8P223MB0365066DF0B56E60A0E2C4E9BAAF2@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM>
 <c45a5869-e39e-bc20-0559-079f0b93ca37@passwd.hu>
 <DM8P223MB03657732DC376984DF4ED8DBBAAF2@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM>
 <558752ee-492d-0f3a-6201-329741334f30@passwd.hu>
 <Z_OXaaYDLDGDLkvo@phare.normalesup.org>
 <df7389db-4a04-bdf2-9fcc-b5440e9e026b@passwd.hu>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <df7389db-4a04-bdf2-9fcc-b5440e9e026b@passwd.hu>
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3
 (nef.ens.fr [129.199.96.32]); Wed, 09 Apr 2025 10:33:59 +0200 (CEST)
Subject: Re: [FFmpeg-devel] SW's Patchsets Overview
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/Z_Yw9zf_ZveCoIP5@phare.normalesup.org/>
List-Archive: <https://master.gitmailbox.com/ffmpegdev/>
List-Post: <mailto:ffmpegdev@gitmailbox.com>

Marton Balint (HE12025-04-09):
> Not showing pointer addresses also has benefits, such as easier diffability
> of output, or better human readability. It depends on actual use case which
> is "useful", so a logging flag completely makes sense to me to show or hide
> it, depending on what the user wants.

Sure, it has second order benefits: it makes a few things a little
easier. For example if you want to remove the address to diff the output
of multiple runs, you can just pipe through sed; you are already piping
to get the diff anyway.

But the problems it causes, not being able to identify the source of a
warning, are first order.

> As for the question of the default behaviour, I don't have a strong opinion,
> both can make sense, maybe I would keep the existing behaviour for the
> library, but change the default for the cli tools to no-pointer output.

Even in the CLI tool, this change is harmful as soon as there are
multiple instances of the same component, like two scale filters.

Detecting that situation to enable the flag would not be worth the
effort and would clash with the principle of least surprise.

Stop with the sunk costs, just drop this misfeature.

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