On Sat, May 23, 2020 at 04:36:24PM +0200, Nicolas George wrote: > Limin Wang (12020-05-23): > > OK, if nobody object it, I'll remove it after the patchset are OK. > > That should be in the same patch. > > > I have no idea how to use parse_key_value_pair() and how to support it in > > command > > line with option? so I use it as format directly. > > The answer to something we do not know should be to learn, not to do > without and result in an inferior implementation. OK, I'm glad to learn how to use it, I haven't find how to use it in the existing code.
> > I am very much opposed to turning this option into just the name of the > format, especially now that it starts getting extended. > > In this case, transforming the string into an AVDictionary, passing it > around and warning if there are remaining options should be the simplest > choice. So I should to use av_find_info_tag to parse the options string? any sample code in the existing code for refering? > > 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-requ...@ffmpeg.org with subject "unsubscribe". -- Thanks, Limin Wang _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
