From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <78ef64122fed7daa18548b4984d01a8b@quanstro.net>
From: erik quanstrom <quanstro@quanstro.net>
Date: Wed, 17 May 2006 22:06:32 -0500
To: 9fans@cse.psu.edu
Subject: Re: [9fans] strangely typed functions in standard library
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: 51dfb1e8-ead1-11e9-9d60-3106f5b1d025

while this is true, i believe that the real reason for this is that
on a >=32-bit machine, an ushort can just be declared
to be a long by the compiler whereas the compiler must emit 
instructions to convert a long to an unsigned short.

- erik

On Tue May 16 10:10:37 CDT 2006, 0xef967c36@gmail.com wrote:
> On 5/16/06, Matt Stewart <rotaerk1@gmail.com> wrote:
> > The following functions are described as accepting a Rune, but instead
> > the parameters are of type long.  Why?
> >
> > int runelen(long);
> > char *utfrune(char *, long);
> > char *utfrrune(char *, long);
> 
> full unicode is 32 bit, even if plan9 (afaik)
> supports only characters in the BMP.