From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <07ceecfd621281a30ced4eb9226e0c24@hamnavoe.com>
To: 9fans@9fans.net
From: Richard Miller <9fans@hamnavoe.com>
Date: Mon,  3 Jun 2013 20:09:33 +0100
In-Reply-To: <9fd46f174ab35243e649a8cec6705de6@gmx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] gmtime() ulong
Topicbox-Message-UUID: 62a26604-ead8-11e9-9d60-3106f5b1d025

I can't mind-read the intention of the change, but the effect
is to do unsigned div/mod instead of signed.  This allows the
time value to be treated as an unsigned 32-bit number, so we
should be looking at a 2106 problem not a 2038 problem.

Unfortunately while gmtime() is right, asctime() is getting
its centuries in a twist:

term% date 4070930400
Thu Jan  1 06:00:00 GMT 2099
term% date 4102466400
Fri Jan  1 06:00:00 GMT 2000