Path: utzoo!utgpu!watserv1!watmath!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!wuarchive!bcm!tmc.edu!sob
From: sob@tmc.edu (Stan Barber)
Newsgroups: news.software.b
Subject: Re: The anomolous handling of bad dates in cnews.
Message-ID: <5791@gazette.bcm.tmc.edu>
Date: 31 May 91 20:58:53 GMT
References: <1991Apr25.223301.27280@world.std.com> <1991May16.211311.3544@eua.ericsson.se> <1991May23.024533.9731@world.std.com>
Sender: usenet@bcm.tmc.edu
Organization: Baylor College of Medicine, Houston, TX
Lines: 21
Nntp-Posting-Host: tmc.edu

In article <1991May23.024533.9731@world.std.com> geoff@world.std.com (Geoff Collyer) writes:
>As I said above, inews rewrites the date, if it can understand the date
>at all, into canonical form.  If it can't understand the date using a
>fairly tolerant parser (getabsdate for Date: and getdate [for now] for
>Expires:), I don't think substituting the current date is a great
>idea.

I am afraid I disagree with this.

If inews is used when posting an article and it can't figure out the date,
I can't think of a rational case for not using the current date. Note
that I am referring to when an article is first posted, NOT when it is relayed.

If there is a rational case for not using the current date under these
circumstances, I look forward to reading about it.


-- 
Stan           internet: sob@bcm.tmc.edu         Director, Networking 
Olan           uucp: rutgers!bcm!sob             and Systems Support
Barber         Opinions expressed are only mine. Baylor College of Medicine