- 2021.01.04 14:55 "Re: [Tiff] Motions related to C99 use in libtiff", by Edward Lam
- 2021.01.04 18:43 "Re: [Tiff] Motions related to C99 use in libtiff", by Greg Troxel
- 2021.01.05 17:01 "Re: [Tiff] Motions related to C99 use in libtiff", by Jeff Breidenbach
- 2021.01.05 20:29 "Re: [Tiff] Motions related to C99 use in libtiff", by Kurt Schwehr
- 2021.01.05 20:46 "Re: [Tiff] Motions related to C99 use in libtiff", by Kemp Watson
-
2021.01.06 04:45 "Re: [Tiff] Motions related to C99 use in libtiff", by William Bader
- 2021.01.06 10:40 "Re: [Tiff] Motions related to C99 use in libtiff", by Even Rouault
- 2021.01.06 14:15 "Re: [Tiff] Motions related to C99 use in libtiff", by Bob Friesenhahn
-
2021.01.10 12:12 "Re: [Tiff] Motions related to C99 use in libtiff", by Even Rouault
- 2021.01.10 14:54 "Re: [Tiff] Motions related to C99 use in libtiff", by Bob Friesenhahn
- 2021.01.10 16:27 "Re: [Tiff] Motions related to C99 use in libtiff", by Roger Leigh
- 2021.01.15 15:58 "Re: [Tiff] Motions related to C99 use in libtiff", by Even Rouault
2021.01.10 16:57 "Re: [Tiff] Motions related to C99 use in libtiff", by Even Rouault
I can not support a solution which will result in most existing applications to fail to compile by default.
The change for typedefs is needed since the existing typedef do break some potential users of libtiff.
The breakage introduced by MR #185 is a compile time breakage. This is the easiest class of breakage to deal with, and here the solution is as simple as adding
#define TIFF_LEGACY_TYPES
before
#include "tiffio.h"
if you don't want to add the _t suffix in your usage of [u]intXXX types.
Once again, breaking the build by default for the major proportion of apps depending on libtiff is not an option that I can support.
I knew there wasn't going to be a concensus, hence those motions. Happy to serve as the bad cop :-)
Even
Spatialys - Geospatial professional services
http://www.spatialys.com