From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu, Paul Lalonde <plalonde@telus.net>
Subject: Re: [9fans] tarfs & 2GB limit
Date: Fri, 13 Jan 2006 19:07:50 -0600 [thread overview]
Message-ID: <20060114010750.3D1973256A@dexter-peak.quanstro.net> (raw)
In-Reply-To: <CC31E981-FFE7-4F3F-9E0F-175AAE0F516C@telus.net>
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
next prev parent reply other threads:[~2006-01-14 1:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-13 14:11 cej
2006-01-13 16:41 ` erik quanstrom
2006-01-13 22:33 ` geoff
2006-01-14 0:30 ` erik quanstrom
2006-01-13 22:36 ` C H Forsyth
2006-01-13 22:43 ` geoff
2006-01-14 0:03 ` erik quanstrom
2006-01-14 0:33 ` Devon H. O'Dell
2006-01-14 0:59 ` Paul Lalonde
2006-01-14 1:07 ` erik quanstrom [this message]
2006-01-14 12:15 ` erik quanstrom
2006-01-14 18:22 ` Russ Cox
2006-01-14 21:27 ` erik quanstrom
2006-01-16 2:57 ` erik quanstrom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060114010750.3D1973256A@dexter-peak.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@cse.psu.edu \
--cc=plalonde@telus.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).