←back to thread

The C23 edition of Modern C

(gustedt.wordpress.com)
397 points bwidlar | 1 comments | 15 Oct 24 16:06 UTC | HN request time: 0s | 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{3}[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. JonChesterfield ◴[15 Oct 24 22:18 UTC] No.41853692{4}[source]▶
It's a nuisance to implement the thing you want to add to the standard yourself. It's easier to ship it in the language and then complain at compiler devs that they're running behind the edge of progress.

This interacts in the obvious way with refusing to correct mistakes after the fact for fear of breaking user code.

I don't believe anyone has written a paper along the lines of "let's not bother with the existing practice part anymore", it's more an emergent feature of people following local incentive structures.