Re: Support for tv_sec=-1 (one second before the epoch) timestamps?

[Taylor R Campbell <campbell+netbsd-tech-kern%mumble.net@localhost>]

> Date: Sat, 15 Dec 2018 10:30:13 +0100
> From: theo4490%borm.org@localhost
> 
> 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.