> Date: Sat, 15 Dec 2018 10:30:13 +0100 > From: theo4...@borm.org > > Might I suggest that the obvious solution to this, and probably a host > of other issues, is to make time_t an always negative number > (negint/neglong?) and redefine the epoch as 03:14:09 UTC on Tuesday, 19 > January 2038, leaving (time-t) -1 as a special value for errors and > halting the system when the clock would overflow to (time-t) 0 > (ENOMORETIME).
A cute idea, but we already dealt with this problem a decade ago by making time_t 64-bit on every platform.
