This is a replay of a post I recently submitted to iPhoneSDK to explain why using non-mutable objects like NSString to learn leak detection is a bad idea.
The original post by Robert Scott complained that this code wasn’t showing Leaks in instruments even though it should be leaking a NSString with every pass.
I recently saw this post on turning off NSLog for non-debug builds, and found it disappointing and inspirational at the same time. Scattering hundreds of #ifdefs around code is a recipe for disaster. Eventually some non debugging code will end up inside the #ifdef and the debug and release builds will function differently, making debugging more difficult.
I’m not a big fan of debugging from log statements, but they can occasionally be useful.
What follows is details on building a full NSLog() replacement that turns off with a single #ifdef in the header file that contains the function. You can either download the m and h file, or continue on to the extended entry for an explanation of how it works and ways to make it more useful for your particular needs.
Every time I try to quit Versions it pops up an alert and says “Waiting for transactions to finish”. The alert will stay on the screen until I force quit Versions. This makes every reboot or logout a painful process.
This has been driving me crazy for awhile now, so I looked into the problem and found a “solution”. While I can’t vouch that it will work for everyone, I wanted to share it in the hopes that it might work for some.
This is going to be long so that everyone can understand the cause and possible soutions.
My twelve year old son brought to my attention a security bug he discovered on his iPhone. He has an even more paranoid security mind than I do, because he primarily uses his iPhone to send and receive sweet nothings between himself and his girlfriend, and he is certain that his mother and I are desperate to intercept these messages.
At the end of August my first iPhone application HazMat went on sale via the iTunes App Store. During the past 6 months I have been having private conversations with various individuals about the development process and the resulting sales experience, and I thought it might be useful to others to collect this in a narrative about the application. My goal is to give a full open view about the problems, pitfalls and pleasures of writing iPhone applications.
Send questions via email
Those of you solely interested in my sales number can check them here.
