From: "Lluís Batlle i Rossell" <viriketo@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] strangely typed functions in standard library
Date: Sat, 20 May 2006 00:49:20 +0200 [thread overview]
Message-ID: <446E4B70.6060901@gmail.com> (raw)
In-Reply-To: <87f034ae0605152003x4d8ee664o4bef08473c10eef6@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 647 bytes --]
Matt Stewart 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);
>
From History in this wikipedia page (http://en.wikipedia.org/wiki/UTF-32):
UCS-4 is sufficient to represent all of the Unicode code space, which
has 1114112 (= 2^20+2^16) code points and therefore requires only up to
hexadecimal 10FFFF. Some people consider it wasteful to reserve such a
large code space for mapping a relatively small set of code points, so a
new encoding form, UTF-32, was proposed.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3311 bytes --]
next prev parent reply other threads:[~2006-05-19 22:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-16 3:03 Matt Stewart
2006-05-16 11:40 ` Martin Neubauer
2006-05-16 15:09 ` R
2006-05-19 22:49 ` Lluís Batlle i Rossell [this message]
2006-05-19 22:43 ` quanstro
2006-05-18 3:06 erik quanstrom
2006-05-18 9:21 ` Bruce Ellis
2006-05-19 4:43 ` quanstro
2006-05-19 5:03 ` geoff
2006-05-19 12:43 ` Joel Salomon
2006-05-19 13:03 ` Victor Nazarov
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=446E4B70.6060901@gmail.com \
--to=viriketo@gmail.com \
--cc=9fans@cse.psu.edu \
/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).