From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: Date: Thu, 22 Nov 2012 02:33:26 +0000 Message-ID: From: Charles Forsyth To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Subject: Re: [9fans] go forth and ulong no more! Topicbox-Message-UUID: dd9bdd82-ead7-11e9-9d60-3106f5b1d025 That will obviously work, and indeed I use uintmem the same way to avoid having yet another type, but that's only because that's specific to the kernel, and of little use. Otherwise, I think there's a difference between storing a pointer value in an integer, and storing a size. For one thing, many programs might use usize, but few programs (in fact) ever need uintptr. If I want to grep for pointer/integer conversions, I can grep for uintptr, but with (what I take to be) your scheme, I'll get lots of false hits, as ordinary programs might well compute with sizes. On 22 November 2012 02:15, Bruce Ellis wrote: > uintptr for size_t.