• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Categories and splitting an app into logical blocks.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Categories and splitting an app into logical blocks.


  • Subject: Re: Categories and splitting an app into logical blocks.
  • From: Erik Buck <email@hidden>
  • Date: Fri, 15 May 2009 14:09:54 -0700 (PDT)

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 (email@hidden)

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:

This email sent to email@hidden

  • Prev by Date: Re: User Access Rights
  • Next by Date: Re: NSCFArray autoreleased with no pool in place
  • Previous by thread: Re: Categories and splitting an app into logical blocks.
  • Next by thread: Re: Categories and splitting an app into logical blocks.
  • Index(es):
    • Date
    • Thread