From: Steven Vormwald <sdvormwa@mtu.edu>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] awk, not utf aware...
Date: Tue, 26 Feb 2008 16:32:52 -0500 [thread overview]
Message-ID: <1204061572.6925.14.camel@wren> (raw)
In-Reply-To: <FD14802E-AB9F-4C48-9DD0-B085346E33DA@mac.com>
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
next prev parent reply other threads:[~2008-02-26 21:32 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-26 12:18 Gorka Guardiola
2008-02-26 13:16 ` Martin Neubauer
2008-02-26 14:54 ` Gorka Guardiola
2008-02-26 20:24 ` erik quanstrom
2008-02-26 21:08 ` geoff
2008-02-26 21:21 ` Pietro Gagliardi
2008-02-26 21:24 ` erik quanstrom
2008-02-26 21:32 ` Steven Vormwald [this message]
2008-02-26 21:40 ` Pietro Gagliardi
2008-02-26 21:42 ` Pietro Gagliardi
2008-02-26 23:59 ` Steven Vormwald
2008-02-27 2:38 ` Joel C. Salomon
2008-02-29 17:00 ` Douglas A. Gwyn
2008-02-26 21:34 ` erik quanstrom
2008-02-27 7:36 ` Gorka Guardiola
2008-02-27 15:54 ` Sape Mullender
2008-02-27 20:01 ` Uriel
2008-02-28 19:06 ` [9fans] localization, unicode, regexps (was: awk, not utf aware...) Tristan Plumb
2008-02-28 15:10 ` [9fans] awk, not utf aware erik quanstrom
2008-03-03 23:48 ` Jack Johnson
2008-03-04 0:13 ` erik quanstrom
2008-02-27 9:57 erik quanstrom
2008-02-28 18:54 Aharon Robbins
2008-02-28 21:48 ` Uriel
2008-02-28 22:08 ` erik quanstrom
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=1204061572.6925.14.camel@wren \
--to=sdvormwa@mtu.edu \
--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).