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=MAILING_LIST_MULTI, RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 1855 invoked from network); 15 May 2020 21:53:47 -0000 Received: from minnie.tuhs.org (45.79.103.53) by inbox.vuxu.org with ESMTPUTF8; 15 May 2020 21:53:47 -0000 Received: by minnie.tuhs.org (Postfix, from userid 112) id 67E139C96A; Sat, 16 May 2020 07:53:43 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id 5D26A9C677; Sat, 16 May 2020 07:53:29 +1000 (AEST) Received: by minnie.tuhs.org (Postfix, from userid 112) id 451319C677; Sat, 16 May 2020 07:53:28 +1000 (AEST) Received: from minun.buric.co (minun.buric.co [51.15.8.196]) by minnie.tuhs.org (Postfix) with ESMTP id E10DA9C668 for ; Sat, 16 May 2020 07:53:25 +1000 (AEST) Received: by minun.buric.co (Postfix, from userid 1000) id C010735C1037; Fri, 15 May 2020 23:53:22 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by minun.buric.co (Postfix) with ESMTP id B609F35C1036; Fri, 15 May 2020 17:53:22 -0400 (EDT) Date: Fri, 15 May 2020 17:53:22 -0400 (EDT) From: Steve Nickolas X-X-Sender: mary@sd-119843.dedibox.fr To: Richard Tobin In-Reply-To: <20200515213138.8E0F72D2D71E@macaroni.inf.ed.ac.uk> Message-ID: References: <20200515213138.8E0F72D2D71E@macaroni.inf.ed.ac.uk> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed 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: tuhs@tuhs.org Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" On Fri, 15 May 2020, Richard Tobin wrote: >> Isn't it nonstandard (although I am aware of some compilers that do it) to >> default the type of char to unsigned? > > No. > > "The implementation shall define char to have the same range, > representation, and behavior as either signed char or unsigned char." > - C99 > > (Technically it's a separate type from both of them.) > > -- Richard > > Huh. I thought all integers were supposed to be signed by default regardless of their size. o.o That said, I do use "int c; ... c=fgetc(stdin);" or the like in my code. -uso.