From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu, Paul Lalonde <plalonde@telus.net>
References: <20060113164151.ED27C35076@dexter-peak.quanstro.net>
	<516c07525677816b5a69698dca337a86@vitanuova.com>
	<9ab217670601131633x7fa1f177u@mail.gmail.com>
	<CC31E981-FFE7-4F3F-9E0F-175AAE0F516C@telus.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
In-Reply-To: <CC31E981-FFE7-4F3F-9E0F-175AAE0F516C@telus.net>
Subject: Re: [9fans] tarfs & 2GB limit
Message-Id: <20060114010750.3D1973256A@dexter-peak.quanstro.net>
Date: Fri, 13 Jan 2006 19:07:50 -0600
Cc: 
Topicbox-Message-UUID: d6aee57a-ead0-11e9-9d60-3106f5b1d025

already there: from p9p has the corrispondence in u.h:

typedef uint64_t u64int;
typedef int64_t s64int;
typedef uint8_t u8int;
typedef int8_t s8int;
typedef uint16_t u16int;
typedef int16_t s16int;
typedef uintptr_t uintptr;
typedef uint32_t u32int;
typedef int32_t s32int;

Paul Lalonde <plalonde@telus.net> writes

| 
| 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