From owner-freebsd-arch Sun Jun 3 9:35: 6 2001 Delivered-To: freebsd-arch@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id BFF0A37B401; Sun, 3 Jun 2001 09:35:03 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id CAA09374; Mon, 4 Jun 2001 02:34:58 +1000 Date: Mon, 4 Jun 2001 02:33:21 +1000 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Poul-Henning Kamp Cc: obrien@FreeBSD.ORG, Matt Dillon , David Wolfskill , arch@FreeBSD.ORG Subject: Re: time_t definition is worng In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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, 4 Jun 2001, I wrote: > On Sat, 2 Jun 2001, Poul-Henning Kamp wrote: > > > In message <20010602124732.F31257@dragon.nuxi.com>, "David O'Brien" writes: > > Uhm, time_t must be signed and at least 32 bits. > ... > In theory, it can be any signed arithmetic type from signed char to XXXXXX Oops. I should have said that it can be _any_ arithmetic type. (It can also have any representation in C90 although not in POSIX (POSIX requires it to have a particular broken representation that can't handle leap seconds). > > >I am more than willing to define time_t as `long long' so it is 64-bits > > >across the board. > > > > We'll have to do this before 2038 anyway... > > You mean "before 2106". uint32_t can represent times between 1970 > and 2106. If you want to represent times much before 1970, then time_t > is already inadequate. Here I use the fact that it can be unsigned. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message