|
From: Stephen W. <st...@ic...> - 2015-05-08 15:06:02
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I think in this day and age, inttypes.h or stdint.h can be assumed to be present. On 05/08/2015 12:42 AM, Martin Whitaker wrote: > There are a number of places in the Icarus code where a pointer is > cast to an integer or vice versa. Currently the code uses a long or > unsigned long integer for the purpose. This doesn't work in 64-bit > Windows, because the Windows ABI requires long integers to be 32 > bits. The proper solution is to use the intptr_t or uintptr_t > types. > > In parts of the Icarus code, there are tests for HAVE_INTTYPES_H, > but in other parts things from inttypes.h (e.g. int64_t and > uint64_t) are used unconditionally. What is the current policy on > this? > > I would guess that any compiler that supports the C++ features we > use is also going to have inttypes.h. - -- Steve Williams "The woods are lovely, dark and deep. steve at icarus.com But I have promises to keep, http://www.icarus.com and lines to code before I sleep, http://www.picturel.com And lines to code before I sleep." -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlVM0IUACgkQrPt1Sc2b3ilGwQCeKxD/IE5g9aU0TPoSTi40nuK4 Q5cAn2YKMxeUYh61Grtp3QRNHmA7772y =iLxl -----END PGP SIGNATURE----- |