From mboxrd@z Thu Jan  1 00:00:00 1970
Mime-Version: 1.0 (Apple Message framework v753)
In-Reply-To: <62de1c2c6c8cd64152312915825615eb@plan9.bell-labs.com>
References: <62de1c2c6c8cd64152312915825615eb@plan9.bell-labs.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <FD14802E-AB9F-4C48-9DD0-B085346E33DA@mac.com>
Content-Transfer-Encoding: 7bit
From: Pietro Gagliardi <pietro10@mac.com>
Subject: Re: [9fans] awk, not utf aware...
Date: Tue, 26 Feb 2008 16:21:22 -0500
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Topicbox-Message-UUID: 6303be68-ead3-11e9-9d60-3106f5b1d025

And it's wonderful that the C standard defines a character literal as
so:

	char-literal:
		' characters '
	characters:
		character
		characters character

(or something like that)

Question, then: why do we need wchar_t/Rune?

On Feb 26, 2008, at 4:08 PM, geoff@plan9.bell-labs.com wrote:

> Plan 9 awk is an APE program, so it uses the unpronounceable ANSI
> mbtowc/wctomb functions to deal with UTF.  Thus it uses mblen rather
> than utflen or utf8len.
>