At 05:13 PM 3/18/2003, Branko Čibej wrote: >[EMAIL PROTECTED] wrote: > >>brane 2003/03/18 15:10:15 >> >> Modified: include apr.hw apr.hnw apr.h.in >> . configure.in CHANGES >> Log: >> Define a printf format and format length for apr_uint64_t. >> Also define APR_INT64_T_FMT_LEN on Windows and Netware; Unix already >> defines that symbol. >> >[snip] > >> int64_t_fmt='#define APR_INT64_T_FMT "Ld"' >> int64_t_fmt_len='#define APR_INT64_T_FMT_LEN 2' >> + uint64_t_fmt='#define APR_UINT64_T_FMT "Lu"' >> + uint64_t_fmt_len='#define APR_UINT64_T_FMT_LEN 2' >> int64_value="long double" >> long_value="long double" >> > >Could someone please check if I'm doing the right thing here? Using long >doubles for 64-bit ints seems totally weird to me...
Agreed, long is a modifier. A "long" is really shorthand for "long int". double is a floating point type, so long double implies large floating point values to me. longlong makes much more sense. Bill
