Roger Leigh via Tiff <[email protected]> writes: > Over the next few weeks, I’m going to be looking at opening a series > of merge requests to address various categories of static analysis > warning in the codebase, plus enabling specific compiler warnings by > default to check for them by default in the CI builds. The aim being > to improve the quality and robustness of the codebase. Most of these > are fairly trivial to implement, but questions such as the above > really depend upon what the original intentions were and any > compatibility constraints we have to factor in.
I think it would be good to be clear on where we are and where we're going in terms of system requirements to build tiff. If that's C99 and some degree of POSIX compliance, then perhaps the main path can be just to typedef tmsize_t to size_t, and to band-aid it for deficient platforms. A second concern is that a warning rototill risks breakage on platforms not tested, and usually CI is a very limited set. Besides GNU/Linux, macOS, and Windows, I'd want to see a couple of BSDs and something from the illumos family. Also, CPU variety: not just i386/x86_64/aarch64, but also earmv6 or v7, sparc or sparc64, ppc, or at least something big endian. Perhaps that's an alpha release after things are ok in CI. _______________________________________________ Tiff mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/tiff
