From mboxrd@z Thu Jan  1 00:00:00 1970
Mime-Version: 1.0 (Apple Message framework v753)
In-Reply-To: <E4B0530E-03CA-402B-8C6E-D98D90DBF457@mac.com>
References: <62de1c2c6c8cd64152312915825615eb@plan9.bell-labs.com>
	<FD14802E-AB9F-4C48-9DD0-B085346E33DA@mac.com>
	<1204061572.6925.14.camel@wren>
	<E4B0530E-03CA-402B-8C6E-D98D90DBF457@mac.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <1F20B1BA-05C3-4555-80DF-8107DE8140D9@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:42:24 -0500
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Topicbox-Message-UUID: 6331c3f8-ead3-11e9-9d60-3106f5b1d025

(which I have sitting next to me)

On Feb 26, 2008, at 4:40 PM, Pietro Gagliardi wrote:

> Yes. I'm too lazy to pick up my copy of the standard.
>
> On Feb 26, 2008, at 4:32 PM, Steven Vormwald wrote:
>
>> On Tue, 2008-02-26 at 16:21 -0500, Pietro Gagliardi wrote:
>>> 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?
>>
>> The definitions are (<> used to indicate non-terminals in the
>> grammar...):
>>
>> (6.4.4.4) character-constant:
>> 	' <c-char-sequence> '
>> 	L' <c-char-sequence> '
>>
>> (6.4.4.4) c-char-sequence:
>> 	<c-char>
>> 	<c-char-sequence> <c-char>
>>
>> (6.4.4.4) c-char:
>> 	any member of the source character set except the single-quote ',
>> backslash \, or new-line character
>>
>> 	<escape-sequence>
>>
>> Steven Vormwald
>> sdvormwa@mtu.edu
>>
>>
>