From my dabbling and learning IOS development, the biggest problem that I expect my code will have is memory leaks. I can understand that as a very limited embedded computer, its an engineering tradeoff of features vs memory/time/code/bugs/... but the idea of a programmer managing his own memory makes me shudder.
Memory management in iOS isn't that bad or difficult, retain and release policy is really clear. Maybe we are spoiled by garbage collected languages.
All you need are three or four rules when it comes to memory management, crystal clear.
You can found and solve your memory leaks using Static Analyzers and with Instrument tools.
Using Build and Static Analyze, you will get all the possible leaks in your code at compile time.
Using Instrument tools, you can find run time leaks. These are very useful to handle memory management.
With the iOS 5 you can handle garbage collection by exploiting features like Automatic Reference Counting - ARC which allows you to track the reference count of variables and thus collect them.
Java Pal - Your friend in technology and innovation...India.
Thats a good features in iOS 5.
But in lower versions as well as in iOS 5, the build and analyze and Instrument tool is very useful. ARC is one more feature to handle memory after iOS 5.
Thanks,
Niketa.
Yes, of course, and I accept that blame. In fact, i covet that blame. As does this tiny ad:
a bit of art, as a gift, the permaculture playing cards