Path: utzoo!utgpu!water!watmath!clyde!bellcore!decvax!decwrl!hplabs!sdcrdcf!trwrb!desint!geoff
From: geoff@desint.UUCP (Geoff Kuenning)
Newsgroups: news.software.b
Subject: Re: Another 'unparsable date' error
Keywords: unparsable date
Message-ID: <1683@desint.UUCP>
Date: 16 Feb 88 21:39:29 GMT
References: <8123@eddie.MIT.EDU> <1988Feb11.184413.18950@sq.uucp>
Reply-To: geoff@desint.UUCP (Geoff Kuenning)
Organization: Interrupt Technology Corp., Manhattan Beach, CA
Lines: 14

In article <1988Feb11.184413.18950@sq.uucp> msb@sq.UUCP (Mark Brader) writes:

> > >	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.  (Found by playing with values for about
> 1 minute; I figured it was quicker than writing a program.)

Whenever I see a date in the range of "00-09", I think 20th, not 21st,
century.  The range of a 31-bit number is about 68 years;  the base is
1970.  So a maximal negative number produces a date in the early 1900's.
I'd suspect 0x7FFFFFFF, though I didn't take the time to try it out.
-- 
	Geoff Kuenning   geoff@ITcorp.com   {uunet,trwrb}!desint!geoff