- 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.04 14:23 "[Tiff] Motions related to C99 use in libtiff", by Even Rouault
Hi,
We do not have a formal project steering committee and decision making rules, but given the good discussion that has taken place, I think it is time to take a decision. I'd suggest we proceed with a majority vote with all people that want to cast their votes, with the voting period open until end of week.
Motion 1:
Require compiler with C99 support to build libtiff
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)
Candidate implementation for both by Roger Leigh at:
https://gitlab.com/rleigh/libtiff/-/commits/require-c99
My vote:
Motion 1: +1
Motion 2: +1
Even
Spatialys - Geospatial professional services
http://www.spatialys.com