Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!dali.cs.montana.edu!caen!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!peregrine!sceard!mrm
From: mrm@sceard.Sceard.COM (M.R.Murphy)
Newsgroups: news.software.b
Subject: Re: IMPORTANT: Users of Rodney's UUCP modules / GUS
Message-ID: <1991May17.132331.13402@sceard.Sceard.COM>
Date: 17 May 91 13:23:31 GMT
References: <1991May13.172233.5581@zoo.toronto.edu> <DByX213w164w@mantis.co.uk>
Reply-To: mrm@Sceard.COM (M.R.Murphy)
Organization: The Mole and Badger Association of Northern San Diego County
Lines: 31

In article <DByX213w164w@mantis.co.uk> mathew@mantis.co.uk (CNEWS MUST DIE!) writes:
[...]
>
>Look, I don't care what the mistake is or who made it. C News should not
>discard an article unless it is unable to correct the header; and if it does
>discard an article, it should at least attempt to warn the poster.

Others have pointed out that it might not be polite to a poster's site-mates,
site administration, or upstream E-mail connections to flood the poster with
thousands of warning messages. I don't want to pay for sending those thousands
of messages. I'd much rather wade through the thousands of lines of cruft in
a log file than send thousands of mail messages. Then I could even call the
poster on the telephone and offer to help. Oh, well.

[...]
>If it *was* the missing comma, then I apologise for assuming that it was the
>non-RFC822 4-digit year which was at fault. I don't apologise for the
>flaming, though. A missing comma in the date is such a simple-to-allow-for
>and likely-to-occur error that I still think C News is VERY wrong to drop
>articles because of it.

Yeah. I thought that FORTRAN compilers ought to be able to correct
      DO 10 I=1 15
to
      DO 10 I=1,15
too.

(To the Severely Humor-Impaired TwitS, please note that the last section was,
in fact, a sarcastic response.)
-- 
Mike Murphy  mrm@Sceard.COM  ucsd!sceard!mrm  +1 619 598 5874