X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Date:	Thu, 17 Sep 2009 11:30:37 -0400
From:	Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: 64-bit time_t?
Message-ID:	<20090917153037.GB14618@ednor.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<4AB21CCC DOT 8030205 AT byu DOT net>
MIME-Version:	1.0
In-Reply-To:	<4AB21CCC.8030205@byu.net>
User-Agent:	Mutt/1.5.20 (2009-06-14)
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

On Thu, Sep 17, 2009 at 05:26:04AM -0600, Eric Blake wrote:
>Is the transition to 1.7 a good time to change the ABI and offer a 64-bit
>time_t type that won't overflow in 2038?  Would we have to do the same
>sort of transition magic as was done back in 1.5 for 32-bit vs. 64-bit off_t?

Argh.  I was *just* thinking about this yesterday.

I think the answer is yes.  We can probably do some header file magic to
allow backwards contemptibility, too.

I hate making a last minute change like this now but it really is the best
time to get this done I think.  I'll take a look at how hard it would be to
do this over the weekend.

Thanks for bringing this up, Eric.

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -