2021.01.06 04:45 "Re: [Tiff] Motions related to C99 use in libtiff", by William Bader

Motion 2 (requires Motion 1 to pass):

Allow use of C99 data types in libtiff API instead of custom [u]intXXX typedefs, thus requiring code using libtiff to have C99 build capabilities (will cause a API and ABI breakage)

As long as the C99 data types correspond to the custom typedefs, won't the ABI remain the same?

Would temporarily freezing the last pre-C99 ABI help with the transition?

If Motion 2 includes C99 printf formats, is it worth separating that out?