From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <a6b42012b72b18cede04de81b48877ca@vitanuova.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] same functions everywhere
From: rog@vitanuova.com
In-Reply-To: <00c601c3189e$5901dea0$e3944251@insultant.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Date: Mon, 12 May 2003 17:48:09 +0100
Topicbox-Message-UUID: a97e0a86-eacb-11e9-9e20-41e7f4b1d025

> From: "Douglas A. Gwyn" <DAGwyn@null.net>
> > rog@vitanuova.com wrote:
> > > don't most >8bit character encodings (including unicode) provide at
> > > least one code point to represent "not a character"?
> >
> > We're not talking about character codes, but rather data
> > obtained via getc().  It could be an arbitrary binary stream.
>
> yup, getc() returns 8 bits.  it does not return unicode chars or unicode
> codespace characters.

if that's the case then doug's original objection isn't a problem, as
you're guaranteed that int has more than 8 bits, so there's always
space for a representation of EOF.

i'm slightly doubtful that the standard actually says 8 bits though.
K&R just says "returns the next character", which could mean anything.