Talk:Year 2038 problem
Add topicLatest comment: 1 month ago by TarkusAB in topic Year 2000
 | This article was nominated for deletion on May 2, 2022. The result of the discussion was Snow keep. |
 | This article is rated B-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||
Why signed?
[edit]Why is this a signed 32 bit integer? Is there any particular reason? 188.147.100.26 (talk) 01:30, 17 December 2023 (UTC)
- So that times before the epoch can be stored. David Malone (talk) 13:57, 17 December 2023 (UTC)
- Things existed before 1970. People's birthdates, for a quite common example. ~2025-35601-84 (talk) 11:08, 22 November 2025 (UTC)
"Year 2068 problem" listed at Redirects for discussion
[edit]
The redirect Year 2068 problem has been listed at redirects for discussion to determine whether its use and function meets the redirect guidelines. Readers of this page are welcome to comment on this redirect at Wikipedia:Redirects for discussion/Log/2025 December 20 § Year 2068 problem until a consensus is reached. Vestrian24Bio 13:16, 20 December 2025 (UTC)
Shouldn't the overflow happen slightly earlier?
[edit]I calculated the date and time by hand and came up with January 18 2038 at 15:28:30 UTC. I could be wrong, though.
Leuchar55 (talk) 03:23, 2 June 2026 (UTC)
- Actually, I did the math again and ended up at Jan 18 2038 at 3:14:07 UTC. A day earlier.
- Leuchar55 (talk) 03:27, 2 June 2026 (UTC)
- So, there are 68 years and 17 of them are leap years and you get 18 full days in 2038. Each day is 86400 seconds long (except leap seconds). Then you get 3 full hours, 14 full minutes and 7 seconds in Jan 19th. You can check that this is zero:
- (365*68+17+18)*86400 + 3*3600 + 14*60 + 7 - 2147483647
- David Malone (talk) 10:59, 2 June 2026 (UTC)
Year 2000
[edit]@Canavalia: Please share your source that the Year 2000 problem is due to 32-bit time representation. TarkusABtalk/contrib 04:21, 31 August 2026 (UTC)
- You're parsing the sentence wrong. "The problem...arises from the choice to use only 32-bit ..." refers to the 2038 bug, not the Y2K bug. As to the citation needed, it is in the article: "Unix time has historically been encoded as a signed 32-bit integer, ..." Canavalia (talk) 05:04, 31 August 2026 (UTC)
- Oh my, I was reading it wrong. So, so sorry! TarkusABtalk/contrib 05:18, 31 August 2026 (UTC)
Categories:
- B-Class Time articles
- Mid-importance Time articles
- B-Class Computing articles
- Low-importance Computing articles
- B-Class software articles
- Low-importance software articles
- B-Class software articles of Low-importance
- All Software articles
- B-Class Computer science articles
- Low-importance Computer science articles
- All Computing articles