[TUHS] v7 K&R C

Ronald Natalie ron at ronnatalie.com
Sun May 17 07:59:45 AEST 2020

The issue is making char play double duty as a basic storage unit and a native character.
This means you can never have 16 (or 32 bit) chars on any machine that you wanted to support 8 bit integers.

> On May 15, 2020, at 7:34 PM, Steffen Nurpmeso <steffen at sdaoden.eu> wrote:
> ron at ronnatalie.com wrote in
> <077a01d62b08$e696bee0$b3c43ca0$@ronnatalie.com>:
> |Char is different.  One of the silly foibles of C.    char can be signed or
> |unsigned at the implementation's decision.
> And i would wish Thompson and Pike would have felt the need to
> design UTF-8 ten years earlier.  Maybe we would have a halfway
> usable "wide" character interface in the standard (C) library.
> --steffen
> |
> |Der Kragenbaer,                The moon bear,
> |der holt sich munter           he cheerfully and one by one
> |einen nach dem anderen runter  wa.ks himself off
> |(By Robert Gernhardt)

More information about the TUHS mailing list