Date: Mon, 4 Jun 2001 11:47:18 -0400 (EDT) From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu> To: obrien@FreeBSD.org Cc: arch@FreeBSD.org, freebsd-standards@bostonradio.org Subject: Re: time_t definition is wrong Message-ID: <200106041547.LAA76688@khavrinen.lcs.mit.edu> In-Reply-To: <20010602142011.N31257@dragon.nuxi.com> References: <200106012318.f51NI8w38590@bunrab.catwhisker.org> <200106020823.f528N5O98998@earth.backplane.com> <20010602085237.A73968@dragon.nuxi.com> <200106021739.f52Hd9V03943@earth.backplane.com> <p05100e0fb73ee9d458f7@[128.113.24.47]> <20010602124907.G31257@dragon.nuxi.com> <200106022005.f52K5FR04823@earth.backplane.com> <20010602131404.M31257@dragon.nuxi.com> <200106022040.f52KeSJ05088@earth.backplane.com> <20010602142011.N31257@dragon.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
<<On Sat, 2 Jun 2001 14:20:11 -0700, "David O'Brien" <obrien@FreeBSD.org> said: > time_t needs to be consistent across all FreeBSD platforms. No, it doesn't. > Otherwise we get in consistent behavior across our platforms. Which will always be the case given that some platforms are ILP32 and some are LP64. s/time_t/size_t/g and see where that argument gets you. > This includes both the size of it, and the spelling of the printf() > format specifier. Nonsense. Any program which attempts to print a time_t without casting appropriately is simply, flat-out, wrong, and has been wrong for more than ten years now. -GAWollman 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?200106041547.LAA76688>