Hacker News new | ask | show | jobs
by pjmlp 120 days ago
I can also analyse C and C++ code for such issues, while keeping using a mature languages ecosystem.
1 comments

If you can statically analyze c for memory safety, why did pazlo bother building fil-C?
Where did I wrote that static analysis was enough on its own?
Can you phrase that as a direct answer to my question? Trying to learn something here. Appreciate it!
I the sentence "I can also analyse C and C++ code for such issues, while keeping using a mature languages ecosystem." it is implied there are many tools that perform analysis of C and C++ code.

Some of those tools are static, others are dynamic, some require a special build, others are hybrid, others exist on all modern IDEs.

So it can be a mix of lint, clang tidy, VS analysis, Clion, ASan, USBsan, hardned runtimes, contracts (Frama-C), PVS, PurifyPlus, Insure++,....