On 15 May 2009, at 2:57 PM, Тимофей Даньшин wrote:
Is it a good idea to split all those classes into categories for
writing, reading and testing? For example, Database (Writing),
Database(Reading), Database(Testing) and so on? Or is it a silly
thing to do for some reason?
That's something for you to judge. If you find categories make your
code easier to understand, or help in breaking the methods into
separate implementation files (and therefore making it easier to
understand), by all means break your class into categories.
I _think_ there's a (negligible) overhead in loading a category from a
separate dynamic library, but none for categories in a single linkage
unit. I expect someone may correct me on this.
— F
--
Fritz Anderson -- Xcode 3 Unleashed: Now in its second printing -- <http://x3u.manoverboard.org/
>
_______________________________________________
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
