2 ms·
Because you're breaking backwards compatibility by changing the interpretation of those timestamp fields. If you do that, you might as well switch to a 64-bit t
by jabl 6y ago
Because you're breaking backwards compatibility by changing the interpretation of those timestamp fields. If you do that, you might as well switch to a 64-bit time_t.
Treating a 32-bit timestamp field as unsigned seconds since the epoch at least keeps backwards compatibility with existing software up until 2038.