Checksum: 12674
Lines: 19
Path: utzoo!lsuc!sq!msb
From: msb@sq.uucp (Mark Brader)
Date: Fri, 19-Feb-88 22:02:59 EST
Message-ID: <1988Feb19.220259.1870@sq.uucp>
Newsgroups: news.software.b
Subject: Re: Another 'unparsable date' error
Summary: Not minus-infinity
References: <8123@eddie.MIT.EDU> <1988Feb11.184413.18950@sq.uucp> <1683@desint.UUCP>
Reply-To: msb@sq.UUCP (Mark Brader)
Organization: SoftQuad Inc., Toronto
Keywords: unparsable date

> > > >	expire: Unparsable date "6 Feb 06 06:28:15 GMT"
> > 
> > Assuming the date to be in the 21st century, this gives a time value
> > of 1139207295, or 0x43E6EC7F.

> Whenever I see a date in the range of "00-09", I think 20th, not 21st,
> century.  I'd suspect 0x7FFFFFFF ...

He means 0x80000000, of course.  Nope.  My arithmetic this time may be a
little suspect, but ctime() seems to work on negative values on this machine,
except for printing the day of the week as garbage unless it's Friday,
["%" never returns a negative result, right? :-)] and that gives me the
above date as being -2016552705, i.e. -0x78322701, i.e. 0x87CDD8FF assuming
2's complement 32-bit numeration.  Which doesn't seem to help much either.
Oh well.

Mark Brader, SoftQuad Inc., Toronto, utzoo!sq!msb, msb@sq.com
	"I'm a little worried about the bug-eater," she said.  "We're embedded
	in bugs, have you noticed?"		-- Niven, "The Integral Trees"