Year 2038 Problem
The original Unix timestamp datatype (time_t) stores a date and time as a signed 32-bit integer representing the number of seconds since 1 January 1970. During and after 2038, this number will exceed 231 − 1, the largest number representable by a signed 32-bit integer, causing the Year 2038 problem (also known as the Unix Millennium bug, or Y2K38). To solve this problem, many systems and languages have switched to a 64-bit timestamp, or supplied alternatives which are 64-bit.
Read more about this topic: Y2K Problem, Programming Problem, Date Bugs Similar To Y2K
Famous quotes containing the words year and/or problem:
“Listen, that’s the one that done it. The dusters. They started it anyways. Blowin’ like this year after year. Blowin’ the land away. Blowin’ the crops away. Blowin’ us away now.”
—Nunnally Johnson (1897–1977)
“Most childhood problems don’t result from “bad” parenting, but are the inevitable result of the growing that parents and children do together. The point isn’t to head off these problems or find ways around them, but rather to work through them together and in doing so to develop a relationship of mutual trust to rely on when the next problem comes along.”
—Fred Rogers (20th century)