From: "Joel C. Salomon" <joelcsalomon@gmail.com>
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 21:38:40 -0500 [thread overview]
Message-ID: <7871fcf50802261838k1312b9doc979c4a065c93e6b@mail.gmail.com> (raw)
In-Reply-To: <FD14802E-AB9F-4C48-9DD0-B085346E33DA@mac.com>
On Tue, Feb 26, 2008 at 4:21 PM, Pietro Gagliardi <pietro10@mac.com> wrote:
> And it's wonderful that the C standard defines a character literal as
> so:
But it leaves the meaning of a literal like 'abcd' up to the compiler.
I did something very perverse -- but 'legal' -- in the compiler I
started writing for class...
Also recall that sizeof('c') == sizeof(int). I suspect, though, that
literals like 'abcd' are left from the B (word-addressable, not
byte-addressable) days.
A quick check of /sys/src/cmd/cc/lex.c shows that kenc disallows such horrors.
--Joel
next prev parent reply other threads:[~2008-02-27 2:38 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
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 [this message]
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=7871fcf50802261838k1312b9doc979c4a065c93e6b@mail.gmail.com \
--to=joelcsalomon@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).