2021.01.04 14:23 "[Tiff] Motions related to C99 use in libtiff", by Even Rouault

2021.01.07 06:16 "Re: [Tiff] Motions related to C99 use in libtiff", by William Bader

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

Not sure what you mean exactly here

What I meant, and it is probably not a good idea, would be keeping the C ABI the same for a while (which might not be possible if the pre-C99 long doesn't match the C99 intXXX replacement on some platforms) so that libtiff could be built with the C99 headers but other packages that use libtiff could be compiled with the pre-C99 headers (either by an ifdef or by swapping out the header files manually or by giving the C99 headers a different name) so that applications could be built during the transition when not all of the components using libtiff have been converted. As long as the old and new headers define the same ABI, packages that compile with either one could link to the same libtiff object library.

Could the C++ issues be solved by writing additional C++ overloads using the C99 types? The versions using pre-C99 types could be marked [[deprecated]] during the transition.