> I have kept the individual functions separate on purpose, to make it easy to > compare with the .NET impl. (compilers should inlinie those anyway)
Calling add_extended_prefix without pre-validation results in error, since it does check for \\?\, \\.\, or \??\; only it's wrapper get_extended_win32_path does. And it's not private, it's in the header. path_normalize is a do nothing function. Keeping the comments about where the code originated from may be useful. Copying the structure of .NET results in problems. These patches are very difficult to review. E.g. stat is not covered: https://ffmpeg.org/pipermail/ffmpeg-devel/2022-May/296448.html. Parts of FFmpeg still use fopen instead of av_fopen_utf8. Some of these uses are in examples or tests or inside #ifdef DEBUG blocks. Others aren't: dvdsubdec.c:620 uses fopen and it is not covered by your previous patchset https://ffmpeg.org/pipermail/ffmpeg-devel/2022-May/296189.html. So please check that all uses of CRT functions that do I/O: https://docs.microsoft.com/en-us/cpp/c-runtime-library/stream-i-o?view=msvc-170 https://docs.microsoft.com/en-us/cpp/c-runtime-library/low-level-i-o?view=msvc-170 https://docs.microsoft.com/en-us/cpp/c-runtime-library/directory-control?view=msvc-170 https://docs.microsoft.com/en-us/cpp/c-runtime-library/file-handling?view=msvc-170 are actually covered (plus WinAPI functions as well). _______________________________________________ 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".
