On Tue, Jan 11, 2000 at 04:51:01PM -0800, David Good wrote:
> On Mon, Jan 10, 2000 at 01:45:23PM -0800, Michael Elkins <[EMAIL PROTECTED]> wrote:
> > On Thu, Jan 06, 2000 at 12:49:26PM +0000, Lars Hecking wrote:
> > > I'm not sure about the if (tm.tm_year < 70) part. According the UNIX98
> > > specification by The Open Group, which has been adopted by all major
> > > Unix vendors, two-digit years 69-99 refer to the 20th century (19xx),
> > > and 00-68 refers to the 21st century (20xx), so I think this line of code
> > > should really read
> >
> > The UNIX clock can't represent dates before January 1, 1970 0:00:00 UTC, so
> > it doesn't make any sense to change the heuristic from its current method.
>
> I think UNIX98 does this because January 1, 1970 0:00:00 UTC is
> Wed Dec 31 16:00:00 1969 Pacific time (for example), so there *can* be valid
> UNIX dates where the year is 69. Of course, I don't know that it makes much
> sense to bother with a case that only covers 12 hours...
At least on my system, time_t is signed. Sometime in January 2038 it
flips back to sometime in January 1901. I think that's the common
implementation.
jf
--
John Franklin
[EMAIL PROTECTED]
ICBM: N37 12'54", W80 27'14" Z+2100'
