Is it not a bit ridiculous that the system can't cope?
surely a computer system in todays world of modern tech would be able to cope with the figure of 00:00, as 00:00 is just a number on the clock as is 00:01, 00:02, 00:03 and so on....
The system, or at least one of them, certainly does throw a wobbly if you try to enter a time of 0000, but I've always thought that it was a deliberate decision to make it so (to avoid any confusion) rather than just a limitation of the system.
On a similar note, what days are they registered as?
For example, there was this service this morning: 2W85 0042 Bedford to Three Bridges. Would this be classified as today (15th), or yesterday (14th)?
Isn't midnight 24.00 and 1 minute past midnight is 00.01, as its called the 24 hour clock
I would guess the confusion is what date does the 00:00 refer to? I seem to recall that for this very reason, military timings are always 23:59 or 00:01 as it removes this ambiguity.
(Slightly off topic) - I once had a deadline set for "Friday night at 24:00" because the lecturer was so sick of "When you say midnight Friday do you mean the start or end of Friday!
0000 is midnight at the start of a day, 2400 at the end of a day. I think.
I've also seen times reported as 24nn which is even more confusing. Can't remember where, mind (but I didn't dream it!).
(Slightly off topic) - I once had a deadline set for "Friday night at 24:00" because the lecturer was so sick of "When you say midnight Friday do you mean the start or end of Friday!
Wouldn't the start of Friday still be night?!
I know. But I was trying to that pedantic!I think that's usually considered "morning", e.g. "I have to get up early because I have to catch a train at 2 o'clock in the morning".
There is no such time as 24:00; after 23:59:59 the next second is 00:00:00 the next day.
And talking of Y2K, the consequences of not handling the "century" correctly do still cause some issues with computer systems even today; I know of at least one application that used just DD.MM.YY and went from 31.12.2014 to 01.01.1915. And for Microsoft applications, the next date after 31.12.2029 is 01.01.1930, so there are 15 years left to solve that one if the century is not used and you rely on the "default" processing...
But as is shown here, there is scope for confusion so for most public use, 00:00 & 24:00 don't exist in schedules....
Microsoft Software uses a 100 year 'Window' for interpreting 2 digit year input. The extremes of the window can be altered fairly easily in the date/time section of the system setup. The arrival of 2030 will not be a problem.
p.s. Note that it's only when inputting in the format dd/mm/yy that it happens anyway, type it in as dd/mm/yyyy and it will take whatever date you want. Likewise if cell A1 in a spreadsheet contains 31/12/2029, typing =A1+1 in a cell will return 01/01/2030
What will happen at year 10,000??
I bet that will mess my computer up.
What does the automated voice say with 00 hours departures?
Zero-zero? Oh oh? Hundred? Or just midnight??
In the Year 10,000 the computers will rule the world.