Coding standards for 32/64-bits data

Bron Gondwana brong at
Thu Jun 30 11:10:50 EDT 2011

On Thu, Jun 30, 2011 at 10:54:43PM +0900, OBATA Akio wrote:
> For ticket 3376 (time_t != unsigned long), I would be helpful if TIME_T_FMT is also introduced.
> (or use fixed type (uint64_t?) for network protocol/database timestamp instead of time_t?)

To be honest, you can mostly use uint32_t for times in Cyrus
still - because all the timestamps get stored down into 32
bit fields in the binary formats.

But it might make sense to pass it around in 64 bit format
everywhere that we're not actually storing to disk...


More information about the Cyrus-devel mailing list