Re: [Hamlib-developer] Year 2038 issues

[C. v. W. <van...@ch...>]

> >time_t being 32 bit.
> That complacency is the problem. Is there a defined 64bit time type in C? 

Of course there is int64_t in stdint.h, but I do not like that type
since there is no printf editor for that. But this is not the 
problem:

As a programmer, you cannot influence what type time_t actually is,
but you can easily determine the type behind with sizeof().

I believe that the assumption

sizeof(time_t) = sizeof(long) = sizeof(void *)

will hold for the forseeable future just for supporting
code of lazy programmers (there is no *need* to have
the same size for these), so I guess there will be 
*something* done for 32-bit systems, e.g. internally
referencing this to 1. Jan. 2000, but this remains to
be seen.

I remember well all the cassandras warning for the „Y2K“
proble - - and nothing happened.

Yours,

Christoph DL1YCF