Re: 64/32/16bit curl_off_t for DJGPP and WATCOMC
Date: Tue, 3 Jun 2008 13:41:28 +0100
Gisle Vanem wrote:
> AFAICS this boils down to whether djgpp/OW can support >2GB files
> or not. Since neither of them have a 64-bit fseek() function they cannot
> handle huge files. True or false? If so, curl_off_t should be a 'unsigned
> (which maps to 16 or 32-bit depending on model (small/large/flat))).
Historically, before the invention of off_t, long was used for file
offsets not int. Is DOS lseek/fseek using int or long?
Received on 2008-06-03