3 ms·
> They're a good idea, but not a substitute for knowing the rules. It's a good thing no one made that claim, then. The whole point is that were seeing people
by chipdart 2y ago
> They're a good idea, but not a substitute for knowing the rules.
It's a good thing no one made that claim, then.
The whole point is that were seeing people in this thread making all sort of wild claims on how it's virtually impossible to catch these errors in C++ even though back in reality there are a myriad of static analysis and memory checker tools that do just that.
Your average developer also knows how to type in a space character but still it's a good idea to onboard linters and automatic code formatters.
- eddd-ddde 2y agoYou made the claim > Why? What's wrong with using one of the many static code analysis tool to tell you about them if/when they appear? You clearly pose static analysers as an alternative to understanding UB. You still need to understand how things work.
- rcxdude 2y agoIt's not impossible to catch those errors in C and C++. In fact, every time you run a new tool against a large C or C++ codebase you will find new ones. What none of these tools do is catch all the issues, as demonstrated by the fact that people keep finding new ones.