2021.01.06 10:40 "Re: [Tiff] Motions related to C99 use in libtiff", by Even Rouault

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?

Yes, that's a good point. I don't think it will actually change. I had some doubts about the C++ stuff. In tiffio.h, there are some C++ defaulted parameters, but the functions are exported as C, so there should be no ABI change.

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

Not sure what you mean exactly here

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

My vision is that we do the full move, that is Motion 2. Motion 1 would be just a partial move. The C99 printf thing is part of Motion 1

Spatialys - Geospatial professional services
http://www.spatialys.com