3 ms·
The problem is you must keep all those "misfeatures" in the back of your head when trying to code "in the modern way". If you'd really try hard to ignore them,
by akavel 10y ago
The problem is you must keep all those "misfeatures" in the back of your head when trying to code "in the modern way". If you'd really try hard to ignore them, they'll just show up now and then and wreak havoc, sprinkled with some bitter undefined behavior topping.
As a related question: I seem to vaguely recall some mention by someone on HN, that somebody is trying to get some kind of "safe/strict blocks" markers into C++ (or some compiler? I have the feeling it was to be MSVCpp?), where "misfeatures"* would be disabled. Is anybody aware of something like this? Or was that just a beautiful dream I had?
* -- for some unknown definition of "misfeatures"
- DennisP 10y agoSounds like someone could make a decent language by just removing all the old misfeatures from C++ and calling it something new. You could argue that anyone who wants that is already on Rust or whatever, but I bet there are plenty of people who like modern C++ and don't necessarily like Rust.
- akavel 10y agoAs to the "related question", see answer I got in a related subthread here: https://news.ycombinator.com/item?id=13277071 https://news.ycombinator.com/item?id=13277071 That's probably what created my vague memories.