From: Nicolas George <george@nsup.org> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH 1/2] avformat/tee: refactor option processing Date: Mon, 7 Jul 2025 17:32:14 +0200 Message-ID: <aGvofg9Ufg5Bs7fo@phare.normalesup.org> (raw) In-Reply-To: <A7E9AB26-C15A-4AF3-B910-1232BB55D771@gmail.com> Marvin Scholz (HE12025-07-04): > If copying two strings fails here, it is highly unlikely any of the following > code, needing much more memory, would have any chance of succeeding. > Yes it introducers two copies which could fail but the chance for that happening > is so small that I dont think it justifies using hacks like this, which also introduce > risk of turning into more serious issues when the AVDictionary code is changed and someone > is unaware of this hack here. Please tell us: How unlikely do you think it needs to be for us to dispense with the checks? 1/1000? 1/1E6? (Hint: the answer is 0.) > We are talking about copying two option strings here, during setup, > not per frame, not every few seconds. You already gave that argument, and I already explained to you that efficiency was the tiniest of my arguments. But it is still an argument. > I disagree making this hack official. Well, I disagree making the current code more verbose for hypothetical reasons. 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".
next prev parent reply other threads:[~2025-07-07 15:32 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-06-24 22:08 Marvin Scholz 2025-06-24 22:08 ` [FFmpeg-devel] [PATCH 2/2] avformat/tee: fix multiple bsfs in tee Marvin Scholz 2025-06-25 9:56 ` Nicolas George 2025-06-26 15:42 ` Marvin Scholz 2025-06-25 11:23 ` [FFmpeg-devel] [PATCH 1/2] avformat/tee: refactor option processing Nicolas George 2025-06-25 12:04 ` Marvin Scholz 2025-07-03 9:08 ` Nicolas George 2025-07-04 14:52 ` Marvin Scholz 2025-07-07 15:32 ` Nicolas George [this message] 2025-07-07 15:52 ` Marvin Scholz 2025-07-07 16:00 ` Nicolas George 2025-07-07 16:13 ` Marvin Scholz 2025-07-07 16:55 ` Nicolas George 2025-07-07 16:04 ` Vittorio Giovara
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=aGvofg9Ufg5Bs7fo@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