Date: Fri, 1 Jun 2001 13:52:11 -0700 (PDT) From: John Polstra <jdp@polstra.com> To: stable@freebsd.org Cc: chad@DCFinc.com Subject: Re: Re[2]: time_t definition is worng Message-ID: <200106012052.f51KqBT29871@vashon.polstra.com> In-Reply-To: <200106012015.NAA17134@freeway.dcfinc.com> References: <200106012015.NAA17134@freeway.dcfinc.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <200106012015.NAA17134@freeway.dcfinc.com>, Chad R. Larson <chad@DCFinc.com> wrote: > > From the commit log: > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > revision 1.25 > date: 2001/05/18 01:43:25; author: obrien; state: Exp; lines: +2 -2 > Make _BSD_TIME_T_ (time_t) an `int' rather than `long'. This will help > flag errors where programmers assume time_t is a long, which it is not on > 64-bit platforms. > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > > Well, time_t may or not be a "long", depending on your platform. But it > sure as hell is 64-bits. > > Back out the revision. No, time_t is and always has been 32 bits on all FreeBSD platforms. I agree with Matt that it would be nice if it were 64 bits at least on 64-bit platforms. Unfortunately, practically speaking it's too late to make that change now. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa 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?200106012052.f51KqBT29871>