Tom Lord <xxxxxx@emf.net> writes:

> Hmm.  Well, an example of what it fails to sidestep is the issue of
> making the values representable by the C `char' type a subset of CHAR?
> It's also a fairly sorry approach to take for implementing many
> network protocols in a way that is simple, direct, "tolerant of what
> it receives".

Then what you want is a function ascii->char which maps an ascii value
to a character.  And name it that, since that's what you mean!
Nothing then prevents ebcdec->char or utf8->char or whatever else.

Thomas