Hi there, On Tue, 12 Nov 2024, Frantisek Rysanek via Freedos-user wrote:
... You are possibly safe on a modern 32bit platform as well, because the C type may be #defined with explicit length ...
Some libraries switched from signed to unsigned 32-bit integers for time_t which kicks the can down the road until 2106, see for example glibc v2.40: https://github.com/bminor/glibc/blob/master/NEWS Again for example for glibc you can use #define _TIME_BITS=64 to get 64 bit time_t values and then recompile. 64 bit time values will certainly outlast our planet, and likely outlast the universe. https://www.gnu.org/software/gnulib/manual/html_node/Avoiding-the-year-2038-problem.html
... file timestamps in FAT are subject to a problem with year 2108. ...
Note also, DOS API calls which manipulate the date are limited to 2099: https://en.wikipedia.org/wiki/Time_formatting_and_storage_bugs#Year_2100 I don't know what, if anything, anyone can do about that.
... What a pity. I myself will have overflowed by then.
Ditto. :( -- 73, Ged. _______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
