Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] lavu/attributes: add ff_ prefix to attribute_deprecated
Date: Tue, 12 Mar 2024 10:21:52 +0100
Message-ID: <AS8P250MB07448A8412003E6AAD397DC88F2B2@AS8P250MB0744.EURP250.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <171023422319.7287.11903630014703761101@lain.khirnov.net>

Anton Khirnov:
> Quoting Andreas Rheinhardt (2024-03-12 09:56:46)
>> Anton Khirnov:
>>> Otherwise it might conflict with caller-defined identifiers.
>>>
>>> ff because it is not supposed to be used by external callers.
>>> ---
>>
>> This is public, so it should be av_attribute_deprecated.
> 
> As the commit message says, this is not supposed to be used by external
> callers. Or do you see any reason why it should be public?
> 

It is public given that it is declared in a public header. That is what
matters.
Furthermore, we have used the FF_ and AV_ prefixes for public macros and
the av_ prefix for public symbols, but IIRC we do not use the ff_ prefix
for public symbols at all, therefore I'd like us not to reserve another
namespace.

>> For the same reason it is actually an API break to no longer provide the
>> un-prefixed version.
> 
> I am still providing the unprefixed version under a deprecation guard.
> 

I overlooked that.

>> Is this just a general precaution or did you run into an actual conflict?
> 
> The former.
> 

_______________________________________________
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:[~2024-03-12  9:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-12  8:43 Anton Khirnov
2024-03-12  8:56 ` Andreas Rheinhardt
2024-03-12  9:03   ` Anton Khirnov
2024-03-12  9:21     ` Andreas Rheinhardt [this message]
2024-03-12 10:12       ` Anton Khirnov
2024-03-12 10:32         ` Andreas Rheinhardt

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=AS8P250MB07448A8412003E6AAD397DC88F2B2@AS8P250MB0744.EURP250.PROD.OUTLOOK.COM \
    --to=andreas.rheinhardt@outlook.com \
    --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