Path: utzoo!utgpu!water!watmath!clyde!ima!haddock!karl From: karl@haddock.ima.isc.com (Karl Heuer) Newsgroups: comp.std.c Subject: Re: The type of time_t Message-ID: <10005@haddock.ima.isc.com> Date: 25 Oct 88 03:45:41 GMT References: <442@grand.UUCP> <8700@smoke.BRL.MIL> <6964@cdis-1.uucp> <9816@haddock.ima.isc.com> <1988Oct22.230215.19411@utzoo.uucp> Reply-To: karl@haddock.ima.isc.com (Karl Heuer) Organization: Interactive Systems, Boston Lines: 12 In article ron@ron.rutgers.edu (Ron Natalie) writes: >Frankly, life is going to be screwed up before the time bits are fixed because >many programs that compute dates think that 2000 is not a leap year. I doubt that there are many such programs, since the naive algorithm (y%4==0) happens to agree with the correct one until 2100 (the century and quadri- century corrections cancel each other out in 2000). The problem that's likely to occur in 2000 has to do with two-digit notation for the year; now *that's* going to screw up a lot of existing code. (The `date' command doesn't even *have* a notation to set the date beyond 1999!) Karl W. Z. Heuer (ima!haddock!karl or karl@haddock.isc.com), The Walking Lint