64-bit time_t?
Eric Blake
ebb9@byu.net
Thu Sep 17 11:26:00 GMT 2009
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Is the transition to 1.7 a good time to change the ABI and offer a 64-bit
time_t type that won't overflow in 2038? Would we have to do the same
sort of transition magic as was done back in 1.5 for 32-bit vs. 64-bit off_t?
- --
Don't work too hard, make some time for fun as well!
Eric Blake ebb9@byu.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkqyHMsACgkQ84KuGfSFAYDWGwCfeNEhefLmrz9u+0A135ZLbLzO
LacAn3BUdTXa8I8RwxHCSZKyK1JQweCS
=QhZR
-----END PGP SIGNATURE-----
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
More information about the Cygwin
mailing list