> There are old-school reasons and new-school reasons. > > One of the biggest old-school reason is source duplication. You have to write > everything “twice”, once in @interface, once in @implementation. This has > been mitigated somewhat over the years, but Obj-C is literally twice the > number of files as Swift, and (in my experience so far) twice the number of > source lines to do the same thing.
You don’t have to “write everything twice”, (you *might* do that, but you don’t have to). The only thing you have to define “twice” are public methods and you just copy and paste these anyway. There are more files, but the .h file is generated automatically when you create the Class, so it’s no big deal. Dave _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
