Date: Wed, 26 Aug 1998 16:48:00 -0500 From: Zach Heilig <zach@gaffaneys.com> To: "Susan R. O'Brien" <srobrien@mss.lucent.com>, freebsd-bugs@FreeBSD.ORG Subject: Re: Y2K problem Message-ID: <19980826164800.A1675@znh.org.> In-Reply-To: <35E4637C.5E26EEC3@mss.lucent.com>; from Susan R. O'Brien on Wed, Aug 26, 1998 at 03:35:25PM -0400 References: <35E4637C.5E26EEC3@mss.lucent.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980826164800.A1675>