Path: csiph.com!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: Keith Thompson <Keith.S.Thompson+u@gmail.com>
Newsgroups: comp.lang.c
Subject: Re: K&R, 2nd edition, Brian's concerns with ``char c = EOF''
Date: Tue, 23 Nov 2021 09:43:48 -0800
Organization: None to speak of
Lines: 17
Message-ID: <87pmqqhinf.fsf@nosuchdomain.example.com>
References: <86pmqwkm7u.fsf@levado.to> <878rxjq4l9.fsf@nosuchdomain.example.com> <snfr3l$chl$1@solani.org> <87ilwjj4gl.fsf@nosuchdomain.example.com> <snj3eu$6a8$1@solani.org>
Mime-Version: 1.0
Content-Type: text/plain
Injection-Info: reader02.eternal-september.org; posting-host="b82abc4b3fdda89f0afa055b2002bcb0"; logging-data="17228"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/ARipILqaqBhPbzNIM1z98"
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux)
Cancel-Lock: sha1:FusH6fZYFyhfKqSmqJegArx6Hzw= sha1:EmJE28f3rzL7aNYf/TzZ4uf0Ttg=
Xref: csiph.com comp.lang.c:163610

Philipp Klaus Krause <pkk@spth.de> writes:
> Am 22.11.21 um 21:55 schrieb Keith Thompson:
>> but useful and non-conforming is
>> sometimes better than conforming.
>
> A 16-bit ptrdiff_t on a freestanding implementation that does not
> support objects bigger than (1 << 15) would be another common example.
> Though that is only nonconforming for C99, C11 and C17, but valid C90,
> C95 and C23.

How would it be valid C23?  The N2731 draft defines PTRDIFF_WIDTH in
<stdint.h> and requires it to be at least 17.

-- 
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
Working, but not speaking, for Philips
void Void(void) { Void(); } /* The recursive call of the void */