Date: Tue, 5 Jun 2001 14:34:03 -0400 From: "Drew Derbyshire" <avatar+pop3@kew.com> To: <freebsd-stable@FreeBSD.ORG> Subject: Re: time_t definition is worng Message-ID: <029c01c0edee$18b52d20$94cba8c0@xena> References: <200106051533.IAA02947@gndrsh.dnsmgr.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> Bite the freaking bullet and make time_t long long across all platforms > NOW!! Yes, you'll have to fix ufs, and probably a lot of things that > we haven't even thought of, but NOW is the time to start, not in 20 years!! Jeez. Don't break working code. Push for a fix of the UNIX epoch now if you want, but use a new typedef and new library calls. Then you don't break code which WILL work for another 26 years; also, you can search for time_t in the code and if you find it, you know you still have a problem in 2038. IPV6 support is rapidly getting into sources only because it didn't break every program on the planet using IPV4. Learn from the example. -ahd- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?029c01c0edee$18b52d20$94cba8c0>