Folders are good. I’d avoid glomming too many types into one file, because 
you’ll spend a lot of time scrolling through that file looking for things. 
Better to break things into smaller files where possible.

Charles

> On Jul 13, 2017, at 8:53 AM, Eric E. Dolecki <[email protected]> wrote:
> 
> Perhaps. Then maybe a folder of categorized structs and enums? I personally 
> dislike seeing them sprinkled throughout AppDelegate & other classes. It's 
> easy to cntrl-click to where they are defined, but it seems like a lot of 
> clutter.
> 
> On Thu, Jul 13, 2017 at 9:52 AM Charles Srstka <[email protected] 
> <mailto:[email protected]>> wrote:
> For a project of any appreciable size, that’s gonna be one huge file…
> 
> Charles
> 
> > On Jul 13, 2017, at 8:37 AM, Eric E. Dolecki <[email protected] 
> > <mailto:[email protected]>> wrote:
> >
> > I am planning on putting all my structs and enums into it's own swift file
> > - to keep my project cleaner. Seems safe enough, thoughts on this?
> >
> > Thanks,
> > Eric
> > _______________________________________________
> >
> > Cocoa-dev mailing list ([email protected] 
> > <mailto:[email protected]>)
> >
> > Please do not post admin requests or moderator comments to the list.
> > Contact the moderators at cocoa-dev-admins(at)lists.apple.com 
> > <http://lists.apple.com/>
> >
> > Help/Unsubscribe/Update your Subscription:
> > https://lists.apple.com/mailman/options/cocoa-dev/cocoadev%40charlessoft.com
> >  
> > <https://lists.apple.com/mailman/options/cocoa-dev/cocoadev%40charlessoft.com>
> >
> > This email sent to [email protected] 
> > <mailto:[email protected]>
> 

_______________________________________________

Cocoa-dev mailing list ([email protected])

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 [email protected]

Reply via email to