@Jim Getzen: but having to switch back and forth between a source file and its header when I want to add/change a method or instance variable is inconvenient
Not as incovenient as not having headers to look at. :) Some of this may come down to project size and whether you're the only author or not, buy having a nice, summarized view of all the methods sure seems pretty nice to me.
Also, keep in mind that Objective-C doesn't force you to declare methods ahead of time. I often go along adding methods on the fly while I'm experimenting, and them only go back and add them to the header later if I plan to keep those methods around.
possible circular references
Do you mean double-includes? #import prevents that.
by Scott Stevenson — Feb 20
Not as incovenient as not having headers to look at. :) Some of this may come down to project size and whether you're the only author or not, buy having a nice, summarized view of all the methods sure seems pretty nice to me.
Also, keep in mind that Objective-C doesn't force you to declare methods ahead of time. I often go along adding methods on the fly while I'm experimenting, and them only go back and add them to the header later if I plan to keep those methods around.
possible circular references
Do you mean double-includes? #import prevents that.