From owner-freebsd-arch Wed Jun 6 18:48: 0 2001 Delivered-To: freebsd-arch@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id E415337B403 for ; Wed, 6 Jun 2001 18:47:58 -0700 (PDT) (envelope-from obrien@nuxi.ucdavis.edu) Received: from dragon.nuxi.com (root@trang.nuxi.com [206.40.252.115]) by relay.nuxi.com (8.11.2/8.11.2) with ESMTP id f571lsR16499; Wed, 6 Jun 2001 18:47:54 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f571lre46031; Wed, 6 Jun 2001 18:47:53 -0700 (PDT) (envelope-from obrien) Date: Wed, 6 Jun 2001 18:47:53 -0700 From: "David O'Brien" To: Garrett Wollman Cc: arch@FreeBSD.org, freebsd-standards@bostonradio.org Subject: Re: time_t definition is wrong Message-ID: <20010606184753.C45892@dragon.nuxi.com> Reply-To: obrien@FreeBSD.org References: <200106020823.f528N5O98998@earth.backplane.com> <20010602085237.A73968@dragon.nuxi.com> <200106021739.f52Hd9V03943@earth.backplane.com> <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> <200106041547.LAA76688@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200106041547.LAA76688@khavrinen.lcs.mit.edu>; from wollman@khavrinen.lcs.mit.edu on Mon, Jun 04, 2001 at 11:47:18AM -0400 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Jun 04, 2001 at 11:47:18AM -0400, Garrett Wollman wrote: > > 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. With size_t you want to be able to hold the largest number you can. It is used for lengths, etc.. where you don't want wrap around. In time_t's case we already know we will get a wrap around, and in my mind all our plaforms should do it at the same point. -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message