From owner-freebsd-bugs Wed Aug 26 14:44:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA26437 for freebsd-bugs-outgoing; Wed, 26 Aug 1998 14:44:43 -0700 (PDT) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: from a486n1.znh.org (dialup12.gaffaneys.com [208.155.161.62]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA26432 for ; Wed, 26 Aug 1998 14:44:40 -0700 (PDT) (envelope-from zach@gaffaneys.com) Received: (from zach@localhost) by a486n1.znh.org (8.9.1/8.9.1) id VAA02177; Wed, 26 Aug 1998 21:48:00 GMT (envelope-from zach) Message-ID: <19980826164800.A1675@znh.org.> Date: Wed, 26 Aug 1998 16:48:00 -0500 From: Zach Heilig To: "Susan R. O'Brien" , freebsd-bugs@FreeBSD.ORG Subject: Re: Y2K problem References: <35E4637C.5E26EEC3@mss.lucent.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <35E4637C.5E26EEC3@mss.lucent.com>; from Susan R. O'Brien on Wed, Aug 26, 1998 at 03:35:25PM -0400 Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Aug 26, 1998 at 03:35:25PM -0400, Susan R. O'Brien wrote: > I'm using 2.2.5 and was looking at the source code for localtime and > asctime. They're using a #define TM_YEAR_BASE 1900. > > This looks to be a bit of a problem for Y2K compliancy! > > Anyone checking this out? Yes, if you look closely, you will notice that 'tm_year' is not restricted to being only 2 digits, is good for INT_MAX years (or till AD 2147483647 for FreeBSD). More specifically, the year 2000 will be 100, 2001 -> 101, ... . -- Zach Heilig -- zach@gaffaneys.com Real Programs don't use shared text. Otherwise, how can they use functions for scratch space after they are finished calling them? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message