WvV> I don't think the 'minute' can ever be "60" !?
NB> second = zeroToSixty
WvV> The 'second' can be "60" when there is a leap second inserted into UTC.
That was the case at 2016-12-31 23:59:60, it was mentioned in the news.
WvV> It would be very cool if anyone ever accomplished to write a message WvV> with that date/time stamp! (Without cheating of course! ;))
You could try by resetting your system clock to 2016-12-31 23:50:00, write a mail, and wait to 23:59:59 when pressing at the saving button. With my RISC OS E-Mail and Point software I can do that. Note the wait time for the reaction second everyone has ;-). But I doubt very much if my Acorn RISC OS 4.04 and its clients can generate that specific timestamp 23:59:60. It would result in 2017-01-01 00:00:00. Of course you could manually edit the outgoing msg or mailpack to the suggested timestamp. But then how will other systems on the route react? I soppuse they would generate an error, or correct the timestamp, in stead of sending it further unchanged to 2016-12-31 23:59:60. Inserting that extra Second at 2016-12-31 23:59:59 was not the most logical moment. I think it was a nice idea if they did it at 2016-02-29 23:59:59, then 2016-02-29 23:59:60 would be very unique as birthday moment ;-). I.e. very difficult to plan.
Henri.
--- * Origin: Connectivity is the Future; UniCorn BBS 31 26 4425506 (2:280/1208)
