Date: Wed, 31 Oct 2001 19:02:30 -0500 (EST) From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu> To: peter.jeremy@alcatel.com.au Cc: arch@FreeBSD.org Subject: Re: 64 bit times revisited.. Message-ID: <200111010002.fA102UC18044@khavrinen.lcs.mit.edu> In-Reply-To: <20011101102014.D94635@gsmx07.alcatel.com.au> References: <20011031163741.C85128@gsmx07.alcatel.com.au> <200110311947.OAA05182@devonshire.cnchost.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <20011101102014.D94635@gsmx07.alcatel.com.au> you write: >finding this software. 2038 is biting some applications now Those applications are broken. Any application which deals with prospective events that far into the future needs to be dealing with dates, not POSIX seconds-since-the-epoch. There are many changes which can happen between now and 2038 which would make any calculation involving seconds-since-the-epoch even more invalid than it already is. If you have a real-world application that depends on something happening precisely 1,142,910,768 seconds from now, I'd like to hear about it. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200111010002.fA102UC18044>