"Benjamin J. Stassart" <[EMAIL PROTECTED]> writes: > I have no idea if TMDA is 2038 compliant and I would hope it doesn't > use a two digit year, so I don't know if "dated=100Y" works.
This depends not on TMDA, but on your Unix OS where times are represented as seconds since the Epoch (midnight Jan 1, 1970). On 32-bit systems, signed longs of 32 bits give you a range of just over 68 years, so in 2038 you will run out of bits. [EMAIL PROTECTED] ./tmda-address -V TMDA/1.0.1+ "Bold Forbes" (Python/2.3.3 on Darwin-6.8-Power_Macintosh-powerpc-32bit) [EMAIL PROTECTED] ./tmda-address -d 100Y [EMAIL PROTECTED] [EMAIL PROTECTED] ./tmda-check-address [EMAIL PROTECTED] STATUS: VALID EXPIRES: Tue Jan 19 03:14:07 2038 UTC Presumably you will be using a system that uses 64 bit longs by then. :-) You can already see that TMDA works well past 2038 on such a system. [EMAIL PROTECTED] ./tmda-address -V TMDA/1.0.1+ "Bold Forbes" (Python/2.2.1 on linux-x86_64) [EMAIL PROTECTED] ./tmda-address -d 100Y [EMAIL PROTECTED] [EMAIL PROTECTED] ./tmda-check-address [EMAIL PROTECTED] STATUS: VALID EXPIRES: Wed Jan 16 06:43:02 2104 UTC _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
