From: Leo Izen <leo.izen@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [RFC] AVDictionary2
Date: Tue, 8 Apr 2025 20:00:20 -0400
Message-ID: <378b18ff-4a2d-4852-8671-2330d2ba0f99@gmail.com> (raw)
In-Reply-To: <20250408101959.GP4991@pb2>
On 4/8/25 06:19, Michael Niedermayer wrote:
> Hi all
>
> As i have too many things to do already i did the most logic thing and
> started thinking about a new and unrelated idea.
>
> This is a list of problems and ideas, that everyone is welcome to add to and
> comment on.
>
> AVDictionary is just bad.
>
> * its complicated internally with
> unneeded alternative (AV_DICT_DONT_STRDUP_VAL/KEY) these are rarely used
> and probably not relevant for performance.
>
As far as I'm aware the main purpose of AV_DICT_DONT_STRDUP is to
transfer ownership to the dictionary to save a call to malloc/free. If I
construct a string e.g. with av_bprint API, and then I want to pass it
as a value to an AVDictionary *, then without access to
AV_DICT_DONT_STRDUP_VAL as an option, I will then have to free it.
Since your goal is to avoid malloc/free calls I feel like this is a
reasonable interface to continue to support.
- Leo Izen (Traneptora)
_______________________________________________
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:[~2025-04-09 0:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 10:19 Michael Niedermayer
2025-04-08 16:10 ` Romain Beauxis
2025-04-08 20:29 ` Michael Niedermayer
2025-04-08 22:18 ` Gerion Entrup
2025-04-08 22:35 ` Michael Niedermayer
2025-04-08 22:37 ` softworkz .
2025-04-08 16:56 ` softworkz .
2025-04-08 18:16 ` Michael Niedermayer
2025-04-08 18:36 ` softworkz .
2025-04-08 19:45 ` Michael Niedermayer
2025-04-08 21:30 ` softworkz .
2025-04-11 19:06 ` Michael Niedermayer
2025-04-12 1:41 ` softworkz .
2025-04-12 11:02 ` softworkz .
2025-04-09 0:00 ` Leo Izen [this message]
2025-04-09 16:56 ` Michael Niedermayer
2025-04-10 8:40 ` Nicolas George
2025-04-10 18:31 ` softworkz .
2025-04-11 20:50 ` Michael Niedermayer
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=378b18ff-4a2d-4852-8671-2330d2ba0f99@gmail.com \
--to=leo.izen@gmail.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