This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] Y2038: provide kernel support indication


* Albert ARIBAUD:

> - one new boolean for every new feature, which libc can read/write.
>   Reading happens every time the feature is used.
>   Writing happens very rarely, once when first first using / testing for
>   the feature (e.g. at application start), once if using the feature
>   fails (e.g. a syscall returns ENOSYS).
>
> - two accessors (getter/setter) for every new feature if it must be
>   read/set from another glibc library than libc (e.g. librt).

I'm still surprised that this is needed.  Why can't applications call
the function in question and react to a well-documented error code?

Thanks,
Florian


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]