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

2021.01.07 14:08 "Re: [Tiff] Motions related to C99 use in libtiff", by Bob Friesenhahn

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

To be clear, there are no "pre-C99" headers. The definitions that libtiff has been providing are based on pure C types.

Regardless, it is easy to allow users of libtiff to compile dependent software using the legacy type names, which were already in heavy use by dependent software in the early '90s. I am not sure if they were there since the very beginning of libtiff in 1988 or added somewhat later.

Bob

Bob Friesenhahn
bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/
Public Key, http://www.simplesystems.org/users/bfriesen/public-key.txt