Date: Fri, 23 Apr 1999 07:42:02 -0400 From: Chris Johnson <cjohnson@palomine.net> To: Ilya Varlashkin <ilya@ripn.net> Cc: stable@FreeBSD.ORG Subject: Re: Year 2000 Message-ID: <19990423074202.A19312@palomine.net> In-Reply-To: <199904231136.PAA44330@diamond.ripn.net>; from Ilya Varlashkin on Fri, Apr 23, 1999 at 03:35:59PM %2B0400 References: <4.1.19990419154056.00b88920@mail-r> <199904231136.PAA44330@diamond.ripn.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Apr 23, 1999 at 03:35:59PM +0400, Ilya Varlashkin wrote: > According to Ludwig Pummer: > > At 02:20 PM 4/19/99 , Chad R. Larson wrote: > > >... But it did make me wonder if the FreeBSD organization, > > >or any of y'all out there have so done (and if so, what the outcome > > >was). I'd expect sore spots in the locale stuff, perhaps in process > > >accounting. > > > > http://www.freebsd.org/y2kbug.html > > > > Ok, just look: > > "After extensive analysis and testing, we believe that > FreeBSD is 100% Y2K compliant...." (from that page) > > But what about struct tm from /usr/include/time.h: > > int tm_year; /* years since 1900 */ > > So I suppose asctime(3), localtime(3) and gmtime(3) are not Y2K-compliant, > are they? Applications that blindly rely on Y2K-compliant OS will > operate wrong year value. Did I missed something? An int can hold integers bigger than 99. In the year 2003, for example, tm_year would be 103, which fits nicely into an int. Chris 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?19990423074202.A19312>