2021.01.02 02:04 "Re: [Tiff] Enabling and requiring C99 language support", by Edward Lam

Just to throw my 2 cents in, it seems easiest and least contentious to stop at !185.

Now that the world is moving to Python 3, hopefully there will be less use of Visual Studio 2008, and therefore more use of VS versions that do not have stdint.h. From our niche corner of the world (vfxplatform.com), the minimum compiler version on Windows is Visual Studio 2017.

-Edward

PS. <rant> As an aside, the uint64 vs size_t situation on OSX is quite annoying. uint64 is already defined in their system headers so it *must* be the same type as uint64_t or else you'll get warnings/errors about mismatched types. Furthermore, uint64_t is NOT the same underlying type as size_t even though OSX only supports 64-bit processes these days and their byte size is identical. For C++, this is extra annoying because you need extra overloads for size_t on OSX so that it works the same way for your uint64 overloads.I actually ran into a (since fixed) Boost.Hash bug because it had an int64_t/uint64_t overloads for hashing that was being used for all platforms except on OSX (which defaulted to the generic implementation that used a different algorithm) because of this type difference. This was one source of our regression test differences on OSX vs Linux/Windows until we finally realized this years later. </rant>