News for hackers. Stuff that matters.
Re:Why undefined behavior may call a never-called function by zokier on Sunday September 24, 2017 @03:14PM (#15326025)
> Unfortunately, I'm also sure that we don't have the time to do it.

And that really is the crux of the issue. Despite the significant amount of discussion around the problems of C UB, there is precious little work being done to actually "solve" the problems.

https://blog.regehr.org/archives/1287

> Since we published the Friendly C proposal, people have been asking me how it’s going. This post is a long-winded way of saying that I lost faith in my ability to push the work forward. However, I still think it’s a great idea and that there are people besides me who can make it happen.

Re:Why undefined behavior may call a never-called function by unrealhoang on Sunday September 24, 2017 @07:28PM (#15327060)
I believe creating safer languages like: Go, Rust, Swift are also attempts to solve the problem. It doesn’t need to be C/C++
Re:Why undefined behavior may call a never-called function by zokier on Monday September 25, 2017 @02:46AM (#15328498)
Agreed on both points. Still I think there would be room for a more C like language in the market. Rust in all its greatness is also very complex, gaining more of a C++ feeling to it. I don't think any of the new languages (including modern C) manage to replicate the feeling of simplicity and transparency of k&r c.