From owner-freebsd-hackers Thu Aug 13 14:13:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA17553 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 14:13:21 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lariat.lariat.org (lariat.lariat.org [206.100.185.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA17547 for ; Thu, 13 Aug 1998 14:13:18 -0700 (PDT) (envelope-from brett@lariat.org) Received: (from brett@localhost) by lariat.lariat.org (8.8.8/8.8.6) id PAA15313; Thu, 13 Aug 1998 15:12:42 -0600 (MDT) Message-Id: <4.1.0.44.19980813150058.03f4dd80@127.0.0.1> X-Sender: brett@127.0.0.1 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1.0.44 (Beta) Date: Thu, 13 Aug 1998 15:03:05 -0600 To: Mike Smith From: Brett Glass Subject: Re: 64-bit time_t Cc: Mike Smith , hackers@FreeBSD.ORG In-Reply-To: <199808131924.MAA00367@dingo.cdrom.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:24 PM 8/13/98 -0700, Mike Smith wrote: >> I'd kind of like to do financial projections for my retirement and not >> have the calculations blow up, as they do now. > >time_t is a format for the system current time. As such, you're abusing >it mightily if you expect it to be a general-purpose time value. It's used throughout UNIX and UNIX programs as such. And rightfully so; it's silly to have multiple date formats. >Might I suggest that you should consider using something with perhaps a >slightly reduced precision, like anyone else that does work involving >longer timeframes? This would create an incompatible notation and would make life much more difficult than fixing the basic problem. >time_t is not a hammer. Nope, but I don't intend to carry an entire box of tools to screw in a light bulb.... ;-) --Brett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message