|
|
Пишет LWN.net (![[info]](http://lj.rossia.org/img/syndicated.gif){kind=small} syn_lwnheadline)@ 2017-02-22 15:56:00 |
 |
|
 |
|
|
|
|
|
|
 |
|
 |
A draft glibc year-2038 design document
The year-2038 apocalypse is now just under
21 years away. For those who are curious about how the GNU C Library
plans to deal with this problem, there is a
draft design document out for review. "In order to avoid
duplicating APIs for 32-bit and 64-bit time, glibc will provide either one
but not both for a given application; the application code will have to
choose between 32-bit or 64-bit time support, and the same set of symbols
(e.g. time_t or clock_gettime) will be provided in both cases."
The year-2038 apocalypse is now just under
21 years away. For those who are curious about how the GNU C Library
plans to deal with this problem, there is a
draft design document out for review. "In order to avoid
duplicating APIs for 32-bit and 64-bit time, glibc will provide either one
but not both for a given application; the application code will have to
choose between 32-bit or 64-bit time support, and the same set of symbols
(e.g. time_t or clock_gettime) will be provided in both cases."
