Editing Talk:1340: Unique Date
Please sign your posts with ~~~~ |
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
− | |||
− | |||
− | |||
− | |||
What about Daylight Saving Time adjustments and leap seconds? Don't they bring duplicates of the same time or is there a way to account for that in the current system? --[[User:Muskar|Muskar]] ([[User talk:Muskar|talk]]) 10:06, 28 March 2014 (UTC) | What about Daylight Saving Time adjustments and leap seconds? Don't they bring duplicates of the same time or is there a way to account for that in the current system? --[[User:Muskar|Muskar]] ([[User talk:Muskar|talk]]) 10:06, 28 March 2014 (UTC) | ||
:One hour is duplicated each year at the end of DST. Not much happens during that hour, because it's the middle of the night. A poorly written computer program that instructs the computer to set back the clock one hour whenever the clock reaches a specific time would get caught in a recursive loop (never advancing beyond that time). Properly, clocks are set back one hour when that time is first reached, but are allowed to advance after the duplicate hour concludes. | :One hour is duplicated each year at the end of DST. Not much happens during that hour, because it's the middle of the night. A poorly written computer program that instructs the computer to set back the clock one hour whenever the clock reaches a specific time would get caught in a recursive loop (never advancing beyond that time). Properly, clocks are set back one hour when that time is first reached, but are allowed to advance after the duplicate hour concludes. | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
Leap second does not result in a duplicate. The additional second is allowed by increasing the number of seconds in a minute. Normally, the 60 seconds of 11:59 are numbered from 11:59:00 to 11:59:59, which is followed by 12:00:00. When there is a leap second, 11:59 has 61 seconds, numbered from 11:59:00 to 11:59:60 (61 total seconds) and then 11:59:60 is followed by 12:00:00.[[Special:Contributions/173.245.48.24|173.245.48.24]] 18:42, 29 March 2014 (UTC) | Leap second does not result in a duplicate. The additional second is allowed by increasing the number of seconds in a minute. Normally, the 60 seconds of 11:59 are numbered from 11:59:00 to 11:59:59, which is followed by 12:00:00. When there is a leap second, 11:59 has 61 seconds, numbered from 11:59:00 to 11:59:60 (61 total seconds) and then 11:59:60 is followed by 12:00:00.[[Special:Contributions/173.245.48.24|173.245.48.24]] 18:42, 29 March 2014 (UTC) | ||
Line 50: | Line 40: | ||
::It's March 15th now, and it still says the 10th. It's not dynamic. [[Special:Contributions/199.27.128.76|199.27.128.76]] 20:47, 15 March 2014 (UTC) | ::It's March 15th now, and it still says the 10th. It's not dynamic. [[Special:Contributions/199.27.128.76|199.27.128.76]] 20:47, 15 March 2014 (UTC) | ||
− | |||
− | |||
It's funny that Randall seems to have never heard of [http://tools.ietf.org/html/rfc2550 RFC 2550], which goes than the Long Now Foundation in expanding the representable date range. [[Special:Contributions/173.245.53.161|173.245.53.161]] 15:05, 10 March 2014 (UTC) | It's funny that Randall seems to have never heard of [http://tools.ietf.org/html/rfc2550 RFC 2550], which goes than the Long Now Foundation in expanding the representable date range. [[Special:Contributions/173.245.53.161|173.245.53.161]] 15:05, 10 March 2014 (UTC) | ||
Line 66: | Line 54: | ||
:: As a (culturally) dd/mm/[yy]yy person (and ignoring, for brevity, the different options for delimiter), I find yyyy-dd-mm as illogical as mm/dd/yyyy... Why should anybody switch 'precision direction', mid-way? Still, as someone who went through the Y2K process ''and'' worked with colleagues across the Atlantic, I tend to use dd/Mmm/yyyy habitually in "for humans" systems (giving the abbreviated month spelling to avoid all ambiguity, as well as full year-number), or my own "yyyymmdd[-hhmm[ss[.ddd...]]]" format in (informal and internal) programming situations, with comments attached to any conversion routines (inwards and outwards). ((And, yes, there ''are'' ISO/other standards, but I find converting from/to them and internally working with my own long-practiced format works best, for me. YMMV. But be aware of how'd you deal with (or ignore) Leap Seconds!)) [[Special:Contributions/141.101.98.47|141.101.98.47]] 14:58, 12 March 2014 (UTC) | :: As a (culturally) dd/mm/[yy]yy person (and ignoring, for brevity, the different options for delimiter), I find yyyy-dd-mm as illogical as mm/dd/yyyy... Why should anybody switch 'precision direction', mid-way? Still, as someone who went through the Y2K process ''and'' worked with colleagues across the Atlantic, I tend to use dd/Mmm/yyyy habitually in "for humans" systems (giving the abbreviated month spelling to avoid all ambiguity, as well as full year-number), or my own "yyyymmdd[-hhmm[ss[.ddd...]]]" format in (informal and internal) programming situations, with comments attached to any conversion routines (inwards and outwards). ((And, yes, there ''are'' ISO/other standards, but I find converting from/to them and internally working with my own long-practiced format works best, for me. YMMV. But be aware of how'd you deal with (or ignore) Leap Seconds!)) [[Special:Contributions/141.101.98.47|141.101.98.47]] 14:58, 12 March 2014 (UTC) | ||
::: I once toyed with the notation 0y20140310, with the "0y" prefix (a pun on C's "0x") distinguishing it from the eight-digit integer 20140310. I later decided that 0y20140310.175959 would be a good way to extend it to specify both date and time, and it still parses as a single C token if that property is useful. (And it sorts properly, of course.) [[Special:Contributions/199.27.128.68|199.27.128.68]] 04:15, 24 March 2014 (UTC) | ::: I once toyed with the notation 0y20140310, with the "0y" prefix (a pun on C's "0x") distinguishing it from the eight-digit integer 20140310. I later decided that 0y20140310.175959 would be a good way to extend it to specify both date and time, and it still parses as a single C token if that property is useful. (And it sorts properly, of course.) [[Special:Contributions/199.27.128.68|199.27.128.68]] 04:15, 24 March 2014 (UTC) | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− |