Path: csiph.com!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: Tim Rentsch
Newsgroups: comp.lang.c
Subject: Re: "A diagram of C23 basic types"
Date: Tue, 08 Apr 2025 11:05:59 -0700
Organization: A noiseless patient Spider
Lines: 25
Message-ID: <86r022cyuw.fsf@linuxsc.com>
References: <87y0wjaysg.fsf@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Injection-Date: Tue, 08 Apr 2025 20:06:00 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="3be70bfd357a158f55184c1ca57022b7"; logging-data="2859686"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+7ZN3FgGrxwctqv55MOzf0HXbDdpXirys="
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.4 (gnu/linux)
Cancel-Lock: sha1:nzWpsUOVo5xtaovA6ynf1dOKqm0= sha1:m/KePpeBnTJ2vFOWTQPnYQjK3jw=
Xref: csiph.com comp.lang.c:392212
scott@slp53.sl.home (Scott Lurndal) writes:
> bart writes:
>
>> On 08/04/2025 15:57, David Brown wrote:
>>
>>> On 08/04/2025 15:32, bart wrote:
>>
>> [1] Maybe _t names are reserved, but this:
>>
>> typedef struct {int x,y;} uint64_t;
>
> 7.34.15 Integer types
>
> Typedef names beginning with int or uint and ending with _t are potentially
> reserved identifiers and may be added to the types defined in the
> header. Macro names beginning with INT or UINT and ending with _MAX, _MIN,
> _WIDTH, or _C are potentially reserved identifiers and may
> be added to the macros defined in the header.
It would be better if it had been explained that these statements
are not currently among the requirements given by the C standard,
but only advisories listed in the "Future Directions" section.
Names like uint64_t are not reserved, even in the not-yet-ratified
draft C standard.