At 16:59 04/04/28 -0400, Keith Moore wrote:
Not so. The amount of work in decoding an integer (say a UNIX-style
time_t) to a date is approximately equal to the amount of work in
parsing a RFC822 style date, and it's at least as easy to botch
up the decoder as to botch the RFC 822 date parser. The amount of
work in encoding an integer date from yyyy/mm/dd/hh/mm/ss form
is more than the amount of work in encoding that same quantity
in RFC 822 format - and it's harder to get that encoder right.
Are you saying that
yyyy/mm/dd/hh/mm/ss -> integer
is more work than
RFC 822 -> integer
?
If yes, could you say why?
Regards, Martin.