For one this winudf is compiled with https://openwatcom.org/ which targets older C89/C99 and legacy C++ standards alongside legacy platforms (DOS, OS/2, Win16/Win32). So unlikely direct reuse would help
Plus 16-bit segmented code. The code contains explicit "FAR" declaration for pointers, etc... when taking "outside" code to such an environment, extensive changes might be required.
I'm wondering why this is implementing udf on its own and not reusing and improving videolan's libudfread[1]
[1]https://code.videolan.org/videolan/libudfread
For one this winudf is compiled with https://openwatcom.org/ which targets older C89/C99 and legacy C++ standards alongside legacy platforms (DOS, OS/2, Win16/Win32). So unlikely direct reuse would help
Plus 16-bit segmented code. The code contains explicit "FAR" declaration for pointers, etc... when taking "outside" code to such an environment, extensive changes might be required.