From: Zhao Zhili <quinkblack@foxmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH 3/3] avcodec/videotoolboxenc: Fix variable type of AV_OPT_TYPE_BOOL Date: Tue, 16 Jul 2024 23:18:16 +0800 Message-ID: <tencent_6CA034CD807835033F9F577B9C4CE0BA5A09@qq.com> (raw) In-Reply-To: <6c493ada-50f3-437c-b9e2-45e1bc3bec7f@gmail.com> > On Jul 16, 2024, at 23:10, James Almer <jamrial@gmail.com> wrote: > > On 7/16/2024 11:53 AM, Rémi Denis-Courmont wrote: >> Le tiistaina 16. heinäkuuta 2024, 17.46.53 EEST Zhao Zhili a écrit : >>> From: Zhao Zhili <zhilizhao@tencent.com> >>> >>> --- >>> libavcodec/videotoolboxenc.c | 2 +- >>> 1 file changed, 1 insertion(+), 1 deletion(-) >>> >>> diff --git a/libavcodec/videotoolboxenc.c b/libavcodec/videotoolboxenc.c >>> index 747681fd05..78ef474d7a 100644 >>> --- a/libavcodec/videotoolboxenc.c >>> +++ b/libavcodec/videotoolboxenc.c >>> @@ -262,7 +262,7 @@ typedef struct VTEncContext { >>> int realtime; >>> int frames_before; >>> int frames_after; >>> - bool constant_bit_rate; >>> + int constant_bit_rate; >>> >>> int allow_sw; >>> int require_sw; >> Shouldn't it be fixed the opposite way, actually assigning to or evaluating as >> a boolean? > > No, because -1 is allowed for AV_OPT_TYPE_BOOL, which is used as "undefined" in plenty of options. > And we don't use bool type anywhere as it's not really portable, or at least didn't use to. Dunno the current state ever since we moved to c11. Yes, it’s unlikely to update opt.c to use bool as AV_OPT_TYPE_BOOL. And maybe it’s still a rule to not use bool in public header file. For other cases, I see no reason to forbidden it. > _______________________________________________ > 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". _______________________________________________ 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".
prev parent reply other threads:[~2024-07-16 15:18 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-07-16 14:46 Zhao Zhili 2024-07-16 14:53 ` Rémi Denis-Courmont 2024-07-16 15:10 ` James Almer 2024-07-16 15:15 ` Rémi Denis-Courmont 2024-07-16 15:18 ` Zhao Zhili [this message]
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=tencent_6CA034CD807835033F9F577B9C4CE0BA5A09@qq.com \ --to=quinkblack@foxmail.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