Fifth draft of the Y2038 design document

[Zack Weinberg]

On Wed, Feb 22, 2017 at 1:45 PM, Paul Eggert <eggert@cs.ucla.edu> wrote:

> I don't get the point about "a possible implementation" for struct timespec
> on little-endian vs struct timespec64 on big-endian systems. The
> implementations are identical.

I'm fairly sure this is just an error - one of the two (I don't know
which) needs to have the padding and the nanoseconds field in the
opposite order.

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*.

zw