Path: ...!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: Sun, 27 Apr 2025 12:05:16 -0700 Organization: A noiseless patient Spider Lines: 23 Message-ID: <86selt8lxv.fsf@linuxsc.com> References: <87y0wjaysg.fsf@gmail.com> <20250403150210.000020f8@yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Date: Sun, 27 Apr 2025 21:05:16 +0200 (CEST) Injection-Info: dont-email.me; posting-host="dc2911ce881fc369ab336d464007b401"; logging-data="1512646"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18TsxMe7rW256Av2kx5LxXMNz36TpuwTVQ=" User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.4 (gnu/linux) Cancel-Lock: sha1:DHK7vlSk0dHqX9dNGEgihaRGAJA= sha1:mgQkJNV+ztFjz8N7d3bsxwgTqnw= Bytes: 2075 Michael S writes: > On Wed, 02 Apr 2025 16:59:59 +1100 > Alexis wrote: > >> Thought people here might be interested in this image on Jens >> Gustedt's blog, which translates section 6.2.5, "Types", of the C23 >> standard into a graph of inclusions: >> >> https://gustedt.wordpress.com/2025/03/29/a-diagram-of-c23-basic-types/ > > That's a little disappointing. > IMHO, C23 should have added optional types _Binary32, _Binary64, > _Binary128 and _Binary256 that designate their IEEE-754 namesakes. > Plus, a mandatory requirement that if compiler supports any of IEEE-754 > binary types then they have to be accessible by above-mentioned names. I see where you're coming from, but I disagree with the suggested addition; it simultaneously does too much and not enough. If someone wants some capability along these lines, the first step should be to understand what the underlying need is, and then to figure out how to accommodate that need. The addition described above creates more problems than it solves.