C meeting is over. C23 added: • Hacker News Board

Re: C meeting is over. C23 added:

#361

Post by loeg » Tue, Feb 22, 2022, 12:37 AM UTC

rossy wrote: post #187

sys_64738 wrote: post #124

Does anybody bother about the stuff after C99?

MSVC just got C11 support a little over a year ago, so you won't see many big cross-platform projects using it yet, unfortunately. Some projects can optionally use C11 stdatomic.h and stdalign.h to replace old OS and compiler-specific extensions, but most of them still keep fallback code in case C11 isn't available.

You could also use GCC's mingw platform to target windows, which supports all the same modern C features GCC does for other targets.

Re: C meeting is over. C23 added:

#362

Post by DrMeepster » Tue, Feb 22, 2022, 4:58 AM UTC

pkrumins wrote: post #113

drran wrote: post #108

Earlier quoted context omitted.

Majority of CVE's are because of C memory model, which is fixed in modern languages. C memory model is the constant source of vulnerabilities, thus it better to write new code in a memory safe language, like Rust.

Rust is a syntax error, not a programming language.

what does this mean? It sounds like you tried to make a funny programming insult, but it fell flat if that's what you were going for

Re: C meeting is over. C23 added:

#363

Post by pornel » Wed, Mar 02, 2022, 7:12 PM UTC

nec4b wrote: post #220

coldtea wrote: post #197

Earlier quoted context omitted.

And he was right. He didn't mean it as a statement of fact (which would be wrong, and he already knew it).

No he was definitely wrong. Ask any C developer. His comment: https://news.ycombinator.com/item?id=20828974

When I complain C's portability sucks, because it can't do anything useful without a ton of ifdefs, people tell me it's not a problem, I should just use POSIX.

https://twitter.com/rygorous/status/1224413742667988992