| delorie.com/archives/browse.cgi | search | 
| X-Authentication-Warning: | delorie.com: mail set sender to djgpp-bounces using -f | 
| X-Authentication-Warning: | envy.delorie.com: dj set sender to dj AT delorie DOT com using -f | 
| From: | DJ Delorie <dj AT delorie DOT com> | 
| To: | djgpp AT delorie DOT com | 
| Subject: | Re: 64-bit time_t type in DJ 2.05? | 
| In-Reply-To: | <t50lrd$joh$1@dont-email.me> (djgpp@delorie.com) | 
| Date: | Thu, 05 May 2022 13:09:09 -0400 | 
| Message-ID: | <xny1zfsy8a.fsf@envy.delorie.com> | 
| MIME-Version: | 1.0 | 
| Errors-To: | nobody AT delorie DOT com | 
| X-Mailing-List: | djgpp AT delorie DOT com | 
| X-Unsubscribes-To: | listserv AT delorie DOT com | 
"Frank Sapone (fhsapone AT windstream DOT net) [via djgpp AT delorie DOT com]" <djgpp AT delorie DOT com> writes: > Does DJGPP support some sort of 64-bit time_t type? No. We actually considered this back when we were writing the 2.0 C library, and decided that (1) it would break too many programs (then), and (2) if anyone was still using MS-DOS in 2038, they could fix it ;-) We also considered an unsigned time_t, which moves the problem to 2164, but that would have broken other programs.
| webmaster | delorie software privacy | 
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |