Quick joke
-
... or not so much!!! Programmer (Me) : Place 0 (zero) on that regestry key. Tech Staff question: Hexadecimal or decimal?
-
... or not so much!!! Programmer (Me) : Place 0 (zero) on that regestry key. Tech Staff question: Hexadecimal or decimal?
Dilbert: You use zeros? We had to use the letter 'O'!
Author of The Career Programmer and Unite the Tribes www.PracticalStrategyConsulting.com
-
... or not so much!!! Programmer (Me) : Place 0 (zero) on that regestry key. Tech Staff question: Hexadecimal or decimal?
0:00hs (what is the same as 24:00hs) belongs to "today" or to "tomorrow"?
Engaged in learning of English grammar ;)
For God so loved the world, that he gave his only begotten Son, that whosoever believeth in him should not perish, but have everlasting life.(John 3:16) :badger: -
0:00hs (what is the same as 24:00hs) belongs to "today" or to "tomorrow"?
Engaged in learning of English grammar ;)
For God so loved the world, that he gave his only begotten Son, that whosoever believeth in him should not perish, but have everlasting life.(John 3:16) :badger:Read up on your ISO 8601. The day begins with 00:00, and ends with 24:00 (not that I like 24:00, but it's in the Standard).
-
Read up on your ISO 8601. The day begins with 00:00, and ends with 24:00 (not that I like 24:00, but it's in the Standard).
Yes, but none clock shows "24:00", when the time pass of "23:59" the clock goes to "0:00", what led to think what 00:00 == 24:00, and the "today" and "tomorrow" share the exact same second ;), what brings confusion about if you are counting some second twice or once some day have one second minus than other :zzz::zzz::zzz:
Engaged in learning of English grammar ;)
For God so loved the world, that he gave his only begotten Son, that whosoever believeth in him should not perish, but have everlasting life.(John 3:16) :badger: -
Read up on your ISO 8601. The day begins with 00:00, and ends with 24:00 (not that I like 24:00, but it's in the Standard).
I didn't think 2400 was even a valid time.
BW
Quick to judge, quick to anger, slow to understand.
Ignorance and prejudice and fear walk hand in hand.
-- Neil Peart -
I didn't think 2400 was even a valid time.
BW
Quick to judge, quick to anger, slow to understand.
Ignorance and prejudice and fear walk hand in hand.
-- Neil Peart -
No? How about 23:59:60?
-
No? How about 23:59:60?
I've never seen anyone use 24:00, likely because nobody does. From a quick read about ISO date/time standards in the ISO 8601 specification I found that it is generally accepted that people use 00:00 as a representation of midnight. However, ISO 8601 accepts that 01/01/2007 24:00:00 and 01/02/2007 00:00:00 are both equal representations of midnight. I don't see any reason to not use 00:00:00 as midnight in the programming I do that requires date/time management. Maybe you can shed some light on why you think it's such a big deal.
Aaron Clint Work
-
I didn't think 2400 was even a valid time.
BW
Quick to judge, quick to anger, slow to understand.
Ignorance and prejudice and fear walk hand in hand.
-- Neil PeartI remember reading somewhere (found one reference: http://www.merlyn.demon.co.uk/datefmts.htm#ODs[^]) that even times above 24:00 were acceptable if it will reduce confusion. The example I remember them giving was for train station schedules: If the train schedule started at, say, 03:00, then the end of the schedule would be given as 27:00, so that you could differentiate which day's schedule the time belonged to.
-- Marcus Kwok