News for hackers. Stuff that matters.

A comment on Let’s Stop Bashing C. Parent comment

Re:Let’s Stop Bashing C by ekidd on Friday December 02, 2016 @11:56AM (#13090216)
djb, who is famous for being an exceptionally talented and careful C programmer, summarized these issues better than I ever could: https://groups.google.com/forum/m/#!msg/boring-crypto/48qa1k...

Yes, every time a C program relies on undefined behavior, it's a bug. And as djb observed, virtually all non-trivial C programs contain these bugs. This is the core of my argument.

Yes, we could rely on C programmers never making mistakes. But it would be better to design languages with no undefined behavior.

[ Parent | on HN ]
Re:Let’s Stop Bashing C by ArkyBeagle on Friday December 02, 2016 @07:31PM (#13093491)
His idea of flagging UB at compile-time is pretty obvious - I have to wonder what the economics are that it hasn't been an emphasis at all, all these years.

I do get a facial tick when people say "all significant C programs use (or contain) UB." It's never been necessary and it's always been shameful.

[ Parent | on HN ]
Re:Let’s Stop Bashing C by RUG3Y on Friday December 02, 2016 @12:18PM (#13090405)
As someone that doesn't HAVE to use C, this weirdness is one of the things that makes it interesting to me. I'm sure I'm the exception here, and if I were writing lots of C code for big projects I'd feel otherwise.
[ Parent | on HN ]