views:

51

answers:

2

I'm diving into iOS development and I just found out about the Static Analyzer and it's been pointing out all sorts of mistakes I was making in the code. The Static Analyzer doesn't really seem to eat up any extra time when building and so I'm wondering why it isn't enabled by default.

Are there any reasons you wouldn't want to use the Static Analyzer every time you build your iOS app?

Thanks in advance for your help!

+4  A: 

No, I use it all the time. One cannot have enough help tracking down all the bugs :-)

Anders K.
thanks, anders. while we're on the topic, are there any other goodies that aren't turned on by default that you recommend I start using?
BeachRunnerJoe
For debug builds switch to the CLANG/LLVM 1.5 compiler, which will give you even more warnings...
Kendall Helmstetter Gelner
@BeachRunnerJoe: "Treat Warnings as Errors." That should definitely have been turned on by default.
Rob Napier
+1  A: 

Mostly because it does eat up extra time when you build your app. Your app is probably pretty small or you'd notice the difference. When your app takes 10-20 minutes just to compile, you're more likely to just run static analysis "from time to time." Before you commit is a good time to do it.

Rob Napier