2021.01.04 15:35 "Re: [Tiff] Motions related to C99 use in libtiff", by Even Rouault

I'm probably missing something.

Motion 2 (requires Motion 1 to pass):

Did you mean this the other way around instead?

No, I really meant what I wrote. Motion 1 simplifies our autoconf/cmake scripts by requiring C99 headers, while still allowing libtiff headers to be used by software not requiring C99. That is you'd build libtiff with a "modern" compiler, and use it with an ancient one.

Motion 2 means we require C99 for libtiff internal use and external use, and avoid conflicts with the [u]intXXX types defined potentially in other headers.

Time to move on... Roger made the effort to do the work. We can't get stuck for eternity with pre-C99 constraints. People that can't cope with C99 can use past releases.

Even

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