Path: ...!feed.opticnetworks.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Tim Rentsch <tr.17687@z991.linuxsc.com>
Newsgroups: comp.lang.c
Subject: Re: "undefined behavior"?
Date: Tue, 18 Jun 2024 17:23:09 -0700
Organization: A noiseless patient Spider
Lines: 8
Message-ID: <86frt9ixw2.fsf@linuxsc.com>
References: <666a095a$0$952$882e4bbb@reader.netnews.com> <v4d4h5$1rc9e$1@dont-email.me> <877cet7qkl.fsf@nosuchdomain.example.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Injection-Date: Wed, 19 Jun 2024 02:23:09 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="fa54ab77d267afe6c3d864a61670dc2b";
	logging-data="1657039"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18ttqKxhcyCDatcJjEzfHRbcT4s8z08qKY="
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.4 (gnu/linux)
Cancel-Lock: sha1:DnKKXRsV+zL1p98163vyV6Cqo04=
	sha1:Mp8x5uODfOt9JpTcDIGM8brHuCc=
Bytes: 1331

Keith Thompson <Keith.S.Thompson+u@gmail.com> writes:

> (I'd like to a future standard require plain char to be unsigned,
> but I don't know how likely that is.)

It seems unnecessary given that the upcoming C standard
is choosing to mandate two's complement for all signed
integer types.