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] SW's Patchsets Overview
Date: Wed, 9 Apr 2025 10:33:59 +0200
Message-ID: <Z_Yw9zf_ZveCoIP5@phare.normalesup.org> (raw)
In-Reply-To: <df7389db-4a04-bdf2-9fcc-b5440e9e026b@passwd.hu>

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

  parent reply	other threads:[~2025-04-09  8:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-02  1:07 softworkz .
2025-04-02 19:45 ` Marton Balint
2025-04-02 20:18   ` softworkz .
2025-04-06 21:04     ` Marton Balint
2025-04-06 21:12       ` softworkz .
2025-04-08 22:24         ` Michael Niedermayer
2025-04-08 22:45           ` softworkz .
2025-04-12  1:43             ` Michael Niedermayer
2025-04-07  9:14       ` Nicolas George
2025-04-07  9:47         ` softworkz .
2025-04-08 22:53         ` Marton Balint
2025-04-08 23:31           ` softworkz .
2025-04-09  8:33           ` Nicolas George [this message]
2025-04-14 15:44 ` softworkz .
2025-04-18  5:58   ` softworkz .

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=Z_Yw9zf_ZveCoIP5@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