On Mon, Apr 20, 2015 at 09:53:38AM +0200, Martti Kühne wrote: > Are we discussing something for which #include <stdint.h> does not > leave any questions open? int32_t, int_fast32_t or int_least32_t would > probably be the solution here?
We probably want to replace long with uint_least32_t for character representation. long is 8 bytes long on amd64 and 4 bytes long on x86, same as uint_fast32_t. uint_least32_t is 4 bytes almost always. int is not an option as it may be 2 bytes long. > Is there any problem with using stdint.h in general that I'm not aware of? st is already using it.
