Year 2038 problem

[Marco Atzeri]

On 20/11/2015 12:30, Richard Earnshaw wrote:
> On 20/11/15 10:53, Clemens Ladisch wrote:
>>
>>> one can push out the problem another 70 years with no speed or size
>>> penalty, at the small cost of not being able to represent dates before
>>> 1970.
>>
>> That cost probably is not so small.
>>
>> And do you really want to _create_ a year 2106 problem?
>>
>>
>> Regards,
>> Clemens
>>
>
> time_t is a signed type, so with a 32-bit time_t we only have a positive
> range of 68 years when counting in seconds.  1970 + 68 years = 2038.  I
> don't know where you get the 1900 from.

it is in reality  13th Dec 1901.

1970-68 = 1902

Nice counter on:
https://en.wikipedia.org/wiki/Year_2038_problem

Regards
Marco