Hi,
>> I just discovered, to my dismay, that size_t is only 32 bits, even on
>> 64-bit processors. Is there a particular pressing reason for this? A
>> quick investigation reveals that even dd(1) is affected -- this is IMO
>> not good.
>
> You are wrong.
>
> limits.h:#define SIZE_T_MAX ULONG_MAX /* max value for a size_t (historic) */
Okay, I don't have a 64-bit machine running OpenBSD to check -- but is 'long'
64-bits on those? In that case I am indeed wrong.
>> I'd suggest, given modern file sizes, that we bump it to 64 bits on all
>> platforms. Comments?
>
> No way.
Can I trouble you for an explanation?
--schaafuit.
