Also remember that although "1 class per file" is usual practice, there's nothing in the language that requires it.
If the cleanest solution turns out to be 22 very small and somewhat similar classes, put them in 1 file (well ok, 2) instead of spreading them between 22 (well ok, 44) files. -- Scott Ribe scott_r...@killerbytes.com http://www.killerbytes.com/ (303) 722-0567 voice _______________________________________________ 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
