Groups | Search | Server Info | Keyboard shortcuts | Login | Register


Groups > comp.lang.c > #392924

Re: "A diagram of C23 basic types"

From Tim Rentsch <tr.17687@z991.linuxsc.com>
Newsgroups comp.lang.c
Subject Re: "A diagram of C23 basic types"
Date 2025-04-27 12:05 -0700
Organization A noiseless patient Spider
Message-ID <86selt8lxv.fsf@linuxsc.com> (permalink)
References <87y0wjaysg.fsf@gmail.com> <20250403150210.000020f8@yahoo.com>

Show all headers | View raw


Michael S <already5chosen@yahoo.com> writes:

> On Wed, 02 Apr 2025 16:59:59 +1100
> Alexis <flexibeast@gmail.com> 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.

Back to comp.lang.c | Previous | NextNext in thread | Find similar


Thread

Re: "A diagram of C23 basic types" Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-04-27 12:05 -0700
  Re: "A diagram of C23 basic types" Michael S <already5chosen@yahoo.com> - 2025-04-28 16:27 +0300
    Re: "A diagram of C23 basic types" BGB <cr88192@gmail.com> - 2025-04-29 13:38 -0500
    Re: "A diagram of C23 basic types" Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-05-06 15:06 -0700

csiph-web