
Xcode 3.2 introduces a revolutionary feature known as static analysis. You can think of static analysis as advanced warnings, identifying bugs in your code before it is run - hence the term "static". Unlike traditional compiler warnings, the Xcode 3.2 static analyzer has a much deeper understanding of your code. By traveling down thousands of possible code paths, the analyzer identifies logical errors such as unreleased memory—well beyond simple syntax errors normally found at compile time.

Let Xcode Find the Problem and Show You
Xcode's static analyzer runs as part of the build process, but when a coding mistake is identified, Xcode integrates the analysis report in a truly innovative manner. Message Bubbles appear beside the suspect code, and upon clicking the message bubble, the editor walks you through the logical steps in your code using graphical arrows. These arrows step you through the code that leads to the identified bug. By following the arrows through your code, it becomes clear why your objects may be leaking, where coding conventions may be misused, or why your case statements never return the values you expect. These bugs would otherwise have been found at runtime, perhaps after your application was already in production.