Gilles Detillieux (firstname.lastname@example.org)
Wed, 3 Feb 1999 13:54:17 -0600 (CST)
According to Geoff Hutchison:
> The only problem we might run into is if some server *really* breaks the
> standard and sends us dates in a really weird format like 02/03/99
> 1:58:03 PM EST.
Well, with my patch, getdate() should detect that both attempts at
mystrptime() failed, and fall back on the current date. The problem
before was that mystrptime() could fail, and getdate() wouldn't know it,
so it passed nonsense in the tm structure to strftime(), which in some
implementations would do really nasty things.
> Should we try to match every possible date format?
No, of course not, but if any non-standard date formats become popular
in any case (and Microsoft has a phenomenal knack for popularizing
non-standard implementations of protocols), then it should be fairly
easy to add extra attempts at mystrptime() in getdate() to handle them.
Anything else can fall back on the current time.
-- Gilles R. Detillieux E-mail: <email@example.com> Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/~grdetil Dept. Physiology, U. of Manitoba Phone: (204)789-3766 Winnipeg, MB R3E 3J7 (Canada) Fax: (204)789-3930 ------------------------------------ To unsubscribe from the htdig mailing list, send a message to firstname.lastname@example.org containing the single word "unsubscribe" in the SUBJECT of the message.
This archive was generated by hypermail 2.0b3 on Wed Feb 10 1999 - 17:09:05 PST