> On Thu, Jun 05, 2008, David Schwartz wrote: > > > > > 1) All routines are based on a uint64_t to hold the seconds > since the epoch. > > So you can still easily convert to/from time_t for in-range values. > > > > Well there has been a problem on some platforms in the past which > don't have a > 64 bit integer type. The pqueue code for example was changed as a result. > > Steve.
It would be trivial to make the code revert to a 32-bit value with the exact same functions in that case. You simply create your own type that's 64-bit where possible and 32-bit where not. If it's 32-bit, you just 'ifdef' out the fixup functions and wind up using the regular time functions. You wouldn't get the benefit of being able to manipulate times past 2038 on those platforms, but you wouldn't lose anything. Sadly, making the code work with two 32-bit values and no native 64-bit type would be a bit more of a challenge. I'm not totally happy with different functionality on different platforms. Though I feel a bit better because no existing functionality would be removed in the process. DS ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager [EMAIL PROTECTED]
