Fifth draft of the Y2038 design document

[Albert ARIBAUD]

Hi Zack,

On Wed, 22 Feb 2017 13:51:12 -0500, Zack Weinberg <zackw@panix.com>
wrote :

> Speaking of struct timespec, though, why does this spec not consider
> the possibility of changing the type of 'tv_nsec' to a new typedef,
> say nsec_t, which can vary between 32- and 64-bit modes?  Yes, this
> requires a change in POSIX (and ISO C as well now, unfortunately), but
> one that would be a good idea *anyway*.

Honestly, I think I have enough on my plate right now with GLIBC Y2038.
I don't think I'd be able to add talking to the Posix and C standards
folks about a change which may break existing code in subtle ways.

But I'm curious about replacing the implementation-defined 'long' which
an equally implementation-defined nsec_t: what would be the incentive
for C implementers to choose a definition for nsec_t other than
'typedef long nsec_t;'?

> zw

Cordialement,
Albert ARIBAUD
3ADEV