Re: [9fans] tarfs & 2GB limit

[Paul Lalonde <plalonde@telus.net>]

And though it doesn't feel very plan9ish, I'm now going to sing the  
virtues of <inttypes.h>.
having standard sized integer types (int32_t, uint32_t, et al), along  
with intptr_t (an int that can hold any pointer) just makes too much  
sense, and adds information for the reader: you can be pretty sure  
you're mucking with addressing in an intptr_t; and that you need 16  
bits with a uint16_t.

If only converting old code with sizeof(int) == sizeof(int32_t) and  
sizeof(void *) == sizeof(int) assumptions weren't so time consuming :-(

Paul

On 13-Jan-06, at 4:33 PM, Devon H. O'Dell wrote:

> 2006/1/13, C H Forsyth <forsyth@vitanuova.com>:
>> 51c52
>> <               f.addr = (void*)(blkno+1);
>> ---
>>>               f.addr = (void*)((ulong)blkno+1);
>>
>> it will be cleaner to have fileinf declare
>>         union {
>>                 void*   addr;
>>                 ulong   blockno;
>>         };
>> (or whatever is required) and use the right member of the union.
>> just say `no' to converting between void* and integers, when it's  
>> not essential.
>
> Yes, this happens wayyyy too often. Since sizeof(int) and sizeof(void
> *) are not the same on AMD64, there's even more reason to try to avoid
> it.
>
> --Devon