Re: 2048 bug
Re: 2048 bug
- Subject: Re: 2048 bug
- From: Nick Zitzmann <email@hidden>
- Date: Mon, 13 Jul 2009 12:29:27 -0600
On Jul 13, 2009, at 12:16 PM, Esteban Bodigami wrote:
cann't we just count the minutes after the 1st of January of 1970
instead of seconds after it?
...it is a more sane way (IMO) to solve it than passing from the
bits in which it is counted and therefore DOUBLING that variable.
1. It's 2038, not 2048. See <http://en.wikipedia.org/wiki/Year_2038_problem
>
2. Your suggestion would blow away compatibility with every shipping
application that measures time in seconds instead of minutes.
3. It's already fixed in the 64-bit libraries. time_t on 64-bit will
not become a problem for the next 292 billion years, by which point
you probably won't be using the computer you're currently using...
Nick Zitzmann
<http://www.chronosnet.com/>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
| References: | |
| | >2048 bug (From: Esteban Bodigami <email@hidden>) |