Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Rémi Denis-Courmont" <remi@remlab.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 1/2] Replace FFMIN/FFMAX by type specific macros
Date: Mon, 02 Jun 2025 21:28:09 +0300
Message-ID: <28388FF0-90BC-44F4-8EA4-BDC2BF04D3AC@remlab.net> (raw)
In-Reply-To: <GV1P250MB07379E5A2ECA7030E299E9638F62A@GV1P250MB0737.EURP250.PROD.OUTLOOK.COM>

Hi,

On that note, we should keep in mind that FFmpeg also uses (or abuses) FFMIN and FFMAX for pointer arithmetic. It feels a bit of an abuse to refer to pointers as integers.
_______________________________________________
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-06-02 18:28 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-31 13:32 Michael Niedermayer
2025-05-31 13:32 ` [FFmpeg-devel] [PATCH 2/2] avutil/opt: round min/max in integer context Michael Niedermayer
2025-05-31 17:40 ` [FFmpeg-devel] [PATCH 1/2] Replace FFMIN/FFMAX by type specific macros Marton Balint
2025-05-31 17:54   ` Zhao Zhili
2025-06-01 22:07   ` Michael Niedermayer
2025-06-02 15:06   ` Rémi Denis-Courmont
2025-06-28 14:35     ` Kacper Michajlow
2025-06-28 14:53       ` Kacper Michajlow
2025-06-28 18:57       ` Rémi Denis-Courmont
2025-06-29  2:44         ` Kacper Michajlow
2025-06-29  7:05           ` Rémi Denis-Courmont
2025-06-29 11:04             ` Kacper Michajlow
2025-06-29 14:31               ` Rémi Denis-Courmont
2025-06-02 15:47 ` Andreas Rheinhardt
2025-06-02 18:28   ` Rémi Denis-Courmont [this message]
2025-06-04  1:05   ` Michael Niedermayer
2025-06-07 23:29     ` Michael Niedermayer
2025-06-07 23:37       ` Andreas Rheinhardt
2025-06-08 20:16         ` Michael Niedermayer
2025-06-08 20:47           ` Andreas Rheinhardt
2025-06-08  6:51       ` Marton Balint
2025-06-28 11:48       ` Rémi Denis-Courmont

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=28388FF0-90BC-44F4-8EA4-BDC2BF04D3AC@remlab.net \
    --to=remi@remlab.net \
    --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