4 ms·
You can already hit these problems today. People always think about the current date, although there very valid are reasons to store future (or past) dates. Fo
by _jomo 12y ago
You can already hit these problems today. People always think about the current date, although there very valid are reasons to store future (or past) dates.
For example, if you're are a scientist you might want to calculate where planet xyz is in 100,000 years - and store that date on your computer, today.
- cs- 12y agoAnd then you would of course use a toolbox (or make one) that supports large dates, or even work with other time units (ie. D)
- perlgeek 12y agoOne doesn't have to go that far. Mortgages, life insurance, annuity assurance and the like can run for more than the mere 23 years that are between now and 2038. Heck, I won't even be retired in 2038 if things continue to work as they do now.
- _jomo 12y agoApparently it already caused trouble with AOLServer in 2006 [0] because there was a database connection timeout of 1 billion seconds which hit the 32bit limit. [0]: http://www.mail-archive.com/aolserver@listserv.aol.com/msg09844.html http://www.mail-archive.com/aolserver@listserv.aol.com/msg09...