2021.01.04 14:23 "[Tiff] Motions related to C99 use in libtiff", by Even Rouault
- 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.05 17:14 "Re: [Tiff] Motions related to C99 use in libtiff", by Greg Troxel
As pointed out by Roger,
https://gitlab.com/rleigh/libtiff/-/blob/ bb0c8ac183e263759ed9e6a6c0563d35b9459c77/libtiff/tiff.h#L68
there's actually an easy way to make packages that wouldn't change their source code to still compile by setting -DTIFF_LEGACY_TYPES That should hopefully make packagers' effort reasonable.
Yes, that's easy enough and a reasonable compromise. Thanks for pointing that out, and to Roger for doing it.