News for hackers. Stuff that matters.
Re:A Usable C++ Dialect That Is Safe Against Memory Corruption by fjsolwmv on Thursday March 15, 2018 @06:43PM (#16597111)
The compiler shouldn't rejected UB, it should define all behavior, and reject all code constructs that can't have behavior fully defined (like accessing raw pointers as arrays, so bounds- checking is impossible). It can throw an exception on null de-reference at runtime. That's slow, but safe.
Re:A Usable C++ Dialect That Is Safe Against Memory Corruption by adrianN on Friday March 16, 2018 @01:47AM (#16598893)
Slow but safe is not why people choose C++ for their software.
Re:A Usable C++ Dialect That Is Safe Against Memory Corruption by wruza on Friday March 16, 2018 @05:14AM (#16599468)
There is a compiler option for that, just run javac alias instead of g++