Does anyone do anything around 2038 time_t errors?

Question

Possible duplicate:
What should we do to prepare for 2038?

I do not mean "people" in the abstract. I mean that you are doing something, and if so, then what?

I am an ancient programmer and remember when I wrote COBOL at the end of 70, telling others on my team, "you know that this will not work in 2000." To which the answer was "yes, but this system will not be used by that time in 25 years."

2038 is 28 years old.

Answer 1

I am adding a disclaimer to my software release that states: Best before 2038.

Answer 2

. !

Answer 3

, 64- . , , ISO-8601.

Answer 4

64- time_t, ( = ).

, , , , ( ).

Answer 5

The easiest way, I think, is to write software that can be easily maintained. That is, a low relationship between data models and the algorithms working on them. Most DBMSs and computer languages ​​are already designed to support this kind of abstraction.