From: Anton Khirnov <anton@khirnov.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v4] avutil/csp: create avpriv API for colorspace structs
Date: Fri, 20 May 2022 17:50:29 +0200
Message-ID: <165306182914.17509.14786031095194231291@lain.red.khirnov.net> (raw)
In-Reply-To: <1d00bdb9-cf77-aa08-1799-db77d2548d0c@gmail.com>
Quoting James Almer (2022-05-20 13:53:35)
> >
> > 3. avpriv_ vs av_
> > avpriv is evil, it combines the pain of ABI/API compatibility while the
> > public cant use it
>
> Not making it public allows us to not commit to a fixed design *now*.
> Unless there's a clear need for this to be part of the public API, i
> don't think it's a good idea to do so. This change is being made because
> this API is afaict needed in lavc, and not by some project using lavu.
The commit message claims it will be used in lavc and lavf. Seems to me
like a strong sign that it really should be public.
As far as I'm concerned, avpriv should not exist at all.
--
Anton Khirnov
_______________________________________________
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".
next prev parent reply other threads:[~2022-05-20 15:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 15:18 Leo Izen
2022-05-18 18:23 ` Michael Niedermayer
2022-05-18 18:27 ` Michael Niedermayer
2022-05-20 10:28 ` Michael Niedermayer
2022-05-20 11:26 ` Ronald S. Bultje
2022-05-20 13:11 ` Michael Niedermayer
2022-05-20 13:39 ` Ronald S. Bultje
2022-05-20 11:53 ` James Almer
2022-05-20 13:23 ` Michael Niedermayer
2022-05-20 15:50 ` Anton Khirnov [this message]
2022-05-20 16:02 ` Leo Izen
2022-05-20 16:33 ` Niklas Haas
2022-05-20 12:08 ` Leo Izen
2022-05-20 17:20 ` Niklas Haas
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=165306182914.17509.14786031095194231291@lain.red.khirnov.net \
--to=anton@khirnov.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