upvote

points

by pjmlp23 hours ago |
comments
upvoteby throw-qqqqq21 hours ago|
[-]
TIL, thanks for updating me on this!

I read Herb Sutter’s post many years ago, but didn’t know they had picked up the work again.

I see that VLAs are still not supported, which is a shame IMO, but the C-support seems much better than it used to be at least.

reply
upvoteby pjmlp18 hours ago|
parent|
[-]
They never will, as mentioned they have decided not to support what became optional in C11.

If C23 ever comes to land on MSVC, which I have my doubts given the radio silence on C support, I assume they might add the VLAs part that made it again back into C23.

reply
upvoteby uecker18 hours ago|
parent|
[-]
If you care about C, use gcc.
reply
upvoteby pjmlp17 hours ago|
parent|
[-]
As proven by industry adoption of clang, that isn't an option in many platforms.

Additionally clang is driving C extensions for safety that should have long been part of the language.

reply
upvoteby uecker15 hours ago|
parent|
[-]
IMHO gcc has better warnings and support for safety. Industry mostly wants a BSD-licensed toolchain. I could not care less.
reply
upvoteby pjmlp7 hours ago|
parent|
[-]
GCC only recently started with its safety analysers, it doesn't do C++, and isn't as customisable as clang tidy.

Additionally it lacks the language extensions Apple and Google have been adding to clang, which remains to be seen which ever get proposed to be part of the standard.

You might care less, however as mentioned there are industry relevant platforms where GCC doesn't get to play at all, thus plenty of people do care.

reply
upvoteby uecker6 hours ago|
parent|
[-]
This discussion was about C not C++. GCC also has language extensions for safety, such as the access attribute, the dynamic object size pass, and far better warnings.

Big tech cares about a lot of things of dubious value to me, the users, or developers. As a C programmer, if you want to write modern and safe C, my recommendation is to use gcc.

reply