←back to thread

The C23 edition of Modern C

(gustedt.wordpress.com)
515 points bwidlar | 1 comments | 15 Oct 24 16:06 UTC | HN request time: 0.207s | source
Show context
bitbasher ◴[15 Oct 24 17:31 UTC] No.41850914[source]▶
Really looking forward to #embed, once the compilers catch up. Until then, Golang.
replies(5): >>41851074 #>>41851080 #>>41851110 #>>41851215 #>>41851883 #
enriquto ◴[15 Oct 24 17:47 UTC] No.41851074[source]▶
This is not how C standards work. If it appears in the standard, it means that it is already implemented in some compilers (in that case, at least in gcc and clang).
replies(1): >>41852554 #
pjmlp ◴[15 Oct 24 20:04 UTC] No.41852554[source]▶
That isn't really how it goes, that is how it used to be up to C99.
replies(1): >>41852590 #
enriquto ◴[15 Oct 24 20:08 UTC] No.41852590[source]▶
Thanks for the correction! Do you know if there is a document from the standards body explaining the change in philosophy?
replies(2): >>41853226 #>>41853692 #
1. MathMonkeyMan ◴[15 Oct 24 21:18 UTC] No.41853226[source]▶
I've heard something along the lines of "the standard is to define facilities that will be used in most programs, and to codify widespread existing practice." That was in the context of "I don't like this proposed feature," though. This was for C++, not C.

A lot of stuff in the C++11 standard library was based on widespread use of Boost. Since then, I don't know. Also, were things like templates and lambdas implemented as compiler extensions before standardization? I don't know, but I doubt it. Maybe "we're a committee of people who will decide on a thing and we hope you like it" was always the norm in many ways.