Bruno Haible <[EMAIL PROTECTED]> writes: > Paul Eggert wrote: >> Clearly you don't write financial applications dealing with 30-year >> bonds. :-) > > So you want that 'time64_t' type to be useful specifically for financial > applications?
I was kidding! (But I'm afraid others are not: I have heard stories of people who converted to 64-bit just for this reason. Obviously their view of the world was oversimplified...) The main reason I want 64-bit time_t is so that my apps can stat any file without getting EOVERFLOW. gnulib can't easily work around that problem on 32-bit platforms, though. (I can think of a way to do it, but it'd be pretty horrible....)