On Mon, Dec 13, 2021 at 8:48 PM Anton Khirnov <an...@khirnov.net> wrote: > > > - The request to wait for a new string handling API to land and be used > > for the relevant functions in this set. This has not seen opposition > > from anyone yet, but it's not very feasible if said new API is not yet > > in a state beyond a draft/RFC. It would delay this set indefinitely. We > > can use AVBPrint in the meantime, and name the functions in a way that > > reflects it, to leave the cleaner names for the future API. > > I said this before, but let me state again that I oppose this for > various reasons. >
I concur with an opposition on the fact alone that some future API currently not even in a final design format should not block current work for an indeterminate timeframe - especially since its hardly the only spot we ever handle strings, so its not anything new. - Hendrik _______________________________________________ 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".
