Bob Eager wrote:
> On Tue, 21 Sep 2021 03:36:56 -0400, Paul wrote:
>
>> The dates all look "normal" on my newsclient.
>
> Try checking on the website. That says 51 years.
>
But that is their interpretation of this.
Date: Tue, 10 Mar 2020 12:50:00 +0000 (GMT+00:00) <===
From: Jimk <
jk98...@gmail.com>
References: <r48095$2ub$
1...@dont-email.me>
Subject: Re:Chalet style house insulation.
The JimK post doesn't have "Thu, Jan 1, 1970 12:00 AM"
anywhere in the raw content.
That's why I provided the Howard links, so you could see
for yourself that JimK did not post such a string.
All it takes is poorly coded conversion routines (that
call perfectly-correct system routines), to screw up
like that. Somebody did not check for an ERRNO before
using the value. It's not some time-library making
the mistake here. It's an applications programmer
who is abusing the results of the conversion routines.
Every input you feed to that library, must have
the inputs validated. In the JimK example, I
would be giving the string a "hair cut" by removing
the "(GMT+00:00)" part, which adds no value. The
+0000 next to it, already says that.
Paul