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? Maybe ? What trade-offs have you considered ? On reason to use categories is just to break large class implementations into separate files for whatever reason: logical grouping, separate authors, short files, incremental compilation,... Don't implement the same method in multiple categories though. That least to chaos quickly because the order in which categories load is unspecified and can change. _______________________________________________
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
