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 10:25 AM, Joseph Myers wrote:
>
> I don't think we should be particularly concerned by what __* names are
> visible to user code; the visibility of such names is simply a side-effect
> of how the C language works.
Hmm, well, our opinions differ, as I've seen too many people abusing the
C-language rules and would rather avoid these problems when it's easy,
as it is here.
However, as long as __time64_t and __time_t are not visible to user code
when _TIME_BITS=64, this will address most of my own practical concerns
and should be OK as a compromise.
> They should be present, or not, however is
> convenient for implementing and maintaining the installed headers (which
> includes keeping those headers consistent between different *_t typedefs
> in most cases).
My impression is that it will be more convenient to put __time64_t in a
private header, to help remind maintainers that that the situation with
time_t is different, as there is no intent to support mixed-mode user
code with time_t. But I understand if your opinion differs.