On 11/7/2024 5:00 AM, michal.lyszc...@bofc.pl wrote:
Having code we know is going to crap out in the near future is kinda strange
design choice. I think you could have ignored it when there was 50 years left,
but this will happen in 14 years which is not that far for embedded systems
that can work for decades.
Just to be clear, there is no year 2038 problem in the existing code
that uses the uint32_t definition for time_t. The problem would be
introduced if we changed this to a int32_t type. We currently have a
year 2106 problem which is not so pressing. We have 82 years left.
