From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 12519 invoked from network); 16 May 2020 22:00:16 -0000 Received: from minnie.tuhs.org (45.79.103.53) by inbox.vuxu.org with ESMTPUTF8; 16 May 2020 22:00:16 -0000 Received: by minnie.tuhs.org (Postfix, from userid 112) id 85E479C5F1; Sun, 17 May 2020 08:00:12 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id C93149C5E5; Sun, 17 May 2020 07:59:51 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=pass (1024-bit key; secure) header.d=mxes.net header.i=@mxes.net header.b="uLuS46ub"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id 8DCFC9C5E5; Sun, 17 May 2020 07:59:50 +1000 (AEST) Received: from smtp-out-3.mxes.net (smtp-out-3.mxes.net [198.205.123.68]) by minnie.tuhs.org (Postfix) with ESMTPS id 0DA6D9C5E4 for ; Sun, 17 May 2020 07:59:50 +1000 (AEST) Received: from Customer-MUA (mua.mxes.net [10.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 4A6D87598D; Sat, 16 May 2020 17:59:47 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mxes.net; s=mta; t=1589666388; bh=8v1tv2NMpbj6QgCd8ytd9lyJZBAhbi0jBF0ZadZTCpE=; h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date: Message-Id:References:To; b=uLuS46ubYpNO2RSqYyi1oRGluWfUsX6RcsU4noBDZ9vmlZTaL9cbr3r0VGsG+5vsy as53ATQ6U25fBjLFkQXaf3EIs+xk6GVZTa3zDuR9Uq/sDjk1BTpFdgh7AAY0XuG8iO bE8o5lJI/cCAkyMnBgXiwN0IPPNj/0jZ1IFLasY8= Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\)) From: Ronald Natalie In-Reply-To: <20200515233427.31Vab%steffen@sdaoden.eu> Date: Sat, 16 May 2020 17:59:45 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: <5DB09C5A-F5DA-4375-AAA5-0711FC6FB1D9@ronnatalie.com> References: <20200515213138.8E0F72D2D71E@macaroni.inf.ed.ac.uk> <077a01d62b08$e696bee0$b3c43ca0$@ronnatalie.com> <20200515233427.31Vab%steffen@sdaoden.eu> To: Steffen Nurpmeso X-Mailer: Apple Mail (2.3608.80.23.2.2) X-Sent-To: Subject: Re: [TUHS] v7 K&R C X-BeenThere: tuhs@minnie.tuhs.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: The Unix Heritage Society mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: The Eunuchs Hysterical Society Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" 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 = wrote: >=20 > ron@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. >=20 > 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. >=20 > --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)