Re: Question about structs and enum placement in a project

I've broken out a folder "Structs and Enums" with sub-folders based on related areas of operation. I'm currently prototyping so I don't have tons and tons of operation types. Seems good enough, adds organization, and it keeps my classes much cleaner. I will probably end up with less than a dozen

Re: Question about structs and enum placement in a project

If they’re not being declared inside another object, why not put them in their own files? > Am 13.07.2017 um 15:53 schrieb Eric E. Dolecki : > > Perhaps. Then maybe a folder of categorized structs and enums? I personally > dislike seeing them sprinkled throughout

Re: Question about structs and enum placement in a project

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 wrote: >

Re: Question about structs and enum placement in a project

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

Re: Question about structs and enum placement in a project

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 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

Question about structs and enum placement in a project

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 (Cocoa-dev@lists.apple.com) Please do not post admin requests or