News for hackers. Stuff that matters.
Re:Moving to a provenance-aware memory object model for C: p... by pjmlp on Sunday April 14, 2019 @01:22PM (#19660536)
Contracts, static analysis is still in infancy (clippy vs PVS-Studio).

While C's copy-paste compatibility is C++ security story Achilles heel, there is still quite a lot that can be used for writing safer code.

Re:Moving to a provenance-aware memory object model for C: p... by littlestymaar on Monday April 15, 2019 @09:22AM (#19665077)
As far as you only use safe Rust, static analysis is in a way better shape than C++, just because C++ has nothing as powerful as the borrow checker.
Re:Moving to a provenance-aware memory object model for C: p... by pjmlp on Monday April 15, 2019 @04:15PM (#19668509)
Google and Microsoft are working on adding one to clang and Visual C++ static analysers.

https://herbsutter.com/2018/09/20/lifetime-profile-v1-0-post...

Re:Moving to a provenance-aware memory object model for C: p... by littlestymaar on Tuesday April 16, 2019 @02:49AM (#19671635)
And it will probably be incomplete because C++ hasn't be designed with it in mind (How do you avoid shared mutability when everything is mutable by default ?).

Yet, this is good to see C++ trying to catch-up. (And if it's catching up, it means Rust is ahead in terms of static analysis ;)