This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [RFC 1/7] y2038: Introduce struct __timespec64
On 3/28/19 9:19 AM, Joseph Myers wrote:
>> In this case explicit 64 bit type is used (__ino64_t).
> Yes, consistency with that is an argument for having __time64_t in the
> installed headers
But the two cases are not consistent. Glibc exposes the type ino64_t to
user code, because ino_t is part of the file API and Glibc attempts to
support mixed-mode 32-bit programs that use both 32-bit ino_t and 64-bit
ino64_t in the same program.
> There should not, however, be a public interface time64_t
Yes, and that's why the two cases are not consistent. We're planning to
do time_t differently: we are not attempting to support mixed-mode user
code, so there is no need to export either __time64_t or time64_t to
user code.