3 ms·
For what it's worth, Apple do use a static analyser - they even wrote their own, and it's actually pretty good. If I remember correctly, it's even activated by
by antimagic 12y ago
For what it's worth, Apple do use a static analyser - they even wrote their own, and it's actually pretty good. If I remember correctly, it's even activated by default for new projects in XCode these days.
But static analysers are not perfect, and theirs is apparently not clever enough to catch this bug. Maybe they will patch the analyser in response to this bug, or maybe not - there is a trade off between speed and thouroughness with static analysers.
- pjmlp 12y agoIt is one thing to have a static analyzer in the compiler, which is quite good. Clang almost makes C feel like Pascal. And another very distinct one, is having the respective coder use it
- anon1385 12y agoYou have not demonstrated that the clang static analyser was able to detect this. You are going to have to do that before you start firing off accusations that the developers at Apple ignored the warnings.