はてなブックマーク

A while back I posted instructions for how to document Objective-C with Doxygen. In part 2 I published a very basic helper script to make it less onerous to document code in Xcode 3. While the script wasn’t perfect, I think it using it was definitely more convenient than writing every documentation comment entirely by hand. One of the changes in Xcode 4 is that there is no support for user defined

A while back I described a method for creating singletons in Objective-C. Since I wrote that, Apple has released automatic reference counting. My original example demonstrated how to prevent reference counts for singletons from decreasing. While this is still a valid approach, it would be nice to not have to get involved with reference counting at all. Also, the basic template for a singleton was

This approach no longer works with Xcode 4. Read Using the Doxygen Helper in Xcode 4 for a work around. In part I I covered how to comment your code with javdoc style comments that can be extracted into html documents or other types of output. What I want to cover in this post is how to incorporate documenting your code into your workflow. The first problem to tackle is the additional overhead inc

As I alluded to in my earlier post regarding memory management, I recently had a tricky bug using Core Data on multiple threads in my current project. The scenario is this: I have an import operation that runs on a background thread that reads a very large amount of data from a MySQL database and imports it into the local data store. It’s more than a stupid import; the operation makes sure that al