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] |
On 1/7/19 2:17 PM, Joseph Myers wrote:
What do you propose instead? Mention int64_t and uint64_t only?Programs and libraries should use types such as off_t, and arrange to be built with _FILE_OFFSET_BITS=64, which would make them unaffected by a future change to the default.
+1. GNU applications have been doing this for nearly two decades. It's by far the best approach for free software.
I suppose I should start adding "#define _TIME_BITS 64" to GNU applications, to future-proof them so that they will take advantage of 64-bit time_t on 32-bit platforms the instant that glibc starts publishing it. Are we definitely going to use this as the feature-test macro, or is it still possible that we'll use something else?
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |