LogFAQs > #932099564

LurkerFAQs, Active DB, DB1, DB2, DB3, DB4, Database 5 ( 01.01.2019-12.31.2019 ), DB6, DB7, DB8, DB9, DB10, DB11, DB12, Clear
Topic List
Page List: 1
TopicHow will we address the Year 2038 problem?
YoshitoKikuchi
12/26/19 10:50:40 PM
#1:


https://en.wikipedia.org/wiki/Year_2038_problem

The Year 2038 problem (Y2038) relates to representing time in many digital systems as the number of seconds passed since 00:00:00 UTC on 1 January 1970 and storing it as a signed 32-bit binary integer. Such implementations cannot encode times after 03:14:07 UTC on 19 January 2038. Just like the Y2K problem, the Year 2038 problem is caused by insufficient capacity of the chosen storage unit.

---
Dont be ridiculous. I think FIVE evil steps ahead
https://imgur.com/YQpeyD3
... Copied to Clipboard!
Topic List
Page List: 1