From: James Almer <jamrial@gmail.com> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] [PATCH] lavfi/af_aformat: remove support for comma-separated lists Date: Wed, 2 Mar 2022 13:17:41 -0300 Message-ID: <2b3b0b03-4f1f-5970-4614-838f8b7eb092@gmail.com> (raw) In-Reply-To: <20220302160438.4136064-1-george@nsup.org> On 3/2/2022 1:04 PM, Nicolas George wrote: > It has been deprecated for nine years. We need to make sure to add FF_API_ defines when we introduce this kind of deprecation in the future, as it forces people to at least look at them at every major bump. Nine years is definitely overkill. > > Signed-off-by: Nicolas George <george@nsup.org> > --- > libavfilter/af_aformat.c | 11 ++--------- > 1 file changed, 2 insertions(+), 9 deletions(-) > > > I want to share the delimiter-seeking function with vf_format and add > support for '/'. > > > diff --git a/libavfilter/af_aformat.c b/libavfilter/af_aformat.c > index ed3c75311a..d2599431dc 100644 > --- a/libavfilter/af_aformat.c > +++ b/libavfilter/af_aformat.c > @@ -62,19 +62,12 @@ AVFILTER_DEFINE_CLASS(aformat); > > #define PARSE_FORMATS(str, type, list, add_to_list, get_fmt, none, desc) \ > do { \ > - char *next, *cur = str, sep; \ > + char *next, *cur = str; \ > int ret; \ > \ > - if (str && strchr(str, ',')) { \ > - av_log(ctx, AV_LOG_WARNING, "This syntax is deprecated, use '|' to "\ > - "separate %s.\n", desc); \ > - sep = ','; \ > - } else \ > - sep = '|'; \ > - \ > while (cur) { \ > type fmt; \ > - next = strchr(cur, sep); \ > + next = strchr(cur, '|'); \ > if (next) \ > *next++ = 0; \ > \ LGTM. _______________________________________________ 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-03-02 16:17 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-02 16:04 Nicolas George 2022-03-02 16:17 ` James Almer [this message] 2022-03-02 16:27 ` Nicolas George
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=2b3b0b03-4f1f-5970-4614-838f8b7eb092@gmail.com \ --to=jamrial@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